did chrome/chromium update break pro audio control?

[prof hazmatt]

In Nov I upgraded from a 10 year old focusrite scarlett to an Ultralite Mk4 and loving it so far......As of Sunday everything worked fine, and tonight now audio passes through to DAW just fine, MOTU discovery sees it, but when I click on 'open pro audio control' it opens up my default browser (chrome) and I get an error "this browser is not supported, Please click here to learn more and upgrade to a more modern browser" the click here link (http://whatbrowser.org/) gives me a 404 broken error, and nothing happens. I try to talk to the ultralite in MS Edge, same thing. Just downloaded Firefox and that works. So hooray for still being able to control signal routing...maybe this is a sign I should support Mozilla again? Anyone else having trouble? Anyone experience something similar in the past?

cheers,
M

[mikehalloran]

Send a trouble report to Google.I've been doing this for years. Chrome is the only browser I know where you can do that. It's under Tools/Help/Report an issue.

Sometimes, it's something that is broken in Chrome. If so, updating the browser a few hours later will show it fixed. Google will not get back to you.

More often, it's some Chrome extension getting in the way. Try disabling all browser extensions and plugins and see if you still have a problem. If gone, re-enable one at a time after checking you have the latest version. Any bets on it being a pop-up or ad blocker?

[prof hazmatt]

Interesting thought, and makes sense for potential incompatibility. Only extensions I'm using for chrome are google docs & adobe PDF reader, and I guess it is something else under the hood because it also affected Microsoft Edge, which I don't normally use, and doesn't have any extensions installed. Does anyone know if the Pro Audio Control relies on any flash components? That's supposed to be deprecated in Chrome any day now.

Thanks for the suggestion to contact Google, will take this up with them, and likewise reach out to MOTU. Now to recreate some of my presets with Firefox since I did the factory reset last night.

[mikehalloran]

Interesting thought, and makes sense for potential incompatibility. Only extensions I'm using for chrome are google docs & adobe PDF reader, and I guess it is something else under the hood because it also affected Microsoft Edge, which I don't normally use, and doesn't have any extensions installed. Does anyone know if the Pro Audio Control relies on any flash components? That's supposed to be deprecated in Chrome any day now.

Thanks for the suggestion to contact Google, will take this up with them, and likewise reach out to MOTU. Now to recreate some of my presets with Firefox since I did the factory reset last night.

Flash was supposed to be gone Jan 1, 2017. That clearly didn’t happen but Safari, Firefox and others are also dropping it on Dec. 31, 2020. It remains a serious security risk.

[Hackej]

Hi!

Just want to know if anything got solved regarding this, as I have the same problem with my new Motu 828ES.
BUT the strange thing is that Chrome opens up the web UI correctly if opening up Motu Discovery first and using the second link
(from "All Devices" tab) in the Discovery application.

So when trying to start the Pro Audio Control application in different ways I get this result:
o From Minimised Motu Icon = Browser error
o From Motu generated desktop shortcut (from installation) = Browser error
o From Discovery link “Thunderbolt / USB" tab/page = Browser error
o From Discovery link “All Devices” tab/page = Web mixer opens correctly in Chrome

And in Edge it opens up correctly as well.
But beware, when I open up Pro Audio Control in both Edge and Chrome at the same time, they tend to display some different info.
Primarily different "current" invoked presets for for example Routing.

Any developments regarding this?

/Hackej

[tyrone22]

I have not tried yet but almost certain it is due to flash player being removed during an update from windows 10... I updated my offline DAW and this is happening seeing if I can find flash player again to install

[tyrone22]

Is this being worked on?

[Hackej]

Hi!

I found a solution for this that works for me!

Check the browsers zoom level and set it to 100% and then try again.
Different browsers have different ways of setting zoom level, but usually as part of setting in the browsers menu.

/Hackej

[tyrone22]

Nice ill try ot but I just installed Firefox which is fine....

[John_nj]

Currently only Firefox works for me.
Chrome, Chromium Edge, and Opera all generate the
"This browser is not supported.
Please click here to learm more and to upgrade to a more modern browser."
error when trying to connect to my 624.

Changing the zoom has no impact.

Interestingly, both Chrome, Edge, and Opera all work fine on my Mac running MacOS 11.3.

[mikehalloran]

Chrome lets you submit trouble tickets. You do this under the Tools menu. They will never get back to you but I’ve never had a problem that wasn’t resolved in a few hours. After you submit, wait awhile and click on the About line and check for updates. When you see one, run it and see if the problem persists.

[theMidiTamer]

Am I the only one having troubles with MS Edge (which currently is my main browser)? I always get the "the browser is not supported" message. Luckily I still have Firefox, but it's pretty much annoying to have to always open a specific browser whenever I simply have to adjust latency buffers.

Edit: I'm on Windows 10.

[CharlzS]

Am I the only one having troubles with MS Edge (which currently is my main browser)? I always get the "the browser is not supported" message. Luckily I still have Firefox, but it's pretty much annoying to have to always open a specific browser whenever I simply have to adjust latency buffers.

Edit: I'm on Windows 10.

Something to try: https://microsoftedge.microsoft.com/add ... pfmbiglpko

Start Pro Control and when you get the error change the Domain tab in the User Agent add-in to 'On' and select Mac OSX Safari.

[theMidiTamer]

Thanks, I tested all the User Agents in the list with no luck unfortunately.

[rwandering]

I don't know if this is still an issue for people, but I never had this problem. I just checked it now and it is working fine.

I'm using an 828es with 1.3.5+181 firmware, Edge 90.0.818.66.