Re: [vdr] Logical Channel Numbers

[Stuart Morris]

On 3 July 2016 at 16:24, Ville Skyttä <ville.sky...@iki.fi> wrote:

> On Sat, Jul 2, 2016 at 7:05 PM, Stuart Morris <stuart8mor...@gmail.com>
> wrote:
> >
> > I have recently upgraded to VDR v2.2.0 and I notice in the changelog
> that support for Logical Channel Numbers (LCN) has been added.
> > Is there any way to sort and select VDR channels by LCN yet?
>
> Works fine for me with the lcn-support-v2 patch from
> http://www.saunalahti.fi/~rahrenbe/vdr/patches/
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>

Works for me to once I had set the DVB standard compliance to NORDIG on the
VDR setup menu.
I get Freeview Logical Channel Numbering OK. The channels list still needs
sorting by some means or other.
Thanks to you all
Stuart
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Logical Channel Numbers

[Stuart Morris]

I have recently upgraded to VDR v2.2.0 and I notice in the changelog that
support for Logical Channel Numbers (LCN) has been added.
Is there any way to sort and select VDR channels by LCN yet?

BTW My attempts at using scan to generate a channels.conf with LCN have
been unsuccessful due to the fact that scan does not detect DVB-T2
FreeviewHD muxes in the UK.

Thanks
Stu-e
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] DVB-T2 device in France

[Stuart Morris]

I have a 290e I use for DVB-T2 reception and it has worked really well for
some time now.
Shame you can't buy them anymore :-(

On 19 September 2015 at 10:21, Jari Fredriksson  wrote:

> On 17.9.2015 15:01, Nicolas Huillard wrote:
>
>> Hello all,
>>
>> My previous mail to this ML is apparently dated 2011 ;-) Everything was
>> OK there since then... Except that my Hauppauge Nova-T-500 died
>> recently, and my ancient PCI cards do not work in the 2013 server.
>>
>> I'm looking for advice for a new DVB-T2 device, which should :
>> * have a good tuner, because some channels (transponders, ie.
>> frequencies) are difficult to catch here ; the TV set (Panasonic) works
>> perfectly well, and I've added an RF amplifier on the roof, so I guess
>> the Nova-T-500 tuner was not good enough
>> * have a PCI or preferably PCI-e bus, and dual tuner (I don't really
>> like USB sticks, which tend to lead to a mess of cable)
>> * be robustly supported with stock kernels in Debian (jessie and
>> future), which does not seem to be a problem anymore...
>>
>> If there are some dual-tuner, DVB-T2 + S2 card out there which are well
>> supported by VDR, that's OK too. I may prefer to add another DVB-S2 card
>> later on though (there is no sat-dish on the roof yet).
>>
>> TIA !
>>
>
>
> I use an USB tuner "PCTV Systems nanoStick T2 290e" from Hauppauge. It has
> a good Sony tuner, and DVB-T2 in my setup works fine even with an desktop
> antenna (the broadcast mast is in visible range though).
>
> Driver is in kernel, and this was the first Linux tuner for DVB-T2 and
> supported even in the older kernels. I use it in a Raspberry Pi 2 with two
> DVB-C tuners and I'm all happy.
>
>
> --
> jarif.bit
>
> ___
> 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] Which epg for Sky UK

[Stuart Morris]

 The other reason for me to use the patch is for Freeview
 HD's EIT. The
 encoding is exactly the same as Freesat's but I think the
 difference is
 that it still uses standard PIDs instead of non-standard
 ones. So EEPG
 would have to detect the encoding by using the flag bytes at
 the start
 of the string instead of by the PID they're from.

I would like to second what Tony states here. When I used the EEPG plugin 
(quite a long time ago), it failed to decode Freeview HD EPG because it did not 
support the encoded EPG delivered on the standard PID. So this is why I use the 
patch instead of the EEPG plugin.

I spent some time trying to figure out how to modify the plugin to suit my 
needs but it was beyond my understanding and I gave up.


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR2 plugin streaming problem

[Stuart Morris]

 I'm finding plugins streamdev, xvdr and
 vnsi
  all
   fail
to stream live TV and radio. Is this to be
  expected
   with
VDR-2.0.0 until plugin developers can catch 
 up?

No, at least streamdev and vnsi have both
 been
  working
   fine
for me.
   
   OK Thanks.
   It might yet be something I'm doing wrong. I'll
 dig
  deeper.
  
  Nope I definitely cannot get streamdev to stream. I
 tried to
  stream to VLC using any of the URLs on the
 localhost:3000
  webpage without success.
  
  VDR syslog extract:
  Apr  3 22:17:23 bob vdr: [30570] Streamdev: Accepted
  new client (HTTP) 192.168.1.104:56251
  Apr  3 22:17:23 bob vdr: [8832]
 streamdev-livestreaming
  thread started (pid=30557, tid=8832, prio=high)
  Apr  3 22:17:23 bob vdr: [8831] streamdev-writer
 thread
  started (pid=30557, tid=8831, prio=high)
  
  VLC log (last few lines only):
  access_http debug: http: server='bob' port=3000
  file='/TS/T-9018-4173-6720.ts'
  main debug: net: connecting to bob port 3000
  main debug: connection succeeded (socket = 23)
  access_http debug: protocol 'HTTP' answer code 200
  access_http debug: Content-Type: audio/mpeg
  access_http debug: Connection: close
  access_http debug: Pragma: no-cache
  main debug: using access module access_http
  main debug: TIMER module_need() : 78.455 ms - Total
 78.455
  ms / 1 intvls (Avg 78.455 ms)
  main debug: Using stream method for AStream*
  main debug: starting pre-buffering
  
  Can anyone suggest how I can investigate this further?
  Thanks
 
 This is getting stranger. I have installed the xineliboutput
 plugin which appears to mostly work OK except there is no
 live TV, only the no signal picture is displayed.
 
 There is a common thread here, all of these plugins fail to
 stream live TV or radio.

After a rebuild of VDR2 and plugins from freshly unzipped source files, the 
problem has gone away.

Thanks
Egg Face


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR2 plugin streaming problem

[Stuart Morris]

Congratulations on the
  release of VDR-2.0.0.
   
I'm finding plugins streamdev, xvdr and vnsi
 all
  fail
   to stream live TV and radio. Is this to be
 expected
  with
   VDR-2.0.0 until plugin developers can catch  up?
   
   No, at least streamdev and vnsi have both been
 working
  fine
   for me.
  
  OK Thanks.
  It might yet be something I'm doing wrong. I'll dig
 deeper.
 
 Nope I definitely cannot get streamdev to stream. I tried to
 stream to VLC using any of the URLs on the localhost:3000
 webpage without success.
 
 VDR syslog extract:
 Apr  3 22:17:23 bob vdr: [30570] Streamdev: Accepted
 new client (HTTP) 192.168.1.104:56251
 Apr  3 22:17:23 bob vdr: [8832] streamdev-livestreaming
 thread started (pid=30557, tid=8832, prio=high)
 Apr  3 22:17:23 bob vdr: [8831] streamdev-writer thread
 started (pid=30557, tid=8831, prio=high)
 
 VLC log (last few lines only):
 access_http debug: http: server='bob' port=3000
 file='/TS/T-9018-4173-6720.ts'
 main debug: net: connecting to bob port 3000
 main debug: connection succeeded (socket = 23)
 access_http debug: protocol 'HTTP' answer code 200
 access_http debug: Content-Type: audio/mpeg
 access_http debug: Connection: close
 access_http debug: Pragma: no-cache
 main debug: using access module access_http
 main debug: TIMER module_need() : 78.455 ms - Total 78.455
 ms / 1 intvls (Avg 78.455 ms)
 main debug: Using stream method for AStream*
 main debug: starting pre-buffering
 
 Can anyone suggest how I can investigate this further?
 Thanks

This is getting stranger. I have installed the xineliboutput plugin which 
appears to mostly work OK except there is no live TV, only the no signal 
picture is displayed.

There is a common thread here, all of these plugins fail to stream live TV or 
radio.



___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDR2 plugin streaming problem

[Stuart Morris]

Congratulations on the release of VDR-2.0.0.

I'm finding plugins streamdev, xvdr and vnsi all fail to stream live TV and 
radio. Is this to be expected with VDR-2.0.0 until plugin developers can catch 
up?

Stu-e


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR2 plugin streaming problem

[Stuart Morris]

  Congratulations on the release of VDR-2.0.0.
 
  I'm finding plugins streamdev, xvdr and vnsi all fail
 to stream live TV and radio. Is this to be expected with
 VDR-2.0.0 until plugin developers can catch  up?
 
 No, at least streamdev and vnsi have both been working fine
 for me.

OK Thanks.
It might yet be something I'm doing wrong. I'll dig deeper.


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR2 plugin streaming problem

[Stuart Morris]

   Congratulations on the
 release of VDR-2.0.0.
  
   I'm finding plugins streamdev, xvdr and vnsi all
 fail
  to stream live TV and radio. Is this to be expected
 with
  VDR-2.0.0 until plugin developers can catch  up?
  
  No, at least streamdev and vnsi have both been working
 fine
  for me.
 
 OK Thanks.
 It might yet be something I'm doing wrong. I'll dig deeper.

Nope I definitely cannot get streamdev to stream. I tried to stream to VLC 
using any of the URLs on the localhost:3000 webpage without success.

VDR syslog extract:
Apr  3 22:17:23 bob vdr: [30570] Streamdev: Accepted new client (HTTP) 
192.168.1.104:56251
Apr  3 22:17:23 bob vdr: [8832] streamdev-livestreaming thread started 
(pid=30557, tid=8832, prio=high)
Apr  3 22:17:23 bob vdr: [8831] streamdev-writer thread started (pid=30557, 
tid=8831, prio=high)

VLC log (last few lines only):
access_http debug: http: server='bob' port=3000 file='/TS/T-9018-4173-6720.ts'
main debug: net: connecting to bob port 3000
main debug: connection succeeded (socket = 23)
access_http debug: protocol 'HTTP' answer code 200
access_http debug: Content-Type: audio/mpeg
access_http debug: Connection: close
access_http debug: Pragma: no-cache
main debug: using access module access_http
main debug: TIMER module_need() : 78.455 ms - Total 78.455 ms / 1 intvls (Avg 
78.455 ms)
main debug: Using stream method for AStream*
main debug: starting pre-buffering

Can anyone suggest how I can investigate this further?
Thanks


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23

[Stuart Morris]

Hi
I have updated my DVB drivers using:
git clone git://linuxtv.org/media_build.git
cd media_build 
./build
make install

Yet VDR complains of the wrong DVB API version number:
dvbdevice.h:18:2: error: #error VDR requires Linux DVB driver API version 5.3 
or higher!

/usr/include/linux/dvb/version.h reports version 5.2 and the date of the file 
is old, meaning it was not updated when the drivers were updated.

Can anybody explain what has gone wrong here?
Thanks


--- On Sun, 15/1/12, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote:

 From: Klaus Schmidinger klaus.schmidin...@tvdr.de
 Subject: [vdr] [ANNOUNCE] VDR developer version 1.7.23
 To: vdr@linuxtv.org
 Date: Sunday, 15 January, 2012, 15:10
 VDR developer version 1.7.23 is now
 available at
 
       ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2
 
 A 'diff' against the previous version is available at
 
       ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff
 
 MD5 checksums:
 
 de136f7be28c4b6f1fa0e2218b4acc11  vdr-1.7.23.tar.bz2
 2977b75cd8dacad187d11c10b867d56a 
 vdr-1.7.22-1.7.23.diff
 
 WARNING:
 
 
 This is a *developer* version. Even though *I* use it in my
 productive
 environment. I strongly recommend that you only use it
 under controlled
 conditions and for testing and debugging.
 
 
 The changes since version 1.7.22:
 
 - Removed the '.pl' suffix from svdrpsend.pl (sorry, I
 missed that one).
 - Fixed bonding more than two devices.
 - Fixed handling symbolic links in
 cRecordings::ScanVideoDir() (reported by
   Sundararaj Reel).
 - Fixed a memory leak in cRecordings::ScanVideoDir() in
 case there are too many
   link levels (reported by Sundararaj Reel).
 - Removed redundant memset() in the ctor of
 cSatCableNumbers (triggered by
   Ville Skyttä pointing out that the argument
 sequence in the call was wrong).
 - Removed a redundant NULL check in
 cDvbSpuDecoder::setTime() (thanks to Ville Skyttä).
 - Added HasSnr to the DEBUG_SIGNALQUALITY output in
 cDvbTuner::GetSignalQuality()
   (triggered by Ville Skyttä pointing out that the
 variable HasSnr was unused).
 - Updated the Finnish OSD texts (thanks to Rolf
 Ahrenberg).
 - Added support for HbbTV to libsi (thanks to Christoph
 Haubrich).
 - Added support for devices with more than one delivery
 system per frontend.
   This requires a DVB driver with version 5.5 or
 higher that can handle the
   DTV_ENUM_DELSYS call. With older drivers it will
 fall back to one delivery
   system per frontend.
 - Updated the Hungarian language texts (thanks to István
 Füley).
 - cDvbTuner::ExecuteDiseqc() now makes sure only one tuner
 sends SCR commands
   at any given time (reported by Frank Neumann).
 - cEvent::FixEpgBugs() now replaces any newline characters
 in stream component
   descriptions with blanks (thanks to Torsten Lang for
 reporting a problem with
   EPG data from BSkyB's MTV MUSIC,
 S28.2E-2-2010-7012).
 - Fixed cDvbSubtitleConverter::SetOsdData() (thanks to Rolf
 Ahrenberg).
 - Fixed cListBase::Move() in case From and To are equal
 (reported by Sundararaj
   Reel).
 - Added support for DVB-T2 to libsi (thanks to Rolf
 Ahrenberg).
 - Added support for handling DVB-T2 transponders. 
 This requires a DVB driver
   with version 5.3 or higher that can handle the
 DTV_DVBT2_PLP_ID call (thanks
   to Rolf Ahrenberg).
 - Fixed cConfig::Load() for g++ version 4.7.0 (thanks to
 Ville Skyttä).
 - Fixed a possible memory corruption in cTsToPes::GetPes()
 in case of broken
   TS packets, e.g. when switching channels.
 - Fixed the SVDRP command CLRE for a single channel in case
 there are events
   that have a timer (thanks to Timo Eskola).
 - BIDI support now checks at runtime whether the system
 runs with UTF-8 (suggested
   by Torsten Lang).
 - Added member functions Adapter() and Frontend() to
 cDvbDevice (suggested by
   Rolf Ahrenberg).
 - The parameters that are only used by second generation
 delivery systems (DVB-S2
   and DVB-T2) are no longer written into channels.conf
 for first generation
   delivery systems (DVB-S and DVB-T).
 - Changed IndexToHMSF() so that it can handle negative
 Index values.
 - Added option -N to the msgmerge call in the Makefile,
 because fuzzy translation
   mostly resulted in useless strings.
 - The new setup option Replay/Show remaining time can be
 used to switch between
   showing the total length or the remaining time of
 the recording that is currently
   replayed.
 - Fixed wrongfully displaying the length of a recording in
 the title of the replay
   progress display.
 - Fixed frozen live view with device bonding in case the
 bonded master is used for
   live viewing (reported by Uwe Scheffler).
 
 Have fun!
 
 Klaus
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23

