The only other thing to mention is I have the 2Tb and therefore 16Gb memory verion of the iPad Pro M1. So, that may have nothing to do with the Audio Unit not loading problem, I don’t know. In fact, the blank rectangle is accompanied by a slow deliberate movement to the left, of the Audio Units list moving itself upward through the alphabetical list of AU’s, until it gets the (already highlighted) iSEM entry into view!Ī bit spooky, but I assume it’s the Apple ‘learning’ thing, same as GarageBand makes two copies of files I save, because I demonstrated my habit of doing that to it I guess. Now, on Cubasis 3.4.1, that doesn’t happen - now it comes up with the ‘Oxygene IV’ patch. What’s weird is that when you install a fresh instance of iSEM, it always comes up with ‘xtranasty’ as the sound patch. That brings me to another symptom - Audio Units are always insulated form one another, they never interact, unless like Fabfilter ProQ3 it’s intended to be aware of other instances in the same song project in that DAW. On iSEM, this is ‘Oxygene IV’ it so happens. I know 40 tracks seems a lot, I sort of use it as a template type thing, I put my fave synths in, and have typical sounds use, selected on them. It stands out only because, Cubasis 3 has improved so much in terms of reliability, for me at least. A problem ought to be repeatable if the software is working well (you know whatI mean!).īut, I know nothing of these things. The troubling thing is the sporadic nature of it - this suggests to me, it’s a programming thing. I gave it a minute, then re-invoked Cub3.4.1 but again, although the iSEM track appeared, the sound would not play and a blank space appeared when I tapped on the synth icon to the left of the track. So I copied the MIDI block to the ‘working’ iSEM track, and played around a bit, and then swiped the whole app away. I tried twice to ADD an entirely new track with iSEM in it - the first time, a failure, same blank rectangle, but the second times, success. I copied the track altogether, and the big blank rectangle was still all that appeared when I tapped the synth icon, and even with ‘solo’ on, no sound came out. So I returned to press on the iSEM synth issue. I turned solo off and on again, something like that. I had a few tries at it, and it eventually did load. I went through all the other instruments - Moog, Micrologue, Hammerhead, everything else seemed to work, except Poison 202, another excellent instrument, and it wouldn’t load at first. I hit on the ‘iSEM’ icon to the left of the track, and a big empty rectangle appeared, where normally the image of the white fascia of the iSEM synth would be. It made no sound when I played the track, there being some MIDI data already recorded. I loaded this 40-track project up, after updating to Cub3.4.1 and dabbled with a few synths, this being the first one. The fault is that iSEM synth by Oberheim was in a project. My former device was iPad Pro 2.īut I did use Cub 3.4 on this M1 ipad just fine. I put this down primarily to the new device I have, being M1 and seriously using multiple cores. Earlier versions, I had to make the ‘multi-core’ function turn off to stop crackling, and DSP rocketing up - now it’s the other way around I think, now I MUST enable multi-core. It’s 3.4.1 that’s the first cause of this issue. It works really well, and two weeks ago it was all fine. It is 3.4.1 and it’s on my freshly-acquired (used) iPad Pro M1. The latest Cub3 version, I updated after a couple of days. If I just say ‘ASIO4ALL’ those in the know will understand! It’s come on leaps and bounds and I take to it much better than the Cubase product (v9.5 I had on a PC), I want my problems to be music problems. So in general I really appreciate Cubasis 3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |