i still run cubase on the atari st. my favorite over-all cubase is vst24, but the atari seems to handle several complex hardware midi tracks better than any midi sequencer i have ever used.
don’t get me wrong, these days i mostly run se on pc, and le4 on mac, but i still feel that other than the atari over heating after a while, it is the most solid and predictable version of cubase or any other midi sequencer.
Er… You did what?!? There aren’t many Atari Falcons left (less in a working state). They are sought after by collectors and members of the Atari community. Typical price on eBay for a ‘stock’ machine is £250 upwards - I’ve seen them go for nearly double that with the right spec though…
A BIG shame.
So what are the chances of a sudo port / re-imagined version of the Atari Cubase for iOS ? 
Virtually none. The reason Cubase worked so well on the Atari was that is was designed to work tight with the hardware. People still claim the midi timing of the Atari has never been beaten by modern technology. This isn’t as surprising as it first seems. Modern OS’s have to share hardware with many processes via an abstraction layer. So in a midi application where timing is critical it is possible for any running process to implicitly introduce unpredictable lag - admittedly this lag should be insignificant, but it can sometimes be noticed especially with a system that has many processes potentially running at once.
With the Atari running in standard single tasking TOS, you run Cubase in the knowledge the whole machine is dedicated to running just that one application - just one of the reasons Atari hardware offered a near flawless midi sequencing environment.
iOS development framework won’t allow developers anywhere near the hardware and multitasking on iOS will almost definitely interfere with midi timing to and from external devices. Plus you’ll need some kind of midi interface to do it properly IMHO.
Well by sudo port I just ment the kind of app it was … Midi only pre audio workhorse of a sequencer .
As far as timing goes I can see the argument , but Roger Linn talked about how simple it is to get right not too long back on his page . I would not see why a 1ghz duel core cpu that only had to do midi and sysex data > core midi i/o , GUI , and maybe background Wifi could not be accomplished since there are no audio drivers , plugins , runtimes and major os services to tax it .The iPad is fairly efficient . Oh well I guess a useful & nostalgic trip may not be in the cards .
When I got my 1040ST I started out with Pro 24 then graduated to Cubase when it came out. Had the SMP24 early on, I think pre Cubase because I had to upgrade the PROM when I got Cubase or a later version of Cubase. Sold the Atari about 10 years ago but still have the SMP24 collecting dust in a corner.
How can todays kids understand that my buddies were utmost envious after I had bought a 30 MB Megafile HD for a ridiculous price of 500 €? The thing was almost as big as a portable record player, considerably loud & the reorganisation of a database (Besides storing backups from Cubase projects Id been using Chessbase managing 40.000 chessgames! at the time 
.) took all night long.
Me too! Good ole memories of the crash down bombs…
Two things that used to drive me nut’s back in the good old days…
The bombs and Error 144… Reboot. hahaha, Atari and bloody Ensoniq
Haha! Error 129 on the ASR-10. Damn that message! 
Oh, I see … maybe not only for the ASR 
Obsolete Synthesis
Love the name!
16 voice generator received unknown message
17 voice list corrupt
32 UART overrun
49 parser bad parameter type
56 memory allocation error GETBLOCK
57 memory allocation error FREEBLOCK
63 RAM error (main ram)
64 SCSI not connected
128 BUS error
129 odd address error
130 divide by zero error
131 illegal instruction error
132 CHK instruction error
133 TRAPV instruction error
134 privelege violation
135 TRACE error
136 line 1010 emulation error
137 line 1111 emulation error
138 spurious interrupt error
139 unused vector error
144 out of system buffers error
145 unknown sampling interrupt
192 unknown sequencer event
194 no more sequencer buffers.
Error 129… Odd Address Error, you got to love programmers really. Most of them are equally unintelligible untill at least three pints have been consumed.
Yeah! And then they reach a critical mass of beer in their bellies and they start to giggle and get neurotically friendly that’s kinda creepy. Might be some chemical reaction with the Jolt Cola they’ve been consuming during the day?
real person >>> <<< programmer on joltbeer
Thats when you get hit with a… 134 privelege violation.
I also have a dead Atari, monitor and 20MB hard disk languishing in a cupboard.
It appears that Barrie is still managing to make coin from Atari + Cubase; check this for Atari technoporn if you will:
This guy sold me a good few power supplies and upgraded my RAM to 2.5 MB.
I used to do the thing with Turbo RAMDisk - Load Cubase once at the start of the day then warm-start if it crashed. Imagine that - a system that can preserve its memory contents through a soft reboot. Losing that facility was not progress.
Mmmm, that rackmount Falcon is tempting…and I’d love to revisit my HiSoft Basic programs one more time
I had to comment. Aren’t those days just memorable. I too have my 1040STE and I’m not parting with it. Unfortunately my wife threw out my 520st! Pissed me off!
But I recall DR T’s Omega. I even wrote Steinberg a suggestion to use velocity stems that Dr. T’s Tiger used. I still hate editing stacked velocity bars in cubase. Man why won’t steinberg listen to great ideas. This was a great feature in Omega.
But those were such great times. I remember buying a falcon because it did direct to disk recording. But the Mac and PC were already ahead by the time it came out. Too bad for Atari. They should have just began making PC clones.
That’s unacceptable! Throw out your wife! 
i agree and sue her
A bearded lady, I’ve heard …
Still running my Atari rig… works great