emusonacid!

I tried several times to load a sample (.wav file - size 430 kb) from floppy.
The machine starts, but it doesn't finish to load the file and it stops at 95% with no other messages (ie file corrupeted, error in end of file or other similar).
I tried to load smaller files (size 30 kb) with the same procedure and it worked well.
Maybe it depends on the size of the file? Are the other ways to load wav sample than through floppy?
Thanks

I load them without problems, only one time happened and it was floppy with bad sectors and data was corrupted, try to use a new floppy.

make sure the sample is 16 bit?

Is there a way to understand if the file contain a 16 bit sample or something different?

paozir wrote:Is there a way to understand if the file contain a 16 bit sample or something different?

When you move the mouse arrow over the wav-file in the explorer, it should show you
Type:wav
Bitrate: 1411 (for 16 bit stereo), 2116 (for 24 bit stereo) for example
Size: in kb/MB

Also Wave-Editors like Audition, Soundforge, Wavelab will give you detailed info about your wav(s).

I only tried this once with EOS 4.61 and it worked, but I read here on the board there is a problem with this in EOS 4.70,
(dunno if it was that it was not working at all or if it only happened to longer samples that never finish to load I forgot, sorry, you may search the board for it)

Paozir

Are you using an Ultra or Classic model ?
I have 2 -E6400 classics and this could be useful for me at the moment, depending upon load times which i know can be slow.
How long did it take to load + How big was the wav file?

thanks

I get this sometimes too, using a scsi zip drive. Some wav files load perfectly and some cause my e6400 Ultra to freeze as it loads, so the loading screen stops at 93% or so, and I have to power it off and back on again. It doesn't seem to be dependent on size, and some files that have been created in exactly the same way as others load and some don't. Mysterious business -does anyone know if EOS 4.7 has any peculiar restrictions about file names or sizes of WAVs?

It could be meta-tag data that is screwing with your machine. Try to remove any metas and give it another go.

Thanks, I find that saving wavs in Audacity seems to do the trick for some reason.

caraway wrote:Thanks, I find that saving wavs in Audacity seems to do the trick for some reason.

it is probably striping the meta-tag data and just giving you clean wavs.

Sorry to hijack the thread but I'm also having a problem loading wavs via floppy. I saved some drum samples to disk but the E6400 only sees one of them, any ideas why this might be the case?

I've tried several different disks.

@joselle: But you browsed thru the floppy- banks with INC-button/data-wheel for example, did you ? As they appear as one sample per bank in sampler, i.e. if you saved 7 samples to floppy the Ultra makes them appear as 7 banks on the floppy with 1 wav each. Do NOT put wav-files in a folder on the computer and save to floppy, if you do only ONE sample will be shown in Ultra. Just my first obvious idea. If it's not that you had to check the wav-files for compability (bit-/samplerate and such).

I really think your problem could be that extra data is saved within the wav file (meta data)
This data can include text and picture info.
I believe that if you use audacity you can strip the data from the wav.....
1 load some files into the program
2 save as wav
Job done... as it will not allow any of these tags to be saved.
Just make sure you save the wav in a resolution EOS can read.
If you are still having trouble email me a wav and I will check it out on my sampler

I think it is exactly the way Rascal Revenge described it.
-> Every .WAV-file is interpreted by EOS as a complete bank.
When you browse the samples in this bank, you just see exactly one single sample.
When switching back to view all banks on the floppy disc, then you will see some other banks with the same name of the stored .WAV-files that also hold just one sample each. That's it.