[Stuart Morris]

Thanks
I pointed Make.config to the media_build/linux directory and built that way.
I'm surprised because I fully expected the media_build script to install the 
headers to.

--- On Sun, 22/1/12, Ian Bates ian_and_joa...@talktalk.net wrote:

 From: Ian Bates ian_and_joa...@talktalk.net
 Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
 To: VDR Mailing List vdr@linuxtv.org
 Date: Sunday, 22 January, 2012, 12:40
 Hi,
 
 Something to try:
 
 *Short answer*
 
 Make sure VDR Make.config points to the appropriate
 media_build directory (DVBDIR variable)
 
 *Longer answer*
 
 I'm not sure a simple 'install' of the DVB drivers changes
 any system headers.  So VDR needs to point the headers
 relevant to the available modules.
 
 1. Ensure you really have built and installed the
 media_build DVB stack.  
 
 2. Point VDR Make.config to your git media_build directory
 NOTE '/linux' suffix:
 
 ...
 
 # From my vdr Make.config:
 #DVBDIR  = /usr/local/src/v4l-dvb/current/linux
 #DVBDIR  =
 /usr/local/src/linux-tbs-drivers/current/linux
 DVBDIR  =
 /usr/local/src/linux-tbs-drivers/testing/linux
 
 # Change to where you have downloaded and built your DVB
 stuff 
 DVBDIR  = /usr/local/src/dvb/media_build-git/linux
 
 ...
 
 3. make VDR and install
 
 
 If you have followed these steps already then I'm sorry not
 to add anything new.
 
 
 Regards,
 
 
 Ian.
 
 
 On 22 Jan 2012, at 11:03, Stuart Morris wrote:
 
  Hi
  I have updated my DVB drivers using:
  git clone git://linuxtv.org/media_build.git
  cd media_build 
  ./build
  make install
  
  Yet VDR complains of the wrong DVB API version
 number:
  dvbdevice.h:18:2: error: #error VDR requires Linux DVB
 driver API version 5.3 or higher!
  
  /usr/include/linux/dvb/version.h reports version 5.2
 and the date of the file is old, meaning it was not updated
 when the drivers were updated.
  
  Can anybody explain what has gone wrong here?
  Thanks
  
  
  --- On Sun, 15/1/12, Klaus Schmidinger klaus.schmidin...@tvdr.de
 wrote:
  
  From: Klaus Schmidinger klaus.schmidin...@tvdr.de
  Subject: [vdr] [ANNOUNCE] VDR developer version
 1.7.23
  To: vdr@linuxtv.org
  Date: Sunday, 15 January, 2012, 15:10
  VDR developer version 1.7.23 is now
  available at
  
        ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2
  
  A 'diff' against the previous version is available
 at
  
        ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff
  
  MD5 checksums:
  
  de136f7be28c4b6f1fa0e2218b4acc11 
 vdr-1.7.23.tar.bz2
  2977b75cd8dacad187d11c10b867d56a 
  vdr-1.7.22-1.7.23.diff
  
  WARNING:
  
  
  This is a *developer* version. Even though *I* use
 it in my
  productive
  environment. I strongly recommend that you only
 use it
  under controlled
  conditions and for testing and debugging.
  
  
  The changes since version 1.7.22:
  
  - Removed the '.pl' suffix from svdrpsend.pl
 (sorry, I
  missed that one).
  - Fixed bonding more than two devices.
  - Fixed handling symbolic links in
  cRecordings::ScanVideoDir() (reported by
    Sundararaj Reel).
  - Fixed a memory leak in
 cRecordings::ScanVideoDir() in
  case there are too many
    link levels (reported by
 Sundararaj Reel).
  - Removed redundant memset() in the ctor of
  cSatCableNumbers (triggered by
    Ville Skyttä pointing out that
 the argument
  sequence in the call was wrong).
  - Removed a redundant NULL check in
  cDvbSpuDecoder::setTime() (thanks to Ville
 Skyttä).
  - Added HasSnr to the DEBUG_SIGNALQUALITY output
 in
  cDvbTuner::GetSignalQuality()
    (triggered by Ville Skyttä
 pointing out that the
  variable HasSnr was unused).
  - Updated the Finnish OSD texts (thanks to Rolf
  Ahrenberg).
  - Added support for HbbTV to libsi (thanks to
 Christoph
  Haubrich).
  - Added support for devices with more than one
 delivery
  system per frontend.
    This requires a DVB driver with
 version 5.5 or
  higher that can handle the
    DTV_ENUM_DELSYS call. With older
 drivers it will
  fall back to one delivery
    system per frontend.
  - Updated the Hungarian language texts (thanks to
 István
  Füley).
  - cDvbTuner::ExecuteDiseqc() now makes sure only
 one tuner
  sends SCR commands
    at any given time (reported by
 Frank Neumann).
  - cEvent::FixEpgBugs() now replaces any newline
 characters
  in stream component
    descriptions with blanks (thanks
 to Torsten Lang for
  reporting a problem with
    EPG data from BSkyB's MTV
 MUSIC,
  S28.2E-2-2010-7012).
  - Fixed cDvbSubtitleConverter::SetOsdData()
 (thanks to Rolf
  Ahrenberg).
  - Fixed cListBase::Move() in case From and To are
 equal
  (reported by Sundararaj
    Reel).
  - Added support for DVB-T2 to libsi (thanks to
 Rolf
  Ahrenberg).
  - Added support for handling DVB-T2 transponders.
 
  This requires a DVB driver
    with version 5.3 or higher that
 can handle the
  DTV_DVBT2_PLP_ID call (thanks
    to Rolf Ahrenberg).
  - Fixed cConfig::Load() for g++ version 4.7.0
 (thanks to
  Ville Skyttä).
  - Fixed a possible memory

Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23

[Stuart Morris]

I also had to copy compiler.h from my kernel sources to the media_build 
directory otherwise various plugins would not compile.
cp /usr/src/kernels/2.6.35.14-96.fc14.i686.PAE/include/linux/compiler.h 
/usr/local/src/media_build/linux/include/linux/

--- On Sun, 22/1/12, Stuart Morris stuart_mor...@talk21.com wrote:

 From: Stuart Morris stuart_mor...@talk21.com
 Subject: Re: [vdr] [ANNOUNCE] VDR developer version 1.7.23
 To: VDR Mailing List vdr@linuxtv.org
 Date: Sunday, 22 January, 2012, 14:50
 Thanks
 I pointed Make.config to the media_build/linux directory
 and built that way.
 I'm surprised because I fully expected the media_build
 script to install the headers to.
 
 --- On Sun, 22/1/12, Ian Bates ian_and_joa...@talktalk.net
 wrote:
 
  From: Ian Bates ian_and_joa...@talktalk.net
  Subject: Re: [vdr] [ANNOUNCE] VDR developer version
 1.7.23
  To: VDR Mailing List vdr@linuxtv.org
  Date: Sunday, 22 January, 2012, 12:40
  Hi,
  
  Something to try:
  
  *Short answer*
  
  Make sure VDR Make.config points to the appropriate
  media_build directory (DVBDIR variable)
  
  *Longer answer*
  
  I'm not sure a simple 'install' of the DVB drivers
 changes
  any system headers.  So VDR needs to point the
 headers
  relevant to the available modules.
  
  1. Ensure you really have built and installed the
  media_build DVB stack.  
  
  2. Point VDR Make.config to your git media_build
 directory
  NOTE '/linux' suffix:
  
  ...
  
  # From my vdr Make.config:
  #DVBDIR  = /usr/local/src/v4l-dvb/current/linux
  #DVBDIR  =
  /usr/local/src/linux-tbs-drivers/current/linux
  DVBDIR  =
  /usr/local/src/linux-tbs-drivers/testing/linux
  
  # Change to where you have downloaded and built your
 DVB
  stuff 
  DVBDIR  = /usr/local/src/dvb/media_build-git/linux
  
  ...
  
  3. make VDR and install
  
  
  If you have followed these steps already then I'm
 sorry not
  to add anything new.
  
  
  Regards,
  
  
  Ian.
  
  
  On 22 Jan 2012, at 11:03, Stuart Morris wrote:
  
   Hi
   I have updated my DVB drivers using:
   git clone git://linuxtv.org/media_build.git
   cd media_build 
   ./build
   make install
   
   Yet VDR complains of the wrong DVB API version
  number:
   dvbdevice.h:18:2: error: #error VDR requires
 Linux DVB
  driver API version 5.3 or higher!
   
   /usr/include/linux/dvb/version.h reports version
 5.2
  and the date of the file is old, meaning it was not
 updated
  when the drivers were updated.
   
   Can anybody explain what has gone wrong here?
   Thanks
   
   
   --- On Sun, 15/1/12, Klaus Schmidinger klaus.schmidin...@tvdr.de
  wrote:
   
   From: Klaus Schmidinger klaus.schmidin...@tvdr.de
   Subject: [vdr] [ANNOUNCE] VDR developer
 version
  1.7.23
   To: vdr@linuxtv.org
   Date: Sunday, 15 January, 2012, 15:10
   VDR developer version 1.7.23 is now
   available at
   
         ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.23.tar.bz2
   
   A 'diff' against the previous version is
 available
  at
   
         ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.22-1.7.23.diff
   
   MD5 checksums:
   
   de136f7be28c4b6f1fa0e2218b4acc11 
  vdr-1.7.23.tar.bz2
   2977b75cd8dacad187d11c10b867d56a 
   vdr-1.7.22-1.7.23.diff
   
   WARNING:
   
   
   This is a *developer* version. Even though
 *I* use
  it in my
   productive
   environment. I strongly recommend that you
 only
  use it
   under controlled
   conditions and for testing and debugging.
   
   
   The changes since version 1.7.22:
   
   - Removed the '.pl' suffix from svdrpsend.pl
  (sorry, I
   missed that one).
   - Fixed bonding more than two devices.
   - Fixed handling symbolic links in
   cRecordings::ScanVideoDir() (reported by
     Sundararaj Reel).
   - Fixed a memory leak in
  cRecordings::ScanVideoDir() in
   case there are too many
     link levels (reported by
  Sundararaj Reel).
   - Removed redundant memset() in the ctor of
   cSatCableNumbers (triggered by
     Ville Skyttä pointing out that
  the argument
   sequence in the call was wrong).
   - Removed a redundant NULL check in
   cDvbSpuDecoder::setTime() (thanks to Ville
  Skyttä).
   - Added HasSnr to the DEBUG_SIGNALQUALITY
 output
  in
   cDvbTuner::GetSignalQuality()
     (triggered by Ville Skyttä
  pointing out that the
   variable HasSnr was unused).
   - Updated the Finnish OSD texts (thanks to
 Rolf
   Ahrenberg).
   - Added support for HbbTV to libsi (thanks
 to
  Christoph
   Haubrich).
   - Added support for devices with more than
 one
  delivery
   system per frontend.
     This requires a DVB driver with
  version 5.5 or
   higher that can handle the
     DTV_ENUM_DELSYS call. With older
  drivers it will
   fall back to one delivery
     system per frontend.
   - Updated the Hungarian language texts
 (thanks to
  István
   Füley).
   - cDvbTuner::ExecuteDiseqc() now makes sure
 only
  one tuner
   sends SCR commands
     at any given time (reported by
  Frank Neumann).
   - cEvent::FixEpgBugs() now replaces any
 newline
  characters
   in stream

Re: [vdr] [PATCH] vdr-1.7.21 DVB-T2 support

[Stuart Morris]

I'm running 1.7.21 with a DVB-T and DVB-T2. The only patch I have is for
decoding the compressed EPG for UK Freeview HD. Does DVB-T2 need special 
handling in VDR? That's not been my experience.

I suspect it depends on the tuner driver. I'm using a PCTV nanoStick 290e.

--- On Wed, 21/12/11, Rolf Ahrenberg rahre...@cc.hut.fi wrote:

 From: Rolf Ahrenberg rahre...@cc.hut.fi
 Subject: Re: [vdr] [PATCH] vdr-1.7.21  DVB-T2 support
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 21 December, 2011, 14:24
 No comments? Am I really the only one
 running such a DVB-T + DVB-T2 system?
 
 Anyway, this has worked quite nicely for a rather long time
 on my setup, and therefore I strongly suggest the
 integration of the patch into the official VDR tree before
 the next stable release.
 
 BR,
 --
 rofa
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [PATCH] vdr-1.7.21 DVB-T2 support

