XRECODE

The one that shipped with the app but I've tried several other versions too. No difference at all. I really suspect xrecode is not properly working in Windows 11. Yesterday I've tried it again in WINDOWS 10 without any problems. Did you reproduce the conversion yourself in Windows 11? I also will reproduce it in a clean virtual win11 machine. If the problem occurs again I can only come to the conclusion that the current xrecode version does work properly in Windows 11.

I'm developing the app on Windows 11, but could not reproduce the issue even using your settings
You could try to reset program's settings like this - https://imgur.com/OwfF5DD
Check if it works after that.
If it does, put your original settings back one by one to find out which one is causing the crash.

admin wrote: Wed Apr 02, 2025 8:11 am I'm developing the app on Windows 11, but could not reproduce the issue even using your settings
You could try to reset program's settings like this - https://imgur.com/OwfF5DD
Check if it works after that.
If it does, put your original settings back one by one to find out which one is causing the crash.

Wow. In that case my current system can only be the culprit!
I will try your suggestion and report back to you. Thank you.

It most likely is some option, not the system

Well..it does indeed have something to do with my current windows 11 because in the virtual windows 11 machine everything works normally. However, I really wouldn't know what could be wrong. Reset everything and also reinstalled. Nothing helps. Lame.exe doesn't work well on my current system.

How exactly the crash looks?

admin wrote: Wed Apr 02, 2025 10:11 am How exactly the crash looks?

Stops suddenly. No activity anymore. Have to terminate process with the task manager.

OK, I see. Could it be related to the folder name of the files (e.g. some special character)? I noticed you have "Create files in the source folder" option enabled. Could you try to convert to a specified folder instead? This behavior would explain why lame_enc.dll option is working fine, because it's not affected by any of this.

admin wrote: Wed Apr 02, 2025 10:25 am OK, I see. Could it be related to the folder name of the files (e.g. some special character)? I noticed you have "Create files in the source folder" option enabled. Could you try to convert to a specified folder instead? This behavior would explain why lame_enc.dll option is working fine, because it's not affected by any of this.

Already did this several times. No success...

Is there a possibility to use the lame_enc.dll with extreme quality settings?