PacoCasanovasOld
Fractal Fanatic
Dear User, Dear FAS
Disclaimer: This is not a bitching and a whining thread - it's also not a thread about some one, who is new to DAWs and new to such products in general.
Cliff recently said, the mac driver was written by apple - sad but true, that's correct. Class compliant means - you put your device to a computer and in most cases it works without a custom driver because it uses resources/code form the operating system. On a WIN based system, this is not an easy task because class compliant USB 2.0 Audio is not supported directly - it will dedect a device but it would not loading the driver automatically - IMO a reason why there are specific ASIO drivers (regarding to the axefx II Manual) on a WIN system. On MAC instead most applications use core audio and core midi - which can either be connected with a class compliant driver or a custom made driver (as many pro audio manufacturer does for mac audio interfaces). Instead of the poor standard audio clock, they use the internal device audio clock, which is (hands down) much more stable than apples adoption ever will be!
To get the same great audio results on a MAC, we need the same "quality custom made drivers" as given to the WIN users.
ASIO is a multi-channel audio protocol, originally introduced by Steinberg (the company who wrote the Cubase DAW and also is responsible for the VST standard) - which is not a WIN system internal protocol such as "Direct Sound", which is not usefull for pro application needs or low latency performance. Class Compliant USB 2.0 Audio on a MAC has slightly better performance than Direct Sound on a WIN but it's not the superior solution for low latency performance on a mac, which can be reached with a custom driver application for Mac CoreAudio/MIDI!
Please make this possible - as many of the axefx user are Mac-user and we deserve the same performance as WIN users - neither Mac or WIN people should fighting each other here.
Love and Peace to the FAS-Community
Sincerely
Paco
Disclaimer: This is not a bitching and a whining thread - it's also not a thread about some one, who is new to DAWs and new to such products in general.
Cliff recently said, the mac driver was written by apple - sad but true, that's correct. Class compliant means - you put your device to a computer and in most cases it works without a custom driver because it uses resources/code form the operating system. On a WIN based system, this is not an easy task because class compliant USB 2.0 Audio is not supported directly - it will dedect a device but it would not loading the driver automatically - IMO a reason why there are specific ASIO drivers (regarding to the axefx II Manual) on a WIN system. On MAC instead most applications use core audio and core midi - which can either be connected with a class compliant driver or a custom made driver (as many pro audio manufacturer does for mac audio interfaces). Instead of the poor standard audio clock, they use the internal device audio clock, which is (hands down) much more stable than apples adoption ever will be!
To get the same great audio results on a MAC, we need the same "quality custom made drivers" as given to the WIN users.
ASIO is a multi-channel audio protocol, originally introduced by Steinberg (the company who wrote the Cubase DAW and also is responsible for the VST standard) - which is not a WIN system internal protocol such as "Direct Sound", which is not usefull for pro application needs or low latency performance. Class Compliant USB 2.0 Audio on a MAC has slightly better performance than Direct Sound on a WIN but it's not the superior solution for low latency performance on a mac, which can be reached with a custom driver application for Mac CoreAudio/MIDI!
Please make this possible - as many of the axefx user are Mac-user and we deserve the same performance as WIN users - neither Mac or WIN people should fighting each other here.
Love and Peace to the FAS-Community
Sincerely
Paco
Last edited:
