Hi,
I'm looking for help with my vdr 1.6 system.
I think the problem only affects BSkyB channels Channel4, More4,
E4 and Film4: those channels a/v are out of sync (sometimes
more, sometimes less). Recordings from those channels are also
affected.
I think that at some point, I didn't have this a/v sync issue,
but I could be wrong.
My vdr uses vdr-xine with a new xine-lib 1.2 (for vdpau) as
output device.
Due to the unstable nature of some of the components, I've tried
exchanging parts of …
[View More]my output chain to their stable
counterparts: xine-lib 1.1.17, ffmpeg-0.5, xine-ui-0.99.5.
Also, I've tried deactivating "Dynamic Ticks" in the kernel.
None of those measures have helped.
Can anyone here point me to where the a/v sync issue is most
likely to originate from?
Can it be vdr itself? Does vdr process video separate from
audio?
>From what I've read so far, xine-lib delegates MPEG TS
processing to ffmpeg.
[View Less]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello list.
As the subject already says, this is about VDR portability, or how to get
VDR up and running on a FreeBSD system.
In times where we have such really nice plugins like softdevice and
streamdev, we no longer need real MPEG2 or DVB hardware in a VDR system.
As i want to use my FreeBSD systems to watch TV or play VDR recordings i
decided to give porting VDR to FreeBSD a try.
Attached you can find the results.
In short terms: It simply …
[View More]works!
The only missing feature right now is, starting VDR as root and switching
to another user (-u command line option).
For now it is possible to watch any recording made by a VDR with real
hardware if the video directory is directly accessible over the network
(mountable by the client) or the use the streamdev plugin to stream VDR to
VDR.
All tests where done using a Linux system with two FF-DVB-S devices,
streamdev-server plugin and NFS exported video directory plus a wired and
a wireless FreeBSD-7.0 client running VDR with streamdev-client and
softdevice plugin.
As far as i could test the whole setup until now, everything works the
same way on FreeBSD as it does under Linux and i now have real
channel-hopping.
The patches are made in a way that a patched VDR will still compile under
Linux. Every modification, to the source or to the Makefiles is ifdef'd
out. So unless you say you want to compile VDR for FreeBSD you have an
unmodified version of source.
In case the ML software strips the attachments, the files are also
available for download at: ftp://ftp.frm2.tum.de/pub/jpulz/VDR/
Thoughts or comments from others are welcome.
regards
Joerg
- --
The beginning is the most important part of the work.
-Plato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
iD8DBQFH0Dy8SPOsGF+KA+MRAmVBAJ9Tzfxg0zWNN/fEX8vfeMOW2muvSACgivha
raTzC4R92jZ+Petp9Mqwr9E=
=f08n
-----END PGP SIGNATURE-----
[View Less]
Hi guys, do any of you have information with regards to Dual DVB-S2
Tuners on a PCI or preferably a PCI-E type card working on vdr?
I did have a look on http://www.linuxtv.org/wiki/index.php/DVB-S2_PCIe_Cards
But only mentions 2 and they seem to be a rare find. Well at least where I live.
Does anybody else know of working DVB-S2 cards for Linux? I did find
plenty of Hybrid/Dual type cards but they seem to be supporting DVB-T
+ DVB-S/S2 and not even both at the same time :(
Any advice would …
[View More]be appreciated.
Thanks,
Theunis
[View Less]
Hello list,
At the moment if I press the Guide button (or select a specific program
from EPG list) i can see the detailed description of the event. Now
pressing up/down or left/right scrolls the "Long Description", if this
doesn't fit in the OSD window.
I wonder if it's possible to implement a different behaviour for the
left/right keys: to "scroll" between programs. Pressing right should
bring up the next event, pressing left should bring up the previous
event. To scroll in the OSD …
[View More]window Up and Down are fine.
thanks,
Füley István
[View Less]
Hi
When we delete index file on some HD recording due to synchronous problem for
editing, sometimes vdr is not able to rebuild it , start for few seconds and
generate an errors
Stream has "something" in it, you can add mark but not navigate between
without crashing vdr , when playing records, time goes not seconds to seconds
but every two seconds
Is it possible for next release to increase the buffer size to 300 instead of
100 in recording.c , class cIndexFileGenerator ? This has been …
[View More]tested
successfully by at least two users with same problem
Thanks in advance
[View Less]
> From: "Simon Baxter" <linuxtv(a)nzbaxters.com>
> Subject: [vdr] PVRINPUT plugin and "black/cinema bars"
>
> Hi Everyone
>
> My machine has (among others) a PVR-500 dual-channel analog card and I'm
> running vdr-1.6.0 with pvrinput-2008-07-05.
you should upgrade to our new pvrinput version:
http://projects.vdr-developer.org/attachments/download/288/vdr-
pvrinput-2010-04-14.tgz
see http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/HISTORY
>
&…
[View More]gt; Doesn't matter which aspect ratio I choose, every channel under the PVR-500
> displays with black (cinema) bars on the top and bottom of the image.
I am pretty sure that your TV station broadcasts analogue TV not anamorphic,
which means it "delivers" the black bars to prevent the aspect ratio of a
16:9 content.
Using the full screen for 16:9 content would result in "egg heads". We call
this anamorphic. A 16:9 TV would stretch this; a 4:3 TV screen would need to
scale it down (generating the needed bars).
At least in Germany analogue broadcastings are never anamorphic.
I gues you are using the extern inputs to supply video from a digital
receiver? Then it could be anamorphic of course. You would need to tell your
digibox that you have a 16:9 TV.
The pvrinput setup-entry "aspect ratio" does not really change the aspect
ratio. It is only an ID inside the mpeg which notifies the TV if it is
anamorphic or not.
Unfortunately there is no way to detect the incoming signal (Tuner or extern).
Therefore it is not possible to automatically choose the right setting.
> Any ideas how to remove these?
The driver does not support clipping/cropping. We will always encode the whole
capture size. If there is already a bar, it will also be in the encoded
stream. You could try to use the zoom mode of your TV.
>
> Plugin setup is as follows:
> pvrinput.BackupHack = 0
> pvrinput.BackupInterval = 30
> pvrinput.EnableDigibox = 1
> pvrinput.FastChannelChange = 1
> pvrinput.RedRemoteDevice = /dev/ledxmit
These setup items have never been in any pvrinput version, so I gues you made
patches. Could you provide them to me?
Greets,
Martin
[View Less]
> From: VDR User <user.vdr(a)gmail.com>
> Subject: Re: [vdr] PVRINPUT plugin and "black/cinema bars"
> > I am pretty sure that your TV station broadcasts analogue TV not
> > anamorphic, which means it "delivers" the black bars to prevent the
> > aspect ?ratio of a 16:9 content.
>
> The 'black bars' are called letterboxing. It's used to _preserve_ the
> aspect ratio of widescreen content on 4:3 displays, not prevent it as
> you've suggested.
I meant …
[View More]that. Sorry for the mistake, english is not my native language.
>
> > Unfortunately there is no way to detect the incoming signal (Tuner or
> > extern). Therefore it is not possible to automatically choose the right
> > setting.
>
> Sure there is, just look in the mpeg headers. If for some reason that
> flag isn't set correctly, you can also use the resolution along with
> some simple math to calculate the aspect ratio.
The mpeg is not delivered by the broadcaster, it is generated by the encoder.
The content of the header is a result of the V4L2_CID_MPEG_VIDEO_ASPECT
setting done by the application.
>
> >> Any ideas how to remove these?
> >
> > The driver does not support clipping/cropping. We will always encode the
> > whole capture size. If there is already a bar, it will also be in the
> > encoded stream. You could try to use the zoom mode of your TV.
>
> You _could_ write some functions to detect and remove letterboxing,
> though I don't know anyone motivated enough to actually do it.
The main goal of the pvrinput-plugin is to use the hardware encoder.I think it
is a bad idea to do software-based on-the-fly-recoding.
Simon, which output device do you use? Maybe the xine- or xineliboutput-Plugin
can do the needed zoom for you. (?)
Greets,
Martin
[View Less]
------Original Message------
From: Halim Sahin
Sender: vdr-bounces(a)linuxtv.org
To: vdr(a)linuxtv.org
ReplyTo: VDR Mailing List
Subject: [vdr] help: translating plugin for vdr-1.7.14
Sent: Apr 27, 2010 13:32
Hi,
I am seeing a small problem when i do this in my plugin:
virtual const char *Description(void) { return tr(DESCRIPTION); }
running make i18n doesn't add the DESCRIPTION string for translation to
the pot file.
Same for Plugin name.
BR.
Halim
…
[View More]_______________________________________________
vdr mailing list
vdr(a)linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
s pozdravom
Marek Hajduk
France-tech s.r.o.
konatel spolocnosti
[View Less]
------Original Message------
From: Halim Sahin
Sender: vdr-bounces(a)linuxtv.org
To: vdr(a)linuxtv.org
ReplyTo: VDR Mailing List
Subject: [vdr] help: translating plugin for vdr-1.7.14
Sent: Apr 27, 2010 13:32
Hi,
I am seeing a small problem when i do this in my plugin:
virtual const char *Description(void) { return tr(DESCRIPTION); }
running make i18n doesn't add the DESCRIPTION string for translation to
the pot file.
Same for Plugin name.
BR.
Halim
…
[View More]_______________________________________________
vdr mailing list
vdr(a)linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
s pozdravom
Marek Hajduk
France-tech s.r.o.
konatel spolocnosti
[View Less]
Hello,
Did anybody try to compile latest wirblescan plugin for vdr 1.7.14? I
mean version 0.0.5-pre11e. I've got these errors:
scanner.c: In member function ‘virtual void cScanner::Action()’:
scanner.c:679:25: error: expected type-specifier
scanner.c:679:25: error: cannot convert ‘int*’ to ‘cSwReceiver*’ in
assignment scanner.c:679:25: error: expected ‘;’
scanner.c:957:28: error: expected type-specifier
scanner.c:957:28: error: cannot convert ‘int*’ to ‘cSwReceiver*’ in
assignment scanner.c:…
[View More]957:28: error: expected ‘;’
make: *** [scanner.o] Error 1
I didn't find maintener's direct email address, that is why I decided to
write to this mailing list.
Regards,
Yarema
[View Less]