1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Audio files not loading to Reaktor

Discussion in 'REAKTOR' started by Phil84, Jun 2, 2020.

  1. Phil84

    Phil84 New Member

    Messages:
    4
    Hi there, I've searched a bit but couldn't find a clear answer to these. Closest I found in here was this but things disorientated a bit and couldn't extract a clear solution.

    Thing is that while I am trying to load certain files (first noticed that in FORM but it happens within REAKTOR in general) they just won't. If I drag'n'drop these, they won't drop, if I try to locate them in the file manager, once I select one I get the message
    The x-filepath.wav cannot be opened. Error while reading x-filepath.wav ! where x-filepath is wherever that file may be, and on another machine, which I first got the feedback from saying "sample is not authorized". Authorized to be used within Reaktor? What kind of "authorization" is that is needed? Production of my files, both those not working as well as those working fine, is the same every time in the post-production level.

    Mentioned on the previous thread are the extensions (checked, nothing changed), bit-depth (checked, nothing changed) and the stereo to mono conversion (original was in stereo, exported to mono, then I was able to load it but wouldn't get sound :/ )

    I' ve tried these files in every other possible situation, with other samplers, incl. Kontakt, as standalone audio files or whatever, success everytime except within Reaktor.

    What is it I'm missing? I'd be really glad to know :)

     
  2. Paule

    Paule NI Product Owner

    Messages:
    7,555
    Please attache one of your not loading audio wave file here. TIA
     
  3. Phil84

    Phil84 New Member

    Messages:
    4
    Here are just a couple, thanks in advance :)
     

    Attached Files:

  4. Paule

    Paule NI Product Owner

    Messages:
    7,555
    An easy answer: both are 24 bit.
    Please convert them with an audio editor to 16 bit.
    You can use Audacity or if you own Wavelab.
    If you're on pc take the free wavosaur. It's a good program for sample edit.
    https://www.wavosaur.com/
     
  5. Phil84

    Phil84 New Member

    Messages:
    4
    Appreciate the response but my problem with this is not how to be able to eventually load this but to find out WHY this happening, what causes it, in order to prevent it from happening. Btw, 24-bit isn't the case since I have countless wav and aiff files in 24bit-44.1kHz that work just fine. I can even bounce or export the above files (keeping the 24-bit) and they 'll eventually load. What drives me crazy is the reason why this is happening, I haven't figured out what is different in the process of creation/production that brings up this problem..
     
    • Like Like x 1
  6. Paule

    Paule NI Product Owner

    Messages:
    7,555
    After saving with wavosaur (24 bit also) they are loadable in p.e. FLOWs with sample input.

    With a hex viewer you can see - the headers are different.
    66Bonk1Spring.png wavosauer saved 66Bonk1Spring.png

    The left is yours.
    So if I got samples from any source and they don't load, wavosaur comes into play. Then everything works fine!

    66Bonk1Spring - end.png wavosauer saved 66Bonk1Spring - end.png

    The EOF - end of file - looks different also
     

    Attached Files:

    Last edited: Jun 3, 2020
  7. Portthames

    Portthames New Member

    Messages:
    19
    Paule thanks for the reply

    to be honest converting hundreds of thousands of samples to 16 bit makes this option unlikely for me, but if it works it's at least an option
     
  8. arachnaut

    arachnaut NI Product Owner

    Messages:
    3,106
    These files you posted are unusual. I loaded them into an audio editor and then saved them again in the same format and they work fine in 24-bit depth. Reaktor does support lots of bit depths including 24 (but not 64).

    The problem is subtle and points out a weirdness. The WAV format is a container file. That means it is divided into parts called 'chunks' and each chunk is defined by a header. Audio programs are supposed to ignore chunks it does not understand and the chunk header has a size field to tell the program how much data to process or ignore in the chunk.

    Your file has a 'fact' chunk which is usually used to specify some compression information. But I don't think the file data is compressed and the fact chunk is supposed to preceed the data it describes, I believe.

    I think it is this mal-formed fact chunk that is causing the problem.

    Here are two displays - your file - listed as Bad-Wave and the same file re-saved that will load in Reaktor:

    'Bad'

    Bad-WAV.png

    'Good'

    Good-WAV.png

    What is weird is that chunks are supposed to be ignored, but in this case, I think the file format is not correctly built so it is confusing Reaktor.
     
    • Like Like x 1
  9. arachnaut

    arachnaut NI Product Owner

    Messages:
    3,106
    Oh!! It is something else, not what I wrote.

    If you look at the 'Size' field in your sample, it says the data size is 22 bytes. In the other display the data size is 24932 bytes which is probably more correct.

    The format tag is also unusual.

    I think this type of Wave file is a bit odd, how was it made?
     
    • Informative Informative x 1
  10. Paule

    Paule NI Product Owner

    Messages:
    7,555
    With wavosaur you can use the batch converter
     
  11. Phil84

    Phil84 New Member

    Messages:
    4
    So, it took me a while to get back, we were doing some tests, and although I don't have a clear answer yet, there are some things I'd like to share. The original files that made me aware of the issue were within a sample pack I released. That was on a collab with a renowned duo and while checking and sorting the files I received, I admit I didn't come across the issue, everything seemed perfect.

    Once I was aware, I contacted them, asking for more info on certain processing during export. We then went backwards, step by step, since every single file they'd sent me, it just wouldn't load. We started from plain to obsolete 24-bit PCM, then went with bouncing in place, converting to 16, followed by alternative daws, multiple OS, ultimately taking it off computers. In all the outcomes, the result was I still couldn't just drag n drop, but when I was trying to locate the file in Reaktor's file browser, only the first type would pop a "couldn't find" message, while others just still wouldn't load, but with no error messages or whatsoever.

    Version of Reaktor I use is 6.3.2 and I kept trying with no luck. Then I thought I'd check on older versions. Went on the laptop, it had 6.2.2 on. Downloaded FORM there too, went on dragging the files and voila! Everything could be dropped in the sample editor. Everything except the 24-bit PCM option. That one would still pop an error message.

    So the questions (well, a couple of them) now are

    i) what could be wrong with that particular 24-bit PCM, since others of the same type are able to properly be loaded.
    ii) is there a known issue with 6.3.2 that explains the above?

    Since this happened, I've checked every single file we've ever released, meaning from other packs. We release everything in 24-bit / 44.1kHz and everything loaded just as they should.

    I'm attaching a folder containing the different alterations of the test file, if you wanna have a look.

    Thanks!
     

    Attached Files:

  12. Paule

    Paule NI Product Owner

    Messages:
    7,555
    header RIFF Wavefmt: all except
    header RIFF WaveJUNK: Master HOFA EXPORT (24-44100), (FL export)_bip, (FL export)_IN, (FL export)_IN16

    All your 12 different formats are readable in FORM