Audiobus: Use your music apps together.
What is Audiobus? — Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.
Download on the App StoreAudiobus is the app that makes the rest of your setup better.
Mozaic (as destination for external MIDI) crashes in Loopy Pro
I found strange behaviour in LP 1.1.8. Could I ask anybody for trying this scenario, please?
Create new LP project
Open mixer
Add external MIDI device (AKAI LPK25 in my case)
Add Mozaic
Add Mozaic to the external MIDI channel as Destination
Close LP, open LP
You should see exclamation icons instead of the standard Mozaic icons like I do.
Mozaic works normally after reloading.
Comments
What do you mean "close lp"?Do you mean force it to quit or do you mean switch to another app and back?
If the latter, is Play in Background on or off in Loopy's System Settings panel?
Does it only happen if Mozaic is a destination for hardware? What if you add Virtual Midi In as the midi input?
Sorry for "Windows" terminology. I meant force LP to quit.
Yes, only for hardware input. I tried Mozaic with Virtual MIDI and it was OK.
@filo01 - I've tried what you said with an external NanoKEY Studio and can't reproduce that problem. I tried by switching away from Loopy with and without Play in Background on. Then I tried force-closing Loopy both with and without background on. No crashes of Mozaic.
Do you have a script loaded in Mozaic in your tests?
Have you tried restarting your device?
Are any other hosts running with Mozaic at the same time?
Yes, but it is default script "Welcome to Mozaic". I also tried my script with the same result.
Yes. I even tried to create project as I described above, force LP to quit, shutdown and start iPad and start LP.
No, I don't have any other host except Loopy Pro.
Sorry, I don't know what to say. I can't reproduce that issue and can't recall anyone else having reported something like that.
Is Play in Background enabled in Loopy Pro? It shouldn't matter though.
Pinging @Michael ...
What happens if you save your project before force-quitting?
What OS version are you running?
@wim Thank you. (Yes, Play in Background is enabled)
Result is the same after reopening LP - Mozaic crashed
16.7 (20H19)
I did another test.
At first I saved project XX which was created as I described in my 1st post above (External MIDI+Mozaic linked as destination) Then I duplicated this project and saved it. Then I forced LP to quit and started it again. It was reopened with duplicated project and Mozaic crashed. Then I loaded first project XX and Mozaic was correctly initialized.
Are you creating the project from the default Loopy Pro template?
Do you have any bindings for the LPK25? Any Global Profile mappings? Any Project Wide Follow Actions?
Sorry, I'm just fishing for anything that might be different besides the hardware from what I'm testing.
Yes
I don't think so. I don't even know what is it.
I'm using LP as simple as possible, just for hosting AU.
I appreciate it.
Do you have any other external controller you could try in place of the LPK?
Holy cow, thank you, you are right!
I absolutely did not expect there to be a problem in the hardware and it really is.
I have also M-Vave SMK25 keys and there is no Mozaic issue with the same scenario.
I also tried AKAI and MVave together as MIDI source to Mozaic and it crashed again.
OK, but what now? I like my AKAI much more than MVave ...
@filo01 : If you save the project before force-quitting and then launch Loopy Pro and then re-open the project, does it open correctly?
If you look in the Settings app in Privacy&Security->Analytics and Improvements -> Analytics Data are there any logs with Mozaic in the name?
This issue sounds like something @brambos would need to look into.
@filo01 : launch a midi monitor with your Akai connected and see if it is sending some midi .
Also, in Control Settings, find your device and turn off feedback enabled and toggle the timestamps setting and see if that makes a difference.
It would be very interesting to see what's coming from that LPK 25. Streambyter is good for this kind of thing because it reports some things that other apps such as MidiSpy don't.
I thought maybe it the cause could be a flood of midi clock messages but couldn't find out whether or not the LPK outputs clock when set to Internal clock for it's arp. I know my NanoKEY Studio does, so I set it up to send clock. That didn't cause any issues though.
No, it doesn't
Yes. I repeated my scenario and latest Mozaic log is in the attachment.
I launched MIDI sniffer and then launched LP with crashed Mozaic. Log from MIDI sniffer is in the attachment.
I switched Feedback to Off and toggle timestamps as well - no difference
Thank you @espiegel123 for your help.
Sorry, I was not able to get any data from standalone Stream Byter. It worked as AU in LP but its MIDI monitor is not armed during launch of LP.
Do you have AUM, AudioBus, or any other host you could try instead, to narrow down whether this is a Mozaic issue, or something related to Loopy Pro specifically.
Part from Mozaic log linked above.
MALLOC_TINY 117e00000-117f00000 [ 1024K] rw-\/rwx SM=PRV ",
"exception" : {"codes":"0x0000000000000002, 0x0000000117bb0000","rawCodes":[2,4693098496],"type":"EXC_BAD_ACCESS","signal":"SIGBUS","subtype":"KERN_PROTECTION_FAILURE at 0x0000000117bb0000"},
"termination" : {"flags":0,"code":10,"namespace":"SIGNAL","indicator":"Bus error: 10","byProc":"exc handler","byPid":630},
No, unfortunately not.
Here's something you could try:
Route the LPK to Streambyter AUv3 in Loopy Pro
Route Streambyter to Mozaic
Install the following code in Streambyter to block Sysex:
The text file you attached above had only a couple of Sysex messages. This should block those.
@wim I have no idea what this magic equation means but you win because it works now.
Thank you!
I think this is a nice workaround but it would be also nice to know what is a real source of this issue...
@filo01 : does the Akai constantly send this out? Look in streambyter’s midi monitor?
I am puzzled about how it knows to send that message when loopy launches.
It basically says to block any midi message received that starts with F0 in hexadecimal. Sysex messages start with F0 and end with F7. The contents in-between are the actual message. I have no idea what this message means but it's probably just a product identifier.
So, now we know that the sysex message is the culprit. But we don't know for sure whether Loopy is crashing the plugin as it passes it along while Mozaic is reloading or if Mozaic itself has a problem with that message. I suspect Loopy is starting to feed the message too soon before Mozaic is fully initialized, but that's just a guess.
It'd be easier if I had the LPK to test with or you had another host to try, but as the sysex is known, I may be able to imitate it in another host.
Yes. It's not a good workaround and shouldn't be needed. I'm sure either developer will want to fix it once it's narrowed down.
Pinging @Michael and @brambos in case either happens to have an LPK 25 they can test with.
No luck. I set up to send the same sysex message on project load. I couldn't reproduce a mozaic crash.
Sorry, I'm all outta ideas.
@brambos a crash log is attached to a messsge up-thread that may provide clues
https://forum.audiob.us/discussion/comment/1264652/#Comment_1264652
I will have a look. But I don’t have that particular controller, so testing will be a challenge.
I don’t see anything odd in the two sysex messages in the log above..
Do you mean periodically? From what I have seen in MIDI sniffer, that 2 sysex commands was sent just once during LP launch.
I would like to do that but my standalone StreamByter doesn't show any MIDI commands in its internal MIDI monitor and I don't see any "Options" or "Settings" where I can set LPK25 as MIDI source.
I found this in SB manual "If you need to process hardware, bluetooth or network MIDI, then you will need a routing app like MidiFire to interconnect (although in this case MidiFire has the StreamByter module built in).". As a beginner I'm not sure if it is important for my case or not.
.
Could this SysEx message be related to LP's built-in support for certain controllers? Does LP send a query ("who are you") message to the LPK25, triggering its reply? And maybe LP is wrongly forwarding this internal message to Mozaic.