On 6 Jun 2010 at 14:24, Christopher Smith wrote:

> On Sun Jun 6, at SundayJun 6 1:58 PM, David W. Fenton wrote:
> 
> > On 6 Jun 2010 at 10:21, Christopher Smith wrote:
> >
> >> I remember my first computer, an old Atari ST 8 bit 8 mHz  machine
> >> with 1 meg of RAM, always had flawless MIDI timing because  the
> >> operating system prioritised  MIDI message timing.
> >
> > Well, that wasn't a multi-tasking OS, no?
> 
> True enough, but no operating system at that time was multitasking 
> for micro (home) computers. It was a computer aimed directly at 
> electronic music, though, because the MIDI was built into the 
> hardware AND the operating system, and the OS gave first priority to 
> MIDI. Amazing for the time. I didn't even have a hard drive for the 
> first year I owned it, because I didn't need one.

None of that has anything to do with it. As a non-multi-tasking OS, a 
programmer could be sure that if he sent off a task to the CPU to be 
processed synchronously, nothing would interfere with it being run to 
completion.

In a multi-tasking OS, the programmer does not have that control -- 
the OS decides how to timeslice and hand out CPU cycles to competing 
applications.

> I have perhaps an incomplete understanding of OS architecture, but 
> shouldn't it be possible to time-stamp MIDI events incoming, so that 
> they are always recorded at the right time, and to give priority to 
> playback so that MIDI messages are sent as close to the proper time 
> as the message itself allows (roughly  1 ms)? 

OS processes and threads can be assigned priorities, but the OS has 
control over exactly what happens. If two threads of equal priority 
request CPU time, the OS has to decide between them. It may or may 
not reflect what *you'd* prefer.

> That's what the Atari 
> OS did. 

I don't really think it did at all. It was a matter of the fact that 
there were no processes competing for CPU time so that the programmer 
of the sequencer had full control of the process from beginning to 
end. 

> It seems that my computer (Mac) is always too busy doing 
> something else (internal housekeeping, I imagine) to worry about 
> proper MIDI timing. 

In general, that's a sign of inadequate memory for the number of apps 
being run. That is, paging in of and out to the swap file is going to 
bring everything else to a halt, but it's the highest priority of 
anything the OS is going to do because otherwise, apps would run out 
of memory.

> Or maybe that's just Finale. But I also get an 
> inordinate amount of slop with Cubase on Mac as well, both with 
> virtual instruments (yes, I know about latency) and with the same 
> external MIDI devices that had great (okay, not great, but 
> acceptable) timing with my Atari. But Finale is the worst I have ever 
> experienced.

The virtual instruments are likely the cause of the memory problems. 
I've never quite understood why people thought the trade-off between 
soft synths and hardware synths was a good thing. It always seemed to 
me that having a separate processor handling sound was a *good* 
thing, but that architecture never caught on for Macs, and has fallen 
out of use on Windows.

-- 
David W. Fenton                    http://dfenton.com
David Fenton Associates       http://dfenton.com/DFA/

_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale

Reply via email to