This is currently under investigation.Yeah, curious if those of us who already fixed the Scene 2 thing in 2.01b1 will have to do it again (Not that it’s a big deal, just wondering)
This is currently under investigation.Yeah, curious if those of us who already fixed the Scene 2 thing in 2.01b1 will have to do it again (Not that it’s a big deal, just wondering)
It’s just interesting because people who came from 1.00/2.00 to 2.01b1 had to do it OR* from 1.00/2.00 to 2.01b2 had to do it but not when going from 2.01b1 to b2 somehow.This is currently under investigation.
Sure but it's a symptom of something going wrong under the hoodFor the scene 2 switch issue, I just reloaded my scenes layout. Problem solved
This has been found and fixed for the next release. I was told it was an error of simple math.Sure but it's a symptom of something going wrong under the hood
Strange that I wasn't somehow at fault.This has been found and fixed for the next release. I was told it was an error of simple math.
It is normal for Cab 2 to use more CPU than Cab 1.Has anyone else been able to reproduce the Cab 2 block using more than double the CPU of Cab 1 block?
Can you elaborate on the steps needed to reload your scenes layout please? I have this issue now and don't want tweak every preset to fix it.For the scene 2 switch issue, I just reloaded my scenes layout. Problem solved
You do not need to load entire Layouts. It’s one switch. Also, it’s global, not per preset thankfully.Can you elaborate on the steps needed to reload your scenes layout please? I have this issue now and don't want tweak every preset to fix it.
Ah, ok, thanks for the infoIt is normal for Cab 2 to use more CPU than Cab 1.
Cab 1 enjoys an architectural benefit (and I don't mean crown molding).
Thank you!You do not need to load entire Layouts. It’s one switch. Also, it’s global, not per preset thankfully.
In the editor, click FC Edit or whatever it’s called in the top right.
Click Layout 2 (Scenes)
Click switch 2
Change where it says ‘Scene 1’ to ‘Scene 2’
I can post screenshots later but I’m at work now.
This update is killer and has fixed a lot of bugs, hopefully including the BIG bug that was giving me no output randomly. The only bug I've noticed so far is my delay feedback increasing on it's own. It'll go from 11% to 61% on multiple presets once I switch to them a second time. First time is usually normal. So far it has just done this on the tape delay that I have set for slap back. I'm wondering if it's because I'm using some old presets that I had drag and dropped into the FM9 recently that I had backed up from a previous FM9 backup. I haven't noticed it on newly created presets yet. This also occurred on the last beta.
You know, you get all pruny if you sit too long in the hot tub. Just sayin'.Strange that I wasn't somehow at fault.
Concur.I gotta say that whatever was done, it sounds effin awesome!!! I’ve only had two minor hiccups to speak of...
...I leveled all my presets last night at zero db and when I went back to play again today, those same levels that were perfect yesterday, were about 4db too loud today. I adjusted everything and will report back if that happens again.
They figured out the issue and it'll be fixed in the next update!This happened to me when this current beta came out. I updated the night before a gig and was running through the presets real quick. All seemed normal then happened back on a preset I could have sworn I had been on but the delay feedbacks was WAY up. At that point I didn't even experiment and just rolled back. I just figured I was mistaken and that I had not tried that preset after the update like I thought. Since the gig I have updated back to the most recent beta but the delays all seem normal. I am on the lookout for it now though.