Bug 5262

Summary:	Video flickers when mplayer engine is used.
Product:	Fedora	Reporter:	V. <bug.report.tracker>
Component:	smplayer	Assignee:	Sérgio Basto <sergio>
Status:	RESOLVED EOL
Severity:	enhancement	CC:	fedora, leigh123linux
Priority:	P1
Version:	f30
Hardware:	x86_64
OS:	GNU/Linux
namespace:

Description V. 2019-05-13 20:20:39 CEST

When using mpv engine, everything seems to work fine.

However, with mplayer engine the following issues have been noticed:

1. Sometimes mplayer fails to play remote streams with default cache settings. Disabling "auto" in Preferences -> Performance -> Cache seem to helps.

2. Video flickers and sometimes disappears altogether when context menu
is opened over the video area (right click), or compact mode is toggled (Ctrl+C).
This doesn't happen when a video is played in a separate window,
or in a standalone mplayer.

The following packages are installed:
mplayer-common-1.4-1.fc30.x86_64
mplayer-1.4-1.fc30.x86_64
smplayer-19.1.0-2.fc30.x86_64

Thanks,
V.

Comment 1 Sérgio Basto 2019-05-13 20:41:28 CEST

Please try report upstream, this a develloping problem not packaging problem ... 

Looks similar to [1] Try enabling the option "frame drop" in preferences -> performance.

[1] 
https://forum.smplayer.info/viewtopic.php?f=2&t=11681

Comment 2 V. 2019-05-13 21:33:43 CEST

(In reply to Sérgio Basto from comment #1)
> Please try report upstream, this a develloping problem not packaging problem
> ... 
> 
> Looks similar to [1] Try enabling the option "frame drop" in preferences ->
> performance.
> 
> [1] 
> https://forum.smplayer.info/viewtopic.php?f=2&t=11681

Thanks!

BTW, looks like unchecking "Repaing the background of the video window" in Preferences -> Advanced helps to workaround the flickers and black artefacts.

However there seems to be more issues with mplayer, since sometimes
the following message constantly appears in mplayer log when playing remote streams:

[aac @ 0x7fd251783940]channel element 0.12 is not allocated

This doesn't happen the the stream is piped to a standalone mplayer by youtube-dl.

I've posted the issues to https://forum.smplayer.info

Thanks,
V.

Comment 3 Sérgio Basto 2019-11-07 20:30:50 CET

it should be fixed , can you confirm ? 

Thank you

Comment 4 V. 2019-11-22 17:13:52 CET

(In reply to Sérgio Basto from comment #3)
> it should be fixed , can you confirm ? 
> 
> Thank you

Still seeing "[aac @ 0x7feb2d9a4940]channel element 0.12 is not allocated" messages.

The flickering seem to have disappeared, though sometimes after full screen toggle the window stays black (not redrawn).

Packages used:
smplayer-19.10.2-1.fc30.x86_64
mplayer-common-1.4-1.fc30.x86_64
mplayer-1.4-1.fc30.x86_64

Thanks,
V.

Comment 5 Sérgio Basto 2019-12-26 03:55:23 CET

(In reply to V. from comment #4)

> 
> Still seeing "[aac @ 0x7feb2d9a4940]channel element 0.12 is not allocated"
> messages.

I saw something similar when video was not completed downloaded .i.e. the file was completely corrupted

Comment 6 V. 2019-12-26 13:06:24 CET

Seeing this with any(In reply to Sérgio Basto from comment #5)
> (In reply to V. from comment #4)
> 
> > 
> > Still seeing "[aac @ 0x7feb2d9a4940]channel element 0.12 is not allocated"
> > messages.
> 
> I saw something similar when video was not completed downloaded .i.e. the
> file was completely corrupted

This happens with video streams. Not sure if they are corrupt. Seem to be played fine with mpv.

For example:

# mplayer http://content.jwplatform.com/manifests/vM7nH0Kl.m3u8

or

# smplayer http://content.jwplatform.com/manifests/vM7nH0Kl.m3u8
View -> MPlayer/mpv log (Ctrl + M)

Thanks,
V.

Comment 7 leigh scott 2020-05-27 03:25:29 CEST

Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.