hdx aaxdsp is dying

[TNM]

Originally Posted by Emcha_audio

Vi works on a different process when using HDX, the Buffer of the HDX is already fixed and independent of the Software buffer (from what I undertand) The plugin dsp processing is done on the card itself and doesn't need Software buffer size. So setting a higher buffer count for vi use would not affect the dsp processing as far as I know of.

The Audio signal has to be converted from Analogue to digital (numeric) to be able to be processed by the chip, therefore EVERY system always process the audio Post conversion, even the Appolo system.



Autotune has a live option that is light on latency and can be used natively quite nicely.

you are misunderstanding...

HDX still has a selectable buffer that affects the latency of playing native VI's live..

I am asking how the performance of that is.. is 64 usable? Any idea of the actual latency to native plugins? In this case it's the output latency that matters, when playing VI's. My apollo is very low even at 128 sample, 3.5ms output latency (the only thing that matters for VI's is output latency), so it takes just 3.5ms from me hitting a key to hearing the sound.

Pro tools using core audio, unlike all other daws i have used, suffers horrendous performance losses under 128 buffer at 48k and 256 buffer at 96k.. I am wondering how the HDX driver performs in these situations.. Of course i realise whatever buffer i choose has nothing to do with the latency of the DSP plugins.. I am talking about native here, as i would still use a lot of that with HDX (probably another reason I need 2 cards, for the voice count).

[TNM]

Originally Posted by ejsongs

Anyone else using brainworx g console and sknote api?

Wasn’t aware of sknote api. I have distro and brainworx n.

Sknote stuff is good. Only thing I didn't like was their EMT250 emu.. not at all.. but that's not dsp anyway..nor even aax native..

their dynamics stuff is very very good.

Also they have a native spring reverb that has gone aax native recently and is fantastic.. called necklace i think.

I have the brainworx neve and love it but the ssl is well on my list.. top plugins.

[Carl Lie]

Originally Posted by TNM

you are misunderstanding...

HDX still has a selectable buffer that affects the latency of playing native VI's live..

I am asking how the performance of that is.. is 64 usable?
Pro tools using core audio, unlike all other daws i have used, suffers horrendous performance losses under 128 buffer at 48k and 256 buffer at 96k.. I am wondering how the HDX driver performs in these situations.. Of course i realise whatever buffer i choose has nothing to do with the latency of the DSP plugins.. I am talking about native here, as i would still use a lot of that with HDX (probably another reason I need 2 cards, for the voice count).

It's not an issue with HDx even with VI's. Another reason why I like HDX. I keep my buffer at 1024 all the time and get tight VI response. Thats what Emcha was saying. You don't need to worry about it.

C

[TOM@METRO]

Running HDX here. Lots of MIDI/VI stuff. 128/256 buffer and no client complaints about latency..

[YYR123]

another thing I did recently to help my VI/Midi latency was to run with a MOTU Fastlane USB/MIDI controller.

That helped so much....

I really noticed in stand alone mode with different software apps....crazy difference.

So much better than depending on AISO or native drivers.

[Raoul23]

Stop keep tempting me guys


Sent from my iPhone using Tapatalk

[TNM]

Originally Posted by Carl Lie

It's not an issue with HDx even with VI's. Another reason why I like HDX. I keep my buffer at 1024 all the time and get tight VI response. Thats what Emcha was saying. You don't need to worry about it.

C

1024? That doesn't make sense.. if it had no bearing why would they even provide the choice? Maybe 1024 is tight enough for you but i am sure it is different to say choosing 128.

[Carl Lie]

Originally Posted by TNM

1024? That doesn't make sense.. if it had no bearing why would they even provide the choice? Maybe 1024 is tight enough for you but i am sure it is different to say choosing 128.

The output buffer has nothing to do with the latency on tracks in HDx. The mixer is using the HDx card.

C

[TNM]

Originally Posted by Carl Lie

The output buffer has nothing to do with the latency on tracks in HDx. The mixer is using the HDx card.

C

ok so what's it for then, seriously?

[Emcha_audio]

Originally Posted by TNM

ok so what's it for then, seriously?

The output buffer is exactly for the use of Native plugins and VI's, the cards are already set at a fix internal buffer that is not accessible by the user. So you can put a high output buffer to have a high native plugin count (watch out for eating voice count if you dont place the plugins in the right order native vs dsp) and to use VI without suffering performance drop.