Reply to thread

Message

<blockquote data-quote="Lehmden" data-source="post: 1307627" data-attributes="member: 109222">Hi.To start off, I’ve fixed two bugs today. One was specific to Linux (support for AppImage files was broken, but that’s now resolved), while the other was a genuine bug affecting all platforms: the application would crash if the generation of thumbnails—triggered when replacing a cover or preview image—was cancelled. This has also been fixed, and the relevant files have been synced to GitHub.Following that, I began work on the music-related component. The actual re-encoding engine is not the same as the one used for videos, as the requirements are too distinct. However, the video encoding engine served as a very useful foundation, saving me from having to start completely from scratch. In fact, it’s already functional and can even be triggered from within the GUI.[ATTACH=full]219725[/ATTACH]During processing, the familiar progress indicator appears once again:[ATTACH=full]219724[/ATTACH]The engine also includes a &quot;hi-res safeguard&quot; to prevent high-end audio files from being accidentally converted into &quot;lousy&quot; .mp3s—unless, of course, that is explicitly desired.The next step is the audio metadata scraper, which will be significantly more complex to develop than the recoding engine.</blockquote>

[QUOTE="Lehmden, post: 1307627, member: 109222"] Hi. To start off, I’ve fixed two bugs today. One was specific to Linux (support for AppImage files was broken, but that’s now resolved), while the other was a genuine bug affecting all platforms: the application would crash if the generation of thumbnails—triggered when replacing a cover or preview image—was cancelled. This has also been fixed, and the relevant files have been synced to GitHub. Following that, I began work on the music-related component. The actual re-encoding engine is not the same as the one used for videos, as the requirements are too distinct. However, the video encoding engine served as a very useful foundation, saving me from having to start completely from scratch. In fact, it’s already functional and can even be triggered from within the GUI. [ATTACH type="full"]219725[/ATTACH] During processing, the familiar progress indicator appears once again: [ATTACH type="full"]219724[/ATTACH] The engine also includes a "hi-res safeguard" to prevent high-end audio files from being accidentally converted into "lousy" .mp3s—unless, of course, that is explicitly desired. The next step is the audio metadata scraper, which will be significantly more complex to develop than the recoding engine. [/QUOTE]

Verification