Re: [vdr] DVB-T2 device in France

[Morfsta]

On Thu, Sep 17, 2015 at 8:58 PM, Karim  wrote:

> Hi,
>
> I use TBS6280 (dual tuner, pci-e) from Turbosight in dvb-t mode (no dvb-t2
> signal here): good card, not expensive and great technical support. Newer
> model is TBS 6281 :
>
> http://www.linuxtv.org/wiki/index.php/TBS6281
>
> I hope it helps.
> Regards.


I have the TBS6281 and have found that the drivers from TBS are a pain to
get co-existing at the same time with other kernel DVB drivers (e.g. my
Prof USB DVB-S2 device) and need re-installing after every kernel update.
Also, I think that the open source drivers do not support DVB-T2.

However, on the positive side once the driver is installed, the card is
stable.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

[vdr] VDR / Softhddevice Freeview HD Multichannel HE-AAC Audio Handling

[Morfsta]

Hi,

I'm using vdr 2.0.6 (2.0.6-6yavdr1) and softhddevice 0.6.1rc1 and I'm
noticing that for multichannel audio output on UK Freeview HD
channels (which I believe use HE-AAC) that there is no centre channel being
output through my amplifier (connected via HDMI) which is receiving only
PCM 2.0 - only left and right stereo audio is heard.

If I watch the same channel directly via my TV's Freeview HD tuner
(connected using ARC HDMI to the same amp) then I think some transcoding
occurs and Dolby Digital is shown on the amplifier and I get all channels
correctly.

Multichannel audio is working fine via VDR on Freesat HD channels which
just uses standard Dolby Digital so I'm guessing its something to do with
the handling of HE-AAC multi channel sound, either in VDR or Softhddevice.

Is anyone else seeing the same problem? I recorded "Blades of Glory" the
other day on BBC Three which was broadcast in 5.1 which exhibits the
problem.

Cheers,

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

Re: [vdr] TBS6285 slow onscreen menu

[Morfsta]

Hi,

I can confirm this issue and also reported this to TBS last week (hadn't
seen this thread) with regard to my dual DVB-T2 card (TBS6281) and worked
with them on the problem.  The issue is the second adapter provided by the
card being untuned on bootup and VDR start and the associated kdvb process
entering the D state.

I worked around it for now by using dvbtune to tune the adapter to an
initial DVB-T frequency on boot up (init script which starts before VDR),
but they say they are fixing it in the next driver release.

Thanks,

Morfsta



On Thu, Jun 12, 2014 at 9:46 PM, Milos Kapoun  wrote:

> Hi all,
>  I am solving it with TBS support. High CPU load is caused by untuned
> (unused) adapters.
>
> After each:
>
> Jun 12 21:39:23 streamer vdr: [3860] frontend 2/0 timed out while tuning
> to channel 0, tp 76
>
> CPUload += 1; :-}
>
> When all adapters are tuned everything is OK and load is low, for example
> 0.3.
>
> Milos
>
> Dne 2014-06-12 16:31, Milos Kapoun napsal:
>
>  Thank you for your replay. It is good to see that card is working.
>> Could you send driver version?
>>
>> Milos
>>
>>
>> Dne 2014-06-12 16:01, Pasi Juppo napsal:
>>
>>> I have TBS6285 card and been using it for few months without
>>> problems. There was an issue with remote control but with lirc
>>> parameter change (delay changes to get rid of repetition) it got
>>> fixed. The card and drivers have been working pretty much flawlessly
>>> in my case (yavdr distro).
>>>
>>> Pasi
>>>
>>
>>
>>
>> ___
>> 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] [Announce] streamdev-0.6.1

[Morfsta]

On Fri, Dec 6, 2013 at 8:55 AM, Frank Schmirler  wrote:

>
> Can you try adding the sleep command as suggested in my first answer? Maybe
> try a short delay (e.g. 500 ms) and a long delay (e.g. 3000 ms). If it
> helps,
> I'll add a setup option.
>
>
Hi Frank,

Putting in a delay of 500ms definitely improves things - its been streaming
awhile without any buffering / drop outs.

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

Re: [vdr] [Announce] streamdev-0.6.1

[Morfsta]

On Mon, Dec 2, 2013 at 11:39 AM, Frank Schmirler  wrote:

> Hi,
>
> On Sat, 30 Nov 2013 16:36:14 -0800, VDR User wrote
> > If his recordings stream fine and the problem is only with live tv,
> > how could that possibly be network congestion?
>
> I should have written "temporary network congestion".
>
> When streaming a recording, the client can pre-buffer data to prevent
> buffer
> underruns. With live TV this is not possible as data becomes available
> just in
> time. So fluctuations in the available network bandwidth could have an
> impact.
> The fact that streamdev uses TCP to transmit the stream might be an
> additional
> problem here as packet loss leads to retransmission.
>
> As Morfsta is able to view HD recordings while he seems to get problems
> even
> with SD live TV, bandwith alone surely isn't the problem. But temporary
> congestion or high packet loss due to e.g. interference sound reasonable
> to me.
>
> Regards,
> Frank
>
>
Difficult to trace these problems isn't it? I get a sustained transfer rate
when copying files over of around 15MB/sec - so I would have thought this
would be ample for SD and HD streaming?

I was just surprised to find very few options to play with in streamdev
with regard to buffer sizes etc. I presume this is by design and the way in
which it works?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [Announce] streamdev-0.6.1

[Morfsta]

On Thu, Nov 28, 2013 at 8:48 PM, Frank Schmirler  wrote:

> Hi,
>
> it was about time to publish a streamdev release for VDR 2.0.
> Streamdev-0.6.1
> is now available from
> http://projects.vdr-developer.org/projects/plg-streamdev/files. The server
> plugin requires at least VDR 1.7.25. The client plugin should even work
> with
> VDR 1.6. On VDR version up to 1.7.33 the Makefiles have to be replaced by
> the
> old versions which are shipped along with the source.
>

Hi Frank,

Thanks for all your hard work with streamdev.

I have been using the VDR Samsung SmartTV VDR plugin which relies on
streamdev for transfer of live channels over the network and it uses its
own proprietary implementation for the transfer of recordings. I have tried
using it over wifi as well as powerline. The recordings (SD and HD) play
flawlessly over the network, however the streaming of live channels using
streamdev results in regular buffering (SD and HD) and eventually the TV
just gives up playing them. Is there any buffer options or other
configurable settings within streamdev that might alleviate this problem? I
can't seem to find much that would help.

Look forward to hearing from you and TIA.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] [ANNOUNCE] vdr-rotorng-0.3

[Morfsta]

On Tue, Feb 19, 2013 at 5:03 PM, YUP  wrote:
> Hey Morfsta,
> Vdr 2.0.0 is coming, it's time to update your plugin. BTW, take a look into
> this issue http://projects.vdr-developer.org/issues/740 . The same error I
> discovered when compiled against vdr-1.7.38.
> Regards,
> Yarema

That issue was fixed in version 0.3.1. Are there any further changes
that are required for VDR 2.0.0?

Regards,

Morfsta

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

Re: [vdr] Does anyone see this or is the VDR mailing list broken?

[Morfsta]

On Fri, Feb 8, 2013 at 11:38 AM, Torgeir Veimo  wrote:
> The purpose for me would be to run a VDR client on a raspberry pi.
> XBMC already runs there and I've used it a bit with VNSI, but until I
> can get the native GUI running on XBMC, it's not WAF ready. I assume
> whenever libxine is finally able to make use of the hw accelerated
> decoding, xinelibplugin will supply what's needed.

Yes, I have a few Pis too, I posted awhile ago as to whether anyone
had had any joy with getting a VDR client running on it but didn't get
a response.

I would much prefer to use a Pi as a client, rather than run it
through XBMC which seems very laggy as a PVR on a Pi.

Is anyone working on xine acceleration for the Pi do you know?

Thanks

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

Re: [vdr] Does anyone see this or is the VDR mailing list broken?

[Morfsta]

> I use XVDR and miss in some ways the plain old Vanilla VDR "GUI".
> Maybe its possible with configuration, but I would like to "push"
> XBMC to the background and be able to use all remote keys in XVDR as if I
> was working natively with VDR, then maybe a single key press to get back to
> "normal" XBMC functionality. Its a WAF thing.

Look at yavdr, it provides that but the other way around and for me
that is preferable as we watch TV / recordings much more than using
XBMC to listen to music or watch videos.

You use vanilla VDR as the base, then when you need XBMC you call it
either via the desktop/mouse or via the VDR menu
(Applications/Media/XBMC). When you exit XBMC it seamlessly goes back
into VDR.

I found that remote control and sound (including AC3 and DTS) work
seamlessly out of the box now with the latest version.

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

Re: [vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35

[Morfsta]

On Tue, Jan 1, 2013 at 8:52 PM, Lars Hanisch  wrote:
>  This is an invitation: Please create more posts in english at vdr-portal! If 
> a critical mass is passed it will be
> easier for the ones coming past us. Sure there's only a small "international" 
> part, but it is there. And of course there
> will be "idiots", you got them everywhere, even at this mailing list. :)
>  I promise if I have something valuable to say to an question asked in 
> english I will give my best and will answer it.
>

I can second Lars here, following my English post on vdr-portal we
worked together to fix rotorng with later versions of VDR in yavdr
0.5.0.

Perhaps a sticky at the top of the forum discussing and encouraging
the use of English for non-German speaking users would help and giving
some guidance on the best way to approach it, so as to avoid flames.

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

Re: [vdr] [ANNOUNCE] vdr-rotorng-0.3

[Morfsta]

Okay, updated version (0.3.1) has been uploaded to the VDR Projects site.

I have also fixed all the compilation warnings (at last)!

Thanks

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

Re: [vdr] [ANNOUNCE] vdr-rotorng-0.3

[Morfsta]

On Fri, Oct 26, 2012 at 7:59 AM, Lars Hanisch  wrote:
>>  There are two places: one in the class definition and one a few lines below 
>> that. Just search for "ChannelSwitch"... :)
>  Line 336 and line 347.

Oops. Thanks for the help, I'll update and release a fixed version.

Thanks

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

Re: [vdr] [ANNOUNCE] vdr-rotorng-0.3

[Morfsta]

On Thu, Oct 25, 2012 at 5:42 PM, Lars Hanisch  wrote:
>  You've forgotten the wrap the definition of ChannelSwitch into #if's:
>
> --- a/rotorng.c
> +++ b/rotorng.c
> @@ -333,7 +333,11 @@
>int last_position_shown;
>bool transfer;
>  protected:
> +#if VDRVERSNUM >= 10726
>virtual void ChannelSwitch(const cDevice *Device, int ChannelNumber, bool 
> LiveView);
> +#else
> +  virtual void ChannelSwitch(const cDevice *Device, int ChannelNumber);
> +#endif
>  public:
>cStatusMonitor();
>  };
>

