studiomux 5 beta

Thanks Pascal! Great to see some of the inner workings & complexities of this beast of an app. I have always considered it to be practicaly a work of majic…I am always amazed that it works! Easily the most used, & useful app that i have…with AUM coming in a close second. Fantastic work! Thank You! Must be getting close to release? Have you tested with os15 Beta yet?

Again, many thanks for your perseverence & tenacity in re-writting the app for us. It really is apreciated. :smile:

Hi,

Not yet, just installing it, unfortunately as Developer an iOS update usually also requires to update OSX and Xcode (both beta), which can pretty nasty.

Just wrote some sentences to the upcoming release:

AUM is the gold standard… i hope studiomux will become as reliable/stable as AUM… you may have noticed, that we also adopt some gui parts of AUM, just becaus we didn’t know how to do better.

Best

1 Like

AUM is undoubtedly the gold standard for functionality & reliability, everything I do on ios goes through it, but without Studiomux, I wouldn’t be able to get it out into an external DAW, (Ableton) without a lot of messing about. I guess that makes Studiomux the most vital component in this particular work flow.
Untill os 14 screwed it up, Studiomux was very stable & reliable, crashes were rare. I am sure Smux 5 can achieve the same level of reliability again, looking forward to the release…cheers…Mark…

1 Like

Another AU that crashes while loading for me: Stratosphere Cloud Reverb

Hi Pascal,

Any news on Windows? In my case, audio stopped working since version 5.091.

Thanks in advance.

Hey evereone! Joined beta and tested Studiomux 5 beta on Win 10 x64, Bitwig. I got evething working, but no audio signal from VST:
moog

btw is there any way to route midi from Bitwig into iPhone 7 in my case?

Will appreciate all advices on how to make it run in Bitwig, win 10

Tested also StudiomixEffect vst, I could send midi data using it from Bitwig. I hear the voice on iPhone but still could not route that signal back into DAW :confused:

Studuomux 5 released here in the U.K. Just gave it a quick spin. Working great, feels nice & stable.(Win 10, Ableton 11)

     Cograts @Pascal & the team. It Lives!
1 Like

Glad to hear that! Hope Studiomux could be used in Bitwig also!

Hi,

we successively released the app for devices running iOS 14 and above.

It crashes (does not load properly) here too. But for hell hell we cannot identify the root of the issue… But we are working on it,

Best

Maybe Blue Mangoo can shed some light?

Any luck figuring out why Timeless 3 isn’t working?

Hi,

so… we found the issue, that caused many AUv3 effects not to load. It will be fixed in v. 5.115.

Update: I tested the latest beta v. 5.115 on several devices and for the first time i encountered an issue many of you reported before:

After updating from 5.114 to 5.115 it seems like parts of the old binary to remain on the device and the former issues remain. I had to delete the old App and reinstall the Update to really get it. This honestly exceeds my horizon…

Pascal

1 Like

Does one only need to remove the app on the iOS side or on the desktop side as well?

The new version fixes a lot of issues. I am happy to report that all the AUv3 on the iPad that weren’t working before are working now.

A couple of things:

  • in the iOS app, it feels like there needs to be a ‘clear session’ or ‘new session’ command in the Files popup so that you can create a new session from scratch if you have a session already open.
  • I don’t know if this is expected, but on the Mac side (at least in Ableton), making any change in the Ableton audio preferences (such as adjusting the buffer size) causes the Mac plugin to lose its send receive settings

Hey, Pascal! Will check it out in Bitwig today, thanks!

I’ve tested new version, but still no sound in Bitwig 4.0.1 on Win10 x64 :confused:

This is how SM vst looks like in my case in Bitwig:

It seems to me that eveything is ok here.

This is how it looks on mobile:

Should I try to route audio using Audiobus or AUM?

joined the beta, and now don’t get a sound) Release version was buggy, but at least I could record something from Ipad.

But what I’ve noticed is that versions of the latest beta servers don’t match - studiomux_5.114.dmg for mac but 5.099 for windows, and I’m using windows pc. Do they have to match?

UPD: reinstalled the app and server - same results. Studiomux shows that it’s connected, vst3 plugin shows that both device and channel are set, but no audio.

Seconding the above that Win10(x64) with server version 5.099 and beta app version 5.116 does not forward audio to the daw. Additionally the VST3i is highly unstable in reaper. Behavior changes session to session however I have noticed the following:

Adding plugins on tracks will crash Reaper v6.35. This is pretty consistent unless you set the IAA/AU outputs into channels before attempting to load the plugin.

Changing the channel of output (Ex. Bremen) in the IOS App wile connected will crash reaper.

Midi seems to work well!

1 Like

A little update. It seems like Apps like Animoog work without issue for audio delivery. The challenge seems to come from using AUM as an input source. Hooking up IAA AUM port 1 to the studiomux input results in no sound. In AUM we are presented with IAA audio bus 1 in the output channel. We are also presented with buttons for record play and reset. None of which are responsive. If a second device like Animoog is hooked up, both tracks peak and present horrible noise. Muting the AUM channel and then turning back on monitoring in studiomux allows for the Animoog channel to come through correctly.

1 Like

One last update for the day.

This looks like when you monitor the incoming track in Reaper, as well as arm the track the instrument amplifies itself peaks and distorts. This is remedied by turning off one of the monitoring options.

With regards to the plugin. It seems that in reaper it presents a mixdown of all the audio channels to the plugin with the second available audio channel (i.e. not bremen, but the next place name).

It should be noted that this behavior seems to be limited to Reaper. Ableton seems to handle all the plugins properly.