Anyone tried the analyze lately?
The result in the chord sheet is an E-chord in every bar, doesn't matter what happens in the audio …

Running 2019/632/64bit

Seems to be ok in 32bit


chEEEEEEErs
Thomas

Here we go again.
Works fine here. Please post a step by step list of how you're going about this.

Hi Thomas,

...tagging on to John's post above...

I also tried it with 2019/632/64-bit and it worked for me. That said, I notice that you are in Sweden. If you are using the Swedish version of the program, this might behave a little differently than my English version.


Did you open Audio Chord wizard using options #2 or #3 on the image below?


These are two different audio chord wizards... #2 is the old version that has been around for many years and #3 is the newer version that uses the recently added Audio Edit window.

Also, have you tried using the 32-bit version of BIAB to see if it also behaves badly?

Lastly, as John as said, if you can give us brief step-by-step instructions on how you opened the audio file, we can follow them and see if we can re-create the issue.

Regards,
Noel

My brand new 2019 Mac (304 build) is doing the exact same thing with the E in every chord. I imported the audio via AUDIO menu -> Import Audio (WAV, AIFF, M4A...). I did the Oh Shanadoah sample from the ACW tutorial for Mac 2018 on youtube. Song played fine. I went to Audio Edit and placed the bar lines and checked the Auto Analysis (as instructed by the video) and the generation window with the progress bars popped up. I went back to the Chord Sheet and everything was E.

I did test this through the STAND ALONE ACW program and that generated the chords correctly.

What is meant by the comment "Here we go again..." - is this an issue from the past that is coming forth again?

I and in Colorado - so it is not an international version.