Are you sure? Its definitely in my copy and seems to be in the one on
the projects site.

Thanks

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

[vdr] [ANNOUNCE] vdr-rotorng-0.3

[Morfsta]

Hi,

The third version of my plugin rotorng has been released here: -

http://projects.vdr-developer.org/projects/plg-rotor-ng/files

This plugin allows you to steer a disecq 1.1 rotor, find satellites
with a signal meter and to store them at given positions. It also has
a rudimentary channel scanner which works with both DVB-S and S2. Much
of this code has been merged together from the existing actuator and
rotor plugins, so thanks to the developers of those for their work.

Please see the README file, there are a number of functions within the
user interface that aren't fully implemented or working but the main
functions are there.

Changes since previous version: -

2012-10-11: Version 0.2

- updated sat card store value in config, always resetting
- fixed issue with change implemented in 1.7.23 (thanks to Ihanisch)

2012-10-21: Version 0.3

- Added patch for vdr-1.7.27 onwards, old patch for VDR still exists also.
- Fixed problem with cStatusMonitor::ChannelSwitch call introduced in
VDR 1.7.26 so dish moves on channel change

Good luck!

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

Re: [vdr] rotorng broken with 1.7.27 - any changes to vdr core / kernel?

[Morfsta]

On Thu, Oct 25, 2012 at 3:32 PM, Klaus Schmidinger
 wrote:

>
> What "ChannelMonitor"?
> There is no such thing in VDR.
>

Hi Klaus,

Thanks for getting back to me.

Sorry, I meant cStatusMonitor::ChannelSwitch.

> cDvbTuner is local to dvbdevice.c, and cDvbTuner::ExecuteDiseqc() is
> private.
> So I'm afraid you can't do this without a patch.

Would it be possibe to update this in a later version of VDR please
Klaus? Given that there is currently no multiple satellite support in
code VDR (there should be really - many people would appreciate this),
then it would make sense to at least permit a plugin to be able to
move the dish with diseqc commands.

Kind Regards

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

Re: [vdr] rotorng broken with 1.7.27 - any changes to vdr core / kernel?

[Morfsta]

Hi Klaus,

I fixed the problem I had with rotorng, it was a problem with a YAVDR
patch and also your changes to ChannelMonitor.

I'm trying to get my head around the VDR function
cDVBTuner::ExecuteDiseqc to try and remove the requirement for a patch
for VDR core in future.

If I would like to send a FE_DISEQC_SEND_MASTER_CMD from a plugin, how
would I write the code to do this from inside the plugin? Is this
possible?

I am trying to setup a cDiseqc object but don't know how to build it
just to be able to send a raw command of type dvb_diseqc_master_cmd.

Any help you would be able to give me would be much appreciated and
would hopefully move this plugin forward. I'm not a C++ developer,
more a code hacker so please be gentle! ;-)

Many Thanks,

Morfsta



On Mon, Oct 15, 2012 at 9:29 AM, Morfsta  wrote:
> On Fri, Oct 12, 2012 at 3:31 PM, Klaus Schmidinger
>  wrote:
>>
>> I'm afraid I can't think of anything obvious.
>> Could you try using versions 1.7.13 thru 1.7.27 in turn to see
>> which version introduced the problem?
>>
>
> Thanks Klaus, I will dig into it.
>
> I suspect it could be related to some changes in YAVDR but I will
> build a vanilla VDR(s) at some stage and test it with that too.

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

[vdr] HDMI CEC support in VDR with Pulse Eight Adapter

[Morfsta]

Hi,

Has anyone had any experience of working with the Pulse Eight USB to
HDMI CEC adapter [1] with controlling VDR when using a graphics card
or other non-CEC device as an output?

It seems that support for this has been implemented within Myth TV and
XBMC, but I haven't seen anything on VDR.

It would be very useful to be able to control VDR from your TV handset
and also be able to power on / off VDR with all other HDMI CEC
devices.

I wondered if anyone has started work on a CEC VDR PLUGIN or whether
it should be implemented within the core itself, alongside LIRC and
KBD?

If not, I might look at trying to hack up a plugin if I get some time.

Thanks,

Morfsta

[1] http://www.pulse-eight.com/store/products/104-usb-hdmi-cec-adapter.aspx

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

Re: [vdr] rotorng broken with 1.7.27 - any changes to vdr core / kernel?

[Morfsta]

On Fri, Oct 12, 2012 at 3:31 PM, Klaus Schmidinger
 wrote:
>
> I'm afraid I can't think of anything obvious.
> Could you try using versions 1.7.13 thru 1.7.27 in turn to see
> which version introduced the problem?
>

Thanks Klaus, I will dig into it.

I suspect it could be related to some changes in YAVDR but I will
build a vanilla VDR(s) at some stage and test it with that too.

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

[vdr] rotorng broken with 1.7.27 - any changes to vdr core / kernel?

[Morfsta]

Hi Klaus,

As part of a recent upgrade from vdr-1.7.22 to 1.7.27 within yavdr I've
seen that my rotorng plugin doesn't work anymore and this is shown in the
syslog when I try to send a disecq command: -

 vdr: [8287] ERROR: frontend 1/0: Invalid argument

The plugin includes a patch to the vdr src which adds another method to
cDvbTuner: -

+bool cDvbTuner::SendDiseqcCmd(dvb_diseqc_master_cmd cmd)
+{
+  cMutexLock MutexLock(&mutex);
+  if ((frontendType!=SYS_DVBS2 && frontendType!=SYS_DVBS) || SendDiseqc)
+return false;
+  diseqc_cmd=cmd;
+  SendDiseqc=true;
+  newSet.Broadcast();
+  return true;
+}
and modifies cDvbTuner::GetFrontendStatus with: -

  cMutexLock MutexLock(&mutex);
+if (SendDiseqc) {
+   CHECK(ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD,
&diseqc_cmd));
+   SendDiseqc=false;
+   }
Has anything changed in VDR, or perhaps the driver that means this no
longer works the way that it used to? I've looked through the HISTORY and
can't spot anything that stands out.

Thank for any help you can provide.

Kind Regards,

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

[vdr] VDR on Raspberry Pi

[Morfsta]

Hi,

Now that Raspberry Pis are quite common, cheap (~£25) and
easily acquired (I received my order within 2 days from Farnell) has anyone
considered whether it might be feasible to put together an output plugin
for VDR for it? It is now possible to play MPEG-2 (with a codec license
costing £2.40) as well as 1080p H.264 with hardware acceleration.

There is work on VOMP (previously on Hauppauge MediaMVP) to work as a VDR
client on the Pi and as far as I can see quite a lot of progress has been
made. I'm wondering whether it would be possible to run VDR with HDMI video
/ audio output on one of these too and given the work done so far on VOMP
and XBMC how difficult it would be to create an output plugin?

Cheers,

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

Re: [vdr] Quiet times...

[Morfsta]

I'll bite three.

There is no summer in England, so no excuses for all this quietness
On Mon, Aug 6, 2012 at 4:14 PM, Oliver Schinagl wrote:

> I'll bite too :)
>
> I'm still 'waiting' for comments on my patch that I posted on 23-07-12;
> 11:21
>
> [PATCH] Make RGYB buttons customizable (attempt 2)
>
>
> On 06-08-12 09:04, Klaus Schmidinger wrote:
>
>> It's been rather quiet on the VDR mailing list lately, but I guess
>> everybody (like myself) is enjoying the summer and engaged in outdoor
>> activities...
>>
>> 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
>
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] Rotor / Rotor-NG not working with latest VDR

[Morfsta]

On Sun, Dec 25, 2011 at 12:32 PM, ilia mane  wrote:
> Thank you Lars Hanisch it work for me.I just disable the dynamite plugin in
> /etc/vdr/plugins/order.conf and the rotorng plugin work now.

Just returned from the Christmas period, merry Christmas all!

Then it looks like dynamite is the problem. Rotorng has a setup option
for the satellite adapter that is connected to the rotor and normally
it is set to 1,2,3 etc depending on the allocated adapter # at boot
up. I guess this might now change with this virtual proxy for the
adapter that is setup by dynamite?

How is this handled, for example by femon or other plugins that need
to communicate with the required physical adapter #?

Thanks,

Morfsta

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

Re: [vdr] Rotor / Rotor-NG not working with latest VDR

[Morfsta]

>  Please install the latest updates with:
> $ sudo apt-get update
> $ sudo apt-get dist-upgrade
>
>  There was an error in the vdr-plugin dynamite's Makefile.

Hi there,

Thanks for your help, but the rotor / rotorng plugins still don't work
after the update.

Any other ideas?

Kind Regards,

Morfsta

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

Re: [vdr] Rotor / Rotor-NG not working with latest VDR

[Morfsta]

On Tue, Dec 20, 2011 at 9:20 AM, Ales Jurik  wrote:
>
> I also had to implement changes into Seppo patch for gotoxx - so maybe
> you could take a look into the latest version of gotoxx patch for
> 1.7.22, it is working without problems, hope it helps.
>
> You could find the patch at
> http://www.linuxtv.org/pipermail/vdr/2011-December/025511.html

I don't know the previous patch, what did you have to change?

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

Re: [vdr] Rotor / Rotor-NG not working with latest VDR

[Morfsta]

On Tue, Dec 20, 2011 at 9:23 AM, Klaus Schmidinger
 wrote:
> On 20.12.2011 09:49, Morfsta wrote:

> I don't see what could have changed in version 1.7.21 that might
> have an impact on this.
> "Satellite Channel Routing" (SCR) and "Device Bonding" (unicable)
> were implemented in later versions.

I think the yavdr VDR distribution has the Unicable patch applied to
1.7.21, there is an option "log LNB usage" in the LNB menu and there
is a # Unicable set of entries in the disecq.conf file.

The rotor and rotorng plugin use: -

  if (ActuatorDevice->SendDiseqcCmd(switch_cmds[KNr]))

to send the disecq sequence to move the rotor where KNr is the device
number with the rotor atached.

Has this means to send the disecqc command now changed as part of
unicable support both in core VDR 1.7.21 and as part of the patch?

Kind Regards,

Morfsta

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

[vdr] Rotor / Rotor-NG not working with latest VDR

[Morfsta]

Hi,

I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR
1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin
no longer drive the rotor using any of the functions in the menu.

Is anyone else seeing this too?

I think that this could be because of recent changes to disecq
handling code within VDR as part of the Unicable update. Klaus could
you point me in the direction of what might have changed such that
these plugins no longer work and I will do my best to implement a fix.

Thanks very much for your help,

Regards,

Morfsta

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

[vdr] [ANNOUNCE] vdr-rotorng-0.1.0

[Morfsta]

Hi,

The first version of my plugin rotorng has been released here: -

http://projects.vdr-developer.org/projects/plg-rotor-ng

This plugin allows you to steer a disecq 1.1 rotor, find satellites
with a signal meter and to store them at given positions. It also has
a rudimentary channel scanner which works with both DVB-S and S2. Much
of this code has been merged together from the existing actuator and
rotor plugins, so thanks to the developers of those for their work.

This is an alpha version, though it has been stable on my own system
for a few months. I haven't been able to make as much additional
progress on it as I'd like since my previous email due to work and
holidays so I'm releasing it as is for the moment.

Please see the README file, there are a number of functions within the
user interface that aren't fully implemented or working but the main
functions are there.

Good luck!

Regards,

Morfsta

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

Re: [vdr] How about a small UK/Ireland S28.2E VDR community forum?

[Morfsta]

On Fri, May 6, 2011 at 9:04 AM, Henning Pingel  wrote:
>
>>> I was wondering if it would make sense to offer a place for VDR users
>>> using the sky_uk/freesat/S28.2E/freeview platforms to communicate with
>>> each other. The intention is that people can discuss their special needs
>>> like freesat EPG, red button stuff, channel lists, channel logos and all
>>> other things and test new inventions (like the red button extension)
>>> together.

I think its a great idea. There must be a fair number of English VDR
users out there (I'm one of them!) and I've always found the lack of
UK based support and discussion frustrating and whilst the German
users are pretty helpful on vdrportal, I get the feeling they get
frustrated with us asking questions that have been answered in German
previously that we can't search for!

I think if you widen it up too much it'll never happen or become
watered down and MythTV already has a lot of English-based support.
I'd suggest keeping it narrow to English speaking VDR users (or yaVDR
at a push, which I do now use and its as stable now for me after a lot
of config as using a FF card or my previous Reel eHD) and of course we
can then cover UK channel logos and red button support etc in there as
a subset. VDR Portal IMHO would be the ideal location if we can
consider asking them to open an area for us.

I'd be happy to help and contribute.

Thanks,

Morfsta

PS - for those waiting for rotor-ng, its still on my to do list to
finish off. A combination of holiday and high work load has meant that
I've not had a lot of time to look at it recently. I may release an
alpha release of it as it is for those that are waiting if there is
any demand for it? It has been stable in my box for a few months now.

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

Re: [vdr] UK Channel Logos

[Morfsta]

On Thu, Apr 21, 2011 at 6:43 PM, Dominic Evans  wrote:
> I spent some time earlier in Illustrator, sourcing vector images of
> various UK channel logos from promotional PDFs issued by Freeview,
> Freesat and Sky and dumped them into individual SVG files for each
> channel.

Excellent work, there's always lots of German logos for VDR, but very
little for UK users.

> Ideally these could be used to build a decent set of images for use
> with VDR (e.g., PearlHD skin), EPG (yaepghd?) and web interface
> (live).
>

Do they just need converting to XPM, PNG or something similar? How can
we do this?

It would be great to convert them so that we can now use them in VDR.

Thanks

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

Re: [vdr] rotor-ng

[Morfsta]

On Tue, Mar 22, 2011 at 12:05 PM, Arturo Martinez  wrote:
> Excellent news!
> I am sure the entire rotor vdr community will be very glad to hear that!
> At the moment I use diseqc.conf with goto position commands for each sat
> position to move the dish
> With rotor-ng does diseqc use have to be switched off in vdr and the plugin
> takes care of everything or does it parse diseqc.conf?

VDR Diseqc settings are off in my configuration.

Similarly to the rotor and actuator plugins there is a file in the
plugin directory that stores the disecq postion number for every
satellite: -

S3.0E 31
S4.0E 30
S4.8E 15
S7.0E 14
S9.0E 29
S10.0E 13
S13.0E 12
S16.0E 11
S19.2E 10

At the moment you need to manually edit the file to set the positions
up. A later version might include assigning or changing the position
numbers directly in the plugin interface.

I should at this point thank Luca Olivetti for all his work on the
actuator plugin. I'm no developer, so wouldn't have been able to get
this far without all the work he did on the scan interface etc. I've
merely hacked his work to modify it to work with disecq 1.1 and fixed
some issues with DVBS2 tuning. Ideally, we should probably work
together to unify the two plugins so you can select Actuator / Disecq
/ GOTOX as the motor type attached and have a totally new plugin
probably called "Dish" or something similar.

Still left to do: -

1) Remove or fix some actuator specific interface buttons that are not
too relevant or don't work
2) Fix enabling and clearing of limits as this doesn't work with my
VBOX, I can't clear the limits via the plugin once they are set
3) Look at "recalc" and see how that can be implemented within rotor-ng
4) Remove old unused code that is related to actuator use
5) Update documentation etc
6) Find somewhere to host it - vdrprojects?
7) Implement GOTOX (though I don't use it so not sure how it would be
tested. Might need a volunteer to do this by looking at the GOTOX
patches for rotor and implementing them on rotor-ng).

Thanks

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

Re: [vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin]

[Morfsta]

On Sun, Mar 20, 2011 at 10:08 PM, Timothy D. Lenz  wrote:
> I only have a Nexus-s for sat card and right now my rotor alignment is all
> screwed up. Relays went bad and had to replace them. I left the rotor
> elevation setting untouched but now it over shoots more and more the farther
> it goes as if the elevation is wrong. Haven't had time to look into it.

Well, it seems I found the problem. The HAUPPAUGE NOVA-S2-HD card
(HVR4000 lite / CX24116 frontend) won't lock onto DVB-S2 channels with
FEC_AUTO or ROLLOFF_AUTO set. So, I modified the plugin to allow
selectable values for FEC and ROLLOFF and now it works fine. I can now
lock and scan DVB-S and DVB-S2 channels (QPSK and 8PSK) directly from
the plugin menu and move the dish to find and store satellites with
diseqc and signal strength meter. Ideal for feedhunting now!

When I get a bit more time I'll tidy up the plugin and release it as
it should now act as a pretty good satellite channel scanner
irrespective of whether you have a rotor within VDR. I haven't tested
the entire satellite transponder scanning functionality yet for
DVB-S/S2, that will be the next task but hopefully it won't need many
changes.

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

[vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin]

[Morfsta]

On Mon, Oct 11, 2010 at 1:32 PM, Morfsta  wrote:

> This really is sorely missing from VDR. Its a nice project which I
> might look at if I ever get a spare moment! First I would have to
> update my VDR from 1.7.0 with multiproto as lack of good support for
> vdr-rotor has been holding me back from upgrading to S2API and later
> development versions of VDR.

Well, it took awhile but I have updated to yavdr 0.3 with S2API and a
NV card and it is pretty stable now.

The old rotor plugin is pretty unstable with yavdr (and perhaps later
versions of VDR in general) and it seemed that no-one wanted to fix
it, so I finally got around to modifying the actuator plugin to work
with my disecq rotor (well actually a V-BOX hooked up to a 24V
actuator). I can now get rid of the rotor plugin completely and drive
my dish to the right positions and find / tune satellites with the
modified actuator plugin, which IMHO works and looks better.  It also
allows me to scan DVB-S channels right from the plugin too.

I'd like to release it at some point when I've tidied it up (perhaps
as rotor-ng or something), but one issue I have is with DVB-S2 signal
tuning and scanning on my Hauppauge Nova HD-S2 card - does anyone have
this functionality working either with this card or another card with
the actuator plugin's scanner?

When I tune to a DVB-S2 channel (QPSK or 8PSK) within the plugin I get
nothing, but when I tune in VDR the plugin shows full lock etc. I'd
like to get this functionality working before releasing it and I
thought it might be a problem with the card not supporting
ROLLOFF_AUTO but that doesn't make any difference.

Any help would be great.

Thanks,

Morfsta

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

Re: [vdr] Request for rotor/actuator support integration to vdr

[Morfsta]

On Sun, Jan 23, 2011 at 8:56 AM, Arthur Konovalov  wrote:

> I agree and awaiting too native rotor support in the vdr core.

I would also love to see native rotor support. The plugin crashes all
the time with yavdr and is virtually unusable.

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

Re: [vdr] Developer versions

[Morfsta]

On Wed, Jan 12, 2011 at 12:02 PM, Laz  wrote:
> Sounds good. How are you running iPlayer, etc.? Through Firefox or
> equivalent?

No. Boxee (and XBMC) provide BBC iplayer apps formatted for the big
screen that require only a remote control to navigate.

