Forums

Full Version: support for CUE sheets and chapter points
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
One feature that would be really great would be to support CUE files that highlight individual tracks in a dj mix. For more information, see Wikipedia: Cue sheet (computing).

There are many DJs out there now that create mixes and accompany it with a cue sheet to help listeners discover new tracks.
Hi svz

That's an excellent and straightforward suggestion. Thanks especially for the wikipedia link, it allowed me to see not just why, but also how we should implement this feature.

Look forward to seeing CUE file support in a future AudioCodex version.

Out of interest, how do you see this working with AudioCodex? For us to implement Playlist to CUE export would be fairly simple. Would you want to see importing as well?

Regards,

alex Wrote:
Hi svz

That's an excellent and straightforward suggestion. Thanks especially for the wikipedia link, it allowed me to see not just why, but also how we should implement this feature.


No problem. I'd like to make it as easy to understand as possible Smile

alex Wrote:
Look forward to seeing CUE file support in a future AudioCodex version.
Out of interest, how do you see this working with AudioCodex? For us to implement Playlist to CUE export would be fairly simple. Would you want to see importing as well?


I would be most interested in import. The relationship is sort of like a playlist to individual song files, however ,this is a single audio file (dj mix, similar to playlist, but mixed by the DJ) and clips of the track would have additional metadata, sort of like an ID3v2 tag just for that section. This is support in the .M4A/B spec as chapter points (ala DVD) Now providing the ability to export a CUE file from the master output that can be provided for mixes made with AudioCodex is also interesting, but less interesting than reading them IMHO. It would be pretty useful and sweet as well. Especially if it can be created automatically based on ID3 tags and fader settings.

For a playlist output, I am used to seeing M3U or XSPF, not a CUE file. A CUE file is more used to signal parts of a media file. It is most often used for DJ Mixes, CDs or Broadcasts that are a single file and you want to give someone the ability to easily split it into parts based on logical boundaries. The splitting is usually done to burn the single file to a CD, so although it is a single mix there are track listings that correspond with parts within the mix just as you would see when buying a mixed CD.

From a UI prespective it would be nice to see the track of a mix next to the title of the file. So if the file is splesh_live_at_qool.mp3 and the ID3v2 says the artist is "Splesh" and title is "5 Hour Set @ Qoöl, San Francisco 2005" it could show the particular track he was spinning next to it (or underneath it) based on the cue sheet. something like:
- 5 Hour Set @ Qoöl, San Francisco 2005 : Splesh { Michael Jackson - Beat It [Splesh Mix] (Qoöl Recordings) }

I am not exactly sure, but I am hoping you are getting the idea. Probably the easiest way to think about a cue sheet is chapter points in a DVD.

Some examples and uses are:
- http://www.djstrex.com/mixes/
- http://www.hybridized.org/sets/editcue/423/518
- http://www.cuedb.net/
- http://djmixes2k.dfx.at/
- http://www.rockbox.org/twiki/bin/view/Ma...eetSupport
- http://www.tsyle.com/how_to_burn_cue_files.php

I hope that helps,

-- Sander

svz Wrote:
For a playlist output, I am used to seeing M3U or XSPF, not a CUE file. A CUE file is more used to signal parts of a media file.


Of course, thanks for clarifying. :-)

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.

svz Wrote:
From a UI prespective it would be nice to see the track of a mix next to the title of the file. So if the file is splesh_live_at_qool.mp3 and the ID3v2 says the artist is "Splesh" and title is "5 Hour Set @ Qoöl, San Francisco 2005" it could show the particular track he was spinning next to it (or underneath it) based on the cue sheet. something like:
- 5 Hour Set @ Qoöl, San Francisco 2005 : Splesh { Michael Jackson - Beat It [Splesh Mix] (Qoöl Recordings) }


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.

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.

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 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.

alex Wrote:
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.

alex Wrote:
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

alex Wrote:
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.

alex Wrote:
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.

alex Wrote:
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

Reference URL's