Running Win7
I can't use "Open with..." to use latest version of Avidemux.
I have the most recent version 2.7 saved in "C:\Program Files\Avidemux 2.7 - 64 bits"
But ever since installing the first iteration of v.2.7, if I try to use "Open with..." to open a video clip, the version that appears is 2.6.1. No matter what I try, I can't make v2.7 appear in the list of "Open with..." programs on my computer.
So I have to open v2.7, then find the clip and open it. This is time-consuming and inefficient.
Is there a fix for this? (I hesitate to delete previous versions since I don't want to delete any files that might be needed to run later versions. And some previous versions have convenient features that have disappeared in later versions.)
That is OS related:
https://support.microsoft.com/en-us/help/18539/windows-7-change-default-programs (http://changewhichprogramswindows7usesbydefault)
Thanks but I am aware of the procedure described in the link you provided. It does not make any difference. I can assign any other program I want (older versions of Avidemux, etc.) but v2.7 does not appear.
I'm not on windows, is there not a way where you can browse to avidemux 2.7, in these procedures.
Yes, there is, but for whatever reason the program refuses to open v2.7 from it.
See attached images.
Even more strange, now that I have v2.7 180123, a previous version of v2.7 now appears in the list of options (image attached). It's as if the latest iteration won't appear but previous ones will.
Image 1: selected v2.7 from browse list in Program files.
Image 2: v.2.6 appears not v.2.7.
Image 3: Options list now includes older build of v.2.7
If you installed these V2.6 and V2.7, then probably the application data/configuration settings are getting mixed up.
Should not run these together on the same PC (V2.5 plus V2.6orV2.7 is okay).
Else run all these avidemuxes as a portable in their own private folder (not in the special "program files" folder)
Thanks for the information! I didn't realize that would be a problem.
I've installed today the last avidemux 2.7 version, unisstalled 2.6 version but v2.7 doesn't appear in the list of "Open with..." programs on my computer.
Of course I've tried to choose the program from the list with right click/open with/default programs but after choosen avidemux it is ignored!!
https://www.technorms.com/26760/add-remove-programs-open-menu-registry
What happens when you replace "avidemux.exe" with
"avidemux.exe --load"
in the registry key?
The background: Avidemux requires --load as option between the exe name and the file name of the video.
More specific: https://superuser.com/questions/136133/how-do-i-set-advanced-file-associations-in-windows-7
Sorry for the delay - I've been busy with other things.
I followed the instructions on the link you provided.
The only program listed under .7z/Open with List was firefox - which of course is not an "Open with" option for image or video files.
I did as suggested. It did not help.
Quote from: eumagga0x2a on July 01, 2018, 10:52:06 AM
The background: Avidemux requires --load as option between the exe name and the file name of the video.
Is this new? No previous version (before 2.7) required it.
This was plainly my error. The first argument passed to application is interpreted as video to load even without the --load option. "Open with..." with Avidemux works fine for me on Windows 10 once I fought all the way for the right to point to the exact location of avidemux.exe.
I'll recheck on Windows 7 later.
Same for Windows 7, works fine once I've pointed to avidemux.exe.
Here is explanation and solution:
Find the registry key for the application you wish to associate, lets say for Notepad++.exe in \HKEY_CLASSES_ROOT\Applications\notepad++.exe \shell\open\command\
Check if the .exe path is right. If not, then change the path to the correct one.
After doing this, you can now go to the file you wish to associate and use the standard way Open With and choose the program you wish to open.
Explanation:
This issue happens when Windows gets confused about the filepath for a program, as file associations are handled using only the base executable name of a program (source).
This bug can be caused by:
Running multiple versions of a program (i.e. Notepad++ and Notepad++ Portable)
Moving programs to different folders.
Changing drive letters