Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
On Saturday 02 October 2010, you wrote: I'm currently using text2skin and Enigma without channel logos with 1.6.0-2 and it works fine for me. Forgot to mention that I'm not 100% sure if it's OSD related, but the only situation where I frequently run into problems in this setup is when working with cut marks; especially when moving them the OSD seems to get stuck or corrupt quite often. Sometimes just waiting a few seconds fixes it, sometimes restarting the replay and editing does the trick, and sometimes VDR restarts. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
I now tested vdr-dxr3-0.2.11.. It is perfect otherwise, but OSD is all messed up. Subtitles work fine, though! Good to hear. The git version has working OSD, but subtitles bug sometimes (they often appear in wrong location on screen). Also git version doesn't have working audio, which basicly forces me to use this 0.2.11 version anyway. :) But working OSD would be nice. Which skin do you use? The TROUBLESHOOTING file included with the plugin contains tips that work for some people at least with earlier VDR versions. I'm currently using text2skin and Enigma without channel logos with 1.6.0-2 and it works fine for me. Hi! I use ST:TNG.. I tried the classic vdr and it was the same. I haven't tried any others. I'm using VDR 1.7.15.. Anyway, there must be some difference between git and your version, I'll try to diff them.. :) It's annoying to have two almost working versions. :) git version is fine except for the audio and subtitles, and 0.2.11 is fine except for the OSD. So now we just need to combine the working features of both versions. :) -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
Al 02/10/10 09:51, En/na Teemu Suikki ha escrit: It's annoying to have two almost working versions. :) git version is fine except for the audio and subtitles, and 0.2.11 is fine except for the OSD. Mmh, strange, my osd is working (with the usual problems but mostly working). Note that my version is not exactly the same as the cvs one, but there should be no differences wrt the osd. So now we just need to combine the working features of both versions. :) They diverged too much, that's why I first tried the git version then I went back to the cvs one. Bye. -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Problem with VDR 1.7.15 and dxr3plugin 0.2.10
Hi!
I managed to fix 0.2.11 OSD.. It's quite simple, in file dxr3osd_subpicture.c
*** 87,92
if (Areas[i].bpp != 1
Areas[i].bpp != 2
! Areas[i].bpp != 4
! Areas[i].bpp != 8)
{
return oeBppNotSupported;
--- 87,91
if (Areas[i].bpp != 1
Areas[i].bpp != 2
! Areas[i].bpp != 4)
{
return oeBppNotSupported;
--
So apparently Areas are not supported in 8bpp? I checked both git
versions (master and buffer-and-sync-rewrite) and they also have 8bpp
removed just like above.
--
Teemu Suikki
http://www.z-power.fi/
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cSdtFIlter and LinkChannels
I'm trying to understand cSdtFilter in order to write a channel scanner. will it the plugin for vdr with possibility to scan dvb-s2 channels ? Goga I see that when it finds a SI::NVODReferenceDescriptorTag it will add it to the previously found channel with channel-SetLinkChannels, but it only does if it is in the current section (channel is a local variable) while the sdt could span several sections. From the specifications here http://neuron2.net/library/mpeg2/iso13818-1.pdf and here http://www.dvb.org/technology/standards/a005r5.tm1324r13.tr101211.v1.10.1.pdf I don't understand if this mechanism is correct, shouldn't the time_shifted_services link to the NVOD_reference? Besides, I don't see that the relation between a channels and its linkchannels is preserved in channels.conf (though I don't really care). I also see that cSdtFilter starts processing with the first section, and that shouldn't really be necessary as long as one processes all sections. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cSdtFIlter and LinkChannels
Al 02/10/10 12:19, En/na Goga777 ha escrit: I'm trying to understand cSdtFilter in order to write a channel scanner. will it the plugin for vdr with possibility to scan dvb-s2 channels ? Hi, no, it's integrated in the actuator plugin. It should work with s2 channels, but I've no means to check it (currently using dvb-s and there are no interesting channels for me in s2). Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr xine-lib eac3
Hi
I play with your sample , it has only one audio track and strictly no sound on
it ...
So I decide to replace my recent xine-ui by the very latest here
http://hg.debian.org/hg/xine-lib/xine-ui/
xine-lib is latest one with only your patch in mpeg-pes
ffmpeg is the full latest git with absolutely no patch
the result is the same ..
So I destroy the /.xine/config file and I can open the ts file and play with
audio track .. if I play too hard, I have the message saying :
-load_plugins: plugin vdpau_h264 will be used for video streamtype 4d.
-Broken NAL, skip it.
-ffmpeg_audio_dec: augmentation du buffer à 98304 pour éviter sa saturation.
-load_plugins: plugin ffmpegaudio will be used for audio streamtype 41.
-ffmpeg_audio_dec: trying to open null codec
-audio_decoder: no plugin available to handle 'E-AC-3'
no more sound available ... so it's better
Back to vdr, I try to play with sound track and crash immediatly
I remark that when crashing, and running xine-ui to reconnect to vdr playing
my records, it has stop replay and fall back to live TV .. strange !!!
I was focusing on xine but on vdr log there is a message I didn't saw :
-SetPlayMode: 0
-SetPlayMode: 1
-SetPlayMode: 0
-SetPlayMode: 1
-SetDigitalAudioDevice: 1
-::write(2048) returned -1, error 32: Broken pipe
-vdr-xine: Client disconnected!
-SetPlayMode: 0
-SetPlayMode: 1
-SetDigitalAudioDevice: 0
I will report on our forum this event and ask my colleague to check also this
part if they have time. In a short way does it means that vdr-xine ask
xine-ui to break itself and stop replaying ?
For myself, I will break for one week hoping somebody will continue to test or
find what can be wrong in our basis config
Thanks for your help and sorry to not have enough skills to debug or
understand the source code
Best regards
Le Saturday 02 October 2010 12:54:07 Jose Alberto Reguero, vous avez écrit :
I use latsest xine-ui hg. The problem may be ffmpeg or xine-lib or xine-ui.
Are you sure that you have the latest versions and no aditional patches?
You can do hg diff o svn diff to see the changes you have in the
repositories. Here is a sample:
http://dl.free.fr/pByrnmYwZ
Jose Alberto
El Viernes 01 Octubre 2010, dplu escribió:
Hi
I continue to search why it fail ... with no luck, hope other people will
have time to make test
basis test setup :
vdr 1.7.15 extention patch + patch e-ac3 for vdr-xine
xine-ui 0.99.6
latest git ffmpeg
latest xine 1.2 with basic e-ac3 patch for only
From vdr : crash every time I change audio track as described previously
Second test
Try opening the TS file from xine-ui directly, same behaviour
op mode :
At startup sound track is 0 (should be fra), play nice
track --
display track off , no crash
track ++
display 0 instead of fra , no crash
track ++
display qaa , it's real name .. crash in couple of seconds
Here is the log with high verbosity
http://pastebin.com/BvGKDk0v
Hope this help you, I underline in yellow some strange thing
By the way, if you have time, can you post a sample of recording made at
home so we can also test your sample with our configuration
Many thanks for your help and have a nice week end
Best regards
Le Thursday 30 September 2010 22:51:34 dplu, vous avez écrit :
Here is the result of my colleague using vdr-sxfe verbose and changing
the audio track
[9665] [demux_vdr] audio stream changed: 0341 - 03410001
Erreur de segmentation (=segfault error)
As you can see this is the same error , he use this patch
diff -r cb99a1abe986 src/combined/ffmpeg/ff_audio_decoder.c
--- a/src/combined/ffmpeg/ff_audio_decoder.c Fri Apr 09 18:55:47 2010
+0200 +++ b/src/combined/ffmpeg/ff_audio_decoder.c Sat Apr 10 16:23:14
2010 +0200 @@ -219,6 +219,12 @@
this-context-extradata_size);
break;
}
+ case BUF_AUDIO_EAC3:
+ case BUF_AUDIO_A52:
+ {
+ this-context-request_channels = 2;
+ break;
+ }
default:
xprintf(this-stream-xine, XINE_VERBOSITY_LOG,
ffmpeg_audio_dec: unknown header with buf type 0x%X\n, codec_type);
We continue to investigate
thanks for your help
Le Thursday 30 September 2010 22:40:34 dplu, vous avez écrit :
I will add this patch to my xine-lib and rebuild all
Here are two more samples to test given by colleague, I will also
wait the answer from Karim Afifi to have comparative tests
http://dl.free.fr/mE6yTLPnx
http://dl.free.fr/u2dWSU5R8
Other idea : may it comes from my xine-ui version ? did you use a
fresh one from http://hg.debian.org/hg/xine-lib/xine-ui/
Many thanks for your help and have a nice evening
Le Thursday 30 September 2010 22:27:52 Jose Alberto Reguero, vous
avez
écrit :
The error you report doesn't matter. It is because there is no case
for EAC3. I have an additional patch to use only two channels, and
I don't have this error. You can
