It could also be solved by adding the data to the same directory as the tracks they pertain to, as mentioned earlier, though I know people could be loathe to clutter up often already cluttered music repositories with a bunch of strange files. Also, files are personal data, and in the unlikely instance that multiple users existed in one dj-employed system, technically that analysis data would be personal and having it in a shared directory like Program Files would be a breach of compartmentaliz ation. This could be solved partially by having the data stored in the installation directory if that directory is the Program Files folder, though of course that wouldn't mend the potentially varying paths for the tracks (unless the analysis data has some kind of hash to be able to recognize an mp3 or whatever type upon input). Also, the tree changes for my tracks from computer to computer sometimes I dj with a smaller usb drive and a borrowed computer, or use a usb if a computer that I'm using has different music than I want to dj with for that particular gig. If I wanted to transfer my analysis date to any computer account with a different username there'd be a problem, even if it is true that identical paths will work in separate installations. But if I didn't, it would have been because of different usernames, and the analysis data is in the user folder. I'm pretty sure that I had the same filepaths. But I'm not getting one for the foreseeable future.Įven so, I'm all for adding access to features via preferences, and I'm sure doing that would be useful to many RJ: I've always wanted a master collection drive, external, it would order my files much more efficiently. Unfortunately, none of my externals have enough capacity to take responsibility for even most of my relevant collection, much less all. On Thu, at 5:52 PM, Daniel Schürmann wrote: > To manage notifications about this bug go to:
#Mixxx portable portable#
> make BPM/waveform analysis data portable
> Development Team, which is subscribed to Mixxx. > You received this bug notification because you are a member of Mixxx > have you more infos about the corner cases of this? > Mybe we should make this feature visible in preferences? > * so I can share all track metadata cues and playlists between two or more
> * I have all my tracks on a external HD > My personal solution for this is like that:
On Thu, at 5:52 PM, Daniel Schürmann > wrote: It should work if you use the same library /and/ the path to the files is Mixxx directory in the live tree, and even then the paths would potentially cause problems.Īnalysis data is very important. At best, they would have to employ some kind of Union overlay ghosting the analysis directory into the. As the system now stands, a live distro cannot use pre-rendered analysis data except under very restrictive circumstances that require a lot of end-user customization, something live environments are not typically engineered for. It has come to my attention that this bug as originally suggested, meaning being able to move the analysis data, and then recognize it wherever it ends up, is an especially important feature for live distros deploying Mixxx. I think the recipient Mixxx in this description was totally unaware of it even though it had all kinds of data sitting in the analysis folder. I recently tried to copy all the data from my analysis directory to its analogue on another computer hoping that it would be read, but the Mixxx of the recipient computer seemed completely unaware of it, no BPM data was displayed at all and the waveforms dd not seem rendered any earlier.
When I've spent hours analyzing my collection I'd like to be able to grab that data and transfer it to other machines with the same or similar songs, so I don't have to do it all over again, especially if the machines I'm transferring it to are slower than the one I used for the analysis and scanning will subsequently take longer.
0 kommentar(er)
