The Mixcraft Import Function
Posted: Mon Aug 11, 2014 8:00 pm
I'm a very new user of Mixcraft and already loving what I'm able to do with the provided samples. I thought to import some of my own samples but the results were not as useful as I had hoped.
For the vast majority of a GB or so of loops, Mixcraft used the domain name of the producer as the name of the loop when the filename provides a much more descriptive name. In principle that descriptively formed filename is available using the File Source or File Location fields. But, in my case. the relatively long path name makes use of these fields quite cumbersome. I had hoped, rather speculatively, that one of the fields would contain the file name and the other would contain the path. However, it seems to me that the both fields were loaded with the same value, that of the complete path.
Of course, I could relocate the files on my hard drive. But life becomes somewhat awkward when software applications determine the locations of files. Having nevertheless given this arrangement a try I found that it didn't work well because the samples are organized into folders containing folders. So even if I move the collection to the root directory of a drive, the path names of individual samples tend to be long and unwieldy.
My question, of course, is how one can best make use of the import function. But I wonder in particular whether there may be ways to exercise more control over the process so that the fields of imported records have the most useful values possible.
Thanks for any related thoughts!
Cheers,
For the vast majority of a GB or so of loops, Mixcraft used the domain name of the producer as the name of the loop when the filename provides a much more descriptive name. In principle that descriptively formed filename is available using the File Source or File Location fields. But, in my case. the relatively long path name makes use of these fields quite cumbersome. I had hoped, rather speculatively, that one of the fields would contain the file name and the other would contain the path. However, it seems to me that the both fields were loaded with the same value, that of the complete path.
Of course, I could relocate the files on my hard drive. But life becomes somewhat awkward when software applications determine the locations of files. Having nevertheless given this arrangement a try I found that it didn't work well because the samples are organized into folders containing folders. So even if I move the collection to the root directory of a drive, the path names of individual samples tend to be long and unwieldy.
My question, of course, is how one can best make use of the import function. But I wonder in particular whether there may be ways to exercise more control over the process so that the fields of imported records have the most useful values possible.
Thanks for any related thoughts!
Cheers,