> I've got a couple of Media MVPs hanging off of my setup too! They won't do
> HD, though. :-(

No, but my other screens are both 19" so HD doesn't really matter to
me - the screens are too small to warrant HD.

There is a Media MVP HD out, but its not supported yet - I think there
is some work going on (see VOMP forum) but I wouldn't hold your breath
for awhile, if ever, due to the API not being public.

Cheers

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

Re: [vdr] Developer versions

[Morfsta]

> Why not exclusively use the yaVDR repositories?

My winter project has been to migrate my old hand compiled VDR-1.7.0
system using Reel EHD to yaVDR (distro) using a Nvidia GT210 with HDMI
audio. Its taken a bit of tweaking to get somewhere near (mostly
addressing audio sync issues when I used the motherboard sound card
via SPDIF) but now I can get HD video with multichannel audio through
VDR and also switch from the VDR main menu into Boxee (need to add
this yourself) to handle playing local media (and free movies provided
in the library) as well as running apps such as BBC iplayer and all
the hundreds of other TV apps available (You Tube, Browser, Flickr,
CNET, NASA TV etc).

I also compiled up the vomp mediaplayer plugin to drive my 2 Hauppauge
Media MVPs (TV and media distributed through the house) and hooked it
up to my rotor (rotor plugin seems pretty unstable though and crashes
VDR regularly) and use channel scan to find sat channels.

I'm really pleased with it as it makes a great HTPC and Internet TV
App solution and it has a high WAF.

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

Re: [vdr] xine-lib and vaapi support

[Morfsta]

On Wed, Nov 10, 2010 at 12:52 PM, Darren Salt
 wrote:
> I demand that lucian orasanu may or may not have written...
>
>> how about moving to mplayer instead of xine-lib, is not maintained very
>> well any more?

Would be good, I returned to xinelibout / xine-lib with yavdr recently
after using a reel eHD for awhile to find that the same old sync
problems exist which is a real shame otherwise it would be pretty
good. I especially see sync issues on channels with Dolby Digital 2.0,
Stereo PCM doesn't seem too bad.

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

Re: [vdr] [ANNOUNCE] vdr-actuator-1.2.0 plugin

[Morfsta]

On Sat, Oct 9, 2010 at 4:58 PM, Luca Olivetti  wrote:
> Hello,
>
> I'm releasing version 1.2.0 of the "actuator" plugin available at
>
> http://www.ventoso.org/luca/vdr/
>
> This plugin controls a linear actuator (or an horizon to horizon one)
> through the parallel port with a simple circuit.
>
> From this version it is also possible to use the plugin without an actuator,
> i.e. as a channel scanner only.
>
> Note that it only compiles with the current development version of vdr.
>
> The changes:
>
> - Version for current development version of vdr (>= 1.7.15)
> - DVB-S2 support (untested, I don't have DVB-S2 hardware)
> - Experimental seractuator module (uses a serial port instead
>  of a parallel port)
> - Complete rewrite of the channel scanner
> - The plugin can now work without an actuator (i.e. as a channel scanner
>  only) with the command line option "-s" or "--scanonly"
>
> Bye
> --
> Luca
>
>

Good work - I think it would be great if we could merge in the old
rotor plugin into one overarching "VDR Dish" plugin which will work
with both the 24V actuators as well as the diseqc motors, to include
DVB-S / DVB-S2 channel scanners (entire satellite and single
transponders), signal strength / quality meters, dish tuning /
adjustment controls and with the ability to add selected channels to
the overall channel list etc.

This really is sorely missing from VDR. Its a nice project which I
might look at if I ever get a spare moment! First I would have to
update my VDR from 1.7.0 with multiproto as lack of good support for
vdr-rotor has been holding me back from upgrading to S2API and later
development versions of VDR.

Thanks,

Morfsta

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

Re: [vdr] vdr-1.7.15 problem with TV

[Morfsta]

Isn't it about time that VDR had a native out of the box plugin for
X11 output with H264 acceleration? There's so many problems with
having xine or xinelibout plugins developed by 3rd parties and relying
on syncing up with xine etc...

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

Re: [vdr] xmltv2vdr genre info added

[Morfsta]

>
> Is the maintainer still around?

Just about... ;-) thanks for your improvement.

I will review this and push it up to Klaus for inclusion on the FTP site.

Thanks

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

Re: [vdr] xbmc-pvr (was - HD clients for vdr)

[Morfsta]

I got xbmc-vdr working the other day - but can't seem to see any
active deinterlacing when using VDPAU Temporal. Other methods such as
bob and weave work okay, but not VDPAU. Does anyone else see this
problem? Pretty useless without any reasonable deint going on.. :-(

Thanks,

Morfsta

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

Re: [vdr] xbmc-pvr (was - HD clients for vdr)

[Morfsta]

Does the unified xbmc pvr work with VDR 1.7.8? The howto instructions
on the xbmc forum only mention 1.7.4.

Does 1.7.8 and latest xbmc-pvr svn only require a new streamdev (to
support TS?), or are other patches required?

Would be good if someone could outline what's needed to get it working.

Thanks,

Morfsta

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

Re: [vdr] xbmc-pvr (was - HD clients for vdr)

[Morfsta]

On Thu, Aug 20, 2009 at 7:55 PM, VDR User wrote:
> I should note that even though I did give it a try, I never intended
> to replace VDR with it regardless of the test results.  I am a VDR
> loyalist. :)

I too have tried Myth on a number of occasions and have found it
unwieldy and slow, not sure why its so popular, perhaps because of the
flashier interface.

I currently have an ehd but have also just invested in a nvidia 9400,
to begin fiddling with VDR + XBMC but as usual I never get really
great results from using X11 based output, even with VDPAU and
temporal-spatial de-interlacing. It never seems to be up to the same
quality as a dedicated output card like the eHD, or FF TT card before
it.

That said, I haven't done the XBMC + VDR bit yet, just tried using
vdr-xine and xinelibout which just don't cut it. :-(

Right now I have ehd on one HDMI input for the TV with LIRC remote
control and X11 desktop with XBMC on the other output with mouse
control. Would be nice to eventually have all of it on one output with
just LIRC control for it all, but right now it serves me well with
good quality output and stability.

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

Re: [vdr] BBC HD Problems

[Morfsta]

On Sun, Nov 23, 2008 at 11:34 AM, Morfsta wrote:
> Hi,
>
> There appears to have been some changes made recently to BBCHD on 28.2E: -
>
> BBCHD:BBC:10847:vC56M2O35S0:S28.2E:22000:2328:2330=NAR;2329=eng:2331:0:6940
> :2:2050:0
>
> It is now not watchable with a reel eHD card - no audio and stuttering video.
>
> The Reel support people are saying this is possibly because they have
> started using AAC audio which is not supported by VDR.
>
> Is anyone else having problems with this and FFMPEG or CoreAVC via
> xine or is it still fine?
>
> Thanks,
>
> Morfsta
>

FYI It looks like BBC HD has finally gotten around to fixing this
issue that I reported to them in December. I can watch BBC HD at the
moment fine with my eHD card.

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

Re: [vdr] SKY and VDR

[Morfsta]

On Fri, Jul 31, 2009 at 1:02 PM, Alex Fazzari wrote:
> Hi everyone,
>
> What I'd like to do is get the stream straight to disk, preferably
> including HD streams. Can I do this using a DVB-S card and a dragon
> (or similar) cam with VDR?

Alex,

Encryption chat is off topic for this mailing list and let's keep the
solution legal.

All of that is feasibly possible, assuming a dragon cam supports the
version of NDS encryption used in NZ. Though with a dragon cam you'll
need to transfer your original viewing card to an official box for
updates every month. Alternatively you could use a softcam and phoenix
card reader alongside your original viewing card which will handle the
monthly updates for you.

For HD you'll need a later version of VDR that support DVB-S2 (if used
in NZ) and H264.

I recommend that you visit the DVBN forums which has a lot more
information about what you are trying to achieve and would be the best
place to ask questions on the subject.

Regards,

Morfsta

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

Re: [vdr] Any really working HD video output systems for VDR?

[Morfsta]

On Mon, Jun 8, 2009 at 8:54 PM, Georg Acher wrote:

> Just ask, there are no secrets ;) There's just not enough time to guess what
> will be of interest...

Great! Georg, can you let us know why FF/FR and pause/play handling
within VDR with reelbox-3 is so laggy? It makes jumping, searching and
seeking within VDR almost unusable.

Is there anything we can do to fix this?

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

Re: [vdr] VDR feature request: GotoStoredPosition

[Morfsta]

On 4/27/09, marti...@embl.de  wrote:
> To enable/disable GotoStoredPosition we would need a setting (on/off)
> on the Diseqc setup menu



IMHO, VDR needs multi satellite support bundled with it (via diseqc
1.2), which could be achieved either in the core, or as a bundled
plugin. The plugin should: -

1) Set East/West limits
2) Drive the rotor east/west for tuning
3) Store sat locations at certain position numbers
4) Display signal strength etc
5) Allow scanning of DVB-S / S2 transponders and add these to VDR channel lists

