Nice support for hundreds of dollars spent. I've even offered to send them a sample project to test. Sometimes if I persist they reply with all the usual checklists for me to follow, but eventually they abandon me, never considering the remote possibility that they may actually have a bug, or trying to reproduce the problem. Over and over all they do is send me an automated email telling me to expect followup within a short period, and then they drop the ball. Its as if the drums were being processed by different clock sources that were all starting to drift. Sadly, I've tried no less than 10 times over almost 2 years now to get help from Cakewalk on this. Pick a nice medium tempo like 120, select the 8 bar sequence (grid snap on so it's exact), enable looping, and let it play.Īfter about a minute (less if you're ears are sensitive to timing problems), you'll begin to hear that the snare, kick, and the other drums are beginning to trigger out of sync with each other. To reproduce it, grab any 8 bar drum pattern that has instances where the kick, snare, and maybe a tom or cymbal all trigger together at one or more points in the sequence. With this configuration, I have found that "looping" to build up a song idea has become a frustrating and nearly impossible venture because of a synchronization issue.
Using Session drummer 3, I've been in the habit of routing my snare, kick, and "all other" drums to three separate audio tracks, so I can process some drums separately from the others. Sound card is M-audio Delta 24/96, ASIO drivers. Using Session Drummer 3 with Sonar 8.5.3. Synchronization problem with session drummer 3
0 kommentar(er)
