Welcome, Guest. Please login or register.

Author Topic: ASIO for all SBs!! (was does it has to be supported by hardware?)  (Read 2855 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show only replies by Jose
Pretty much that. I guess if it's supported by hardware in the soundcard performance will be better? Or I'm just talking nonsense.. :-?  

Merry Christmas by the way :-o  :-D  8-)

[EDIT] I found a way cool link with independent drivers for those who don't know. Check on my second post bellow.
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline Trev

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 1550
  • Country: 00
    • Show only replies by Trev
ASIO is a low latency (i.e. say goodbye to crackle and stutter), software interface similar to AHI and DirectSound. ASIO drivers allow ASIO clients (e.g. Steinberg Cubase) to interact with sound hardware. Check out http://www.steinberg.net for more information. If both your hardware and software support ASIO, then you'll probably get better results and a move advanced feature set (i.e. more than two channels) using ASIO instead of the operating system's default interface.

However, don't expect steller performance out of a consumer-level sound card. Products from DigiDesign, MOTU, Aardvark, Echo, and so on will give you the best results. But if you're using a PC and don't want to spend $1000 on a sound card, then get yourself a Sound Blaster Audigy 2 and a copy of Cubasis VST (or whatever your favorite multichannel recording software happens to be). It also pays to get a nice set of monitors. I like (and use) the Mackie HR824. I'd stay away from monitors that share an amp and must be sold as a matched pair.

Trev
 

Offline Trev

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 1550
  • Country: 00
    • Show only replies by Trev
Oops. Did I answer your question? I don't think I did. :-) The hardware is independent of the ASIO driver, but your hardware vendor (or some creative individual) needs to write the ASIO driver.

Trev
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show only replies by Jose
Thx.

So that support for ASIO2.0 at 24b 96khz on Audigy Platinum Ex, or the new Platinum Pro ONLY  is just software related?  Bastards 8-)
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline iamaboringperson

  • Hero Member
  • *****
  • Join Date: Jun 2002
  • Posts: 5744
    • Show only replies by iamaboringperson
Are you guys talking about the spy agency in Australia?
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show only replies by Jose
Ugh?  :-?

Here's a cool thing to watch!!!
I guess I allways end up making restless searches to my questions.... :-D

CHECK THIS OUT

Way cool ugh??
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline Trev

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 1550
  • Country: 00
    • Show only replies by Trev
Quote
So that support for ASIO2.0 at 24b 96khz on Audigy Platinum Ex, or the new Platinum Pro ONLY is just software related?


ASIO is just a software interface. While ASIO may support 96 KHz 24-bit sampling, the underlying hardware may not. Here are the layers:

1. Hardware
2a. Driver
2b. Operating System
3. Application Programming Interface
4. Application

A Sound Blaster Live! card will do 48 KHz 16-bit sampling at best. However, it's possible that the sound data will be upsampled somewhere along the line. Here's an example using the layers above:

1. 48 KHz 16-bit
2. 48 KHz 16-bit
3. 48 KHz 16-bit
4. 96 KHz 24-bit

In this example, the sound data is upsampled by the application. On playback, the sound data will be downsampled to a format supported by the hardware. A higher bit-depth should provide an increase in accuracy while editing a sample, and moving from a low bit-depth to a high bit-depth doesn't change the quality of the sample. Resampling the data at a different rate (in either direction) or moving to a lower bit-depth will usually result in distortion or loss of quality.

I don't know if this really making any sense. :-) Anyhow, before a sound card's ASIO driver can support a feature, the underlying hardware must support that feature. In some cases, an application can compensate for missing features by downsampling, downmixing, etc.

Trev
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show only replies by Jose
Hmm, to be honest not really ;-)
From what I've read since I posted this, ASIO is just a protocol kind of thing to bypass the operating system so that ASIO applicaions (hosts) can communicate with the hardware faster and have for example very low latency.
So in the above example you gave the layers would be Hardware > ASIO > Driver > Host software
Correct me if I'm wrong though, I like to know this kind of stuff.
The most interesting thing though is that some card makers make the more low end models with less features but just in software, and independent drivers like the one I posted above give the people with a simple soundblaster ASIO support wich is very helpfull.
They also expect to have an ASIO2.0 driver for the Audigy2 line. On the Audigy2 line of cards only the more expensive PlatinumEX and the New PlatinumPro have ASIO2.0 support.
In general these drivers are improved for musicians wich is way cool. They even exchange the back and front channels so that the AC97 codec is not used resulting in a better sound for the soundblaster and Audigy.
If you have one and do music, and haven't checked this, I suggest you try it out. Cool stuff.
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline Trev

  • Hero Member
  • *****
  • Join Date: May 2003
  • Posts: 1550
  • Country: 00
    • Show only replies by Trev
Quote
So in the above example you gave the layers would be Hardware > ASIO > Driver > Host software


Well, maybe. Some operating systems (like Windows NT/2000/XP) won't let you go directly from an API to hardware. There's usually something in between, which in most cases is the driver. It would really look more like this:

1. Hardware
2. Driver
3. ASIO
4. Application

. . . which is why I used 2a and 2b for the driver and the operating system.

Don't get too excited about using a Sound Blaster for multichannel recording and playback. With my Sound Blaster Live!, I have five usable inputs (line in 1, line in 2, and mic in), but the first two are bonded stereo channels--the left and right channels can't be controlled independently. The same goes for the outputs (front left/right and rear left/right). The newer cards may be a bit more flexible, but you're still going to have to deal with the Sound Blaster's crappy audio. Don't be fooled by the THX logo. :-) But if you're a musician on a budget, it's a great deal. And let's face it, a great musician can make just about anything sound good.

So, with ASIO, you're bypassing the operating system's audio interface and talking directly to the hardware driver. Now, I'm not an ASIO guru, so in operating systems like Windows NT/2000/XP, there may be an ASIO driver that sits below the OS layer and talks to the hardware using a pluggable driver interface. That makes sense for performance. . . . I guess it's time to read the manual. :-P

Trev
 

Offline iamaboringperson

  • Hero Member
  • *****
  • Join Date: Jun 2002
  • Posts: 5744
    • Show only replies by iamaboringperson
ASIO (ā'zĭō) n. Australian Security and Intelligence Organization. [initials]