https://bugs.kde.org/show_bug.cgi?id=407153
--- Comment #11 from Mauro Carvalho Chehab <mchehab+sams...@kernel.org> --- (In reply to Wolfgang Bauer from comment #10) > (In reply to Wolfgang Bauer from comment #9) > > This obviously leaks the eventManager though, I suppose I can look into > > trying to fix that too... > Or does it? > I'm not completely sure, but maybe the event should be detached again > somewhere? I'm not completely sure either, but it doesn't hurt to explicitly detach it at unregisterEvents(). Did some tests here with RPi3. It seems that it fixed the issue here, although RPi3 is too slow for ISDB-T/H.264 decoding, even for low-res mobile channels. (In reply to Wolfgang Bauer from comment #8) > (In reply to Mauro Carvalho Chehab from comment #5) > > VLC < 3 has a problem with H-264 parser, with causes it to not work properly > > with MPEG-TS: the problem is that it doesn't properly find the start of an > > H.264 frame. When a TV channel is switched, it is unlikely to get the start > > of an H.264 frame: it will generally get in the middle. In practice, one has > > to try several times to setup a channel until VLC recognizes the stream. > > Well, my DVB card doesn't support DVB-S2 (only DVB-S), so I can't tell. > > > Also, it doesn't support new types of encoding, like H-265. > > It should support H.265 via the libavcodec plugin I think. It is not a matter of just having support at libav. The libVlc is reponsible to identify the used codecs from the video descriptors within the MPEG Transport Stream. Also, most codecs assume that you're decoding the video from the start of a frame. When you're watching life TV, at the moment a channel is switched, you'll start receiving MPEG-TS frames, receiving data usually in the middle of a frame. It is up to libVlc to identify that, wait until the end of the frame and only after that send the frames for decoding. The sync logic for H.264 is broken on 2.x (at least last time I tested). I warned VLC developers about that - and I guess I even opened a bug - but didn't receive any feedback about a fix. I'm almost sure that the descriptors for H.265 (any any other needed sync code) got added only during 3.x development, but it would be possible that someone may have backported to 2.x. -- You are receiving this mail because: You are watching all bug changes.