[Stuart Morris]

Ok I agree pure luck plays a part on my behalf. All my DVB-T2 channels
are QAM256 so none of the other DVB-T cards would ever be selected to tune
to a DVB-T2 channel, at least in the UK at present.

--- On Thu, 22/12/11, Rolf Ahrenberg rahre...@cc.hut.fi wrote:

 From: Rolf Ahrenberg rahre...@cc.hut.fi
 Subject: Re: [vdr] [PATCH] vdr-1.7.21  DVB-T2 support
 To: VDR Mailing List vdr@linuxtv.org
 Date: Thursday, 22 December, 2011, 11:24
 On Thu, 22 Dec 2011, Stuart Morris
 wrote:
 
  I'm running 1.7.21 with a DVB-T and DVB-T2. The only
 patch I have is for
  decoding the compressed EPG for UK Freeview HD. Does
 DVB-T2 need special handling in VDR? That's not been my
 experience.
  I suspect it depends on the tuner driver. I'm using a
 PCTV nanoStick 290e.
 
 Well, your T2 channels are most propably using PLP id 0 and
 your driver is defaulting to that one, so your working setup
 is pure luck until the broadcasting systems are getting more
 complex :)
 
 Also without the patch there's no mechanism to prevent your
 DVB-T cards tuning to DVB-T2 channels.
 
 BR,
 --
 rofa
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Using some mediaplayer as set top box player for VDR

[Stuart Morris]

I tried the upnp plugin without success. Development appears to have stalled:
http://projects.vdr-developer.org/projects/plg-upnp

I have tried Vdrnfofs to export VDR recordings to a virtual file system. Then 
added that to my miniDLNA server pool. This serves recordings to a DLNA client 
ok, but it does not update with new recordings for some reason I have not yet 
discovered. The bigger problem with this approach is that it's difficult to get 
a DLNA client that has convenient features like resume playback, skip 
forward/backward and even just plain old fast forward/rewind.

I am seriously considering going down the XBMC-pvr route. The Openelec-pvr 
experimental branch works OK as a VDR client, if a bit unstable at the moment. 
Openelec is a minimal Linux OS built around XBMC. My target hardware is a basic 
PC with a good nVidia graphics card and only 4Gbyte USB flash disk as a boot 
device. It's a lot bigger than a TV set-top-box but it's not expensive. My 
budget is about £150. To keep power costs down, it uses suspend-to-ram when not 
in use. Resume from suspend is super quick.


--- On Sat, 17/12/11, Kartsa k...@kniivila.com wrote:

 From: Kartsa k...@kniivila.com
 Subject: Re: [vdr] Using some mediaplayer as set top box player for VDR
 To: VDR Mailing List vdr@linuxtv.org
 Date: Saturday, 17 December, 2011, 23:23
 How about DLNA? I found something
 about DLNA server plugin but was not 
 sure how it was used. If I would install that plugin and
 byu a DLNA 
 player could that combination work? Or better yet does
 anyone have any 
 experience on such combination?
 
 \\Kartsa
 
 09.12.2011 14:25, Kartsa kirjoitti:
  Yes i've seen this thread before and it has been some
 development since I
  last read it. But it still has no actual results :)
 
  -Original Message-
  From: vdr-boun...@linuxtv.org
 [mailto:vdr-boun...@linuxtv.org]
 On Behalf Of
  Stuart Morris
  Sent: 9. joulukuuta 2011 11:48
  To: VDR Mailing List
  Subject: Re: [vdr] Using some mediaplayer as set top
 box player for VDR
 
  A replacement for the Hauppauge MediaMVP has been
 sought after for a long
  time.
  See this thread for a history:
  http://forum.loggytronic.com/index.php?topic=526.0
 
  --- On Wed, 7/12/11, Petric Frankpfr...@gmx.de 
 wrote:
 
  From: Petric Frankpfr...@gmx.de
  Subject: Re: [vdr] Using some mediaplayer as set
 top box player for
  VDR
  To: VDR Mailing Listvdr@linuxtv.org
  Date: Wednesday, 7 December, 2011, 23:01 Hello,
 
  Am Mittwoch, 7. Dezember 2011, 23:30:09 schrieb
 Dieter
  Hametner:
  Am Mittwoch, 7. Dezember 2011 schrieb Kartsa:
  I tried to find some comparison or like to
 find
  out if there a other
  mediaplayers to view recordings than
 MediMVP. My
  MediaMVP has started to
  act funny (=does not want to work) and I
 started
  to find a replacement
  for it. It seems to be quite difficulta
 task or I
  just havent found good
  sites. If someone has any pointers I
 would
  appreciate it.
  I was looking at Freeagent GoFlex TV HD
 and was
  wondering if it could be
  used as a playback device and then I
 started to
  google for some sites
  for different possibilities with no real
 luck. So
  if anyone has either
  any good sites to chack or any experience
 in set
  top boxes I would love
  to hear.
  You might want to look at
      http://www.raspberrypi.org/
  [dream on]
  If this box supports HDMI-CEC to use the remote
 control of the TV set
  to manage the VDR system ...
  [dream off]
 
  regards
     Petric
 
  ___
  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
 
 
 ___
 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] compile error vompserver

[Stuart Morris]

The problem has been reported on the Vomp forum:
http://forum.loggytronic.com/index.php?topic=602.0

No fix yet.

--- On Wed, 7/12/11, Andreas Hölscher andr...@andreas-hoelscher.de wrote:

 From: Andreas Hölscher andr...@andreas-hoelscher.de
 Subject: [vdr] compile error vompserver
 To: Klaus Schmidinger's VDR vdr@linuxtv.org
 Date: Wednesday, 7 December, 2011, 18:41
 Hallo,
 ich habe vor kurzem auf openSuSE 12.1 geupdated und wollte
 jetzt die
 aktuelle Version des VDR mit meinen Plugins kompilieren.
 Leider bekomme
 ich beim vompserver immer eine Fehlermeldung. Da ich keine
 Ahnung vom
 Programmieren habe, hoffe ich hier ein paar Tipps zu
 bekommen. Hier ist
 die Fehlermeldung:
  mediafile.c: In member function ‘virtual MediaList*
 MediaFile::getMediaList(const MediaURI*)’:
  mediafile.c:126:21: error: expected primary-expression
 before ‘struct’
  mediafile.c:126:36: error: ‘d_name’ was not
 declared in this scope
  mediafile.c:126:42: error: ‘offsetof’ was not
 declared in this scope
  mediafile.c:126:58: error: array bound is not an
 integer constant before ‘]’ token
 
 und hier die entsprechenden Zeilen aus der Datei
 mediafile.c:
  MediaList* MediaFile::getMediaList(const MediaURI *
 parent){
    ULONG
 mediaType=parent-getAllowedTypes();
    Log::getInstance()-log(MediaFile::getMediaList,Log::DEBUG,parent
 %s,types=0x%0lx,parent-getName(),mediaType);
    MediaList *rt=NULL;
    rt=new MediaList(parent);
    const char
 *dirname=parent-getName();
    //open the directory and read out the
 entries
    DIR *d=opendir(dirname);
    struct dirent *e;
    union { // according to The GNU C
 Library Reference Manual
      struct dirent d;
      char b[offsetof(struct dirent,
 d_name) + NAME_MAX + 1];
      } u;
 
 Zeile 126 ist char b[offsetof(struct dirent, d_name) +
 NAME_MAX + 1];
 
 Ich freue mich über jeden Tipp, bei Bedarf kann ich
 natürlich auch mehr
 Code zitieren, ich wollte die Zitate nicht zu lang werden
 lassen.
 
 Danke,
 Andreas
 
 
 openSuSE 12.1
 Kernel 3.1.0-1.2-desktop
 vdr 1.7.22
 vompserver 0.3.1-3-Yaris (von http://www.russle.net/vomp/)
 
 
 -- 
 Andreas Hölscher, Roetgen/Eifel
 http://www.andreas-hoelscher.de
 
 ___
 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 some mediaplayer as set top box player for VDR

[Stuart Morris]

A replacement for the Hauppauge MediaMVP has been sought after for a long time.
See this thread for a history:
http://forum.loggytronic.com/index.php?topic=526.0

--- On Wed, 7/12/11, Petric Frank pfr...@gmx.de wrote:

 From: Petric Frank pfr...@gmx.de
 Subject: Re: [vdr] Using some mediaplayer as set top box player for VDR
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 7 December, 2011, 23:01
 Hello,
 
 Am Mittwoch, 7. Dezember 2011, 23:30:09 schrieb Dieter
 Hametner:
  Am Mittwoch, 7. Dezember 2011 schrieb Kartsa:
   I tried to find some comparison or like to find
 out if there a other
   mediaplayers to view recordings than MediMVP. My
 MediaMVP has started to
   act funny (=does not want to work) and I started
 to find a replacement
   for it. It seems to be quite difficulta task or I
 just havent found good
   sites. If someone has any pointers I would
 appreciate it.
   
   I was looking at Freeagent GoFlex TV HD and was
 wondering if it could be
   used as a playback device and then I started to
 google for some sites
   for different possibilities with no real luck. So
 if anyone has either
   any good sites to chack or any experience in set
 top boxes I would love
   to hear.
  
  You might want to look at
    http://www.raspberrypi.org/
 
 [dream on]
 If this box supports HDMI-CEC to use the remote control of
 the TV set to 
 manage the VDR system ...
 [dream off]
 
 regards
   Petric
 
 ___
 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] Garbage time and date

[Stuart Morris]

I have set my VDR to update the system clock and this has been working
well for many years now. However I recently had a problem with my DVB-T
antenna system causing bad reception and it really screwed up the system
clock, ocasionally changing to the wrong date and time. I verified this
by looking at the system log.

I thought DVB packets were checked for integrity with a checksum.
How could this happen? Could it be that the shear volume of corrupted packets 
means that a simple checksum is not robust enough?

Thanks


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Epgsearch not avoiding repeats

[Stuart Morris]

My mistake...I think.
I had previously had this setting:
Compare subtitle yes
Which I later changed to no, but did not delete the timers it had already 
created. Once I deleted the timers and triggered an update I got zero repeats.

Am I correct in saying that with Compare subtitle set to yes, if there is no 
subtitle it is classed as different?

Apologies for my daft mistake confusing the word exert with excerpt :-/

--- On Sun, 30/10/11, Christian Wieninger cwienin...@gmx.de wrote:

 From: Christian Wieninger cwienin...@gmx.de
 Subject: Re: [vdr] Epgsearch not avoiding repeats
 To: VDR Mailing List vdr@linuxtv.org
 Date: Sunday, 30 October, 2011, 8:54
 Hi Stuart,
 
 please turn on the log file with '-v 2' and have a look at
 epgsearch.log 
 to see what's going on.
 
 cheers,
 Christian
 
 
 Am 29.10.2011 23:43, schrieb Stuart Morris:
  Hi
  Since upgrading to Epgsearch 1.0 I'm getting lots of
 repeat recordings.
  Please can anyone suggest what could be wrong here?
 
  To avoid repeats I have these settings:
  Avoid repeats yes
  Allowed repeats 0
  Compare title no
  Compare subtitle no
  Compare summary yes
  Min. match in % 90
  Compare date no
 
  Here is a exert from epgsearchdone.data:
 
  R 1319913000 1800 28
  C T-9018-8194-8258
  T Harry Hill's TV Burp
  D Harry Hill delivers his trademark take on the top
 shows on the box. Will he be looking for inspiration in the
 Downton Abbey pantry, on The X Factor or on Coach Trip's
 holiday? [S]
  @epgsearchchannel3 -
 ITV1/channelsearchtimerHarry Hill's TV
 Burp/searchtimerstart1319912880/startstop1319915400/stops-id28/s-ideventid32842/eventid/epgsearch
  r
  R 1319913000 1800 28
  C T-9018-16515-17603
  T Harry Hill's TV Burp
  D Harry Hill delivers his trademark take on the top
 shows on the box. Will he be looking for inspiration in the
 Downton Abbey pantry, on The X Factor or on Coach Trip's
 holiday? [Upscaled HD]
  @epgsearchchannel51 - ITV1
 HD/channelsearchtimerHarry Hill's TV
 Burp/searchtimerstart1319912880/startstop1319915400/stops-id28/s-ideventid32842/eventid/epgsearch
  r
  R 1319916600 1800 28
  C T-9018-8194-8357
  T Harry Hill's TV Burp
  D Harry Hill delivers his trademark take on the top
 shows on the box. Will he be looking for inspiration in the
 Downton Abbey pantry, on The X Factor or on Coach Trip's
 holiday? [S]
  @epgsearchchannel33 - ITV1
 +1/channelsearchtimerHarry Hill's TV
 Burp/searchtimerstart1319916480/startstop1319919000/stops-id28/s-ideventid32842/eventid/epgsearch
  r
 
  Thanks


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Epgsearch not avoiding repeats

[Stuart Morris]

Hi
Since upgrading to Epgsearch 1.0 I'm getting lots of repeat recordings.
Please can anyone suggest what could be wrong here?

To avoid repeats I have these settings:
Avoid repeats yes
Allowed repeats 0
Compare title no
Compare subtitle no
Compare summary yes
Min. match in % 90
Compare date no

Here is a exert from epgsearchdone.data:

R 1319913000 1800 28
C T-9018-8194-8258
T Harry Hill's TV Burp
D Harry Hill delivers his trademark take on the top shows on the box. Will he 
be looking for inspiration in the Downton Abbey pantry, on The X Factor or on 
Coach Trip's holiday? [S]
@ epgsearchchannel3 - ITV1/channelsearchtimerHarry Hill's TV 
Burp/searchtimerstart1319912880/startstop1319915400/stops-id28/s-ideventid32842/eventid/epgsearch
r
R 1319913000 1800 28
C T-9018-16515-17603
T Harry Hill's TV Burp
D Harry Hill delivers his trademark take on the top shows on the box. Will he 
be looking for inspiration in the Downton Abbey pantry, on The X Factor or on 
Coach Trip's holiday? [Upscaled HD]
@ epgsearchchannel51 - ITV1 HD/channelsearchtimerHarry Hill's TV 
Burp/searchtimerstart1319912880/startstop1319915400/stops-id28/s-ideventid32842/eventid/epgsearch
r
R 1319916600 1800 28
C T-9018-8194-8357
T Harry Hill's TV Burp
D Harry Hill delivers his trademark take on the top shows on the box. Will he 
be looking for inspiration in the Downton Abbey pantry, on The X Factor or on 
Coach Trip's holiday? [S]
@ epgsearchchannel33 - ITV1 +1/channelsearchtimerHarry Hill's TV 
Burp/searchtimerstart1319916480/startstop1319919000/stops-id28/s-ideventid32842/eventid/epgsearch
r

Thanks

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] eepg plugin with UK freeview (not freesat!) EPG

