Help - LIVE says: Corrupt WAV FILES. NOT!
-
mickelectric
- Posts: 7
- Joined: Thu May 02, 2002 6:44 pm
- Location: Los Angeles, CA
- Contact:
Help - LIVE says: Corrupt WAV FILES. NOT!
LIVE 1.5 DEMO will not accept any of my WAV files in my library that I have converted from AKAI cd-roms with Battery or Reaktor. And that is most of my wav files. I've tested many of these files and it is not a few but all that LIVE says are corrupt.
When I click the file it will not preview and when I try to place in a slot I get the message: "can't read audio file - file is corrupt."
These wav files work perfectly in EVERY other application on my PC ranging from windows media player to Sound Forge to Cubase, Reaktor, Reason, Acid etc.
As much of my library came from Akai CD-roms and were converted with BAttery or Reaktor - this severely limits my loop material.
Other people are surely having this problem as well. I don't think you can blame it on Battery as the files work everywhere but in LIVE.
Hopefully there is a fix for that.
When I click the file it will not preview and when I try to place in a slot I get the message: "can't read audio file - file is corrupt."
These wav files work perfectly in EVERY other application on my PC ranging from windows media player to Sound Forge to Cubase, Reaktor, Reason, Acid etc.
As much of my library came from Akai CD-roms and were converted with BAttery or Reaktor - this severely limits my loop material.
Other people are surely having this problem as well. I don't think you can blame it on Battery as the files work everywhere but in LIVE.
Hopefully there is a fix for that.
Please visit http://www.creativepower.com
-
mickelectric
- Posts: 7
- Joined: Thu May 02, 2002 6:44 pm
- Location: Los Angeles, CA
- Contact:
files on the way
I'll pick out a couple of small ones and send them your way.
By the way,
I also noticed that LIVE will not accept loops from FRUITY LOOPS that were saved as 32 bit floating files. Unfortunately FRUITY only allows 16 bit exports or 32 bit floating. Just thought you'd like to know.
Thanks
By the way,
I also noticed that LIVE will not accept loops from FRUITY LOOPS that were saved as 32 bit floating files. Unfortunately FRUITY only allows 16 bit exports or 32 bit floating. Just thought you'd like to know.
Thanks
Please visit http://www.creativepower.com
Same prob here: Files generated with Akai 6000 samplers are considered "corrupt" (what a nice word for a file..) by live. I have to open the file in a sample editor and re-save it in order to make it work, which is a lot of hassle since I got about 2 gigabytes of Akai files in my sample library.... they do work in Logic though....
FORMAT
FORMAT
Hello Alex!
The issue of Live declaring wav-files being corrupt seems to continue. I can say now that definitley every file coming from Native Instruments applications or having been touched by it (take whatever you like, Kontakt, Spectral Delay, Reaktor and so on) by LIve is declared to be corrupt. I considered this to be a problem of conflict between different analysis-methods.
But then every sample on all of the five CDs coming with Kontakt now by Live are declared as being corrupt.
Well, as far as I can figure out, these files contain no analysis information in their header, since Kontakt itself is analysing them just when I start the tone- resp. time-machine. But nevertheless Live is declairing them as being corrupt files.
I have to open and save them in Wavelab/Samplitude to make them readable to Live.
I've sent two examples, one directly from the Kontakt sample-CDs (YT-ORSNR4x16) and one analysed by Kontakt (CLEAN_1_G4X03) to you by email.
Please find a reasonable solution to this verrry annoying thing soon, while this is obviously an N-I issue (Wavelab alerts to a corrupt header too, but opens the file anyway)...
Regards
The issue of Live declaring wav-files being corrupt seems to continue. I can say now that definitley every file coming from Native Instruments applications or having been touched by it (take whatever you like, Kontakt, Spectral Delay, Reaktor and so on) by LIve is declared to be corrupt. I considered this to be a problem of conflict between different analysis-methods.
But then every sample on all of the five CDs coming with Kontakt now by Live are declared as being corrupt.
Well, as far as I can figure out, these files contain no analysis information in their header, since Kontakt itself is analysing them just when I start the tone- resp. time-machine. But nevertheless Live is declairing them as being corrupt files.
I have to open and save them in Wavelab/Samplitude to make them readable to Live.
I've sent two examples, one directly from the Kontakt sample-CDs (YT-ORSNR4x16) and one analysed by Kontakt (CLEAN_1_G4X03) to you by email.
Please find a reasonable solution to this verrry annoying thing soon, while this is obviously an N-I issue (Wavelab alerts to a corrupt header too, but opens the file anyway)...
Regards
Vaio AR11S
XP Pro SP2
2GB RAM
intel T2500 2GHz
200GB RAID-0
RME FF400
XP Pro SP2
2GB RAM
intel T2500 2GHz
200GB RAID-0
RME FF400
-
randw
Me too via Nuendo
Yup
I too get the 'corrupt file' mesage when I export 16bit aif's from Nuendo Mac version...
I have to open in Peak and re-save...
post me here if ya want some small files from me too.
rand
I too get the 'corrupt file' mesage when I export 16bit aif's from Nuendo Mac version...
I have to open in Peak and re-save...
post me here if ya want some small files from me too.
rand
-
joypet
re: Corrupt Music Files
Hello,
I would like to know if a solution to this problem was found.
I purchased LIVE about 2 months ago to run on my iBook and 8500. Beyond the tedious corrupt file issue, I am now experiencing system error 10's while recording into LIVE! How can I do any gigs using LIVE with the fear of either my files being assumed bad, or worse, the whole system locking up on me?
I would greatly appreciate any feedback or answers pertaining to this.
Thanx-
I would like to know if a solution to this problem was found.
I purchased LIVE about 2 months ago to run on my iBook and 8500. Beyond the tedious corrupt file issue, I am now experiencing system error 10's while recording into LIVE! How can I do any gigs using LIVE with the fear of either my files being assumed bad, or worse, the whole system locking up on me?
I would greatly appreciate any feedback or answers pertaining to this.
Thanx-
With version 1.51 the corrupt file problem is almost solved. However, every file that was once handled by Live and is saved in a self contained set is no problem at all. The only corrupted files I got recently still come from N-I's Spektral Delay. But if you open them through any serious Wave editor and save them again, there should be no problem anymore.
The recording thing: Could that be up to your IBook? Sounds like it...
The recording thing: Could that be up to your IBook? Sounds like it...
Vaio AR11S
XP Pro SP2
2GB RAM
intel T2500 2GHz
200GB RAID-0
RME FF400
XP Pro SP2
2GB RAM
intel T2500 2GHz
200GB RAID-0
RME FF400
-
Guest
Some not so good results regarding corrupt files and 1.5.2
Well tried 1.5.2 with horrible results,
1.5.2 is good for samples generated with 1.5.2. All samples generated with a earlier release of Ableton (1.5) (or at least 80% of them, no kidding) is reported to be corrupt.
I'm a software developer myself and have a small tip to make to the dear developers of Ableton Live:
When doing changes to the format for a load or a save, can't you at least make sure that if you fail to load the new corrected format, that you try the old format that you generated before. This way I don't have to regenerate a huge amount of samples.
The way to make a migration is to have a dynamic enough load routine that can load all old formats and a corrected save routine that save the best format available.
1.5.2 is not a good fix for the problem with corrupt wav files. I did a test. Tested the all samples with 1.5 (all worked in Live). Installed 1.5.2 and rebooted. 80% of the samples I have generated with 1.5 failed to load. uninstalled and installed 1.5 again. All worked again...
/Magnus
Win2k sp2
Live 1.5
1.5.2 is good for samples generated with 1.5.2. All samples generated with a earlier release of Ableton (1.5) (or at least 80% of them, no kidding) is reported to be corrupt.
I'm a software developer myself and have a small tip to make to the dear developers of Ableton Live:
When doing changes to the format for a load or a save, can't you at least make sure that if you fail to load the new corrected format, that you try the old format that you generated before. This way I don't have to regenerate a huge amount of samples.
The way to make a migration is to have a dynamic enough load routine that can load all old formats and a corrected save routine that save the best format available.
1.5.2 is not a good fix for the problem with corrupt wav files. I did a test. Tested the all samples with 1.5 (all worked in Live). Installed 1.5.2 and rebooted. 80% of the samples I have generated with 1.5 failed to load. uninstalled and installed 1.5 again. All worked again...
/Magnus
Win2k sp2
Live 1.5