On 11.1.2011 22:20, Timothy D. Lenz wrote:
I would prefer a ffmpeg (mplayer) based interface and dump xine because
xine/vdpau combo doesn't properly handle problems with the atsc stream.
You can use ffmpeg decoding with xineliboutput.
~/.xine/config_xineliboutput:
# priority for ffmpegaudio de
Hi Tony,
setting the summary for timers has been dropped in VDRAdmin-AM years
ago, simply because that was also dropped in VDR. It's readonly now so
that one can see what plugins/tools (epgsearch...) add to a timer's
AUX field.
Best regards,
Andreas
2011/1/11 Tony Houghton :
> When setting a tim
Hi Tony,
please read my reply to your first mail.
Andreas
2011/1/11 Tony Houghton :
> On 11/01/11 20:17, VDR User wrote:
>>
>> On Tue, Jan 11, 2011 at 10:28 AM, Tony Houghton wrote:
>>>
>>> When setting a timer with vdradmin the popup includes a box which is
>>> supposed to contain the programm
On Wednesday 12 Jan 2011, Torgeir Veimo wrote:
> On 12 January 2011 13:09, VDR User wrote:
> > On Tue, Jan 11, 2011 at 4:40 PM, Torgeir Veimo
wrote:
> >> You can always try softdevice, which is mostly a playback interface
> >> using ffmpeg.
> >
> > Isn't softdevice abandoned?
>
> It hasn't see
> 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 th
On Wednesday 12 Jan 2011, Morfsta wrote:
> > 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
On 12/01/11 10:35, Andreas Mair wrote:
Hi Tony,
setting the summary for timers has been dropped in VDRAdmin-AM years
ago, simply because that was also dropped in VDR. It's readonly now so
that one can see what plugins/tools (epgsearch...) add to a timer's
AUX field.
Could you show it as a read
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
maybe he's thinking about when you click on a show, you get a popup box
with the show name and any other epg info vdr has.
On 1/11/2011 1:17 PM, VDR User wrote:
On Tue, Jan 11, 2011 at 10:28 AM, Tony Houghton wrote:
When setting a timer with vdradmin the popup includes a box which is
supposed
xineliboutput still uses xine. So it sounds like you are saying dump vdr
and keep xine. xine is the problem, not vdr.
On 1/11/2011 1:41 PM, Tony Houghton wrote:
On 11/01/11 20:20, Timothy D. Lenz wrote:
I would prefer a ffmpeg (mplayer) based interface and dump xine because
xine/vdpau combo do
When vdr was using the hardware video out of a nexus card, it worked
great. I had a LOT fewer problems. The video interface plugin should be
just that and nothing more.
It doesn't need support for irc in it
It doesn't need lirc support, that is in vdr
There is an mplayer plugin if you need to
Didn't nvidia do the early ffmpeg patch as part of the example of how to
support vdpau? That would explain why they work better together.
On 1/11/2011 9:30 PM, VDR User wrote:
That would be great actually. Or just having another option period
besides something dependent on libxine. The guy w
But you still need xine to use xineliboutput. Even if not using it for
decoding. I tried onec before when someone said it could use ffmpeg and
found it still depended on xine. Just like xine needs a lot of crap
installed to compile it that is never used. KISS
On 1/12/2011 3:04 AM, Pertti Kosun
On 12/01/11 18:09, Timothy D. Lenz wrote:
xineliboutput still uses xine. So it sounds like you are saying dump vdr
and keep xine. xine is the problem, not vdr.
You misunderstand. xineliboutput has a number of components:
1. A stream server plugin.
2. An integrated player plugin based on xine.
On Wed, Jan 12, 2011 at 10:31 AM, Tony Houghton wrote:
> 1. A stream server plugin.
> 2. An integrated player plugin based on xine.
> 3. Standalone xine-based players for connecting to the server.
>
> I propose using 1, ignoring 2 (you can disable it with CLI options, I do
> this anyway because it
On 12/01/11 18:42, VDR User wrote:
On Wed, Jan 12, 2011 at 10:31 AM, Tony Houghton wrote:
1. A stream server plugin.
2. An integrated player plugin based on xine.
3. Standalone xine-based players for connecting to the server.
I propose using 1, ignoring 2 (you can disable it with CLI options,
On Wed, Jan 12, 2011 at 11:15 AM, Tony Houghton wrote:
>>> 1. A stream server plugin.
>>> 2. An integrated player plugin based on xine.
>>> 3. Standalone xine-based players for connecting to the server.
>>>
>>> I propose using 1, ignoring 2 (you can disable it with CLI options, I do
>>> this anywa
On 12/01/11 20:31, VDR User wrote:
So there's no vdr output plugin option available that uses ffmpeg for
vdpau decoding and also provides the user with VDR's osd.
Hopefully someone capable of writing an output plugin will take
interest after reading all the recent posts on the subject.
So you
On Wed, Jan 12, 2011 at 2:33 PM, Tony Houghton wrote:
>> So there's no vdr output plugin option available that uses ffmpeg for
>> vdpau decoding and also provides the user with VDR's osd.
>>
>> Hopefully someone capable of writing an output plugin will take
>> interest after reading all the recent
19 matches
Mail list logo
