FAQ

Frequently Asked Questions

Is DarkOneJSP3 an official DarkOne release?

No. It is an unofficial community continuation and does not imply endorsement by the original theme, component or sample authors.

Which foobar2000 architecture is required?

DarkOneJSP3 targets foobar2000 v2 x64 with Columns UI. A live v0.9.19 installation was confirmed with foobar2000 2.25.10 x64 portable, JScript Panel 3.8.5 and JSplitter 4.1.12.

Should I import the included FCL?

The FCL is optional. The authoritative setup reference is the Layout and Panel Map. Manual layout construction is recommended because it creates component instances for the local installation and makes every title and script assignment visible.

Does an upgrade require a factory reset?

Normally, no. Persistent JScript Panel and JSplitter properties are retained. Use a factory reset only when intentionally restoring defaults or when troubleshooting a configuration-specific issue.

Do I need to re-import the JScript Panel entries after upgrading?

Not normally. Older saved entries are supported through compatibility helpers and reset adapters. Re-importing the supplied entries is useful when you want the newest entry metadata and import structure.

Can the enhanced samples be used by other themes?

Yes. From v0.9.17 onward, the enhanced sample tree is standalone and no longer requires the DarkOneJSP3 project directory. See Enhanced Sample Library.

Will the sample library overwrite files used by another theme?

It may replace matching files in foo_jscript_panel3\samples and helpers.txt. Back them up first, especially when another theme includes locally modified versions.

Which Queue Viewer should I use?

The native Queue Viewer component is recommended because it can add, remove, reorder and clear queue entries. The scripted fallback provides DarkOne styling, selection, navigation and source-item commands, but JScript Panel 3 does not expose the mutation APIs needed for complete queue editing.

Why does Album Notes report an AllMusic HTTP 403?

AllMusic may reject scripted requests even when the page works in a normal browser. Album Notes can attempt a MusicBrainz relationship lookup as an AllMusic URL resolver. Some albums still require Fetch from manual AllMusic URL... or another enabled source.

Why does Album Notes say MusicBrainz could not match an album?

The automatic search could not confidently identify the release. Supply a MusicBrainz release-group or release MBID, correct the tags, forget the saved identity and resolve again, or use a manual AllMusic URL where appropriate.

Why are there many “Playlist loaded” console lines?

foobar2000 reports each restored playlist during startup. These lines are informational unless accompanied by an actual error or failed script initialisation.

Why does the theme briefly show a native grey or black surface at startup?

With Startup set to Off, native Columns UI or JSplitter backing surfaces may briefly appear before every child completes its first paint. Use Black reveal when this is noticeable. Optional reveal modes intentionally coordinate nested controller readiness.

Why does JS Playlist use more CPU at 8 ms?

An 8 ms refresh interval targets very smooth animation but performs more frequent work. Select 10, 12 or 16 ms from the playlist settings when lower CPU usage is more important.

Why can’t I find a setting mentioned in the guide?

Right-click location matters. Playlist rows, empty panel areas, scrollbars, the volume knob, the centre display and the InfoStack tab strip expose different menus. See the Configuration Guide.

What should I include in a bug report?

Include component versions, the exact panel or script, reproduction steps, console output, screenshots when useful, and confirmation that the issue occurs on the current stable release. Run the validator where possible.

How do I roll back?

Close foobar2000 and restore the backed-up DarkOneJSP3 folder and JScript Panel sample files. Re-import the backed-up Columns UI layout only when the layout itself changed.