winkpain

I know I read something, somewhere here in a topic about this but don't remember.... Is it possible to record or output the MIDI note info of an ARP(pegiator) sequence generated in CW? Any way to patch the MIDI output of one track into the MIDI input of another? I've grown so accustomed to the ease of doing precisely this in Ableton, that I've thought it was possible here too, but.... No?

No screenset issues here - not with any Workspace or "None". Just saying for info purposes....

Another note/curiosity on the protocol for section splitting of clips, specifically audio. I notice that with Auto Crossfades enabled and then executing a Split Clips at Boundaries will apply the fades as expected. However, when not doing this manual split clips operation first and then committing an arrangement that splits clips as needed, no such fades are applied, even with Auto Crossfades still enabled. I also notice that these audio splits do not honor the snap to zero crossings setting on the split locations on the audio clips. Both of these - auto crossfades and zero crossings settings - would be a "smart" default for the Arranger's commit split protocol for audio clips, in my opinion, and would provide for much less "clean up" after a Commit Arrangement call.

I notice that using Slide or Nudge on Sections does not affect the sections themselves. Choosing a section (and allowing it to select the associated clips) and then executing a Process/Slide or Process/Nudge will move the clips but not the associated section. Perhaps this is as intended but I had expected otherwise and just wanted to point it out.

Thanks for the updates! All mentioned fixes that I have tested are functioning as expected. For me, the minor problem of Arranger Section renaming continues. That is, right-clicking Section or clicking on Section Inspector menu dots and choosing "Rename..." does nothing. Double-clicking the section name in the inspector or hitting F2 does work for renaming function, however.

I'm not sure if this is a consistent problem with all users, but I still have the issue with Ripple Edit mentioned with the 2020.1 release as discussed here... Additional details are that when using the full PRV view and attempting to copy/paste, drag/copy, or duplicate notes with Ripple Edit engaged that status does not take effect - i.e. existing notes just get pasted on top of rather than sliding over, "ripple-style". Performing the same edit (on the exact same notes on the same track) in the inline PRV (or with clips), however, the behavior is as expected with Ripple Edit functioning accordingly with notes sliding over accommodating the copy function. @msmcleod we had exchanged over this a bit. I wonder if it's still on the radar... 2020-03-21-15-37-42.mp4.bc5f81487aa60fa396f15ad407d98e42.mp4 2020-03-21-15-37-42.mp4.bc5f81487aa60fa396f15ad407d98e42.mp4

I do confirm that this behavior is only with "Snap by" chosen. Although I still don't get the logic of the one "snap unit" offset. As is further exemplified in this video, you see that as I drag the boundary to the preferred Snap by location, the visual change in the section moves as expected as I drag, but when I let go it snaps to a bar(or whatever snap unit is chosen) after that point. This offset is unique behavior not seen with dragging clips or notes with Snap by chosen. 2020-04-14-10-51-20.mp4

Thank you for replying. Yes, understood. I have understood the difference between Snap To and Snap By and have used them accordingly without confusion for a while now. Or.... Correct me if I'm wrong here in the following example: IF my section boundary is at the start of a measure, for example at 3.01.000, whether Snap is set to "To" or "By", the behavior expected would be the same if I drag it one or two bars earlier. That is, if I let go of it as I near the 2.01.000, it will snap to 2.01.00 (or by one measure). If I let go at 1.01.000, it will snap to 1.01.000 (or by two measures). Yes? What I found, and what is shown in video, is that if I drag the boundary to 2.01.000 and let go, it snaps to 3.01.00. If I drag to 1.01.00 and let go, it snaps to 2.01.000. In other words, a bar after the expected snap to or by point. This what I don't get....

Technically, yes. But only the one function will....well, function. CW permits binding multiple keystrokes the the same functions and permits multiple functions to be bound to the same keystrokes. If there is a "by design" reason for this, I don't see it, nor has it been explained. I do know that it causes a lot of confusion

Understood. But if I want to have snap enabled for measures, I just want it to snap correctly.

Yes, this is odd !

Yes, snap settings are set, as suggested for Arranger, to 1 bar. But one would assume that it would snap to the nearest measure boundary beneath the cursor, and not the measure after the nearest measure as you see it doing here. And the Rename function simply doesn't work for me when right-clicking or menu dot clicking. Dunno...

