Jump to content

Latency using Q25 to trigger MTPowerKit sounds


Recommended Posts

The delay is all on the audio side from two sources:

  • buffering in the audio driver and
  • plug-in delay compensation.

Depending on the audio driver and driver mode, this setting may be adjusted using the buffer size slider under Mixing Latency in CbB preferences or using software supplied by the audio interface manufacturer.

If there are any audio FX in the project, to see if plug-in delay compensation is an issue press the FX button in the Mix Module. This will bypass all effects eliminating the PDC needed for the plug-ins.

Link to comment
Share on other sites

  • 2 years later...
1 hour ago, brandon said:

is the Q25 plug and play with CBB or is an interface necessary?

An audio interface of some sort would be needed to monitor/record the Q25's onboard audio through/into Cakewalk, but used as a MIDI controller to drive a drum VSTi in Cakewalk as the OP suggested, nothing else is needed; it would just be a USB-MIDI controller in that case.

Link to comment
Share on other sites

The problem is that Alesis doesn’t supply any Midi drivers. It uses a generic driver. Midi latency can come into play as a result. 

I did a video on midi latency once and I tested all the midi controllers I had on hand 

Controllers that came with a midi driver - Roland, Korg, Yamaha- had very low latency at around 3ms.
The only controller I had that didn’t have a driver was an Alesis Synth Station. It came in at 10 ms.  

Of note was 5 pin Din Midi connected via my Motu interface was identical for two controllers that had both USB and Din. 3ms. 

One old Roland from 1987 was slow at 8ms.  

We will assume that your Alesis will have higher midi latency. 
Now add to that your audio latency and your going to be well over 20 ms using computer audio. 
 

You will read that drummer’s always monitor the audio from the drum kit when recording because any latency from a computer output will interfere with your performance. 

Link to comment
Share on other sites

Based on the orginal post and title I made the istake of assuming the Q25 was a drum contoller with onboard sounds. Appears it's just a class compliant controller keyboard with no driver as John noted. So nothing special is required to used it, and MIDI latency won't necessarily be that terrible even without a dedicated driver. My guess is the OP's issue was more likely due to plugin delay or audio latency - as scook suggested - than to poor MIDI performance.

  • Like 1
Link to comment
Share on other sites

Thanks for looking it up @David Baay

I was too lazy and assumed it was that notorious Alesis Drum kit. 
The other negative about Alesis is a key went dead on mine which is normally easy to fix. I have replaced those silicon sensors on all 3 major brands.  But Alesis doesn’t sell parts! 
I tried to give it away and nobody wants it! 
Alesis and Mackie = no customer service or parts. 
The 1987 Roland I bought the sensors no problem. I gave that away to a friend who is still using it. 40 years later The Alesis lasted 3 years! 

Link to comment
Share on other sites

On 1/15/2025 at 3:00 PM, David Baay said:

An audio interface of some sort would be needed to monitor/record the Q25's onboard audio through/into Cakewalk, but used as a MIDI controller to drive a drum VSTi in Cakewalk as the OP suggested, nothing else is needed; it would just be a USB-MIDI controller in that case.

Thank you

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...