René | 1 Jan 2012 18:41

Re: LiveBuffer for vdr 1.7.x

On 23.12.2011 14:27 , Marc wrote:
> There is a typo error in vdr.c but that's all.
>
> For gentoo users, I attached the patches I use. I relocated some hunk of
> config.c and config.h and renamed USE_LIVEBUFFER to LIVEBUFFER in Makefile.
>
> Patch the ebuild and put the other patch in
> /etc/portage/patches/media-video/vdr-1.7.21 (I use the epatch_user tool
> instead of the script, see the ebuild patch).

Hi Marc,

I'm having trouble in getting the patch you posted to work in my setup. 
Could you please check if you find something that i screwed up?

http://paste.me.uk/1484.html

I have saved the patch as: 
0001-opt-96-livebuffer12-rmm.dpatch-rebased-onto-1.7.21.patch

What i did was that i deleted the message-headers etc from the file, and 
left the first row to be: diff --git a/Makefile b/Makefile

Best Regards,

René

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
(Continue reading)

Marc | 1 Jan 2012 19:23

Re: LiveBuffer for vdr 1.7.x

On 01/01/2012 18:41, René wrote:
> On 23.12.2011 14:27 , Marc wrote:
>> There is a typo error in vdr.c but that's all.
>>
>> For gentoo users, I attached the patches I use. I relocated some hunk of
>> config.c and config.h and renamed USE_LIVEBUFFER to LIVEBUFFER in 
>> Makefile.
>>
>> Patch the ebuild and put the other patch in
>> /etc/portage/patches/media-video/vdr-1.7.21 (I use the epatch_user tool
>> instead of the script, see the ebuild patch).
>
> Hi Marc,
>
> I'm having trouble in getting the patch you posted to work in my 
> setup. Could you please check if you find something that i screwed up?
>
> http://paste.me.uk/1484.html
>
> I have saved the patch as: 
> 0001-opt-96-livebuffer12-rmm.dpatch-rebased-onto-1.7.21.patch
>
> What i did was that i deleted the message-headers etc from the file, 
> and left the first row to be: diff --git a/Makefile b/Makefile
>
>
>
> Best Regards,
>
> René
(Continue reading)

René | 1 Jan 2012 20:44

Re: LiveBuffer for vdr 1.7.x

On 01.01.2012 20:23 , Marc wrote:
> Hi René,
>
> You can watch the output of the patch
> (/var/tmp/portage/media-video/vdr-1.7.21-r2/temp/0001-opt-96-livebuffer12-rmm.dpatch-rebased-onto-1.7.21.patch.out)
> and see where it fails.
>
> vdr 1.7.22 is out now on vdr-devel overlay. I'll post an updated patch
> for it tomorrow. It could work better on your configuration.

Hi Marc,

I pasted the output over here: http://pastebin.com/8eMsEuMf

It looks that it can't find the files to patch. Maybe the patch was not 
compatible with Gentoo?

It would be great if you could send an updated ebuild to 1.7.22 :-) I 
really miss the days when i updated my vdr on every release.. Now i have 
been "stuck" with 1.6.x for ages..

Do you think that it would be possible to add the livebuffer-patch back 
to the official gentoo overlay? Even better if it could be added as a 
basic feature of vdr (that could be turned on/off from the settings :-) 
Klaus? Please, please, pleaaaaase :-)

Regards,

René

(Continue reading)

VDR User | 1 Jan 2012 21:13
Picon

Re: LiveBuffer for vdr 1.7.x

On Sun, Jan 1, 2012 at 11:44 AM, René <linuxtv <at> hertell.com> wrote:
> the official gentoo overlay? Even better if it could be added as a basic
> feature of vdr (that could be turned on/off from the settings :-) Klaus?
> Please, please, pleaaaaase :-)

There was talk of this some time ago, though I don't think anything
solid came of it. I personally am not interested in it unless ram came
be used for the buffer storage. Having a harddrive (or even worse, an
ssd) in a constant write state 24/7 is not something I'd like to do.
Whatever the case, I think you'll be stuck with the patch for a while.

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
René | 1 Jan 2012 22:31

Re: LiveBuffer for vdr 1.7.x

On 01.01.2012 22:13 , VDR User wrote:
> There was talk of this some time ago, though I don't think anything
> solid came of it. I personally am not interested in it unless ram came
> be used for the buffer storage. Having a harddrive (or even worse, an
> ssd) in a constant write state 24/7 is not something I'd like to do.
> Whatever the case, I think you'll be stuck with the patch for a while.

I have set my livebuffer to use 2gb memory (hdd). If i would have 4gb 
ram (now i have just 1gb), then i would use a 2gb ramdisk for 
livebuffer, and the rest for my system. This would be more than enough.. 
:-) But having a patch working for vdr is ok too :-)