The new functions bring up a little issue that concerns Keyboard Shortcut managing. To exemplify with this new Arranger function: CW has this new function and it is assigned the default key binding of A in order to display the Arranger as well as in the Track View - View menu showing as "Arranger Show/Hide A ". However, I have historically had A bound to a different function in my custom bindings set up. A remains "co-bound" to the new default function as well as my custom one, but only my custom one functions. - This particular point is an over-arching issue with CW's allowance of multiple Key Bindings, which I see as an oversight. Multiple bindings shouldn't be allowed, especially with default bindings. This situation creates serious confusion as I've discussed elsewhere here But more the point here, and a minor one, really, but... If I then bind Arranger view to the newly available E, it will function but the Track View - View menu item still reads "Arranger Show/Hide A " I would ask either update the menu item Key Binding reminder text, or Don't allow custom (i.e. multiple)bindings on default bindings

Couple issues with the new Arranger function for me: Right-clicking or clicking menu dots and choosing Rename does not function (Double clicking the name in the Arr. Inspector or pressing F2 DOES work, however) Re-sizing a Section by grabbing boundary edge has odd behavior and doesn't re-size to my chosen point but is offset awkwardly by a measure, it seems Both these issues displayed in attached video.... 2020-04-13-13-34-38.mp4

I totally agree with that! Thanks for sharing in my pain! I guess you have time on your hands (don't we all!) to search that out 😉 The Enhanced Editing feature is for people using a particular hardware controller setup, I believe. Definitely not a majority user function, so very glad it has been taken out of harm's way!

Wow! Thank you!! Can't help but feel I played a tiny part in this!

Where and how is it still free to upgrade to Win 10?

Turn Workspaces to "None", go to Keyboard shortcuts and import the one you saved (from the default folder that comes up), and make sure save for next session is on. Hit Apply and Close. Leave Workspaces on None or choose "Manage Workspace" and uncheck Keyboard shortcuts from "Load from Workspace" window. Do this last one if you prefer to use Workspaces, and do it for each workspace that you would want to use, saving each as you go. Maintaining this protocol should keep your shortcuts loaded, but you can always re-import the one you exported, save workspace again (or make sure it's on "None"), and save project to be sure.

Did you also Export them (your custom bindings), either to a folder of your choice or the default?

Yup! 😉 It is only these couple custom bindings files that got misplaced there. I have them copied and backed up elsewhere. I will leave the ProgramData folder well enough alone. Thanks again!

Thanks. I'll happily leave it alone. There are, however, files in there now that were placed there by mistakenly confusing it for the other Cakewalk Core in the user folder. Just best to leave those alone as well? I will prefer that user folder Core folder from now on.

Yes thank you. I guess mostly my question is currently concerning Key Bindings, which isn't mentioned in the default folder list. And when exporting a custom bindings file, CW seems to default to, alternately , either C:\Users\%username%\AppData\Roaming\Cakewalk\Cakewalk Core or C:\ProgramData\Cakewalk\Cakewalk Core When examined, these folders seem similar in content to each other with many of the same files and folders but not all, and as such it can get confusing where an exported bindings file is or "wants to be". Anyone know? Should these two folders mirror each other??

I believe just editing your original post and put ting "[SOLVED]" in the title will work. Glad you figured it out. No shame! There are SO many permutations of incorrect possibilities, and sharing the process here is why we come, or some of us anyway.

So many good ideas here! I'm curious: Is the OP, "What new updates......", actually a query from CbB bakers or.... are we just asking each other for gits and shiggles? "Is this the real life? Is this just fantasy?"

Ah well. Thank you @JoseC and @bvideo I thought it was likely not an easy situation. As I said, according to the nord manual in its MIDI Implementation section, it says that: "If you use the OCTAVE SHIFT function, you can transpose the Nord Electro 2 keyboard ± 2 octaves (if the selected instrument supports this)." which is, of course, a little vague but makes it sound like they thought of it at least. The octave shift function is such a basic and ubiquitous function on all keyboards, I just took it for granted that it would work the way it's..... supposed to(?) But it seems that they are expecting an "instrument" (a DAW in my case) to support CC 29 as octave shift messages. I wonder which ones, if any, do... And yes, I assumed that the change would be internal to the keyboard itself and that it would just alter the note numbers by an octave before the keyboard sent them. And I didn't think that cc 29 as an octave shift was standard implementation as I've never seen octave shift ever being listed on any controller legend. But.... I figured I'd ask. Using the nord is just my only option where I am at the moment. It is not a huge deal to do the MIDI transposing on a per track basis for the time being, and a CAL script is a clever idea, but not necessary or worth it for now. Thanks again!