Clever FFmpeg GUI doesn't work

[BenBen21]

Hi, I have Windows 7 and i have downloaded the latest version of Clever FFmpeg GUI (and of FFmpeg), but during first launch, after I confirm "bin" folder, I have the following error:


[Attachment 83993 - Click to enlarge]

If needed I can post the error details.

[videoAI]

try posting here:
clever-FFmpeg-GUI-small-FFmpeg-UI-fully-portable-no-installation

address it to @ProWo

[BenBen21]

@videoAI thanks for the advice!

[GTHElectronics]

I have had the same problem for the past year. "clever Ffmpeg GUI" used to work perfectly now it just gives an exception and every time I open it we start all over again as it does not even save the directories it asks for! It used to find Ffmpeg itself but now you have to tell it where it is even though it is in the same "bin" directory. Completely useless now. Very sad but it has forced me to learn command line programming which is actually very easy once you get the hang of it! Please make it work again or stop pretending it is useful - it is useless and very annoying!

My error message is below but makes no sense at all - the software hangs up supposedly running a file analysis which never ends on the file selected:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: Cannot start process because a file name has not been provided.
at System.Diagnostics.Process.Start()
at clever_FFmpeg_GUI.Module1.Analyze_new_source(Form& msbx_cf)
at clever_FFmpeg_GUI.Form2.Show_Tracks()
at clever_FFmpeg_GUI.Form2.New_inputfile()
at clever_FFmpeg_GUI.Form2.Button2_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9290.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
clever FFmpeg GUI
Assembly Version: 1.0.0.0
Win32 Version: 3.3.7
CodeBase: file:///C:/Program%20Files/ffmpeg/bin/clever%20FFmpeg%20GUI.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9277.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9251.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9214.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
PortableSettingsProvider
Assembly Version: 0.2.5.0
Win32 Version: 0.2.5.0
CodeBase: file:///C:/Program%20Files/ffmpeg/bin/PortableSettingsProvider.DLL
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Web.Extensions
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Web.Extensions/v4.0_4.0.0.0__31bf3856ad364e35/System.Web.Extensions.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[ProWo]

What version? Delete it.
Retry with the latest beta: https://files.videohelp.com/u/292773/clever_ffmpeg_gui_newest_beta.zip

[GTHElectronics]

Hi, sorry about the delay but the Videohelp login failed. The beta is exactly the same. Incidentally I did put all 4 files in the ffmpeg/bin directory, not knowing whether the other files (mainly dll and config) were needed. Such a shame as the earlier versions worked perfectly and I kept up with new releases only to find last year that it didn't work any more so gave up and created batch files for ffmpeg direct for cutting and joining plus now encoding to MP2 and MP4 which pretty well covers all I need that MKTtoolnix can't do easily!

To be fair to you I would like this to end on a more positive note.

[ProWo]

Do the following:
The ffmpeg folder should remain separate, without files from my zip.
Extract the zip with all files into a separate folder, e.g. clever.
Then start the clever FFmpeg-GUI.exe and follow the instructions.

[GTHElectronics]

Hi, same error. Also puzzled why this has changed as you were quite specific about putting all in the bin directory before and surely it shouldn't matter where it is unless it was to find the ffmpeg files which now it won't? Similar error message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidOperationException: Cannot start process because a file name has not been provided.
at System.Diagnostics.Process.Start()
at clever_FFmpeg_GUI.Module1.Analyze_new_source(Form& msbx_cf)
at clever_FFmpeg_GUI.Form2.Show_Tracks()
at clever_FFmpeg_GUI.Form2.New_inputfile()
at clever_FFmpeg_GUI.Form2.Button2_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9290.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
clever FFmpeg GUI
Assembly Version: 1.0.0.0
Win32 Version: 3.3.7.06
CodeBase: file:///C:/Program%20Files/ffmpeg/clever/clever%20FFmpeg%20GUI.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9277.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9251.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9214.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
PortableSettingsProvider
Assembly Version: 0.2.5.0
Win32 Version: 0.2.5.0
CodeBase: file:///C:/Program%20Files/ffmpeg/clever/PortableSettingsProvider.DLL
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
System.Web.Extensions
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9282.0
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Web.Extensions/v4.0_4.0.0.0__31bf3856ad364e35/System.Web.Extensions.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[GTHElectronics]

It doesn't seem to find the file even though it is listed on your main page and it says it is scanning the file.

[GTHElectronics]

I have no tried selecting files from another directory, also avi files instead of mp4. Every time it is the same. Also tried drag and drop, same again.

[GTHElectronics]

Unless you have a bright idea I will just give up and accept I have plenty of other solutions. Pity is I did use this for file splitting etc but not for many months now.

[ProWo]

You'll have to give me a little more information.
1) which files are in your FFmpeg\bin folder?
2) which files are in the clever folder?
3) does the folder c:\users\xxx\AppData\clever ffmpeg GUI exist?
(replace xxx with your username in WIndows)?
If yes, delete it.

[GTHElectronics]

For anyone else who has a problem and wants to use ffmpeg for encoding etc look here: http://www.gthelectronics.com/ffmpeg.htm

[GTHElectronics]

files in ffmpeg/bin are the 3 expected plus my batch files but nothing else. The ffmpeg/clever directory has your 4 files in it.
Yes, there was an entry in c:\users\xxx\AppData\local\ but that was from 2021 so I have deleted this directory - maybe that was an old one though how it got there I don't know. Most entries are in roaming these days. Running clever GUI again does not seem to re-create any users entry.

[ProWo]

