Importing BM2 into Auria

edited February 2013 in Support
I did a search and couldn't find an answer on this issue. Almost all of the wav files I import into Auria from BM2 do not work. They show up as having no bits and the time at 00:00. Has anyone else had this issue? Please help.

Comments

  • edited 5:26PM
    Yes. I've been bringing this issue up a few times, working with other apps and BM2 wavs.
    Other people have, too. BM2 makes bad exports occasionally.
    It can read its own wav files, but others can't.
    Was hoping this would be fixed by now...

    Intua, thoughts?
  • edited 5:26PM
    Yeah, I'm not sure what BM2 is doing when it creates WAVs, but I've had other apps outright crash from trying to load WAVs made with BM2.
  • edited 5:26PM
    .wav file format follows RIFF specs. That is, it is a concatenation of several blobs of data, each of which is headed by a data type code and a length. Apps can order these any way they like and can include (or not) additional data type blobs.

    When I first started coding to this format I was unaware of the optional parts and so used a struct to represent the entire header up to the data chunk. It failed this way when I tried loading files from Logic. I'm hypothesizing a similar problem here. The loader must at least see and skip chunks it does not recognize. Auria probably encodes some meta data in one of these optional blobs before the data blob.

    Of course I could be totally wrong and off base. But it's a thought.
  • edited 5:26PM
    .wav file format follows RIFF specs. That is, it is a concatenation of several blobs of data, each of which is headed by a data type code and a length. Apps can order these any way they like and can include (or not) additional data type blobs.

    When I first started coding to this format I was unaware of the optional parts and so used a struct to represent the entire header up to the data chunk. It failed this way when I tried loading files from Logic. I'm hypothesizing a similar problem here. The loader must at least see and skip chunks it does not recognize. Auria probably encodes some meta data in one of these optional blobs before the data blob.

    Of course I could be totally wrong and off base. But it's a thought.

    I believe you are right. It's something with the headers on the wavs BM2 makes. I read about it somewhere on the Auria forum. They also mentioned that they made a fix for it in Auria a few updates back but I still have issues.

    The only way I can consistently get a wav from BM2 to work in Auria is to copy and paste. For the most part I bring all my files to Audacity to convert the BM2 wav to a standard wav with headers.
Sign In or Register to comment.