Started by Norbi, April 06, 2021, 06:12:30 PM
Quote from: Norbi on April 06, 2021, 06:12:30 PMit seems Avsproxy(64) executable/function is broken in version 2.7.8 and unable to load audio with ffmpegsource and multithreading support is broken either.
Quote from: Norbi on April 06, 2021, 06:12:30 PMI just installed Avidemux_2.7.8VC++64bits.exe which doesnt have any avisynth avs proxy support it seems...
Quote from: eumagga0x2a on April 06, 2021, 06:46:30 PMVC++ builds seem to have even two AviSynth demuxers (interfaces between AviSynth and Avidemux), but, again, someone else needs to look into it, perform testing etc.
Assert failed :0 at line 411, file F:\jenkins\workspace\VS2019_no_import\avidemux_core\ADM_coreMuxer\src\ADM_coreMuxerFfmpeg.cppThe application has encountered a fatal problemThe current editing has saved and will be reloaded at next start
Quote from: eumagga0x2a on April 07, 2021, 05:06:47 AMThis assert failure means simply that the bit depth of uncompressed (L)PCM audio as passed to the muxer is unsupported. Currently only 16 and 24 bits per sample are supported, else you need to re-encode the audio stream.
Quote from: Norbi on April 08, 2021, 12:51:27 AMI tested on the original mpeg2 video too and replaced the original audio track with external mp2, and cut the movie resulted the same. Cutting doesn't affect the external audio track. It always start to play from the beginning.
Quote from: eumagga0x2a on April 08, 2021, 07:09:16 PMYes, indeed. External audio tracks are special as they are by nature independent from video tracks and thus don't have the segment handling logic which is available for internal audio tracks.There is a good reason not to have one: imagine, you delete a portion of video loaded in Avidemux first, add an external audio track second, then you undo the deletion. What should happen? Should the external audio track get a gap?Therefore, please always mux an external audio track into the video first, save the video, load the result, then perform any editing steps.