AVIMux GUI Changelog

What's new in AVIMux GUI 1.17.8

Jan 26, 2013
  • New:
  • The CTextFile class is redone. Text files can now be handled in UTF-16 big and little endian (with BOM only), UTF 8 (with BOM only) and the local charset of your windows installation
  • Added highlighting for streams that are default and for streams that AVI-Mux GUI cannot put into AVI files (this visual feature can be disabled)
  • When creating XML files, now STL is used
  • Matroska tags can be used to create several titles for one matroska stream. Note that this is, as far as I know, not yet supported by players or filters.
  • The BitStream class is redone. Reading AAC audio is now faster.
  • The widht and height of the settings window is increased if the right-bottom-most button is cropped.
  • There is now a setting to enable, disable or leave unchanged the cleartype font setting
  • Fixed bugs:
  • When opening Matroska files containing Vorbis audio streams, the vorbis audio streams' titles were not imported
  • A crash occurred when opening a matroska file containing Tags with no target
  • The windows size should not be restored correctly and on the correct screen when restarting AVI-Mux GUI
  • The delay setting was printed in the wrong place for A_MS/ACM audio tracks in matroska files
  • DTS streams with frames of 2012 bytes got a wrong duration because the PCMSampleCount header field was not used. This made the audio go out of sync
  • When the size estimation of a Vorbis audio track failed, a crash occurred
  • AC3 and DTS: The LFE channel was ignored. This caused incorrect channel information to be written in headers. This did not affect replay on most players, but I got a report that a Nero AVI file parser interpreted this difference between header and real stream data as a broken file.
  • AC3: Due to some rounding that (erroneously) occurred when reading AC3 audio files with 44.1 kHz, such streams were muxed incorrectly.
  • Nowadays, there is no long double anymore in Visual Studio. Due to this, when trying to write 80 bit floats into matroska file, a 64 bit float was written instead and padded with 2 zero bytes. This is fixed. IMPORTANT: 80 bit floats are no longer allowed in the matroska specification. 80 bit floats can only be selected when matroska v1/v2 enforcement is disabled.
  • the file name in the START command in scripts was converted to UTF-8, then it was interpreted as 8859-1 and again converted to UTF-8, which led to disrupted file names
  • a crash occurred when dropping an XML chapter file onto an edition in the chapter editor

New in AVIMux GUI 1.17.7 (Aug 10, 2006)

  • 1.17.6 didn't allow raw video stream extraction due to a missing change after a modification in the GUI
  • reading multisegment matroska files was broken in 1.17.6
  • Muxing an AVI file had higher CPU load when showing the progress view
  • There was a problem in the SSA parser leading to a crash when some attributes simply didn't exist
  • A problem introduced with 1.17.6 causes a crash when opening WAV files. This was introduced when adding file highlighting in the source file list
  • Video stream names were ignored for AVI files
  • MP3 files with garbage at the beginning were never detected as CBR
  • Joining NanDub-made AVI files with b0rky AC3 streams didn't work

New in AVIMux GUI 1.17.6 (May 30, 2006)

  • new
  • separate output thread when muxing
  • highlighting for files in the source file list
  • use PgUp/PgDn buttons to move files and streams
  • hex viewer for EBML/RIFF tree
  • can choose default file name
  • fixed bugs
  • video stream default flag was ignored and always set
  • after deleting files from the source file list, adding new files didn't work
  • after starting to mux from a matroska source, the ebml tree of that file could not be built anymore (critical section handling bug)
  • CLOSEAPP script command didn't work anymore in .5
  • when restarting a muxing job, OGG/Vorbis source files were not reinitialized
  • when using Vorbis audio sources, the large CodecPrivate wasn't taken into consideration when guessing the required header space. With auto cue size enabled, this could lead to a lockup when trying to finalize a matroska output file
  • fixed another bug in the read-ahead mechanism