Jump to content

winkpain

Members
  • Posts

    476
  • Joined

  • Last visited

Everything posted by winkpain

  1. @msmcleod here is this... 2020-03-21-15-37-42.mp4
  2. Right-clicking the Snap value and choosing sets the Primary snap value. This functions as normal. Pressing N, for me ,toggles Snap (primary, I assume) on and off, as it should. Ctrl-Shift-N does apparently nothing, for me. But then I don't have a Secondary value set-up, which in order to do, it says in the manual (page 317 in downloaded Cakewalk Reference pdf): "To assign the secondary Snap to Grid settings, hold down the N key while selecting the desired snap settings in the Control Bar’s Snap module. To momentarily apply the secondary Snap to Grid resolution, hold down the N key while dragging or editing data that is snapping to the grid. When the N key is released, the main global snap settings are restored. To swap the primary and secondary Snap to Grid settings, press CTRL+SHIFT+N. Note: To enable/disable Snap to Grid, press the N key quickly. To assign or use the secondary Snap to Grid resolution, keep the N key pressed" Don't know what to say about keyboard driver. It's the default Standard PS/2 Microsoft keyboard driver. And I was curious if, for you, pressing and holding a key did not make it repeat as long as you held it down. I don't how to make it not do that, on any computer. And I suppose I'm more curious how you get into the choosing of the Secondary Snap settings if not by pressing and holding N, which is the only way the manual mentions to do so....
  3. I will do. Meanwhile, a most consistent aspect of the problem occurs with no Edit history in that: "With consistency it will be mysteriously "off" 'tho showing to be "on" right when opening a project saved with it "On". In other words, a project saved with Ripple Edit in the on state and opened with it in the on state will nevertheless behave as if Ripple Edit is off right from the start. Toggling Ripple off then on again will get it working in this situation.
  4. Nope. No Third party keyboard driver here. Just standard Windows 10 on a laptop. Ctrl-Shift-N seems to be for switching between Primary and Secondary. But in order to set it up to begin with, you are meant to press and hold N, then drag the mouse to Snap module for choosing those secondary settings, then release the N. Pressing N, or any key, and holding is just the same as pressing the key repeatedly over and over, however. It is this way on every computer keyboard I've ever worked on... So it just toggles the Snap function on and off quickly and repeatedly. Does it not do that for you?
  5. This discussion has introduced me to this "Secondary Snap" idea. HOWEVER, I can not get it to engage. Whenever I press and hold the N key it simply machine-gun toggles snap on and off many times while I hold it. I can't even move my mouse in order to go to the module to choose secondary settings while holding N down(or any key for that matter). How is this accomplished?
  6. Yes. Make selection first - click and drag in track or on timeline, select a clip to have its time selected, or any other time selection method, and then do a Shift-L. The selected time will be looped.
  7. This is certainly a bug. Not sure if it is release specific, but I don't think it was happening before, so I'm re-posting here: I am finding that Ripple Edit is disengaging mysteriously even while it's indicator (in the upper right of the Track view) shows it to be on. Simply toggling it off then on again will re-engage it. With consistency it will be mysteriously "off" 'tho showing to be "on" right when opening a project saved with it "On". And otherwise randomly, after being in regular use of the Ripple Edit functions with it in the on state, and having done some other types of edits, changing views, etc., and then executing an edit that should cause the Ripple functions, it no longer functions. Although still showing to be on, I need to toggle it off then on again to get it to work. More details with video examples here -
  8. Yeah. OK then. Well, I keep reminding myself that it's a free program, and generally a good one at that. So it goes. I would love to hear a reason from bakers or experts as to why this is not implemented, however.
  9. Precisely! Amazing oversight. And feels odd to be the only one (one of the only?) to notice it. Isn't this a "normal" workflow - to quantize edit multiple select audio transients to make improvements on a recorded performance?
  10. Yeah. I tried that idea. But yes, very time consuming. So is the "option" of selecting all the undesired transients, setting them to Disable, then selecting the desired, still enabled transients and choosing quantize, then re-enabling the disabled transients and move on to the next edit where you would have to do this process all over again. Surely there is something basic somewhere to allow me to quantize just my desired, selected transients. As I move through a, say, 4 minute long clip of a performance and just need to correct multiple irregularities leaving the rest of the clip intact, doing any of these options - selecting/editing one at a time, splitting into multiple clips to edit separately, disabling all the data you don't want to edit and editing the remainder (a profoundly counter-intuitive procedure) - are a great expenditure of time. Imagine if you couldn't quantize just the selected notes in a MIDI clip. Why are Audio Transients different? You can select them. And you can quantize them. Why can you not do both together???
  11. I agree with scook in that I find it way easier to work in the full PRV rather than inline. It's easier to see everything.
  12. ...and it works on other clips/tracks? Straaaange!
  13. ...Or perhaps you have a different tool selected. Hit "T" to engage Tool window and make sure Smart Tool (arrow on the left) or the Move Tool (crosshairs) are selected in order to move notes in PRV or inline PRV
  14. Perhaps a Clip Lock is engaged? (right-click the clip or look in the Clip pane of the Inspector)
  15. I believe this is one of those issues that just gets referred to the "feature request" bin. There are no Smart Grid settings that I know of. I have brought up this same point here elsewhere sometime before and got no response leading me anywhere to change it. I absolutely agree: the "smart" grid changes snap/grid resolutions at very inappropriate zoom levels rendering it a hindrance rather than a help to workflow. In any case, such a tool should have settings available for modification per user preference. There's nothing smart about a one-size-(that doesn't)-fit-all tool .
  16. Thanks for the suggestion, but I think you miss my point. I know fair well how to select multiple transients. My question is: after selecting multiple specific transients (with the Audio Transients edit tool, ctrl-clicking or drag selecting, etc.) how then do I edit , and specifically, how to apply Quantize to only those selected transients?? As far as I can tell even still, when choosing quantize, Cakewalk ignores chosen transients and simply quantizes all transients in a clip. So, simply put: How do I quantize only selected multiple transients in a clip??
  17. Yes. This I know quite well. Thank you, 'though. That is, as I mention, a very time consuming process with the issue that I outline above.
  18. Is there something I'm missing? I am not a frequent AudioSnap user in CbB to say the least, but I am very familiar with the profound ease of adjusting chosen audio in, for example, Ableton (sorry for the reference to someone else 😉 ) I think it is this very issue that has kept me away from it, but I am trying again.... So, here in Cakewalk I have an audio performance that is mostly good. In a few places there are some transients that could be tightened up, nowhere near all of them but enough that makes editing them individually very time consuming. If I quantize the entire clip to a single resolution (the only option), the notes/beats that I don't want affected become edited, of course, and many of them undesirably. I want to quantize just select transients to the selected resolution. I turn on edit transients (with edit tool, AudioSnap enable, or such) in an audio clip, select only specific transients by their markers by ctrl/shift-click or drag selecting, and then when I choose to quantize, ALL the transients on the clip are affected as opposed to just the transients that are selected, just as if I had simply quantized the entire clip to begin with. Is there a setting somewhere that allows me to edit only the selection? And if so, the default setting is off?? That is certainly counter-intuitive. No doubt I am just missing some very obvious thing right before me eyes....
  19. When I am editing in Audio Transient mode (with Smart Tool) on a track's transient markers, I can select markers and move them manually one-by-one, but when I have selected only certain markers either by ctrl-clicking or drag-selecting, thus making only my chosen markers turn yellow, and then choosing Quantize, instead of only my selected transients being affected, all the transients on the track are quantized. I want to quantize only my selection. What am I doing wrong?
  20. ...I also just found your "VST Inventory Tool" which helps see things more clearly, as well!
  21. Yes, my Sonar is X3 Producer. And, sorry I'm still a little confused: by "restore the excluded plug-ins", do you mean restore them to their excluded state? And, since there are two versions that Cakewalk sees - for me one in the default "Shared" folder, the other in my custom "E:\Vstplugins64" folder - which ones should I use (have enabled), and which ones should I have excluded?
  22. Thanks for this! Yes, it would seem to be these very excluded plugins that are the issue here with that referenced window/message. I had, indeed, enabled them as led to by a friendly post by Creative Sauce on YouTube, not an official CbB post, I know, but he does have good and seemingly knowledgeable presentations. So, you are saying that I should re-exclude them as they were done by default? And then, on the per-project fixes you mention above, how do I go about "replacing the plug-ins with the appropriate version"? They are, after all, the default plugins that came with the install. Where would I find other more appropriate versions? Again, my re-installation process was a "clean" one. So all traces of previous installations had been wiped from Registry and all, as directed. So where would the "confusion" now stem from?
  23. Well, that is possible. But I have CbB pointed to my custom VST(2) folder as well as the separate default VST3 folder, and all my other VST2 plugins were seen. However, now the project in question is, in fact, loading those VSTs. I guess it just took a few scans to see them...? I don't understand that, but I'm not complaining. I didn't realize the migration issue with iZoptope. By that, I see that you mean that CbB's ability to choose the better of multiple versions of a plugin as chosen in Preferences/File/VST Settings will not function with iZotope plugins. NOW, the remaining issue with this project (and others) is that, upon opening I get the attached message about those few included CbB plugins which, in my case, were installed automatically by CbB into both the /.../Cakewalk/Shared AND my custom VST folder as indicated when choosing from the pull-down menu in the window. The items in the two locations have different CLSIDs and the window seems to indicate it doesn't know which to use. It also seems to not matter which one I choose, however, and simply clicking "OK" allows me to continue as usual. This is an issue I have noted elsewhere here, but it was one that I thought my clean re-installations would remedy. Should I just remove the duplicate dlls? Why does Cakewalk install them in both places if it on confuses itself? Along the same lines, should I just remove the "duplicate" VST2 versions of the iZotope plugins in the above original issue in order to force VST3 usage in their case?
×
×
  • Create New...