Hi Nathaniel,
@NathanielAlgo
thanks for your reply.
The problem with the current situation is, that you can’t reach those cue points or analysis data in one handy file. I guess the major problem is, that when you export your library to a different djay Pro setup (eg. via USB Device to some Live Kit of a Venue or a different DJ), the soundfiles need to be stored in the same folder structure to get recognized and when i replace that library file in appdata, the soundfiles that have been stored and registered in library before, are lost. At the moment i can’t even move my files into another folder of the same HDD or rename them without loosing the cue points.
I have the situation, that i practice on my desktop mashine, because it is faster and i can record my mixes in a better quality. I have a laptop kit for life situations and would like to transfer tracks with cue points and analysis data from my desktop to my life kit. Also i would like to invite other DJs using djay pro playing on my kit during a show.
But this is not possible, because cue points and analysis data gets lost. So what i am doing now, is often repeating the work with setting the markers of 20-30 Tracks just to play them on my laptop. That costs extra hours. And believe me, i tend to play tracks i purchased from beatport, juno or bandcamp.
My wish: When you work with files stored on a hard drive, i would love to have for each of a soundfile i’ve analyzed and worked with in djay pro, a sepperate file, that contains cue points and analysis data, like meta info and graphical wave form data. Like Wavelab does with .wav files and .wav.gpk files.
You then have 2 Files:
My cool track.aiff
My cool track.djay
When you read in these audio files together with metafile at other djay pro systems, you then should have the same experience like on your local mashine.
I know you have to care about two cases:
-
One is the online libraries (soundcloud etc.) where you need to store the metadata in a collection based on the adress of the stream and the online account, because no physical file on a harddrive will be stored.
-
Second is the Filesystem working with soundfiles where you can add such an additional meta file, for sure.
I think this is why you put all that data in a library file at the local app data folder.
Could you understand me?
Thanks for paying attention. This would be such a big improvement.
Greetings,
Paul =)