[Stuart Morris]

I too have seen occasional EPG data on other channels become garbled.

Is it possible that 'other transport stream' EIT data when received on the HD 
channel transport stream, is sometimes Huffman compressed? This of course is 
regardless whether the Eepg plugin is present or not.

--- On Sat, 27/8/11, Laz l...@club-burniston.co.uk wrote:

 From: Laz l...@club-burniston.co.uk
 Subject: Re: [vdr] eepg plugin with UK freeview (not freesat!) EPG
 To: VDR Mailing List vdr@linuxtv.org
 Date: Saturday, 27 August, 2011, 10:46
 On Saturday 27 August 2011 01:18:31
 Tony Houghton wrote:
  On Fri, 26 Aug 2011 20:42:38 +0100
  
  Laz l...@club-burniston.co.uk
 wrote:
   I thought it had been doing this scrambling when
 I tried it earlier
   in the week but have now proved it to myself.
   
   Time to start adding some more printfs...
  
  The first byte of encoded strings should be 0x1f,
 followed by 1 or 2
  indicating which table should be used (one is
 optimised for titles, the
  other for descriptions). Normal strings either start
 with a printable
  character for the default character set or a code 
 0x20 indicating the
  character set. I use eepg too, but I haven't noticed
 it scrambling
  anything (this is probably the first time I've looked
 at QVC's schedule
  though ;)).
 
 Over the evening, it scrambled more and more channels!
 
 :-s
 
 Thanks for the pointer to 0x1f! Now I know where to look.
 
 (I assume that eepg only decodes EPG that comes in over
 the air and doesn't 
 touch any EPG alread stored.)
 
 Laz
 
 ___
 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] FreeviewHD compressed EPG

[Stuart Morris]

In the absence of a modification to the Eepg plugin to decompress the
FreeviewHD EPG, I have applied the original Freesat.diff to my
installation of VDR 1.7.21 and have achieved some success accessing the
FreeviewHD EPG.

The patch is here:
http://www.rst38.org.uk/vdr/freesat.diff

The first hunk fails to apply but this is ok because that part of the
patch is relevant to freesat only.
The decompressed EPG has many 'holes' in it due to incomplete Huffman
lookup tables in the freesat.diff.
I did manage to port the Freesat lookup tables from the Eepg plugin to the 
freesat.diff and I can now receive what appears to be the complete FreeviewHD 
EPG :-)


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr-checkts + vdrnfofs

[Stuart Morris]

--- On Mon, 3/10/11, Tobi listacco...@e-tobi.net wrote:

 From: Tobi listacco...@e-tobi.net
 Subject: Re: [vdr] vdr-checkts + vdrnfofs
 To: vdr@linuxtv.org
 Date: Monday, 3 October, 2011, 11:16
 On 03.10.2011 11:39, Stuart Morris
 wrote:
 
  vdr-nfofs looks interesting. Can it be used in
 conjunction with a DLNA server like MiniDLNA? 
 
 Should work. Just make MiniDLNA's config point to the
 vdrnfofs file
 system. But I have no idea, if the *.nfo files are of any
 use to DLNA
 devices. And it might be a little bit slow if you have a
 lot of VDR
 recordings.
 
  Does it support H264 vdr recordings?
 
 It supports VDR 1.6 (001.vdr) and VDR 1.7.x (0001.ts). It
 doesn't care
 about the encoding. The VDR files are just virtually
 concatenated and
 presented as a single *.mpg file.
 
 Tobias

Sorry if this is obvious to others, but why do I get this error:
ImportError: No module named vdrnfofs

I know nothing of Python. Is there something else I need to install in addition 
to fuse-python?

Thanks
Stuart

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] vdr-checkts + vdrnfofs

[Stuart Morris]

