anyone know what the size is?
the same must hold true for all the freeware sampler players, no?
thanks.
//c
maximum size of samples in mod2?
hmm, i've had this problem with the mod2 since the begining...i couldn't figure out why some samples would load and others would give me the dialogue saying that the sample isn't in the right format.
mono, wave format, 16bit, 44.1khz with a .wav extension....all things i was following.
i attributed the problem to having a cap limit on file size, i have an external sampler so i didn't really care and let it pass.
i use Bias Peak as my main audio editor and it seems it is adding something to the file that makes luna think it isn't in the right format. it uses quicktime to import and save wav files....i'll have to email cw and bias about this.
i tried a different convertor (sound app) and i was able to load 2 and 3 mb sized files! woo hoo!
there probobly isn't even a limit, and yes, how many times after making a posting do you figure out an anwser to your problem not long after the initial positing.
anways.
//c
mono, wave format, 16bit, 44.1khz with a .wav extension....all things i was following.
i attributed the problem to having a cap limit on file size, i have an external sampler so i didn't really care and let it pass.
i use Bias Peak as my main audio editor and it seems it is adding something to the file that makes luna think it isn't in the right format. it uses quicktime to import and save wav files....i'll have to email cw and bias about this.
i tried a different convertor (sound app) and i was able to load 2 and 3 mb sized files! woo hoo!
there probobly isn't even a limit, and yes, how many times after making a posting do you figure out an anwser to your problem not long after the initial positing.
anways.
//c
well, so far i've found out by looking at a wav file made from peak and one made with sound app within sound apps get info window, that peak has a larger attribute called blocking...never heard of it before. the file created with peak has a value of a 160 byte offset, the soundapp wav has the value of a 44 byte offset.
my looping information apparently isn't getting saved in peak when converting either.....argh!
i am fairly sure there is no option in peak to turn off anything peak would be adding to the file.
peak uses quicktime services to support a bunch of file formats for reading and writting, i imagine the problem lies in quicktime.
i will try out 2 other audio editors to see if the results are any different, though i imagine they use quicktime services as well.
blah.
//c
my looping information apparently isn't getting saved in peak when converting either.....argh!
i am fairly sure there is no option in peak to turn off anything peak would be adding to the file.
peak uses quicktime services to support a bunch of file formats for reading and writting, i imagine the problem lies in quicktime.
i will try out 2 other audio editors to see if the results are any different, though i imagine they use quicktime services as well.
blah.
//c
think I'm gonna run a batch over my samples. I've batched my own samples to have my headers. Got to get thses out againOn 2002-02-07 11:36, subhuman wrote:
You're right, the WAV reader won't load a .WAV with extra header information. Soundforge saves this header information by default, so any waves you editted in soundforge without unchecking "save info to header" wont load.
