Yeah, sorry 'bout that man. I realized afterwards that heck, there is a Windows version too, duh. Which I don’t back up, but since they’re pretty lightweight, I’m gonna start saving the Windows installers for users if they need to revert and don’t have them.
Ideally, we as customers should have access to previous build/LM installers in our accounts, or here on the forum.
So back to your question… there is no need to uninstall when reverting or upgrading BFD3, or the LM. If you have the installer for 184.108.40.206, just run it and it will overwrite your current LM version with the previous one.
But maybe hang on a few days, as Drew says they can probably bang out a hot fix for this issue.
I thought this yesterday but forgot again.
He already has it! Sent it over to him yesterday.
If anyone else wants it, ping me.
@BFD_Drew Wait, the hot fix, or previous version?
The hotfix. And it seems to work very well.
Yeah, he sent it to me. I’ll try it out in a bit.
Hotfix seems to be working for me. No issues with custom saved output routing now. Thanks for the prompt fix.
Hi, where can I get the hotfix?
Check your inBox. I sent you a PM.
Got it… and tried. Its working so far Thanks a lot!! Now I can continue. Happy…
I also suffer from this problem.
Can I try hot fix ?
My environment is Mac OSX.
It should stay, if for nothing else than Drew not having to spend the extra time reading emails, and sending it out/sending a link and people who need not have to jump thru three extra needless hoops just to access a fix.
Good post, FB, IMHO.
if it’s stil in Beta shouldn’t be here as far as I understand? Otherwise it would have been announced in the public forum? I really don’t know as it was a small code fix as stated by Drew in the original post. Oh well we’ll see what he says…
All technically true, but also its technically here being sent to askers from the public forum, so… who feckin knows?
@Fender_Bender , are you in the beta testing group btw? Really feels like you should be if you arent.
Heya, let me send it out please, so I can keep track of who has it
@BFD_Drew That’s what I suspected. Sorry mate, just trying to help.
Nah, no beta testing for me. I currently only have one solid production setup, so I’d rather keep everything on it always functional. I have a hunch that we have way more than enough beta testers currently anyways.
That said, I don’t mind trying to help out here and there, or report bugs that I potentially find.
I’m also seeing this.
I was perfectly happy with 3.3 but suddenly started getting an annoying Demo Web API popup, so finally migrated to inMusic and 3.4.
Which busted the routing in all my projects.
I raised a support ticket 8 days ago which has been completely ignored.
I appreciate Drew and the team are jumping on it, but alongside various migration issues, it’s not been a great experience with inMusic so far TBH.
Just PM Drew for the hotfix. It seems to work fine and correct the routing issue.
All good, Drew’s kindly sorted now.