[vdr] Rewind and Fast Forward problems
Hi, I guess this must be an error in my setup, maybe channels.conf, or something similar, but just cannot find it.. I recently went from 1.6.0 to 1.7.12 and now 1.7.13, and all my old and new recordings alike either cannot be rewinded or fast forwarded. One way works, and another does not, one way works in some recordings and the other in the rest of them. What happens is that when you rewind (or ff), it looks good and goes backwards, but then when you go to play, it starts at the place you started the rewind. Also, while rewinding, if you have the status bar on, the time does not count at all, and the green bar only moves little if at all. Tried to search this list.. But still baffled and thankful for any help. I'm in Finland, Helsinki, Welho Cable network. Example of a channel that does not work: MTV3 D;MTV Oy:282000:C0M128:C:6900:305=2:561=fin:817:0:49:42249:2:0 My conf: http://www.iki.fi/hyvatti/dvb/vdr-17-setup.txt Regards, jaakko.hyva...@iki.fi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.13
On Wed, 3 Mar 2010, Timothy D. Lenz wrote: If it's going to be limited to 1 letter, v does seem right for video, i for iptv would be good. I think ATSC uses ether c or t. Not sure. But if I understand what is happening here, might be a good idea to go to a 2 or 3 letter ID right now so things don't have to be patched latter. IPTV will be using 'I' - at least my initial implementation does. Anyway I cannot imagine a situation that there ever will be more input plugins than there are available visible characters (26 [A-Z] + 26 [a-z] + 10 [0-9] + ...). BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rewind and Fast Forward problems
Hi, Are you using the newest firmware which can play ts for FF-card? Maybe this is your problem. BR. Halmi -- Halim Sahin E-Mail: halim.sahin (at) t-online.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rewind and Fast Forward problems
Am Donnerstag, den 04.03.2010, 11:20 +0200 schrieb Jaakko Hyvätti: Hi, I guess this must be an error in my setup, maybe channels.conf, or something similar, but just cannot find it.. I recently went from 1.6.0 to 1.7.12 and now 1.7.13, and all my old and new recordings alike either cannot be rewinded or fast forwarded. One way works, and another does not, one way works in some recordings and the other in the rest of them. What happens is that when you rewind (or ff), it looks good and goes backwards, but then when you go to play, it starts at the place you started the rewind. Also, while rewinding, if you have the status bar on, the time does not count at all, and the green bar only moves little if at all. That sounds similar to a problem that i've seen: When you play a recording for a while and then, let's say after 30 Minutes, jump forward one minute, the first jump effectively goes back a few minutes, subsequent forward jumps then really go forward. I thought this problem is related to the reelbox plugin (i am using a reel eHD), but now i think that VDR sometimes loses track about it's actual position. Tried to search this list.. But still baffled and thankful for any help. I'm in Finland, Helsinki, Welho Cable network. Example of a channel that does not work: MTV3 D;MTV Oy:282000:C0M128:C:6900:305=2:561=fin:817:0:49:42249:2:0 My conf: http://www.iki.fi/hyvatti/dvb/vdr-17-setup.txt Regards, jaakko.hyva...@iki.fi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.13
On 03/04/10 10:30, Rolf Ahrenberg wrote: On Wed, 3 Mar 2010, Timothy D. Lenz wrote: If it's going to be limited to 1 letter, v does seem right for video, i for iptv would be good. I think ATSC uses ether c or t. Not sure. But if I understand what is happening here, might be a good idea to go to a 2 or 3 letter ID right now so things don't have to be patched latter. IPTV will be using 'I' - at least my initial implementation does. Anyway I cannot imagine a situation that there ever will be more input plugins than there are available visible characters (26 [A-Z] + 26 [a-z] + 10 [0-9] + ...). There will only be 'A' to 'Z' - and I also think this should be enough ;-) Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] SVDRP Port
The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump. While this is not a major issue I'd prefer to register an official port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that. Any comments/ objections? Best regards, Christian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] SVDRP Port
On 4 March 2010 13:44, Christian Tramnitz chris@gmx.net wrote: The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump. While this is not a major issue I'd prefer to register an official port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that. Any comments/ objections? A lot of changes is required if from end user perspective. Nothing that can't be fixed in a few minutes. Would this then imply that plug-ins like streamdev (network plug-ins) should also register? Best regards, Christian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] SVDRP Port
Hi, epgsearch uses SVDRP for timer programming. Although the port can be configured in epgsearch's setup a change of the default port would probably cause some support. Plugins can not read vdr's SVDRP port til now, so it would be great to have any function for this and a change of the default would do no harm. BR, Christian Christian Tramnitz schrieb: The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump. While this is not a major issue I'd prefer to register an official port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that. Any comments/ objections? Best regards, Christian ___ 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] SVDRP Port
On 4 March 2010 22:02, Christian Wieninger cwienin...@gmx.de wrote: epgsearch uses SVDRP for timer programming. Although the port can be configured in epgsearch's setup a change of the default port would probably cause some support. Plugins can not read vdr's SVDRP port til now, so it would be great to have any function for this and a change of the default would do no harm. The client can check if svdrp is defined in /etc/services, and use the new official port from there, otherwise default to 2001. -- -Tor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] SVDRP Port
Am 04.03.2010 13:00, schrieb Theunis Potgieter: A lot of changes is required if from end user perspective. Nothing that can't be fixed in a few minutes. No change is required from end-user perspective in the end when the plugins/extensions are adapted to the new port. (In the current vdr-dev 1.7.x most plugins also have to be adopted to work with the latest version so this is not really an issue, see cChannel changes in 1.7.13). Also, for experienced users (and 1.7.x is still a dev version) changing a port number in the config (or worst case in the plugin source code) shouldn't be too complicated either. Would this then imply that plug-ins like streamdev (network plug-ins) should also register? streamdev, live and vdradmin are not using its own protocol but http (on a non-standard port). The reason for not using a standard port is that port 80 will be already in use, so using a non-standard port is feasible. Best regards, Christian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rewind and Fast Forward problems
On 04/03/10 04:25, Falk Spitzberg wrote: Am Donnerstag, den 04.03.2010, 11:20 +0200 schrieb Jaakko Hyvätti: Hi, I guess this must be an error in my setup, maybe channels.conf, or something similar, but just cannot find it.. I recently went from 1.6.0 to 1.7.12 and now 1.7.13, and all my old and new recordings alike either cannot be rewinded or fast forwarded. One way works, and another does not, one way works in some recordings and the other in the rest of them. What happens is that when you rewind (or ff), it looks good and goes backwards, but then when you go to play, it starts at the place you started the rewind. Also, while rewinding, if you have the status bar on, the time does not count at all, and the green bar only moves little if at all. That sounds similar to a problem that i've seen: When you play a recording for a while and then, let's say after 30 Minutes, jump forward one minute, the first jump effectively goes back a few minutes, subsequent forward jumps then really go forward. I thought this problem is related to the reelbox plugin (i am using a reel eHD), but now i think that VDR sometimes loses track about it's actual position. Tried to search this list.. But still baffled and thankful for any help. I'm in Finland, Helsinki, Welho Cable network. Example of a channel that does not work: MTV3 D;MTV Oy:282000:C0M128:C:6900:305=2:561=fin:817:0:49:42249:2:0 My conf: http://www.iki.fi/hyvatti/dvb/vdr-17-setup.txt Regards, jaakko.hyva...@iki.fi I have something similar using 1.7.12 and ATSC, was working under 1.6.0 fine... I can fastwind and rewind, even go from fastwind to rewind, but if I play at the end of the fastwind then the picture remains paused. I can go from the pause to rewind or fastwind, but not play. I have to exit the recording, and then go back in, when VDR will start from where it left off. This is quite frustrating, as we routinely record things to wind through the commercials. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rewind and Fast Forward problems
Hi, Thank you for your help Halim, this firmware solved the problem: http://www.escape-edv.de/endriss/firmware Thanks for the link, it was mentioned in vdr 1.7.8 announcement, but was too hard for me to spot. Maybe that should be mentioned in INSTALL or MANUAL in the sources. Or in PLUGINS/src/dvbsddevice/README like this: --- old/vdr-1.7.13/PLUGINS/src/dvbsddevice/README 2009-12-29 14:00:29.0 +0200 +++ vdr-1.7.13/PLUGINS/src/dvbsddevice/README 2010-03-04 19:05:33.913710408 +0200 @@ -18,3 +18,10 @@ Full Featured DVB cards based on the TechnoTrend/Fujitsu-Siemens design. This code was originally part of the core VDR source, and was moved into this plugin in VDR version 1.7.11. + +Requirements: + +For your Full Featured card to play correctly the current TS +recordings, please install the latest firmware to /lib/firmware/: + +http://www.escape-edv.de/endriss/firmware Regards, Jaakko On Thu, 4 Mar 2010, Halim Sahin wrote: Hi, Are you using the newest firmware which can play ts for FF-card? Maybe this is your problem. BR. Halmi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.13
Someone once said they didn't see a need for more then 640k of ram too :) May not need 30+ symbols, but to keep to symbols that somewhat match what they are for would call for reuse of some letters. On 3/4/2010 2:30 AM, Rolf Ahrenberg wrote: On Wed, 3 Mar 2010, Timothy D. Lenz wrote: If it's going to be limited to 1 letter, v does seem right for video, i for iptv would be good. I think ATSC uses ether c or t. Not sure. But if I understand what is happening here, might be a good idea to go to a 2 or 3 letter ID right now so things don't have to be patched latter. IPTV will be using 'I' - at least my initial implementation does. Anyway I cannot imagine a situation that there ever will be more input plugins than there are available visible characters (26 [A-Z] + 26 [a-z] + 10 [0-9] + ...). BR, -- rofa ___ 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] [ANNOUNCE] VDR developer version 1.7.13
On Thu, 4 Mar 2010, Timothy D. Lenz wrote: May not need 30+ symbols, but to keep to symbols that somewhat match what they are for would call for reuse of some letters. Well, even I do prefer I - IPTV, but I don't see no problems using X - IPTV. The description of source params explains perfectly the source in both cases - no matter what the type character is. BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LCD with vdr-1.7.x ?
On 27/12/09 05:32, Gregoire Favre wrote: On Mon, Dec 07, 2009 at 07:02:19PM +0200, Mika Laitio wrote: I have used lcdproc-plugin to get information from displayed channel, played mp3, etc. to lcd in antec fusion v2 silver. Newest version seems to be maintained at http://projects.vdr-developer.org/projects Great, seems to work just fine :-) Thank you very much, Am trying to get this working having just got an LCD display. I have it working with XBMC and the lcdproc program which comes with Gentoo. However, with VDR, when running with the plugin, VDR ignores all user input (keyboard and remote) and then gets killed by the watchdog. Not sure anything is coming on the LCD either. Is there something I should know? This is lcdproc-0-0-10-jw6 Will try 7.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] SVDRP Port
On 04.03.2010 12:44, Christian Tramnitz wrote: The current SVDRP Port 2001 is being used for several years now, but unfortunately it has never been registered with IANA. As such it does not show up in /etc/services and there is no name resolution for it, i.e. when starting a tcpdump. While this is not a major issue I'd prefer to register an official port with IANA to avoid port conflicts in the future. I already checked with them, but port 2001 is already registered to another service, so doing this we would get a new port number. Since this is freely configurable in vdr (and most plugins/extensions that rely on it) I do not see an issue with that. Any comments/ objections? I like port 2001 - why stir this up and cause turmoil amoung all those who have been using the default port for so long? What are services dc and wizard, anyway? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
