Topic: Latency in Solo w/ EZD

Viewing 12 replies - 1 through 12 (of 12 total)

Replied July 7, 2008 at 20:04 #1922117

Rogue
Moderator

Hi – sorry for the late reply.

it sounds like you have a WDM driver selected. No matter the value selected in such cases solo will force on a 512 buffer to avoid serious issues that could force you to hard reset the machine, not good! That said it might be a different issue but that’s the most obvious explanation that comes to mind.

Best regards,
RM

Rogue Marechal - Toontrack
Configuration Manager

Replied January 8, 2009 at 03:31 #1925630

Mark Farrell
Participant

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?

Replied January 9, 2009 at 02:49 #1925638

Mark Farrell
Participant

anybody?

Skiltrip, did you manage to fix this?

Replied January 9, 2009 at 12:38 #1925641

Rogue
Moderator

Hi – have you adjusted the buffer to 512? … that’s the lowest an Mbox 1 will go down to I’m afraid so yes there will likely still be a perceivable lag but that’s the best you can expect with this configuration.

Best Regards, RM

Rogue Marechal - Toontrack
Configuration Manager

Replied January 10, 2009 at 04:00 #1925670

Mark Farrell
Participant

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.

Replied January 12, 2009 at 12:39 #1925680

Rogue
Moderator

well. I can only repeat that the original MBox can not perform at latency below 512 buffer. I recommend you contact Digidesign for confirmation and troubleshooting of your problem however.

Best Regards, RM

Rogue Marechal - Toontrack
Configuration Manager

Replied January 13, 2009 at 10:59 #1925711

Mark Farrell
Participant

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.

Replied January 13, 2009 at 12:42 #1925714

Rogue
Moderator

http://duc.digidesign.com/showthread.php?p=1318243

… as per above, we are not Digidesign specialists so until you clarify what minimum value your hardware can operate at then we’ll be at a standstill as setting a value lower than the MBox is capable of could be detrimental and produce a higher latency than the minimum value it can operate at. In fact back in the days ProTools 6.4 (IIRC) would squeal like a pig if you attempted this.

Don’t get me wrong, we are happy to help but I don’t believe for a second that the original MBox can go as low as 128 buffer. It’s also not unreasonable to think that testing of newer MBOX ASIO drivers against the original hardware design has been minimal… I might be right or I might be wrong but confirmation on this aspect from the horses’ mouth is mandatory before we look any further.

Best Regards, RM

Rogue Marechal - Toontrack
Configuration Manager

Replied January 15, 2009 at 06:17 #1925741

Mark Farrell
Participant

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.

Replied January 15, 2009 at 06:18 #1925742

Mark Farrell
Participant

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.

Replied January 15, 2009 at 11:26 #1925746

Rogue
Moderator

So what would be the reason that outside of PT on the same computer im getting latency?

simply put, the drivers interfacing between sound card and hosts have nothing in common. Digidesign uses a proprietary protocol to optimize their hardware for ProTools but rely on the ASIO industry standard for compatibility with other hosts.

The only thing I can offer is that our programmer has a quick look at what may cause the problem in solo with the latest Digi drivers but ultimately if the ASIO driver does not do its job properly there is nothing we can do about it. I would also suggest you try in another host, such as a demo of Ableton Live and see if it fares any better with another non Digidesign application and report your experience.

Best Regards, RM

Rogue Marechal - Toontrack
Configuration Manager

Replied January 16, 2009 at 03:58 #1925767

Mark Farrell
Participant

Thanks, will have a play and see what happens.
Author

Replies

Viewing 12 replies - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.

Please log in to read and reply to this topic.

Latency in Solo w/ EZD

E-drum Workshop

Viewing 12 replies - 1 through 12 (of 12 total)