![]() However, having to do that is an arbitrary change that occurred without any obvious reason, and if I was someone who wanted / needed to use wifi or BT I would be stuck with a completely dead setup that worked days before. In fact I advocate it - I have no use for wifi or BT when using these apps usually - I mostly use hardwired keyboards / connections only - so hardly ever any wifi MIDI or the like. Now, I don't mind switching off wifi to work with audio. This auto-fixed itself for a while after being reported to Steinberg - something about registering with AB from their end they said - but then has reappared - quite absent of any further changes to Cubasis. ![]() Cubasis to then lose its transport controls. Doing so however continues to cause, e.g. (MTDAW, Cubasis updated, Auria not updated).ģ.) There is a partial unsatisfactory workaround - one can switch off wifi. Does not matter whether it has been updated or not.Ģ.) The audio will not be routed to the AB chain - doesn't matter what app you route to - whether it has been updated or not. None of my iPads have cellular.ġ.) App willl start just fine, but AB will not switch back to the AB overview screen. I have the latest app update for every app that is available, Audiobus and 7.1.2. I have tried this on multiple iPads with different configurations (mini original, mini Retina, iPad 3), all running 7.1.2. iOS 8 can wait - this Anything in the input slot exhibits the following behavior if wifi is on: Soooo, - let's hope for a resolution for this within a small handful of days - if not hours. I DO expect what I have on iOS 7.1.2 to keep on running and that things that haven't been updated to not break - that is bizarre - and wrong. I don't expect to update to iOS 8 any time soon. That should be addressed very quickly - not just "eventually". Looking forward to this getting worked out - certainly - and - yes - maybe "in time" - BUT - the things that have broken on 7.1.2 have not been expected. in cases where they rely on the iPad as part of their music business.Īs it happened the person I referred to above's gig was postponed but they have upcoming events too and need answers. Many have stayed on iOS 7 in order to avoid such issues - esp. Similarly there was no hint that somehow iOS 7 would have developing issues even for apps not updated by the developers yet. That's certainly not been true for apps that updated in good time. with Audiobus on iOS 7 or that users on iOS 7.1.2 should not update such apps. There was no hint given that as apps updated for iOS 8 they would break things esp. The state of affairs needs addressing - pronto. I and others have been using them - and 7.1.2 just fine. Some apps that updated several weeks ago for iOS 8 / AB SDK 2.1 compatibility did not do this when downloaded and installed. If an app is now requiring iOS 8 only, then it should say so on the app store. Some people are relying on this to continue to work in a revenue generating environment and the app updates for iOS 8 should not have broken apps on 7.1.2. ![]() Said person uses an app that has not been updated for iOS 8 and that app is no longer playing nicely with AB on 7.1.2. They, like me and like many who read the strong suggestion from the AB team to wait on the upgrade to iOS 8 because of the lack of app updates being completed yet, have not updated to iOS 8 in order to avoid the apps they rely which have not been updated for iOS 8 compatibility no longer working. 32 Arpeggios included, unlimited useer arpeggios possible.At least one person I know of originally had a paying gig tonight in which they use iPads live on stage.Unique randomizer generates Arpeggios with 100% usability. ![]()
0 Comments
Leave a Reply. |