--- On Sun, 2/10/11, Tobi listacco...@e-tobi.net wrote:

 From: Tobi listacco...@e-tobi.net
 Subject: [vdr] vdr-checkts + vdrnfofs
 To: VDR Mailing List vdr@linuxtv.org
 Date: Sunday, 2 October, 2011, 22:21
 Hi,
 
 Just in case someone finds them useful, I've just put two
 tiny tools online:
 
 vdr-checkts: checks VDR recordings for continuity errors
 
 http://projects.vdr-developer.org/git/vdr-checkts.git
 http://projects.vdr-developer.org/git/vdr-checkts.git/tree/README
 http://projects.vdr-developer.org/git/vdr-checkts.git/snapshot/vdr-checkts-0.1.tar.gz
 
 
 
 vdr-nfofs: A Fuse file system for VDR recordings, mapping
 them to
 *.mpg/*.nfo files
 
 http://projects.vdr-developer.org/git/vdrnfofs.git/
 http://projects.vdr-developer.org/git/vdrnfofs.git/tree/README
 http://projects.vdr-developer.org/git/vdrnfofs.git/snapshot/vdrnfofs-0.7.tar.gz
 
 Have fun,
 
 Tobias

vdr-nfofs looks interesting. Can it be used in conjunction with a DLNA server 
like MiniDLNA? The problem with DLNA servers I have tried is they present vdr 
recordings as a list of 1.ts files which is not user friendly.
Does it support H264 vdr recordings? I'm looking for a solution to view HD 
recordings on a TV using a thin client, like a DLNA client for example.

Stuart


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z

[Stuart Morris]

--- On Thu, 29/9/11, Stuart Morris stuart_mor...@talk21.com wrote:
 From: Stuart Morris stuart_mor...@talk21.com
 Subject: Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z
 To: VDR Mailing List vdr@linuxtv.org
 Date: Thursday, 29 September, 2011, 14:15
 
 
 --- On Thu, 29/9/11, Dominic Evans oldma...@gmail.com
 wrote:
 
  From: Dominic Evans oldma...@gmail.com
  Subject: Re: [vdr] eepg plugin + UK freeviewHD =
 }?Ln??X??Z?Z
  To: VDR Mailing List vdr@linuxtv.org
  Date: Thursday, 29 September, 2011, 13:25
  On 29 September 2011 13:14, Dominic
  Evans oldma...@gmail.com
  wrote:
   On 29 September 2011 13:00, Stuart Morris stuart_mor...@talk21.com
  wrote:
   Looking at the source code for Eepg it's not
  looking for the Freeview private data descriptor tag
  0x233a.
   Does anyone know where I could find
 information on
  Freeview descriptors?
   Would they be the same as Freesat?
  
   I doubt they would be the same, but perhaps
   http://deadpenguin.org/svn/dp/trunk/src/core_si.c is a
  start for you
   to investigate from?
  
  
  You probably need to get hold of a copy of the DTG
 D-Book
  to get
  actual documentation of the private data descriptors.
  
  http://www.dtg.org.uk/publications/books.html
 
 The Freeview private data descriptor I referred to above
 came from the Deadpenguin developer website. Unfortunately
 Deadpenguin does not appear to use the Freeview private data
 descriptor.
 
 The D-Book is THE reference, but £1 is rather steep
 for access to technical data.
 
 Are there any applications or libraries that can analyse
 DVB streams and list the descriptors?
 

Dvbsnoop shows the compressed epg data is in the event descriptor of the 
transport stream EIT. I should have realised earlier if I had run VDR without 
the Eepg plugin and seen the gibberish epg for Freeview HD channels was still 
there.

I'll try creating an issue on the Eepg plugin page of the VDR Projects website.


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z

[Stuart Morris]

--- On Sat, 17/9/11, Laz l...@club-burniston.co.uk wrote:

 From: Laz l...@club-burniston.co.uk
 Subject: Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z
 To: vdr@linuxtv.org
 Date: Saturday, 17 September, 2011, 20:49
 On Saturday 17 September 2011
 20:32:48 Stuart Morris wrote:
  I have installed the EEPG plugin from the experimental
 branch;
  http://projects.vdr-developer.org/projects/plg-eepg/repository/show?rev=exp
  erimental (last revision was 26/08/2011), but I am
 getting gibberish in the
  EPG for the FreeviewHD channels.
  
  Does anyone know of a fix for this?
 
 That's exactly what I was getting when I tried it a couple
 of weeks back: it 
 didn't seem to touch the EPG for the HD channels (which are
 encoded) but I 
 also saw it trying to decode the EPG for other channels so
 I was seeing 
 gibberish creeping in at random for other channels.
 
 I gave up for now because I can only currently play back HD
 stuff off line on 
 a beefier machine!
 
 As I understand it, it's all just meant to work.
 
 Cheers,
 
 Laz
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

I uncommented #define DEBUG, recompiled and enabled full verbosity
for logging in the Eepg plugin osd menu. The system log shows that
the Eepg plugin is ignoring the Freeview/FreeviewHD extended epg:

Sep 29 08:14:11 localhost vdr: [28047] EEPG: Ended all processing
Sep 29 08:14:11 localhost vdr: [28047] EEPG: PMT scan idle
Sep 29 08:14:11 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:11 localhost vdr: [28047] EEPG: PMT pid now 0x02d5 (idx=19)
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT pid now 0x02d4 (idx=18)
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT pid now 0x02d3 (idx=17)
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT pid now 0x02d2 (idx=16)
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT pid now 0x02d0 (idx=15)
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT pid now 0x02cb (idx=14)
Sep 29 08:14:10 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT pid now 0x02c9 (idx=13)
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT pid now 0x02c7 (idx=12)
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT pid now 0x02c6 (idx=11)
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT pid now 0x02ce (idx=10)
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT pid now 0x02ca (idx=9)
Sep 29 08:14:09 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT pid now 0x02c2 (idx=8)
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT pid now 0x02c3 (idx=7)
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT pid now 0x02cc (idx=6)
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:08 localhost vdr: [28047] EEPG: PMT pid now 0x02c1 (idx=5)
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT pid now 0x02c0 (idx=4)
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT pid now 0x02cf (idx=3)
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT pid now 0x02bf (idx=2)
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT pid now 0x02d7 (idx=1)
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT next
Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT pid now 0x02bd (idx=0)
Sep 29 08:14:07 localhost vdr: [28047] EEPG: trigger
Sep 29 08:14:07 localhost vdr: [28047] EEPG: Filter Pid:0,Tid:0 added.
Sep 29 08:14:07 localhost vdr: [28047] EEPG: setstatus 1
Sep 29 08:14:07 localhost vdr: [28047] EEPG: trigger
Sep 29 08:14:07 localhost vdr: [28047] EEPG: setstatus 0
Sep 29 08:14:05 localhost vdr: [28041] EEPG: trigger
Sep 29 08:14:05 localhost vdr: [28041] EEPG: setstatus 0

Does anyone know how the Eepg plugin detects supported systems like
Freesat, Sky UK, Mediahighway etc?

Stuart


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z

[Stuart Morris]

--- On Thu, 29/9/11, Stuart Morris stuart_mor...@talk21.com wrote:

 From: Stuart Morris stuart_mor...@talk21.com
 Subject: Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z
 To: VDR Mailing List vdr@linuxtv.org
 Date: Thursday, 29 September, 2011, 10:12
 
 
 --- On Sat, 17/9/11, Laz l...@club-burniston.co.uk
 wrote:
 
  From: Laz l...@club-burniston.co.uk
  Subject: Re: [vdr] eepg plugin + UK freeviewHD =
 }?Ln??X??Z?Z
  To: vdr@linuxtv.org
  Date: Saturday, 17 September, 2011, 20:49
  On Saturday 17 September 2011
  20:32:48 Stuart Morris wrote:
   I have installed the EEPG plugin from the
 experimental
  branch;
   http://projects.vdr-developer.org/projects/plg-eepg/repository/show?rev=exp
   erimental (last revision was 26/08/2011), but I
 am
  getting gibberish in the
   EPG for the FreeviewHD channels.
   
   Does anyone know of a fix for this?
  
  That's exactly what I was getting when I tried it a
 couple
  of weeks back: it 
  didn't seem to touch the EPG for the HD channels
 (which are
  encoded) but I 
  also saw it trying to decode the EPG for other
 channels so
  I was seeing 
  gibberish creeping in at random for other channels.
  
  I gave up for now because I can only currently play
 back HD
  stuff off line on 
  a beefier machine!
  
  As I understand it, it's all just meant to work.
  
  Cheers,
  
  Laz
  
  ___
  vdr mailing list
  vdr@linuxtv.org
  http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
  
 
 I uncommented #define DEBUG, recompiled and enabled full
 verbosity
 for logging in the Eepg plugin osd menu. The system log
 shows that
 the Eepg plugin is ignoring the Freeview/FreeviewHD
 extended epg:
 
 Sep 29 08:14:11 localhost vdr: [28047] EEPG: Ended all
 processing
 Sep 29 08:14:11 localhost vdr: [28047] EEPG: PMT scan idle
 Sep 29 08:14:11 localhost vdr: [28047] EEPG: PMT next
 Sep 29 08:14:11 localhost vdr: [28047] EEPG: PMT pid now
 0x02d5 (idx=19)
..snip..
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT next
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: PMT pid now
 0x02bd (idx=0)
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: trigger
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: Filter
 Pid:0,Tid:0 added.
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: setstatus 1
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: trigger
 Sep 29 08:14:07 localhost vdr: [28047] EEPG: setstatus 0
 Sep 29 08:14:05 localhost vdr: [28041] EEPG: trigger
 Sep 29 08:14:05 localhost vdr: [28041] EEPG: setstatus 0
 
 Does anyone know how the Eepg plugin detects supported
 systems like
 Freesat, Sky UK, Mediahighway etc?
 
 Stuart
 
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

Looking at the source code for Eepg it's not looking for the Freeview private 
data descriptor tag 0x233a.
Does anyone know where I could find information on Freeview descriptors?
Would they be the same as Freesat?

Stuart


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z

[Stuart Morris]

--- On Thu, 29/9/11, Dominic Evans oldma...@gmail.com wrote:

 From: Dominic Evans oldma...@gmail.com
 Subject: Re: [vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z
 To: VDR Mailing List vdr@linuxtv.org
 Date: Thursday, 29 September, 2011, 13:25
 On 29 September 2011 13:14, Dominic
 Evans oldma...@gmail.com
 wrote:
  On 29 September 2011 13:00, Stuart Morris stuart_mor...@talk21.com
 wrote:
  Looking at the source code for Eepg it's not
 looking for the Freeview private data descriptor tag
 0x233a.
  Does anyone know where I could find information on
 Freeview descriptors?
  Would they be the same as Freesat?
 
  I doubt they would be the same, but perhaps
  http://deadpenguin.org/svn/dp/trunk/src/core_si.c is a
 start for you
  to investigate from?
 
 
 You probably need to get hold of a copy of the DTG D-Book
 to get
 actual documentation of the private data descriptors.
 
 http://www.dtg.org.uk/publications/books.html

The Freeview private data descriptor I referred to above came from the 
Deadpenguin developer website. Unfortunately Deadpenguin does not appear to use 
the Freeview private data descriptor.

The D-Book is THE reference, but £1 is rather steep for access to technical 
data.

Are there any applications or libraries that can analyse DVB streams and list 
the descriptors?

Thanks
Stuart

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] eepg plugin + UK freeviewHD = }?Ln??X??Z?Z

[Stuart Morris]

I have installed the EEPG plugin from the experimental branch;
http://projects.vdr-developer.org/projects/plg-eepg/repository/show?rev=experimental
(last revision was 26/08/2011), but I am getting gibberish in the EPG for the 
FreeviewHD channels.

Does anyone know of a fix for this?

Thanks


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] xine 1.2 vaapi

[Stuart Morris]

Does anyone know how one can enable vaapi in xine 1.2?

I've got an AMD HD4200 motherboard graphics system working ok with 
MPlayer-vaapi.
I have built FFMPEG with VAAPI but I don't know how to test if that works.
I would like to watch UK FreeviewHD using Xineliboutput or Xine plugins.

Thanks


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] FreeviewHD success with Nanostick 290e

[Stuart Morris]

Hi
I too have just acquired a 290e and I am having difficulty getting it to work 
with VDR.
Apart from the flakey driver at the moment, 'seeding' VDR's channel.conf is 
difficult. I tried using w_scan like this:

w_scan -c GB -o 7 -I my_init_tune_file

My tuning file (UK Sandy Heath) contained 1 line like this:
T 474166670 8MHz 2/3 NONE QAM256 32k 1/32 NONE

w_scan produced this:
BBC HD;BBC:474166670:I999B8C23D0M998T999G32Y0:T:27500:101:0:0:0:17472:0:0:0
BBC One HD;BBC:474166670:I999B8C23D0M998T999G32Y0:T:27500:6601:0:0:0:17540:0:0:0
ITV1 HD;ITV:474166670:I999B8C23D0M998T999G32Y0:T:27500:201:0:0:0:17603:0:0:0
Channel 4 HD;CHANNEL 
FOUR:474166670:I999B8C23D0M998T999G32Y0:T:27500:301:0:0:0:17664:0:0:0

However, VDR uses the first available tuning device when one of these channels 
is selected, which happens to be a DVB-T device and not the 290e DVB-T2 device.

Is this a problem with channels.conf or do I need to use a later version of 
VDR? I am currently using VDR 1.7.15.

Laz how exactly did you 'seed' your channels.conf?

Thanks
Stuart

--- On Fri, 19/8/11, Laz l...@club-burniston.co.uk wrote:

 From: Laz l...@club-burniston.co.uk
 Subject: [vdr] FreeviewHD success with Nanostick 290e
 To: Chris Rankin ranki...@yahoo.com, VDR Mailing List vdr@linuxtv.org
 Date: Friday, 19 August, 2011, 8:55
 
 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.
 
 It was clever enough to switch to the Nanostick for the HD
 mux because it's 
 the only device that can do QAM256 (not sure if _only_
 DVB-T2 includes QAM256 
 or whether my other devices are too old ot do it as part of
 DVB-T).
 
 I get now/next EPG for the HD channels but it's encrypted
 (it needs a plugin 
 to decode, from what others have said).
 
 If I switch to BBC One HD, femon gives me a video bit-rate
 of about 7 Mbit / s 
 and an audio bit-rate of about 150 kbit / s. It claims to
 have a signal 
 strength of 70% but I'm not sure I believe that! By
 comparison, BBC One gives 
 me something like 3 Mbit / sv video and 260 kbit / s audio,
 and signal 
 strength of 70%.
 
 vdr has now written out the new entries to channels.conf:
 
 BBC 
 HD;BBC:61800:B8C23D23M256Y0:T:0:101=27:102=eng@17,106=eng@17:0:0:17472:9018:16516:0
 ITV1 
 HD;ITV:61800:B8C23D23M256Y0:T:0:201=27:202=eng@17,206=eng@17:0:0:17604:9018:16516:0
 Channel 4 HD;CHANNEL 
 FOUR:61800:B8C23D23M256Y0:T:0:301=27:302=eng@17,306=eng@17:0:0:17664:9018:16516:0
 BBC One 
 HD;BBC:61800:B8C23D23M256Y0:T:0:6601=27:6602=eng@17,6606=eng@17:0:0:17540:9018:16516:0
 
 These are from the Emley Moor transmitter (I'm not sure how
 whether PIDs, 
 etc., are the same between different transmitters but it
 might help someone.)
 
 I'm not seeing anything on my tele' but I suspect my output
 device (a Matrox 
 G450 with softdevice) can't go up to that high a
 resolution! Actually, I don't 
 think it will currently play anything other than MPEG2.
 
 I have a recording going from BBC One HD and there is a
 1.ts file which is 
 growing rapidly.
 
 I just played it back on a different PC. Mplayer output:
 
 Playing 1.ts.
 TS file format detected.
 VIDEO H264(pid=6601) AUDIO AAC LATM(pid=6602) SUB
 DVB(pid=6605)  PROGRAM N. 
 132
 FPS seems to be: 25.00
 Load subtitles in ./
 ==
 Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec
 family
 Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
 ==
 ==
 Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio
 decoders
 AUDIO: 48000 Hz, 2 ch, s16le, 0.0 kbit/0.00% (ratio:
 0-192000)
 Selected audio codec: [fflatm] afm: ffmpeg (FFmpeg AAC in
 LATM)
 ==
 AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
 Starting playback...
 Unsupported PixelFormat 61
 Unsupported PixelFormat 53
 [h264 @ 0xeccca0]mmco: unref short failure
 Movie-Aspect is 1.78:1 - prescaling to correct movie
 aspect.
 VO: [vdpau] 1440x1080 = 1920x1080 Planar YV12 
 
 Looking good!
 
 As far as I can tell, it seems to be working.
 
 :-)
 
 Next step, get the epg sorted out...
 
 Cheers,
 
 Laz
 
 ___
 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] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Sat, 22/1/11, Niko Mikkilä n...@phnet.fi wrote:

 From: Niko Mikkilä n...@phnet.fi
 Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
 To: VDR Mailing List vdr@linuxtv.org
 Date: Saturday, 22 January, 2011, 17:17
 On 2011-01-22 08:16 +0100, Thomas
 Hilber wrote:
  On Wed, Jan 19, 2011 at 12:42:40PM +, Stuart
 Morris wrote:
   conversion and then draw the first field to the
 frame buffer. At the next
   vertical sync the shader would convert the second
 field and draw that to
   the frame buffer. With VDPAU is there a new
 OpenGL interop function that
  
  that's not the whole story. You still have to consider
 synchronicity between
  incoming data rate (TV-stream) and outgoing data rate
 (VGA/Video timing).
 
 Yep. As Stuart said, framedrops/duplicates will happen, but
 with his
 drawing technique they don't cause the player to lose field
 sync. I
 think that's already quite acceptable, since at least
 recordings can be
 played without any video judder if audio is resampled.
 
 --Niko

Standard definition video is going to be harder than I thought.
I used xrandr to set this mode via HDMI to my LCD TV:
# 1440x576i @ 50Hz (EIA/CEA-861B)
ModeLine 1440x576 27.000 1440 1464 1590 1728 576 581 587 625 -hsync -vsync 
Interlace
The TV reported mode 576i ok, but the desktop graphics were unreadable.
I tried to view an interlaced standard def video using my little test 
application and it looked awful.
However the 1080i mode worked very well:
# 1920x1080i @ 50Hz (EIA/CEA-861B)
Modeline 1920x1080 74.250 1920 2448 2492 2640 1080 1085 1095 1125 +hsync 
+vsync Interlace

I think for standard definition video via HDMI there will be a need to
upscale to a resolution better supported by HDMI and that requires
inverse telecine and deinterlacing. This may still be within the
capabilities of todays low power systems.

My little test has staisfied me that 1080i or 1080p video can be displayed
with interlaced output.

Stuart

BTW my hardware setup was an old Sony KDL32V2000, and AMD HD4200 integrated 
graphics with the AMD closed driver.



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Fri, 28/1/11, Lucian Muresan luci...@users.sourceforge.net wrote:

 From: Lucian Muresan luci...@users.sourceforge.net
 Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
 To: VDR Mailing List vdr@linuxtv.org
 Date: Friday, 28 January, 2011, 11:37
 On 28.01.2011 10:57, Stuart Morris
 wrote:
 [..]
  Standard definition video is going to be harder than I
 thought.
  I used xrandr to set this mode via HDMI to my LCD TV:
  # 1440x576i @ 50Hz (EIA/CEA-861B)
  ModeLine 1440x576 27.000 1440 1464 1590 1728 576 581
 587 625 -hsync -vsync Interlace
  The TV reported mode 576i ok, but the desktop graphics
 were unreadable.
 
 I guess that's because it's a very strange resolution with
 strange
 aspect ratio, shouldn't that have been 1024x576i to
 maintain a 16:9
 aspect ratio with square pixels? I only found 1440 on BBC
 HD which
 broadcasts in 1080i but sets the aspect ratio flag to
 16:9...
 
 Lucian

The HDMI spec has a minimum pixel clock rate, such that modes like 576i
and 480i must repeat horizontal pixels to maintain a pixel rate above the
minimum. There is also an embedded information field in the HDMI link that
tells the HDMI sink (the TV) which pixel(s) to discard. There appears to
be no way to control this information and the graphics card I assume is
interpolating horizontally anyway (not repeating). This might explain why
the display looked so awful.

Stuart



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Deinterlace video

[Stuart Morris]

I believe the issue with this flag is understandable when you consider the
very simple nature of most set-top boxes decoding broadcast digital TV. It
will always send video to the TV interlaced regardless of the content. So
it does not care about de-interlacing. However it does need to know how to
convert the decoded frame colour space and for this the interlace flag I
suspect can be relied upon.

If the content is flagged as interlaced, separate the decoded YUV frame
into separate YUV fields then convert to RGB. If the flag is clear convert
the decoded YUV frame to RGB. For all material send to the TV interlaced
at the appropriate resolution.

This will also be important if the applicatgion is ever likely to display video 
media other than broadcast TV where it is flagged as progressive.

If however you wish to de-interlace the picture you will need
sophisticated pulldown detection which will disable the deinterlacer when
progressive content is detected. To detect 2:2 pulldown for example
(typical progressive source material broadcast in the UK) you would need
to detect combing artefacts within successive decoded frames. No
combing/mouse teeth for several consecutive frames would then cause the
de-interlacer to be disabled.

3:2 pulldown is a little easier to detect because there are flags to
indicate fields must be repeated. However reconstruction and display of
3:2 video is more complicated.

--- On Wed, 19/1/11, Timothy D. Lenz tl...@vorgon.com wrote:

 From: Timothy D. Lenz tl...@vorgon.com
 Subject: Re: [vdr] Deinterlace video
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 19 January, 2011, 19:25
 Is it possible to figure out if the
 stream is interlaced or not by looking at the stream? Seems
 like it should be able to figure out within a frame or two
 (.033ms) and then just ignore the useless flags? Needs to be
 done with epg data. I think the Insignia boxes just try to
 read data regardless of flags because they are able to find
 data when atscepg won't.
 
 On 1/19/2011 8:55 AM, VDR User wrote:
  On Wed, Jan 19, 2011 at 5:47 AM, Tony Houghtonh...@realh.co.uk 
 wrote:
  I thought there was supposed to be a flag in MPEG
 meta data which
  indicates whether pairs of fields are interlaced
 or progressive so
  decoders can determine how to combine them without
 doing any complicated
  picture analysis. Are broadcasters not using the
 flag properly, or xine
  not reading it? xine-ui's preferences dialog has
 an option to disable
  interlacing for progressive material, have you set
 that in whichever
  front-end you're using?
  
  There is.  Unfortunately I can't begin to count
 the number of times
  I've seen the flag set incorrectly, essentially making
 it useless.
  
  ___
  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] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Tue, 18/1/11, Niko Mikkilä n...@phnet.fi wrote:

 From: Niko Mikkilä n...@phnet.fi
 Subject: Re: [vdr] Replacing aging VDR for DVB-S2
 To: VDR Mailing List vdr@linuxtv.org
 Date: Tuesday, 18 January, 2011, 13:06
 On 2011-01-15 22:36 +, Tony
 Houghton wrote:
 
  I wonder whether it might be possible to use a more
 eonomical card
 which
  is only powerful enough to decode 1080i without
 deinterlacing it and
  take advantage of the abundant CPU power most people
 have nowadays to
  perform software deinterlacing. It may not be possible
 to have
 something
  as sophisticated as NVidia's temporal + spatial, but
 some of the
  existing software filters should scale up to HD
 without overloading
 the
  CPU seeing as it wouldn't be doing the decoding too.
 
 It's possible, but realtime GPU deinterlacing is more
 energy-efficient:
 
 - For CPU deinterlacing, you'd need something like
 Greedy2Frame or
 TomsMoComp. They should give about the same quality as
 Nvidia's temporal
 deinterlacer, but the code would need to be threaded to
 support
 lower-frequency multicore CPUs.
 
 Yadif almost matches temporal+spatial in quality, but it
 will also be
 about 50% slower than Greedy2Frame.
 
 - Hardware-decoded video is already in the GPU memory and
 moving
 1920x1080-pixel frames around is not free.
 
 - Simple motion-adaptive, edge-interpolating deinterlacing
 can be easily
 parallelized for GPU architectures, so it will be more
 efficient than on
 a serial processor. For example, GT 220 can do 1080i
 deinterlacing at
 more than 150 fps (output). Normal 50 fps deinterlacing
 only causes
 partial load and power consumption. GT 430 is currently
 worse because of
 an unoptimized filter implementation:
 http://nvnews.net/vbulletin/showthread.php?p=2377750#post2377750
 
 Still, only the latest CPU generation can reach that kind
 of performance
 with a highly optimized software deinterlacer.
 
  
  Alternatively, use software decoding, and hardware
 deinterlacing.
 
 GPU video decoding is very efficient thanks to dedicated
 hardware. I'd
 guess that current chips only use about 3 Watts for
 high-bitrate
 1080i25.
 
 Also, decoding and filtering aren't executed on the same
 parts of the
 GPU chip. They are almost perfectly parallel processes, so
 combined
 throughput will be that of the slower process.
 
 
  Somewhere on linuxtv.org there's an article about
 using fairly simple
  OpenGL to mimic what happens to interlaced video on a
 CRT, but I don't
  know how good the results would look.
 
 Sounds like normal bobbing with interpolation. Even if it
 simulates a
 phosphor delay, it probably won't look much better than
 MPlayer's -vf
 tfields or the bobber in VDPAU.
 
 Sharp interlaced (and progressive) video is quite flickery
 on a CRT too.
 
 
  BTW, speaking of temporal and spatial deinterlacing:
 AFAICT one means
  combining fields to provide maximum resolution with
 half the frame
 rate
  of the interlaced fields, and the other maximises the
 frame rate while
  discarding resolution; but which is which? And does
 NVidia's temporal
 +
  spatial try to give the best of both worlds through
 some sort of
  interpolation?
 
 Temporal = motion adaptive deinterlacing at either half or
 full field
 rate. Some programs refer to the latter by 2x. Motion
 adaptive means
 that the filter detects interlaced parts of each frame and
 adjusts
 deinterlacing accordingly. This gives better quality at
 stationary
 parts.
 
 Temporal-spatial = Temporal with edge-directed
 interpolation to smooth
 jagged edges of moving objects.
 
 Both methods give about the same spatial and temporal
 resolution but
 temporal-spatial will look nicer.
 
 --Niko
 
 
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

My experience with an nVidia GT220 has been less than perfect. It can perform 
temporal+spatial+inverse_telecine on HD video fast enough, but my PC gets hot 
and it truly sucks at 2:2 pulldown detection. The result of this is when 
viewing progressive video encoded as interlaced field pairs (2:2 pulldown), 
deinterlacing keeps cutting in and out every second or so, ruining the picture 
quality.

IMHO the best way to go for a low power HTPC is to decode in hardware e.g. 
VDPAU, VAAPI, but output interlaced video to your TV and let the TV sort out 
deinterlacing and inverse telecine.

I have experimented using FFMPEG and OpenGL and I achieved a very good quality 
picture on a 1080i CRT monitor (I have yet to try an HDMI flat panel TV).

These are the key requirements to achieve interlaced output:

Get the right modelines for your video card and TV.
Draw interlaced fields to your frame buffer at field rate and in the correct 
order (top field first or bottom field first).
When drawing the field to the frame buffer, do not overwrite the previous field 
still in the frame buffer.
Maintain 1:1 vertical scaling (no vertical scaling), so you will need to 

Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Wed, 19/1/11, Niko Mikkilä n...@phnet.fi wrote:

 From: Niko Mikkilä n...@phnet.fi
 Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 19 January, 2011, 11:43
 Replying to myself...
 
 ke, 2011-01-19 kello 12:48 +0200, Niko Mikkilä kirjoitti:
  ke, 2011-01-19 kello 10:18 +, Stuart Morris
 kirjoitti:
   My experience with an nVidia GT220 has been less
 than perfect. It can
   perform temporal+spatial+inverse_telecine on HD
 video fast enough, but
   my PC gets hot and it truly sucks at 2:2 pulldown
 detection. The
   result of this is when viewing progressive video
 encoded as interlaced
   field pairs (2:2 pulldown), deinterlacing keeps
 cutting in and out
   every second or so, ruining the picture quality.
  
  I think VDPAU's inverse telecine is only meant for
 non-even cadences
  like 3:2. Motion-adaptive deinterlacing handles 2:2
 pullup perfectly
  well, so try without IVTC.
 
 Not perfectly well apparenty; there will be slight
 artifacting at sharp
 horizontal edges, so the trigger to deinterlace is pretty
 low. Probably
 to avoid any visible combing in interlaced video.
 
 Pullup seems to work fine for me though, but I only have
 VP2/VDPAU
 feature set A hardware.

My problems with VDPAU inverse-telecine were apparent only on HD video.
It did seem to be ok with SD video.
With HD video, if I disabled inverse-telecine and left the advanced
deinterlacer on, it (not surprisingly) deinterlaces the progressive
picture resulting in loss of detail and twittering.
For progressive HD material I have to manually turn off deinterlacing,
then turn it on again for interlaced material. That's annoying.



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Wed, 19/1/11, Torgeir Veimo torg...@netenviron.com wrote:

 From: Torgeir Veimo torg...@netenviron.com
 Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 19 January, 2011, 11:24
 On 19 January 2011 20:18, Stuart
 Morris stuart_mor...@talk21.com
 wrote:
  IMHO the best way to go for a low power HTPC is to
 decode in hardware e.g. VDPAU, VAAPI, but output interlaced
 video to your TV and let the TV sort out deinterlacing and
 inverse telecine.
 
 Unfortunately, with VDPAU, the hardware combines fields
 into frames,
 then scales, which results in ghosting with interlaced
 material.
 
 So this approach would not work with stock xineliboutput,
 which uses a
 fixed output resolution. If you could avoid the scaling
 altogether
 with interlaced material, eg with a modified xineliboutput
 setup, then
 this would be feasible I guess.

One would need to be able to access the decoded frame containing 2 fields
and perhaps use an OpenGL shader to perform field based colour space
conversion and then draw the first field to the frame buffer. At the next
vertical sync the shader would convert the second field and draw that to
the frame buffer. With VDPAU is there a new OpenGL interop function that
allows access to the decoded frame?

I should add I have not yet ventured into writing OpenGL shaders!

Stu-e



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Wed, 19/1/11, Niko Mikkilä n...@phnet.fi wrote:

 From: Niko Mikkilä n...@phnet.fi
 Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 19 January, 2011, 10:48
 ke, 2011-01-19 kello 10:18 +,
 Stuart Morris kirjoitti:
  My experience with an nVidia GT220 has been less than
 perfect. It can
  perform temporal+spatial+inverse_telecine on HD video
 fast enough, but
  my PC gets hot and it truly sucks at 2:2 pulldown
 detection. The
  result of this is when viewing progressive video
 encoded as interlaced
  field pairs (2:2 pulldown), deinterlacing keeps
 cutting in and out
  every second or so, ruining the picture quality.
 
 I think VDPAU's inverse telecine is only meant for non-even
 cadences
 like 3:2. Motion-adaptive deinterlacing handles 2:2 pullup
 perfectly
 well, so try without IVTC.
 
 
  IMHO the best way to go for a low power HTPC is to
 decode in hardware
  e.g. VDPAU, VAAPI, but output interlaced video to your
 TV and let the
  TV sort out deinterlacing and inverse telecine.
 
 Well, flat panel TVs have similar deinterlacing algorithms
 as what VDPAU
 provides, but it would certainly be a nice alternative.
 
  These are the key requirements to achieve interlaced
 output:
  
  Get the right modelines for your video card and TV.
 Draw interlaced
  fields to your frame buffer at field rate and in the
 correct order
  (top field first or bottom field first). When drawing
 the field to the
  frame buffer, do not overwrite the previous field
 still in the frame
  buffer. Maintain 1:1 vertical scaling (no vertical
 scaling), so you
  will need to switch video output to match the source
 video height
  (480i, 576i or 1080i). Display the frame buffer at
 field rate and
  synchronised to the graphics card vertical sync.
 Finally, there is NO
  requirement to synchronise fields, fields are always
 displayed in the
  same order they are written to the frame buffer, even
 if occasionally
  fields are dropped.
 
 Interesting. Could you perhaps write full instructions to
 some suitable
 wiki and post the code that you used to do this? I'm sure
 others would
 like to try it too.

I can provide the simple bit of source code I have used to demonstrate the 
basic principle. Please see attached.


  

#include stdio.h
#include stdlib.h

#include libavcodec/avcodec.h
#include libavformat/avformat.h
#include libswscale/swscale.h

#include SDL/SDL.h
#include GL/gl.h

#ifdef __MINGW32__
#undef main /* Prevents SDL from overriding main() */
#endif

