Save Selection As JPEG - Quality Options?

[eumagga0x2a]

Another thing I wondered about, is whether that script needs a certain version of python to work?

It doesn't rely on any (external) Python interpreter at all. The minimal subset of Python Avidemux uses is contained in the libADM_script_tinyPy.dll plugin.

[eumagga0x2a]

I should probably add that I use ZIP-packaged Avidemux builds for testing purposes on Windows (there are no other reasons for me to boot it in the first place), unless I specifically plan to test the installer. I extract it into an empty directory and run the graphical executable simply by clicking on it in the Windows Explorer window.

Usually, there are quite a few different builds in different locations, but they are never extracted over another build and also never run concurrently.

[Dave9]

SUCCESS!

I have done a few things.  I updated python to 3.13.2, which didn't seem to make a difference, unless I needed to reboot first but didn't before testing.  I see you posted about that and no surprise that it didn't make a difference.

Next I deleted the contents of the Avidemux installation folder.  I had thought that installing a new version over-top of the old was acceptable since it sees the old version, wants to install to the same folder it's in, and offers to keep the settings, but apparently not.

After clearing out the installation folder, reinstalled same version 2.8.2 r241212 again to that folder, standard install, and it has no problem with No Disk message, none of the other errors I posted about, ("so far" no errors at all), and it does use the script properly now to sequentially name and save PNG for all the frames instead of only the first 37 frames.

Thank you for the guidance!

Sorry that my replies were not more prompt.  I have this topic showing "Receive Emails and Alerts", and double checked that my profile has a valid gmail account listed, but I have not been receiving any email updates for this topic.  Gmail doesn't show them marked/blocked as spam either.

[Dave9]

After I started getting tired of Avidemux making the index files with the latest version, I tried the same thing with the prior version, instaling it to a cleaned out folder instead of over-top of an existing installation, like I'd done with the newest nightly version.

I cleared the folder out, installed Avidemux_2.8.2 VC++ 64bits 240601 to that empty folder, and ran it as the only instance of Avidemux.  Doing so, it still won't use that sequential naming script to save more than 37 PNG images before it stops, while the latest nightly build still works to save all that are selected, so for the time being I'll use the older version till I need to save sequential PNG so I don't have all the index files to clean up, then run the newer one for saving sequential PNG images with the script.

[eumagga0x2a]

installed Avidemux_2.8.2 VC++ 64bits 240601

I repeat myself, but the last known good nightly is a cross-compiled r241212 at the moment. It is pointless to take something else.

I started getting tired of Avidemux making the index files with the latest version

Create an environment variable ADM_NOINDEX_MP4 with value 1 for MP4 files (ADM_NOINDEX_MKV for Matroska files respectively). A pull request implementing indexing preferences is waiting for being merged once the dust settles and we get regular, working nightly builds again.

[FeRD_NYC]

You know, not for nothing, but if the concern with adding a PNG-export feature is wanting to avoid growing avidemux's already-considerable number of menu options, there is a way to avoid that: The "Save as Image" submenu's painfully out-of-date "Save as BMP" option could be replaced with a "Save selection as PNG" feature, and avidemux would have exactly the same number of menu options it had before. 

[Dave9]

installed Avidemux_2.8.2 VC++ 64bits 240601

I repeat myself, but the last known good nightly is a cross-compiled r241212 at the moment. It is pointless to take something else.

I don't like to update Avidemux too often because something breaks, or depends on  some certain video driver version, or introduces something I have to take effort to stop like the index files.  I am using ver 2.8.2 and don't want headaches switching.  I'll try another version eventually and probably stay with 2.8.2 because there seems to be very little regard for keeping compatibility.

I've been off on a rant while drinking so take this post however you want to, but no other apps I use, have this much BS maintenance involved, the rest of my apps I just use without ever having to post in a forum about them.


If it needs a newer version of (anything), this is a bad move in my opinion.  Keep it backwards compatible.  Don't be a snob about updating everything.  I won't do that, nor do most users want to unless they drank the kool-aid.

I have never encountered this kind of  skittish force update/change behavior before.  Just stop it, cut it out!  Stop introducing incompatibilities.  Excuses are excuses.  I understand the reasons and suggest that it's foolish.  The worst thing is to limit the audience in order to be lazy.

Do whatever you want, and I will not update regularly because of the arrogance of not respecting keeping legacy systems running.

Don't break things!

I know my post is a big vague, but I contrast this with the many many other apps I use, which don't have this problem.  It seems very much like the developers are snobs that want to artificially ruin compatibility, and I accept that, it is their call to make, and also why they will leave a lot of people not wanting to bother trying every new version of the app.