Mostly this is done by the rotor plugin, but it doesn't seem to be
supported anymore. :-(

Thanks,

Morfsta

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

Re: [vdr] BBC HD and vdpau

[Morfsta]

On Wed, Apr 22, 2009 at 8:05 PM, Reinhard Nissl  wrote:
>> Sounds like VDPAU (or xine's interface with VDPAU) doesn't support
>> MBAFF properly then.
>>
>> BBCHD is one of the few HD channels that uses MBAFF, most use PAFF.
>
> Is there a chance to provide a TS sample for investigation?
>
> Bye.

Reinhard, look here: http://www.megaupload.com/?d=Y9UIF304

Thanks,

Morfsta

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

Re: [vdr] BBC HD and vdpau

[Morfsta]

On Tue, Apr 21, 2009 at 11:02 PM, Luca Olivetti  wrote:

> I doubt it. I think it's simply a case of vdpau not working properly, or
> some magic setting that has to be tweaked (I had really funky colors
> until I reset the hue,saturation and contrast by editing .xine/config,
> no way to correctly adjust them from insinde xine).
> FWIW I'm using the laptop display (which has 1680x1050 resolution, so
> there's a bit of scaling involved from 1440x1080).
>
> Bye
> --
> Luca

Sounds like VDPAU (or xine's interface with VDPAU) doesn't support
MBAFF properly then.

BBCHD is one of the few HD channels that uses MBAFF, most use PAFF.

Kind Regards,

Morfsta

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

Re: [vdr] BBC HD and vdpau

[Morfsta]

On Mon, Apr 20, 2009 at 4:55 PM, Rob Davis  wrote:
> I have VDR working with BBC HD almost, and Sky HD +24 and a few others,
> however, BBC doesn't seem to display properly, as well as having
> problems with the audio selection.  It looks like it has macrovision
> protection or something like that.. (Using vdr-sxfe and xine-libs with
> h264 support).
>
> As I said, other channels seem to work.  I would try ITV HD but there's
> never anything on...
>
> Any tips?

There is a bug in the broadcast of BBCHD (on Astra 28.2E, this problem
doesn't occur on 1W) as the audio descriptor is wrong for the AC3
stream. This doesn't seem to cause problems with any other receiver
now apart from VDR. I have mailed the BBC twice, and they say they are
going to fix it at their "next technology refresh" as they don't want
to be uncompliant with the DVB standards but they haven't done this
since my first mail in December so don't expect anything soon.

If you turn Dolby Digital off in the VDR DVB menu then it will play
only the MPA track and the picture will then work fine in VDR.
However, unfortunately this track also comes with audio description
which can be pretty annoying if you're not visually impaired!

It would be nice to see BBC HD again with VDR - if someone could give
some pointers on how we might be able to fix it (see my earlier mail
to this list on the subject with more technical details) I would work
on a patch for those who are interested. But right now, I don't know
where to start (I'm a hacker not a coder).

Thanks,

Morfsta

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

Re: [vdr] weekly or daily timers

[Morfsta]

On Mon, Apr 20, 2009 at 11:36 AM,   wrote:
> Is there someway in VDR to say schedule a repeated timer 'record this monday 
> to
> friday from 9pm til 11pm' or at least a daily timer 'record this every monday
> between 9pm and 11pm'
>
> Perhaps some plugin? Any hints?

If you press "0" on a timer date/time then it changes from being a one
off recording to being weekly recurring.

Pressing left/right after that gives you lots of options, e.g.
recording Sun - Sat / Mon - Fri / Sat & Sun etc

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

Re: [vdr] [PATCH] vompserver-0.3.0 for VDR >= 1.7.3

[Morfsta]

On Mon, Apr 13, 2009 at 11:47 PM, Thomas Günther  wrote:
> Hi!
>
> Here is a patch for the vompserver plug-in and VDR >= 1.7.3:
>
> http://toms-cafe.de/vdr/download/vompserver-0.3.0-1.7.3.diff
>
> Tom

Hi Tom,

Thanks for making the patch, before I go back down the route of
fiddling with VDR > 1.7.0 again, could you confirm that this patch
allows playback of TS recordings on Vomp clients?

If so, I think it would also be a good idea to post this to the vomp forum too.

Thanks,

Morfsta

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

Re: [vdr] Forthcoming VDR Release To Support VDPAU (???)

[Morfsta]

On Mon, Mar 9, 2009 at 11:34 PM, Klaus Schmidinger
 wrote:

> Why should any special output device get support in VDR core, if
> I'm permanently being pestered to remove even support for DVB devices
> from the core code?

Is core VDR still being developed?

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

Re: [vdr] eHD experiences with VDR

[Morfsta]

On Thu, Feb 26, 2009 at 6:52 PM, Antti Hartikainen  wrote:
> S2API patch didn't work with my DVB-T tuners so i needed to change tuning 
> code from dvbdevice.c a little bit (to do it like scan-s2
> did, as tuning worked fine with it)

I had the same problem, can you post a diff to apply on top of the
S2API patch to fix the DVB-T tuning problem?

> 4) Fast forward/rewind problems. Skipping with green/yellow buttons have 
> about 2-3 second delay >before anything happens. FF/FRWD with left/right 
> buttons work.. mm.. just poorly, never can know in >which point of recording 
> it will start playing again when pressing play.

I can confirm this problem with all version of VDR and reel plugin it
is very frustrating and makes controlling playback of recordings
difficult.

Morfsta

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

> Can you try with vdr-1.7.4, that's the first version from vdr 1.7x
> series that i got working with s2api and hvr-4000.
> I have testeed it with streamdev server plugin and mplayer&vlc.

vdr-1.7.4 works fine with all my devices - but vomp isn't compatible
with it yet for replaying its recordings and also the rotor plugin
(which I use to move the dish and scan transponders) also won't
compile at the moment (I didn't search for any updates, anyone know if
it has been re-written for S2API or even if it is still being
maintained?) so I will stick with 1.7.0 multiproto for now and wait
for 1.7.4 / S2API to mature and become more widely supported with
plugins etc.

vdr-1.7.0 and the S2API patch doesn't work with DVB-T at all here, so
I guess there's a bug in the patch there somewhere that affects
reception of UK transmitters (perhaps handling of QAM 16 modulation?)

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger
 wrote:
>>> Have you considered trying VDR 1.7.4?

Klaus, 1.7.4 works fine with S2API and DVB-T here

Looks like there might be a problem in your patch somewhere Niels, but
not sure where? I would still prefer to use 1.7.0 if possible, as
expected a ton of plugins don't compile with 1.7.4... :-(

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

> I still think it's a problem with the channel.conf. For fun, please try
> using the old and default scan for DVB-T. Because I used the old dvb-scan
> with the option to output for VDR on my Gigabyte GT-U7000-RH based DVB-T
> adapter to scan for KPN Digitenne bouquets (location Zwolle/Apeldoorn).

Tried this, again finds all the channels but when put into VDR no
video appears (however I do see the programme listings in the EPG).

Any more ideas?

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger
 wrote:
> Well, even using *any* version 1.7.x in a productive environment
> is a risk ;-)
[SNIP]
> S2API was necessary for HDTV channels, and recording HDTV channels
> only makes sense in TS. The PES recording of HDTV broadcasts was never
> officially supported by VDR.

The other problem is that I don't think anyone has got VDR 1.7.4
working with the eHD yet, which is my output device... :-( So it seems
everywhere I look at the moment I am stuck. :-(

Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it
starts up? Is there perhaps a capability flag in the driver that has
not been setup for the devices that I am using? I compared the channel
settings of BBC ONE in VDR with multiproto version and s2api version
that I am running and they are exactly the same.

@Niels, which DVB-T devices are you using successfully with VDR-1.7.0
so that I can compare them with my own drivers? It seems strange
though that scan-s2 successfully finds all the channels but VDR won't
play them.

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

On Wed, Feb 4, 2009 at 10:46 AM, Klaus Schmidinger
 wrote:
> Have you considered trying VDR 1.7.4?

Eek! Isn't that the one that even you don't consider using in a
productive environment? ;-)

I'm not sure about the TS stuff and how that works and also that I
won't be able to replay normal/HD recordings etc or whether it will
work with VOMP or streamdev and all the other cool stuff I use. This
is the problem for trying to use VDR/S2API etc in a productive
environment with updated OS etc, it kind of leaves the users in a
limbo where too much is being changed at once with implemented S2API
*and* TS. :-(

I'm really confused now with where everything is at and what to do!

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

>> The Multiproto channels.conf should be interchangeable with S2API. But
>> *some* modulation types didn't exist in S2API when I wrote the patches and
>> you need to check this for yourself. You need to check the settings (Red
>> button to edit in the TV Channels overview) and see if they are indeed
>> correct and change them accordinly. My best guess, is that the modulation
>> types are wrong.

Sorry to double post but as an update I removed all DVB-T channels and
then rescanned them using scan-s2 from
http://mercurial.intuxication.org/hg/scan-s2/.  It found all the
channels on my transmitter. Also DVB-S channels seem to be working
fine, not tried S2 yet.

The new format for DVB-T presented is: -

BBC 
ONE;BBC:73:I999B8C34D34M16T2G32Y0:T:27500:600:601=eng,602=eng:0:0:4165:9018:4101:0

which is now accepted by VDR. However, I get a black screen when
tuning to them. In user.log I see: -

Feb  4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter0/frontend0
Feb  4 10:38:08 morfsta vdr: [18340] device 1 provides: DVBS DSS
Feb  4 10:38:08 morfsta vdr: [18344] tuner on device 1 thread started
(pid=18340, tid=18344)
Feb  4 10:38:08 morfsta vdr: [18345] section handler thread started
(pid=18340, tid=18345)
Feb  4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter1/frontend0
Feb  4 10:38:08 morfsta vdr: [18340] device 2 provides: DVBS DSS
Feb  4 10:38:08 morfsta vdr: [18347] tuner on device 2 thread started
(pid=18340, tid=18347)
Feb  4 10:38:08 morfsta vdr: [18348] section handler thread started
(pid=18340, tid=18348)
Feb  4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter2/frontend0
Feb  4 10:38:08 morfsta vdr: [18340] device 3 provides: DVBS DVBS2
Feb  4 10:38:08 morfsta vdr: [18340] device 3 forced to frontendType SYS_DVBS2
Feb  4 10:38:08 morfsta vdr: [18350] tuner on device 3 thread started
(pid=18340, tid=18350)
Feb  4 10:38:09 morfsta vdr: [18351] section handler thread started
(pid=18340, tid=18351)

which is funny  because devices 0 and 1 are DVB-T:

[   12.497993] DVB: registering adapter 0 frontend -858993460 (Philips
TDA10045H DVB-T)...
[   12.554597] DVB: registering adapter 1 frontend -858993460
(Conexant CX22702 DVB-T)...
[   12.594872] DVB: registering adapter 2 frontend 0 (Conexant
CX24116/CX24118)...

then when VDR starts tuning I see:

Feb  4 10:38:18 morfsta vdr: [18344] frontend 0 timed out while tuning
to channel 1, tp 642
Feb  4 10:39:18 morfsta vdr: [18347] frontend 1 timed out while tuning
to channel 1, tp 642
Feb  4 10:39:21 morfsta vdr: [18344] frontend 0 timed out while tuning
to channel 1, tp 642

Any suggestions?

Thanks

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

Re: [vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

On Wed, Feb 4, 2009 at 9:39 AM, Niels Wagenaar  wrote:
> Goodmorning!

Morning Niels, thanks for getting back to me so quickly!

> You might want to try Igor's repo
> http://mercurial.intuxication.org/hg/s2-liplianin)  since Steve's hasn't
> been updated for over 3 months. This however won't fix your problem perse.

OK, done that.

> Did you install mine S2API patch from 7-10 for VDR 1.7.0? Because this is
> the latest version and this has been tested with DVB-T, DVB-S, DVB-S2 and
> DVB-C. And with succes! ;)
>

Specifically I have installed:

vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff
vdr-1.7.0-s2api-07102008-h264-clean.patch

the only other plugin I am using at this stage is the reelbox plugin
output which seems to work fine.

> BTW, you might want to increase the logging for VDR or check the logfiles
> in /var/log what VDR has thrown out (Ubuntu uses /var/log/user.log for
> instance). My best guess is an frontend timeout error. This means that a
> timeout (duh!) occured when tuning to the selected channel. This can mean
> a reception problem (not likely, but good to point out) or a problem in
> your channels.conf.
>

Now I have recompiled it all and when I run VDR I get: -

vdr: error while reading '/video/config6/channels.conf'

in /var/log/user.log I see: -

Feb  4 10:06:01 morfsta vdr: [17791] loading /video/config6/channels.conf
Feb  4 10:06:01 morfsta vdr: [17791] ERROR: unknown parameter key 'A'
Feb  4 10:06:01 morfsta vdr: [17791] ERROR: error in
/video/config6/channels.conf, line 2

Line 2 is a DVB-T channel: -

BBC ONE;BBC:73000:A0B8C34D34G32I0M16P0T2Y0:T:27500:600:601=eng,602=eng:0:0:4
165:9018:4101:0

This channel works fine in vdr-1.7.0 with multiproto and there are
definitely no reception problems as all DVB-T and DVB-S channels works
fine with previous implementation (which I have kept in a seperate
parition obviously!).

> The Multiproto channels.conf should be interchangeable with S2API. But
> *some* modulation types didn't exist in S2API when I wrote the patches and
> you need to check this for yourself. You need to check the settings (Red
> button to edit in the TV Channels overview) and see if they are indeed
> correct and change them accordinly. My best guess, is that the modulation
> types are wrong.
>

It seems that the channels.conf isn't interchangeable as the
multiproto channels.conf now seems to be rejected and I can't even
start VDR now. Perhaps the leading A is now unsupported in the
options, is there a way I could possibly modify the file to remove
this stuff?

> See the above ;)

Any more ideas? ;-)

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

[vdr] VDR 1.7.0 & S2API - Channels not Available

[Morfsta]

Hi,

Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly
(it worked for me for months with no issues so why would I want to
change it for now?) trying to make the transition from multiproto to
S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have
downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api
patch and install S2API from Steven Toth's mercurial repository.

On booting the kernel loads all the modules and I see the various
frontends and when I start VDR it loads all of the relevant firmware
okay. When I start VDR it won't show any of the FTA channels on DVB-T
or DVB-S (not even tried S2!) and all I get is "Channel Not
Available". I wish VDR were more descriptive in why the channels are
not available! :-)

Apologies if this has been asked before, but is there anything I'm
missing? Is the problem that I took my channels.conf from my
multiproto VDR and something has now changed in the format?

It would be good to get this working as my old OS is now messy and
really needs a clean build with a shiny new kernel and I can't patch
up to date multiproto with the old HVR4000 patches (a few FAILS which
I guess I could fix, but might take some time as they don't look that
trivial) and an older version of multiproto from HG doesn't compile on
the new kernel!

Can anyone point me in the right direction on what might be going on?

Thanks

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

Re: [vdr] Options for deinterlacing (or not)

[Morfsta]

> Thomas Hilber  wrote:
>
>> Maybe some day FrameRateControl will allow for a pure open source HDTV
>> solution. Running with adequate picture quality on moderately powered
>> CPUs.

I think it is very important for HDTV without any other solution. One
of my main reasons for buying a eHD was that whilst xine / coreavc was
great for watching films (progressive source) etc, it was not good for
watching sport (interlaced source) and even with a Core2 Duo 3Ghz
enabling good interlacing (tvtime) resulted in the processor becoming
bound and huge amount of frame drops.

Taking this problem out of the equation would be a big help.

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

Re: [vdr] Which extension for TS files?

[Morfsta]

> I am strongly against this.
> *.ts may conflict with KDE, but it is a usual ending for transport stream.
> Several mpeg-tools can handle this. I think the dreambox is also using *.ts
> for its recordings.
>

I agree - .ts is the way to go if it a straight dump of the Transport Stream...

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

Re: [vdr] HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?

[Morfsta]

On Fri, Jan 2, 2009 at 8:53 PM, Gregoire Favre  wrote:

> I give up... thank for your answer.

I am still using multiproto here ... it works. :-)

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

Re: [vdr] 1080p ready VDR

[Morfsta]

On Thu, Dec 25, 2008 at 11:10 PM, Tony Houghton  wrote:
...
> (I haven't heard of anyone releasing a patch for the BBC HD audio pid problem 
> yet).
...

This is a fault with the broadcaster, not a problem with VDR. I have
informed the BBC of the problem and they have acknowledged the issue
and are going to fix it shortly (they say in the New Year after a
Christmas period "change freeze" period), so it should just go away.

Apparently it was due to an upgrade that the BBC applied to their
encoders. The problem doesn't cause any problems with Sky or Freesat
boxes so they didn't notice it in testing.

Must say, I was very impressed with their response and I'm looking
forward to seeing the fix being implemented.

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

Re: [vdr] VDR with S2API (update)

[Morfsta]

On Tue, Dec 9, 2008 at 7:48 PM, Georg Acher <[EMAIL PROTECTED]> wrote:
> Why all this eHD-bashing? Just because a *commercial* company already made a
> complete HDTV-vdr-solution more than 18 months ago that the vdr-community
> hasn't achieved until now?
>
> Of course the eHD won't live forever, probably not half as long as the
> FF-card, but it solved an imminent issue at that time and it allowed to run
> vdr and HDTV on it.
>
>
> The reelvdr code base is tested by a really large number of users (many
> thousands and not many geeks ;-) ). Is there any specific reason why you
> don't want to profit from the experiences RMM already made?
>

