Avidemux Forum

Quote from: test32421 on October 23, 2024, 11:43:58 AMI don't have an account with any of those services, but I'll look into it.

No account (and no email address despite the website trying to suggest otherwise!) needed for WeTransfer for files less than 2 GB in size.

Quote from: test32421 on October 23, 2024, 11:43:58 AMAnd by saving to a container, I mean simply importing a .vob file to avidemux and doing nothing else other than select a container format and save it.

Again, "save it" will either copy the video stream or re-encode it. The only bit of information this statement provides is that the segment layout was at its default state (the entire video selected).

Regarding VOB files from commercial video DVDs, I am not sure that an assumption that the layout of actual MPEG-PS streams matches file boundaries is valid. This may be fully intentional. In this case, loading VOB files in Avidemux may not produce expected results.

Never had this in previous 2.7.6.
1st pass ok, 2nd pass freezes when there is a small glitch in the recording. It's reproductible, and it hangs always in the same part of the recording.
No error messages, only a non responding encoding window.
I don't know if it can be useful, I'm joining the WER file captured by Windows.
I have tried to remove the corrupted part by cutting it in Avidemux, but still the same.
Any advice ? Something I can do to give more diagnosis information, debugging logs, etc.?

I don't have an account with any of those services, but I'll look into it. And by saving to a container, I mean simply importing a .vob file to avidemux and doing nothing else other than select a container format and save it. But when I instead cut the beginning out, for instance, the "new" beginning of the output file does not seem to exhibit the issue.

And I'm aware of the issues with B-frames, but that is said mainly to occur with cutting operations from what I understand. If I just import a whole .vob file and save it, using copy mode, I don't understand why that would result in a changed framerate, but apparently it does.

Quote from: test32421 on October 22, 2024, 03:10:56 AMI have noticed that with MPEG-2 .vob 720x480 29.970030 FPS files, simply saving them to a container results in a almost 1 second video stutter at the beginning.

Please provide a sample (just a 50, max. 100 MB large head portion of the file should be enough) via WeTransfer, Mega, Dropbox or Google Drive. Not sure what you mean by "simply saving them to a container" vs cutting. What matters, it is copy mode vs re-encoding.

FPS deviations originate mostly from dropped undecodable early B-frames in open-GOP streams.

Quote from: B-boy_Style on October 21, 2024, 01:47:57 PMHere we go:

I am sorry for having assumed this to be self-explanatory, but I need admlog.txt from the session ending in the assert failure (from user's POV: a crash) from the failure to initialize OPUS decoder. Once Avidemux is started again, the log with relevant information gets overwritten and therefore the new log is useless.

Please launch Avidemux, try to load the MKV file in question, reproduce the crash, don't restart Avidemux yet, attach admlog.txt.

Thank you.

Quote from: B-boy_Style on October 21, 2024, 06:58:52 PMthe video file despite it's playing without a problem in MPC-HC is probably corrupted because a lot of converters gave an error why trying to proceed it.

We'll see. Could you please attach (not paste into the post body!) the textual analysis of the file by MediaInfo to your reply? Cannot use dumps, sorry for that.

Using the current 2.8.2 nightly in copy mode, I have noticed that with MPEG-2 .vob 720x480 29.970030 FPS files, simply saving them to a container results in a almost 1 second video stutter at the beginning. I first thought this happens when merging together several .vob files, but it happens even on just one. I don't know how accurate the FPS display in VLC is but with .mkv, I get 29.970628 FPS, with .mp4 29.967584, with .avi 29.970000 (doesn't support AR forcing by the way, I know the format is considerered obsolete but still).

However, if I instead cut the file, there is no visible stutter at the beginning, and if I select .mp4 output, VLC even shows the same FPS as with the input file. It seems to me this is some kind of bug in avidemux or a defect in the decoder (shown as Lavcodec). Maybe it only accepts 29.97 FPS and drops frames to get there? At any rate, playing the .vob file in VLC does not show this stutter at the beginning.

Btw, the video file despite it's playing without a problem in MPC-HC is probably corrupted because a lot of converters gave an error why trying to proceed it.

But I still decided to report it here just in case. I have some dmp files if needed.

Here is the link for the *.dmp files:
https://transfer.pcloud.com/download.html?code=5Zv7py5Z84eRDpaFlOBZGKVJZ5ilQrlsRhebWnd20PG3P1BXI97H7

Here we go:

Btw, I am currently with GTX 1660 as my main RX 3070ti is on diagnostics (if that does matter).

You cannot view this attachment.

Could you please post the error ("Cannot init libopus" etc.) from admlog.txt (%localappdata%\avidemux\admlog.txt) at the line preceding the one with assert failure?

Thank you.

Hello,

I am using the latest beta build 2.8.2.240908 but when I am trying to import a video file to convert it to mp4 I am getting this error on startup:





Can you fix is in the next release please?

Thanks and keep up the good work!