Also - my AUDIO menu is different from what you displayed - are you using a Windows version? I have the new Mac version.
(tried to upload a picture, but wasn't sure how to do that).

Help the Same Problem" all EEEEEEEEEEEEE

I just updated last weekend to the New MAC version 64bit (304) Band-in-a-Box UltraPAK+ upgrade. I have been a faithful update fan since 2014 and updated to I have the same problem with the Chord Wizard. I have tried every way to upload my mp3. The MP3 is just me playing once on my guitar so I know what chords should be showing up. I have used all three ways of importing my MP3. I can get the MP3 in the #2 and #3 versions and I then put my bar markers in. THen when I run the Analyzer all I get is EEEEEEEEEEEE. Though I can hear the music Changing. The only way I can see anything that looks close to right is when I run the old standalone version of the Chord Wizard. IT looks like it gets all the chords right but then when I try to import into BIAB the program crashes or the Chord Wizard just close and nothing crosses over. I will try to sit down this weekend and do some screenshots if that would help anyone to understand what is going on. I am in the US running a US version of the program on a MAC 2019 running OS Mojave

Sgtmusic

This is the windows forum

Just a Short update.
I switched back to my 2018 version 32bit and the Chord Wizard worked. if you have done an update lately and still have the 32bit for 2018 use that until PGmusic gets a fix for the Chord Wizard. I will post the screenshots this weekend of the issue with at least the MAC version of BIAB Chord wizard if someone wants to figure it out. Thanks All.
Sgtmusic

I have noticed same thing and when importing .wav file into 64 bit there is nothing but static. Not an issue with mp3 only wave. 32 bit version seems to work fine. I let PG know but have not had a response yet.

So why are you guys posting in the Windows forum?

Band-in-a-box for Macintosh

The 2019 Mac version just came out of Beta testing so they will want to know about this.

Bob

Mine is happening on the windows version

Well Forgive me, I just typed in the issue I was having with the Chord Wizard and figured someone might be having the same. I also thought since the 2019 version for Windows has been out a lot longer than the MAC version you all might be able to give some insight into issues you might have seen. But I guess this is a Windows Forum so I will head out and find a Mac Forum.

I too am a Veteran 23 years of services, and still serving the US Army Medical Corp everyday
Thank you for your time.
Sgtmusic

thomasc
Try the last version that you had for BIAB or the 32bit version and see if that fixes your problem. I am not sure about Windows versions but that worked for me.
Good luck from Brother
From the USA

Same file in ACW 32 bit

UPDATE: I rolled back to build 628 and it works fine. went back to build 632 and problem is back... There is an issue

Yes, and the O/P appears to be running Windows. But no user experiencing the exact same problem can comment here?

Thanks for your continued service especially the Medical Corp. As one former Sarge to another (Air Force) we have to pay attention to details, right?

I can see if you're not really familiar with Microsoft and Apple products you may not think there's a lot of differences but there are. The two platforms do have similarities but they are quite different. The Mac folks have been complaining for years that the Mac version doesn't have everything the Windows version has. It looks like the brand new as of last week 2019 Biab for Mac has closed that gap by a lot but since I've never owned a Mac I really don't know. That's why there's a separate forum for each.

Bob

I'm also Running 2019/632/64bit Win10. This also happened to me once with a file. My opening sequence to import my WAV file was open BIAB. Click the ACW Button. Select file.


Note for the programmers: I edited and corrected the chords to the song and had to generate twice before BIAB recognized the edits. No tracks had been frozen. The file was still in it's just opened state after import from the ACW analysis.

Not a conspiracy theory or anything but I use the ACW daily and this never happened prior to the release of Xtra Styles 7..... (I'm a fan of Dan Aykroyd in "Sneakers" 1992)

Thanks, we're working on a patch for this.

Maybe it is style pack 7. I didn't purchase it. Noel96 can't replicate. Wonder if he has the style pac7? Lastly a fix is coming. Being that in this thread 2 work and 2 don't ..
.

and then...just a few posts later...

Too much time spent being defensive and trying to prove the user has made a mistake! And, of course, the OP and several others were correct and the bug has been fixed.

Thanks Andrew, for listening to the reports and fixing the issue! You are appreciated!

+1

Actually, I have to agree. Why can't we work together more as a consolidated team here and support each other instead of simply trying to continually find issues with other's posts and berating users for minor political incorrectness and at the same time offering no worthwhile assistance?

C'mon team. There was a lot of unnecessary criticism to users simply for not using the 'correct' forum, when the underlying problem was ignored. People came here for help and were jumped on instead. The problem was not isolated to any particular platform but nobody bothered to even consider that. Not good. We should be doing better.

What he said^

Me too, worked fine.

I started posting here in June of 05. I had Biab for the first time a year or so before that. Even though I knew NOTHING about this stuff I read the manual, read the help files and got some the basics figured out.

I was aware of the forum from day one and read pretty much everything in all the different forums. I picked up a lot of info just by doing that. This was all before my first post. When I started posting I knew exactly which forum was which and which one to post on with my question.

Now, is that not what most would consider a logical and correct way to understand something as complex as digital audio and Biab in particular? I think so and I also think I'm not in the minority about that. I think this is a fairly common way to go about this.

I wanted to have a halfway decent understanding of how all this works BEFORE I even started posting. Without that basic understanding it's difficult to even know what questions to ask. Plus I hate looking stupid because I didn't do basic research first.

PG made a deliberate effort to list all the different forums in different categories. Within each category are individual forums. At the top of most forums is a Info and FAQ. Somebody took time to think about that and write it out carefully. It's obvious PG wants posters to read and understand those FAQ's.

The PG Product forums don't have a FAQ at the top because product forums are self explanatory IF someone is paying attention to something as simple as knowing what OS they have and looking at each forum in the list before posting.

It's common courtesy to do this when you're in a forum as a guest of the company you bought a product from. If PG doesn't care then why is the forum organized the way it is and why are there FAQ's all over the place? It's also disrespectful to not do that.

Two posters in a row both have Mac's. I said "So why are you guys in the Windows Forum?" and then posted the link to the Mac forum. This is some huge slight? This is being totally confrontational and chasing people away? Sorry, I don't think so.

To Sgtmusic and Smoknjazz, I didn't go into any of this in my replies to you but now I needed to to make this point. Please don't take it personally and certainly don't let this chase you away. This is a great forum and we will help you with issues you may have. Just pay attention to the different forums, ok?

Bob

The OP and several others WERE CORRECT! They reported a BUG that PGM has now identified and fixed!

We all benefited from their persistence in the face of denials and unwarranted criticisms of their choice of forum to post in.

I would add one more point...we are not guests...we are paying customers!

Thank you, Bob, for you're well drawn out disk on people just joining the Form. I am 55 years old and have been recording for 30 years as well as building computers both MAC and Windows-based. I hold a Degree in computer science. If you truly understand anything about the makeup of BIAB you would understand that the majority of the GUI interface is the same but the coding on the back is a little different. I am doing my own tare down of the 64bit system to see where the issue is a difference between the 32bit framework which still seems to work when using the Chord Wizard.

As for the Forum if you go to the top of the page and just type in your question it goes to the first logical similar subject topic. If it gave you a pull-down to separate between Mac OS and Window based operating systems I would have chosen that. And avoid you altogether.

I am so glad I spent 23 years in the military protecting your right to troll a conversation and point out the obvious.

Thank you but you were no help.
Have a Nice day.

What are you talking about, go to the top of the page and just start typing? Where?

Troll a conversation? Don't be throwing your military service in my face, I joined in 1964 my brother and belong to my local American Legion. And the Commander a good sax player, and myself, piano/keyboards play for a couple hours after the meetings.

Bob

This: