Re: [vdr] Converting all recordings to TS?
I'm watching the recording from Playstation3, and it can't play PES format.. I know I could transcode pes-ts with mediatomb or ps3mediaserver, but it's far easier to simply have TS recordings and stream directly with http. Anyway, thanks everyone for all the ideas, I'll look into it.. :) 2010/8/25 Halim Sahin halim.sa...@t-online.de: Hi, Just wondering why you want to convert old vdr recordings to ts? Vdr-1.7.15 can play old recording in pes format. BR. Halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
On Wed, Aug 25, 2010 at 11:16:37PM +0300, Prelude wrote: I have suffered this annoying judder in both live and recording viewing. My config_xineliboutput: http://pastebin.com/kxe7RvX0 xorg.xonf: http://pastebin.com/6fCvWvxU sorry, from that configuration alone I can't tell you what's going wrong. When I started to setup my VDPAU machines (end of last year) I first made sure that the Xserver really is running a 50Hz modeline. I mostly play 25/50Hz streams. This way I found an Xserver bug/misbehavior. Only if I explicitly set the modeline params manually in xorg.conf I get real 50Hz output (instead of 60Hz). Please see attached my xorg.conf. Always try: DISPLAY=:0 nvidia-settings --query RefreshRate to verify. Even the Xorg.0.log lies about the fact that 50Hz are active but in reality it uses 60Hz. Maybe nVidia has fixed that in the meantime. After this tuning to a channel with live ticker gives me perfect results. There is not any judder at all. The problem with all this juddering is that the symptom 'judder' alone gives you no hint at all about the root cause of the problem. Maybe you first verify your current nvidia-settings result. cheers Thomas Section Monitor Identifier Monitor0 HorizSync 50.0 - 60.0 VertRefresh 50.0 Option ExactModeTimingsDVI true Option UseEDID false ModeLine 1920x1...@50p 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync EndSection Section Device Identifier Device0 Driver nvidia Option ModeDebug True EndSection Section Screen Identifier Screen0 Device Device0 MonitorMonitor0 DefaultDepth24 SubSection Display Modes 1920x1...@50p EndSubSection EndSection Section Extensions Option Composite Disable EndSection ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Impact in cDevice::GetDevice
Hi Lars, a third one (just comes to my mind, not deeply thought about): Write a device-plugin which provides a new source. Then you will have your own channels. In each channel entry you can configure which real channels are behind this and the plugin will attach a receiver to the next free real device and passes through the data. That would be a transparent way for recordings, live tv etc. and you don't have to patch vdr (hopefully). You only have to look where to get the epg but I think there's a copy epg from one channel to another-patch... i've also thought about such a function. I stopped thinking about this when recognizing the following (an example): There is a non-ff-device like xineliboutput, softdevice, pvr350 or something like this. Then vdr needs to start the transfer mode. The transfer (cTransferControl resp. cTransfer) object gets attached (i think as a receiver, but perhaps something else). The newly device needs also a transfer object because it is not the device providing the channel. Then there are 2 chained transfer objects. For Recordings, there is a cRecord object. This record objects receives also the stream from a device. There i need another transfer object, too. This complexity gets multiplied with more than one receiver (streamdev, liveview, recordings). At this moment, for me this is like rocket science. There is another, easier way. To introduce such functionality to pvrinput (thats the devices i have and at the moment i'm watching dvb-c channels. if the dvb-c device is in use, i switch to a pvrinput channel). For the (and only for this) channels provided by the pvrinput plugin there is an alternative approach: pvrinput can tune to an analog channel if it is requested for an dvb-c one. Cheers, Rainer ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Converting all recordings to TS?
Thanks for this!
I modified the script slightly, some error checks etc. I also added
directory/file renaming magic so the generated files work with VDR
correctly..
index files are deleted, vdr will regenerate them when you open the first time.
Oh and this script will combine 001.vdr, 002.vdr etc to single
1.ts... This is because I couldn't make multiple file http
streaming work to ps3, now I don't have to worry about that. :) VDR
supports 2GB anyway if you enable it in the settings.
--
Teemu
2010/8/26 Éric Laly el...@free.fr:
Le 25/08/2010 18:43, Teemu Suikki a écrit :
Hi,
I just upgraded to VDR 1.7.15, mainly because I want to watch TS
recordings with PS3, directly from PS3 browser with VDRAdmin and
StreamDev.. I already have it pretty much working, both LiveTV and
recordings work fine. I have been modifying VDRAdmin-am slightly to be
more ps3-oriented. :)
Anyway, now the biggest problem is that I have about 1TB of recordings
recorded with older VDR.. I'd like to convert all of those to TS. :)
Is there some simple shell utility? Writing the actual script is not a
problem, if I just knew what program to use for the conversion.
I've had the same problem recently but with XBMC.
I've written a little script to transcode all my recording (see joined).
For transcoding I've used vlc, the heart of the script is:
cvlc --play-and-exit --sout=#std{access=file,mux=ts,dst=$ts_file}
$pes_file
Hope this can help.
Éric.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--
Teemu Suikki
http://www.z-power.fi/
transcode_pes_ts.sh
Description: Bourne shell script
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
On Thursday 26 Aug 2010, Thomas Hilber wrote: When I started to setup my VDPAU machines (end of last year) I first made sure that the Xserver really is running a 50Hz modeline. I mostly play 25/50Hz streams. This way I found an Xserver bug/misbehavior. Only if I explicitly set the modeline params manually in xorg.conf I get real 50Hz output (instead of 60Hz). Please see attached my xorg.conf. Always try: DISPLAY=:0 nvidia-settings --query RefreshRate to verify. Even the Xorg.0.log lies about the fact that 50Hz are active but in reality it uses 60Hz. Maybe nVidia has fixed that in the meantime. After this tuning to a channel with live ticker gives me perfect results. There is not any judder at all. The problem with all this juddering is that the symptom 'judder' alone gives you no hint at all about the root cause of the problem. I've been following this thread with interest... I had been happily running vdr-1.7.0 with a Matrox G450 video card, softdevice, and a CRT TV. At first, I was using a home-built VGA-SCART lead (these cards can generate composite sync so no need for combining sync signals), and then I found a VGA-sVideo cable (came with a similar graphics card at work, ahem!). Then my old TV blew up and I now have a full-HD LCD TV. I've been using the same setup with the new TV and it still works pretty well for the SD signals I can currently receive. HD is starting to appear in the UK and it seems like a good time to replace my current P4-based vdr box with a smaller, low power unit, and an Nvidia ION systems seems to be the current option (although a lack of PCI slots is a tad worrying, at least for the small form-factor boards!). A couple of quick questions... What is the best method for my current SD broadcasts: home-made VGA- SCART lead or HDMI? (Do any of these boards have sVideo these days?) Do I run the X server at the SD resolution or at 1920x1080 and let xine rescale rather than the TV? I'm guessing run the X server at 1920x1080 and then both SD and HD work easily together (with full HD OSD?). I toyed with the xine and the xineliboutput plugins a _long_ while back: which is the easiest option for getting VDPAU working? Thanks, Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
Hi, Am 26.08.10 12:16, schrieb Laz: Then my old TV blew up and I now have a full-HD LCD TV. I've been using the same setup with the new TV and it still works pretty well for the SD signals I can currently receive. if you new LCD with HDMI use it to connect your HDMI output of the ION board with your TV. Works perfectly here. Xorg works perfectly with it (even sound over hdmi had worked till I upgrade the firware of my Denon receiver :( ). Here the settings from my xorg.conf: Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Device Identifier Card0 Driver nvidia VendorName nVidia Corporation BoardName Unknown Board BusID PCI:3:0:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Viewport 0 0 Depth 1 EndSubSection SubSection Display Viewport 0 0 Depth 4 EndSubSection SubSection Display Viewport 0 0 Depth 8 EndSubSection SubSection Display Viewport 0 0 Depth 15 EndSubSection SubSection Display Viewport 0 0 Depth 16 EndSubSection SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection I use the xineliboutput plugin. Bye, Matthias -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning. -- Rich Cook ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
On Thu, 26 Aug 2010 10:33:48 +0200 Thomas Hilber v...@toh.cx wrote: When I started to setup my VDPAU machines (end of last year) I first made sure that the Xserver really is running a 50Hz modeline. I mostly play 25/50Hz streams. This way I found an Xserver bug/misbehavior. Only if I explicitly set the modeline params manually in xorg.conf I get real 50Hz output (instead of 60Hz). Please see attached my xorg.conf. Always try: DISPLAY=:0 nvidia-settings --query RefreshRate to verify. Even the Xorg.0.log lies about the fact that 50Hz are active but in reality it uses 60Hz. Maybe nVidia has fixed that in the meantime. Are you aware of the interaction between DynamicTwinView and XRandR? The NVidia driver lies to xrandr about the refresh rate if DynamicTwinView is enabled (the default). See NVidia's README. -- TH * http://www.realh.co.uk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
On Thu, Aug 26, 2010 at 03:06:51PM +0100, Tony Houghton wrote: Are you aware of the interaction between DynamicTwinView and XRandR? The no. But if Xorg.0.log tells me (in the bad case): (II) NVIDIA(0): Validating Mode 1920x1080: (II) NVIDIA(0): 1920 x 1080 @ 50 Hz (II) NVIDIA(0): For use as DFP backend. (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 148.50 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2448 (II) NVIDIA(0): HSyncEnd, HTotal : 2492, 2640 (II) NVIDIA(0): VRes, VSyncStart : 1080, 1084 (II) NVIDIA(0): VSyncEnd, VTotal : 1089, 1125 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. [...] (II) NVIDIA(0): 1920x1080_50 : 1920 x 1080 @ 50.0 Hz (from: EDID) [...] (II) NVIDIA(0): Config Options in the README. (II) NVIDIA(0): Setting mode 1920x1080_50 and it uses a 60Hz modeline though this is clearly a Xserver bug for me. - Thomas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Xorg displaying 50 Hz but uses 60 Hz with Nvidia driver (was: Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.)
Am Donnerstag, den 26.08.2010, 16:16 +0200 schrieb Thomas Hilber: On Thu, Aug 26, 2010 at 03:06:51PM +0100, Tony Houghton wrote: Are you aware of the interaction between DynamicTwinView and XRandR? The no. But if Xorg.0.log tells me (in the bad case): (II) NVIDIA(0): Validating Mode 1920x1080: (II) NVIDIA(0): 1920 x 1080 @ 50 Hz (II) NVIDIA(0): For use as DFP backend. (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 148.50 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2448 (II) NVIDIA(0): HSyncEnd, HTotal : 2492, 2640 (II) NVIDIA(0): VRes, VSyncStart : 1080, 1084 (II) NVIDIA(0): VSyncEnd, VTotal : 1089, 1125 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. [...] (II) NVIDIA(0): 1920x1080_50 : 1920 x 1080 @ 50.0 Hz (from: EDID) [...] (II) NVIDIA(0): Config Options in the README. (II) NVIDIA(0): Setting mode 1920x1080_50 and it uses a 60Hz modeline though this is clearly a Xserver bug for me. Do you know if it has been reported to Nvidia? I think the X.org people would not look at it, since you use the proprietary driver. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xorg displaying 50 Hz but uses 60 Hz with Nvidia driver (was: Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.)
On Thu, Aug 26, 2010 at 04:31:28PM +0200, Paul Menzel wrote: Do you know if it has been reported to Nvidia? I think the X.org people would not look at it, since you use the proprietary driver. I dont't know if especially this problem has been reported to nVidia. There are heaps of error reports of that kind reported to nVidia that all sound quite similar. - Thomas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xorg displaying 50 Hz but uses 60 Hz with Nvidia driver
Am Donnerstag, den 26.08.2010, 17:13 +0200 schrieb Thomas Hilber: On Thu, Aug 26, 2010 at 04:31:28PM +0200, Paul Menzel wrote: Do you know if it has been reported to Nvidia? I think the X.org people would not look at it, since you use the proprietary driver. I dont't know if especially this problem has been reported to nVidia. There are heaps of error reports of that kind reported to nVidia that all sound quite similar. I got the same answer from Aaron as Tony told us. Am Donnerstag, den 26.08.2010, 13:58 -0700 schrieb Aaron Plattner: It's not a bug, please see the README: ftp://download.nvidia.com/XFree86/Linux-x86/256.44/README/faq.html#WhyIsTheRefreshdcf0a Thomas, having just VertRefresh 50.0 in your `xorg.conf`, did you measure the 60 Hz directly at the output or were you just saying the tools reported 60 Hz? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
Al 26/08/10 10:33, En/na Thomas Hilber ha escrit: to verify. Even the Xorg.0.log lies about the fact that 50Hz are active but in reality it uses 60Hz. Maybe nVidia has fixed that in the meantime. To watch HD broadcasts I use the hdmi output on my laptop. It isn't configured in xorg but I just configure it on the fly with nvidia-settings in twin-view mode (the laptop panel at 60Hz and the hdmi port at 50Hz). Provided that I disable Force Full GPU Scaling, the tv reports a 50Hz signal. Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xorg displaying 50 Hz but uses 60 Hz with Nvidia driver
On Thu, Aug 26, 2010 at 11:23:22PM +0200, Paul Menzel wrote: Thomas, having just VertRefresh 50.0 in your `xorg.conf`, did you measure the 60 Hz directly at the output or were you just saying the tools reported 60 Hz? without specifying the modeline directly in xorg.conf (the bad case) the tool reported 60Hz, Xorg.0.log reports 50Hz and at the same time it was juddering like mad. This is clearly a bug for me because the Modes 1920x1080_50 setting is ignored and on top of that Xorg.0.log lies about this. After specifying the modeline directly in xorg.conf (the workaround) the tool and Xorg.0.log reported 50Hz. And live ticker scrolled smoothly without any jumping. For me this is evidence enough the tool reported the right thing in both cases. cheers Thomas ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
