I am going to change the license for text contributions to the wiki.
Currently, text is licensed under the GNU Free Documentation License (FDL).
For some reasons (see discussion of
http://www.linuxtv.org/pipermail/vdr/2005-February/000072.html), i will
change the license to GPL.
All translated articles currently in the wiki will preserve the FDL licence
and will get a hint, until they are rewritten from scratch.
Only articles i have the (only) copyright on will be relicensed.
Has anyone …
[View More]objections against this intention or the procedure?
With regards,
Thomas
[View Less]
> > * U.S. patent number 6,847,778, entitled Multimedia Visual Progress
> > Indication System, which describes, among other things, methods for
> > displaying a trick play bar to a user which visually indicates the
> > amount of stored program material or the length of a
> recording session
> > as well as the user's current position within the stored program
> > material.
>
> This means we can't use a progress bar? How absurd.
(I am sorry I …
[View More]haven't uploaded english patent dictionary into my head, but
patent knowledge is there :)
- I am 100% sure there was programs earlier than TiVo's patent apply where
such progress bar is available. Xing players in early 90's? This would
void the patent or give first right use to products used that prior TiVo's
apply date.
- If patent were OK, then countries/areas where patent has been applied and
granted cannot use such feature => US VDR users cannot see progress bar
without a license.
- Tivo has also right to first claim patent in EU, but if it hasn't done
that EU users can use patented technology.
- But patent isn't automatic. You can use and build such features. Tivo has to
start asking VDR communities for license fees. And after that battle begins.
NOTE: I haven't checked patent claims (what Tivo is actually claiming).
> > * U.S. patent number 6,792,195, entitled Method and Apparatus
> > Implementing Random Access and Time-Based Functions on a Continuous
> > Stream of Formatted Digital Data, which describes methods of
> > controlling streaming media in a digital device, including the
> > functions that enable DVRs to pause live TV as well as rewind,
> > fast-forward, play, play faster, play slower, and play in reverse
> > television signals cached by the DVR.
>
> So, now its too late. We can never have a replay buffer? I
> really wanted to implement that.
Again, was replay buffer published knowledge (on forum, mailing list etc) prior
apply date by Tivo?
> > * TiVo has also acquired the exclusive right to license and enforce
> > U.S. patent number 5,241,428 entitled Variable- Delay Video
> Recorder
> > known in the industry as the Goldwasser Patent. Filed in
> March 1991,
> > the Goldwasser Patent is one of the earliest patents
> regarding digital
> > video recorders of which TiVo is aware. This patent covers devices
> > that permit the simultaneous recording and playback of
> video material
> > with a variable time delay between recording and playback
> of a given
> > video program segment.
> >
>
> Doesn't VDR already do this as well? So, legally, we cant
> record and playback at the same time? Ridiculous.
Patentwise this is the hardest thing for VDR to counter, and every other
recording/playback device because it is so old (1991). On the otherway,
patent would expire after 11 years.. :-)
I just want to remind open source communities, publish on mailing list new
ideas. That makes acquiring patents very hard (or if patent is given, then
it is easy to counter)! It is cheap, usually your monthly ADSL fee.. :-)
(Or you can patent it by yourself if you have the money, and sell licences
to Tivo to gain money).
Best regards, Jori
[View Less]
VDR developer version 1.3.22 is now available at
ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.22.tar.bz2
*** NOTE THAT THE WARNINGS REGARDING THE USE OF VPS CONTROLLED
*** TIMERS FROM PREVIOUS RELEASE NOTES STILL APPLY!
The changes since version 1.3.21:
- Removed some unneeded code and fixed access to unallocated memory in
cEvent::FixEpgBugs() (thanks to Wolfgang Rohdewald).
- Avoiding unnecessary calls to SetPid() in cDvbDevice::SetAudioTrackDevice()
(thanks to Marco Schlüßler).
- …
[View More]No longer calling EnsureAudioTrack() in cDevice::SetChannel() if a Transfer Mode is
started, to avoid setting the audio PID on the primary device (thanks to Marco
Schlüßler for pointing this out).
- Replaced the call to system("sync") in SpinUpDisk() with fdatasync(f) to avoid
problems on NPTL systems (thanks to Chris Warren for pointing this out).
- Increased POLLTIMEOUTS_BEFORE_DEVICECLEAR in transfer.c to 6 to avoid problems
with the larger buffer reserve (thanks to Marco Schlüßler).
- Fixed the call to SetVideoFormat() in cDvbDevice::cDvbDevice() (parameter is _bool_).
- Added support for setting the video display mode (thanks to Marco Schlüßler).
- The new setup option "DVB/Video display format" can be used to define which display
format to use for playing wide screen video on a 4:3 tv set.
- Changed MAXDPIDS to 16 (8xAC3 + 8xDTS) (thanks to Werner Fink for pointing this out).
- Completed dutch language texts (thanks to Hans Dingemans).
- Added 'smi' to the Finnish language codes (thanks to Rolf Ahrenberg).
- Fixed ensuring there is a current audio track in case there is only one track
(thanks to Werner Fink for reporting this one).
- Improved automatic audio track selection.
- Keeping the track language codes and descriptions in Transfer Mode (thanks to
Luca Olivetti).
- Fixed handling repeated kAudio keys.
- Improved displaying the the current audio track in the ST:TNG channel display.
The DVB driver I am currently using can be found at
ftp://ftp.cadsoft.de/vdr/Developer/linux-dvb.2004-12-26.tar.bz2
which is the CVS 'HEAD' version from 2004-12-26, made available as a complete
archive for your convenience.
Of course, you can also use any newer driver version.
Have fun!
Klaus
[View Less]
Hi,
I just upgraded to vdr 1.3.22 and discovered that there are still
problems with playback over NFS and 54 MBit WLAN.
When I read the the video files with dd and 8kB blocksize I get a data
rate of about 1200 kB/s, and this should be sufficient to playback any
recording.
It seems that vdr doesn't fill used buffer aggressively enough. The file
reader should keep the buffer at the top limit so that dvbplayer always
has enough data available. When I stop playback I get the info that 0 %
of …
[View More]the buffer was used.
I also increased various buffer sizes like PLAYERBUFSIZE to 8 MB, but
this didn't help this time. In 1.2 this solved any problems most of the
time.
I activated DEBUGRINGBUFFERS and set logging to 3 but I don't get any
output.
Any ideas?
Emil
[View Less]
> >>TIVO GRANTED EIGHT NEW DOMESTIC AND FOREIGN PATENTS The
> United States
> >>Patent and Trademark Office (USPTO) recently issued new patents to
> >>TiVo covering important aspects of DVR software and hardware design.
> >
> >
> > What can I say but Aaaaaaarrrggghhhhh!!!!!!!
> >
> > What was that Clash song again? "I'm so bored with the U.S.A."...
>
> Well, thanks to the EU commission that has repeatedly ignored
> the …
[View More]EP decisions, we're going the same route.
And again if open source communities have made such features and published them
before the date Tivo applied for patent, that is the easy way of removing the
patent.
USPTO doesn't check google for that stuff.. :-) They take money from
companies by allowing them to patent things, and decide later if that
patent was a valid one.
BR, Jori
[View Less]
> Well, like I think I said, a good LCD should give crisper
> text than a CRT. In fact, it can appear too crisp and look a
> bit ugly without anti-aliasing, but I do find old-fashioned
> pixelly LucidaTypewriter still the most usable for terminals.
<IMO>
Also check your tube. Put black background and white text and type
whole screen full of h -character for example. Now look closely,
is your tube aligned correctly, so you see white h, not h with a
red shadow. Problem is …
[View More]more visible on edges of screen. I'd say
even cheap LCD with DVI is unaffected with this.
Then check fall-out of light intensity on edges of tube. Also LCD should be
checked for this, and for backlight 'pollution' when on black background.
Then put some software blinking black and white background, with lines
on screen. Does frame geometry change on you tube? On tube-TV's normally
it does. And some poor monitors with inadequate power supply.
So you need to decide which annoys you more. Possibility of one or couple
of dead pixels or blurry analog image with uneven colors. Go to movies
and sometimes you can see dust in theatre's hardware. Black pixels throughout
the film you paid to see.. :-)
Then with video and 60Hz, that is completely ok with LCD/TFT because picture
won't flicker. And applies same to 50Hz. So you don't need to play with
1920x1080@120Hz -modes which which is high bandwidth and introduces softness
on analog video signals.
Of course there is the color gamut thing, but I am not prepared to write
about that.. :-)
Some both technologies has its benefits. I prefer LCD and digital technology
because it removed my head aches because of eye fatigue. And I don't like anti-
aliased text on screen because it 'softens' the focus. It is better so see
pixels and use resolution high enough (1600x1200).
But on DVB & DVI, frame transfer chain is too perfect. All DVB encoding artifacts
are too visible. That is the bad side. HDTV is much better, and nothing wins on
seeing HDTV on projector (which on my case is "cheap" and not 1080-resolution.. :-)
Only MPEG compression on gradients annoy. Why sunsets needs to look like coming through
solarise filter?
With DVB material the FF-DVB card's composite out is good way of hw anti-alias,
and the output quality is ok. Maybe S-Video would reduce color bleeding more.
For RGB sync on green circuitry must be built. :-(
</IMO>
Best regards, Jori
[View Less]
Please can you help me with compiling dxr3 plugin for vdr.
I use vdr 1.3.14 vdr-dxr3-0.2.2 and ffmpeg 0.4.6
When I try make plugins I got following output:
make[1]: Entering directory `/video/vdr/PLUGINS/src/dxr3'
make[1]: Leaving directory `/video/vdr/PLUGINS/src/dxr3'
make[1]: Entering directory `/video/vdr/PLUGINS/src/dxr3'
g++ -O2 -Wall -Woverloaded-virtual -c -DPLUGIN_NAME_I18N='"dxr3"'
-DSOCKET_CHMOD=0660 -D_GNU_SOURCE -I../../../include
-I../../../../DVB/include -I../../../../ffmpeg …
[View More]dxr3.c
In file included from dxr3osd.h:14,
from dxr3abstractiondevice.h:17,
from dxr3syncbuffer.h:15,
from dxr3demuxdevice.h:14,
from dxr3device.h:17,
from dxr3.c:10:
spuenc.h:52: error: syntax error before `*' token
spuenc.h:91: error: `cWindow' was not declared in this scope
spuenc.h:91: error: `win' was not declared in this scope
spuenc.h:91: error: parse error before `,' token
spuenc.h:93: error: parse error before `*' token
In file included from dxr3abstractiondevice.h:17,
from dxr3syncbuffer.h:15,
from dxr3demuxdevice.h:14,
from dxr3device.h:17,
from dxr3.c:10:
dxr3osd.h:16: error: parse error before `{' token
dxr3osd.h:21: error: `cWindow' was not declared in this scope
dxr3osd.h:21: error: `Window' was not declared in this scope
dxr3osd.h:23: error: parse error before `protected'
dxr3osd.h:25: error: `cWindow' was not declared in this scope
dxr3osd.h:25: error: `Window' was not declared in this scope
dxr3osd.h:25: error: virtual outside class declaration
dxr3osd.h:25: error: variable or field `CommitWindow' declared void
dxr3osd.h:26: error: `cWindow' was not declared in this scope
dxr3osd.h:26: error: `Window' was not declared in this scope
dxr3osd.h:26: error: virtual outside class declaration
dxr3osd.h:26: error: variable or field `ShowWindow' declared void
dxr3osd.h:27: error: `cWindow' was not declared in this scope
dxr3osd.h:27: error: `Window' was not declared in this scope
dxr3osd.h:27: error: parse error before `)' token
dxr3osd.h:27: error: virtual outside class declaration
dxr3osd.h:28: error: `cWindow' was not declared in this scope
dxr3osd.h:28: error: `Window' was not declared in this scope
dxr3osd.h:28: error: parse error before `,' token
dxr3osd.h:28: error: virtual outside class declaration
dxr3osd.h:29: error: `cWindow' was not declared in this scope
dxr3osd.h:29: error: `Window' was not declared in this scope
dxr3osd.h:29: error: virtual outside class declaration
dxr3osd.h:29: error: variable or field `CloseWindow' declared void
dxr3osd.h:31: error: parse error before `public'
dxr3osd.h:33: error: destructors must be member functions
dxr3osd.h:33: error: virtual outside class declaration
dxr3osd.h:34: error: parse error before `}' token
In file included from dxr3syncbuffer.h:15,
from dxr3demuxdevice.h:14,
from dxr3device.h:17,
from dxr3.c:10:
dxr3abstractiondevice.h:72: error: syntax error before `*' token
In file included from dxr3device.h:17,
from dxr3.c:10:
dxr3demuxdevice.h:41: error: syntax error before `*' token
In file included from dxr3.c:10:
dxr3device.h:55: error: ISO C++ forbids declaration of `cOsdBase' with no type
dxr3device.h:55: error: `cOsdBase' declared as a `virtual' field
dxr3device.h:55: error: parse error before `*' token
../../../include/vdr/device.h:132: warning: `virtual int
cDevice::ProvidesCa(const cChannel*) const' was hidden
dxr3device.h:54: warning: by `virtual int cDxr3Device::ProvidesCa(int)'
make[1]: *** [dxr3.o] Error 1
make[1]: Leaving directory `/video/vdr/PLUGINS/src/dxr3'
[View Less]
Hi,
I am running vdr-1.3.22 with graphlcd 0.1.2-pre4 and sometimes get a
segmentation fault in the graphlcd code when stopping a replay with the
"exit" key. This happens mostly when I stop replaying a VDR recording,
but I've seen this too when I terminate MP3 playback in the MP3 plugin.
The following backtrace is from a crash after stopping a VDR reording:
#0 cChannel::GetChannelID() const (this=0x0) at channels.h:66
66 tChannelID(int Source, int Nid, int Tid, int Sid, int Rid = 0)
{ …
[View More]source = Source; nid = Nid; tid = Tid; sid = Sid; rid = Rid; }
(gdb) bt
#0 cChannel::GetChannelID() const (this=0x0) at channels.h:66
#1 0x403790bf in cGraphLCDState::SetChannel(int) (this=0x8960900,
ChannelNumber=0) at state.c:552
#2 0x40377b4c in cGraphLCDState::Replaying(cControl const*, char const*) (
this=0x8960900, Control=0xbffff140, Name=0x0) at state.c:269
#3 0x080d7069 in cStatus::MsgReplaying(cControl const*, char const*) (
Control=0x82d4768, Name=0x0) at status.c:41
#4 0x080b0672 in ~cReplayControl (this=0x82d4768) at menu.c:3292
#5 0x080bca12 in cControl::Shutdown() () at player.c:84
#6 0x080e3318 in main (argc=5, argv=0x0) at vdr.c:781
Has anybody seen this too?
Wolfgang
[View Less]
Hello,
I'm pleased to announce a new pre-release of vdr softdevice plugin.
In short words: softdevice plugin is for getting vdr to your desktop with
so called budget cards. You'll get vdr output via framebuffer or X11-Xv or
DirectFB or vidix to your screen. Decoding is done via ffmpeg.
For compile options, please read the Makefile carefully and decide which of
the available output methods fit to your system.
Plugin's homepage is located at: http://softdevice.berlios.de/
Changelog since …
[View More]last release:
2005-03-04: 0.1.0pre1
- some i18n changes
2005-03-03:
- fb-out: fix for build option USE_SUBPLUGINS
fix alpha mask misplacement
fix locking during video and OSD drawing
2005-03-02:
- increased osd fallback timeout
- removed syoff and sxoff from Draw(...)
2005-02-27:
- save "vo" and "ao" calling args in setup store.
- new runtime arg "-L path_name". Default set in Makefile to: "./PLUGINS/lib"
- USE_SUBPLUGINS is now default build option
- dfb-out: fix for segfault on via unichrome with current DirectFB cvs.
2005-02-25:
- vidix-out: fix segfaults upon switch from software OSD back to pseudo mode.
match available fourcc against selected.
support for YUY2 added (without soft alpha [todo]).
- all-out: unified constuctor parameter
optionaly output method is loaded at runtime. by this, one can
build and ship binaries with all methods enabled to target
enviroments where not all libs are present.
- removed obsolete OSD option "sync on" (I-frame/all frames).
2005-02-18:
- support for DIRECTCOLOR framebuffer ( most ATI cards, tested with Mach64)
- fixed osd flickering in framebuffer mode vdr>1.3.7
- software alpha blending implemented for Vidix (vdr>1.3.7)
- software alpha blending done in software for Xv out and vdr>1.3.7
- osd scaling for vdr and Xv >1.3.7
2005-02-13:
- a/v sync: auto adjusting back index instead of using fixed value 4
2005-02-08:
- dfb-out: fix for field parity in tv-out mode
- xv-out: fix compile warnings on amd64 (reported by Konrad Naumann)
2005-01-23:
- added suspend video playback patch.
2005-01-15:
- fix OSD drawing when multiple areas are used (with text2skin plugin)
- dfb out: reverted top-field first setting as it may crash
- removed some unused code
- subtract already spend time from delay before entering delay loop
(found by Stefan Lucke)
- audio pts calculation changed to use sample rate and number of channels
2005-01-13:
- compatibility fix for vdr-1.3.18
- aspect ratio handling for 16:9 TV output
- dfb-out TVout: set top field first and acpect scaleing for TV mode if not set
2005-01-12:
- fix aspect ratio calculation/recognition on some dvds
By subscribing to the to cvs list via
https://lists.berlios.de/mailman/listinfo/softdevice-cvs
you'll get informed about lastest changes.
For those who are interested in active development, subscribing to
https://lists.berlios.de/mailman/listinfo/softdevice-devel
is a good choice.
Members of softdevice development crew are:
Torgeir Veimo, Martin Wache and me, Stefan Lucke.
--
Stefan Lucke
[View Less]