Hi all.

My thoughts, for anyone interested..
 
Loop Construction View:
*  Allow per slice curves/fades when using, for example, the gain automation.
    (or at least allow the nodes to be moved independently)
 
This would help to eliminate pops when using the gain to isolate elements within a clip, you could simply fade out the slice rather than it being stepped.
 
*  Allow slices to be reversed.  Allow slices to be rearranged.
 
These two things would open up a world of creative potential when using Loop Construction.
 
Pro Channel:
*  Allow multiple instances of the Quadcurve EQ, PC76 Channel Compressor, PC4K Bus Compressor and Tube Saturation Module on a track or bus.
 
During a mix session I'll use multiple EQ's and compressors on a track or bus.  In most cases I'd prefer to use these modules over using third party equivalents via the FX Chain module.
 
*  Allow Ctrl+dragging of Pro Channel modules to other Pro Channels.
 
This would be very useful, for obvious reasons.
 
*  Allow per module Sends, or, introduce a Send/Splitter module.
 
This would allow increased routing flexibility; taking the post Quadcurve EQ signal and send it to a separate bus before the signal continues through the Pro Channel for example.

I am all for efficiency and productivity. Keyboard strokes sometimes are faster than mouse click. Following are my suggestions.

Within piano roll view-

TAB keyboard button for automatically high/select the note/event in the piano roll view, going to next note by pressing TAB again. Shift+TAB for going back to the previous note.

> button for increasing the highlighted note length and < button for decreasing.

P + up arrow button move hightlighted note to higher pitch. P+down arrow move highlighted note to lower pitch.

V + up arrow/down arrow button increase or decrease highlighted note's velocity value.

B + left arrow/right arrow button to shift highlighted note beat position values.



Thats my suggestion wish list. I find the so call smart tools tedious and clumsy. Right click open note value manual is not productive enough. Please consider this Cakewalk.

Assuming there is going to be a release in the next few months (just speculation) there's probably a feature freeze now. That should not stop you posting further suggestions though esp if I'm wrong.

In the PRV, many MIDI manipulations can be performed with CAL scripts bound to keyboard shortcuts. For example:
Increase Note Length
    (forEachEvent
        (if (== Event.Kind NOTE)
            (if (< Note.Dur 65535)
                (+= Note.Dur 1)
            )
        )
    )

Raise Pitch
    (forEachEvent
        (if (== Event.Kind NOTE)
            (if (< Note.Key 127)
                (+= Note.Key 1)
            )
        )
    )
 
Increase Velocity
    (forEachEvent
        (if (== Event.Kind NOTE)
            (if (< Note.Vel 127)
                (+= Note.Vel 1)
            )
        )
    )
 
 
 

CakeAlexS
Assuming there is going to be a release in the next few months (just speculation) there's probably a feature freeze now. That should not stop you posting further suggestions though esp if I'm wrong.

Again with the standard disclaimer that I don't speak for Cakewalk, it has been my experience that they're always interested in suggestions on how to improve the program. I suspect they have some folder somewhere marked "stuff worth prioritizing for future versions"

scook
In the PRV, many MIDI manipulations can be performed with CAL scripts bound to keyboard shortcuts. For example:
Increase Velocity
    (forEachEvent
        (if (== Event.Kind NOTE)
            (if (< Note.Vel 127)
                (+= Note.Vel 1)
            )
        )
    )
 

Sorry for the OT post.
I just realized CAL isn't that hard. I've always hated lisp syntax, it's bass ackwards (which might be one reason why CAL isn't huge. No one codes in lisp, if it looked like Perl or JS, there would be a bazillion scripts out there) but looking at the above syntax it seems like it might be relatively hackable. Now I'm going to read the ref manual and play with it. A controllable midi compressor seems like it might be relatively easy to code (I need one of those).
Thanks!
 

Anderton
 
Again with the standard disclaimer that I don't speak for Cakewalk, it has been my experience that they're always interested in suggestions on how to improve the program. I suspect they have some folder somewhere marked "stuff worth prioritizing for future versions" 

I do hope so Craig, I mean, who wouldn't want the option to use multiple Quadcurve EQ's in a single channel?
The thing sounds so good!

Loop Construction view definitely needs some love though, a version 2.0 would be most welcome :)

TomHelvey
Now I'm going to read the ref manual and play with it. A controllable midi compressor seems like it might be relatively easy to code (I need one of those).
 

John S. Allen's Cakewalk CAL programming information page

Here's a Programming Guide by D. Glen Gardenas and Ton Valkenburgh
 
More stuff from Ton Valkenburgh :
 
Examples and library  :

http://web.archive.org/web/20060429074139/http://home.wanadoo.nl/t.valkenburgh/CAL.html

 
CAL course  (select CAL Course in bar at left for English version):

http://web.archive.org/web/20070203202120/http://home.wanadoo.nl/t.valkenburgh/indexmidi.html

 

golophei I am all for efficiency and productivity. Keyboard strokes sometimes are faster than mouse click. Following are my suggestions.
Within piano roll view-
TAB keyboard button for automatically high/select the note/event in the piano roll view, going to next note by pressing TAB again. Shift+TAB for going back to the previous note.
> button for increasing the highlighted note length and < button for decreasing.
P + up arrow button move hightlighted note to higher pitch. P+down arrow move highlighted note to lower pitch.
V + up arrow/down arrow button increase or decrease highlighted note's velocity value.
B + left arrow/right arrow button to shift highlighted note beat position values.
 
Thats my suggestion wish list. I find the so call smart tools tedious and clumsy. Right click open note value manual is not productive enough. Please consider this Cakewalk.

 
Very good suggestions! The same should work in staff view as well. In addition, because I am also a "mouse user" most of the time, I would like to suggest a compact, detachable, always-on-top note duration value palette (much like such things are done in Photoshop, e.g.).
 

 
 

Paul P

TomHelvey
Now I'm going to read the ref manual and play with it. A controllable midi compressor seems like it might be relatively easy to code (I need one of those).
 

John S. Allen's Cakewalk CAL programming information page

Here's a Programming Guide by D. Glen Gardenas and Ton Valkenburgh
 
More stuff from Ton Valkenburgh :
 
Examples and library  :

 
http://web.archive.org/web/20060429074139/http://home.wanadoo.nl/t.valkenburgh/CAL.html
 

 
CAL course  (select CAL Course in bar at left for English version):

 
http://web.archive.org/web/20070203202120/http://home.wanadoo.nl/t.valkenburgh/indexmidi.html
 

 

Nice resource! Thanks!
 
Regards,
Dan