int main(int argc, char *argv[])
{
AVFormatContext *pFormatCtx;
int i, j, k, videoStream;
AVCodecContext  *pCodecCtx;
AVCodec *pCodec;
AVFrame *pFrame;
AVPacketpacket;
int frameFinished;
struct SwsContext *img_convert_ctx;
float   aspect_ratio;
int frmcnt = 0;
int DispList;

SDL_Surface *screen;
SDL_Event   event;

if (argc  2)
{
fprintf(stderr, Usage: test file\n);
exit(1);
}
// Register all formats and codecs
av_register_all();

if (SDL_Init(SDL_INIT_VIDEO | SDL_INIT_AUDIO | SDL_INIT_TIMER))
{
fprintf(stderr, Could not initialize SDL - %s\n, SDL_GetError());
exit(1);
}

// Open video file
if (av_open_input_file(pFormatCtx, argv[1], NULL, 0, NULL)!=0)
return -1; // Couldn't open file

// Retrieve stream information
if (av_find_stream_info(pFormatCtx)0)
return -1; // Couldn't find stream information

// Dump information about file onto standard error
dump_format(pFormatCtx, 0, argv[1], 0);

// Find the first video stream
videoStream=-1;
for (i=0; ipFormatCtx-nb_streams; i++)
if (pFormatCtx-streams[i]-codec-codec_type==CODEC_TYPE_VIDEO)
{
videoStream=i;
break;
}
if (videoStream==-1)
return -1; // Didn't find a video stream

// Get a pointer to the codec context for the video stream
pCodecCtx=pFormatCtx-streams[videoStream]-codec;

// Find the decoder for the video stream
pCodec=avcodec_find_decoder(pCodecCtx-codec_id);
if (pCodec==NULL)
{
fprintf(stderr, Unsupported codec!\n);
return -1; // Codec not found
}

// Open codec
pCodecCtx-thread_count = 2; // Use 2 processor cores if available
if (avcodec_open(pCodecCtx, pCodec)0)
return -1; // Could not open codec

// Allocate video frame
pFrame=avcodec_alloc_frame();

// Calculate aspect ratio
if (pCodecCtx-sample_aspect_ratio.num == 0) aspect_ratio = 0.0;
else aspect_ratio = av_q2d(pCodecCtx-sample_aspect_ratio) * 
pCodecCtx-width / pCodecCtx-height;
if (aspect_ratio = 0.0) aspect_ratio = (float)pCodecCtx-width / 
(float)pCodecCtx-height;
fprintf(stderr, Aspect ratio = %f by %d\n, 
pCodecCtx-height*aspect_ratio, pCodecCtx-height

Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)

[Stuart Morris]

--- On Wed, 19/1/11, Torgeir Veimo torg...@netenviron.com wrote:

 From: Torgeir Veimo torg...@netenviron.com
 Subject: Re: [vdr] Deinterlace video (was: Replacing aging VDR for DVB-S2)
 To: VDR Mailing List vdr@linuxtv.org
 Date: Wednesday, 19 January, 2011, 13:50
 On 19 January 2011 23:47, Tony
 Houghton h...@realh.co.uk
 wrote:
  I thought there was supposed to be a flag in MPEG meta
 data which
  indicates whether pairs of fields are interlaced or
 progressive so
  decoders can determine how to combine them without
 doing any complicated
  picture analysis. Are broadcasters not using the flag
 properly [...]
 
 Broadcasters can't even get the EPG data correct.


In my limited experience, watching UK Freeview recordings made with VDR,
using Xines TVtime deinterlacer, with the progressive frame flag option
set, deinterlace is on all of the time including video derived from a
progressive film source, which is wrong.

I think it is safe to rely on this flag for deciding on whether to convert
colour space in fields or frames, but it seems it gives you no clues
whether to deinterlace or not.



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] reelchannelscan not working with empty channels.conf!

