UI exception (Win11Pro, non-fatal, recoverable)

Bugs / Feature Requests Bugs
1

MCEBuddy Version: 2.6.5 28 Feb 2025
Operating System: Win11Pro 24H2 10.0.26100.3476
Summary of the problem:

************** Exception Text **************
System.ArgumentException: Must specify valid information for parsing in the string.
   at System.Enum.EnumResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument)
   at System.Enum.TryParseEnum(Type enumType, String value, Boolean ignoreCase, EnumResult& parseResult)
   at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase)
   at MCEBuddy.GUI.ConversionTaskExpertSettingsForm.WriteSettings(ConversionJobOptions cjo)
   at MCEBuddy.GUI.ConversionTaskExpertSettingsForm.WriteAndValidateSettings()
   at MCEBuddy.GUI.ConversionTaskForm.oKcmd_Click(Object sender, EventArgs e)
  ...

MCEBuddy 2.6.5-28Feb2025 UI Bug 20250323.txt (9.0 KB)
Steps to replicate the bug:

  1. Open MCEBuddy Settings
  2. Expand General Settings
  3. Open/Change a Conversion Task
  4. Expand Advanced Settings
  5. Open Expert Settings
  6. Browse/Select a custom Comskip.INI file
  7. CANCEL selecting a custom Comskip INI file
  8. Click “OK” button (even though nothing was changed)
  9. Error dialog should appear

It is possible to continue. Select “Cancel” instead of “OK”. Unwind UI normally.
Full error message attached.

2

Hmm, I’m not able to replicate the problem with your steps above. To clarify you click on the ... to select the custom comskip ini and then click “Cancel” instead of “Open”?

Could you capture a video of the steps to replicate it? I suspect it may be some other settings which is throwing it off.

EDIT: If you can please attach your mcebuddy.conf file also so I can replicate the exact setup.

3

I think I just got it to trigger in fewer steps. I’ll try that, see if I can record it, and attach my conf file.
MCEBuddy UI bug-2025-03-23.mkv (608.9 KB)
mcebuddy.conf (23.2 KB)

4

Thanks the conf file was helpful. The issue wasn’t with comskip but rather with the GPU selection. I think you may have copies the mcebuddy.conf from a different computer or possibly changed your hardware setup. The conf file was pointing to using NVidia as the preferred GPU where as the system doesn’t have a nvidia so when writing the settings back it would cause an exception. This has been fixed in the next build so if there’s a missing GPU selection it will default back to Any.

2 Likes
5

Yes, the conf was copied over after install to a rebuild of my media server that doesn’t have a nVidia GPU.

Weird how that affected the GUI, though. Thanks for looking, finding, and resolving!

I’ll update my conf file now that you’ve noted the root cause. Thanks again!

You and the MCEBuddy team/family are the best!

1 Like