Started by fjbg, February 15, 2021, 06:09:21 AM
Quote from: fjbg on February 16, 2021, 05:14:04 AMmy concern is a long loading with some mp4 files (almost instantly with 2.7.5)
Quote from: fjbg on February 16, 2021, 05:14:04 AMslow motion when reading them (like 1/2 speed).
Quote from: fjbg on February 16, 2021, 05:14:04 AMI'll stick like this for now as everything seems perfect.
Quote from: eumagga0x2a on February 16, 2021, 07:18:51 AMOld versions like 2.7.5 didn't bother to identify the exact frame type (P-frame or B-frame, keyframe info was taken from the container and simply trusted) in MP4 containers with H.264 video streams. This means, all frames were assumed to be P-frames unless the video was decoded and the decoder identified the correct type. This rendered some checks, necessary for copy mode, ineffective.With many issues affecting copy mode fixed, it became important to know the correct frame type right when the video is loaded.If you don't use copy mode, you can safely interrupt the scan by pressing "ESC" while a MP4 file is being analyzed. If you do use copy mode, Avidemux needs to know the real frame type for H.264 now.
Quote from: eumagga0x2a on February 16, 2021, 07:18:51 AMPlease clarify. Does "reading" stand for "loading" or for "playing back"? Current builds allow to use decoder multithreading in libavcodec at the cost of disabling HW decoder. With modern multicore CPUs, this hugely boosts decoding speed. If you never re-encode, keeping HW accel enabled, especially on Linux with VDPAU and VA-API (libva) HW accels, is beneficial for lowering energy consumption.However, there is a known issue with GUI going unresponsive during playback when the fps of the video is equal the refresh rate of the display. Please provide more info about the problem you experience to allow assessment.
Quote from: fjbg on February 17, 2021, 05:46:32 AMdisplay : 3840 * 2160 (32 bits), 30 hz (just checking that for you, i now wonder why this isn't in 60 hz, gonna try that now)
Quote from: eumagga0x2a on February 17, 2021, 08:55:44 AMYou may need to connect the display via DisplayPort or a high speed HDMI cable for 60 fps refresh rate. If the videos you load in Avidemux have higher fps than the refresh rate of the display, the playback indeed turns jerky and lags.
Quote from: eumagga0x2a on February 17, 2021, 08:55:44 AMApart from that: What display output in Avidemux do you use? On Windows, it should be the one called "DXVA2" (actually, DirectX) whenever possible. I don't mention the unaccelerated "Qt" one, that one is just a safe fallback for the case that all other options fail.
Quote from: eumagga0x2a on February 17, 2021, 08:55:44 AMIf you don't need OpenGL display output (you really don't, except of when "DXVA2" one crashes) or OpenGL-based video filters, you should disable OpenGL on Windows. Crashes indicate a buggy graphics drivers, however.