4

[Mark Farrell]

Thanks, will have a play and see what happens.

[Mark Farrell]

Just to confirm as well im having this problem with superior 2.0 NY- Avatar, even though the topic is slightly different, the problem is the same.

[Mark Farrell]

I understand your not digidesign specialists therefore any advice on the mbox would be unsupported. But i’ve used the MBOX with pro tools 6 PT 6.4 PT 7.0 PT 7.4 and now PT 8.0 All have been compatible with the original MBOX and have always allowed me to choose 128 buffer settings that have worked. Right now i can use PT 8 superior 2.0 at 128 and its great to record to. So what would be the reason that outside of PT on the same computer im getting latency? It doesnt seem to make sense because wouldnt the asio drivers im using for toontrack solo be the same ones that are being used for PT?
Im just trying to think laterally, to find out what could possibly be the issue. Unfortunatly my geekiness only goes this far.

Obviously you think this is an MBOX issue, which is fine, i only disagree because its worked in the past and for other VI’s. VI’s are unusable once you hit the 256 or higher buffer settings but i’ve been using them for years with an mbox at 128. And it is definatly working at 128 because the difference between 128 and 256 is very noticable. I will post in the DUC forum and see what people say. But the most important thing im asking is can you look past the MBOX issue. If i’d said i’ve got an MBOX 2 and i have this problem, what would be your next step for advice? Could anything else disturb the asio drivers but only whilst in solo mode? as it works perfectly at 128 in Pro tools.

[Mark Farrell]

Well rogue i dont know what to say. I used toontrack solo last year at the Brisbane QPAC theater in Australia live on this exact same setup, nothing has been added or changed on the signal path. I used it at the Queen Street Mall in solo mode as well, again with no problems whatsoever. I used to use it as a plugin in pro tools for live purposes, but didnt like to risk it, as even without rec just having the track rec armed i would get the occasional hicup for about half a sec once every now and again (a pro tools issue). I found i didnt have this issue when i went into toontrack Solo so i kept at that. I have always used and MBOX 1 on winxp laptop, going midi out from my TD-20 into an edirol MIDI/USB cable, then through superior 2.0. I am absolutly baffled at whats happened. And also baffled at how you say with an MBOX 1 you get 512 buffer settings in Toontrack Solo, I have used this in the past with 128 buffer settings. In PT i can get it down to 128 as well which is perfect, just not in solo mode.

Please look past the MBOX 1 issue because im not stupid, i can tell you in all honesty, i was getting 128 buffer settings in toontrack solo for months and months. Just one day for reasons i’ll never know i started toontrack solo and got latency. Changed the buffer settings and it stayed with the same latency. Deselected asio as the audio device, restarted, selected it again, with no luck.
If we looked past the MBOX, what else could be giving me this problem? please i dont want to go back playing live in a pro tools session.
Just to confirm i can tell you that the sound engineer at the QPAC theater was so impressed with the sounds from superior 2.0 that after the concert he came down to check it out, i remember him commenting how it wasnt going through a DAW.

I have never plugged in any other audio device like mbox 2 or mini whatever, it has allways stayed the same.

Help.

[Mark Farrell]

Im confused. I have changed the setting to 512 which isnt acceptable to use. The reason im confused is i’ve used toontrack solo to play superior 2.0 live and it worked brilliantly, with 128 buffer settings. Since then i upgraded Pro tools to version 7 from 6.4 and then onto pro tools 8. The only thing that would have changed was the mbox drivers, but they would have been updated. Before the PT updates everything was working fine, i may have performed other updates, maybe i’ve downloaded some new audio codecs i dont really know. All i know is that prob within the space of a few months solo has gone from perfect, to latency.

[Mark Farrell]

anybody?

Skiltrip, did you manage to fix this?

[Mark Farrell]

I have the same problem! whats a WDM? Asio device is selected on mine, im using mbox 1 and latency in Solo is terrible. What do i do?

[Mark Farrell]

lol, yeah somehow managed to miss the ‘trigger’ button on the module , jesus if its this bad at 28 what am i gonna be like at 58? I changed the velocity fader on the cymbal, hope that solves it. I thought there might have been some setting in superior or something, but hopefully this phantom cymbal doesnt make a comeback.

Question for you though, why was it that when i plugged directly into the TD20 on stage, i didnt get the phantom cymbal triggering when using a preset. It was only when plugging into superior 2.0 (using the same preset on the module) did the phantom cymbal start?

any ideas?

[Mark Farrell]

erm, thanks, but how? i just looked at every setting i could find?

[Author]

Replies