Analysis of non standard files

[regorxxx]

As far as I have seen here:
https://github.com/The-Wizardium/Audio-Wizard/blob/main/assets/docs/API.md#full-track-analysis-track-metadata-helper

Tracks are now analyzed by path (?) using a 'path\u001Fsubsong' format. But how does that work with:

• relative paths in foobar v2
• URLS
• UPNP streams
• Compressed files

Maybe this kind of info could be added to the docs if you already have an answer in your design.

[TT-ReBORN]

Actually this is a COM API limitation when marshaling between COM and JavaScript.
I found about this when I improved the new API and wrote for my future self:

	// Explicit track lists from JavaScript cannot pass native metadb_handle_ptr across COM boundaries.
	// Spider Monkey Panel or JSplitter only supports basic types (BSTR, VARIANT arrays, etc.), so the standard foobar2000 pattern
	// is to serialize handles as "path\u001Fsubsong" strings and recreate them on the C++ side.
	// Recreation creates new handles without cached metadata > GetMetadataField() would return empty
	// album/artist until info is loaded. We therefore preload metadata asynchronously when explicit
	// tracks are provided, ensuring album metric calculations work correctly.

Also I've used the safe \u001F as separator for distinction between path and subsong index.
I prepared this format because I think we can analyze also audio tracks that are in image ISO/CUE format.
I'll take a look after Library Explorer release for the next version release.

-TT

[regorxxx]

Didn't know COM was so limited, thanks for the info. Well at least being able to analyze iso/cue/dsd would be a great improvement, for sure.

[TT-ReBORN]

@regorxxx,

actually I tried a FLAC+CUE image format with Audio Wizard v0.3.0 and my current Georgia-ReBORN waveform script and it works. I do not have the time now to test all formats, but you could try yourself with foo_cuefixer:

FLAC+CUE
APE+CUE
WavPack+CUE
TTA+CUE
WAV+CUE
BIN/CUE
ISO
MDS/MDF
NRG