One of the features we have in development for AudioCodex is a set of track markers, like the in and out points, but with attributes such as text flags and settings keyframes attached to them. Analogous to chapter markers for a DVD, or indeed a CUE list, but also able to store internal AudioCodex settings.
I can see CUE support, both import and export, fitting very well with this feature. In fact that is a very good additional justification for it. We are aiming to get this feature rolled in within the next few updates.
Yes, this is very much inline. This also falls in place with the M4B MPEG-4 Container extension used when the file contains bookmarks (chapters) and saves where you stop playing, such as
iPod Audiobooks.
If I understand this suggestion correctly, the track name (in the main transport bar) would change during playback of the file, but only for files with a CUE list associated. I'm not sure how feasible that is in the short term, but I'll discuss it with Mantis.
Yes, or something along those lines. Basically a way in the UI to display the name/data related to a subset of a clip (chapter in audiobook, track in a mix, etc.).
The more I think about this, this is quite core to what a new audio player needs.
As there are many uses for the concept of identifying part of a file. CUE files is just one of the ways, really.
Some more related links I found:
- http://id3v2-chap-tool.sourceforge.net/
- http://www.macdevcenter.com/pub/a/mac/20...s-mod.html
- http://homepage.mac.com/vaughn/audiobinder/
- http://forums.sbooth.org/viewtopic.php?f=5&t=298
However, one way I can think of to quickly implement your idea would be to use the Track Info key in a custom Music Visualizer to monitor this info. Then you could have your visualizer display the info as it updated during the track playback. Alternatively, we could provide an extension to the Music Visualizer protocol to support this feature for visualizers played through AudioCodex.
That would work for the short term, sure.
I will do some more research, and I'll ensure CUE support is added in a near future version. I can't promise when, as our dev resources are limited, but it is indeed an idea with lots of potential.
I know exactly what you mean. If I wasn't as busy as I already am, I'd say I'd help you code it.
I hope to be able to get your feedback on those features when they are added, so keep an eye on the next few releases.
Thanks again for your ideas and input.
Sure thing and no problem. I appreciate the consideration and looking forward to using AudioCodex. It sure is promising.
-- Sander