• SONAR
  • Note duration times of "zero" when recording midi with a drum pad (Bug? *youtube video*) (p.3)
2013/10/03 00:29:16
bandso
I learned how to use, and played with the cal script for about an hour but it threw a syntax error...god I spend way too much money on gear to hit creativity killing issues like this.. Mixcraft is looking good about now...lol... nah just joking. I'm going to try my controller in Studio One right now and see if is working there.
2013/10/03 01:31:18
swamptooth
Run it through midiox too to see what's going on.
2013/10/03 03:17:45
brundlefly
Like i said, just select the entire clip after recording and set a duration of 60-120 in the Event Inspector module of the Control Bar, and be done with it. I guarantee you it's the drum controller sending Note On/Offs to close together. You didn't mention which Simmons model, but I guess it's not their SD-1000 because a quick check of the manual for that module shows it has adjustable duration.
2013/10/03 04:01:16
swamptooth
There's also the possibility that this is because instead of note off messages per the midi standard sonar translates these as previous midi note with a velocity of zero-which equates in the midi spec with a note off. Midiox will show what's going on.
2013/10/03 07:32:43
beltrom
bandso
I learned how to use, and played with the cal script for about an hour but it threw a syntax error...god I spend way too much money on gear to hit creativity killing issues like this.. Mixcraft is looking good about now...lol... nah just joking. I'm going to try my controller in Studio One right now and see if is working there.




Ooops - terribly sorry. Didn't check to see if it worked. Assumed it did as it seemed people reported using it.
Totally understand if you don't want to see a CAL script again. They are kind of neat though and have their uses.
 
If you're NOT totally burned on CAL, below is an alternate CAL script you can copy and paste to a .cal in your CAL-folder.
This little one is fresh out of the owen but I have tested it on my system.
As minDur (short for minimun duration accepted) is 5 it searches for notes with duration less than 5 and sets those to duration 5.
You can change the number after minDur  to any value you prefer of course and keep it as your script for the particular purpose of fixing 0 durations.
I would also bind it to a shortcut key (Alt + A for example) under Edit > Preferences > Shortcut keys (all CAL's are there so you can bind them to keys).
Then you just have to press Alt + A after recording to execute script below - might save back some of the time I wasted for you.
 
;; Start of CAL
(do
    (int minDur 5)

    (forEachEvent
     (if (== Event.Kind NOTE)
      (if (< Note.Dur minDur)
        (= Note.Dur minDur)
      )
     )
    )
)
NIL


 
 
 
2013/10/03 08:55:42
bandso
I'll give this a try later today when I get home. No I'm not burnt out on Cal code. Using it is just new to me.  I'm a code slinger by day, so I'm used to everything that comes with it. You guys are the best!
2013/10/04 10:34:35
bandso
I have mixed emotions about this post.
 
The good part:
I reported the "bug" to cakewalk through the website and was later told to call customer support, so I called them. I spoke with their customer service rep for about 10 min, having a philosophical conversation about whether any newly recorded midi note that comes into their system should ever have a duration of zero (I say no, he said it depends, ...huh?? why would a newly recorded midi note ever have a duration of zero...)
 
I was indeed given a work around that more or less works. Record your midi take, then select all of the notes before they are quantized (even the ones that were recorded with zero duration) and stretch the length of one of the notes with an above zero duration with the smart tool on the PRV. This adds the same duration to all of the selected notes and brings the notes with the zero duration up to a level of 1 or above. The quantize function will then find these notes and adjust them accordingly. It's not pretty, but it works. Many thanks for that.
 
The bad part:
I was told that this issue is all in my controller and that cake doesn't even consider this a bug to be addressed. However considering I can use the same controller fine in Studio One and Mixcraft, I do indeed think this is something the developers should address in the future. My service number on this issue has been closed and is DOA...
 
I must apologize for the above crack I made about MixCraft. I downloaded the demo to check my controller against it and I've got to say I was impressed. To me it's ugly and looks like a toy, but once I got into in to it I discovered that it is a damn fine and stable DAW that is really built for speedy workflow and quick music creation. My controller also worked flawless with it.
2013/10/04 11:08:20
All4Him
You could try to quantize the note duration only. I usually do that before I start editing my drum tracks recorded with my alesis drum set. It makes them easier to see. In PRV press ctrl + A and then quantize duration only.
2013/10/04 11:45:13
bandso
That's exactly what I'm trying to do, however the newly recorded notes initially are listed with a zero duration in the PRV so the quantize function does not work on them. That is the bug I'm running up against.
 
Please see my very short video at http://www.youtube.com/watch?v=Dq7rVwg5HfI you will notice that I am doing exactly what you describe.
2013/10/04 13:03:14
beltrom
You seem to echo Craig Andertons review of Mixcraft on Harmony Central...
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account