Known problems or limitations
Error: JSplitter v3.7.6 ({86BB0E71-DE6C-4480-BFA5-673B29F223E1}: XXX)
Out of memory: 1332/1073741824 bytes
On some setups after loading a script or while running, specially with large libraries (> 100K tracks), it may be possible that the JS host crashes with an Out of Memory error (like the one above). Unfortunately that's a components limitation, in particular in x86 setups, since it can not have access to the required amount of RAM for processing. There are multiple possibilities.
- Whenever possible, reduce the number of tracks you are applying a tool at. For ex. try not to put your entire library on a single playlist.
- Music Map related features are specially memory intensive. Avoid it if the following tips are not enough to support your RAM usage.
- Use x64 foobar2000 along x64 components. Check if your preferred JS host provides a x64 version.
- Setting a higher RAM limit at the JS host. Input the highest number you can at the following setting (both SMP and JSplitter offer similar options):
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.
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 script updates. Obviously this is only a workaround and a proper fix is expected on posterior SMP releases.
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.
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.
Reporting wrong values at some instances. This usually happens while reading playlist files or importing tracks lists, with track names or artists using exotic chars (ä,â, ...) getting corrupted. Multiple code checks have been added to minimize these situations in any case.
While scanning or tagging, these external tools may fail in some cases (please don't report it):
- Tracks too short (< 10 secs).
- Sub-songs, like those present in an ISO file, since there is not a physical file for every track. You can bypass this limitation converting the tracks into individual files, scanning them and finally copying back the tags. This is only required for ChromaPrint (%ACOUSTID_FINGERPRINT_RAW%) and EBUR 128 (%LRA%).
- Files being blocked by another process (randomly). In this case just re-scan such files.
- CMD tools may fail on Unix systems when using Wine prefixes. In particular, for ChromaPrint and ffmpeg, since the binaries are run via command line using bat files, OS Architecture must be matched (x64, ...). Some measures have been taken to account for it automatically, since the 64 bit binaries are preferred for performance. No further support will be given (although it's possible to replace the 64 bit binaries with 32 bits versions).
- Note these tools are not developed by me -I only coded the wrapper- and they may behave erratically with specific files or hardware configurations. In such cases I have nothing to do, please report to their corresponding developers.