Georg,

I have bought an eHD for my vanilla VDR, possibly like many other
users on here - firstly I must say it is a nice solution, the picture
quality is very nice and unlike when I was using my 3Ghz Core 2
processor and xine output plugin with CoreAVC there are no issues with
deinterlacing of sport channels / live content etc and it looks
excellent with no stuttering etc - also leaves the CPU free.

However, there are some limitations of using one of these devices and
the problem is, where does one get support for the issues? I have
tried your support forum and found the answer to be that I should
implement your own version of VDR (based on 1.4.7?) because the
vanilla version does not currently use TS etc.

Are you selling single eHD cards solely for implementation within Reel
devices? If so, I believe you should make this clear as I wasn't aware
of this and other users won't be. Some of the problems I have when
running eHD with VDR 1.7.0 are: -

1) Upgrading the latest testing version SVN often causes problems with
compilation and you have to try and track down patches from other
sites, or for bleeding edge SVN there simply aren't any available
resulting in it not being possible to compile it. Would it be possible
for Reel to host patches that will apply to vanilla VDR to make this
operate, or have I missed this already?

2) Seeking forward/backward/play/pause/fast forward/fast rewind in
recordings does not work very well and there is a bad delay and lag
when using these functions. This is frustrating and irritates my wife!

3) You cannot play MKV files with the xine mediaplayer (although I
think this also applies to Reel products)

4) Some channels don't work, e.g. BBC HD (very important for us
Brits), SVT HD and others. Apparently BBC HD has been fixed in the
Reel products but it doesn't work for vanilla VDR

5) If the stream is interrupted (i.e. weak signal)  on HD channels /
recordings then the picture does not recover until a channel change.
This is a serious issue which needs to be addressed.

I hope the above helps, the eHD is a very nice solution but has some
issues and for vanilla VDR users
right now there doesnt appear to be any way to get them fixed.

Thanks,

Morfsta

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

Re: [vdr] VDR with S2API (update)

[Morfsta]

On Mon, Dec 8, 2008 at 11:05 AM, Manu Abraham <[EMAIL PROTECTED]> wrote:
> It might be a bit more time, to know the actual status, but the TS
> feature might be a still important feature, if that were to happen.

I am an eHD user and I'm hoping that the TS feature might improve
things as currently I can't watch BBCHD with my eHD because of
problems with the way they are broadcasting the PES ID for the AC3
stream. Also, there is a problem when there is a slight breakup in the
stream - the picture is unwatchable till changing the channel.
Apparently TS will address this. Reel's own implementation of VDR
already used TS and they say it is fixed in there, but it is not
currently fixed in the vanilla version of VDR.

Also, I'm hoping it might improve areas such as seeking and fast
forward/rewind which is currently poor using the eHD - there is bad
lag and it is not sensitive enough for pressing forward/back/play etc.

