Hi
I run
# vdr -Pxine in one console
# xine -p -s vdr in other console
I get xine osd and I found screen is displayed with following error (If I click on VDR button)
- xine engine error -
There is no input plugin available to handle
'vdr:tmp/vdr-xine/stream#demux:mpeg_pes'
Maybe MRL syntax is wrong or file/stream
Source does not exit.
I found bad frame in second console
Can u tell me pl why this error is appearing.
--Thanks and Regards
Gulab Chandra Yadava
______________________________________________________________ DISCLAIMER: This electronic message, and any attachments to this electronic message are intended for the exclusive use of the addressee(s)named herein and may contain legally privileged and confidential information. It is the property of Celstream Technologies Pvt. Ltd. If you are not the intended recipient, you are hereby strictly notified not to copy, forward, distribute or use this message or any attachments thereto. If you have received this message in error, please delete it and all copies thereof from your system and notify the sender at Celstream Technologies or administrator@celstream.com immediately _______________________________________________________________
Hi
I run
# vdr -Pxine in one console
# xine -p -s vdr in other console
use xine vdr:/tmp/vdr-xine/stream#demux:mpeg_pes
not vdr:tmp.....
Hi.
Peter Weber wrote:
I run
# vdr -Pxine in one console
# xine -p -s vdr in other console
use xine vdr:/tmp/vdr-xine/stream#demux:mpeg_pes not vdr:tmp.....
Well, I use xine -s vdr (autosearch the plugin called vdr). Just like I use -s dvd (autosearch the plugin called dvd). Then again, this is with vdr-xine downloaded when I last compiled VDR (1.3.43)... Works a treat. I do, however, have a "sleep 2" in my script after starting VDR, before starting xine; I think it was because I was seeing just that error; VDR startup takes a moment, before vdr-xine gets to create the pipes in /tmp... And if the xine-half doesn't see the stuff in /tmp, you'll probably get an error like that one... If a short gap between the two doesn't help, have a look through syslog, there might be something else up...