Piet Keizer
Registered
Now I know why Steinberg's Cubase won't run under classic and why it probably won't in the forseeable future...
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Cubase users: OS X forces Classic to use virtual memory!
- Thread starter Piet Keizer
- Start date
We don't like Ads much either, but they do help cover the costs of running the site. Please consider turning off your ad blocker. Thank you.
Well, one would not want to run a realtime application under Classic, anyway. The reason is simple: it is my understanding that Classic is running as a non-realtime process under X, and will be pre-empted by the X scheduler.
The good news is that Mach 3 did have support for realtime (read: non-preemptive) processes, but I don't know whether Darwin is able to use or implements such support at this time. Co-operative multithreading on the system level is much more suitable for realtime applications, exactly because one thread can easily hog the system.
Regards,
Marino Ladavac
The good news is that Mach 3 did have support for realtime (read: non-preemptive) processes, but I don't know whether Darwin is able to use or implements such support at this time. Co-operative multithreading on the system level is much more suitable for realtime applications, exactly because one thread can easily hog the system.
Regards,
Marino Ladavac
Piet Keizer
Registered
Are you saying that realtime applications like Cubase might not work well under OS X in the near future?
How about all the other multimedia support? Isn't Quicktime a realtime application?
Or is there anything I don't undestand about your post?
How about all the other multimedia support? Isn't Quicktime a realtime application?
Or is there anything I don't undestand about your post?
Well, what I am saying might as well be FUD as far as Darwin/MacOS X is concerned, because the foundation OS (Mach 3) was engineered with realtime support; the point is that I do not know whether this is currently used by the current implementation of Darwin/Mac OS X.
However, traditional unices are performing rather poorly in realtime aspects (Darwin is not a traditional unix in this sense), so I would not be shocked if there were some temporary problems caused by the BSD layer.
This should not be quite noticeable in Quicktime, apart from occasional frame drop: sound sync, if buffered, is easy; it's only 150 KBps, or thereabouts. 24 channel realtime harddisk recording with realtime effects is not as easy because sound discontinuities are much more noticeable than dropped video frames.
So, Cubase would have problems in a traditional unix, or at least most of them (FreeBSD stable would be quite useless, and Linux should not fare any better---Solaris might, though); whether it will have problems in Mac OS X remains to be seen (but it really should not, especially once DVD playback is there to prove that realtime aspects of Mac OS X are acceptable).
However, traditional unices are performing rather poorly in realtime aspects (Darwin is not a traditional unix in this sense), so I would not be shocked if there were some temporary problems caused by the BSD layer.
This should not be quite noticeable in Quicktime, apart from occasional frame drop: sound sync, if buffered, is easy; it's only 150 KBps, or thereabouts. 24 channel realtime harddisk recording with realtime effects is not as easy because sound discontinuities are much more noticeable than dropped video frames.
So, Cubase would have problems in a traditional unix, or at least most of them (FreeBSD stable would be quite useless, and Linux should not fare any better---Solaris might, though); whether it will have problems in Mac OS X remains to be seen (but it really should not, especially once DVD playback is there to prove that realtime aspects of Mac OS X are acceptable).