Any idea when TS will be implemented? Its been talked about for a long
time now... :-(

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

Re: [vdr] Switching time

[Morfsta]

On Fri, Dec 5, 2008 at 11:05 AM, Alex Betis <[EMAIL PROTECTED]> wrote:
> 2 channels on the same transponder - about 2 seconds - video and sound
> playing right after the switch.
> 2 channels on different transponders - about 4 seconds - sound is playing
> right after the switch, image is shown, but start moving about 1 more second
> later.

Sounds long, I can channel change on DVB-T and DVB-S almost instantaneously.

You can normally fix this by recompiling your kernel with low latency
settings (timer frequency, kernel queuing methods etc) - normally
selecting the best settings for a desktop helps.

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

Re: [vdr] MythTV Adds Support For NVIDIA VDPAU

[Morfsta]

On Mon, Dec 1, 2008 at 12:04 PM, Laz <[EMAIL PROTECTED]> wrote:
> I don't have an nVidia card on my vdr box so I can't play about with this:
> no DVB-T HD stuff in the UK for several years to come so I'm happy using
> CPU grunt for MPEG2 decoding for now.

DVB-T2 HD starts broadcasting in the UK in a phased rollout in 2009.

It might be coming sooner than you think!

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

Re: [vdr] HD playback (was Where is the H.264 patch?)

[Morfsta]

On Fri, Nov 28, 2008 at 11:02 AM, Klaus Schmidinger
<[EMAIL PROTECTED]> wrote:
> I haven't followed this lately, but if the broadcast stream contains
> AC3 data in PES packets with ID 0xC0, then the problem needs to be
> fixed at the broadcaster - VDR merely follows the standard.
> Unless, of course, a bug in VDR can be pointed out...

Hi Klaus,

Perhaps you are right, but the bizarre thing is that I don't see any
evidence on the Internet of other set top boxes suffering from this
problem. But 0xC0 is normally reserved for MPA audio right? Surely
this would cause problems with other STBs? I also don't see users of
other software (e.g. MythTV) having this problem, which seems a bit
suspicious.

I have uploaded a VDR recording of BBC HD to megaupload if you (or
anyone else) is interested in looking at it? Appreciate you might be
busy with other things right now though. Otherwise, I had a look in
device.c around

  case 0xC0 ... 0xDF: // audio
  ...

  case 0xBD: { // private stream 1
   ...
 case 0x80: // AC3 & DTS

but if 0xC0 is being used for audio I can't understand how this can be
adjusted to permit checking for the content of AC3 data too.

Thanks,

Morfsta

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

Re: [vdr] HD playback (was Where is the H.264 patch?)

[Morfsta]

Sorry to double post, but as an update to this the Reel Multimedia
guys have found that it appears that the AC3 track is currently being
broadcast in a PES packet stream with an ID of 0xc0, which could be
incorrect and AC3 should be broadcast with an id of 0xbd. Perhaps some
other set top boxes ignore the id and process the stream based on
content, but it causes severe problems with VDR, including stuttering
picture and no audio.

Klaus, do you have any idea of what they have done and whether it can
or should be fixed in VDR? The RMM guys believe the fix should occur
in VDR and not the eHD driver, which sounds right if other users with
xine/ffmpeg are also suffering.

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

Re: [vdr] HD playback (was Where is the H.264 patch?)

[Morfsta]

> I'm having trouble with playback though. I found "In The Night Garden"
> playing on BBC HD and tried testing with that. With vdr-sxfe the picture
> was mostly OK but very jerky while the sound was hopeless, mostly
> silence with a click or brief snatch of recognisable sound every few
> seconds.

Did you see my post recently about BBC HD not playing with the eHD
card? I am seeing the same symptoms.

>From what I can tell they have changed the way they broadcast the AC3
stream. I noticed they trialled it for a few days then went back to
the original method. Unfortunately they now seem to be using it
permanently which results in BBC HD being unwatchable whilst using
AC3.

Tony, try go into the DVB menu and turn "Use Dolby Digital" to off.
You will then be using the Mpeg Audio track which doesn't exhibit the
same problems here, but I think it has audio description enabled which
is quite irritating.

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

[vdr] BBC HD Problems

[Morfsta]

Hi,

There appears to have been some changes made recently to BBCHD on 28.2E: -

BBCHD:BBC:10847:vC56M2O35S0:S28.2E:22000:2328:2330=NAR;2329=eng:2331:0:6940
:2:2050:0

It is now not watchable with a reel eHD card - no audio and stuttering video.

The Reel support people are saying this is possibly because they have
started using AAC audio which is not supported by VDR.

Is anyone else having problems with this and FFMPEG or CoreAVC via
xine or is it still fine?

Thanks,

Morfsta

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

[vdr] VDR/eHD HD Picture Breakup

[Morfsta]

Hi,

I've posted this to the reel multimedia forum but have had no
response, so thought I'd try here.

This might have been covered in German on the VDR forum or on the Reel
forum so I'm hoping someone knows about it.

I am using VDR and eHD (SVN 8858) and I get picture break ups (ongoing
pixelisation and stutter) until I change channel up and down. This
happens only on HD channels and usually occurs after about 10 minutes
of completely normal viewing.

Has anyone experienced this and is there any fix?

Thanks,

Morfsta

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

Re: [vdr] VDR + extension HD, mediaplayer

[Morfsta]

On Wed, Nov 19, 2008 at 7:03 AM, Mattia Rossi <[EMAIL PROTECTED]> wrote:
> Hi Morfsta
> do you have a link to a test file to play with ?
>
> Mattia

They are all quite big, but you can download one from most torrent sites.

Try downloading any TV episode that is flagged as HDTV 720p.

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

Re: [vdr] VDR + extension HD, mediaplayer

[Morfsta]

On Tue, Nov 18, 2008 at 4:43 PM, Mattia Rossi <[EMAIL PROTECTED]> wrote:
> Hi Per,
> you really really want to follow the section
> Die Reelbox-Plugin´s installieren
> at this link:
> http://www.htpc-forum.de/forum/index.php?showtopic=4568&st=0
>
> it will show you step by step how to compile the necessary plugins
> (xinemediaplayer and filebrowser), and how to compile the xine library
> to allow the xine output to be processed by the eHd card
> (xineplug_hde.so).

Can anyone get the xine plugin and player to work with Matroska video
(MKV) HD files, or is this a known bug (it stutters badly).

Thanks,

Morfsta

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

Re: [vdr] ITV HD

[Morfsta]

> On Fri, 2008-10-24 at 14:10 +0100, Tony Houghton wrote:
>> I've read that ITV HD can only be viewd by pressing the red button on a
>> Freesat receiver. Does this mean VDR can't access it?
>>

VDR works fine with ITV HD since day 1 of broadcast - just put this in
your channels.conf: -

ITV HD;BSkyB:11428:hO0S0:S28.2E:27500:3401:0;3402:0:0:54207:0:0:0

Enjoy,

Morfsta

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

Re: [vdr] Syncearly + subtitles problem

[Morfsta]

> As I remember there was another problem - with audio/video sync. The sound was
> delayed more and more - I've patched the plugin myself to disable the
> audio/video sync algorithm. But in last versions (I'm now using the 8649
> version) it is ok. So it is maybe second reason of your problem.
>
> You could test if immediately after switching to the channel the sync of
> subtitles is good or significantly better then after some time (1-2 minutes)
> it could be the sync problem.

Is there a CHANGELOG somewhere or something similar showing what's
going on with the plugin development and the various revisions?

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

Re: [vdr] for ffmpeg-devels needs the problem h.264 samples

[Morfsta]

On Fri, Oct 3, 2008 at 6:53 PM, Goga777 <[EMAIL PROTECTED]> wrote:
> let's improve ffmpeg together !

Bah! After being trashed by Michael Niedermayer on the FFMPEG list
after mentioning bugs with PAFF interlacing and uploading test content
etc that never seemed to be even acted upon, I don't see why anyone
would be interested in helping the ffmpeg devs!

Anyway, I have moved to Reel Multimedia's eHD card in my VDR box ...
which is nice. I might write up my experiences on it thus far if
anyone is actually interested. There's not much English chat out there
on this card, mostly in German on vdr portal and reel's own portal.

Cheers,

Morfsta

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

Re: [vdr] VDR Development

[Morfsta]

What did I start?!

For what its worth, I think VDR had DVB-S2 support (albeit patches)
long before MythTV..

VDR does need some of its core functionality upgraded - for example
something like the Reel channel scan is badly missing, you should be
able to easily scan for transponders from within VDR, just like most
satellite receivers. I've always found setting up channel lists
painful. Also, other functions such as rotor, better disecq and
sourcecaps etc should also be embedded within the core functionality
by now.

Perhaps a step towards a repo would be for people to work simply on
these core patches with the aim to actually getting them integrated.
Like mini projects, working with Klaus on the final quality on each
one. Perhaps this might be a "half way" solution that satisfies more
people and eventually Klaus might then have his lieutenants to give
further access to.

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

Re: [vdr] VDR Development

[Morfsta]

On Thu, Sep 4, 2008 at 11:46 AM, Klaus Schmidinger
<[EMAIL PROTECTED]> wrote:

> This summer I had quite a few other things to do, and many times
> the weather was just too good to sit by the PC and do programming.
>
> I do intend to continue working on VDR, and I sure hope to find
> more time for it when the weather isn't so fine any more ;-)
>
> Klaus

Glad to hear you're still around and OK Klaus and that you're still
interested in VDR :-)

Sounds like the weather is better in Germany than it has been here in
the UK - we've had no summer for the second year running! Perhaps you
should move here, then we can enjoy VDR development all year round!
;-)

Enjoy!

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

[vdr] VDR Development

[Morfsta]

Hi,

Does anyone know what is happening with VDR development these days?
There doesn't seem to be much activity - is Klaus taking a long
holiday or very busy with work!? :-)

Please don't flame me for asking - I totally understand and appreciate
that Klaus does it in his spare time etc and we have no right to
demand development, but just that Klaus isn't here much these days and
there has not been any new version of VDR 1.7.x for quite some time
now. I presume other people must be wondering too what is going on
with the future development of VDR and whether there is any planned?

Hope everything is okay with Klaus too and he hasn't "disappeared" for
some reason...

Kind Regards,

Morfsta

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

[vdr] Possible PAFF interlaced stream bug(s) fixed in FFMPEG

[Morfsta]

The news you might all have been waiting for - untested here but the
below is reproduced from the FFMPEG Dev mailing list: -

>from: Paul Kendall <[EMAIL PROTECTED]>
>reply-to: FFmpeg development discussions and patches <[EMAIL PROTECTED]>
>to: [EMAIL PROTECTED]
>
>date: Sat, Jul 26, 2008 at 1:13 AM
>subject: [FFmpeg-devel] H.264 & interlacing artifacts
>
>Michael,
>It looks like the latest fixes to h.264 (I'm using revision 14405) seem to
>have fixed the artifacts for NZ DVB-T on the interlaced channels :-)
>
>I will do some more testing, but the results so far look good!
>
>I do see quite a few of these
>2008-07-26 12:04:56.757 [h264 @ 0xb7158230]number of reference frames exceeds
>max (probably corrupt input), discarding one
>
>and some of these
>2008-07-26 12:04:56.774 [h264 @ 0xb7158230]mmco: unref short failure
>
>Thanks
>Paul

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

Re: [vdr] Xineliboutput: segfault when started via init

[Morfsta]

On Fri, Jul 25, 2008 at 3:34 PM, it's me <[EMAIL PROTECTED]> wrote:
[...]
> but a
> automated start via init scripts lead to a segmentation fault (using both
> frontends local sxfe or vdr-sxfe).
>
> ** that's the message:
> --
> Jul 25 16:00:48 localhost kernel: [   59.299437] Local decoder/d[7275]:
> segfault at 0 ip 7f994e00b277 sp 4768ffa0 error 4 in
> libxine.so.2.0.0[7f994dfcd000+53000]
> --
>

It's a known bug that's been there for years - try starting the files
using su (e.g. su - -c  ), that should setup a proper
environment and it shouldn't segfault.

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

[vdr] OT: Deinterlacing algorithms [WAS:Re: [PATCH] RGB/PAL over VGA at variable frame rate]

[Morfsta]

On Wed, Jul 23, 2008 at 9:38 PM, Theunis Potgieter
<[EMAIL PROTECTED]> wrote:
> I notice a AV desync after 5 minutes, it definitely happens when it reaches
> an advertisement that was cut out, or when I jump to a advertisement. :(
>

I can confirm this also occurs with the latest version of vdr-xine.

Have you tried changing the audio.synchronization.av_sync_method in
xine-config to be resample instead of metranom?

I think I found this to be better: -

# method to sync audio and video
# { metronom feedback  resample }, default: 0
audio.synchronization.av_sync_method:resample

# always resample to this rate (0 to disable)
# numeric, default: 0
audio.synchronization.force_rate:48000

Cheers

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

Re: [vdr] xine tvtime parameters explained

[Morfsta]

On Tue, Jul 15, 2008 at 9:54 AM, Goga777 <[EMAIL PROTECTED]> wrote:
>
> is it good for 1080i/720p channels ?
>

Not on my athlon dual core 3Ghz. Too many dropped frames using
greedy2frame or tomsmocomp.

That is why in my patch for xine-lib-1.2 and coreavc I disabled the
interlacer by default as I use CoreAVC's interlacer (bob) which is not
as good particularly for interlaced source material such as sport.

With the current set-up you can use greedy2frame for SD material and
CoreAVC's interlacer for HD material. If anyone has found a way to
better deinterlace HD broadcasts then please let me know, or is it
simply a case of too much cpu power required to process both HD
material and use a high quality deinterlacer.?

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

Re: [vdr] latest xineliboutput cvs and HDTV

[Morfsta]

> i have mean xineliboutput with ffmpeg , I couldn't run vdr-xine + coreavc for 
> linux 170 + dshowserver
>
> Goga
>

Would be nice if xinelibout supported CoreAVC... :-\

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

Re: [vdr] [ANNOUNCE] vdr-webvideo 0.0.1

[Morfsta]

On Wed, Jun 25, 2008 at 7:58 PM, Antti Ajanki <[EMAIL PROTECTED]> wrote:
> I'm glad to announce a new plugin called Webvideo.
>
> The Webvideo plugin allows downloading video files from video sharing
> websites, such as YouTube or Google Video, to your hard disk using the
> VDR menu interface. This plugin only downloads videos, a separate
> program is needed to play them.
>
> The plugin is available at http://users.tkk.fi/~aajanki/vdr/webvideo
>
> Enjoy,
>
> Antti
>

Nice to see someone making a start on this - would be nice to have an
interface that does it all in one.

Has anyone looked at implementing the BBC iPlayer on VDR yet?

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

Re: [vdr] latest xineliboutput cvs and HDTV

[Morfsta]

On Wed, Jun 18, 2008 at 8:12 PM, Goga777 <[EMAIL PROTECTED]> wrote:
> today I updated cvs xineliboutput and I could run vdr 170 + xineliboutput on 
> dvb-s2 hdtv channels without any problems
>

Was that using CoreAVC, or just FFMPEG's H264 support?

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

Re: [vdr] coreavc for Linux (coreavc 1.7.0 + xine patches)

[Morfsta]

On Sat, May 17, 2008 at 8:42 AM, Gregoire Favre
<[EMAIL PROTECTED]> wrote:
> On Sat, May 17, 2008 at 09:47:09AM +0400, Igor wrote:
>
> But I can't apply the needed patch as :



> Could someone explain me how to have libxinevdec in my src dir ?

Patch isn't for HG version of xine, but for the latest release.

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

[vdr] OT: ITV HD Testing on Eurobird but receivable with VDR

[Morfsta]

Hi,

For those of you interested in picking up strange test broadcasts, ITV
HD is currently testing on Eurobird 1 @ 28.5E.

Apparently the channel is currently broadcasting in H.222 (MPEG4 in an
MPEG2 stream?), but can be picked up if you are using
VDR+XINE+COREAVC. Most set top box satellite receivers can't pull in
this channel at the moment.

Presently they are showing a loop of HD images of London at 1920x1088i.

I had to manually enter the information:

11428H / 27500
VPID: 3401
DPID: 3402
SPID: 54207

Anyway, if you are into picking up strange new test broadcasts
(particularly HD) with your VDR box then enjoy.

Cheers,

Morfsta

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

Re: [vdr] Judder with interlaced channels

[Morfsta]

On Fri, May 2, 2008 at 4:40 PM,  <[EMAIL PROTECTED]> wrote:
> I have some problems with interlaced channels on SD & HDTV. Judder and
> jitter and its good visible when I using a SD channel with a
> ticker-tape. If I tune to Discovery HD 1080i its shaking and stutter
> around but 720P channel like National Geographic HD are smooth. I
> don't know where to look at.
>

HDTV on VDR is still an evolving science. What are you using? Xine or
Xinelibout? Are you using FFMPEG or CoreAVC? What de-interlacing
options are you using?

Basically we need more info!

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

Re: [vdr] Defunct screensaver processes under Xine

[Morfsta]

> In file included from i386/dsputil_mmx.c:30:
> i386/mmx.h:24:2: warning: #warning Everything in this header is deprecated,
> use plain asm()! New code using this header will be rejected.
> i386/h264dsp_mmx.c: In function `put_h264_qpel4_h_lowpass_3dnow':
> i386/h264dsp_mmx.c:1881: error: can't find a register in class
> `GENERAL_REGS' while reloading `asm'

Did you say you are building this in a 32-bit chroot jail? If so, try running: -

linux32 bash

prior to the ./configure and make. You might also want to do a "make
distclean" prior to the configure too.

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

Re: [vdr] Defunct screensaver processes under Xine

[Morfsta]

On Tue, Apr 15, 2008 at 3:57 PM, Todd Luliak <[EMAIL PROTECTED]> wrote:

> No, I don't "need" Gnome and am looking into alternatives per your
> suggestion. I hate the idea of having to run a display manager at all, but
> the picture looks too good to back out now. ;)
>

