Drumagog Discussion Board

Thanks Matt, that's useful advice about the "Details", I'll try it.

(I had seen that other thread, and I have my own ways of getting flams to trigger, but those sort of fixes are less than ideal).

Yes, I'm using Advanced mode. Auto doesn't help. (And on the Visual page the resolution line with Auto looks to be set at the same place as when you set resolution to 23ms -- but then then I'm not exactly clear about how Auto works, as the manual doesn't provide any useful info).

The other thing about this that drives me nuts is the inconsistency -- you play the same section back ten times without changing a single thing and five times Drumagog will play the flam and five times it won't.

Is there any reason why the lowest resolution is set to 23ms? This causes me no end of problems with flams and other quick double hits. Yes, I have developed various methods to solve this, but they add an awful lot of time and hassle. Things would be enormously so much easier if I could just set the...

>Yes, we are aware of certain latency issues, such as this one between Cubase 3 and Cubase 4 using Internal Port. We have experienced on our side as well. We will continue to look into this and are hopeful that we will find a solution. Okay, thanks. >Since you're using Drumagog Platinum and BFD, I a...

>As stated in the MIDI section of the manual: >"Due to the fact that MIDI output from a plug-in is not directly supported on most audio applications, Drumagog’s MIDI output is not as accurate as its audio mode. The timing of MIDI notes generated from Drumagog may be off by as much as a few mill...

I've found that Drumagog's MIDI output is not working properly in Cubase 4 (I'm running Cubase 4.5.2 and Drumagog Platinum 4.11). The MIDI output is around 80ms behind where it should be. In a simple project it's exactly 80ms, but in a complex project it's a few milliseconds out from that again, so ...

I'm using XP Pro (SP2) as well. I'm not using the /3GB switch.

I should also point out that my VST Performance meter (as opposed to the general Windows Task Manager CPU meter) was showing about 60% on the project in question.

I get the same sort of thing after loading Drumagog instance number 10 In Cubase 4.10. I'm a bit disappointed as I replaced my old system with a 4Gb Intel Quadcore Q6600-based system just so that I wouldn't have these sorts of issues again. The CPU isn't even close to being maxed out, it's registeri...