Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vdr] Re: Xine-plugin output - FIXME:xineDevice.c:686



Hi,

Stefan Norberg wrote:

On some channels I get "FIXME: xineDevice.c:686"...

I assume, these channels provide dolby audio and you
have enabled dolby audio in my plugin's settings. Am I correct?
I have enabled Dolby Audio, but I don't think the channels I'm experiencing
problems with are broadcast in Dolby Digital. It there any way of telling? I
You might have a look into xine's stream info.

had trouble playing dvd's (audio was like darth vader :) before I enabled
dolby in xine. I'll try to disable it tonight and see if it makes any
difference.
I know this issue for almost a year now, when I started coding on my plugin without DVB receiving equipment.

Yesterday, I've compiled the dvd plugin and the issue is still there. But I didn't use CVS for libdvdnav and libdvdcss, which are specified as requirement. Maybe, the issue has been fixed already in CVS, as Sven Gothel didn't mention anything about that.

I don't know, whether I'll manage it today, to get these two libs from CVS. Are you using the CVS versions?

On these channels audio (and eventually picture) breaks up when I bring up
the OSD while using the xine-plugin. It usually recovers after some time (15
secs or so), but I had crashes too while tuned to these channels.
>
These are mostly broken (while using xine-plugin):
SVT1:306000:C0M64:C:6875:4102:4358=sve;4614=sve:7942:B00,500:1022:40999:40:0
SVT2:306000:C0M64:C:6875:4103:4359=sve;4615=sve:7943:B00,500:1048:40999:40:0
Which application crashes (VDR or xine)?

In the case, that the femon plugin works on these channels, is the signal quality good or are there errors?

I have a broken NOVA-S (which needs to be sent in for repair, btw), that has a lot of errors on all vertical transponders for about 20 minutes after switching the system on. In that time, xine dies quite often. It seems, that the software decoder is not that fault tolerant, as it should be.

These are examples of channels that work fine:
CANAL+:338000:C0M64:C:6875:4097:4353=eng:7937:1:1023:40999:32:0
C MORE FILM:338000:C0M64:C:6875:4105:4361=sve:7945:B00,500:1080:40999:32:0
C+SPORT:338000:C0M64:C:6875:4104:4360=sve:7944:1:1047:40999:32:0

-----Original Message-----
From: vdr-bounce@linuxtv.org [mailto:vdr-bounce@linuxtv.org] On Behalf Of
Reinhard Nissl
Sent: Wednesday, June 02, 2004 1:00 AM
To: vdr@linuxtv.org
Subject: [vdr] Re: Xine-plugin output - FIXME:xineDevice.c:686

On some channels I get "FIXME: xineDevice.c:686"...
I assume, these channels provide dolby audio and you have enabled dolby
audio in my plugin's settings. Am I correct?

Currently, VDR splits large PES packets into smaller ones of size 2048
bytes. But xine can't handle these "continuation" packets. So I try my best to reassemble these packets to the original large packets.

BTW: large PES packets which contain A52 audio data are only handled
correctly by xine-lib-CVS, rc4a doesn't contain the necessary patches.

A FIXME indicates, that a part is missing for the assembly to create a large

packet. Usually, there are no more than 4 FIXME's in a sequence, after which

the assembly should get a new start packet to go on with.

A future solution might be, that VDR breaks the large packets at A52 frame bounderies. Therefore, packet assembly would no longer be necessary. Dr. Werner Fink would like a similar solution for stereo audio too, which would avoid some cracks in audio at cutting positions.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:rnissl@gmx.de





Home | Main Index | Thread Index