You don't need a display manager - you can run VDR with a suitable
plugin at fullscreen right on top of X11.

> and applied the patch  "xine-lib-1.2hg-coreavc.diff" with fuzz,
> then ./autogen.sh --disable-dxr3; make
> only to end up with :
>

[cut]

> So I've been trying to work my way around that to no avail. Your thoughts
> there would be MORE than welcome!
>

Hmmm there isn't an actual compilation error in your paste, you might
have to provide some more lines from above it.

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

Re: [vdr] Defunct screensaver processes under Xine

[Morfsta]

On Mon, Apr 14, 2008 at 7:51 PM, Todd Luliak <[EMAIL PROTECTED]> wrote:
>
>
> I'd be happy if the screensaver never ran again, as it's of no use here
> whatsoever.
> Where do I begin looking to curb the creation of these zombies?
>

Do you need to run gnome at all? Its quite processor intensive if all
you are doing is using it to watch TV. See the other recent thread on
starting VDR/xine at boot time using startx / replacing the session
manager and those problems with gnome screensaver won't be apparent.

Also, there is a later version (patch) of CoreAVC for xine that I
released on the list which will apply to the hg version of xine (with
a bit of tweaking with more recent versions). The updated version will
support channels at resolutions different to 1920x1080i (there are
quite a few of them).

HTH

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

Re: [vdr] VDR and sky CAM

[Morfsta]

On Fri, Mar 7, 2008 at 12:32 PM, Tony Grant <[EMAIL PROTECTED]> wrote:
> Hello fans of British TV.
>
> At the moment I watch the FTA channels on 28.2/28.5 E I am thinking of
> investing £20 in a FTV card for the new freesat service.
>
> Is anyone using the card (or the sky card for existing service) with
> VDR? What kind of DVB-S card do you have (budget or FF)? What brand?
>

Hi Tony,

You can use a Dragon or Diablo CAM with your pay tv card and a FF /
budget card with CI interface, in fact I have tried this with my
Freesat card and it does work. There will be neglible impact on
performance. However, you will need to put your card in an original
Set Top Box once a month to update the card. This will work for all
channels, including HD.

It is also possible to do the whole thing in software using a phoenix
interface (no piracy involved here, just using the phoenix interface
to communicate with your original smart card). This will have more
impact on performance but will still probably be OK.  However, the
broadcaster may at some point decide to change the CAM encoding
format, rendering all but original set top boxes useless (although
this hasn't happened in 2-3 years).

BTW: You do not need a smart card for the forthcoming new FreeSat
service from BBC and ITV, it is all unencrypted (Channel 4 will be FTA
next month, Five to follow suit sometime over the year), including BBC
HD, C4 HD and ITV HD.

Hope this helps,

Morfsta

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

Re: [vdr] BBC EPG from sat ? (loadepg equivalent ?)

[Morfsta]

On Fri, Feb 29, 2008 at 4:32 PM, Brian <[EMAIL PROTECTED]> wrote:

> True, thats about all the info I retrive too. But, I had the occasional
> hang due to networking problems, and it never actually timed out. That
> may have been using Bleb as a source instead of radio times, I can't
> remember now.
> Anyway my solution was to use the at daemon so as not do block other
> things should this script hang.
>
> Cheers Brian
>

I think you can use TV_GRAB_DVB to convert the transponder data to XML
then xmltv2vdr should work to get it into VDR.

 http://www.darkskiez.co.uk/index.php?page=tv_grab_dvb

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

[vdr] [ANNOUNCE] Single CoreAVC Patch that Works with Xine-lib and Vdr-xine

[Morfsta]

Hi,

Attached is a patch to enable decoding of H264 video streams using the
CoreAVC Win32 DLL, the latest HG clone of xine-lib and Reinhard's
vdr-xine and of course VDR. CoreAVC is a commercial and fast
software-based H264 decoder.

To make this work: -

1) Download the latest mercurial xine-lib (hg clone
http://hg.debian.org/hg/xine-lib/xine-lib-1.2)
2) Patch it (cd xine-lib-1.2 ; patch -p 1 < xine-lib-1.2hg-coreavc.diff)
3) Make and install it in your usual way (e.g. ./autogen.sh
--disable-dxr3 ; make ; make install). You might want to remove old
xine-lib first (rm /usr/local/lib/libxine* ; rm -rf
/usr/local/lib/xine)
4) Make and install xine-ui (skip if already installed)
5) mkdir /usr/lib/win32
6) Put CoreAVCDecoder.ax (version 1.5.0 is the only version I can get
working - the version I have is called coreavcdecoder_unpacked.ax) in
/usr/lib/win32
7) Remove the old external ff decoder references (rm
/usr/local/lib/xine/plugins/2.0/xineplug_decode_ff.so  ; rm
/usr/local/lib/xine/plugins/2.0/xineplug_decode_qt.so)
8) Start VDR -Pxine
9) Run xine (xine  -f -pq -I -V xv -A alsa --post vdr_video --post
vdr_audio 
-Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1
vdr://tmp/vdr-xine/stream#demux:mpeg_pes)

You can also tweak some of the CoreAVC settings. See this page for
more details: -

http://code.google.com/p/coreavc-for-linux/wiki/RegisterCoreAVC

but change ~/.mplayer/registry32 with ~/.xine/win32registry.

Note, to increase performance I have disabled the xine de-interlacer
for H264 streams as by default the CoreAVC deinterlacer is enabled. I
don't think it's as good as the xine de-interlacer, but if you want to
try re-enable xine deint on your CPU (too slow on my 2.6Ghz dual core)
then edit xine's src/libw32dll/w32codec.c and re-enable "int field =
VO_BOTH_FIELDS | VO_INTERLACED_FLAG;" and comment out "int field =
VO_BOTH_FIELDS;"

Then you can disable CoreAVC's deinterlacer using the instructions on
code.google.com (registercodec -r ~/.xine/win32registry -k
"HKEY_CURRENT_USER\\Software\\CoreCodec\\CoreAVC Pro\\Deinterlace" -v
3 -t dword)

Note, I haven't written the majority of this patch, it has been
pulled together from about 4 other patches (budice's work on DVBN and
the google code site itself). I have added code to automatically
detect the size of the H264 stream and to set the aspect ratio of the
resultant picture as well as making it apply cleanly (hopefully!)  to
today's HG of xine.

Therefore, the code is nothing more than a total hack and will not
likely see inclusion in xine in it's current form. There is currently
H264 parsing occurring in the demuxer which is probably a "bad thing",
it should be moved out of there. Additionally, I have added a new
variable to the BITMAPINFOHEADER to pass the ratio from the demuxer to
the codec source which is also not ideal, but hey, it works!

It has been pretty stable for me over the last few days and is a vast
improvement over FFMPEG.

Finally, I urge you to go and BUY CoreAVC (http://www.coreavc.com) if
you are using this patch - it's only 15USD.

Let me know if there are any problems and good luck!

Cheers,

Morfsta


xine-lib-1.2hg-coreavc.diff.bz2
Description: BZip2 compressed data
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Re: [vdr] VDR - xine - CoreAVC

[Morfsta]

On Feb 11, 2008 11:03 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:

> I've posted the URL to the spec some weeks ago already. In that
> issue, have a look into Annex E.2.1, Table E-1, Page 313.
>

Sorry. I'll see what I can dig out to set that up properly. For now
hardcoding works well as most H264 channels are 16:9.

> Simply set the progressive_frame flag.
>
> To disable it completely for your decoder even in this case, do
> not set VO_INTERLACED_FLAG when getting the frame.
>

Yup, it was set right there and no need for it. Now CoreAVC runs with
much better performance with xine. No more dropped frames... :-)

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

Re: [vdr] VDR - xine - CoreAVC

[Morfsta]

On Feb 11, 2008 11:00 PM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:

> Which CPU are you using?
>

AMD BE-2350 overclocked to 2.6Ghz. Now running H264 channels like a
charm with CoreAVC.

Almost there

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