Koala Bug?: In Loopy Pro, sending any midi without first opening the Koala interface crashes Koala

Bruques

Anybody come across this?

I have a Loopy Pro project,
some one-shots in Koala,
Linnstrument midi input,
Atom 2 for additional sequencing

I play/record some midi in to Atom 2 which goes onwards routed to Koala, and all is well
Until I save/close/come back later and reopen

Upon receiving any midi at all from any source, be it Atom or the Linnstrument or anything else Koala crashes, and needs reloading, no matter how many times I reload, it will continue to crash when receiving midi, unless/until I open the Koala interface first

Loopy Pro and Koala and Atom are all up to date with app store.
iOS 16.5
iPad Pro M2 11"

@elf_audio ?

wim

@Bruques said:
Anybody come across this?

I have a Loopy Pro project,
some one-shots in Koala,
Linnstrument midi input,
Atom 2 for additional sequencing
(incidentally I can't get the snaps to turn off or change in Koala, they make no difference, no matter the setting it's always actually straight 16ths hard quantizing, hence Atom 2 for sequencing - but that's an aside)
I play/record some midi in to Atom 2 which goes onwards routed to Koala, and all is well
Until I save/close/come back later and reopen

Upon receiving any midi at all from any source, be it Atom or the Linnstrument or anything else Koala crashes, and needs reloading, no matter how many times I reload, it will continue to crash when receiving midi, unless/until I open the Koala interface first

Loopy Pro and Koala and Atom are all up to date with app store.
iOS 16.5
iPad Pro M2 11"

I've seen something similar in Cubasis and Zenbeats as well. Koala wasn't crashing, but it was unresponsive until you open the interface at least once. I believe it's a Koala issue rather than anything with Loopy Pro, since the behavior is there in other hosts as well.

Nevertheless ... @Michael ?

wim

@Bruques - just to clarify, I assume you're talking about Koala as an AUv3, not IAA, correct?

Also ... posting on the Koala Discord server is likely to get more direct attention from the developer: https://discord.gg/85uPhgZf

Bruques

@wim said:

@Bruques said:
Anybody come across this?

I have a Loopy Pro project,
some one-shots in Koala,
Linnstrument midi input,
Atom 2 for additional sequencing
(incidentally I can't get the snaps to turn off or change in Koala, they make no difference, no matter the setting it's always actually straight 16ths hard quantizing, hence Atom 2 for sequencing - but that's an aside)
I play/record some midi in to Atom 2 which goes onwards routed to Koala, and all is well
Until I save/close/come back later and reopen

Upon receiving any midi at all from any source, be it Atom or the Linnstrument or anything else Koala crashes, and needs reloading, no matter how many times I reload, it will continue to crash when receiving midi, unless/until I open the Koala interface first

Loopy Pro and Koala and Atom are all up to date with app store.
iOS 16.5
iPad Pro M2 11"

I've seen something similar in Cubasis and Zenbeats as well. Koala wasn't crashing, but it was unresponsive until you open the interface at least once. I believe it's a Koala issue rather than anything with Loopy Pro, since the behavior is there in other hosts as well.

Nevertheless ... @Michael ?

Certainly seems related, if all is well once the interface is opened. As if the code assumes something standalone esque about the instantiating of the view before it moves on to other things, and if that doesn't happen, it errors deathly!

Bruques

@wim said:
@Bruques - just to clarify, I assume you're talking about Koala as an AUv3, not IAA, correct?

yes indeed, AUv3

Bruques

@wim said:
@Bruques - just to clarify, I assume you're talking about Koala as an AUv3, not IAA, correct?

Also ... posting on the Koala Discord server is likely to get more direct attention from the developer: https://discord.gg/85uPhgZf

I'm not really a discord user, but thank you!

wim

@Bruques said:

@wim said:
@Bruques - just to clarify, I assume you're talking about Koala as an AUv3, not IAA, correct?

Also ... posting on the Koala Discord server is likely to get more direct attention from the developer: https://discord.gg/85uPhgZf

I'm not really a discord user, but thank you!

Me either. It's a necessary evil though. 😂

Bruques

@wim said:

@Bruques said:

@wim said:
@Bruques - just to clarify, I assume you're talking about Koala as an AUv3, not IAA, correct?

Also ... posting on the Koala Discord server is likely to get more direct attention from the developer: https://discord.gg/85uPhgZf

I'm not really a discord user, but thank you!

Me either. It's a necessary evil though. 😂

yeah certainly feels that way a lot of the time.

but i'm mostly succeeding in my resisting of surveillance capitalism.
mostly.

espiegel123

@wim said:

@Bruques said:
Anybody come across this?

I have a Loopy Pro project,
some one-shots in Koala,
Linnstrument midi input,
Atom 2 for additional sequencing
(incidentally I can't get the snaps to turn off or change in Koala, they make no difference, no matter the setting it's always actually straight 16ths hard quantizing, hence Atom 2 for sequencing - but that's an aside)
I play/record some midi in to Atom 2 which goes onwards routed to Koala, and all is well
Until I save/close/come back later and reopen

Upon receiving any midi at all from any source, be it Atom or the Linnstrument or anything else Koala crashes, and needs reloading, no matter how many times I reload, it will continue to crash when receiving midi, unless/until I open the Koala interface first

Loopy Pro and Koala and Atom are all up to date with app store.
iOS 16.5
iPad Pro M2 11"

I've seen something similar in Cubasis and Zenbeats as well. Koala wasn't crashing, but it was unresponsive until you open the interface at least once. I believe it's a Koala issue rather than anything with Loopy Pro, since the behavior is there in other hosts as well.

Nevertheless ... @Michael ?

If Koala is crashing rather than Loopy, Marek would have to look into as the crash logs will be Koala's and won't have information the host could do much with.