Wish there was a way to play audible prompts or audio files when events occur

Started by Philo, August 07, 2022, 05:56:40 PM

Previous topic - Next topic

Philo

I waste more time while using Avidemux for two reasons.  First, since I am often converting .ts files, for some reason when I load a .ts file Avidfemux takes forever because it has to build an .idx file.  I don't understand why Avidemux has to do this for .ts files when it doesn't for other file types, but okay.  So a box pops up telling me that it will take anywhere from two to ten minutes to load the file, depending on the length of the original file and how slow the drive is that the file is coming off of.  Well, nobody wants to sit and stare at a  screen that long, so I tab away and work on something else while it is loaded.

An hour or two later, it dawns on me that I never went back and did my edits on the file and started it encoding.  This is not just a once in a blue moon thing, it happens to me all the time.  And it would REALLY, REALLY help if there were some way to play an audible prompt of any kind (even if just a .wav file or something) when the file is loaded.  Or to be able to launch a shell script which could them play a sound or pop up a box on the screen or do something to alert me that the file is loaded.

The other obvious time I wish there were a way to play a sound is when the file has finished encoding.  This always takes a varying amount of time and of course the time to completion estimate is all over the place depending on the complexity of whatever it's encoding at that moment.  So it would be great if Avidemux could play a sound or run a shell script when the file has finished encoding.

eumagga0x2a

Quote from: Philo on August 07, 2022, 05:56:40 PMFirst, since I am often converting .ts files, for some reason when I load a .ts file Avidfemux takes forever because it has to build an .idx file.  I don't understand why Avidemux has to do this for .ts files when it doesn't for other file types, but okay.

Creating an index of a MPEG transport stream file is indeed a time-consuming procedure as there is nothing comparable with structures of mp4 or Matroska files holding positions and timestamps of all interesting parts in one place. The only way to index a MPEG-TS file is to parse it bit for bit all the way through. This is the reason why MPEG-TS and MPEG-PS demuxers in Avidemux write the collected info to a file so that the next time this stream is loaded, Avidemux doesn't have to start indexing it from scratch.

Quote from: Philo on August 07, 2022, 05:56:40 PMSo a box pops up telling me that it will take anywhere from two to ten minutes to load the file, depending on the length of the original file and how slow the drive is that the file is coming off of.  Well, nobody wants to sit and stare at a  screen that long, so I tab away and work on something else while it is loaded.

An hour or two later, it dawns on me that I never went back and did my edits on the file and started it encoding.

Honestly, I believe this is one of few things about macOS which are really good, compared to this on other platforms.

In the substance, to play a sound upon an event like completion of indexing or encoding, it would be necessary to integrate Qt Multimedia framework into Avidemux which is rather big. Unless we find more use cases for it, the benefits to costs ratio seems to be quite low.

Contrary to that, displaying a notification via QSystemTrayIcon doesn't involve inflating the size of the application. Would such a solution, if it gets implemented during future development, match your needs?