Quote from: eumagga0x2a on October 29, 2024, 11:03:55 AMThank you, might be fixed now, but can't tell for sure without a sample. Please try a future nightly build.I tried to post the video Mega link, but I got: CleanTalk: *** Forbidden. HTTP links blacklisted. Please enable JavaScript. Anti-Spam by CleanTalk. ***
Quote from: eumagga0x2a on October 26, 2024, 05:20:57 AMDoes this happen with the latest available 2.8.2 nightly build?
If it does, please provide a sample.
If the file size is too large for the file to be provided as a sample by the usual tools as WeTransfer, Mega, Dropbox or Google Drive, please at least attach MediaInfo textual analysis for the file in question to your reply (don't try to paste it into the body of the post, CleanTalk is allergic against MediaInfo for whatever reason).Quote from: johnr283 on October 24, 2024, 01:21:48 AMIf I change the output to AAC, the video won't play correctly.
But it will if you disable the DTS audio track, right?
Quote from: coré on October 26, 2024, 07:04:47 PMI want to convert a 29.970 interlaced video to 23.976 fps (which will therefore be deinterlaced) but when I try to modify the framerate in Avidemux, it also modifies the duration of the video.
Quote from: coré on October 26, 2024, 07:04:47 PMin Avisynth, for the videos I want to process, I apply: tdeint mode 2 but this does not seem to exist in Avidemux.
What would be closest to it?
Quote from: question on October 26, 2024, 05:48:52 PMWhy does Avidemux say the optimal is two pass average + target bitrate of 0 then?
Quote from: question on October 26, 2024, 05:48:52 PMI dont understand why converting mp4 to webm results in an increased file size...
Quote from: eumagga0x2a on October 26, 2024, 02:21:52 PMQuote from: sark on October 26, 2024, 01:32:49 PMChanging to Constant Bitrate should reduce output size (significantly in some cases).Please don't, constant bitrate is almost always a poor choice – just the default configuration of the libvpx VP9 encoder plugin is even worse.
Please use the 2-pass average bitrate option with an actually reasonable, non-zero bitrate. If I am not mistaken, two-pass is unfortunately the only way to make libvpx insert keyframes at scene changes rather than stupidly following the specified GOP length.
If keyframes placing is not important for you, use constant quantizer mode. Increasing "Speed" beyond "4" allows for much faster operation at the cost of massively worse compression.
Quote from: sark on October 26, 2024, 01:32:49 PMChanging to Constant Bitrate should reduce output size (significantly in some cases).Please don't, constant bitrate is almost always a poor choice – just the default configuration of the libvpx VP9 encoder plugin is even worse.
Quote from: question on October 26, 2024, 11:59:52 AMNow my problem is that when i convert a mp4 file to webm using avidemux, for some reason the file size is actually larger?