[Stuart Morris]

--- On Fri, 22/10/10, Luca Olivetti l...@ventoso.org wrote:

 From: Luca Olivetti l...@ventoso.org
 Subject: Re: [vdr] reelchannelscan not working with empty channels.conf!
 To: VDR Mailing List vdr@linuxtv.org
 Date: Friday, 22 October, 2010, 10:04
 En/na Halim Sahin ha escrit:
  Hi,
  On Thu, Oct 21, 2010 at 10:03:05PM +0400, Goga777
 wrote:
  have a look on actuator plugin from Luca
  http://www.ventoso.org/luca/vdr/
  
  I read only about dvb-s/s2 support in the
 announcement. Unfortunately in need also dvb-t and maybe
  later dvb-c (I am looking for dvb-c hw currently
 :-().
 
 Yes, unfortunately it only supports dvb-s/s2 (don't forget
 it's meant to work as an actuator, channel tuning/scanning
 is just an aid to point the dish).
 It also currently work with only one card (the card
 connected to the motor), so it'll probably fail in multiple
 cards setups.
 I don't think I can easily adapt it to dvb-t/dvb-c :-(
 
 Bye
 -- Luca
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

Have you tried the wirbelscan plugin?



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] streamdev for xbmc testing-pvr2

[Stuart Morris]

Oh yes I was on to that in a flash.
Things are much improved but still not good enough for my 'production' setup.

You can select VDPAU rendering and temporal/spatial de-interlace for h264 video 
(SD and HD) giving fluid 50Hz frame rate. But when you then watch some mpeg2 
content it falls back to software rendering and the standard 25Hz de-interlace.

Have posted a question on the XBMC forum whether it is possible to select VDPAU 
(and hence VDPAU de-interlace) for both h264 and mpeg2 decoders. The XBMC forum 
is incredibly busy so I am sceptical I will get a response.

BTW
My setup with XBMC is now:

XBMC svn checkout
http://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/pvr-testing2

VDR 1.7.11 (unpatched!)

cvs streamdev with all patches applied from 
pvr-testing2/pvr-addons/streamdev/patches directory.

Stuart

--- On Fri, 22/1/10, Goga777 goga...@bk.ru wrote:

 From: Goga777 goga...@bk.ru
 Subject: Re: [vdr] streamdev for xbmc testing-pvr2
 To: vdr@linuxtv.org
 Date: Friday, 22 January, 2010, 20:48
  I am using that version of
 streamdev with pvr-testing2 ok.
  This is my setup:
  
  Streamdev plugin for XBMC
  http://streamdev.vdr-developer.org/
  
  http://streamdev.vdr-developer.org/snapshots/vdr-streamdev-0.5.0-pre-200
  90706.tgz
  
  
  
  PVR testing version of XBMC
  http://www.xbmc.org/forum/showthread.php?t=45314highlight=pvr
  
  svn checkout
  http://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/pvr-testing2
  
  
  
  Patch VDR 1.7.7 with extensions (for Streamdev
 extension and parental
  rating)
  http://www.zulu-entertainment.de/
  
  http://www.zulu-entertainment.de/page/klick.php?d=VDR+Extensions+Patch
  
  
  cp Make.config.template Make.config
  
  
  Edit make.config enabling:
  
  PARENTALRATING = 1
  STREAMDEVEXT = 1
  Other patches not required for XBMC.
  
  The parental rating patch just gives nice colouring on
 the epg for tv show categories.
  
  Development is very active and shows much promise.
 Disappointing deinterlacing though. There is good
  support for VDPAU but with only half rate temporal. I
 believe there is the intention to support full
  rate deinterlacing... eventually.
 
 several days ago the xbmc developers have added in trunk
 the support of full rate temporal and
 temporal_spatial. You can test them.
 
 Goga
 
 
 ___
 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 for xbmc testing-pvr2

[Stuart Morris]

I am using that version of streamdev with pvr-testing2 ok.
This is my setup:

Streamdev plugin for XBMC
http://streamdev.vdr-developer.org/

http://streamdev.vdr-developer.org/snapshots/vdr-streamdev-0.5.0-pre-200
90706.tgz



PVR testing version of XBMC
http://www.xbmc.org/forum/showthread.php?t=45314highlight=pvr

svn checkout
http://xbmc.svn.sourceforge.net/svnroot/xbmc/branches/pvr-testing2



Patch VDR 1.7.7 with extensions (for Streamdev extension and parental
rating)
http://www.zulu-entertainment.de/

http://www.zulu-entertainment.de/page/klick.php?d=VDR+Extensions+Patch


cp Make.config.template Make.config


Edit make.config enabling:

PARENTALRATING = 1
STREAMDEVEXT = 1
Other patches not required for XBMC.

The parental rating patch just gives nice colouring on the epg for tv show 
categories.

Development is very active and shows much promise. Disappointing deinterlacing 
though. There is good support for VDPAU but with only half rate temporal. I 
believe there is the intention to support full rate deinterlacing... eventually.

Stuart

--- On Fri, 15/1/10, Goga777 goga...@bk.ru wrote:

 From: Goga777 goga...@bk.ru
 Subject: [vdr] streamdev for xbmc testing-pvr2
 To: vdr@linuxtv.org
 Date: Friday, 15 January, 2010, 18:01
 Hi
 
 does support cvs version of streamdev plugin the xbmc
 testing-pvr2 branch ?
 or only 
 http://streamdev.vdr-developer.org/snapshots/vdr-streamdev-0.5.0-pre-20090706.tgz
 will be good for
 xbmc pvr2 ?
 
 Goga
 
 ___
 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] VDR frontend device: Xtreamer

[Stuart Morris]

Hauppauge MediaMVP and vdr-vompserver plugin.

Years of happy use and good waf. No vdr osd so no access to plugins but I can 
access them with vdr-xine on my server.

Sadly standard definition only. I have yet to see an equivalent HD mediaplayer 
that can be as readily hacked like the MediaMVP has.

Stuart

--- On Fri, 27/11/09, Michael Stepanov mich...@stepanoff.org wrote:

 From: Michael Stepanov mich...@stepanoff.org
 Subject: Re: [vdr] VDR frontend device: Xtreamer
 To: VDR Mailing List vdr@linuxtv.org
 Date: Friday, 27 November, 2009, 8:55
 I'd like to know if somebody uses any
 networked media player as VDR client
 
 On Fri, Nov 27, 2009 at 9:59 AM,
 Theunis Potgieter theunis.potgie...@gmail.com
 wrote:
 
 Hi guys, I've recently bought
 an Xtreamer device www.xtreamer.net
 
 
 (apparently a mvix product). I would just like to know if
 anybody else
 
 got it working with streamdev-server plugin on vdr-1.6.0?
 
 
 
 Thanks
 
 Theunis
 
 
 
 ___
 
 vdr mailing list
 
 vdr@linuxtv.org
 
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 
 
 
 
 -- 
 Cheers,
 Michael
 
 
 -Inline Attachment Follows-
 
 ___
 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] Yaepghd record dialog

[Stuart Morris]

Thankyou
The patched yaepghd now silently adds a timer (or deletes one if it already 
exists) for the selected event.

The help bar is behaving strangely. I had no rgyb ellipses. Even when I 
re-implemented the ellipses in the code some were coloured some were not and 
some would be coloured depending on what event was selected. Are you using a 
different theme to the one included with Yaepghd? If I edited the background 
png were the help bar is making it black I could see the coloured ellipses.

Stuart

--- On Sat, 21/11/09, JW solevit...@googlemail.com wrote:

 From: JW solevit...@googlemail.com
 Subject: Re: [vdr] Yaepghd record dialog
 To: VDR Mailing List vdr@linuxtv.org
 Date: Saturday, 21 November, 2009, 16:09
 I'm not the developer of the yaepghd
 plugin, but I had a deeper look at
 the source code. Many things of the record dialog have
 already been
 implemented, but the record dialog isn't called anywhere in
 the source
 code. So I think this done intentionally. I implemented a
 small patch,
 that adds the possibility to set timer with the red button
 without any 
 record dialog. The patch attached contains also some other
 minor
 improvements from other authors. If you have questions
 concerning the
 patch, you can ask at vdr-portal.de
 http://www.vdr-portal.de/board/thread.php?threadid=83864threadview=0page=3
 (even it's a German forum, you will get answers in English
 ;) ).
 
 
  I have been trying out the yaepghd plugin. It looks
 very impressive
  but the record dialog appears to be disabled. Does
 anyone know if this 
  has been intentionally disabled or is only partially
 implemented?
  
  There has been no development activity on this plugin
 for about
  9 months now.
  
  
  
        
  
  ___
  vdr mailing list
  vdr@linuxtv.org
  http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 
 -Inline Attachment Follows-
 
 ___
 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] Yaepghd record dialog

[Stuart Morris]

I have been trying out the yaepghd plugin. It looks very impressive
but the record dialog appears to be disabled. Does anyone know if this 
has been intentionally disabled or is only partially implemented?

There has been no development activity on this plugin for about
9 months now.



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Divx h264 decoder

[Stuart Morris]

Anybody know if it is possible to use the DivX h264 decoder under Linux, much 
like CoreAVC works under DShowServer for Linux?

Stuart



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Vompserver plugin and cIndexFile::Get undefined symbol error

[Stuart Morris]

I am getting an undefined symbol error when I run Vdr 1.7.7 with the 
Vompserver plugin patched for TS format:

vdr: ./PLUGINS/lib/libvdr-vompserver.so.1.7.7: undefined symbol: 
_ZN10cIndexFile3GetEiPtPlPbPi

The plugin compiles ok with no error or warning. cIndexFile::Get is called 
at only one place in Vompserver and the function parameters match perfectly. 
Can anyone suggest what could be wrong?

I am using Gcc 4.3.2.

Stuart



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Vompserver plugin and cIndexFile::Get undefined symbol error

[Stuart Morris]

--- On Wed, 27/5/09, Thomas Günther t...@toms-cafe.de wrote:

  I am getting an undefined symbol error when I run Vdr
 1.7.7 with the 
  Vompserver plugin patched for TS format:
  
  vdr: ./PLUGINS/lib/libvdr-vompserver.so.1.7.7:
 undefined symbol: _ZN10cIndexFile3GetEiPtPlPbPi
  
  The plugin compiles ok with no error or warning.
 cIndexFile::Get is called 
  at only one place in Vompserver and the function
 parameters match perfectly. 
  Can anyone suggest what could be wrong?
 
 You need this line in Makefile or in Make.config:
 
 DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
 -D_LARGEFILE64_SOURCE
 
 Tom
 

That is already in the Vdr-1.7.7 Makefile. Do you mean in the plugin's
Makefile?

Stuart



  

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Vompserver plugin and cIndexFile::Get undefined symbol error

[Stuart Morris]

Thanks Thomas that did it.

I got it to work after renaming Make.config.template
to Make.config. I will post this issue on the Vomp forum.

Stuart

--- On Wed, 27/5/09, Thomas Günther t...@toms-cafe.de wrote:

 From: Thomas Günther t...@toms-cafe.de
 Subject: Re: [vdr] Vompserver plugin and cIndexFile::Get undefined symbol 
 error
 To: Klaus Schmidinger's VDR vdr@linuxtv.org
 Date: Wednesday, 27 May, 2009, 11:06 PM
 Stuart Morris wrote:
  
  That is already in the Vdr-1.7.7 Makefile. Do you mean
 in the plugin's
  Makefile?
 
 That's right.
 
 From HISTORY of VDR-1.7.4:
 - Added DEFINES += -D_FILE_OFFSET_BITS=64
 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
   to Make.config.template (thanks to Johann Friedrichs
 for pointing this out).
   Plugin authors should add this line to their
 Makefile or Make.config if they use
   file access functions that need special versions for
 64 bit offsets.
 
 Tom
 
 ___
 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] Editing usability

[Stuart Morris]

I haved lost count the number of times I have pressed the numbered keys on my 
remote by accident and then panic because I don't know how to undo what then 
happened.

This is definitely a trap for unsuspecting beginners.

Some kind of editing mode would be safer. Otherwise the key layout is ok.

Stuart


--- On Sat, 9/5/09, Udo Richter udo_rich...@gmx.de wrote:

 From: Udo Richter udo_rich...@gmx.de
 Subject: Re: [vdr] Editing usability
 To: VDR Mailing List vdr@linuxtv.org
 Date: Saturday, 9 May, 2009, 9:59 PM
 On 09.05.2009 22:04, Klaus Schmidinger wrote:
  This 'editing mode' could have some (OSD
 visible) key mapping like
  red-toggle mark, green-jump to last mark,
 yellow-jump to next mark,
  blue-start editing. However, this would make
 jumping a lot more difficult.
 
  The color keys are already in use during replay - and
 I really don't see
  how using the color keys would be any more intuitive
 than using the
  number keys.
 
 Users don't expect number keys to do anything else than
 being numbers. 
 The color keys are more 'general use', and
 there's already a common way 
 to display their meaning onscreen.
 
  Personally I don't find the key mapping that
 unintuitive. After all,
  the number keys are unused in replay mode, so why not
 use them for
  editing?
 
 2=Cut
 
   4=Move Back  6=Move Forward
 
   7=Jump Back   8=Test 9=Jump Forward
 
 0=Toggle
 
 Yeah, but was it 7 or 1 for jumping? Does cutting start on
 2 or 8?
 
 Don't get me wrong, I can do this blindfolded in my
 dreams. Its just not 
 as obvious and easy to discover for beginner/infrequent
 users as the 
 rest of VDR is.
 
 
 Cheers,
 
 Udo
 
 ___
 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] 576i output on DVI-HDMI?

