2.6.11 - I-Frame Seeking/Display Problems?

Started by ProfYaffle, February 16, 2016, 04:22:09 PM

Previous topic - Next topic

ProfYaffle

Just wondering if this is personal to me before I do any more digging...

I built 2.6.11 on Ubuntu (Xubuntu 14.04.3/3.19 amd64 on Intel chippery, FWIW) and installed the debs straight over my existing 2.6.10 installation.

I use avidemux primarily for snipping commercials out, so I manually find the start of a break, fine-tune to the most appropriate I-frame, repeat for the end of the break and cut. Rinse, repeat, save to mkv with acodec and vcodec as copy. All is good.

However, I immediately noticed that 2.6.11 seems to have trouble finding I-frames. It would either skip forwards (I use the keyboard up/down) but insist it was on a B-frame, or else skip forward and leave the rendered (frame preview) image the same. If it worked correctly at all, then playing the file in avidemux for a few seconds was a sure way of breaking it until I reopen the file - not convenient if you're trying to cut accurately, as cutting and then playing is the best way of testing the edit.

I used Qt4 originally, but built and tried Qt5 as well on the basis that "it had been tested more". No change. Reverting to 2.6.10 and everything works as intended once again. This is on H.264 .ts files (i.e. HD television recordings) - mainly AC3 audio.

Does this sound at all familiar to anyone else? I've been watching the forum and the bugs to see if anyone else has something similar - but, so far, silence...

