Just noticed that my 2019 BIAB splash screen still said 32bit. I run BIAB from an external drive and followed PG instructions to create a shortcut to 64bit and can now run either version.
I was doing a task today which entails using the ACW to analyse a song in mp3 format. In 64bit the mp3 file won't convert or load and I get a yellow pop up error message saying that the Media conversion can't be done and something about "Foundation was unable to convert to .wav" and an error number (but it's too quick to memorize the whole message)and the process stops! I tried the same thing in 32bit and it worked fine. Anybody have any ideas why it won't work in BIAB 64 please?

Kev,
I can confirm that I'm having the same problem, noticed this yesterday. In 64-bit version, I can't even read the error message, it just very quickly flashes, and no processing of the file. Switch to 32-bit version (this is using the 623 build), it processes the exact same file with no problem.

I haven't used ACW very much, still learning, so I'm not sure if the same situation occurred with earlier versions.

Hi Kev T and Photodoc,

I am not experiencing any issue using the Audio Chord Wizard (ACW) to import a MP3 file in 2019 Band-in-a-Box 64 bit V623. I'm wondering if the program may be experiencing an issue converting from MP3 to WAV. I suspect that may be what the error message is trying to say.

You can view a message log of the messages by navigating to "Help" > "Utilities" > "Display Log Text File Of Green/Yellow Text Messages ...".

Also, press Ctrl + E or "Options" > "Preferences" to open the preferences window and in the bottom, right you can change the amount of time messages are displayed.

Build 623 64 bit is not converting or loading correctly on my system either. 32 bit build 623 is working.

Thanks Jerry and Charlie. At least I'm not the only one experiencing this oddity?? I wonder what makes Jim's setup different to ours?

Jim. Many thanks for the great tip about accessing the error log. From that I can see that the full message reads:
"Audio Conversion Error: Media Foundation failed to convert to .wav The error number is -2147024864 [2019.617.0, 09/03/2019 16:42:17]"

(Another similar message has a different error code of -1072875819. They seem to be the only two codes displayed).

If I get time today I might see if pre - converting the mp3 to wav in Adobe Audition and then trying to load into BIAB 64 ACW works, but still curious why it will convert in 32 but not 64??

Thanks guys for you help so far.

Kind Regards

Kev.

So.....I tried the idea of pre-converting to wav before loading into BIAB 64 and didn't get any error message this time.....but just nothing else happened. Followed the latest ACW vid (BIAB 2018) Audio edit screen was just black.

+1

The black audio edit screen means no audio was loaded onto the track. That doesn't mean the audio WAV file doesn't contain audio though. The converted audio may have not been extracted from the file for some reason. The WAV file may play in another program. Did you test?

If I'm understanding your process, you have an MP3 file and convert and save that MP3 as a WAV and then attempt to use that WAV file in the BIAB ACW, correct?

I'm interested to understand the conversion process you're using better. Can you provide more detail?

Thanks

Just as a guess, are you using 44.1KHz or 48KHz sampling rate with the WAV file?

My suspicion is your MP3 to wav convertor is a 32 bit based utility. My guess is the 64 bit BiaB program wants to see a 64 bit based utility. As a frame of reference, a 64 bit program can not use a 32 bit based DX effect or instrument. PG Music had to update the PG Music effects to 64 bit before the 64 bit BiaB program could utilize them.

My computer has two MP3 to wav convertors. One utility is 32 bit based and the second 64 bit based. For those that use it, the Lame MP3 convertor is 32 bit based.

OK guys, thanks for all the input regarding this. I contacted Support (Mike) today, and he pointed out how this works!

In 64-bit BIAB, the "new" approach is to avoid using the Tool labeled "Audio Chord Wizard". That is the "old" way, which works fine in 32-bit version.

With 64-bit, simply use the menu File | Import | Import Audio (WAV, WMA, MP3, WMV)
(Doing this works quite fast, there is no Green / Yellow message, which made me think something was wrong, but it's not!)

The Audio track appears as an Orange color, and then the trick is to change your "View" by using the "Audio Edit" icon on the "Views icons.
There's your audio..... works fine! Ahem.. just a newbie misunderstanding on my part. Great support folks!

I will experiment some more. I'm understanding that 64 bit may not import a WAV file when using the Audio Chord Wizard to select, import and initiate a chord analysis but wondering if the older version of the ACW will still work if the audio is loaded in the way you indicate.

Charlie,

I had a chance to look at this closer tonight --- it's a little more complicated than I thought earlier.

I record files as either .MP3 or as .WAV in BIAB, but also some likewise recordings in Reaper.
I haven't seen any problems opening files in Reaper itself, whether they are Mp3 or WAV, and originally from either program.

I now see that when I try to import a .WAV file originally rendered from Reaper, into 64-bit BIAB Audio Chord Wizard, nothing happens --- no import.
If the Reaper file is rendered as a .MP3, it imports into ACW just fine. This is 64-bit BIAB.

However, when I switch to 32-bit BIAB, those .WAV files from Reaper import into ACW without any problem! As do the .MP3 files from Reaper.
A bit convoluted, I hope I'm explaining this accurately.

I'd say that 64-bit BIAB has something going on that prevents ACW importing .WAV files from Reaper recordings. No problem at all with 32-bit BIAB.

Jim, thank you for mentioning Auto Chord Wizard, I was frustrated trying to figure what ACW was.

I'm glad my comment was helpful. Thank you for mentioning it!