Perhaps I am being dim but it looks like CueSheets are basically for people who want to choose when a track begins and ends for a particular mix? This sounds interesting but I wonder why not just include Start and Stop fields in the library and then let the MM player or burner use these to create the 'perfect' mix. Or is that what this is about?

cue-support would make this app perfect :D

The only thing missing in this great app (and why I have not bought a 30$ lifetime licence) is this feature; adding "cue-tracks" to library. Please implement this, guys :)

Here is Help File My friend and I made for very First version of CUESheet Editor few years ago it explains all I hope and can answer some Questions :)
[url=http://pekemm.madpage.com/temp/cuesheeteditor.chm]CUESheet Editor Help File[/url]

A cue sheet is basicly a small text file that tells your burner how to burn a CD. It contains information about.
- File (or files) to burn
- Start and stop time of every song
- Album
- Album artist
- Artist
- Title
+ more
The information can be used to burn CD-text into the CD.

It's very common to rip a whole cd into one big (mp3, flac, wav) file, especially if it is a mixed CD (no gaps between the tracks). At the same time you should let the ripper create a cue file wich contains the info desribed above. (Use eg EAC: http://www.exactaudiocopy.de/ )

When you then play the file in MM there wont be any gaps in it. And if you want to create a CD from the file it is very easy and the result is almost an exact copy of the CD. This is by many a preffered way to back up their CD collection.

The downside is that the file is treated as one track with one tag by MM. So you lose information about the individual tracks. You can for example not search for the indiviual tracks wich would be the case if you had ripped the CD into individual tracks. But to create a "perfect" gapless copy of the CD is not always possible todo from individual tracks.

So i think it would be great if MM had full cue sheet support regarding burning as well as full library handling of the tracks within the cue sheet. Then I can manage my backed up CD collection as individual tracks and at the same time have the possibilty to create "perfect" CD copies of them.

/Martin

I only use Winamp for Shoutcast purposes anymore, it's dead to me basically.

I still, after reading all this, have no idea what CUEsheets actually do or what they're used for. Anybody willing to explain this to me?

I was thinking something along the lines of mp3Cue plugins for winamp - even an option that would treat any file with a .cue in a special manner when playing it would be great.

This is a great plugin http://winamp.com/plugins/details.php?id=143011 for winamp... If it could be supported in MM, even without the ability to use the 'subtracks' in a playlist then that'd be cool.

It's a shame that I have to use Winamp for a lot of my music when I'd much rather solely use MM.

It is not possibly right now. It can be made one script that will Make Playlist according to CUE But You will not be able to use that playlist as playlist couse it will point to sam efile and you will get Duplicates.

Pretty please look at cue support, even basic breaking down a music file into multiple play-list entries would be a good start.

My word is not only one, I'll be happy to make CUE Support for MM as soon as MM is capable to support it.
It really needs big and high risk changes to library structure, which if you agree in case we all want stability (like we used from MM) can be done only in case of major version update.
Also CUE support involves few dosent features also needed in MM, lots of UI changes, Calculators, CD Burning, Scripting and in some solutions even player engine itself (Better gapless).

That sounds very interesting! My main wish for MM to develop, is just full cue sheet support, with full library handling, since i have tons of music files with a corresponding cue sheet. So please, please, please! Incorprorate your solution with the next version if possible!

I even voluntare to make some heavy testing, if needed, just to make this feature come true!

Thanks
/Martin

CUE Support is not big deal to make I allready have all needed info and My own APP (Someone order it from me but not paid for making) that do support CUE in Full. The main reason is that Curent MM Library do not support of importing CUE File. I'm 100% sure that no one wants to temper and have games with 60k tracks in library if not 100% sure that it will work flewlessly?
Or am I wrong?

Ok, blaming the Developers leads to nowhere.
I have tried a lot of programms that were promising decent Music Management but none did the trick (except from MusicLibrary perhaps) and most important [b]none was free[/b] and had the developers so close to the users...

Now, concerning the CUE support...
Yes, i do think that this is a MUST have and its sad that no MusicPlayer i know supports CUE files fully.
There is a workaround though, there is a freeware utility out there called CueSplitter. This little magic splits one big Mp3 to smaller ones according to the CUE file. You can then add this files in MM and play them as separate tracks. Compine this with a gapless output plugin and you have something very very close to what you ask.
Offcourse you end up using twice the space you used originally. But the files are cut so accurately that if you throw them in Nero using the correct order and selecting no pause between the tracks you end up with a perfect gapless CD. Having this in mind you may decide that you don't need to have the original large file (at least in your hard drive).
This is what i do, split the large file, delete it and then add the newly created files to MM.
It works fine from me...
Hope this helps

[quote="just hopped by"]it's pretty obvious the MM team doesnt care what the users want, hmm?[/quote]

Perhaps they do and with the finite rescoures they have, they develop features that are in more demand.

There simply doesn't seem to be enough people who want cue sheets.

We really DO care about what our users want. The thing is that the to-do list is incredibly long and not all features can be implemented in a reasonable time. So then it happens that there are users angry that 'their' feature isn't implemented yet...

Jiri