(and I hate to sound like I'm complaining, as I use avidemux every day and - bar the odd crash - it serves me exceptionally well, so thanks!).

ProfYaffle

Just to eliminate my build environment, I just tested Jan Gruuthuse's latest build (commit 9bbd849, dated 16/02/2016) - same issue. Nothing seems to change whether I try X11, Libva, VDPAU or any other display driver either.

mean

That's weird, it could be related to the frame seeking bug that has been fixed
Could you post a small sample of your TS file + explanations on what you do ?

The easiest i can reproduce, the fastest it is fixed in general

ProfYaffle

Thanks for the rapid response. So clearly not a recognised issue, then, which was what I'd assumed.

I'll do a bit more testing first - I've just tried a clean VM of Xubuntu 15.10 (Win10 host) and a couple of dd'ed samples cut from a file that was giving me problems, and they appear to work fine. So I need to establish whether those samples are good for some reason, or whether it's an OS/driver/kernel-specific issue on my 14.04 box.

I might also simply run avidemux from the command line and see if it's unusually complaining about anything...

"I'll be back", as a wise Austrian once said.

ProfYaffle

Well, this is strange...

After confirming all was well on my test VM, I turned to my real system.


user@system:~/Downloads/avidemux3_2.6.11-160216-64bit_14.04_LTS-Trusty-x265-1-5-debs$ dpkg-query -l | grep avidemux
ii  avidemux3-cli-dev                           2.6.10                                       amd64        Simple video editor,main program, command line version
ii  avidemux3-cli-runtime                       2.6.10                                       amd64        Simple video editor,main program, command line version
ii  avidemux3-core-dev                          2.6.10                                       amd64        Simple video editor,core libraries
ii  avidemux3-core-runtime                      2.6.10                                       amd64        Simple video editor,core libraries
ii  avidemux3-plugins-cli-plugins               2.6.10                                       amd64        Simple video editor, plugins (CLI
ii  avidemux3-plugins-common-plugins            2.6.10                                       amd64        Simple video editor, plugins (COMMON
ii  avidemux3-plugins-qt4-plugins               2.6.10                                       amd64        Simple video editor, plugins (QT4
ii  avidemux3-qt4-dev                           2.6.10                                       amd64        Simple video editor,main program qt4 version
ii  avidemux3-qt4-runtime                       2.6.10                                       amd64        Simple video editor,main program qt4 version
ii  avidemux3-settings-settings                 2.6.10                                       amd64        Simple video editor, settings

user@system:~/Downloads/avidemux3_2.6.11-160216-64bit_14.04_LTS-Trusty-x265-1-5-debs$ sudo dpkg -i *.deb
[sudo] password for user:
(Reading database ... 1340678 files and directories currently installed.)
Preparing to unpack avidemux3-cli-2.6.11-160216-runtime.deb ...
Unpacking avidemux3-cli-runtime (2.6.11-160216) over (2.6.10) ...
Preparing to unpack avidemux3-core-2.6.11-160216-runtime.deb ...
Unpacking avidemux3-core-runtime (2.6.11-160216) over (2.6.10) ...
Preparing to unpack avidemux3-plugins-CLI-2.6.11-160216-plugins.deb ...
Unpacking avidemux3-plugins-cli-plugins (2.6.11-160216) over (2.6.10) ...
Preparing to unpack avidemux3-plugins-COMMON-2.6.11-160216-plugins.deb ...
Unpacking avidemux3-plugins-common-plugins (2.6.11-160216) over (2.6.10) ...
Preparing to unpack avidemux3-plugins-QT4-2.6.11-160216-plugins.deb ...
Unpacking avidemux3-plugins-qt4-plugins (2.6.11-160216) over (2.6.10) ...
Preparing to unpack avidemux3-qt4-2.6.11-160216-runtime.deb ...
Unpacking avidemux3-qt4-runtime (2.6.11-160216) over (2.6.10) ...
Preparing to unpack avidemux3-settings-2.6.11-160216-settings.deb ...
Unpacking avidemux3-settings-settings (2.6.11-160216) over (2.6.10) ...
Setting up avidemux3-core-runtime (2.6.11-160216) ...
Setting up avidemux3-plugins-cli-plugins (2.6.11-160216) ...
Setting up avidemux3-plugins-common-plugins (2.6.11-160216) ...
Setting up avidemux3-plugins-qt4-plugins (2.6.11-160216) ...
Setting up avidemux3-qt4-runtime (2.6.11-160216) ...
Setting up avidemux3-settings-settings (2.6.11-160216) ...
Setting up avidemux3-cli-runtime (2.6.11-160216) ...

user@system:~/Downloads/avidemux3_2.6.11-160216-64bit_14.04_LTS-Trusty-x265-1-5-debs$ dpkg-query -l | grep avidemux
ii  avidemux3-cli-dev                           2.6.10                                       amd64        Simple video editor,main program, command line version
ii  avidemux3-cli-runtime                       2.6.11-160216                                amd64        Simple video editor,main program, command line version
ii  avidemux3-core-dev                          2.6.10                                       amd64        Simple video editor,core libraries
ii  avidemux3-core-runtime                      2.6.11-160216                                amd64        Simple video editor,core libraries
ii  avidemux3-plugins-cli-plugins               2.6.11-160216                                amd64        Simple video editor, plugins (CLI
ii  avidemux3-plugins-common-plugins            2.6.11-160216                                amd64        Simple video editor, plugins (COMMON
ii  avidemux3-plugins-qt4-plugins               2.6.11-160216                                amd64        Simple video editor, plugins (QT4
ii  avidemux3-qt4-dev                           2.6.10                                       amd64        Simple video editor,main program qt4 version
ii  avidemux3-qt4-runtime                       2.6.11-160216                                amd64        Simple video editor,main program qt4 version
ii  avidemux3-settings-settings                 2.6.11-160216                                amd64        Simple video editor, settings

user@system:~/Downloads/avidemux3_2.6.11-160216-64bit_14.04_LTS-Trusty-x265-1-5-debs$ sudo dpkg -r avidemux3-cli-dev avidemux3-core-dev avidemux3-qt4-dev
(Reading database ... 1340719 files and directories currently installed.)
Removing avidemux3-cli-dev (2.6.10) ...
Removing avidemux3-core-dev (2.6.10) ...
Removing avidemux3-qt4-dev (2.6.10) ...
user@system:~/Downloads/avidemux3_2.6.11-160216-64bit_14.04_LTS-Trusty-x265-1-5-debs$ dpkg-query -l | grep avidemux
ii  avidemux3-cli-runtime                       2.6.11-160216                                amd64        Simple video editor,main program, command line version
ii  avidemux3-core-runtime                      2.6.11-160216                                amd64        Simple video editor,core libraries
ii  avidemux3-plugins-cli-plugins               2.6.11-160216                                amd64        Simple video editor, plugins (CLI
ii  avidemux3-plugins-common-plugins            2.6.11-160216                                amd64        Simple video editor, plugins (COMMON
ii  avidemux3-plugins-qt4-plugins               2.6.11-160216                                amd64        Simple video editor, plugins (QT4
ii  avidemux3-qt4-runtime                       2.6.11-160216                                amd64        Simple video editor,main program qt4 version
ii  avidemux3-settings-settings                 2.6.11-160216                                amd64        Simple video editor, settings

user@system:~/Downloads/avidemux3_2.6.11-160216-64bit_14.04_LTS-Trusty-x265-1-5-debs$


... and all seems to be working perfectly. I've installed two or three times previously, and had the problem every time... but not here.

The only thing I did differently is to force a truly clean installation - you can see above that I checked the installed packages and made sure all traces of 2.6.10 were removed before running the new version. Yes, lazy of me previously, I know. However...

1. That means that when I built and installed the Qt5 version, I'd still have had some of the Qt4 packages installed (e.g. both avidemux3-qt4-dev and avidemux3-qt5-dev)
2. When I installed Jan's debs, I'd have had the 2.6.11 Qt4 installed but would still have had the 2.6.10 dev packages installed (as his build doesn't include these so wouldn't have updated them)

I don't know if that's relevant, but it's all I can see immediately as a reason, unless some other package updates have fixed the problem (the only updates today were, I suspect, mainly related to the libc bug that's been on the news - nothing specifically A/V-related that I can see:


The following packages will be upgraded:
  base-files initscripts libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev
  libc6-i386 multiarch-support sysv-rc sysvinit-utils thermald
)

So.... I'll keep monitoring, but it might have been a false alarm. I'll leave this here anyway, just in case someone else wants to join in!

ProfYaffle

The only other thought I had is whether it's anything to do with libva hardware acceleration, as I think I played with that (it's a i7 system using on-board HD 4600 graphics). I'll need to do some structured observation *if* it comes back again...

mean

Or you had several versions installed at different places and you used the old one by mistake

ProfYaffle

Possible, though I'm not immediately sure how - it was definitely 2.6.11 (cosmetic changes to the slider/seek bar) and it was started from a menu shortcut that points specifically to /usr/bin/avidemux3_qt4 (actually, padsp /usr/bin/avidemux3_qt4 because of some OSS sound issues once upon a time).

Who knows. If it's not there now, I won't lose any more sleep over it. Thanks for chiming in all the same!

mean

There was indeed another seeking bug
It was not Off-by-one but could be several minutes, and needed a specific environment to trigger

Fixed in head , nightlies are building

ProfYaffle

Thanks for that - I'll build and test a new version as soon as I get a chance.

ProfYaffle

I've been using b289f8b for a couple of days now... no problems to report, and no re-appearance of my seek issue. Related? Hard to say, as it had gone into hiding already (as above). Updating certainly didn't bring it back, though, and all appears to be going well... (so thank you!).

mean

For information
i fell into that bug on a very specific movie i recorded & wanted to reencode
It happened at the end of an ad. At the end of the ad , you go previous keyframe and it jumped back before th beginning of the ad

That made a 100% reproducible use case & enabled me to investigate & find the problem, which was a bug in the dichotomic search for a frame
It only happened when the frame seeked was on a 1+1/2+1/4+1/8 boundary