[Stuart Morris]

It's my understanding that it is the pixel rate that
is doubled to meet the minimum bandwidth requirement
of 25Mpixels/sec for hdmi.
That is pixels are repeated hence doubling the
apparent horizontal resolution.
This is always the case for the 480i and 576i modes.
The modeline you need should be based on standard
EIA/CEA-861B timings like this:

# 1440x576i @ 50Hz (EIA/CEA-861B)
ModeLine 1440x576 27.000 1440 1464 1590 1728 576 581
587 625 -hsync -vsync Interlace

Unfortunately I think there is a special flag that
must be set to indicate pixel-repetition is being used
and I am not sure how you would get a graphics card to
do this.
I have not tried using the above modeline so I cannot
comment on whether it works.
Worth a try though.

There is a good list of EIA/CEA-861B modes here:
http://www.avsforum.com/avs-vb/showthread.php?t=947830page=3
I do know the 720p modeline works on my tv.
GTF timings generally don't work for hdmi.

The other issue with interlaced modes is how are the
odd/even fields synchronised?
Is this the same problem with interlaced output on a
good old vga output?

I have often wondered how vdr-xine or xineliboutput
would implement dynamic resolution switching.
It would be easy to upscale everything to a higher
resolution like 1080p.
But what if your tv can handle only 1080i at best.
It would be better to switch resolution
when broadcasts change between 1080i and 720p on a
program-to-program basis.

Stuart

--- Ville Aakko [EMAIL PROTECTED] wrote:

 2008/7/15 Jukka Vaisanen [EMAIL PROTECTED]:
 
  Well the 100Hz is just a kludge to fit 576i on the
 HDMI signaling. My understanding is that the
 following happens:
 
  PC sends 1-1-2-2-3-3-4-4.. but the a/v receiver
 just ignores every other frame because it knows
 about the 576i kludge also.. so it is just seeing
 1+2-3+4 going into the deinterlacer + scaler. The
 100Hz thing is just a workaround to get enough data
 on the link so that the HDMI handshake will happen
 :P
 
 I'd try to make a modeline:
 
 $ gtf 720 576 50
 
   # 720x576 @ 50.00 Hz (GTF) hsync: 29.65 kHz; pclk:
 26.57 MHz
   Modeline 720x576_50.00  26.57  720 736 808 896 
 576 577 580 593
 -HSync +Vsync
 
 $ gtf 720 576 100
 
   # 720x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz;
 pclk: 58.66 MHz
   Modeline 720x576_100.00  58.66  720 760 840 960 
 576 577 580 611
 -HSync +Vsync
 
 (if these blow up your 50'' fullHD plasma, you're on
 your own - try
 them at your own risk!)
 
 I'd suspect VDR+xinelibout would not support this
 out of the box. You
 probably need to make a script or something to
 change resolutions when
 needed. Also, xinelibout might not like resolution
 switches on the
 fly. But if this is the case, it could probably be
 worked around by
 making xinelibout / X part a frontend (I believe
 this is possible and
 a very common setup anyways), and restarting it when
 needed.
 
 OTOH, I don't see much gain in doing the above
 compared to the
 deinterlacing in software and then scaling, apart
 from saving some CPU
 cycles. I'd doubt any external display could do a
 better job, though
 then again, I haven't had any experience with those
 modern (post-4:3
 CRT era TV) displays =)
 
  - Ville
 
 -- 
 -- 
 Ville Aakko - [EMAIL PROTECTED]
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 



  __
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at 
Yahoo! http://uk.docs.yahoo.com/ymail/new.html

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR on OpenWRT / embedded system

[Stuart Morris]

--- Theunis Potgieter [EMAIL PROTECTED]
wrote:

 I recently learned of the iStar Mini HD
 https://www.istarhd.com/productpage/spec.html
 
 Also based on the Network Media Tank (NMT) from
 Syabas. Apparently it
 could use the same firmware from other suppliers
 like popcornhour.
 This machine has more RAM,  but also not sure if one
 could add a dvb
 device, if you managed to get the dvb api on the
 machine (2.6.15-sigma
 preempt MIPS32_R2 32BIT gcc-4.0) Would it make sense
 to add a usb 2.0
 hub and if you could manage to add the drivers if
 the kernel doesn't
 support it already?
 
 It already has a built in IR, but only 1 usb port
 available.
 
 --
 Theunis
 
 On 29/02/2008, Laz [EMAIL PROTECTED] wrote:
  On Wednesday 27 February 2008 19:46:40 Artem
 Makhutov wrote:
Hi,
   
has anybody thought of running VDR on OpenWRT?
   
The Asus WL-500g Premium is an wlan access
 point with two USB 2.0 Ports.
It has a 266 MHz Broadcom BCM94704 MIPS CPU and
 is running linux.
   
   

http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GP
   
It is possible to connect a harddrive and some
 USB DVB-S cards via USB
to the access point.
   
So VDR has to be compiled for the MIPS
 architecture.
   
The benefit of an access point is that it makes
 absolutly no noice,
is quite inexpensive and takes less
 electricity.
   
It would be great if the access point could
 record videos on its harddisk
and share them over network via samba or stream
 it...
   
Is this possible? Any ideas?
 
 
  Not exactly the same but I've had vdr running
 relatively successfully on a
   Linksys NSLU2, a.k.a. Slug, which was running
 Debian:
 
   http://en.wikipedia.org/wiki/NSLU2
 
   These have got an Intel XScale processor running
 at 133 MHz (underclocked from
   233 MHz) and a whole 32 MB of RAM (although it's
 possible to upgrade that
   with some dubious soldering...).
 
   I had a USB external disk and a USB DVB card on
 it and I used it as a backup
   system for when I went away.
 
   It worked reasonably well but the lack of RAM was
 a bit of an issue because it
   would occasionally randomly kill processes due to
 a lack of memory!
 
   Overall, it worked but there's no serial port
 (well, no external serial port:
   you can solder one on) so I couldn't get a LIRC
 remote detector on it. I
   can't remember if I tried the remote detector on
 the USB card: probably not
   because there's no video output so you wouldn't
 be able to see what you were
   doing, anyway! I've never managed to get more
 than one USB DVB device to work
   properly together for any length of time and a
 single DVB device would be
   restrictive.
 
   I was setting timers using a script which
 converted dates and times into SVDRP
   commands.
 
   There's also the MediaMVP which is a small (I
 think) MIPS system but that's
   designed for this sort of thing so maybe not as
 interesting!
 
   Cheers,
 
 
   Laz
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 

The Syabas NMT clones like the istarhd look very
interesting.
Instead of running vdr on it, maybe just a vdr
front-end like vompclient used on the Hauppauge
MediaMVP?



  ___
Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
now.
http://uk.answers.yahoo.com/

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Output methods and WSS

[Stuart Morris]

Because Vomp does not provide the VDR osd this does present a unique set of
  desirable and undesirable features.
   
  However the two features I find more desirable than anything else is full 
support
  for interlaced scart PAL with WSS and it is stable. This is the ticket to
  domestic use. IMHO this is the Achilles heal of all HTPC applications 
including VDR.
   
  Despite the great effort many VDR developers have put into output methods,
  there remain problems that prevent use in a domestic environment. I used a
  DXR3 for years but could never rely on it because it crashed so often.
  Softdevice, xine and xineliboutput require a pc that consumes too much energy
  to achieve a smooth output. I have not tried a premium DVB card but they are
  expensive, rare and I hear reports they often crash to. I am curious to know 
how
  good a VIA EPIA mini itx board would be.
   
  Stuart

Kartsa [EMAIL PROTECTED] wrote:
  Laz kirjoitti:
 On Tuesday 16 Oct 2007, Stuart Morris wrote:
 
 According to the MVPvdr website
 http://www.rst38.org.uk/mediamvp/mvpvdr.html
 there appears to be no way to set timers so I have never been tempted
 to try it out.

 I failed to get an early version of the MediaMVP plugin to work many
 years ago.

 Vomp is still being developed so maybe you should join the forum
 http://www.loggytronic.com/forum/
 

 Vomp seems to work quite well. I have an older (H2) MediaMVP which I use 
 on a tele' upstairs, mainly for watching recordings but live TV also 
 works. I think it does have the ability to set timers (on the remote vdr 
 server) but I've never tried that.

 I also have a newer (H4) MediaMVP which I've never managed to get to work 
 but I think it's meant to. These things load a firmware using TFTP when 
 you boot them and they seem quite picky about which files they will 
 download (or not in the case of the newer one!).

 It was fairly easy to set the older one up but you do need a DHCP server 
 (to point the MediaMVP at a TFTP server) and a TFTP server to serve the 
 firmware. Both of these are built in to the vompserver plugin but I never 
 managed to get them to work! I'm already running a DHCP server on a 
 different machine so I'm using that to point the MediaMVP at my main vdr 
 box which is running a stand-alone TFTP server.

 Might sound complicated but it works (at least for the older one!).

 Some things it is missing (as far as I can tell) are trickspeed playback 
 and editing functions, and some of the remote buttons do different things 
 from how I've got my main vdr remote set up. It allows playback of 
 recordings to be resumed but it uses its own resume files, so if you are 
 halfway through watching a recording on the real vdr system, it will 
 replay from the beginning on the vomp box!

 I'm not sure I'd want it as my main way of using vdr (lacks some useful 
 features) but is very good for use as a second system. Also much quieter 
 than the old PC I had as a second vdr system upstairs!

 
As I said, I have a MediaMVP and Vompserver running. Have had for some 
time now (six months or so). The biggest problem is the lack of support 
for subtitles. And I agree that as with the current properties I am not 
going to use this as my main device. And you can not edit timers with it 
only wiev them. Also I would like for the resume to be possible while 
changing from vdr to mediamvp or vv. But anyway it is good for as a 
second device in the bedroom. It's small and makes no sound and you can 
use it for wieving live tv or recordings.

And for Stuart, I joined the forum a long time ago :)

Still remains to be answered if anyone has tried MVPVdr?

\\Kartsa

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


   
-
 For ideas on reducing your carbon footprint visit Yahoo! For Good this month.___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Output methods and WSS

[Stuart Morris]

According to the MVPvdr website
  http://www.rst38.org.uk/mediamvp/mvpvdr.html
  there appears to be no way to set timers so I have never been tempted
  to try it out.
   
  I failed to get an early version of the MediaMVP plugin to work many years 
ago.
   
  Vomp is still being developed so maybe you should join the forum
  http://www.loggytronic.com/forum/
   
  Stuart

Kartsa [EMAIL PROTECTED] wrote:
  Haven't anyone got any experience in these other MediaMVP based 
solutions? I have been thinking to test MVPVdr but haven't had the time 
and if someone else has some knowledge allready I would be most 
interested in hearing.

Rob Davis kirjoitti:
 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

 


___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


   
-
 For ideas on reducing your carbon footprint visit Yahoo! For Good this month.___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Ideal conditions for VDR

[Stuart Morris]

What are the ideal conditions under which to run VDR?

For example:
Nice level?
Nice level relative to other apps, daemons and stuff running at the same time?
Pre-emptive kernel?
Kernel timer 250Hz? 1000Hz?
Quantity of system memory?
Processor speed? Frequency scaling?

I am running VDR with Vompserver for the front end.



-
 All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard 
protect you.___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Epgsearch does not create timers

[Stuart Morris]

I am having difficulty getting Epgsearch plugin to create any timers.

This is the procedure I am going through that I believe should cause Epgsearch
plugin to create timers:
 
Menu
Program Guide
Highlight a scheduled program that I wish to create search parameters for e.g.
'Space 1999'
Press 0
Press red button 'Commands'
4 Create search
Use as search timer: yes
Enter to save the search
Press the back button
Press 0
Press blue button 'search'
Select the search just created
Executing the search finds 'Space 1999' in the epg ok
Press the back button
Press blue button 'Actions'
3 Trigger search timer update
Confirm with enter button
Press blue button 'Actions'
5 Show timers created
The display shows '0 Timers'
Exit by pressing menu button

Menu
Timers
No timers set by epgsearch

I am using epgsearch version 0.9.20. My epg is received from UK Freeview
DVB-t. VDR is running as root. There are no patches to vdr. The only other 
plugin
running at the same time is -Pskincurses because the VDR system is headless.
I am using VDR version 1.4.4.

Am I doing something wrong here or is this a bug?



-
 Inbox full of unwanted email? Get leading protection and 1GB storage with All 
New Yahoo! Mail.___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] Burn plugin permissions problem

[Stuart Morris]

I can create DVD ISO files using vdr-burn-0.1.0-pre20 ok but only if vdr is run as root. If I run vdr without root privelage DVD ISO creation fails at the start. My /tmp folder and ISO destination folder have the appropriate access rights. The burn shell scripts are marked executable and can be read by others. Any one know what is wrong here? Here is the dvd.log file[render] sh: /usr/local/bin/vdrburn-dvd.sh: Permission denied [render] sh: /usr/local/bin/vdrburn-dvd.sh: Permission denied [demux] sh: /usr/local/bin/vdrburn-dvd.sh: Permission denied   
		 
Try the all-new Yahoo! Mail . "The New Version is radically easier to use" – The Wall Street Journal___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr