winkpain

Time travel? I'm trying to suss out a possible recording sync issue, and in starting I recorded a MIDI 1/4 note beat from a synth track out to an AUX track to see how the recorded audio lined up with the time grid, assuming there would be delays of varying times with varying latency settings. To my great surprise, I found that, at higher latency/buffer settings the recorded note, rather than being delayed, it preceded the beat it was recorded from!! The higher the latency, the earlier the preceding note would be. How..... is this possible?!? The audio is obviously being written, just after the fact, to a location before it actually occurred in time. Is this the "Automatic Delay Compensation" (which I have never really understood as it is described and seems to be just associated with few and certain plug-ins only some of the times) ? But the results were the same whether the Delay Compensation switch was on (compensation off) or off (compensation on) and also true with just recording the metronome (to an Aux track) internally OR recording the Metronome with a mic from speaker. In the screenshot examples I show the extremes of a buffer size of 32 samples (note recorded on the beat), and then 2048 samples (note recorded before the beat). There is obviously something in the theory of concept of these above settings/process that I have misunderstood. Please educate me? I am using a Steinberg UR22 with latest drivers.

Yup. That's what I figured. But the Workspaces idea is clever, if not ideal...

Is it possible? The entire Control Bar can be floated, but I would like to have an individual module, for example the Snap to Grid module, floating and available to me in any full screen window. Can this be done?

Is the "snap to zero crossings" setting in the Preferences/Customization/Snap to Grid settings actually the only zero crossings setting?? In other words, must I have Snap to Grid on to have audio cuts snap to zero?? I work outside of Snap to Grid a lot, but I almost always want audio to be cut at zero crossings. Isn't there a way to default to this and not have Snap to Grid on? After all, zero crossings are not on a grid. This is further frustrated by Snap to Zero crossings being only available to set in that Preferences section AND it doesn't maintain a checked "On" setting when starting new projects! Even if I have a project open with Snap to Zero crossings checked on in Pref. and then open a new project, keeping the other one open, the Snap to Zero crossings setting is then un-ticked by opening the new project, apparently. Workspaces? I would assume, but I see no Snap to Zero crossings setting in Workspaces. How can we have Snap to Zero crossings just on by default always?? I also would have thought that Loop Construction (which I've never really used) would have tools for editing loop beginnings and endings and/or stretching/moving waveforms. In the manual it mentions, in the appropriate section and talking about the "Audio Scaling" aspect of LC, But....what "precise edits" can you perform here? There are no audio editing tools within Loop Construction. You can zoom in on the zero crossings, but do nothing once there.

Yes, I tried using Tobias Ericson's loopMIDI, but I'm not sure exactly how to use it. I did not succeed. But the Bounce to Clip tip (shoulda thought of that! Doh!) is way easier. Thanks!

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?

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!

Is there anyone out there familiar with using the nord electro (mine is the 2) as a MIDI controller with CbB?? All is well and as expected with keyboard play and buttons and knobs for controllers except for the Octave Shift buttons (cc 29 from the nord) do not alter the MIDI notes being received from the keyboard, so no octave shift is obtained as would be expected or desired. These buttons do shift the octave of the onboard sounds on the nord, so the hardware is functioning. The nord manual indicates that this MIDI octave shift data should be sent as expected and that the only MIDI info not implemented is the pitch shift and mod wheel data, because, well, the keyboard doesn't come with those pieces of hardware. No surprise there. I can determine that MIDI data is being sent when pressing these Octave buttons and that Cakewalk is indeed receiving it at cc 29, however no change occurs. I know how to filter the incoming note info once received in order for the notes to play at the desired octave (with note transpose sliders on the MIDI offset control in CW, for example) but the notes as seen by CW still get recorded/notated in the default octave. I can then select all and transpose, of course, but obviously this is all just a tiresome workaround. And I know how to assign MIDI controllers to functions in the DAW, but this octave shift function, so basic and ubiquitous, seems to not be available to assignment. How and where does Cakewalk receive and use this octave shift data from MIDI keyboards? Is it, in fact at controller number cc 29 ? Is there a way to go in and edit it to use cc 29 if not??

Well.... what happens when you press SHIFT or ALT with the Smart Tool selected??

What's the "wrong tool" ? It works (the SHIFT and ALT options) as expected with the Smart Tool

Does it not work for you to hold SHIFT while dragging the single clip start edge on the lane you want? Otherwise, holding ALT while mousing to the upper half of the chosen clip and then clicking to split just that clip at that point also now works. These are operable on my latest build version (2020.1, build 28), anyway.

O, got it. I'm on a laptop with no Numpad. But no worries I'm working it out.

@Heinz Hupfer These are great! Certainly faster than Ctrl-T > type "12" > Enter ! Thanks so much for sharing! I don't see the semi-tone transpose scripts, but easy enough to take it from here. Thanks again!

How do you bind a keystroke to a specific CAL script?

I have found no fewer than four of the oft-mentioned and important "Cakewalk Core" folders on my machine in the following locations: C:\Program Files\Cakewalk\Cakewalk Core C:\Users\USERNAME\AppData\Roaming\Cakewalk\Cakewalk Core C:\ProgramData\Cakewalk\Cakewalk Core C:\Cakewalk Content\Cakewalk Core What are the differences and which should we be concerned with for importing/exporting/saving of presets, templates, key bindings and such? The two at ...\ProgramData\ and ...\AppData\Roaming\ would seem to serve similar purposes but contain slightly different files, perhaps due to my own confusion in thinking (up to now) that there was only one "Core" folder and having at times chosen the "wrong" one. Should these two be mirrors of each other?

Yeah, I feel a little slow for not copping to that at first as well, especially since I've been through a similar thing before. I did check the key bindings right off but found N and Ctrl-Shift-N to have the appropriate default bindings. It's just that they had, at some point, gotten bound to additional commands in different contexts, which is enough to knock it all off kilter. The multiple bindings don't make themselves clear unless you really comb through the menus and hunt them down. For me custom bindings are an absolute workflow game-changer and the basic defaults are never sufficient. But even still, I see no reason at all to have more than one binding to the same command or vice-versa, and it causes such turmoil. Further reason why there should be a stop gap to prevent such a set-up. For sure, though, the protocol to chase down CbB issues at this point should always begin with setting Workspaces to "none" (this seems to be #1 now), zapping all key bindings, and by-passing all FX while you're at it, and then begin to troubleshoot.

.....However! And Holy Bejeweled Mother of Fudge! For those of you following my, apparently private saga, bless your little hearts!..... I seem to have gotten somewhere - and it doesn't have to do with Workspaces for once! This virus quarantine solo cabin fever workflow makes one dive deep! In order to have a clean slate to troubleshoot with, and inspired by @User 905133's tenacity in sharing my woe, I opened New>Empty project, set Workspaces (just to be sure) to None, and (here's the kicker!), zapped all in my Preferences>Customization>Keyboard shortcuts (or Key Bindings) in order to have a clean slate there as well. And this last thing is what shed the scales from my eyes! I have run into problems before with Key Bindings and am surprised that I didn't think of this before now. Simply put, Cakewalk allows you (mistakenly, I would say) to bind the same keystrokes to multiple functions as well as having a single function bound to multiple keystrokes! Doing so causes no end of confusion and wasted time. I have been through this before and spent literally days going through my decade-long built up custom bindings and eradicating (or so I thought) all the double (or even triple) binds to try and deal with that problem back then. Since there are multiple context windows to go through with many functions and many many key combinations, it takes quite a while. Perhaps a better approach would be simply Zapping All and starting all over again, but as I say, years of custom bindings that are now so ingrained... I wished (and requested) then and I wish even more now that CW would simply not allow you to create multiples of any of these bindings/functions, or at least warn you that you are about to do so. This is the way it is, after all, in other programs, so it seems an oversight. Anyway, with the Keyboard Shortcuts settings it would appear that IF you should happen to bind N to anything anywhere else in all the different contexts, and despite its still being bound to and successfully functioning as the Snap on/off toggle, the keystroke looses what I now see is called its "Toggle Extended" status, which seems to account for its ability to be held down without repeating its action. And IF you should happen to to bind Ctrl-Shift-N to anything anywhere else in all the different contexts it will cease functioning as the Secondary Snap toggle even though it still shows that it is bound to that function. Both of these things I had done at some point over the years and both of these things exactly cause the issue I have been brooding on about here! So sorry! Now I have a functioning Secondary Snap Scenario! Although while the over-mentioned holding down of the N key no longer repeats its toggling action over and over, neither does it allow anything else to be done with mouse or otherwise. This last point seems to be the case on laptops using recent Synaptics touchpad drivers which don't allow simultaneous keyboard and touchpad use, or in other words won't let "Smart Sense" be turned off completely. For me now Ctrl-Shift-N successfully toggles between two Snaps where I can just make any settings in the normal way once in each of the alternates, and that is what maintains. There is no indication that you are in a "Primary" or "Secondary" snap however, so it is technically possible to have the exact same settings in each and not know that you are in the alternate. Toggling will show no difference in this case. Once I got Ctrl-Shift-N working, the default for the second snap was at "1 tick", so it was definitely obvious. Thanks all for bearing with me!