Re: [vdr] VDR with S2API (update)
On Mon, 15 Dec 2008 21:50:45 +0200, Seppo Ingalsuo wrote > I wonder if it solves the problems when the channels are not > perfectly in sync? I have a manually sorted DVB-T channels section > but my autosort handled huge amount of DVB-S channels are usually > bit different in vdr instances due to frequent updates. I think > timersync works only when the channel numbers match. A quick glance at the timersync code reveals that indeed it uses channel numbers and not channel ids. I don't know if this is on purpose or not. If you want to give it a try: Edit timersync.c and simply replace every occurrence of "ToText()" by "ToText(true)" (about 14 times). Regards, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
Frank Schmirler wrote: > On Sat, 13 Dec 2008 18:52:52 +0200, Seppo Ingalsuo wrote > >> - The biggest annoyance: Possible to pause live TV only in vdr #1 >> > > Have you tried with the VDR patch from remotetimers-0.1.0? I never took the > time to test it with timersync-plugin, but I'd be interested to see if instant > recordings and pause live TV works with it, too. > I didn't know about the patch. It would be nice to get pause to work! I wonder if it solves the problems when the channels are not perfectly in sync? I have a manually sorted DVB-T channels section but my autosort handled huge amount of DVB-S channels are usually bit different in vdr instances due to frequent updates. I think timersync works only when the channel numbers match. Seppo > Cheers, > Frank > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Am Mon, 15 Dec 2008 17:18:51 +0100 schrieb Nicolas Huillard : > Torgeir Veimo a écrit : > >> Does somebody know the gpu that is used by the 8200 chipset? Is it > >> not G98? > > > > Some information here; > > http://www.nvidia.com/docs/CP/11036/PureVideo_Product_Comparison.pdf > > Is PureVideo the same as VDPAU ? Definitively not, maybe PureVideo HD, but never PureVideo. Currently even not all PureVideo HD devices are supported. as I told already in my other post, this document is not very helpful. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
On Mon, Dec 15, 2008 at 8:18 AM, Nicolas Huillard wrote: > If so, my old (1 year) GeForce 6150 desktop mobo should accelarate H264, > which is a good news, since in my understanding, VDPAU was only for real > new hardware. One of my boxes has a 6150 so of course I would love if it could accelerate h264 in hardware! I don't think it does though. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.2 + h264-patch + xineliboutput + vdr-xine +softdevice
2008/12/15 Goga777 : >> > That's great news! Myself and several others have been patiently >> > waiting an h264 patch for vdr-1.7.1 and now 1.7.2 (for me at least, >> > not sure who else has switched yet)! It will be great to finally have >> > h264 support in vdr's core but until then we still need updated >> > patches. >> >> Ok, I didn't realize that vdr 1.7.1 still needed h264 patch on top of the >> Klaus S2API patch for watching S2 channels. What patch should I apply? > > there are dvb-s2 mpeg2 channels - for it no need any h.264 patch > there are dvb-s/dvb-s2 channels which are using h.264 codec - for their you > should patch the vdr with h.264 patches > havw a look on VDR Extensions Patch > http://www.zulu-entertainment.de/download.php Yup, Goga is right. I think that extentions patch was adapted to 1.7.1 but it comes with a ton of other crap which is why I never bothered with it. I hate those 'mega-patches' or whatever. We'll be happy with just h264 plain patch which it sounds like we'll finally get soon so that's good news! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Torgeir Veimo a écrit : >> Does somebody know the gpu that is used by the 8200 chipset? Is it not >> G98? > > Some information here; > http://www.nvidia.com/docs/CP/11036/PureVideo_Product_Comparison.pdf Is PureVideo the same as VDPAU ? If so, my old (1 year) GeForce 6150 desktop mobo should accelarate H264, which is a good news, since in my understanding, VDPAU was only for real new hardware. -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ~/.xine/config_xineliboutput load/save and name changes
On Mon, 15 Dec 2008, Nicolas Huillard wrote: Is there a way to tell xineliboutput which file to use ? Like adding a command-line param "--config=~/.xine/config_xineliboutput.$(hostname)" The attached patch should implement this - no guarantees. BR, -- rofa xineliboutput-cvs-configfile.patch.gz Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
> -Ursprungligt meddelande- > Från: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] För Pasi > Juppo > Skickat: den 15 december 2008 16:31 > Till: VDR Mailing List > Ämne: Re: [vdr] VDR with S2API (update) > > > Other point : previous emails talk about various possibilities about DVB > > device "location". > > My ideal setup would be : > > * all DVB devices in a single headless always-on server > > * all clients diskless, using an NFS share > > > This would be ideal solution for me as well! > > Br, Pasi > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr That's how I have always used VDR, one server with seven DVB-S/S2/T cards and three diskless clients plus one laptop. Currently I run just one vdr instance on the server and one instance on each client, except the "master" client that connects via xineliboutput to the server's vdr. /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
Nicolas Huillard wrote: > Udo Richter a écrit : > >>> * if 2 VDRs record the same program at the same time, it seems to a be a >>> big problem... If using a slightly different EPG data, this result in 2 >>> recordings with different times, and if using the exact same EPG, this >>> result in something weird and maybe unusable (say, same station, same >>> EPG, one via DVB-S, the other one via DVB-T, two different streams in >>> one file...) >>> >> This would be a lot better with a client-server timer structure. And in >> the end, I'm pretty sure you don't need two VDR instances to record two >> different programs into the same folder, or? >> > > ...this is a human error, but AFAIK nothing prevents it... > > Other point : previous emails talk about various possibilities about DVB > device "location". > My ideal setup would be : > * all DVB devices in a single headless always-on server > * all clients diskless, using an NFS share > This would be ideal solution for me as well! Br, Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Quoting Torgeir Veimo : > Some information here; > http://www.nvidia.com/docs/CP/11036/PureVideo_Product_Comparison.pdf Not very helpful, it doesn't contain the mentioned chipsets. Gerald This message was sent using IMP, the Internet Messaging Program. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Gerald Dachs schrieb: > Quoting Pertti Kosunen : > > >> Gerald Dachs wrote: >> >>> What makes you so sure that the 8200 chipset is not supported? >>> >> It is VDPAU supported, but AFAIK can't decode VC-1. >> > > But what about this post: > http://www.phoronix.com/forums/showpost.php?p=53474&postcount=39 > He must be wrong or you. > > Does somebody know the gpu that is used by the 8200 chipset? Is it not > G98? Some information here; http://www.nvidia.com/docs/CP/11036/PureVideo_Product_Comparison.pdf -- Torgeir Veimo torg...@pobox.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Gerald Dachs schrieb: > Quoting Pertti Kosunen : > > >> Gerald Dachs wrote: >> >>> What makes you so sure that the 8200 chipset is not supported? >>> >> It is VDPAU supported, but AFAIK can't decode VC-1. >> > > But what about this post: > http://www.phoronix.com/forums/showpost.php?p=53474&postcount=39 > He must be wrong or you. > > Does somebody know the gpu that is used by the 8200 chipset? Is it not > G98? > > Gerald > > Hi, the 8200/8300 chipsets are based on the G86, the frontend bitstream pipeline is still decoded by the CPU. The 9300/9400 chipsets should support full VC-1 hardware decode, they are based on the 98. Kind regards ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Gerald Dachs wrote: > He must be wrong or you. I could be wrong, G98 should be ok. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Quoting Pertti Kosunen : > Gerald Dachs wrote: >> What makes you so sure that the 8200 chipset is not supported? > > It is VDPAU supported, but AFAIK can't decode VC-1. But what about this post: http://www.phoronix.com/forums/showpost.php?p=53474&postcount=39 He must be wrong or you. Does somebody know the gpu that is used by the 8200 chipset? Is it not G98? Gerald This message was sent using IMP, the Internet Messaging Program. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Gerald Dachs wrote: > What makes you so sure that the 8200 chipset is not supported? It is VDPAU supported, but AFAIK can't decode VC-1. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ~/.xine/config_xineliboutput load/save and name changes
Hi, I'm using xineliboutput on 3 VDR clients, sharing the same NFS root FS. All clients are a bit different, and I solved most of the issues with a separate VDR config dir for each client, basically running "/usr/bin/vdr -c /var/lib/vdr.$(hostname) ...". The problem is that xineliboutput seems to use a single ~/.xine/config_xineliboutput config file, stored in the home directory of the vdr user, which is defined by /etc/passwd, which is the same on all clients... Is there a way to tell xineliboutput which file to use ? Like adding a command-line param "--config=~/.xine/config_xineliboutput.$(hostname)" I can also copy a template ~/.xine/config_xineliboutput.$(hostname) file to ~/.xine/config_xineliboutput before starting VDR, but this raises the question : when do xineliboutput read this file (at startup, at each config change, at channel change ?), and write to it (at config change, shutdown ?) This method worked OK for a few days, under strict manual control, but I guess one client setting will eventually get read by another one, breaking it in the process. For the record: I'd like to add the following settings on the CLE266 clients only (these add hardware deinterlacing on a progressive VGA display, which also work very cleanly on an interlaced TV output, probably because xvmc_bob_deinterlacing does exactly the opposite as the VT1622 TV encoder, ie. alternate 25Hz fields at 50Hz): 1 # Use bob as accelerated deinterlace method. 2 # bool, default: 0 3 video.device.xvmc_bob_deinterlacing:1 4 5 # Make XvMC allocate more frames for better buffering. 6 # bool, default: 0 7 video.device.xvmc_more_frames:1 TIA -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
On Sun, 14 Dec 2008 16:42:21 +0100, Udo Richter wrote > > - no channel sync > > This would make an excellent addition to streamdev. Rather a separate plugin or at most part of epgsync-Plugin. Streamdev should stick to what it was meant for: streaming. Remember 4 years ago: Remotetimers feature was part of streamdev by that time. The menu classes in VDR 1.3 started to change frequently and noone kept up with the necessary changes to streamdev. Personally I never missed a channel sync feature. The major channels rarely ever change. Futhermore streamdev and related plugins all use the channel ID, so no need to have the same channel numbers on client and server. Also channel updates and link channels work right out of the box. Cheers, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
On Sun, 14 Dec 2008 09:42:40 +0100, Clemens Kirchgatterer wrote > Seppo Ingalsuo wrote: > > > > vdr in a massive client server configuration is a giant hack with > > > many pieces each with its own little problems summing up. > > > > Not giant system, but some experiences: I have one server running > > three instances of vdr. Vdr #2 and #3 are connected by streamdev to > > vdr #1 that owns dvb hardware. Timersync plugin syncronizes timers to > > vdr #1. > > yes, intelligent timer migration between vdr instances is a not trivial > task. when a timer is to be fired, you have to ask all vdr instances > its timer list and move the timer to the most suitable instance. > taking into account recordings on the same transponder to not waste > dvb devices. the same gues for finding a free dvb device for life-view. You're no longer talking about client-server here. What you have in mind is peer-to-peer. Streamdev et al. haven't been designed for this. I never looked at videgor, but AFAIK it was a peer-to-peer aproach. Cheers, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
On Sat, 13 Dec 2008 18:52:52 +0200, Seppo Ingalsuo wrote > - The biggest annoyance: Possible to pause live TV only in vdr #1 Have you tried with the VDR patch from remotetimers-0.1.0? I never took the time to test it with timersync-plugin, but I'd be interested to see if instant recordings and pause live TV works with it, too. Cheers, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
On Sat, 13 Dec 2008 12:31:05 +0100, Udo Richter wrote > Agreed. Solutions like RemoteOSD and RemoteTiemrs are merely > workarounds. A nice solution to this integrated into VDR would > improve things a lot here. Just curious: What are you missing? > Another parameter for every timer would be a nice > solution: "Record locally" or "Record remotely" - VDR would have to > connect to a remote VDR via SVDRP to read and write these timers. Isn't that exactly what remotetimers-plugin already provides? Cheers, Frank ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Sorry for the direct mail. Quoting Chris Silva <2manybi...@gmail.com>: >> http://www.phoronix.com/scan.php?page=article&item=nvidia_8200_mobos&num=3 >> If I would need anyway a graphics card, then a big cooler would only >> block a pci-e slot. The cpu socket is more near to the back side of the >> motherboard than on many other mainboards. So I would get more space >> between the cpu cooler and the cd rom drive in my S16T case. > > But the problem remains. I need at least 3 PCI slots. So, any > suggestions on other boards with VDPAU *supported* chips? What makes you so sure that the 8200 chipset is not supported? Of course I have read this http://www.nvnews.net/vbulletin/showthread.php?t=124458, but I have found this too: http://www.phoronix.com/forums/showpost.php?p=53474&postcount=39 . On other places I could read that the only differences between 8200 and 9300 are the smaller manufacturing process, clock speed and number of shaders. Here it is even mentioned explicitly http://www.nvnews.net/vbulletin/showthread.php?p=1873716 Gerald This message was sent using IMP, the Internet Messaging Program. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
If PCI slots not enough on board, you can switch to USB DVB-S/S2 devices. For example Tevii S650 (http://www.linuxtv.org/wiki/index.php/TeVii_S650) Regards Oleg Roitburd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.2 + h264-patch + xineliboutp ut + vdr-xine +softdevice
> > That's great news! Myself and several others have been patiently > > waiting an h264 patch for vdr-1.7.1 and now 1.7.2 (for me at least, > > not sure who else has switched yet)! It will be great to finally have > > h264 support in vdr's core but until then we still need updated > > patches. > > Ok, I didn't realize that vdr 1.7.1 still needed h264 patch on top of the > Klaus S2API patch for watching S2 channels. What patch should I apply? there are dvb-s2 mpeg2 channels - for it no need any h.264 patch there are dvb-s/dvb-s2 channels which are using h.264 codec - for their you should patch the vdr with h.264 patches havw a look on VDR Extensions Patch http://www.zulu-entertainment.de/download.php Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
Udo Richter a écrit : >> * if 2 VDRs record the same program at the same time, it seems to a be a >> big problem... If using a slightly different EPG data, this result in 2 >> recordings with different times, and if using the exact same EPG, this >> result in something weird and maybe unusable (say, same station, same >> EPG, one via DVB-S, the other one via DVB-T, two different streams in >> one file...) > > This would be a lot better with a client-server timer structure. And in > the end, I'm pretty sure you don't need two VDR instances to record two > different programs into the same folder, or? ...this is a human error, but AFAIK nothing prevents it... Other point : previous emails talk about various possibilities about DVB device "location". My ideal setup would be : * all DVB devices in a single headless always-on server * all clients diskless, using an NFS share This avoids to raise problems like DVB devices spread around on clients, all with different capabilities, etc. Which could be a real nightmare WRT selecting the proper (powered on) device for recording/liveview, etc... I understand that VDR needs a plugin to solve issues like various DVB-S devices not pointed at the same satellite. Distributing this problem in a client/server setup seems arbitrarily complex to me. (I currently have DVB devices partly spread around, and I don't want VDR or any plugin to solve this issue, as I can just move hardware around) (I also think that VDR is the only STB that can record many channels regardless of the number of tuners : every other commercial STB I know of can record one channel per tuner, and does not even try to suggest that it could be possible to record a second one without a second tuner. The bar is fairly low here, and VDR works much better than normal people expect) Cheers, -- NH ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
What happens if vdr has got multiple FF-dvb-s cards in the same machine, and you want to hookup multiple monitor/tvs? Can vdr successully handle this on the same machine? Or is the only answer now to run multiple intances of vdr, one for each FF-card? If vdr can do that, then surely implementing cross network would also become easier? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