René

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
VDR User | 2 Jan 2012 01:19
Picon

Re: LiveBuffer for vdr 1.7.x

On Sun, Jan 1, 2012 at 1:31 PM, René <linuxtv <at> hertell.com> wrote:
>> There was talk of this some time ago, though I don't think anything
>> solid came of it. I personally am not interested in it unless ram came
>> be used for the buffer storage. Having a harddrive (or even worse, an
>> ssd) in a constant write state 24/7 is not something I'd like to do.
>> Whatever the case, I think you'll be stuck with the patch for a while.
>
> I have set my livebuffer to use 2gb memory (hdd). If i would have 4gb ram
> (now i have just 1gb), then i would use a 2gb ramdisk for livebuffer, and
> the rest for my system. This would be more than enough.. :-) But having a
> patch working for vdr is ok too :-)

RAM is cheap enough now days that having plenty of it isn't a problem
for most people. For example, 4GB will cost you less than a few hours
at the pub with friends. :)

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Torgeir Veimo | 2 Jan 2012 04:12

Re: LiveBuffer for vdr 1.7.x

On 2 January 2012 10:19, VDR User <user.vdr <at> gmail.com> wrote:
> On Sun, Jan 1, 2012 at 1:31 PM, René <linuxtv <at> hertell.com> wrote:
>>> There was talk of this some time ago, though I don't think anything
>>> solid came of it. I personally am not interested in it unless ram came
>>> be used for the buffer storage. Having a harddrive (or even worse, an
>>> ssd) in a constant write state 24/7 is not something I'd like to do.
>>> Whatever the case, I think you'll be stuck with the patch for a while.
>>
>> I have set my livebuffer to use 2gb memory (hdd). If i would have 4gb ram
>> (now i have just 1gb), then i would use a 2gb ramdisk for livebuffer, and
>> the rest for my system. This would be more than enough.. :-) But having a
>> patch working for vdr is ok too :-)
>
> RAM is cheap enough now days that having plenty of it isn't a problem
> for most people. For example, 4GB will cost you less than a few hours
> at the pub with friends. :)

The OP probably meant to have the option to use RAM directly without
fiddling with a RAM disk setup.

--

-- 
-Tor

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

René | 2 Jan 2012 08:21

Re: LiveBuffer for vdr 1.7.x

On 02.01.2012 5:12 , Torgeir Veimo wrote:
>> RAM is cheap enough now days that having plenty of it isn't a problem
>> for most people. For example, 4GB will cost you less than a few hours
>> at the pub with friends. :)
>
> The OP probably meant to have the option to use RAM directly without
> fiddling with a RAM disk setup.

This could be a nice feature, but setting up a ramdisk is also pretty 
easy..

-René

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

Lists | 2 Jan 2012 16:59
Picon

Crystalhd support and help

Hi all, I have a main frontend box running yaVDR 1.7.21 vdr and I have a version 1 AppleTV with a broadcom crystalhd module installed.  I'm running Ubuntu and have loaded from source the crystalhd kernel module and the libraries.

I have xbmc-pvr branch from yaVDR running on the appletv and it works most of the time but cannot keep up with 1080 most of the time (can for 720p).  Does anyone know if this branch has crystalhd support and how do I know if its using it?

Second, I would prefer to use vdr-xineliboutput and have installed vdr-sxfe and vdr-fbfe.  I don't need, nor want all the overhead of xbmc.  I'm thinking if I can one of these to work then it would be perfect - I could use the vdr OSD, etc.  However, I can't find a video module that will work properly.

vdr-sxfe shows me:
Available video drivers: vdpau aadxr3 dxr3 xv vaapi raw opengl xshm caca aa none xxmc sdl vidixfb vidix fb xvmc
Available audio drivers: pulseaudio alsa oss jack none file

I understand to 'use' crystalhd you have to invoke the vaapi video driver?  Is this correct?  When I try it, however, it says
libva: libva version 0.31.1
Xlib:  extension "XFree86-DRI" missing on display ":0".
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva: va_openDriver() returns -1

How can I get around this or is it possible with my setup?  Anyone got this going?

Thanks for any help.

Norm



_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Denis Loh | 2 Jan 2012 17:44

Renaming of all *.c files in *.cpp or equivalent

Hi,

I have a big wish for future development: Please rename all c++ files 
with *.c extensions into *.cpp or equivalent. Many IDEs may cope with 
*.c and treat them as c++ files. However, if not, you must force the IDE 
to do that, which is sometimes hard work to do. I think it is lesser 
work to rename them and edit the makefile to work with cpp for instance.

I am using cpp as default extension for c++ files for long time now.

What do you think about that?

Denis

_______________________________________________
vdr mailing list
vdr <at> linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Gmane