Awesome, I already started messing with the cue sheets and I already see a few short comings in the existing viewer so it'll need some work.
- trying to load a entry currently it only supports a single file. nope it just doesn't allow multiple entries and files too AFAICT
- the buffer is not continuously filled like the playlist viewer so thats more code to write too (otherwise it limits the size)
and code or a plugin to generate them
I'm thinking of basically you feed it a playlist and it converts to a cue file
In option 1 feed it a playlist and if you have a setting enabled for extm3u it gets converted on the first save
but one thing is that both viewers take the plugin buffer as scratch space so making either viewer a plugin could make performance worse
and therefore I guess it depends on what results in the best performance with the least amount of code in core
ATM I'm thinking thats probably option 2 as this is unencumbered by the current playlist stuff, has relatively low overhead for the rest of us
and won't break much else if anything when I introduce a bug
I'm open to suggestions either way.
I envision a context menu item in the playlist viewer that states 'use as cue' which then loads the playlist file and writes the data from the metadata of the files themselves
after conversion when the playlist is selected again the .cue file with the same name is instead loaded in the cue viewer with the currently playing track selected (if it exists)
later you might have changed the playlist so you delete the .cue file your playlist reappears in the viewer and you can again generate a .cue file