[vdr] [announce]: pvr350-1.7.5
There maybe a handful people still using the Hauppauge PVR350 card as output device. Although I have stopped active development, I will adapt the plugin as long as possible for newer vdr versions. I believe that the PVR350 is still a good choice in case you have a SD Tube TV and don't need digital audio output. Version 1.7.5 is online: http://projects.vdr-developer.org/attachments/download/1657/vdr-pvr350-1.7.5.tgz - remove support for vdr < version 2.0 - adapt to changes in vdr-2.1.3 - remove support for ancient ivtv driver versions - adapt Makefile to vdr's new Makefile system - fix segfaults on exit when framebuffer device is missing The plugin is still only for PAL ouput. If there are any users who want to use it for NTSC output, I may consider adding it. Please send me a mail. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
> > streamdev doesn't query for a new device if the current and the next > > channel has the same transponder. This is checked via the following > > define: > > > > channels.h:#define ISTRANSPONDER(f1, f2) (abs((f1) - (f2))< 4) //XXX > > > > All the channels in channel.conf have the same frequency, so streamdev > > only changes the receivers but doesn't query for a device. > > I havent understand exactly what you are doing. Do you use an analogue > > input (like scart) of the pvr500 card and the channel switch script > > changes the channel of another device ? If so, i could imagine the > > frequency in channels.conf doesn't matter and you could simply modify > > the frequencies. > > The frequency matters since he is using the tuner input. > > Lars. I think Rob's version of pvrinput has already the code for calling the externchannelswitch-script in "case eTelevision" and not only in "case eExternalInput". (Otherwise it wouldn't work at startup). The code in ProvidesChannel() and SetChannelDevice checks not only for the same frequency, but also for the channel number: if ((Channel->Number() == CurrentChannel.Number()) && (CurrentFrequency == Channel->Frequency()) && (CurrentInput == input) && (CurrentNorm == norm)) When Rob switches to another channel number, pvrinput should return needsDetachReceivers = true in ProvidesChannel(). It should also get a call for SetChannelDevice(). The problem is that both functions are never called - but obviously only in combination with running streamdev. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
> I have a PVR500 with the PVRInput plugin running on my Backend. > > I am using an old Hauppauge FF DVB-s card just as a frontend on another > low powered system in order to throw the PVRInput channels to the > kitchen. On the backend it's all working, however, switching between > channels doesn't quite work, as the streamdev server will give the > client the same channel over and over again regardless of what it > requested, unless the device changes (ie, if I go from /dev/video1 to > /dev/video2 it'll change channel). how do you force switching the video device? > > An example of the channel list is: > > > 2-WTTW PBS_Affiliate > ntsc;WTTW:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30020:32:32:0 > 3-WREX NBC_Affiliate > ntsc;WREX:67250:TV|NTSC:V:0:301+101=2:300=@4:305:0:30030:48:48:0 > 4-WTVO ABC_Affiliate > ntsc;WTVO:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30040:64:64:0 > 5-WIFR CBS_Affiliate > ntsc;WIFR:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30050:80:80:0 > 6-WQRF Fox_Affiliate > ntsc;WQRF:67250:TV|NTSC:V:0:301+101=2:300=@4:0:0:30060:96:96:0 > > > > But, obviously all on the same line. I think this is probably an issue > with streamdev rather than pvrinput as it works with Vomp happily. > > I need it to detach and change channel in order to trigger the external > channel changer script. pvrinput does its channel settings (this includes executing the externchannelswitch-script) inside its function OpenDvr() while the encoder is still stopped. The settings will only be done if the bool ChannelSettingsDone is false. This bool is always false at first plugin start. I guess this is the reason why your channel settings were done once: > Jun 7 19:13:24 oac vdr: [8795] entering cPvrDevice::OpenDvr: Dvr of > /dev/video1 (PVR500#1) is closed > Jun 7 19:13:24 oac vdr: [8795] entering cPvrDevice::CloseDvr: Dvr of > /dev/video1 (PVR500#1) is closed > Jun 7 19:13:24 oac vdr: [8795] cPvrDevice::ResetBuffering(): tsBuffer > prefill = 314524 for /dev/video1 (PVR500#1) > Jun 7 19:13:24 oac vdr: [8795] channel is television. > Jun 7 19:13:24 oac vdr: [8795] OpenDvr: calling > /etc/vdr/plugins/pvrinput/externchannelswitch.sh 30040 4 1 67250 > Jun 7 19:13:25 oac vdr: [8795] OpenDvr: returned from > /etc/vdr/plugins/pvrinput/externchannelswitch.sh 30040 4 1 67250 > Jun 7 19:13:25 oac vdr: [8795] OpenDvr: sleeping for 3 seconds... > Jun 7 19:13:28 oac vdr: [8795] OpenDvr: waking up > Jun 7 19:13:28 oac vdr: [8795] SetVBImode(525, 0) on /dev/video1 When leaving OpenDvr, the bool is set to true. It will only become false again during runtime, if vdr calls the pvrinput- function SetChannelDevice() and determines the needed settings. And this is your problem. There are no debug messages from pvrinput's SetChannelDevice() or ProvidesChannel(), so vdr never calls these pvrinput functions - although a channel switch for a pvrinput device is requested. But why? I have no idea. It works for you with vomp. It worked for me with streamdev when I tested this last year. But I had only streamdev-server running and used vlc to switch channels. Maybe a streamdev developer reads this and has an idea or can explain possible interactions between streamdev-client, vdr and a receiving device. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] AvetTV a761
> From: ? ?? (Pridvorov Andrey) > It crash also: > > root@ua0lnjvdr:/var/log# v4l2-ctl -D -d /dev/video0 then it is for sure a serious driver bug. You should report this to linux-me...@vger.kernel.org ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] AvetTV a761
> > And yet. If I try use Avertv a761 and PRV 150 with pvrinput plugin, I have vdr crash: > It seems that the driver for your a761 registers also an analog video > device. pvrinput tries to open it and sends a VIDIOC_QUERYCAP to determine > if it's a device it can handle. But the driver don't like it... > > A dirty workaround would be to add the option "video_nr" and "vbi_nr" to > your bttv-module (look at "modinfo bttv") and set the number to something > greater than 16. pvrinput will only test the first 8 video-nodes (see > global.h in its source if it's modified). > > The right way is to look into the driver and test it if it crashes when > you send the ioctl mentioned above. To the original poster: I guess ? ?? is not your real name. It would be nice if you would use at least a nickname. Try "v4l2-ctl -D -d /dev/video0" while vdr is not running. Does this work or does it crash also? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr Digest, Vol 63, Issue 32
> Date: Tue, 27 Apr 2010 07:03:50 +1200 > From: "Simon Baxter" > Subject: Re: [vdr] PVRINPUT plugin and "black/cinema bars" > > Found the original hack (attached). It will take time to have a look at your code. Just to let you know: The current pvrinput source allows to execute a script on every channel change. Have a look at "externchannelswitch" in http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/README We won't support the usage of lirc transmitters directly in the plugin, but you could do it with an own binary. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PVRINPUT plugin and "black/cinema bars"
> From: VDR User > 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 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PVRINPUT plugin and "black/cinema bars"
> From: "Simon Baxter" > 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 > > 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Timer macros vs. filename in "Edit timers"
> I can give you a setup option that switches between the old and the > new version - if it really turns out to be necessary. Anything else > would probably quickly become "rocket science" ,-) > > Klaus As already mentioned by Udo, the current behaviour often generates useless names when using search timers for series. It may be a problem of bad epg data, but the quality of the epg data is as it is. I never had any problems before with displaying the recording name. But now I have wrong names for nearly every timer. My vote is to fully revert the change or make it selectable with a setup option. Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR crashes while recording a high bandwith channel
Several users have reported in the vdrportal forum that the bandwidth problem on FF cards became worse when switching from vdr 1.6 to 1.7 Even installing an additional budget card will not help, because since 1.6 vdr does not always prefer the budget card for recordings. A simple solution could be to install a DVB-T device and configure vdr to always start on a DVB-T channel. But the suspendoutput plugin should do the same trick. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hauppauge PVR HD
> Date: Tue, 12 Jan 2010 11:00:49 -0600 > From: Rob Davis > Subject: [vdr] Hauppauge PVR HD > > Does anyone have any experience with this? Does it work with the > pvr-input plugin? there is a linux driver and support for mythtv. But pvrinput does not support it, as it is currently a "cx2341x"-plugin (mpeg2-hardware encoder chips cx23415/cx23416/cx23418). There is also a big difference: The HD PVR delivers not mpeg2 but a h264/mpg4 stream. I don't know if this stream is compliant to DVB-S2. One would need such a box for testing to see if it is possible to implement support in pvrinput or if it is easier to write a new plugin. Greets, Martin PS: Did you read my answer to your last question about pvrinput? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.11
> Date: Mon, 11 Jan 2010 12:51:19 +0200 > From: Theunis Potgieter > Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.11 > > Hi Klaus, any plans on including vdr-1.7.9-pluginparam.patch for > pvrinput plugin? http://drseltsam.device.name/vdr/pvr/src/pvrinput > > This seems to create an input device of Plugin Type. I guess the > vdr-iptv plugin also creates something similar. pvrinput uses exactly the same pluginparam.patch. (It is taken from the iptv- plugin.) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PVRinput Ideas..
Am Donnerstag, 7. Januar 2010 04:10:21 schrieb Rob Davis: > Would it be possible to get the pvrinput plugin to be able to create > different channels line which all call the same s-video channel this works: Test1:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9012:0:0:0 Test2:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9013:0:0:0 Test3:1:PVRINPUT|SVIDEO1:P:0:301=2:300:305:0:9014:0:0:0 > but also > call the channel change script? I will think about a possibility to call an external script (e.g. /usr/local/bin/extern_channelswitch.sh) in SetChannelDevice() with two parameters: card-number (e.g. 1 if the available pvrinput device that will be used is /dev/video1) and the SID (Service-Id, e.g. 9012 for channel 12 in your receiver) > All it would need to do would be execute the program dct6200 (which > could be in the /etc/vdr/plugins/pvrinput directory) with the argument > of 41 or 08 and the cable box would change. This would also work for > someone using an irblaster with a SkyBox and a PVR card. you would need to write a bash-Script (extern_channelswitch.sh) that executes your dct6200 binary with the needed commands. Should be simple. Please contact me privately with an example how your dct6200 binary has to be called. Is "dct6200 12" sufficient to switch to channel 12? This solution could indeed be useful for other users, as it is not limited to your box. The script could execute lirc irsend or whatever. I can't promise too much but I have an idea and will see if I get it working. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon plugin doesn't work "ERROR (femonosd.c, 504): Function not implemented"
> > Sep 15 08:37:36 video vdr: [17541] ERROR: cOsd::SetAreas returned 6 > > Your OSD is running out of memory. The only cure is to shrink your > current OSD size. Rolf, you know that this happens with the vdr default OSD size? With my FF DVB-C (2 MB) and vdr 1.7.9 I have the following default values after deleting the setup.conf: Left and Right 8% Width 87% Height 84% To avoid the above mentioned error I reduced width and height to 82%. Then I got the femon OSD display, but with an other error: Sep 8 20:26:27 ubuntuvdr vdr: [3668] ERROR: cFemonOsd::cFemonOsd() OSD height (461) smaller than required (480). I increased the height to 84% and the error message disappeared. But now I got no display of the transponder and stream information - only the title. After setting width to 81% and height to 87% everything worked. Why is it not possible to show all femon OSD content with the vdr default OSD size? I don't remember that I had to change the OSD size with earlier vdr/plugin versions. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7.8 shows wrong recording length
I have a TS recording of more than two hours which seems to have no errors (Project X demux log looks fine). When I start playing it with vdr, the replay osd shows a recording lenghth of only 9 minutes. The same values is displayed in the recording menu (yes I know, this is not a vdr feature but comes from a patch) Is it worth to investigate it? I still have this recording on my disc. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PVRInput and Streamdev
There is a bug in pvrinput which may also effect streamdev. (I know for sure that the bug leads to no picture with vdr 1.7.8) Have a look in reader.c There is at four places a wrong assignment. Instead of ts_buffer[1] = (first ? 0x40 : 0x00) || (kVideoPid >> 8); it has to be bitwise: ts_buffer[1] = (first ? 0x40 : 0x00) | (kVideoPid >> 8); @ rob: You are using the PVR500 with NTSC? Did you need to patch pvrinput? As long as the tuner does not support PAL, it should simply return an error and work with the default driver setting (NTSC). I am working on a new pvrinput release and am looking for a NTSC beta tester. If you are interested, contact me privately. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Analog TV plugin
> Date: Wed, 08 Jul 2009 14:14:08 +0200 > From: Thomas Netousek > Subject: Re: [vdr] Analog TV plugin > Hi Martin, > > first of all thanks for your work ! > I am using the HVR1900 which has a DVB-T and an analog part purely for > the capturing from analog. > I am using the pvrusb2 driver from kernel 2.6.29. > This version has two configuration options: > - pvrusb2 sysfs support (EXPERIMENTAL) > - pvrusb2 ATSC/DVB support (EXPERIMENTAL) > > I am disabling the ATSC/DVB support and I get a /dev/video[0,1,2] > instead of /dev/dvb/adapter[0,1,2] I discussed this issue in the pvrusb2 ML: http://www.isely.net/pipermail/pvrusb2/2009-July/002493.html and suggested a possible solution: http://www.isely.net/pipermail/pvrusb2/2009-July/002495.html Would be fine if you could try if this works when "pvrusb2 ATSC/DVB support" is enabled. If you have no other DVB device than the pvrusb2, than I wonder if VDR would accept a not existing - D option. Example: modprobe pbrusb2 adapter_nr=9 vdr -D 0 -Ppvrinput Will vdr fail to start, because the selected dvb adapter is not found? Or will vdr start like there is no DVB device? Note: Maybe you need the dummydevice plugin to get vdr started without any DVB devices. > You are right that I cannot switch easily between DVB-T and analog, but > I do not have that requirement. It should be possible to start a small script via commands.conf, which stops vdr, unloads pvrusb2, reloads it with a different adapter_nr, and restarts vdr with a -D option which allows the usage of the pvrusb2 DVB-T part. This way one could switch between analogue and DVB usage by restarting vdr via OSD. > > So actually I can confirm that pvrinput and pvrusb2 not only work with > one adapter, but with three - and there seems to be no > limit. Do you have three pvrusb2 devices? wow. pvrinput supports a maximum of 8 devices Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Analog TV plugin
> Date: Wed, 08 Jul 2009 07:45:05 +0200 > From: Thomas Netousek > Subject: Re: [vdr] Analog TV plugin > To: VDR Mailing List > Message-ID: <4a543261.5070...@netousek.com> > Content-Type: text/plain; charset=ISO-8859-1 > > I suggest you use a card with hardware MPEG encoder and the pvrinput plugin. > This works perfectly with a Happauge HVR1900 USB card. > > Thomas Hi Thomas, I am one of the developers of the pvrinput plugin and made the changes to support the PVRUSB2. This is the first time somebody confirmed that it also works with their successor. As far as I know you cannot use DVB-T and analogue both at the same time (shared hybrid device). I think vdr will always open the DVB device, so the analogue part would be not accessable. How did you solve it? Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Pvrinput and HVR1300
> > In Germany the PVR150 ist still available in serveral web shops, while the PVR > > 250 seems to be out of stock everywhere. > > > Are any of them delivering to other European countries? Or if youo could > tell me which sells it I can find out my self. try www.amazon.de They sell PVR 150 for 77,98 Euro It seems they deliver to every european country. http://www.amazon.de/gp/help/customer/display.html?nodeId=504950#ausland ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Pvrinput and HVR1300
> > My advise: Sell your HVR 1300 to a Windows user and buy a PVR150 + a > > Linux-supported DVB-T USB-stick. > > > I have actually been thinking of that possibility also. The problem is > there are no PVR150 available. At least I have not seen those for a > while. Would PVR250 be as good/easy to install? I believe I could find > one of those. In Germany the PVR150 ist still available in serveral web shops, while the PVR 250 seems to be out of stock everywhere. Both cards work fine. Some revisions of the PVR 150 have also a radio tuner. You could also use a PVRUSB2. The successor is the WinTV HVR-1950, which analogue part operates exactly as the predecessor PVRUSB2. It is tested with pvrinput yet, but I am pretty sure that I could do necessary changes easily. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Pvrinput and HVR1300
> So does anyone know if the same applies for analogtv plugin also? > > \\Kartsa > Forget the analogtv-plugin. Development stopped years ago. It does not support the current v4l2 mpeg API, so even a PVR150/250/350 would not work. My advise: Sell your HVR 1300 to a Windows user and buy a PVR150 + a Linux-supported DVB-T USB-stick. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Pvrinput and HVR1300
There is basic preparation for a future support in the pvrinput plugin, but it can't work for now. I know that for sure because I am one of the pvrinput developers. The other developer who worked with the HVR1300 wrote a status report in the german vdrportal recently: http://www.vdr-portal.de/board/thread.php?postid=789844#post789844 There are still problems with the driver (freezes), and (as far as I remember) the current release version of pvrinput would need additional hacks and patches. Have a look in the FAQ from the plugin sources: Q: What about the HVR 1300? A: support is not finished yet. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Pvrinput and HVR1300
The HVR 1300 is not supported by the pvrinput plugin. Card/driver work in a very different way from ivtv-supported cards, using a second device for the mpeg encoder. It is not sure if pvrinput will ever support this card. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Which extension for TS files?
> From: Klaus Schmidinger > Up to now VDR has used names like 001.vdr for its recording files. > While moving to Transport Stream as the recording format, I need to > use a different file name extension, and so was wondering which one > to use. My first idea was *.ts, for "Transport Stream", but when I > point, for instance, Konqueror to such a file, it thinks it is a > "Qt Translation Source". So I was wondering if I should use *.mpg > instead. This one is identified by Konqueror as an MPEG file and > will make it launch a proper player. > > What do you think about this? I am strongly against this. *.ts may conflict with KDE, but it is a usual ending for transport stream. Several mpeg-tools can handle this. I think the dreambox is also using *.ts for its recordings. *.mpg would give much more problems with applications. A TS is not an mpeg-file. Applications which can play mpg but not TS may even crash. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] pvrinput-2008-10-04
The pvrinput plugin uses a Hauppauge PVR card as an input device. All cards supported by the ivtv or pvrusb2 driver should work. (Tested with PVR150, PVR250, PVR350, PVR500, PVRUSB2). Winfried Koehler and I work on this plugin since the original maintainer stopped development in 2006. As far as I remember, our new versions were always only announced in the german vdrportal forum. So we think it is time to keep the non-german-speaking vdr users informed. Look into the HISTORY for changes and into the README for further details. http://drseltsam.device.name/vdr/pvr/src/pvrinput/vdr-pvrinput-2008-10-04.tgz mirror: http://wirbel.htpc-forum.de/unofficial_stuff/vdr-pvrinput-2008-10-04.tgz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] pvr350-2008-09-07
Today I announced this version in the german vdrportal forum. The last time I announced a new pvr350 plugin-version here in the ML was June 2007. So it is time to write here again to keep the non-german-speaking users informed. The pvr350-plugin implements an output device for the PVR350 TV out, using the hardware mpeg2 decoder. http://drseltsam.device.name/vdr/pvr/src/pvr350/vdr-pvr350-2008-09-07.tgz Look into the HISTORY for the many changes since June 2007. Attention: The plugin does not work properly with vdr 1.7.1: vdr now simply strips the TS headers and sends the payload to the usual PlayVideo() and PlayAudio() functions. The PES packets have no longer a size of 2kB, and the PES audio ID is always 0. The pvr350 hardware decoder and/or the ivtv driver cannot handle this. We would need a lot of additional code - time will see ... Note: For watching analogue TV from the tuner of the PVR350 you need a second plugin as input device. This is pvrinput, and as there is also a new version, I will announce it in a separate mail. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with v1.6.0 and two DBS-S cards
> From: "Stefan-W. Hahn" <[EMAIL PROTECTED]> > I'm running two DVB-S cards (Nexus FF and Nova). The update was > without any problem. > When recording on one program I can view at the same time just the > channels of the same bouquet but no other ones (two cards!!). But > recording simultaniously on two different bouquets works. > > With v1.4.1 there was no problem in recording one channel and > switching to all other channels. > > I didn't find any hint on the mailinglist or vdr-portal about this > problem. Is there any other having the same problem? > > Are there any hints how to solve this problem? Did you also update the driver/kernel? Is it a Nova SE with s5h1420 Frontend? check with dmesg if both cards are initialized There is a bug in the driver which was fixed a few days ago (still not in the man v4l-dvb hg): http://linuxtv.org/hg/~pb/v4l-dvb/rev/cd7eae82baf9 http://linuxtv.org/hg/~pb/v4l-dvb/rev/84530ecadf89 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Transfer-Mode without remux
Hi Klaus, sending TS payload data directly to the device shouldn`t become a generally method. Please be aware that there are other output devices which can`t handle TS data. For example, the decoder of the PVR350 needs a multiplexed Audio/Video PES. Greets, Martin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How To use DeviceStillPicture ?
I have seen that plugins use this in a different way. For example in this order: DevicePlay DeviceStillPicture DeviceFreeze So the next action to display a new Stillimage would start with DevicePlay Others call neither Freeze nor Play. The dvd-Plugin calls DeviceClear and DevicePlay before DeviceStillPicture. I remember that Klaus once stated that DeviceStillPicture could be seen as a trickmode, so that always a Play has to follow to resume from trickmode. But is it necessary to Freeze the Stillpicture before? And I wonder: How should a device plugin handle the StillPicture function? Is it necessary that StillPicture also calls a Clear() to clear the internal decoder buffers? It looks like that vdr is not doing this in dvbdevice.c, although I am not sure if the av7110 ioctl VIDEO_STILLPICTURE does internally clear the buffers. I noticed problems when both plugins (that one that uses DeviceStillPicture and the device plugin) do a Clear() at the same time. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] pvr350-Plugin -new development snapshot
I just announced it in the vdrportal forum, but it may also be interesting for non-german speaking vdr users. The pvr350-plugin implements an output device for the PVR350 TV out, using the hardware mpeg2 decoder. It was originally written by Dominic Morris, but he stopped development. Based on the last version 0.0.5 from December 2005 (which was only sent to a few people), I adapted the plugin during the last 18 months to ivtv changes. Although I have only very limited knowledge about C++, I also managed to improve some things. Andreas Schäfers helped me a lot; he introduced even ac3-to-mp2 conversion which is important if you use the dvd-plugin. Look into the README for requirements and further details. http://drseltsam.device.name/vdr/pvr/src/pvr350/ There is still much work to do - feel free to contribute patches! For watching analogue TV from the tuner of the PVR350 you need a second plugin as input device. Because the analogtv-plugin is out of date, I highly recommend the latest unofficial pvrinput. Have a look at http://drseltsam.device.name/vdr/pvr/src/pvrinput/vdr-pvrinput-1.0.0_20070523.tgz or http://free.pages.at/wirbel4vdr/unofficial_stuff/vdr-pvrinput-1.0.0_20070523.tgz and look into the README. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] need help with TrickSpeed Code
The pvr350-Plugin uses the following code:
void cPvr350Device::TrickSpeed(int Speed)
{
printf("Set speed %d\n",Speed);
m_RingBuffer->Clear();
SetPlayMode(m_PlayMode);
}
With this code it makes no matter if the vdr-setup is set to Multispeed mode or
not -it always provides one (pretty fast) speed in fast Forward mode. As no
ivtv ioctl is used, I suppose the speed is done by vdr itself and not using the
ivtv driver.
I "borrowed" some code and changed it to this:
void cPvr350Device::TrickSpeed(int Speed)
{
printf("Set speed %d\n",Speed);
struct ivtv_speed speed;
int ret;
m_RingBuffer->Clear();
memset(&speed, 0, sizeof(speed));
speed.fr_mask = 2;
switch (Speed) {
case 1 : speed.scale = 0; break;
case 3 : speed.scale = 30 / (24 / 3); break;
case 6 : speed.scale = 30 / (24 / 6); break;
}
if ( (ret = ioctl(fd_out,IVTV_IOC_S_SPEED, &speed)) < 0 ) {
printf("speed %d\n",ret);
SetPlayMode(m_PlayMode);
}
}
The first press of the left button during playback results in the same speed as
with the old code. But if I increase the speed and then return to a lower
speed, it work as expected. So I have three different speeds, but the initial
speed seems to be always the highest speed.
Could somebody help me? Maybe it is even possible to get three speeds without
using the ivtv ioctls?
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] RE: FF card substitute - Budget and PVR 350?
> Date: Fri, 20 Oct 2006 15:14:57 +1300 > From: Richard Scobie <[EMAIL PROTECTED]> > Subject: [vdr] FF card substitute - Budget and PVR 350? > I note that Hauppauge no longer list the Nexus DVB-S FF card and was > wondering if anyone has succeeded in using the PVR 350, which has a > hardware MPEG2 decoder and OSD, in conjuction with a budget DVB-S card. > > What I am looking for is the full functionality of VDR, for display on a > television set via the video output on the PVR 350 - no VGA card outputs. > > If this is not yet possible, which pieces of the puzzle are still missing? > > Regards, > > Richard You can use the pvr350-plugin. It uses the hardware mpeg2 decoder on the PVR350 (ivtv driver). The plugin is out of development, but I managed to do some changes to get it work with new ivtv drivers. I also found a way to improve the channel switching duration from 4-5 sec to 2-3 seconds. Have a look at http://www.vdr-portal.de/board/thread.php?threadid=55637 I use it in combination with a DVB-T card and think it works better than a dxr3. Unfortunately, the DVD-plugin does not work. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Re: VDR prefers my CI DVB device for recordings and blocks it unnecessarily
Klaus Schmidinger wrote:> @Martin: any news
on this? With recent drivers and firmware it should be> possible to
record and watch even the high-bandwidth channels like ZDF> on a FF
card.
The problem appeared with "Tagesschau" on ARD. Not
every recording on ARD or ZDF has buffer problems, but when it is live and maybe
even 16:9, it is very likely that it happens. And there is no chance to do an
additional recording on the same transponder without problems.
I always use very recent drivers from hg,
never older than 3 weeks. I even patched it
with the performance + refactoring patches
http://www.vdr-portal.de/board/thread.php?threadid=51207
from Oliver ("UFO") which seems to make it a little
bit better.
>The driver I'm using is the Mercurial
version 2006-02-05 (well, actually>that's not _that_ recent, anyway) and
the firmware version F12623 as>of 2006-07-22. The size of my firmware
file is 240044, and the md5sum>is 099329687c91131e616b4dcd8a118a25. My
CPU is an AMD K6/II 450.
F12623 ? where do you get it from? has it ever been
released officially? I remember that Werner mentioned F12623 in vdrportal in
June, but the last version which was posted there is F22623 from
May
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Re: VDR prefers my CI DVB device for recordings and blocks it unnecessarily
I upgraded to 1.4.1-4, which seems to include the patch from Anssi (http://linuxtv.org/pipermail/vdr/2006-August/010360.html ) I am not happy with this patch: My machine has a FF-card and Budget-Card+CAM. There was no timer for any encrypted channel programmed. All active timers were set for ARD. I had absolutely no plans to watch Premiere, I was not even at home :-) But all recordings were done with the FF card. vdr started with the ARD channel, and the well known performance problem of FF cards resulted in bad recordings (buffer usage ... /clearing). You see, I want the the opposite than the original poster asked for. For me it is more important to get good recordings than to be able to switch to an encrypted channel why recording another one. So I want vdr to always use the Budget card for recordings.Can this be done in any way without patching vdr? Is there any solution I don`t see? (Of course I don´t want to hardcode every channel in channels.conf to the Budget card. I still want to be able to make two FTA-recordings on different frequencies.) I think the best solution would be to make this configurable in DVB settings or in timer menu so that the user can select the DVB card he wants to use for the recording. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
