I don't know if anyone else still uses the xmltv2vdr.pl perl script
for piping XMLTV data into VDR's epg, but I've been keeping a version
of it updated with some additional function here:
https://github.com/oldmanuk/xmltv2vdr
These are the changes since the last version (1.0.9) was released on
the mailing list
- Add support for XMLTV episode-num. Currently gets added as EPG entry
'sub-title', if no existing subtitle has been found, in the form
sXXeXX (e.g., Bones~s01e01).
- Change …
[View More]default SVDRP port number to 6419.
- Better support for ATSC/PVRINPUT EPG sources.
- Allow multiple channels to have the same XMLTV channel id, useful for
multi input (e.g., DVB-T, DVB-S) systems where you want to feed VDR
the same info. Previously only a 1:1 mapping was permitted.
I've also received a pull request from someone who rewrote the whole
script to be a lot more readable and to use full XML parsing (rather
than just line-by-line scraping), but I still need to investigate what
the performance penalty is before accepting that in.
[View Less]
Hi,
I wrote a patch to Steve Toth hvr3000 repository, so my FlyDVB Trio can use
multiple frontend.
So I get:
/dev/dvb/adapter0/demux0
/dev/dvb/adapter0/demux1
/dev/dvb/adapter0/dvr0
/dev/dvb/adapter0/dvr1
/dev/dvb/adapter0/frontend0
/dev/dvb/adapter0/frontend1
/dev/dvb/adapter0/net0
/dev/dvb/adapter0/net1
The bus of the two frontend is shared, isn't possible to get access to both
frontend simultaneously, so I get an -EBUSY error by trying accessing
frontend1 if frontend0 is …
[View More]in use.
VDR doesn't support yet the second frontend, and it try to get exclusive
access on both frontend on start, so the second frontend is inusabile.
Vdr should probe for multiple frontend at start, and access frontend only on
channel change.
Please can someone give me an help to wrote a patch for this issue?
Best Regards,
Eddi
[View Less]
Hi all, I just set up a couple of RPI's with the configuration of a
Raspberry Pi, rpihddevice and streamdev-client.
Works great but a couple of questions.
When I'm watching TV with one of the RPI's and want to move to the other
RPI, I cannot change the channel from what the first RPI was viewing. I am
not sure how to tell streamdev to stop streaming so that I can watch TV on
the other RPI? I hope I've been clear with that - it does sound a bit
confusing. I know there is a mainmenu entry …
[View More]that says suspend server, but
it didn't seem to do anything, unless its done in the background.
In relation to this, the RPI doesn't have a power switch so shutting it
down is a pain because when you do the halt -p it doesn't actually power
off and in order to restart it you must cycle the power to the unit.
I'm interested to know what others have been able to accomplish with this
configuration to make it work better for them. I've added a number of
plugins to improve the viewing pleasure and everything has been fast and
clear.
In regards to the rpihddevice I am seeing some tearing or 'flutter' when
there is high motion with 1080 HD. Its not so bad that it isn't usable -
it most certainly works 99% of the time just fine. The one feature I miss
with the rpihddevice that softhddevice had was the automatic zoom - hoping
that gets added to the wish list at some point.
Thanks
Norm
[View Less]
Hi
> When I'm watching TV with one of the RPI's and want to move to the other
> RPI, I cannot change the channel from what the first RPI was viewing. I am
> not sure how to tell streamdev to stop streaming so that I can watch TV on
> the other RPI? I hope I've been clear with that - it does sound a bit
> confusing. I know there is a mainmenu entry that says suspend server, but
> it didn't seem to do anything, unless its done in the background.
Especially for devices like …
[View More]Raspberry Pi it would be very nice to have kind of a "standby" function in VDR, which detaches active receivers and call an appropriate function on the primary device to suspend and blank the output. Then resuming VDR would only take a fraction of a second...
> In regards to the rpihddevice I am seeing some tearing or 'flutter' when
> there is high motion with 1080 HD. Its not so bad that it isn't usable -
> it most certainly works 99% of the time just fine.
Have you set the HDMI frame rate according your video format?
> The one feature I miss
> with the rpihddevice that softhddevice had was the automatic zoom - hoping
> that gets added to the wish list at some point.
I'm afraid this might take a while, since accessing the decoded image is not that easy, however possible. But rpihddevice supports the ScaleVideo() method, so in principle it's possible to do it manually.
Regards,
Thomas
[View Less]