files in ffmpeg/bin are the 3 expected plus my batch files but nothing else. The ffmpeg/clever directory has your 4 files in it.
Yes, there was an entry in c:\users\xxx\AppData\local\ but that was from 2021 so I have deleted this directory - maybe that was an old one though how it got there I don't know. Most entries are in roaming these days. Running clever GUI again does not seem to re-create any users entry.

That's ok, because it's fully portable now and the configuration info stays in the portable.config file in the clever folder.
Does it start right now?

If not, delete the portable.config file and restart clever FFmpeg-GUI.exe.

[GTHElectronics]

Not at the moment and the file clever FFmpeg GUI.exe.config doesn't change but is still dated 28th Oct 2024. All files are unlocked (no R read only flag).
I will try a re-boot to clear any junk in the Registry.

[ProWo]

Not at the moment and the file clever FFmpeg GUI.exe.config doesn't change but is still dated 28th Oct 2024. All files are unlocked (no R read only flag).
I will try a re-boot to clear any junk in the Registry.

You should have this files in your clever folder:

[Attachment 85168 - Click to enlarge]
As I said, delete the portable.config file and leave the others.
Then restart clever FFmpeg GUI.exe

EDIT
The clever FFmpeg GUI.exe.config is used only for high DPI compliance.
The settings are all in the portable.config file.

[GTHElectronics]

Re-boot did nothing. Still the same fault and no change to the config file after entering the ffmpeg and local directories.
I must leave this now for tonight but will try again tomorrow and get back if I find anything.
Thank you for trying and the suggestions.

[GTHElectronics]

I don't have or get a portable.config file - my 4th file was the Readme one

[GTHElectronics]

Should I create a portable.config and if so what is in it?

[GTHElectronics]

I must stop now but will try again tomorrow though it looks pretty hopeless. I did make a portable.config with very little in it and that caused clever GUI to crash. So I removed it, it starts again now but each time it wants the 2 directories which is getting very boring as it never remembers them! Nothing else apart from the same can't find the file message even though it shows it listed.

[videoAI]

@ ProWo

Wouldn't not have been easier to name:
The main config file: Clever FFmpeg GUI.config
And the high DPI config file: High DPI.config or Display Resolution.config

Just my 2c ..

Not at the moment and the file clever FFmpeg GUI.exe.config doesn't change but is still dated 28th Oct 2024. All files are unlocked (no R read only flag).
I will try a re-boot to clear any junk in the Registry.

You should have this files in your clever folder:

[Attachment 85168 - Click to enlarge]
As I said, delete the portable.config file and leave the others.
Then restart clever FFmpeg GUI.exe

EDIT
The clever FFmpeg GUI.exe.config is used only for high DPI compliance.
The settings are all in the portable.config file.

[GTHElectronics]

Cracked it!! I realised/remembered after trying to edit my homemade portable.config that Windows is very fussy about changing things within its own folders, due to special permissions settings. So I just moved the whole clever folder to my own C:\xtras folder which is for a variety of portable files like Drivesort.exe, tsmuxer.exe, Vobedit.exe, PFE.exe etc etc. Now after an initial problem I get a portable.config file created and it seems to work.

So I suggest you either make clever ffmpeg GUI control the Windows permissions or suggest it is kept well away from any Windows directories!!

I will play again tomorrow but think it is now OK. It all went wrong at the time you stopped it being in the bin directory and finding the ffmpeg files itself without the need for a config file. I still think it was better as it was - users still have to know where their ffmpeg bin is so why not just put it all there anyway?

However now I know to keep it well away from Windows all seems OK. Please put this in your readme file.

[GTHElectronics]

The reason clever GUI locked up was because it was stuck trying to create portable.config. It never did until now. All to do with Windows permissions.

[ProWo]

It should already be clear that a program is installed where you have write permissions.

[GTHElectronics]

I agree that "should be clear" but first your original versions didn't write anything and that changed, secondly no other program I have ever installed has had this problem so no, it was not clear!

This whole issue would be easily solved, first you should explain that all 4 files should be placed together and then that this should not be in the Program Files or Windows directories. Then nobody will have a problem. I am clearly not the first, as I joined a thread where another person had found the same issue though I don't know if they ever solved it. Many others will just walk away and give up. Maybe for some odd reason my system has different permissions but placing it where all the older versions had worked was clearly no use any more. That was NOT made clear.

Thank you for indirectly solving this by letting me know about the missing config file which made me realise what had gone wrong. However if your software had reported a failure to write the file rather than saying it was analysing my video file I would have found out much earlier. But it just locked up instead of giving a useful message!

My only reason for using my "xtras" folder is to keep odd small applications somewhere I can easily find them. Nothing in there previously would fail to work elsewhere. Maybe because none of them have config files which they write to. Software which makes or changes files is normally installed so they use the registry. However, as I found out, placing them out of the way of Windows is the solution. This is easily made clear in the readme file which doesn't mention anything about installation currently which is very unusual. All you say is "No installation required. Fully portable.". No mention of the 4 files or where to put them!! So, NOT obvious at all. I could have fiddled with the permissions but I usually stay well clear of them! Maybe running your software as Administrator would have worked but moving the files solved it and of course Windows moved my shortcuts automatically!

So, job done for me and I can use your otherwise excellent software for what I did before: cutting, joining and separating audio and video etc. At least this problem made me learn about the command line use of ffmpeg which I needed so I could use the wealth of video filters available. Ffmpeg is certainly an extremely useful tool.

Now I can go back to praising your software, but when I do, it will be with a warning!!

[ProWo]

Will add a check for write permissions for the program folder.

[GTHElectronics]

Brilliant. Some more installation instructions will solve this problem for any others so they can use your excellent software.

[GTHElectronics]

I have for a long time now had your software listed on my pages as recommended!

[ProWo]

I have for a long time now had your software listed on my pages as recommended!

Thx