Let's apply some logic:
* The 44 works in a different (Windoze) machine: Conclusion, it's a good unit.
Yes the Delta 44 works fine on Windoze
* In the QS, the Delta Control Panel loads and displays but no sound.
You said you sometimes see indications of audio in the Delta display. Does that look like accurate audio or just random noise?
I don't see that you've indicated which DAW or such you're trying to use. Which is it?
Hi GaryN, thanks for your input and sharing of your experience with Delta Gear - So the indications of audio i have seen in the Delta display are definitely actual audio and not just random noise. As to the DAW - I have been using Cubase (from Diehard's instant DAW) and Recycle v2.0.
My $$ is on the ASIO, or lack of it, or incorrectness of it. Why?
* In order for the Delta to work here, you must have the Delta ASIO driver in the DAW's ASIO folder.
* You should NOT have the Sound Manager ASIO driver in there too. There will be issues because Sound Manager and whatever DAW will bump heads and even crash the computer. There's no good reason to route your DAW's output thru the Sound Manager anyway.
Ok thanks for explaining that.
I have placed the Delta ASIO driver in the DAW (Cubase) ASIO folder and Recycle ASIO folder. I will try this again and make sure that the Sound Manager drivers are not in the same folders.
So, assuming that you (hopefully) got the Delta 44 ASIO along with the Control Panel and Extension, make sure that ASIO is where it's supposed to be in the DAW folder.
When you mention the 'Control panel' above - are you just referring to the Delta Control Panel or OS9 Control Panel?
I'm referring to the Delta panel. Since it IS showing the audio yet nothing is making it out of the breakout there may be a different issue.
This thread has been going 'round and 'round about multiple ASIO drivers. That can be and sometimes IS a real problem.
The farther we go however, the more I'm leaning towards the
aftermarket CPU upgrade problem.ASIO = "Audio Streaming Input Output"
The entire reason for its existence is to route audio
around instead of
through the multiple "layers" of hardware that would normally have to pass it thru. It is used to improve timing by keeping the CPU from having to spend time just shuttling audio bits around.
ASIO was originally written for older Windoze systems that were notorious for having horrible audio handling. It's not too much to say it was what made decent audio even possible on PC's. Because the old Mac OS had no pre-emptive multitasking, it too was lousy at handling audio so Steinberg wrote an SDK to help folks to adapt ASIO to the Mac as well. A couple of issues here:
* It was necessary for manufacturers of audio interfaces to write their own ASIO drivers. Some were better at it than others.
* An immediate problem developed in that this was around the time of OS8 and 9, which were near or at EOL while the digital interface "world" was really just getting into gear. Because of that, ASIO 1 soon became ASIO 2 leaving Mac OS9 in the dust. In fact, ALL old-Mac-compatible ASIO SDK updates ended with ASIO 2.3. So, there are multiple versions floating around, all poorly or UN-labeled and little or NO documentation.
* A big part of the problem was/is that Apple, with their usual finesse, said "Steinberg? Who needs Steinberg"? They then developed
Core Audio for OSX and never looked back. Core Audio does everything ASIO does and arguably does it better on the Macs it was specifically written for.
SO…… WhereTF is he going with this? Easy: ASIO is a set of instructions for the computer being used and is tailored to that OS and hardware.
IF you change the CPU, you have to make small tweaks in the ASIO instruction set to accommodate the different characteristics of the new CPU. ASIO is all about data handling and timing so it needs to "know" what it's working with.
* My Deltas worked fine in my MDD until I installed the Sonnet CPU. Then, they stopped dead.
** I tried everything known to myself and anyone who would listen without success.
*** It was
only when I got lucky and reached someone still working at Sonnet who had been there in "the old days" that the solution arrived. What was it, you say?
It was a customized ASIO driver that Sonnet had developed when they started getting complaints that people's interfaces stopped working when they installed Sonnet CPU's. He had kept it at home and was kind enough to send it to me. Nobody else at Sonnet even had a clue about it… as I said,
I got lucky.I should mention that I didn't then and still don't remember having this issue with my old 500Mhz Sonnet in my G3 Desktop. That's partly what helped make me crazy when I had the problem in the MDD… I just never suspected the ASIO driver.
I of course made multiple copies of that damn replacement driver and stored them in different places.
****
I suspect that you just might have the same problem with your OWC CPU.I have no idea
exactly what the hiccup is. Since the objective of ASIO is to go
around the CPU, you would think it shouldn't matter. However, there is a whole bunch of data handling that goes on right next to and around the CPU, and since most/all of these 3rd-party upgrades are basically the same family of IBM 7400-series chips overclocked to Warp speeds, I can imagine the ASIO routines expecting certain timings, buffering and whatever based on the chip identity and so being literally out-of-sync with the new CPU speed.
IF this is all correct, I have no good idea where to go or how to fix it. You can find current ASIO support for Windoze - there's even a site
asio4all.org to customize your "new" Windoze driver, but not so much for our poor old "obsolete" Macs. If you have an original QS CPU, I would say put it back and see if everything starts working. If you don't, I'll dig out one of my old Delta 44 ASIO drivers that worked with my old Sonnet and post it for you to try. It can't hurt and maybe you'll get lucky too.
Meanwhile, I'll hope I'm completely out to lunch here, that there's a simple so-far-overlooked fix and this is all just a typing exercise…
