This is going from bad to worse.
IAA instrument tracks always echo in-coming midi on channel 1, regardless of send channel and midi thru state… Things played via the virtual keyboard, is always played on channel 1… If you set output target and channel, it will play to that… and channel 1.
I wanted to try this with Audiobus, but Cubasis almost consistently crashed when launched from Audiobus (even after iPad re-boot), so I gave up.
Playing back MIDI on an IAA track, also always plays on channel one + additionally any channel that you specify as output in the midi routing. Not useful for multitimbral IAA instruments. As a workaround, you can put your midi on a non-IAA midi track, that you route to the synth that’s hooked up to the IAA track. However, you now have no way of freezing or recording this stuff that I could find.
Also on freezing, you have to know (by magic) that freezing only works properly with a buffer-size of 256, as there is not warning when you freeze a track with a different buffer size setting. Only the timing of your results will be off.
I’ve read that some of these things work like they do “By Design”, but I can’t help feeling that whomever designed/implemented them is either out of their depth or are not given the time & resources they need to make each feature.
I purchased Cubasis and enthusiastically read the documentation front to back before getting started. Once I did get started however, Cubasis seemed to blow up in my face, every step I took. I’m sorry to be so negative, I really wanted to fall in love with Cubasis. Though I knew that the feature set was limited, the virtual instruments, mixer and effects mostly on the cheap side, I purchased it because I believed Steinbergs pedigree would shine through in the foundation of the package.
At this point Cubasis is really overprised for what it is feature wise (compare it to Cubase Elements that’s only 2x the price) and is obviously not ready for the road, even a few years after release. I’m not sure what Stenbergs plan is with Cubasis, but you get the feeling that it’s either:
A. We are just dipping our toes in IOS, to make sure we gain some knowledge and have a leg up if IOS takes off as a music platform. All the while, we are letting the consumers pay for the party. This would obviously not be cool.
B. Give users early access, while we spend the next 3-4 years getting the application to an acceptable state. This would be ok, but then I think you need to state that clearly and adopt a much more open door development approach + give a clear roadmap and let users know what and when they can expect for their money.
For now, this will be my first attempt at an app refund ever. I hope you will soon turn the boat around and I’ll be the first to jump back on.
Moving forward, I’d like to encourage you to focus on fixing the foundation and not on new features or IAP.