[vdr] Crystal Palace channels.conf file
Slightly off topic, am about 6000 miles away, but can someone post an updated Crystal Palace dvb-t/freeview channels.conf file. My slingbox is acting up and, coming from a VDR background, I want to see what the channels.conf is to work out why. (If you're slingbox interested, the BBC Mux is missing half its channels while the slingbox is set to UK, if I set it to Italy, I get all the muxes/channels but no channel order). I will probably use the channels.conf file to work out what the channel mapping is and leave it on. The long term plan is to use vdr-iptv and a script to feed slingbox input into my VDR on this side of the atlantic, just waiting for the slingbox code in xbmc to turn into a standalone program.) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FreeviewHD success with Nanostick 290e
Hi Chris (and list) I've just been doing a bit more testing with my recently acquired Nanostick 290e... I added a fake channel with the frequency 61800 MHz (my HD mux), QAM256, and everything else set to auto or random values. I then switched to it. vdr then picked up BBC HD, ITV1 HD, Channel4 HD, and BBC One HD. Hmmm, interesting, Qam256 is used in the US for Unencrypted cable. Does anyone know if a ClearQam US tuner would work with VDR if you pointed it at a Freeview UK HD Mux? Will have to bring one when I next visit my sister in London. However, if it did, the plethora of cheap ClearQam tuners would help get VDR users HD Freeview.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDHomerun and streamdev
On Tue, 02 Aug 2011 21:38:11 -0500, Rob Davis wrote On 27/07/11 20:37, Kirk Bromfield wrote: I had the same problem until I downgraded to streamdev 0.5.0 and hdhomerun_atsc_firmware_20100828.bin. I am not sure both of these changes are necessary as I changed both at the same time. :( Emerged vdr-streamdev instead of git and it's working now, thanks.. Could you provide a diff between these two versions? I'd like to find out why (current?) git isn't working for hdhomerun. Spoke too soon, It works as long as the channel is streaming/being viewed somewhere else. If, however, the channel is not showing, then streamdev sends the channel before it's tuned, which causes ffmpeg to throw an error as it thinks it's supposed to send an ac-3 track with 0 channels instead of 5.1 or 2.0. Is there a way to set a delay between tuning and sending the ts stream? (Will have a look for a diff tonight).. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDHomerun and streamdev
On Wed, 3 Aug 2011 10:09:12 -0500, Rob Davis wrote Spoke too soon, It works as long as the channel is streaming/being viewed somewhere else. If, however, the channel is not showing, then streamdev sends the channel before it's tuned, which causes ffmpeg to throw an error as it thinks it's supposed to send an ac-3 track with 0 channels instead of 5.1 or 2.0. Is there a way to set a delay between tuning and sending the ts stream? What do you mean with streamdev sends the channel before it is tuned? As you mentioned ffmpeg, I assume you are refering to HTTP streaming here. For HTTP, streamdev first tunes the device, then it adds receivers for the channel's PIDs, sends the HTTP headers and finally starts to forward the data it receives from the device. So unless hdhomerun tunes the channel in the background, it should be tuned when streamdev starts to reply. Regards, Frank What I noticed is that if the frontend is displaying the channel, or the windows vompserver is streaming it, when I call up the channel on my non ac/3 complient vomp box via streamdev and iptv, (which works with my internal atsc cards), the ffmpeg diagnostics report that I have no audio in my audio stream. It see's it as ac/3 but gives it 0 channels, then fails to convert (I had it converting to mp2 and throwing the result back into the iptv plugin, so the remote frontend can play it. When I get home I can show the ffmpeg diagnostic output with a pci card or the hdhomerun if it'll help.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDHomerun and streamdev
On 27/07/11 20:37, Kirk Bromfield wrote: I had the same problem until I downgraded to streamdev 0.5.0 and hdhomerun_atsc_firmware_20100828.bin. I am not sure both of these changes are necessary as I changed both at the same time. :( Emerged vdr-streamdev instead of git and it's working now, thanks.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] HDHomerun and streamdev
I have just added an HDHomerun to my setup. This is a network tuner, which plugs into VDR with the hdhomerun plugin. VDR picks it up as another ATSC tuner and the same channels.conf works with it as with my ATSC tuners. However, I noticed streamdev doesn't work with it, to either another remote VDR server or VLC. If I turn off the plugin and use the ATSC cards it works again. Not much in the way of useful log info (Ie, nothing..) Rob ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
On 06/10/2011 02:26 AM, Frank Schmirler wrote:
On Wed, 8 Jun 2011 20:43:38 +0200, Martin Dauskardt wrote
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.
Streamdev-client won't forward calls to SetChannelDevice and ProvidesChannel
to the server, if the current channel and the requested new channel are on the
same transponder. Instead it will just go ahead and later add the PIDs of the
new channel to the current connection.
Pvrinput obviously uses the same frequencies (i.e. transponder) and even the
same PIDs for different channels, so streamdev-clients current behaviour is
bound to fail. According to an other posting in this thread, it is not
possible to use different frequencies, so it seems the problem needs to be
fixed in streamdev-client. Please try the following patch:
--- a/common.h
+++ b/common.h
@@ -23,7 +23,7 @@
# define Dprintf(x...)
#endif
-#define TRANSPONDER(c1, c2) (c1-Transponder() == c2-Transponder())
+#define TRANSPONDER(c1, c2) (c1-Transponder() == c2-Transponder()
!c1-IsSourceType('V'))
#define MAXPARSEBUFFER KILOBYTE(16)
AFAIKT the problem is streamdev-client only. So HTTP streaming with e.g. VLC
is not affected.
I need to put something else somewhere else:
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-DCONFDIR=\/etc/vdr\ -DUSE_ALTERNATECHANNEL -DUSE_CHANNELBIND
-DUSE_MCLI -DUSE_PINPLUGIN -DUSE_PLUGINMISSING -DUSE_YAEPG -D_GNU_SOURCE
-DPLUGIN_NAME_I18N='streamdev-client' -I/usr/include
-I/usr/include/vdr/include -I.. -I/usr/include/vdr -o device.o device.c
device.c: In member function ‘virtual bool
cStreamdevDevice::IsTunedToTransponder(const cChannel*)’:
device.c:78:14: error: expected ‘;’ before ‘-’ token
device.c:80:13: warning: statement has no effect
device.c:78:7: error: label ‘Channel’ used but not defined
device.c: In member function ‘virtual bool
cStreamdevDevice::ProvidesChannel(const cChannel*, int, bool*) const’:
device.c:109:38: error: expected primary-expression before ‘)’ token
device.c:109:38: error: expected ‘;’ before ‘)’ token
device.c: In member function ‘virtual bool
cStreamdevDevice::SetChannelDevice(const cChannel*, bool)’:
device.c:135:14: error: expected ‘;’ before ‘-’ token
device.c:137:14: warning: statement has no effect
device.c:135:7: error: label ‘Channel’ used but not defined
make[1]: *** [device.o] Error 1
make[1]: Leaving directory `/usr/src/vdr-src/vdr-plugin-streamdev/client'
make: *** [client] Error 2
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
On 06/10/2011 07:12 PM, Rob Davis wrote: AFAIKT the problem is streamdev-client only. So HTTP streaming with e.g. VLC is not affected. I need to put something else somewhere else: Ooops, my fault. I forgot to take a bracket out. Patch works.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
Ok, will try this out tonight when I get home.
For info. PVRInput should treat every channel as a seperate transponder
(imho).
I think you hit the nail on the head though, it's not detaching the first
stream before starting the second, which is why changing channel on the
remote frontend from say 5 to 8 leaves the backend locked on channel 5.
Conversely, the vomp plugin always seems to detach, which probably leads
to longer channel change times, but works with pvrinput.
Could the patch below work for everyone if a conditional check for tuner
type P was put in?
Hi Rob,
for your (and only for your) problem there could be an easier solution:
When doing a channel switch streamdev queries for a new device while
the current device is still active (means receivers are attached to
the device). If no device could be found, streamdev detaches itself
and queries again.
If streamdev only queries for a device after detaching itself, the
pvrinput device gets closed and reopened again incl. executing the
channel switch thing. This is a really hack with some disadvantages
(e.g. like larger channel switch times in case of multiple channels in
a transponder) but i guess this would help.
I guess doing the following line should be sufficient in
server/connection.c (streamdev-version 0.5.0-CVS):
bool cServerConnection::ProvidesChannel(const cChannel *Channel, int
Priority)
{
const cChannel *current =
Channels.GetByNumber(cDevice::CurrentChannel());
const cChannel *current =
Channels.GetByNumber(cDevice::CurrentChannel());
cDevice *device = CheckDlevice(Channel, Priority, false);
cDevice *device = 0;
if (!device || (device == cDevice::ActualDevice()
!cSuspendCtl::IsActive()
StreamdevServerSetup.SuspendMode != smAlways
current != NULL
!TRANSPONDER(Channel, current))) {
// mustn't switch actual device
// maybe a device would be free if THIS connection did turn off
its
streams?
Detach();
device = CheckDevice(Channel, Priority, false);
Attach();
2011/6/9 Rainer Blickle rainer.blic...@googlemail.com:
Hi Rob,
Can we put a check in streamdev to check if it's a pvrinput device and
recall even if the frequency is the same?
if i got it right the pvr devices hasn't to be retuned when switching
the channel, but the externchannelswitch-script has to be executed.
IMO it isn't a good idea to check for a pvrinput device in the
softdevice server. These two plug-ins shouldn't have any dependencies.
What you really need is that the external channel script gets executed
If some constraints are fullfilled. My first idea is to extend the
core vdr for a callback function which informs plugins about
attaching/detaching receivers to/from a device and retuning of a
device.
With this informations a plugin could execute such
externchannelswitch-scripts.
But i think there is a problem that can't be fixed with this approach:
When watch live tv on channel 1 and streamdev requests channel 2, vdr
cannot handle this. Why? : vdr/streamdev doesn't know that 2 different
pvrinput-devices are needed. Correct me if i'm wrong
___
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] Streamdev to Streamdev with PVRInput card
On 09/06/11 01:53, Rainer Blickle wrote: cDevice *device = CheckDlevice(Channel, Priority, false); cDevice *device = 0; With this there is some improvement, however, its calling the old channel again, so if I change from channel 4 to channel 6 then external channel is called, but changes it to channel 4. I wonder is streamdev-client needs something similar to differentiate channels. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
On 06/09/2011 05:23 PM, Rob Davis wrote: On 09/06/11 01:53, Rainer Blickle wrote: cDevice *device = CheckDlevice(Channel, Priority, false); cDevice *device = 0; With this there is some improvement, however, its calling the old channel again, so if I change from channel 4 to channel 6 then external channel is called, but changes it to channel 4. I wonder is streamdev-client needs something similar to differentiate channels. Here is a logfile.. Started remote vdr on channel 4, switched to channel 5. Somehow the channel settings are being lost when the channel is called.. sudo tail -f /var/log/vdr.log Jun 9 21:12:15 oac vdr: [1696] cPvrReadThread::Action() stopped on /dev/video1 Jun 9 21:12:15 oac vdr: [1696] PvrReadThread of /dev/video1 thread ended (pid=1310, tid=1696) Jun 9 21:12:15 oac vdr: [1695] cPvrDevice::SetEncoderState (Stop) for /dev/video1 (PVR500#1) Jun 9 21:12:15 oac vdr: [1675] streamdev-writer thread ended (pid=1310, tid=1675) Jun 9 21:12:15 oac vdr: [1386] buffer stats: 379008 (10%) used Jun 9 21:12:15 oac vdr: [1386] buffer stats: 0 (0%) used Jun 9 21:12:15 oac vdr: [1695] SetVBImode(525, 0) on /dev/video1 (PVR500#1) Jun 9 21:12:15 oac vdr: [1695] receiver on device 10 thread ended (pid=1310, tid=1695) Jun 9 21:12:16 oac vdr: [1386] streamdev: closing streamdev connection to 192.168.2.13:34100 Jun 9 21:12:16 oac vdr: [1386] buffer stats: 0 (0%) used Jun 9 21:12:38 oac vdr: [1376] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0 Jun 9 21:12:39 oac vdr: [1386] Streamdev: Accepted new client (VTP) 192.168.2.13:38657 Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input -1, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: input -1 unknown on /dev/video0 (HDPVR) Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input 0, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video1 (PVR500#1): Channel 4 (4-WTVO ABC_Affiliate ntsc) 67.25MHz, - true Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video1: Receiving()=false, needsDetachReceivers=true, Priority=0, hasPriority=true Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input 0, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video2 (PVR500#2): Channel 4 (4-WTVO ABC_Affiliate ntsc) 67.25MHz, - true Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video2: Receiving()=true, needsDetachReceivers=true, Priority=0, hasPriority=true Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input 0, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video3 (HVR1600): Channel 4 (4-WTVO ABC_Affiliate ntsc) 67.25MHz, - false Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video3: Receiving()=true, needsDetachReceivers=true, Priority=0, hasPriority=false Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesChannel(0) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesTransponder(0) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesSource(0) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesChannel(1) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesTransponder(1) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesSource(1) Jun 9 21:12:39 oac vdr: [1310] connect from 192.168.2.13, port 33742 - accepted Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input -1, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: input -1 unknown on /dev/video0 (HDPVR) Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input 0, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video1 (PVR500#1): Channel 4 (4-WTVO ABC_Affiliate ntsc) 67.25MHz, - true Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video1: Receiving()=false, needsDetachReceivers=true, Priority=0, hasPriority=true Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input 0, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video2 (PVR500#2): Channel 4 (4-WTVO ABC_Affiliate ntsc) 67.25MHz, - true Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video2: Receiving()=true, needsDetachReceivers=true, Priority=0, hasPriority=true Jun 9 21:12:39 oac vdr: [1386] ParseChannel TV input 0, norm=0xb000, card 999 Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video3 (HVR1600): Channel 4 (4-WTVO ABC_Affiliate ntsc) 67.25MHz, - false Jun 9 21:12:39 oac vdr: [1386] cPvrDevice::ProvidesChannel: /dev/video3: Receiving()=true, needsDetachReceivers=true, Priority=0, hasPriority=false Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesChannel(0) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesTransponder(0) Jun 9 21:12:39 oac vdr: [1386] IPTV: cIptvDevice::ProvidesSource(0) Jun 9 21:12:39 oac vdr: [1386] IPTV
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? i hacked device.c.. But don't tell anyone.. :-) 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. I think this is a streamdev issue not a pvrinput one, as if I change from channel 5 to 6 on the remote streamdev client it will continue to display channel 5. If both my tuners are busy then it will lock to channel 5 on my backend if I test it with xineliboutput. Not lock to channel 6. I had a look at the http::// streamdev playlist settings and it sees different channel pids. Streamdev to vlc would work as it breaks the streamdev connection when you change channel. But streamdev-server to streamdev-client doesn't seem to break the connection, just request a second channel as it releases the first. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Streamdev to Streamdev with PVRInput card
Hi Rob, I also don't think its a pvrinput problem because: 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. ok, that makes sense to me... I am using a brain dead cable box which are being given away by the cable company, these have RF out only on either US Channel 3 or 4. I have two of these wired together with a signal combiner (To minimize the side band intererence). For pvrinput they all need this frequency.. (now at Ch 4), if device 1 is busy I hacked pvrinput to flip the frequency to channel 3, but streamdev would never know this. Can we put a check in streamdev to check if it's a pvrinput device and recall even if the frequency is the same? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Streamdev to Streamdev with PVRInput card
/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8834] cPvrReadThread::Action():timeout on select from /dev/video1: 0:Success - retrying Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 0, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 78396, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 78396, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 78396, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 78396, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 78396, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 154160, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 154160, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 154160, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 154160, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 154160, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 154160, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 228044, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 228044, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 228044, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 228044, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 228044, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 228044, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 302304, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 302304, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 302304, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:54 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 302304, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:55 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 302304, prefill = 314524 for /dev/video1 (PVR500#1) Jun 7 19:13:55 oac vdr: [8833] cPvrDevice::IsBuffering(): available = 302304, prefill = 314524 for /dev/video1 (PVR500#1) -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] adding an analog source to a working vdr installation
On 22/05/11 11:32, Arturo Martinez wrote: Hi, I have a working vdr 1.7.16 installation with a satellite dvb-s2 card working fine. Now I have a separate receiver which I would like to integrate with vdr I have a supported bt878 card (item number 23 in the list) http://linuxtv.org/hg/v4l-dvb/file/tip/linux/Documentation/video4linux/CARDLIST.bttv Besides a scart to rca cable to connect the receiver to the bt878 card what else will I need to do so vdr works with it? The sky plugin? (I am not interested in Sky, just want to have analog video input from my third party receiver into my vdr box) or some other analog tv plugin? You need to use an analog card which will convert the analog stream to an mpep2 stream, such as the Hauppauge PVR series (150, 500 etc). You can probably pick one up on ebay for pennies. Alternatively, you can use the Hauppauge PVR-HD which will give you AC3 audio input and possibly HD input if you can find an HDMI to Component converter. You want one of these and the pvrinput plugin. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How about a small UK/Ireland S28.2E VDR community forum?
On 05/05/11 10:38, Henning Pingel wrote: Hello, [This email has been sitting in my drafts folder for a few weeks. Today I had the courage to send it.] I was wondering if it would make sense to offer a place for VDR users using the sky_uk/freesat/S28.2E/freeview platforms to communicate with each other. The intention is that people can discuss their special needs like freesat EPG, red button stuff, channel lists, channel logos and all other things and test new inventions (like the red button extension) together. Being a frequent user of freesat channels myself and being a member of the developers behind the yaVDR distribution (www.yavdr.org), I would like to offer to you to open up an English language community forum on our yaVDR board located at forum.yavdr.com http://forum.yavdr.com. This board is currently mostly used by our development team for internal discussions, so there is not much to see there for external visitors yet. Please don't get me wrong: I don't want to drag away developer discussions from this mailing list, it's more a forum where developers and users who share the same topics (freesat/freeview/SKY_UK) can communicate and solve problems related to VDR together. And knowledge could be made more accessible for new VDR users. Maybe this could also be a good starting point for building up an English language VDR user community forum - starting off with UK/Ireland users. I always thought an English language community was missing next to the German language VDR portal (www.vdr-portal.de http://www.vdr-portal.de). If some of you guys here are interested in such a place, please give me a short reply. It only takes me a couple of minutes to set up a new area on the forum. Or is there already a forum in place? If that is the case, can you add a US / ATSC / PVRInput section too. I get the feeling there are only three people using VDR in the US.. :-) Although it could be good to share.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ATSC Channel providers California (now OREGON
On 4/9/2011 8:52 PM, Simon Baxter wrote: From what I've read Comcast uses two levels of encryption, a basic one for tier one channels (extended basic in marketing terms) then a more comprehensive key encryption for their digital preferred channels. I use a combination of two set top boxes, a PVR HD for HD channels and a PVR500 for SD channels, and two Clear Qam adapters for locals. The Clear Qam are very good quality MPEG 2 HD or SD streams with AC3 audio, the PVR500 is reasonable, but one my boxes has interference on the svideo output. The HD-PVR is really good, giving an H264 with AC-3 passthrough TS stream. However, every now and then the cable box glitches and the HD-PVR stops streaming. PVRInput isn't aware (yet - although Lars is looking into it) that it's not sending anything to VDR. This is a problem when recording as VDR restarts, if I'm doing concurrent recordings then I lose bits of other recording during this time. As an aside, AC-3 is passed through from the original ATSC-QAM stream, I had to patch VDR again to stop checking for ATSC on Audio Type 0x81 or VDR would ignore the audio dpid of the channel and set it to 0. This also had to be done for the VNSI plugin in XBMC-PVR. I really want to thank Lars for teaching me about TS streams.. New question - what hardware support is there for VDR and ATSC? I'm moving to the US, so will be ditching my DVB-C and DVB-S hardware - what should I be buying to work with VDR? I would wait until you get here and then spend a week asking people. I use Comcast at home but have been thinking of switching to Dish as I thought it was supported better with VDR: However, you have to jump through so many hoops now to get it working, it might not be worth it. You could find just using OTA ATSC is good enough and then get Netflix working (alas not in VDR without a bit of hacking and a spare windows PC). Netflix has huge back catalogs of stuff which more than makes up for cable. Any Hauppauge ATSC card will work with Linux either as a PCI or PCI-E. However, there is a minor glitch with the usb cards where they can refuse to sync on a station without unplugging and replugging. Some comcast boxes have firewire output. You can change the channel and get SD and HD out of these, and the IPTV plugin can be made to work with them. However, no decrytion can be done with Linux yet (without severe hoop jumping - read resoldering the motherboard of your sat box to find the box id). IMHO it's better you use an analog input stream. If you can leave a VDR box back home then you can streamdev it to get home TV in the US, something that we would have liked to have done.. Rob ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Firewire output on cable box.
Hi Guys, I discovered yesterday that my cable box produces usable input on the firewire output. Following a mythtv tutorial I managed to get a reasonable ts stream dumped to a file. However, each channel appears to have it's own vpid and apid/dpid (often several) similar to ATSC content. I'm guessing the cable box it outputting the raw ts. To get the fire I followed this page: http://www.mythtv.org/wiki/FireWire And managed to get test-mpeg2 working. This file was playable (in really good quality) on xbmc. Is there a way I can get this into VDR? I tried iptv, but ffmpeg throws an error: [mpegts @ 0x80719c0] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 228701 = 228701 av_interleaved_write_frame(): Operation not permitted Probably due to bugs in the ts stream.. I also tried test-mpeg2 -r 0 - | nc -u 127.0.0.1 4321 in a script but iptv believed the script had finished and tried to kill it? I can put a 1 min sample somewhere if it'll help? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Firewire output on cable box.
On 2/19/2011 3:34 PM, Rob Davis wrote: Hi Guys, I discovered yesterday that my cable box produces usable input on the firewire output. Following a mythtv tutorial I managed to get a reasonable ts stream dumped to a file. However, each channel appears to have it's own vpid and apid/dpid (often several) similar to ATSC content. I'm guessing the cable box it outputting the raw ts. To get the fire I followed this page: http://www.mythtv.org/wiki/FireWire And managed to get test-mpeg2 working. This file was playable (in really good quality) on xbmc. Is there a way I can get this into VDR? I tried iptv, but ffmpeg throws an error: [mpegts @ 0x80719c0] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 228701 = 228701 av_interleaved_write_frame(): Operation not permitted Probably due to bugs in the ts stream.. I also tried test-mpeg2 -r 0 - | nc -u 127.0.0.1 4321 in a script but iptv believed the script had finished and tried to kill it? I can put a 1 min sample somewhere if it'll help? Ok, turns out it was streaming both my cable boxes together in one stream. I appear to have seperated the streams some how.. Now it seems to work with ffmpeg.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] iptv question (possible conflict with altchannel patch)
I noticed that on my setup (1.7.16) iptv only displays one iptv stream. I'm sure it used to do more than one if selected on a different frontend (I think I had up to 8). Is this a change from iptv 0.3.4 to 0.4.2 or is it a conflict with the altchannel plugin..? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] XBMC vnsi dts/pts errors on ATSC Channel through VDR
Using VDR 1.7.16 and the vnsi plugin, xbmc seems to be struggling to play
one particular channel. Unfortunetly, it's the channel I'm doing a
temporary admin contract for, so I kind of need to see it. vdr-sxfe plays
it OK, but I get too much video stuttering on it, and all other channels
play ok on xbmc/vdr.
Working at the station, if the problem is there, I have a hope of getting
it fixed. Their sister station using the same equipment but on a
different frequency and antenna (transmitter) is fine.
I get the same symptoms using both OTA (8vsb) and via Comcast QAM256, so
am fairly sure the problem is specific to something at the station.
The code from demuxer.c (in vnsi plugin) that's being triggered is this:
else if(checkTimestamp)
{
int d = dts + m_epochDTS - m_LastDTS;
if (d 0 || d 9) {
if (d -PTS_MASK || d -PTS_MASK + 18)
{
m_badDTS++;
if (m_badDTS 5)
{
dsyslog(VNSI-Error: DTS discontinuity. DTS = %10lu, last =
%10lu, dts, m_LastDTS);
}
}
else
{
/* DTS wrapped, increase upper bits */
m_epochDTS += PTS_MASK + 1;
m_badDTS = 0;
}
}
I get my logs filled with the VNSI-Error, DTS discontinuity. The audio
stutters. It appears to be AC-3 Stereo, but may be labelled 5.1? I have
audio passthrough to my amp. On another laptop with analog output it
seems to stutter in a different way..
I'm fairly happy putting some kind of checking in VDR or VNSI and
recompiling if it'll help. I have two ATSC tuners, it happens to both
tuners.
Thanks
Rob
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XBMC vnsi dts/pts errors on ATSC Channel through VDR
(Un?)fortunately, this issue doesn't occur in xineliboutput, as the
source is actually HD Mpeg2 720p with AC3, but the issue I have is only
with XBMC and vnsiserver. I am wondering if there's a clock set wrong on
their ATSC muxer or something like that which xine and every set top box
out there ignores, but XBMC looks at.
On 21/01/11 12:34, Timothy D. Lenz wrote:
There was a patch posted a day or two in the in the xine list that had
to do with pts. From freenode #xine:
[11:43] rnissl in case of a video freeze, I assume you had a clock error
[11:44] rnissl hotwings suffers them too for h264
[11:54] hotwings btw, you fixed the pts error rnissl. but when it
occurs the video glitches/freezes briefly. however other players go
smooth right through it (like coreavc+mpc in windows). i think thats due
to bugs in the frame stuff though and not how the pts error is handled
right?
[11:54] rnissl yes, acutally, the pts error is just a pts wrap and
shouldn't be handled like that.
[11:55] rnissl my plans are to release a patch this week which makes
the handling configureable
[11:56] rnissl although I think that this kind of handling is not
necessary or wrong, there may be situations where removing the code
causes other trouble
[11:57] rnissl so a config option should suit both interests
On 1/21/2011 8:58 AM, Rob Davis wrote:
Using VDR 1.7.16 and the vnsi plugin, xbmc seems to be struggling to play
one particular channel. Unfortunetly, it's the channel I'm doing a
temporary admin contract for, so I kind of need to see it. vdr-sxfe plays
it OK, but I get too much video stuttering on it, and all other channels
play ok on xbmc/vdr.
Working at the station, if the problem is there, I have a hope of getting
it fixed. Their sister station using the same equipment but on a
different frequency and antenna (transmitter) is fine.
I get the same symptoms using both OTA (8vsb) and via Comcast QAM256, so
am fairly sure the problem is specific to something at the station.
The code from demuxer.c (in vnsi plugin) that's being triggered is this:
else if(checkTimestamp)
{
int d = dts + m_epochDTS - m_LastDTS;
if (d 0 || d 9) {
if (d -PTS_MASK || d -PTS_MASK + 18)
{
m_badDTS++;
if (m_badDTS 5)
{
dsyslog(VNSI-Error: DTS discontinuity. DTS = %10lu, last =
%10lu, dts, m_LastDTS);
}
}
else
{
/* DTS wrapped, increase upper bits */
m_epochDTS += PTS_MASK + 1;
m_badDTS = 0;
}
}
I get my logs filled with the VNSI-Error, DTS discontinuity. The audio
stutters. It appears to be AC-3 Stereo, but may be labelled 5.1? I have
audio passthrough to my amp. On another laptop with analog output it
seems to stutter in a different way..
I'm fairly happy putting some kind of checking in VDR or VNSI and
recompiling if it'll help. I have two ATSC tuners, it happens to both
tuners.
Thanks
Rob
___
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
--
Rob Davis
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ATSC Channel providers California
On 01/10/10 14:21, Simon Baxter wrote: Is there a CI/CAM option with ATSC-QAM cards? Or are the cable network encryption mechanisms proprietary (needing PVR with HDMI to get into VDR)? As Thomas said, ATSC OTA is always free, however, CableCo's encrypt some of their channels. I had to hack VDR to stop it from updating CAID as Comcast here put a CAID on channels that actually were FTA. I also had to patch VDR to allow stream type 0x80 to actually be 0x02, (Mpeg) as my PBS stations were encoded with type 0x80, which meant VDR gave them a vpid of 0 and thought they were radio channels. From what I've read Comcast uses two levels of encryption, a basic one for tier one channels (extended basic in marketing terms) then a more comprehensive key encryption for their digital preferred channels. I use a combination of two set top boxes, a PVR HD for HD channels and a PVR500 for SD channels, and two Clear Qam adapters for locals. The Clear Qam are very good quality MPEG 2 HD or SD streams with AC3 audio, the PVR500 is reasonable, but one my boxes has interference on the svideo output. The HD-PVR is really good, giving an H264 with AC-3 passthrough TS stream. However, every now and then the cable box glitches and the HD-PVR stops streaming. PVRInput isn't aware (yet - although Lars is looking into it) that it's not sending anything to VDR. This is a problem when recording as VDR restarts, if I'm doing concurrent recordings then I lose bits of other recording during this time. As an aside, AC-3 is passed through from the original ATSC-QAM stream, I had to patch VDR again to stop checking for ATSC on Audio Type 0x81 or VDR would ignore the audio dpid of the channel and set it to 0. This also had to be done for the VNSI plugin in XBMC-PVR. I really want to thank Lars for teaching me about TS streams.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Request - support for ATSC type channel numbers
Not sure if in Euroland, you're aware of how US digital is working and whether it's possible to support the US/ATSC channel number system. Essentially what's happening is a channel will appear on a frequency, then each sub channel is appending to the frequency number with either a . or a -. So, my ABC local channel is on 17. The main channel has a sid of 1, so the channel number is 17.1 or 17-1. They also have a network called MyNetwork, which has a sid of 2, so comes in as 17-2. Just to confuse matters, the 17 is actually the frequency of their old over the air frequency, they actually come in on a different frequency but have a virtual channel number of 17. The SD channels come in essentially as the same, but with a 2 stuck at the beginning, so 217.1 is ABC in SD. My normal TV when channel scanning mixes analog cable channels with digital ones. So old channels are on 2, 3, 4 up to 66, then ATSC channels appear starting on 13.1, 13.2, with 14 being an NTSC analog channel. (This is for Clear-QAM, although ATSC ota has the same type of numbering.). Anyway, is there anyway of getting VDR to support a sub channel number with a dash or period? -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Alternative-Channel patch
On 14/10/10 02:27, Rainer Blickle wrote: Has anybody but me applied this patch ? Rainer The patch seems spread across vdr and skincurses, which I don't use, so it didn't apply. Am looking at breaking it up into manageable parts and trying. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Understanding AC-3
On 02/09/10 13:35, Rolf Ahrenberg wrote: On Thu, 2 Sep 2010, Rob Davis wrote: How do you go about understanding AC-3 within a VDR context? (apart from reading up on it online - which now has my head spinning). The current ATSC AC-3 support requires the 'A' source type for channels and therefore VDR never use ATSC hacks for any pvrinput channel. A quick and dirty hack would be adding an additional check for the pvrinput source type into cChannel::IsAtsc(). Thanks Rolf, I took out the ATSC check in pat.c and now the hd-pvr channel is updating correctly. I don't know why the hd-pvr is also trying to use type 0x81 instead of 6. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Understanding AC-3
On 02/09/10 13:35, Rolf Ahrenberg wrote: On Thu, 2 Sep 2010, Rob Davis wrote: How do you go about understanding AC-3 within a VDR context? (apart from reading up on it online - which now has my head spinning). The current ATSC AC-3 support requires the 'A' source type for channels and therefore VDR never use ATSC hacks for any pvrinput channel. A quick and dirty hack would be adding an additional check for the pvrinput source type into cChannel::IsAtsc(). I commented out the conditional for IsAtsc on type 81 and the hdpvr stuff is now updating correctly. I wonder if this is because the Hauppauge box is passing the AC-3 stream on from the cable decoder which is probably finding encoded Qam 256 under ATSC..? Do we need to check it's ATSC if type is 0x81? Does anything else use it and is it a problem if it does? -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Understanding AC-3
Hi Guy's, How do you go about understanding AC-3 within a VDR context? (apart from reading up on it online - which now has my head spinning). I have a Hauppauge PVR-HD and two ATSC cards. The ATSC cards work as they should and with the new atsc/dn patch on 1.7.15 now have the correct dpids. However, if I turn on add new transponders or update pids, then my Hauppauge PVR channels lose their dpid values.. Sep 1 19:10:33 oac vdr: [8186] changing pids of channel 920 from 4113+4097=27:0;4352=...@106:0:0 to 4113+4097=27:0:0:0 If I keep automatic channel updates off, then xineliboutput and streamdev work for these channels, but vdr-vnsi (xbmc) and vdr-xine don't (no audio).. I'm assuming vdr parses the ac3 headers in some way and sends information onto the playback frontend. How would I go about seeing what those headers might be and looking into patching pat.c accordingly? I noticed all the comments about e-ac3 and wonder if a similar patch should be made for this device. As an aside, vdr recordings from these channels play back fine in vdr-xine. So, more specifically, I suppose I would like to know how to find out the STREAMTYPE: I'm pretty sure it falls under this: case 6: // STREAMTYPE_13818_PES_PRIVATE But I'd be interested in seeing the flow through this section of pat.c and what is happening.. Mainly to see if something needs to be forced on? I can create a five second VDR recording if someone wants to see what the TS stream looks like.. But I'd be interested in diagnosing it myself.. Thanks. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Understanding AC-3
On 02/09/10 11:05, L. Hanisch wrote: Hi, Just an additional info for the ones who want to help - the pvrinput-plugin passes through the TS from the HD PVR to vdr, there's nothing changed. So hopefully the plugin is not the one to blame for... :-) I posted a sample PAT and PMT of the HD PVR in february, perhaps it can be used to clarify something. http://www.linuxtv.org/pipermail/vdr/2010-February/022400.html How do you create the PAT and PMT files and then understand them. I'm pretty sure that sample file was only mp3 input instead of AC3 digital which is what I use now.. Lars. Am 02.09.2010 15:21, schrieb Rob Davis: Hi Guy's, How do you go about understanding AC-3 within a VDR context? (apart from reading up on it online - which now has my head spinning). I have a Hauppauge PVR-HD and two ATSC cards. The ATSC cards work as they should and with the new atsc/dn patch on 1.7.15 now have the correct dpids. However, if I turn on add new transponders or update pids, then my Hauppauge PVR channels lose their dpid values.. Sep 1 19:10:33 oac vdr: [8186] changing pids of channel 920 from 4113+4097=27:0;4352=...@106:0:0 to 4113+4097=27:0:0:0 If I keep automatic channel updates off, then xineliboutput and streamdev work for these channels, but vdr-vnsi (xbmc) and vdr-xine don't (no audio).. I'm assuming vdr parses the ac3 headers in some way and sends information onto the playback frontend. How would I go about seeing what those headers might be and looking into patching pat.c accordingly? I noticed all the comments about e-ac3 and wonder if a similar patch should be made for this device. As an aside, vdr recordings from these channels play back fine in vdr-xine. So, more specifically, I suppose I would like to know how to find out the STREAMTYPE: I'm pretty sure it falls under this: case 6: // STREAMTYPE_13818_PES_PRIVATE But I'd be interested in seeing the flow through this section of pat.c and what is happening.. Mainly to see if something needs to be forced on? I can create a five second VDR recording if someone wants to see what the TS stream looks like.. But I'd be interested in diagnosing it myself.. Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] New ATSC Video Type 0x80?
I am trying to get my head around ATSC / AC3 and have discovered some ATSC Clear Qam channels disappear when update channels is on. Some playing around with pat.c and the isyslog command, I have discovered they appear to have a different type than normal.. Normally Mpeg2 is type 2, but these are 0x80? I notice they do the same thing with AC-3 (0x81 instead of 6) so probably something similar is going on. Sep 2 23:11:29 oac vdr: [5815] pat.c stream type = 80, pid = 2240 Sep 2 23:11:29 oac vdr: [5815] pat.c stream type = 81, pid = 2241 Sep 2 23:11:29 oac vdr: [5815] pat.c wants to update channel Sep 2 23:11:29 oac vdr: [5815] changing pids of channel 355 from 0+0=0:0;22...@106:0:0 to 2240+2240=128:0;22...@106:0:0 If hard coded with vpid and pid of 2240=2 and update channels of, then the picture shows. I will attempt to diagnose tomorrow, probably by adding another Case 0x80 under Case 2 in pat and remux but wanted to point this out for future reference as I know most of the development is done outside of the ATSC world.. Then it's back to working out why my pvr-hd ac-3 (h264 and ac3 @ 720p) don't work in vdr-xine and xbmc/vnsi.. (although do work in vdr-xineliboutput and xbmc/streamdev..) -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LCDProc Status
On 01/09/10 01:51, Matthias Becker wrote: Which version of VDR do you use? 1.7.15, under Gentoo. 2010/8/31 Rob Davisr...@davis-family.info: On 31/08/10 10:49, Rob Davis wrote: On 31/08/10 01:44, Matthias Becker wrote: The plugin is comunity maintained and it's newest version can be found via: http://projects.vdr-developer.org/projects/plg-lcdproc 2010/8/31 VDR Useruser@gmail.com: What error do you see in the log when you try loading the lcd plugin? I'm using the latest version from the site above. The gdb backtrace is: gdb --args vdr -Plcdproc GNU gdb (Gentoo 7.1 p1) 7.1 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-pc-linux-gnu. For bug reporting instructions, please see: http://bugs.gentoo.org/... Reading symbols from /usr/bin/vdr...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/vdr -Plcdproc [Thread debugging using libthread_db enabled] [New Thread 0xb77beb70 (LWP 20271)] [New Thread 0xb6fbdb70 (LWP 20272)] [Thread 0xb6fbdb70 (LWP 20272) exited] [Thread 0xb77beb70 (LWP 20271) exited] [New Thread 0xb77beb70 (LWP 20277)] [New Thread 0xb6fbdb70 (LWP 20278)] [New Thread 0xb65ffb70 (LWP 20280)] [New Thread 0xb5dfeb70 (LWP 20281)] vdr: no primary device found - using first device! [New Thread 0xb55fdb70 (LWP 20282)] [New Thread 0xb4dfcb70 (LWP 20283)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb55fdb70 (LWP 20282)] cLcd::Action (this=0xb660e220) at lcd.c:847 847 const cSchedule *Schedule = Schedules-GetSchedule(channel-GetChannelID()); (gdb) bt #0 cLcd::Action (this=0xb660e220) at lcd.c:847 #1 0x08138555 in cThread::StartThread(cThread*) () #2 0xb7f45a24 in start_thread () from /lib/libpthread.so.0 #3 0xb7c9fb2e in clone () from /lib/libc.so.6 (gdb) -- Rob Davis ___ 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 -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LCDProc Status
On 31/08/10 01:44, Matthias Becker wrote:
The plugin is comunity maintained and it's newest version can be found via:
http://projects.vdr-developer.org/projects/plg-lcdproc
2010/8/31 VDR Useruser@gmail.com:
What error do you see in the log when you try loading the lcd plugin?
I'm using the latest version from the site above.
According to gdb debug, it's seg faulting on line 847 of lcd.c
const cSchedule *Schedule =
Schedules-GetSchedule(channel-GetChannelID());
The context is:
const cSchedule *Schedule =
Schedules-GetSchedule(channel-GetChannelID());
if (Schedule) {
const char *PresentTitle,
*PresentSubtitle;
PresentTitle = NULL;
PresentSubtitle = NULL;
if ((Present =
Schedule-GetPresentEvent()) != NULL) {
nextLcdUpdate=Present-StartTime()+Present-Duration();
PresentTitle =
Present-Title();
PresentSubtitle =
Present-ShortText();
if (
(LcdSetup.ShowSubtitle) (!isempty(PresentTitle))
(!isempty(PresentSubtitle)) )
SetRunning(false,Present-GetTimeString(),PresentTitle,PresentSubtitle);
else if (
(LcdSetup.ShowSubtitle) !isempty(PresentTitle))
SetRunning(false,Present-GetTimeString(),PresentTitle);
} else
SetRunning(false,tr(No EPG info available.), NULL);
if ((Present =
Schedule-GetFollowingEvent()) != NULL)
nextLcdUpdate=(Present-StartTime()nextLcdUpdate)?Present-StartTime():nextLcdUpdate;
rtcycle = 10; // RT
lcrCycle = 10; // LCR
}
}
--
Rob Davis
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LCDProc Status
On 31/08/10 10:49, Rob Davis wrote: On 31/08/10 01:44, Matthias Becker wrote: The plugin is comunity maintained and it's newest version can be found via: http://projects.vdr-developer.org/projects/plg-lcdproc 2010/8/31 VDR Useruser@gmail.com: What error do you see in the log when you try loading the lcd plugin? I'm using the latest version from the site above. The gdb backtrace is: gdb --args vdr -Plcdproc GNU gdb (Gentoo 7.1 p1) 7.1 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-pc-linux-gnu. For bug reporting instructions, please see: http://bugs.gentoo.org/... Reading symbols from /usr/bin/vdr...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/vdr -Plcdproc [Thread debugging using libthread_db enabled] [New Thread 0xb77beb70 (LWP 20271)] [New Thread 0xb6fbdb70 (LWP 20272)] [Thread 0xb6fbdb70 (LWP 20272) exited] [Thread 0xb77beb70 (LWP 20271) exited] [New Thread 0xb77beb70 (LWP 20277)] [New Thread 0xb6fbdb70 (LWP 20278)] [New Thread 0xb65ffb70 (LWP 20280)] [New Thread 0xb5dfeb70 (LWP 20281)] vdr: no primary device found - using first device! [New Thread 0xb55fdb70 (LWP 20282)] [New Thread 0xb4dfcb70 (LWP 20283)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb55fdb70 (LWP 20282)] cLcd::Action (this=0xb660e220) at lcd.c:847 847 const cSchedule *Schedule = Schedules-GetSchedule(channel-GetChannelID()); (gdb) bt #0 cLcd::Action (this=0xb660e220) at lcd.c:847 #1 0x08138555 in cThread::StartThread(cThread*) () #2 0xb7f45a24 in start_thread () from /lib/libpthread.so.0 #3 0xb7c9fb2e in clone () from /lib/libc.so.6 (gdb) -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] LCDProc Status
What's the status of this plugin? I have a two line LCD display which works with xbmc, but when I tried to use the lcdproc vdr plugin VDR won't start up.. I'm using lcdproc-0.0.10-jw7 I just get: Aug 30 18:18:47 oac vdr: LCDproc-Plugin started at 127.0.0.1:13666. Aug 30 18:18:47 oac vdr: [1355] setting current skin to PearlHD Aug 30 18:18:47 oac vdr: [1355] loading /etc/vdr/themes/PearlHD-default.theme Aug 30 18:18:47 oac vdr: [1355] switching to channel 908 Aug 30 18:18:47 oac vdr: LCD output thread started (pid=1355), display size: 2x20 Aug 30 18:18:47 oac vdr: [1437] receiver on device 1 thread started (pid=1355, tid=1437) Aug 30 18:18:47 oac vdr: [1438] TS buffer on device 1 thread started (pid=1355, tid=1438) Aug 30 18:18:47 oac /etc/init.d/vdr[1450]: VDR errors from /var/log/vdr.log: Aug 30 18:18:47 oac /etc/init.d/vdr[1451]: ERROR: /etc/vdr/plugins/live/live.pem: No such file or directory Aug 30 18:18:47 oac /etc/init.d/vdr[1258]: ERROR: vdr failed to start In the logs -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LCDProc Status
On 30/08/10 20:09, VDR User wrote: Aug 30 18:18:47 oac /etc/init.d/vdr[1451]: ERROR: /etc/vdr/plugins/live/live.pem: No such file or directory Well, it seems to be telling you the problem Unfortunately not, that's a certificate missing from another plugin. VDR works fine like this and is a known feature of the vdr-live plugin.. Here is a later log showing all is well when that plugin is removed: Aug 30 18:39:25 oac vdr: [4127] [xine..put] cXinelibServer priority set successful SCHED_RR 2 [1,99] Aug 30 18:39:25 oac vdr: [4127] [xine..put] Listening on port 37890 Aug 30 18:39:25 oac vdr: [4127] [xine..put] Listening for UDP broadcasts on port 37890 Aug 30 18:39:25 oac vdr: [4127] [discovery] BROADCAST: VDR xineliboutput DISCOVERY 1.0 Aug 30 18:39:25 oac vdr: [4126] ERROR: /etc/vdr/plugins/live/live.pem: No such file or directory Aug 30 18:39:25 oac vdr: [4070] [xine..put] cXinelibDevice::StartDevice(): Device started Aug 30 18:39:25 oac vdr: [4070] starting plugin: text2skin Aug 30 18:39:25 oac vdr: [4070] text2skin: loading /etc/vdr/plugins/text2skin/PearlHD/PearlHD.colors Aug 30 18:39:25 oac vdr: [4070] parsing /etc/vdr/plugins/text2skin/PearlHD/PearlHD.skin Aug 30 18:39:25 oac vdr: [4070] starting plugin: streamdev-server Aug 30 18:39:25 oac vdr: [4070] loading /etc/vdr/plugins/streamdev-server/streamdevhosts.conf Aug 30 18:39:25 oac vdr: [4070] streamdev-server: Not starting IGMP. IGMP must be bound to a local IP and on and on.. VDR is still running 4 hours later.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
Sorry to jump in on this, but I wonder if people could suggest what the settings should be in xineliboutput plugins options? I have just upped my card from an 8400 to an N210 with 512MB ram in order to get 1080i/60hz interlacing working. It's an improvement, but I think I still have somewhere to go. I am using a Eurospec TV although am trying to use it at 60hz (I moved to the US from Italy) via a DVI to HDMI cable. I have two modelines, which I switch by my remote using the xrandr command, 720p60 looks better, but I think I should using 1080i I have two ATSC card which show 720p60 and 1080i60 and a Hauppuage PVR HD and the pvrinput plugin, this I use to show HD content from a cable box. That I can select to either 1080i or 720p. Most of the content is originally broadcast in 1080i. I am using ModeLine 1920x1080i60 74.18 1920 2008 2052 2200 1080 1084 1094 1124 +HSync +VSync Interlace and Modeline 1280x720_60 74.48 1280 1336 1472 1664 720 721 724 746 -HSync +Vsync X won't display the correct resolution by default, as my edid is messed up on my TV. What deinterlacing options should I use on the plugin? Bob? TVTime then scaler Bob? Judder correct etc etc? Most SD stuff here is badly done 4:3, with stations like BBC America adding black bars to the top and bottom, so I get a square in the middle of the TV. Xineliboutput can zoom this quite well, but after a while the whole picture judders until I kill vdr-sxfe and reload it. Do I need FFMpeg to work alongside it or will that kill vdpau? Thanks.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Dish Network and Diseqc switches.
I had a nice European sat system until moving to the US. Since coming here I've cludged VDR to work with cable using PVR cards and an HD-PVR. However, I bought a Dish Network satellite Superdish at an auction for about $2.50 and wondered if I can get it working with my DVB-S cards. It appears to have three LNB's, a dual one and then a side one. Each LNB seems to have two plugs coming off it. Can I connect all three to a Eurospec Diseqc switch I brought with me or does it need it's own switch from Dish Networks? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Add missing Dtypes for ATSC
: For PID 1100 AC3 properties changed at 00:22:31.988 (2.0 48kHz 5.1 48kHz) TS WARNING: For PID 1011 $01A89521: Paket discontinuity 6,2 TS WARNING: For PID 1100 $01A8960F: Paket discontinuity 15,9 TS Warning: PCR timing for PID 1001 last PCR:00:52:07.469 current PCR:00:00:01.616 at paket $01A89662 TimeBase:145414 PCRExtension:194 ES WARNING: For PID 1100 AC3 properties changed at -00:29:11.116 (5.1 48kHz 2.0 48kHz) ES WARNING: For PID 1100 AC3 properties changed at -00:28:11.820 (2.0 48kHz 5.1 48kHz) - NAL Unit Type Statistic - Slices : 385218 I-Slices : 0 P-Slices : 0 B-Slices : 0 SP-Slices : 0 SI-Slices : 0 Data Partition A : 0 Data Partition B : 0 Data Partition A : 0 IDR Picture: 3034 SEI: 388252 Sequence Parameter Set : 12135 Picture Parameter Set : 388252 AUD: 388252 End of Sequence: 0 End of Stream : 0 Filler : 0 Slices : 0 Seq. Param. Set Ext. : 0 Cutted pakets at the beginning: 0 Cutted pakets at the end: 0 Discarded pakets (not needed): 24270 [/Code] -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hulu plugin yet?
On 29/07/10 17:36, VDR User wrote: On Thu, Jul 29, 2010 at 1:22 PM, Timothy D. Lenz tl...@vorgon.com wrote: Now that Hulu is offering HD of sorts (720 with sub), are there any plugins in the works to give vdr hulu access? So far the only thing I've seen are just scripts to shutdown vdr and switch to some other program. If mplayer can play hulu then I guess you could hack together something for the mplayer plugin. I use the PlayOn server on a windows box with djmount.. djmount -o playlists -o allow_other /mnt/media/Movies/DLNA Then use xine to find the playlists... I tried using playon with vmware, but got stuttering. Playback is better on xbmc.. Also the Nintendo Wii plays back very well. It does Netflix too. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] pvr-testing2 xbmc discussion
Eric Valette wrote: In vnsiserver, ac3 spdif sound seems all mixed up. ATSC here only uses AC-3, but 5.1 sound only plays with Left and Right front speakers, so I can't hear any dialogue. On my HD-PVR, I get no sound at all, xbmc sees an AC-3 stream, but the info page says 0 speakers? However, the audio settings while the stream is playing believes it to be a 5.1 audio track (which it is..) vnsiserver seems much better with the hdpvr as it doesn't start and stop the stream three times like streamdev does.. (Big blue light flashes on the hd-pvr box when it's being used.) Streamdev will not display output correctly from my pvr500 card using pvrinput. It works with vnsi and obviously vdr-sxfe.. Well, on the other hand, streamdev works with eac3 not vnsserver. In france HD TV use eac3 for audio. Sreamdev works thus better than vnsiserver for me . I suspect the issue we're having with vnsi is pretty much the same, audio passthrough is broken. If vnsi recognises the audio then it converts it to only two channels. In your case it doesn't so you probably get only a picture, which I get with my pvr-input based hdpvr. My other issue is only with the pvr-input plugin and streamdev. The analogue channels (which I use for cable channels through a set top box and a channel change script) gets scrambled when it arrives at xbmc. Ffmpeg doesn't recognise the codec. However that works with vnsi. My hdpvr basically does the same thing for HD channels. It converts them to an h264 channel with ac3 audio. With streamdev, it seems the input is opened three times before the stream is sent (Big blue light comes on and goes off three times) then 1 in 3 times 10 seconds later xbmc starts to show it. With vnsi, within 3 seconds the picture comes on the screen, but no audio. vdr-sxfe, the audio goes out of sync within about 10 mins with vdpau and the hd-pvr.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] pvr-testing2 xbmc discussion
Does anyone know where this is happening now? I know the xbmc forum was down for a while, but this discussion never seemed to happen again afterwards. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] pvr-testing2 xbmc discussion
On 12/05/10 09:24, Henning Pingel wrote: Am Mittwoch, den 12.05.2010, 15:27 +0200 schrieb Rob Davis r...@davis-family.info: Does anyone know where this is happening now? I know the xbmc forum was down for a while, but this discussion never seemed to happen again afterwards. Hello Rob, Could you please specify in what kind of PVR discussion or what kind of information you are interested? I could point out a few threads to you but I'm confused about what you want and why you ask here and not on the XBMC forum? The whole vdr-plugin-vnsiserver discussion is IMHO taking place at www.vdr-portal.de ATM. Cheers, Henning I used to use: http://forum.xbmc.org/showthread.php?t=45314page=54 But it hasn't been updated for a while. I have been using pvr-testing and pvr-testing2 for a while now, and try to keep up to date. However, I have two problems/questions which I want to either ask or flag to the developers but am unsure how to do it or even if it's a known issue? One is, there is an epg issue with people in the -X to GMT timezone, where our listings don't appear for X-1 hours. (So me being in the Chicago timezone (6 hours behind London) At 7am, xbmc won't see any listings before 12pm... I hacked this in a previous version, but don't know whether this is a known issue which is being addressed? It happens with both vnsi and streamdev. In vnsiserver, ac3 spdif sound seems all mixed up. ATSC here only uses AC-3, but 5.1 sound only plays with Left and Right front speakers, so I can't hear any dialogue. On my HD-PVR, I get no sound at all, xbmc sees an AC-3 stream, but the info page says 0 speakers? However, the audio settings while the stream is playing believes it to be a 5.1 audio track (which it is..) vnsiserver seems much better with the hdpvr as it doesn't start and stop the stream three times like streamdev does.. (Big blue light flashes on the hd-pvr box when it's being used.) Streamdev will not display output correctly from my pvr500 card using pvrinput. It works with vnsi and obviously vdr-sxfe.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PVRINPUT plugin and black/cinema bars
On Mon, Apr 26, 2010 at 12:42 PM, Martin Dauskardt md...@gmx.de wrote: 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. If the aspect ratio flag is unreliable, again, you can always just use the resolution and calculate it. 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. If you want to limit the plugin to using only the hardware then I agree. However, if you want to provide capabilities beyond what the hardware is capable of then software is the only other place to do it. This is perfectly fine, although it probably means the user wasted his money on a hardware decoder if he's just going to do software decoding anyways. It doesn't hurt to put more consideration into what you want/need before pouring money into hardware. I know guys that threw a lot of money at hardware decoders only to replace them with cheap vdpau-capable video cards. To each his own I suppose. :) Cheers Except this is an input device, not an output device. It converts an analogue signal to mpeg2, as such, it needs to make guesses about what it's going to find.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ATSC Channel frequency crashing VDR
On Tue, Apr 13, 2010 at 12:45 PM, Rob Davis r...@davis-family.info wrote: The usb adapter works upstairs on a patched VDR 1.6, but am not sure it works on 1.7.12 yet.. Will try again tomorrow. My main problem is by the time I get home from work, my wife wants to watch TV. Maybe she should read a book instead for a change then? Go for a walk/run? Take a nap? ;) SOLVED... It turns out when everything was moved about on Saturday (We just moved into our house), someone stuck some power supplies over the cable feed. I guess I was getting interference on just that frequency. The tests I was doing was in another part of the house, which was why it worked.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ATSC Channel frequency crashing VDR
Yup, me too. I have a button setup on my remote to kill vdr-sxfe and start xbmc-pvr, or vice versa. That way I don't need to get out of my chair to fix xine. I also find on h264 streams, audio goes out of sync easily with vdpau/xine. Doesn't happen with either mplayer or xbmc. I have a Hauppauge PVR-HD which streams hd content from my cable box.. I use vdpau and find it VERY picky about stream quality. It will crash. Xine not as bad but still more picky then the HW video out of a nexus. You could leave that on a badly pixelated stream all day. I've seen vdpau crash even when there are no visual problems with the stream. When it goes down, it seems to take xine with it. A big problem with using ATA and the signal is weak. On 4/14/2010 5:33 AM, Rob Davis wrote: On Tue, Apr 13, 2010 at 12:45 PM, Rob Davisr...@davis-family.info wrote: The usb adapter works upstairs on a patched VDR 1.6, but am not sure it works on 1.7.12 yet.. Will try again tomorrow. My main problem is by the time I get home from work, my wife wants to watch TV. Maybe she should read a book instead for a change then? Go for a walk/run? Take a nap? ;) SOLVED... It turns out when everything was moved about on Saturday (We just moved into our house), someone stuck some power supplies over the cable feed. I guess I was getting interference on just that frequency. The tests I was doing was in another part of the house, which was why it worked.. ___ 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 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using different types of device for the same channel
On 30 March 2010 21:26, Rob Davis r...@davis-family.info wrote: I don't know if I immagined it, but is there a way to get VDR to use a secondary channel if the first channel is busy? To give an explanation, I have multiple ways a I can receive a channel, through ATSC, or through PVRINPUT or NTSC. I would like to know if there is a rollover system, if the first channel is busy, use the second, then third. It seems I saw something which suggested this was possible, but maybe not.. I think the current method is, one channel is tried on multiple devices matching the same source type. Channel 1 is dvb-s, tried on card-x to card-z of the same source type. I am not sure if there is a way to roll-over to another channel/different source type. How would this have to be handled? Will these channels be grouped together? At the moment I have lots of different channels for each source. I'm guessing we could have a transparency file.. T-0-567-4 P-0-40-1 P-0-64-1-64 So if T-0-567-4 is busy, use P-0-40-1, if that's busy use P-0-64-1-64 (Numbers taken from Streamdev, no idea if they're correct..) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using different types of device for the same channel
Theunis Potgieter wrote: It could be possible to do it in a similar way as Alternative channel -patch (http://www.vdr-wiki.de/wiki/index.php/Alternative_channel-patch) handles alternative channels. But since that patch only works for recording a channel it would need some work. Does this patch still work for 1.7.12 or above? My German is not good, but I can see it was applied to VDR 1.4.x.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using different types of device for the same channel
On 30/03/10 17:23, Timothy D. Lenz wrote: What plugin are you using for ntsc and how are you making the channels.conf for ntsc? I have an HVR-1800 and the wiki says it is supported , but I've heard elsewhere that it isn't. I don't think it is, as it's a dual mode card, so VDR will assume it's a DVB card and not allow it to work with IVTV.. I use a Hauppauge PVR-500 which I got on eBay.. I have a script to generate channels.conf for PVRInput and ATSC Clear Qam, which I'm about to publish.. Although it's a bit random.. I need to tidy it up a little first. It requires a kaffeine channels.dvb (generated by w_scan as w_scan won't generate a qam vdr channels.conf), then uses xmltv's output to find channel names and xmltv id's (for loadepg.pl), and then finds their channels from silicondusts qam lookup page using your zip code. Convoluted, but seems to work. Comcast are messing around weekly with our channels, which is what drove me to this.. On 3/30/2010 12:26 PM, Rob Davis wrote: I don't know if I immagined it, but is there a way to get VDR to use a secondary channel if the first channel is busy? To give an explanation, I have multiple ways a I can receive a channel, through ATSC, or through PVRINPUT or NTSC. I would like to know if there is a rollover system, if the first channel is busy, use the second, then third. It seems I saw something which suggested this was possible, but maybe not.. ___ 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 -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XBMC with vdr-1.6.0 ??
On 09/03/10 15:12, Simon Baxter wrote: - Original Message - From: scott sc...@waye.co.uk To: VDR Mailing List vdr@linuxtv.org Sent: Monday, March 08, 2010 9:45 PM Subject: Re: [vdr] XBMC with vdr-1.6.0 ?? One way thats been suggested before, and which I use, is to put xbmc and vdr-xine in a while loop inside a bash shell script and set up a button to stop vdr-xine, and a menu option in xbmc to close it down. If you search this thread you should find some info, if not I can post my stuff. -- Scott Thanks Scott. Yes please, would like to see how you've implemeted it. I found a number of threads and have achieved the following: * added a script (vdr.py) under the My Scripts which calls the xine frontend. But this flags an error Errors in system config or similar, launches xine but closes xbmc at the back end http://forum.xbmc.org/showthread.php?t=42205 * added a phantom button on the main menu, which I'd hoped would launch vdr-py (lower in the above thread). But this just crashes xmbc What I want to achieve is a main menu button which launches an external bash script, to launch xine, which keeps xbmc running in the background. I currently have mms running like this and it works really well. I then use the power button to kill xine (and turn off lirc), and fall back to mms. Thanks Simon This is the script I use. I call irexec as a window manager. I have two buttons, LiveTV which cycles between vdr-sxfe and xbmc and Video which cycles between vdr-sxfe and freevo. I also have a browser configured and huludesktop.. -- Rob Davis irexec.tgz Description: application/tar-gz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XBMC with vdr-1.6.0 ??
scott wrote: One way thats been suggested before, and which I use, is to put xbmc and vdr-xine in a while loop inside a bash shell script and set up a button to stop vdr-xine, and a menu option in xbmc to close it down. If you search this thread you should find some info, if not I can post my stuff. -- Scott On Mon, 8 Mar 2010 19:53:15 +1300, Simon Baxter linu...@nzbaxters.com wrote: Hi Has anyone got XBMC working with vdr-1.6.0? I want to run XBMC, but am not ready to move to a .ts file format yet. So I was thinking I'd just get XMBC to call a script and run vdr-xine (ie not integrate with streamdev etc). This should be easy yes? Any pointers or experience? Thanks Simon ___ 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 The pvr-testing2 version of xbmc works with 1.6.0 (or did three weeks ago) as long as you have a recent streamdev patched.. However, using irexec would work to change from vdr-sxfe and xbmc too. ___ 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] 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] [ANNOUNCE] VDR developer version 1.7.13
On 03/03/10 13:35, VDR User wrote: On Wed, Mar 3, 2010 at 10:47 AM, L. Hanisch d...@flensrocker.de wrote: On my first thought I considered to take 'A' for 'analog', but since there is something like ATSC (and I know nothing about it, if it's supported by vdr or is covered by dvbdevice or whatever), perhaps I should use another one? So I think it would be better to take *'V' = 'analog video'*, since pvrinput is basically an interface to v4l-devices. ATSC is a set of standards developed by the Advanced Television Systems Committee for digital television transmission. ATSC replaced much of the analog NTSC television system[1] in the United States[2][3] on June 12, 2009 and will replace NTSC by August 31, 2011 in Canada[4] and December 31, 2021 in Mexico. Yes, I think you should take ATSC into consideration unless you want to ignore North America. ;) Except ATSC is a subset of DVB.. At the moment ATSC is flagged as T, which I think it should be.. For people that don't really know, ATSC comes in two flavours (or flavors), Over the Air, and Clear Qam. Over the air is using a roof top antenna, like DVB-T, then we get Clear Qam, where you plugin the input from your cable company. By law all cable companies must provide clear (ie, non encoded) local channels. However, Comcast in our region has just released a Basic Digital package, which means we get about 60 channels now Clear Qam, including stuff you would have thought would be encoded (and is on Euro Sat). If you don't want to mess with Nagra-3, card readers, and such like, it's the best way to get VDR showing useful programming. Now, if only there was a channel scanner that could write a VDR style channels.conf with ATSC.. Just in case someone is searching archives, the best way to work out what you should have in your area is to look at the silicon dust website (the manufactorer of the the hdhomerun devices. These will show you (by zip) for OTA and Cable.. My zip code is here: http://www.silicondust.com/hdhomerun/lineup_web/US:61103#lineup_1635553 A channel scanner won't always find the info you need for Cable.. I had to manually insert several Vpids (which for my area were one less than the apid) and turn off auto update.. I then had to tell VDR they were type =2.. Maybe I'll do a Comcast-VDR howto sometime.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Announce] iStreamdev 0.3.7
I got it almost working except for the reencoding. Is there a way I can get some debug output to work out what's wrong..? Am running on Gentoo with vdr 1.7.12. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] analogtv plugin with HVR-1800
On 18/02/10 23:58, Timothy D. Lenz wrote: Ok, I was mainly interrested in adding the ntsc (analog) tuning. I think most if not all the ntsc channels left in our area are spanish, so not really interrested in watching them, more, in, I have the hardware, would be nice if it was usable. I have both these cards: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-1800 http://www.linuxtv.org/wiki/index.php/DViCO_FusionHDTV7_Dual_Express And I just noticed the second card is also listed as having analog tuning: http://www.fusionhdtv.co.kr/ENG/products/HDTV7DualExpress.aspx But according to this link, only the 1800 has linux support for analog: http://www.linuxtv.org/wiki/index.php/ATSC_PCIe_Cards With both cards in, I have 3 dvb adapters and all 3 have: demux0, dvr0, frontend0, net0 Hi Timothy, I was in the same position as you and found an inexpensive pvr500 on eBay. It's a nice card, and more importantly, doesn't interfere with the ATSC cards I have. I also now have a cable HD box connected up to it. PVRINPUT will change the channels on the box to the correct one and either select SVIDEO on the PVR500 or the HDPVR box and display it in HD. At quick glance, it looks like there are quite a few Hauppauge PVR devices listed on eBay at the moment. Just make sure it's an NTSC one. The first two I got were PAL (even though sold from Detroit). The guy didn't realise, in the end I sent them to a friend in Hungary. Rob -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Temporary VDR Support for Freevo (and pvr-hd support)..
This has probably been done before but... I normally use VDR for receiving ATSC and NTSC broadcasts as I can stream it around the house and use a Hauppauge MVP box in different rooms. However, I just got a nice Hauppauge PVR-HD which isn't (yet) supported by VDR. So I hacked a freevo a little to get it using VDR and the PVR-HD.. I did this initially about 4 years ago, but then ended up using VDR instead of Freevo. Anyway, this uses two seperate input mechanisms, so I copied an idea I found on the internet to allow a pvr_cmd into the video_groups structure. This is from my local_conf.py TV_VIDEO_GROUPS = [ VideoGroup(vdev='/dev/video0', adev=AUDIO_DEVICE, input_type='component', tuner_type='external', input_num=0, group_type='pvr-hd', desc='PVR-HD', vcr_cmd = 'cat /dev/video0 %(filename)s sleep %(seconds)s ; kill -9 $!;' ), VideoGroup(vdev='/dev/video0', adev=AUDIO_DEVICE, input_type='component', input_num=1, group_type='pvr-hd', desc='PVR-HD', vcr_cmd='cat /dev/video0 %(filename)s sleep %(seconds)s ; kill -9 $!;' ), VideoGroup(vdev='http://oac:3000/TS', adev=AUDIO_DEVICE, tuner_type=None, input_type='none', input_num=2, group_type='streamdev', desc='VDR', vcr_cmd='mencoder -oac copy -ovc copy -o %(filename)s http://oac:3000/TS/%(channel)s -endpos %(seconds)s;' ) ] TV_CHANNELS = [ ( '','Component','None', None, 1 ), ( 'I31497.labs-4.zap2it.com','906-WREXDT-13 WREXDT fcc',103, None, 2 ), ( 'I58646.labs-4.zap2it.com','919-CNN HD-CNNHD',919, None, 0 ) ] The top line is just using the pvr-hd without any channel change.. (For recording DVR recordings or On Demand things), the second will select channel 103 on VDR to watch, the third will change to channel 919 on my cable box and watch it using the hauppauge pvr-hd (Just watches /dev/video0).. I had to modify generic_record.py as it would send the channel number as a string instead of an integer when working out which group to select and not get the correct group. Then several changes have been made to mplayer.py in TV, which streams from VDR. The channel request is sent with a +1 at the end to select the first audio channel.. (The second can sometimes be spanish here).. Then I changed config.py and generic_record.py to allow the vcr_cmd based on Video_Group. Recordings are native .ts streams, either from the hauppauge (h264,ac3 audio) or the TS from VDR. Hope this helps someone (it goes with Freevo 1.9.0) I get better HD playback with mplayer and vdpau than with vdr-sxfe and xbmc isn't quite there yet.. freevovdrmods.tgz Description: application/compressed-tar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No Audio on ATSC Qam256 or OTA..
My Cable provider or VDR seems to mess up the audio pid regularly for
various channels. Is there a way (or patch) that I can keep the update
pids on, except for the apids? They move the vpids around about once a
month, so keeping vpid updating depending on sid is worthwhile,
otherwise I would turn off the updatepids line.
On Mon, 2009-12-14 at 00:03 -0500, Alex Lasnier wrote:
Klaus Schmidinger wrote:
On 02.08.2009 19:22, Alex Lasnier wrote:
Klaus Schmidinger wrote:
On 07/30/09 01:05, Rob Davis wrote:
Stile wrote:
On Tue, Jun 23, 2009 at 12:43 PM, Rob Davisr...@davis-family.info
wrote:
Alex Lasnier wrote:
Rob Davis wrote:
I have it normally connected to Comcast cable which should pipe
through
a bunch of FTV channels using QAM256. These I can see and hear in
kaffeine with AC97 audio. However, in VDR it appears to change the
pids
automatically so that the audio stops working. If I manually change
VDR
to not auto update and put the APID in then it squeeks rather than
works. However, streaming to mplayer using streamdev seems to work.
(It
does the same this with OTA channels too - although I can only get 4
with a portable antenna.)
ATSC uses only AC-3 audio, so the Apid should be 0 and the Dpid
needs to
be set appropriately. Since the sound squeaks, whatever value you
have
set for the Apid should be the Dpid.
For example,
WIFR-Wx:495000:M256:C:0:1984:0;Dpid:0:0:2:0:0:0
Perfect... Thanks
Is there a way to keep auto update on, but stop Comcast from sending
wrong pids? It keeps settings all audio options to 0 and some vpids
too?
The streamtype for those AC3 PIDs is 0x81. Adding this to pat.c will
add the digital PIDs correctly.
--- pat.c~2009-06-22 12:28:08.0 -0400
+++ pat.c2009-06-22 13:32:48.461538560 -0400
@@ -432,6 +432,9 @@
}
}
break;
+case 0x81: // AC3 DPIDs
+ Dpids[NumDpids++] = stream.getPid();
+ break;
//default: printf(PID: %5d %5d %2d %3d %3d\n,
pmt.getServiceId(), stream.getPid(), stream.getStreamType(),
pmt.getVersionNumber(), Channel-Number());//XXX
}
for (SI::Loop::Iterator it; (d =
(SI::CaDescriptor*)stream.streamDescriptors.getNext(it,
SI::CaDescriptorTag)); ) {
Perfect. I wonder if this could go in the atscepg patch?
Can you try if this also works if you insert the line
case 0x81: // AC3 DPIDs
after the line
//XXX case 8: // STREAMTYPE_13818_DSMCC
instead? I'm asking because I'd like to see whether there are
also language descriptors available...
Klaus
Yes, language descriptors are present. However, ATSC also uses 0x81 as
the AC3 descriptor tag. So we need another
case 0x81:
after
case SI::AC3DescriptorTag:
In case this is still current, can you please send me a (tested) patch?
Klaus
Sure, please see the attached patch.
plain text document attachment (vdr-1.7.10-atsc.diff)
diff -ur vdr-1.7.10.orig/dvbdevice.c vdr-1.7.10/dvbdevice.c
--- vdr-1.7.10.orig/dvbdevice.c 2009-06-06 07:17:20.0 -0400
+++ vdr-1.7.10/dvbdevice.c2009-11-22 13:26:57.0 -0500
@@ -319,6 +319,16 @@
tuneTimeout = DVBT_TUNE_TIMEOUT;
lockTimeout = DVBT_LOCK_TIMEOUT;
}
+ else if (frontendType == SYS_ATSC) {
+ // ATSC
+ SETCMD(DTV_DELIVERY_SYSTEM, frontendType);
+ SETCMD(DTV_FREQUENCY, FrequencyToHz(channel.Frequency()));
+ SETCMD(DTV_INVERSION, channel.Inversion());
+ SETCMD(DTV_MODULATION, channel.Modulation());
+
+ tuneTimeout = DVBT_TUNE_TIMEOUT;
+ lockTimeout = DVBT_LOCK_TIMEOUT;
+ }
else {
esyslog(ERROR: attempt to set channel with unknown DVB frontend type);
return false;
@@ -904,7 +914,7 @@
return type == cSource::stNone
|| type == cSource::stCable (frontendType == SYS_DVBC_ANNEX_AC ||
frontendType == SYS_DVBC_ANNEX_B)
|| type == cSource::stSat(frontendType == SYS_DVBS ||
frontendType == SYS_DVBS2)
- || type == cSource::stTerr (frontendType == SYS_DVBT);
+ || type == cSource::stTerr (frontendType == SYS_DVBT ||
frontendType == SYS_ATSC);
}
bool cDvbDevice::ProvidesTransponder(const cChannel *Channel) const
diff -ur vdr-1.7.10.orig/pat.c vdr-1.7.10/pat.c
--- vdr-1.7.10.orig/pat.c 2009-08-16 11:01:03.0 -0400
+++ vdr-1.7.10/pat.c 2009-11-22 13:31:37.0 -0500
@@ -389,6 +389,7 @@
break;
case 5: // STREAMTYPE_13818_PRIVATE
case 6: // STREAMTYPE_13818_PES_PRIVATE
+ case 0x81: // ATSC AC-3
//XXX case 8: // STREAMTYPE_13818_DSMCC
{
int dpid
[vdr] H264 syncearly patch
I am in the process of moving from 1.6.0 to 1.7.12 to test the pvrinput plug with a Hauppauge-PVR-HD. With 1.6.0 and the h264-syncearly patch I got a nice picture but no audio.. With 1.7.12 I can get audio but no picture. I thought h264 support was built in already to 1.7.12, but I maybe wrong. If not, where can I find an up to date patch for this? The old 1.7.0-h264-syncearly patch doesn't seem to work cleanly.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hauppauge PVR-HD and pvrinput plugin (was: Re: Hauppauge PVR-HD and IPTV plugin)
On Wed, 2010-02-10 at 11:18 +0200, Rolf Ahrenberg wrote:
On Tue, 9 Feb 2010, L. Hanisch wrote:
I received your sample and it looks like a valid TS with PAT, PMT and PCR,
so the plugin has nothing else to do as to pass it through to the vdr
(hopefully).
In the meanwhile, one could also try out the IPTV plugin without any
ffmpeg hassle by using a script that tunes the device and then simply:
cat /dev/video0 | nc -u -p ${PORT} 127.0.0.1
Most of this is extra debug output, but I've never used the nc command.
The port number looks to be the same as ffmpeg would use.. The only
thing that may be different is there is no packet size specified..
Getting new URL
/dev/video0
Change Channel to 951 on Cable Box
starting with node: 1
node 1: vendor_id = 0x24a0 model_id = 0xea05
AV/C Command: 951 = Op1=0x00487C29 Op2=0x00487C25 Op3=0x00487C21
Streamsvideo.sh PID is 32604
Streamdev Plugin 951 /dev/video0
nc -u -p 4321 127.0.0.1
no port[s] to connect to
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Hauppauge PVR-HD and IPTV plugin
Hi, I have a Hauppauge PVR-HD which works but creating an h264 ts stream from a set HD component inputs and does quite a nice job of it. The ts stream is available on /dev/video0 and a simple cat /dev/video0 file.ts will create a watchable high quality dump.. I have got this working with freevo (after a little hacking) but would prefer to get the input into vdr as I can then watch it around the house through streaming. Using vdr-iptv I can get some of the way, but not all of it.. Playing around with different options I get either jerky video or ffmpeg just stops transcoding after a few seconds, and I'm not sure why... I can put a 2 minute ts stream somewhere if it would help but I think it will decode a file before decoding from /dev/video0 Hauppuage-test;IPTV:1000:IPTV|S0P0|EXT|hauppauge.sh|951:P:0:256:257:0:0:1000:1:1:0 more /tmp/iptvstream Script started 951 4321 Getting new URL /dev/video0 Change Channel to 951 on Cable Box starting with node: 1 node 1: vendor_id = 0x24a0 model_id = 0xea05 AV/C Command: 951 = Op1=0x00487C29 Op2=0x00487C25 Op3=0x00487C21 Streamsvideo.sh PID is 14632 Streamdev Plugin 951 /dev/video0 pid of ffmpeg.streamdev 14639 14632 FFmpeg version SVN-r21686, Copyright (c) 2000-2010 Fabrice Bellard, et al. built on Feb 7 2010 22:27:31 with gcc 4.3.3 configuration: --prefix=/usr --libdir=/usr/lib --shlibdir=/usr/lib --mandir=/usr/share/man --enable-static --enable-shared --cc=i686-pc-linux-gnu-gcc --d isable-debug --disable-ffplay --enable-libx264 --enable-libxvid --disable-indev=oss --disable-indev=jack --disable-outdev=oss --enable-x11grab --enable-pth reads --disable-altivec --cpu=athlon-fx --enable-gpl --enable-version3 --enable-postproc --enable-avfilter --enable-avfilter-lavf --disable-stripping --ena ble-hardcoded-tables --disable-doc libavutil 50. 9. 0 / 50. 9. 0 libavcodec52.52. 0 / 52.52. 0 libavformat 52.51. 0 / 52.51. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter1.17. 0 / 1.17. 0 libswscale 0.10. 0 / 0.10. 0 libpostproc 51. 2. 0 / 51. 2. 0 [mpegts @ 0x807a3a0]max_analyze_duration reached [mpegts @ 0x807a3a0]Estimating duration from bitrate, this may be inaccurate Seems stream 0 codec frame rate differs from container frame rate: 119.88 (12/1001) - 59.94 (6/1001) Input #0, mpegts, from '/dev/video0': Duration: N/A, start: 0.387044, bitrate: 169 kb/s Program 1 Stream #0.0[0x1011]: Video: h264, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 59.92 fps, 59.94 tbr, 90k tbn, 119.88 tbc Stream #0.1[0x1100]: Audio: aac, 48000 Hz, 2 channels, s16, 169 kb/s [mpegts @ 0x85f2a80]calculated bitrate 2293687 bps, muxrate 2293687 bps, sdt every 762, pat/pmt every 152 pkts Output #0, mpegts, to 'udp://127.0.0.1:4321?pkt_size=32712': Stream #0.0, 1/9: Video: mpeg2video, yuv420p, 1280x720 [PAR 1:1 DAR 16:9], 1/25, q=2-31, 2000 kb/s, 90k tbn, 25 tbc Stream #0.1, 1/9: Audio: mp2, 48000 Hz, 2 channels, s16, 192 kb/s Stream mapping: Stream #0.0 - #0.0 Stream #0.1 - #0.1 Press [q] to stop encoding [h264 @ 0x808eb00]no picture [mpegts @ 0x85f2a80]dts pcr, TS is invalidme=1.25 bitrate=3297.2kbits/s dup=0 drop=42 frame= 146 fps= 29 q=12.2 size=1843kB time=5.76 bitrate=2645.8kbits/s dup=0 drop=178 frame= 178 fps= 29 q=11.7 size=2178kB time=7.03 bitrate=2537.3kbits/s dup=0 drop=244 Then it just freezes... Any ideas? hauppauge.sh Description: Bourne shell script ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hauppauge PVR-HD and IPTV plugin
On 08/02/10 12:58, L. Hanisch wrote: Hi, Am 08.02.2010 16:53, schrieb Rob Davis: Hi, I have a Hauppauge PVR-HD which works but creating an h264 ts stream from a set HD component inputs and does quite a nice job of it. The ts stream is available on /dev/video0 and a simple cat /dev/video0 file.ts will create a watchable high quality dump.. Is it a cx18-based card? There a plans to integrate support for the native TS-capability of those cards in the pvrinput-plugin, but it will take some time. If you mind you can send me off-list a sample video (up to 4MB with the cat-method). I'm just working on repacking the program stream of ivtv-based cards with valid PAT, PMT and PCR, a pass through of a valid TS shouldn't be that hard. But I don't promise anything since I haven't such a card. Particulary if its controls are too different from the ivtv-ones. regards, Lars. I spoke to Marin a little about this.. In terms of controls.. There are none that need worrying about... It doesn't have a tuner. It would be useful to have a way to control an external channel changer (which Martin nicely put in for my other pvr-500 card (for SD channels off the cable box).. The linux module is pvrhd. Once loaded, along comes a /dev/video0 device. A cat or mplayer command on this work well. The ts stream is dependant on what is fed to it. Ie, if your source is 1080i, then you'll get a 1080i stream, if 720p then that's what you get.. There was a quick sample on the internet, but I can also manually record something for you if you want it.. Just not sure where to leave it.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Hauppauge PVR-HD and IPTV plugin
On 08/02/10 12:35, Rolf Ahrenberg wrote: On Mon, 8 Feb 2010, Rob Davis wrote: [h264 @ 0x808eb00]no picture [mpegts @ 0x85f2a80]dts pcr, TS is invalid Then it just freezes... Does the ffmpeg command work on the commandline? Might be related to the ffmpeg revision... Anyway, you could give a try for the FILE input protocol as it should be quite perfect for your TS source. After a little investigation, it looks like it's an issue of ffmpeg reading directly off the /dev/video0 device. It looks like it gets ahead of itself. If I cat /dev/video0 to a file, sleep 5s and then ffmpeg decode the file, it almost works.. I tried to put /dev/video0 as a file but couldn't get anything out of VDR... Saying that I'm pretty sure I removed the h264 VDR patch since coming to the US. I'm running VDR 1.6 instead of 1.7 as I know what I'm doing better with it in Gentoo.. I will record a 5 min clip and put it somewhere.. Would there be a way to watch a file and call a script? That way I can execute an external channel changer depending on parameter and then dump the output to a fifo.. As an aside, xine-vdpau (xineliboutput) didn't want to play the stream (albeit stuttering horribly) full screen - it looked like a 4:3 picture when it should have been 16:9, although xine-xv didn't have a problem.. -- Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new support
abbe normal ha scritto: rob yes they do have there own channel scanner built into there software and it produces a simple layout of info... i will attach a txt file of that output... so you can have a look at it... thanks guys for all the input think this will work and be smooth working with all your help and input... What do you use to stream it to mplayer or vlc? Looks like the channel scanner has done the right thing. You can check what channels you should get using the hdhomerun website.. For instance for my zip, I get this http://www.silicondust.com/hdhomerun/lineup_web/US:61110#lineup_1173095 Also looks like you're using ATSC over the air intead of Cable.. Is there enough bandwidth to stream an HD mpeg2 stream on your network? I had trouble on mine when I used vdr-sxfe on a seperate box to the server. I worked, but I couldn't access the internet as all my internal bandwidth was gone.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new support
On 21/01/10 04:20, Rolf Ahrenberg wrote: On Thu, 21 Jan 2010, Nicolas Huillard wrote: For those who don't spare some time digging on the website: * this is an Ethernet device: antenna in (single, dual), ethernet out * no storage inside the box * they provide an LGPL library libhdhomerun: include hdhomerun.h and/or hdhomerun_device.h to use the top level API I'd make another 'pseudo' DVB input device plugin for this based on the current IPTV plugin. A quick look at the API reveals that you could dynamically add necessary number of provided tuners as done in IPTV plugin. You could also implement a channel scan functionality as done in IPTV plugin. I quess its' UDP/RTP transport is already compatible with the one implemented in IPTV plugin. The only requirement from core VDR would be the pluginparam patch (or similar) functionality. My thoughts exactly. I am pretty sure this would work as is with vdr-iptv. I had a quick look at some of the US versions and it looks interesting. I got vdr-iptv working with an external cable box and a pvr card, so using a script we could send off whatever card was necessary to change channels and bring in the input. The downside would probably be a long channel change time. More native support could be good.. However, I wonder what the advantage would be to having this over an internal pci dvb card or even a usb one? The pci card is surely cheaper, and the functionality is already there in VDR? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new support
On 21/01/10 15:39, abbe normal wrote: hello guys yes you are right a pci or usb device may be cheaper but in my case at 99 dollars each for usb and 108 dollars for pci didnt make since but in the thought of less pci buses on systems now was a big factor... then you have to double that cost as a single tuner will only allow one channel on that box so recording another is not possible... now being able to use this at any system in the network was the main idea... all this aside i do have the iptv plugin running but dont have it figured out yet... but if this could be add to it and support was added in the plugin think it would be a nice add on... having a channel scanner then a script that would convert that info would be nice to make things simpler... as far as Klaus adding this to vdr id say no when theres a plugin that it could be add to... make more since to do it as a plugin with native support for it... but as i dont even know how to write a plugin im lost at this point... this is why im asking here in hopes the guys that have or work on the plugins could help in pointing me in the right direction... i can then at least try to make it work... most of the guys who know me know i dont know a lot but i dont give up easy if it can be done... so im will to help if im told what and how too... i can at least try... Can you get the channel scan done from something else and post a mplayer or vlc command for each channel. Once you've done that I'll knock you up a quick iptv script.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] IPTV plugin stuttering when decoding ATSC streams with VDR to convert ac-3 to mp3 on the fly
I have VDR working in the US with ATSC. Previously I had it working in
Europe on Satellite. With VDR I have several Hauppauge VOMP boxes which
act as remote front ends. Unfortunetely these do not work with AC-3
audio. Using streamdev and iptv plugins with ffmpeg I want to reencode
the ATSC streams to extra channels in VDR in order to watch them on the
vomp boxes.
I have this almost working. I can see something on the TV but I get
quite a lot of stuttering and breakup of the picture. Audio seems to
work, in that I don't get popping. What am I missing?
When the channel is selected, the IPTV plugin calls a script which
streams from streamdev the TS stream (using mplayer -dumpstream) which
uses a fifo to pipe this into ffmpeg, which writes it to udp, where VDR
picks it up again.
The exciting bits of the script are:
mkfifo $fifo
mplayer $mplayeropts -cache 8192 $URL -dumpstream -dumpfile $fifo
${LOG}
MPID=${!}
ffmpeg.streamdev -v 1 \
-i $fifo -debug 0 \
-f mpegts -vcodec copy \
-acodec ${ACODEC} -ac 2 -ab ${ABITRATE}k -ar 48000 -async $fr \
udp://127.0.0.1:${PORT}?pkt_size=16356
acodec is mp2
abitrate is 192
fr is 29
fifo is dynamically creates
url is http://myserver:3000/TS/103+1
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] lirc-0.8.6 moved socket to /var/run/lirc/lircd
Ian Bates wrote: On 29 Sep 2009, at 20:54, Matthias Schwarzott wrote: On Dienstag, 29. September 2009, Helmut Auer wrote: Hi list! lirc starting from version 0.8.6, does use the socket /var/run/lirc/lircd instead of /dev/lircd, so all apps not using liblirc_client need to be changed. Else IR will not work in VDR. There are two possibilities: 1. Shell code to check which of the two sockets do exist and adding relevant command-line-parameter to vdr (--lirc=/var/run/lirc/lircd). 2. Patching VDR to check both pathes and using the existing one. 3. Change lirc to use /dev/lircd In gen2vdr ( =gentoo ) I set: LIRCD_OPTS=-o /dev/lircd in /etc/conf.d/lircd :) Nice to know that it can be changed, but I have a big BUT: Does irw and all other apps using liblirc_client then still work? I doubt, as they have the new name compiled in. I confirm irw does not work when using the '-o wherever' switch with lirc-0.8.6 (cvs from about a month ago). I guessed but was not sure it had something to do with a compiled-in patch. I came across this issue when playing with an xbmc-pvr install. While debugging the install my work around was as 1. above. Ian. Me too. Although without realising what the problem was at that point I did a symbolic link from /var/run/lirc/lircd to /dev/lircd ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] IPTV: Problems with Base port number
Rolf Ahrenberg wrote: On Fri, 18 Sep 2009, Rob Davis wrote: I am trying to get BBC Radio streams to work. However, I can't work out how to get the IPTV plugin to chage the base port.. The base port is a global setting that can be changed in plugin's setup: iptv.ExtProtocolBasePort=4321 However, if you create more than one IPTV device, the device's base port is the one defined in setup plus device's enumeration: Device 0: 4321 Device 1: 4322 These should be documented (somehow) in plugin's README. mplayer and ffmpeg are both created. (as per the example script) with a different fifo each, but VDR is sending the same PORT to all streams, so if I change channel I get the two streams mixed together. If you're having only one IPTV device, the script should be killed (and mplayer/ffmpeg as well) before the new one is executed with new channel specific parameters when zapping. There were some protocol specific bugs in the channel switching, so you should try the latest public 0.3.0 release, if not already done. How do I create more than one IPTV device? I assumed that it was automatic? I am using 0.3.0. When vdr switches off the channel how is the channel / stream closed? When working, these streams will be accessed by streamdev/xbmc and vomp. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] IPTV: Problems with Base port number
Rolf Ahrenberg wrote: On Fri, 18 Sep 2009, Rob Davis wrote: How do I create more than one IPTV device? I assumed that it was automatic? I am using 0.3.0. -d num, --devices=number number of devices to be created -P 'iptv -d 2' When vdr switches off the channel how is the channel / stream closed? A SIGINT is signaled to the external script. If the script isn't terminated in 2 seconds, a SIGKILL is signaled. This is a blocking mechanism, so you shouldn't be able to run two scripts at the same time within a device. I'm suspecting, that your mplayer/ffmpeg processes won't get killed although the external script does. Ok, thanks, I think I have it working now.. Does it automatically use other devices as it sees fit, or do I need to code that into channels.conf? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] IPTV: Problems with Base port number
Rolf Ahrenberg wrote: On Fri, 18 Sep 2009, Rob Davis wrote: Does it automatically use other devices as it sees fit, or do I need to code that into channels.conf? As you have different frequencies for IPTV channels, VDR should always pick up automatically a free IPTV device if available. Hi Rofa, thanks for all the help. It doesn't seem too. I now have the script killing ffmpeg when it closes, but if I try two channels at the same time of different frequencies they come with the same port. I have also applied the pvrinput patch as well as the iptv patch. I don't know if this will mess things up. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No Audio on ATSC Qam256 or OTA..
Stile wrote:
On Tue, Jun 23, 2009 at 12:43 PM, Rob Davisr...@davis-family.info wrote:
Alex Lasnier wrote:
Rob Davis wrote:
I have it normally connected to Comcast cable which should pipe through
a bunch of FTV channels using QAM256. These I can see and hear in
kaffeine with AC97 audio. However, in VDR it appears to change the pids
automatically so that the audio stops working. If I manually change VDR
to not auto update and put the APID in then it squeeks rather than
works. However, streaming to mplayer using streamdev seems to work. (It
does the same this with OTA channels too - although I can only get 4
with a portable antenna.)
ATSC uses only AC-3 audio, so the Apid should be 0 and the Dpid needs to
be set appropriately. Since the sound squeaks, whatever value you have
set for the Apid should be the Dpid.
For example,
WIFR-Wx:495000:M256:C:0:1984:0;Dpid:0:0:2:0:0:0
Perfect... Thanks
Is there a way to keep auto update on, but stop Comcast from sending
wrong pids? It keeps settings all audio options to 0 and some vpids too?
The streamtype for those AC3 PIDs is 0x81. Adding this to pat.c will
add the digital PIDs correctly.
--- pat.c~ 2009-06-22 12:28:08.0 -0400
+++ pat.c 2009-06-22 13:32:48.461538560 -0400
@@ -432,6 +432,9 @@
}
}
break;
+case 0x81: // AC3 DPIDs
+ Dpids[NumDpids++] = stream.getPid();
+ break;
//default: printf(PID: %5d %5d %2d %3d %3d\n,
pmt.getServiceId(), stream.getPid(), stream.getStreamType(),
pmt.getVersionNumber(), Channel-Number());//XXX
}
for (SI::Loop::Iterator it; (d =
(SI::CaDescriptor*)stream.streamDescriptors.getNext(it,
SI::CaDescriptorTag)); ) {
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Perfect. I wonder if this could go in the atscepg patch?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Analog TV plugin
I am trying to see if this still works, however, the only copies I can find are for older versions of VDR. I'm running 1.6 (almost Ubuntu) at the moment, but can't get the version available for download to patch against this. Unfortunetely, where I'm staying only has Cable which broadcasts in analog, otherwise I can get the local channels only (mostly in HD). The usb dongle thing I picked up appears to be able to do NTSC and ATSC. TvTime works with it as does VDR now. I suppose I can do a a whole bunch of mplayer playlists and watch it using those, but I would like to setup the EPG against the channels. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No Audio on ATSC Qam256 or OTA..
Alex Lasnier wrote: Rob Davis wrote: I have it normally connected to Comcast cable which should pipe through a bunch of FTV channels using QAM256. These I can see and hear in kaffeine with AC97 audio. However, in VDR it appears to change the pids automatically so that the audio stops working. If I manually change VDR to not auto update and put the APID in then it squeeks rather than works. However, streaming to mplayer using streamdev seems to work. (It does the same this with OTA channels too - although I can only get 4 with a portable antenna.) ATSC uses only AC-3 audio, so the Apid should be 0 and the Dpid needs to be set appropriately. Since the sound squeaks, whatever value you have set for the Apid should be the Dpid. For example, WIFR-Wx:495000:M256:C:0:1984:0;Dpid:0:0:2:0:0:0 Perfect... Thanks Is there a way to keep auto update on, but stop Comcast from sending wrong pids? It keeps settings all audio options to 0 and some vpids too? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] No Audio on ATSC Qam256 or OTA..
I've just moved to the US from Europe and trying to get my head around ATSC. I have a Hauppauge HVR950q which works in Windoze and Linux (With Kaffeine) and almost with VDR (my preferred platform). I have it normally connected to Comcast cable which should pipe through a bunch of FTV channels using QAM256. These I can see and hear in kaffeine with AC97 audio. However, in VDR it appears to change the pids automatically so that the audio stops working. If I manually change VDR to not auto update and put the APID in then it squeeks rather than works. However, streaming to mplayer using streamdev seems to work. (It does the same this with OTA channels too - although I can only get 4 with a portable antenna.) I am using Ubuntu's VDR source 1.6.0 something or other, but patched with the ATSC patch. I had a really hard time trying to work out the channels.conf file, and in the end settled for something like: WIFR-Wx�;(null):495000:M256:C:0:1984:0:0:0:2:0:0:0 WQRF-DT�;(null):495000:M256:C:0:2048:0:0:0:3:0:0:0 WIFR-HD�;(null):495000:M256:C:0:2112:0:0:0:1:0:0:0 This is after VDR has eaten the audio pid away. Normally this is one number higher than the vpid. So for WIFR 1985, WQRF 2049 etc. I'm willing to believe I've cocked it up as nothing I had would automatically scan the QAM channels. In the end I used scan and it added VDR Doesn't support ATSC yet instead of M256:C:0. Thanks guys... Fairly soon my shipping will arrive from Italy with my main server, sat cards and Hauppauge MVP's to stick around the house. I wonder what could possibly go wrong? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] BBC HD and vdpau
Luca Olivetti wrote: En/na Morfsta ha escrit: If you turn Dolby Digital off in the VDR DVB menu then it will play only the MPA track and the picture will then work fine in VDR. I tried activating dolby digital (I usually have it set to no), and I don't have a problem with the video (as long as I use xxmc, vdpau, as I said previously, doesn't work). Of course I don't hear anything (I don't have 5.1 hardware), and if I select the normal audio track it skips from time to time, but the video itself is fine. Bye I tried the turning off dolby digital and I get the Narrative track ok, but I still get corruption on vdpau. It's like vertical banding, reminiscent of trying to copy a video with macrovision. My pc doesn't display it well enough on xxmc, (I have an 8400 which should be fast enough with a quad core phenom, but it doesn't want to do it..) I am using a VGA output, maybe it will work if I used a DVI one? Maybe it is HDCP protection? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] BBC HD and vdpau
I'm in a half way stage with VDR and h264. I didn't want the multipro drivers, but wanted to get a few HD channels working with vdpau. I have VDR working with BBC HD almost, and Sky HD +24 and a few others, however, BBC doesn't seem to display properly, as well as having problems with the audio selection. It looks like it has macrovision protection or something like that.. (Using vdr-sxfe and xine-libs with h264 support). As I said, other channels seem to work. I would try ITV HD but there's never anything on... Any tips? (In xxmc it sort of works, but jumps as it doesn't seem to have the guts to play the source.) VDR 1.6.0 with h264 patch. BBC HD works with streamdev :3000/TS/channel info.. on vlc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR-Live plugin
How do you use this from the internet? I have got it working (via Gentoo) on my lan, but I wan't to use it with the extern function of streamdev using my dynamic dns name. I have opened the port but it keeps asking for the username and password (which work at home). I can't work out what config options I might need to set. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR-Live plugin
Heinrich Langos ha scritto: While you are on your local network go to the live plugins web interface. Select Setup from the top menue Activate Use Authentication. Now you should see three more input fields. Two to change your login credentials and one to set a Local net from which no login will be required. I strongly recommend that you use the login. Otherwise everybody from the internet can access your vdr. (And problably 0wn your whole network. As I understand it the vdr code has hardly been audited for security and due to the plugin architecture a buffer overflow in one plugin would compromises the vdr process that (depending on your setup) may even run as root). If you insist on getting hacked you can set the Local net to something like 0.0.0.0/0 This would disable the password question, no matter where you come from. //www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Thanks Henrick, On further investigation I have sorted it out. In my firewall I'd mistyped the portforward, so it was arriving at vdradmin instead, which uses a different password. I have it working. However, for the next version, is there a way to select two different streamdev profiles quickly. When I am home I would like to select streamdev TS, but when away extern? Also, is there a way to allow a change of language in the vlc plugin, or a way to serve up a file with the url in, for instance stream.m3u with the url in it like a playlist, a bit like a dreambox. This would allow the vlc interface to select language etc. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Italy Transmission: DVB-S, DVB-T (We have DVB-S2 too but I watch that on a Dreambox) Encoding: MPEG-2 for SD (3 sats - about 4000 channels), (40 for DVB-T mostly rubbish). -- Latest news on http://www.stpixels.com/view_blog.cgi?user=66685 Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ATSC a good primers guide? (Moving from Italy to the USwith my VDR setup)
- Original Message - From: Joerg Bornkessel m...@websitec.de To: VDR Mailing List vdr@linuxtv.org Sent: Sunday, January 18, 2009 2:24 PM Subject: Re: [vdr] ATSC a good primers guide? (Moving from Italy to the USwith my VDR setup) So, would the DVB-T card just work with ATSC or is it fundamentally different (like DVB-C is different to DVB-S). In which case should I get a USB ATSC dongle or two? For Cabel and Terr you need a patched VDR Also you need then a plugin to get the epg data over atsc Take a closer look here -- http://www.fepg.org/ If you use VDR on Gentoo, yust enable use-flag atsc Ohh, I have gentoo, so that's good. Do you know if I will need a new ATSC card or is a DVB-T card similar enough that it'll work? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ATSC a good primers guide? (Moving from Italy to the US with my VDR setup)
I'm looking at moving from Italy to the US in the summer and am trying to spend my time (while not highly preoccupied about health insurance, jobs, houses, shipping etc) trying to think through taking my VDR setup and Dreambox over to the US. I currently have a couple of Hauppauge DVB-S cards (a Nexus and a Nova) and a Hauppauge DVB-T card in the setup for digital terrestrial. I am wondering in the US if I should go with ATSC or Dish/Direct TV (or both). I'm aiming for Rockford, Illinois which has ATSC coverage. I have three vomp boxes hanging off the VDR server which I was planning to take with me. These currently connect with RGB Scart to my TV's. Then the dreambox 800 connects with HDMI. So, would the DVB-T card just work with ATSC or is it fundamentally different (like DVB-C is different to DVB-S). In which case should I get a USB ATSC dongle or two? How do you connect an RGB Vomp box to an American TV or should I get a couple of Scarted LCD's before I leave here? Is anything available with Scart in the US? My cousin says that a hotel near here is selling off it's 20 TV's for $25 each, is it worth it (I'm guessing thanks to the digital switch off)? If I go down the sat route, can I just stick a dish or direct tv card in the phoenix reader I use for Sky Italia and decode it with vdr-sc / CCcam? (Whatever happen I would be wanting a valid sub to watch what I want to.) The dreambox should display HD, as long as I have the rights to view it? Should I stick with Sat with that or go on the search for an ATSC card? Am I just overcomplicating life? Would I be better off just buying some ATSC set top boxes when I get there. Vomp/VDR was the only satisfying way of watching UK tv in Italy in any quality for us. Thanks for your ideas.. -- Latest news on http://www.stpixels.com/view_blog.cgi?user=66685 Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Plugins DVD and Dolby Digital
NIVAL Michaël wrote: Hi, With VDR-1.5.10 and cvs version plugins DVD, it is not possible to have audio. The syslog shows: [4223] switching to pre 1.3.19 Dolby Digital compatibility mode UseDolbyDigital is disabled. The solution I have for the moment is to apply the patch that I put in attachment. Is this still an issue on 1.6.0? I have just got a FF card working and thought I'd try DVD playback for the first time ever, however, I have no audio on the FF Scart output. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput and ubuntu 7.10 (Gutsy)
I have installed 1.5.17 (i think) of vdr (from the experimental apt repository) however I can't get xineliboutput compiled as it's complaining that it can't find a valid libxine. It looks like the dependencies are quite specific in what they want. Will try to provide more info tomorrow when I'm at work and can check better, but has anyone else resolved this? -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Linking a dreambox to VDR using steamdev server
Rolf Ahrenberg wrote: On Wed, 28 Nov 2007, Rob Davis wrote: I have given this a go in Gentoo and it had 0.3 of vdr-iptv, unfortuntely it didn't seem to display anything on the dreambox, although it did activate the stream.ts command, so something was going on. DREAM;IPTV:4:IPTV|HTTP|192.168.2.7|31344:P:0:0:0:0:0:1:0:0:0 Did you enable the Sid scanner in plugin's setup and is your vdr configured to update pids? (I was using zero pids as an example only). After that you should have changing pids messages in vdr's log. However, if those messages are missing, the plugin and vdr cannot parse necessary information from Dreambox's TS stream and you should add used video and audio (and other) pids into the channels.conf entry. I also noticed the VDR patch appears to break vompserver, so I only get about 8 channels displayed, which is a bigger issue to me as I have three hauppauge mvp's around the house to watch tv. The patch doesn't change any current interfaces - it just adds a few new methods, so it shouldn't break compatibility with any plugin. You could also try Udo's streamplayer plugin. Mybad, I had to recompile vompserver, then it worked. Streamplayer works well, but won't transmit to Vomp, as vomp is expecting a channel list. Now I have vomp working with iptv installed I will play a little more. Maybe it doesn't work with xineliboutput. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Linking a dreambox to VDR using steamdev server
Rob Davis wrote: Mybad, I had to recompile vompserver, then it worked. Streamplayer works well, but won't transmit to Vomp, as vomp is expecting a channel list. Now I have vomp working with iptv installed I will play a little more. Maybe it doesn't work with xineliboutput. Sorry to post to my own post, but I got it working by reducing the buffer from 2mb to 1mb. Am a happy man now. Thanks. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Linking a dreambox to VDR using steamdev server
Rob Davis wrote: Rob Davis wrote: Sorry to post to my own post, but I got it working by reducing the buffer from 2mb to 1mb. Am a happy man now. Thanks. OOops, spoke too soon.. I have discovered a problem with coded channels. If I am watching something which the dreambox can decode using a local card it won't then display it on VDR as it's updating all it's pids etc, including CA, VDR then tries to work out how to decode it, but it's already decoded, so doesn't display anything. Is there a way to optionally block the CA field from updating? (The 31344 port is just a stream of what is being watched on the DM at the time - which is good enough for what we want and saves having to duplicate the entire channel list.) -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Linking a dreambox to VDR using steamdev server
Rolf Ahrenberg wrote: On Tue, 27 Nov 2007, Rob Davis wrote: A typical request from something like vlc to the dreambox would be: http://192.168.2.7:31339/0,0105,0205,0285,0299,1ffe If the channel pids are quite static, you could use the IPTV plugin simply with the following channels.conf entry: Dreambox;IPTV:1:IPTV|HTTP|192.168.2.7/0,0105,0205,0299,1ffe|31339:P:0:0:0:0:0:0:0:0:0 Or you could parse the necessary pids via a shell script and use the plugins's EXT protocol with vlc/netcat/... to achieve the same. Thanks Rolf, I have given this a go in Gentoo and it had 0.3 of vdr-iptv, unfortuntely it didn't seem to display anything on the dreambox, although it did activate the stream.ts command, so something was going on. In the end I used DREAM;IPTV:4:IPTV|HTTP|192.168.2.7|31344:P:0:0:0:0:0:1:0:0:0 Which I had to create using the plugin menu, but that didn't display anything. Although mplayer http://192.168.2.7:31344 displays the current channel quite happily. I also noticed the VDR patch appears to break vompserver, so I only get about 8 channels displayed, which is a bigger issue to me as I have three hauppauge mvp's around the house to watch tv. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Linking a dreambox to VDR using steamdev server
I have two sat cables coming into the lounge, both with the same sats. In the wall conduit are three more sat cables going to the neighbours below (we live in an apartment) and there is no way of adding more cables into the conduits. We have a dreambox which works quite well in the lounge and a VDR server with two SkyStar's. Is there any merit in tweaking streamdev to connect to the dreambox and request a stream from it when it can't get it off it's own sat card? I would like to use the dreambox when it's not needed by VDR, but otherwise slave it to VDR. It handles my Disecq better than VDR and is faster when using my subscription card. I think a way to do it is to create a quick way of reading a dreambox services file and understanding it like a VDR channels.list and then request the stream (via HTTP) from the dreambox in much the same way as one VDR server does to another. In practical terms, a dreambox would need to receive two http requests, the first would change the channel, the second would request the stream. A typical request from something like vlc to the dreambox would be: http://192.168.2.7:31339/0,0105,0205,0285,0299,1ffe I'm not that familiar with C but I can hack most languages reasonably if someone can point me in the right direction. I don't think it would take a lot to get this going, but who knows. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 2 dvb-s cards with different feeds
I would like to know if its possible to have two dvb-s cards connected to different disecq setups? For example, for card 1 to have: 1 - HotBird 2 - Astra 19 3 - Astra 28 Whereas, card 2 would have: 1 - Hotbird 2 - Astra 19 Without it all going pear shaped? If so, how do you reflect that in the setup? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Output methods and WSS
I agree, I have 3 Mvp's, and the setup works well, although the latest boxes create problems if they're reset too quickly. There are some patches in the latest CVS which fix the problem if VDR can't play a stream (without the patch, VOMP just appears to go to sleep). My main desire would be the ability to change audio language. At the moment I have to manually hack the channels.conf file to put my preferred language first and then set VDR to not update pids. The picture quality is better than my Dreambox on Scart. Obviously no HD playback, but then my setup can't handle that yet anyway. On 12 Oct 2007, at 22:34, Kartsa wrote: VOMP plugin is actually quite good and I have been using it with my second TV in the bedroom. One of the best thigs about it is that it's so small :) The problem is it does not support subtitling which is a must in Finland (I forgot to add that in my original post). How about the other MediaMVP related output methods (MediaMVP Plugin, MVPServer, MVPVdr). Do they support subtitles? \\Kartsa db kirjoitti: ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Improving quality of xvideo output for vdr-sxfe
I know this is slightly of topic but I am not sure where else to turn. I am using the binary drivers from nidia on a GeForce 5500 graphics card. I have two cables plugged into it, one dvi to vga adapter which is plugged into my flat panel tv then other a normal vga cable plugged into a flat panel screen. Both screens are mirrored on 1280x1024. The effect I have is that overlay XV displays appear to cut and tear in both mplayer and vdr-sfxe. If I use the xvmc driver then I don't get a video overlay (ie, no menus) although the quality is much better. There are no strange options that I can see if xorg.conf. Can anyone recommend anything I can try? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xvmc playback on vdr-sxfe
I have an nvidia graphics card GeForce FX 5500, which supports xvmc. However on vdr-sxfe it doesn't display the osd. Is there anyway I can persuade it to do so, is it a problem with my config, so is there no way? I am running Gentoo. vdr-sxfe xvdr://oac --video=xvmc says: [2905] [input_vdr] Connecting (control) to tcp://oac:37890 ... [2905] [input_vdr] Server greeting: VDR-1.4.6 xineliboutput-1.0.0rc2 READY [2905] [input_vdr] Connected (control) to tcp://oac:37890 [2905] [input_vdr] Connecting (data) to pipe:///etc/vdr/plugins/xineliboutput/pipes.2575/pipe.0 [2905] [input_vdr] Data stream connected (PIPE) [2905] [input_vdr] WARNING: Video output driver reports it does not support unscaled overlays ! libmpeg2: output port has XvMC capability AFD changed from -2 to -1 -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Logs filling up
How do I stop my logs filling up with: i2c_adapter i2c-1: master_xfer[1] R, addr=0x68, len=1 I am using a SkyStar2 card on gentoo x86. Dunno if it's a kernel module somewhere or something I can do to syslog. Thanks.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] streamdev-client blocking
Having read the Using VDR on Mac OS threads, I have tried out streamdev-client (had been using the server quite often) no a DVB-less system. I am running this under gentoo which creates a VDR process in the bootup, then I use vdr-sxfe to display on the screen. I have managed to get this working by copying the channels.conf over from the original vdr-server, however, when I close vdr-sxfe, the VDR server on the streamdev-client machine doesn't release the stream, which means that no one else can change channel. Is there a way to release the stream to allow channel changing on the server without closing the second vdr process (which would require root access). I figured if I had a local dvb card then switching channels to something local would do it, but I don't, and won't when I get this running on OsX. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] streamdev-client blocking
Rob Davis wrote: Having read the Using VDR on Mac OS threads, I have tried out streamdev-client (had been using the server quite often) no a DVB-less system. I am running this under gentoo which creates a VDR process in the bootup, then I use vdr-sxfe to display on the screen. I have managed to get this working by copying the channels.conf over from the original vdr-server, however, when I close vdr-sxfe, the VDR server on the streamdev-client machine doesn't release the stream, which means that no one else can change channel. Is there a way to release the stream to allow channel changing on the server without closing the second vdr process (which would require root access). I figured if I had a local dvb card then switching channels to something local would do it, but I don't, and won't when I get this running on OsX. Further to my own email, I think I need a dud channels.conf channel that i can select to put the client in suspend mode. However, everytime I try something I get channel not available... Is this the right track? -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Full Screen button for vdr-sxfe
Any way of getting a full screen / windows toggle button for vdr-sxfe (xineliboutput)? I am assuming this is a question for more than just xineliboutput.. What I'd like is a lirc/keyboard command (full screen) which will toggle the behaviour. I am happy to retro edit it into remote.conf. Maybe: LIRC.FScreenLIRCCOMMAND XkeySym.FScreen f for instance.. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Full Screen button for vdr-sxfe
Petri Hintukainen wrote: On Sat, 2007-03-31 at 17:39 +0200, Rob Davis wrote: Any way of getting a full screen / windows toggle button for vdr-sxfe (xineliboutput)? Add line DEFINES += -DXINELIBOUTPUT_FE_TOGGLE_FULLSCREEN to VDR Make.config file and re-compile xineliboutput. It will bind keys f/F to fullscreen toggle and d/D to de-interlace toggle. Thanks Petri, But to be fair, I really would like it on the remote.. Can you hijack something else off the remote? -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 12149 on Astra 19
Rob Davis wrote: I had to hack it to get it.. Don't remember how though.. Actually, CINE+ was split over several transponders CINE+ Promo;CSAT:12129:vC34:S19.2E:27500:168:112=fra,113=eng:0:0:8809:1:1086:0 CINE+ FOOT+;CSAT:12011:vC34:S19.2E:27500:170:120=fra:0:100:8809:1:1086:0 CINE+ FOOT+ 1;CSAT:12129:vC34:S19.2E:27500:161:84=fra,85=eng:0:100:8402:1:1086:0 CINE+ FOOT+ 2;CSAT:12129:vC34:S19.2E:27500:162:88=fra,89=eng:0:100:8403:1:1086:0 CINE+ FOOT+ 3;CSAT:12129:vC34:S19.2E:27500:163:92=fra,93=eng:0:100:8404:1:1086:0 CINE+ FOOT+ 4;CSAT:12129:vC34:S19.2E:27500:164:96=fra,97=eng:0:100:8405:1:1086:0 CINE+ FOOT+ 5;CSAT:12129:vC34:S19.2E:27500:165:100=fra,101=eng:47:100:8406:1:1086:0 CINE+ FOOT+ 6;CSAT:12129:vC34:S19.2E:27500:166:104=fra:0:100:8407:1:1086:0 CINE+ FOOT+ 7;CSAT:12129:vC34:S19.2E:27500:167:108=fra,109=eng:0:100:8408:1:1086:0 CINE+ FOOT+ 8;CSAT:12129:vC34:S19.2E:27500:168:112=fra,113=eng:0:100:8409:1:1086:0 CINE+ FOOT+ 9;CSAT:12129:vC34:S19.2E:27500:169:116=fra,117=eng:59:100:8410:1:1086:0 CINE+ FOOT+ 10;CSAT:12011:vC34:S19.2E:27500:170:120=fra,121=eng:0:100:8811:1:1090:0 CINE+ FOOT+ 11;CSAT:12129:vC34:S19.2E:27500:160:80=fra,81=eng:0:100:8413:1:1086:0 CINE+ FOOT+ 12;CSAT:12207:vC34:S19.2E:27500:170:120=fra,121=eng:62:100:8515:1:1086:0 CINE+ FOOT+ 13;CSAT:12129:vC34:S19.2E:27500:166:104=fra:0:100:8411:1:1086:0 CINE+ FOOT+ 14;CSAT:12129:vC34:S19.2E:27500:167:108=fra,109=eng:0:100:8412:1:1086:0 CINE+;CSAT:12011:vC34:S19.2E:27500:168:112=fra,113=eng:0:0:8810:1:1086:0 MAG CINE+ FOOT+;CSAT:12011:vC34:S19.2E:27500:0:224=fra:0:0:8812:1:1086:0 -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UK Freeview Logical Channel Numbers
Tony Grant wrote: Le jeudi 15 février 2007 à 00:12 +0100, Rob Davis a écrit : What I am after is an ordered channel list in the same order as the official decoders from different providers. ie, someone from outside the UK wouldn't necessarily know that the channels go: BBC 1, 2 , ITV 1, Ch 4, five. Then BBC 3, 4 etc. I always thought that I could put them in the order I want to (which I do) by messing with channels.conf? My on screen EPG is shown with the channels in the same order as hey appear in channels.conf. Am I missing a very important idea here? BBC 1 London;BSkyB:10773:hC56:S28.2E:22000:5000:5001=eng,5002=NAR:5003:0:6301:2:2045:0 BBC 2 England;BSkyB:10773:hC56:S28.2E:22000:5100:5101=eng,5102=NAR:5103:0:6302:2:2045:0 BBC THREE;BSkyB:10773:hC56:S28.2E:22000:5200:5201=eng,5202=NAR:5203:0:6319:2:2045:0 BBC FOUR;BSkyB:10773:hC56:S28.2E:22000:5300:5301=eng,5302=NAR:5303:0:6316:2:2045:0 CBBC Channel;BSkyB:10773:hC56:S28.2E:22000:5200:5201=eng,5202=NAR:5203:0:6317:2:2045:0 CBeebies;BSkyB:10773:hC56:S28.2E:22000:5300:5301=eng,5302=NAR:5303:0:6318:2:2045:0 BBC NEWS 24;BSkyB:10773:hC56:S28.2E:22000:5400:5401=eng:5403:0:6304:2:2045:0 ITV1 Granada;BSkyB:10758:vC56:S28.2E:22000:2342:2343=eng:2320:0:10080:2:2044:0 ITV2;BSkyB:10758:vC56:S28.2E:22000:2348:2349=eng,2351=NAR:2317:0:10070:2:2044:0 ITV3;BSkyB:10906:v:S28.2E:22000:2356:2357:0:0:10260:2:2044:0 ITV4;BSkyB:10758:v:S28.2E:22000:2355:2356=eng:0:0:10072:2:2044:0 :- Below this point are the channels found by epg scan Have a look at: http://www.lyngsat.com/packages/skyuk_chno.html From there a channels.conf file would look roughly: :@101 BBC 1 West;BSkyB:10817:vC56:S28.2E:22000:2305:2307=eng:2309:0:10351:2:2048:0:west.bbc1.bbc.co.uk :@102 BBC 2 England;BSkyB:10773:hC56:S28.2E:22000:5100:5101=eng,5102=NAR:5103:0:6302:2:2045:0:west.bbc2.bbc.co.uk :@103 ITV1 West;BSkyB:10832:hC56:S28.2E:22000:2344:2345=eng:2346:0:10030:2:2049:0:west.htv.co.uk :@104 Channel 4;BSkyB:12168:V:S28.2E:27500:2311+2304:2312=eng,2313=NAR:2314:960,961:9201:2:2024:0:channel4.com :@105 Five;BSkyB:12304:H:S28.2E:27500:514+8190:662=eng,682=NAR:578:960,961:9343:2:2031:0:channel5.co.uk :@106 Sky One;BSkyB:12285:v:S28.2E:27500:513+8190:641=eng,661=NAR:577:960,961:4703:2:2030:0:sky-one.sky.com :@107 Sky Two;BSkyB:12226:h:S28.2E:27500:514+8190:642=eng,662=NAR:578:960,961:5104:2:2027:0:sky-two.sky.com :@108 Sky Three;BSkyB:12226:h:S28.2E:27500:512+8190:640=eng,660=NAR:576:960,961:5103:2:2027:0:sky-three.sky.com :@109 UKTV Gold;BSkyB:11817:V:S28.2E:27500:2326:2328=eng,2330=NAR:2327:960,961:6504:2:2006:0:uk-gold.flextech.telewest.co.uk :@110 UKTV Gold +1;BSkyB:11992:H:S28.2E:27500:2329:2330=eng,2354=NAR:2331:960,961:7605:2:2015:0:plus-1.uk-gold.flextech.telewest.co.uk UK Gold 2~;BSkyB:11817:V:S28.2E:27500:2336:2338=eng:2337:960,961:6516:2:2006:0:uk-gold-2.flextech.telewest.co.uk :@115 BBC THREE;BSkyB:10773:hC56:S28.2E:22000:5200:5201=eng,5202=NAR:5203:0:6319:2:2045:0:choice.bbc.co.uk :@116 BBC FOUR;BSkyB:10773:hC56:S28.2E:22000:5300:5301=eng,5302=NAR:5303:0:6316:2:2045:0:knowledge.bbc.co.uk :@117 ITV2;BSkyB:10758:v:S28.2E:22000:2348:2349=eng,2352=NAR:2354:0:10070:2:2044:0:itv2.itv.co.uk :@118 ITV3;BSkyB:10906:v:S28.2E:22000:2356:2357=eng,2358=NAR:2359:0:10260:2:2054:0:itv3.itv.co.uk :@119 ITV4;BSkyB:10758:v:S28.2E:22000:2368:2369=eng:2370:0:10072:2:2044:0:itv4.itv.co.uk etc.. If you wanted to have the same numbers as a Sky Digibox. Now, if you had two feeds, say Sky UK and Sky Italia (Like us) You also have: http://www.lyngsat.com/packages/skyitalia_chno.html The format is roughly the same.. Tony PS any news on when/if Channel5 and channel4 will be FTA? Their licence expires next year, but no one seems to know if then will then go FTA or stay FTV. I have a FreeSat card, so am not too worried. -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UK Freeview Logical Channel Numbers
Andrew Herron wrote: Hi Rob, I think xmltv2vdr.pl might be a better place to start for what you are trying to achieve... as you can point it at a TV listing web site and extract all the EPG data for the channels listed apparently based on my reading of threads on this list that is! Yes, but not quite the same. What I am after is an ordered channel list in the same order as the official decoders from different providers. ie, someone from outside the UK wouldn't necessarily know that the channels go: BBC 1, 2 , ITV 1, Ch 4, five. Then BBC 3, 4 etc. I know when I moved to Italy from the UK it took me about a year to work out that Rete 4, Canale 5 were followed by Italia 1.. The channel numbers for several providers are already in Lyngsat, with the channel frequencies and tsid's.. Why not extract the info and build an ordered channel list for vdr in the operator designated order? -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
