Skip to content

Known problems or limitations

regorxxx edited this page Sep 29, 2025 · 5 revisions

Crash at startup when trying to load the script on a panel on portable installs

After loading a script into a panel, the panel may crash if foobar does not has the required [full] access to the folder where the scripts reside. This may happen in portable installations since Win 11 restrict permissions to folders outside 'Program Files' or 'Users'. Ask at foobar forums for support.

Crash -unknown reason- at startup when trying to load the script on a panel

The error will warn about script files not being found, although they are in place. This is due to incorrect relative path handling on some systems. In such case, take a look at the ’_switchPaths.zip’, decompress it and follow its instructions. Scripts will be automatically edited to use absolute paths at script loading, thus fixing the problem. The cmd file (.bat) will have to be rerun on future playlist manager updates. Obviously this is only a workaround and a proper fix is expected on posterior SMP releases.

Warning popup about a script being unresponsive

This is not an script error but an SMP feature to avoid scripts blocking the entire software (please don't report it). It's common for processor intensive tasks which require more time to finish (just press continue). Clicking 'stop the script' will crash the panel.

Warning

Since some operations may need more time than usual, to avoid seeing the popup, it’s recommended to change the timer at configuration to the highest value allowed. NOTE: JSplitter allows to set it to 0 to disable it.

Figure 127: Slow script warning at advanced configuration.

Clone this wiki locally