righty right Shayne, but there is the possibility (btw suggested by a member here > year back) to write a kind of 'middleware' driver to handle the communication when Scope runs in the WINE environment.
Given the fact that the GUI of SFP runs (as it's wxwidgets based it's not unlikely), it would be the most easy way imho.
For that purpose you have to write a low level driver according to the hardware layer of the OS, that's capable to map Windows audio calls (which the original Windows version of Sfp sees) to the respective Mac OSX parts.
With 'simple' audio interfaces this approach does indeed work - of course a complex system like Scope is much more demanding.
But it would under all circumstances require an Intel based Mac - and there is no such Mac with a PCI interface, so a Magma would be the only choice.
Certainly more expensive as the solution Huub and a few others found with the 2 machine approach.
In fact I would choose the latter any time, as I find a 'split machine' setup much more convenient. The hardware (except the Adat card) costs barely nothing.
so the a Scope under CrossoverMac (as the commercial version of WINE is called) is more a proof of concept. Crossover is very convenient, I really wouldn't want to bother with unix-ish config files to spare 50 bucks.
As far as I can tell it's an impressive product - I have a fairly exotic and complex developement system running under it as 'non-supported' software in 2 test licenses. Non-supported means it doesn't come with a readymade installer/pre-configuration like several 'major' Windows apps.
I can't remember which, but I have installed and used Windows audio apps under MacOSX and they worked perfectly except that they didn't output any sound. Pretty useless, but they didn't crash...
According to the documentation some basic communication between the Mac statndard sound driver and Windows multimedia drivers is implemented, but of course it fails if an application addresses it in a 'more smart' or optimized way.
cheers, Tom
