Jump to content

Tim Elmore

  • Content Count

  • Joined

  • Last visited

Community Reputation

17 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Before using Melodyne, I copy the original clip to another take lane (in the same track) and mute that original. After applying Melodyne to the duplicate, I can easily revert to the original clip at any time, and there is no extra track.
  2. For over a year, I have been using scook's method for RX8 (RX9 should work the same). It requires a one-time setup. After setting it up using scook's instructions, use the following procedure to edit a clip in RX8: 1. In the CbB Track View, select the clip to edit. 2. In the CbB Utilities menu, select "RX8." RX8 opens, with my clip ready to edit using any of the RX8 features, including the spectral editing display. 2. Perform the desired edits in RX8. 3. When finished editing, press ctrl+s to save the changes (I usually leave RX8 open). 4. About two seconds later, CbB asks if I want to reload the modified clip. Click OK. Done
  3. When I am editing, I typically have the Track View snap interval set fairly coarse, such as one measure, and the Piano Roll View (PRV) snap interval fairly fine, such as 1/16 note. I start with snap enabled for both Track View and Piano Roll View, but they are set to different snap intervals, and they respond accordingly. To toggle snap on or off, I use the N key, which is assigned to Snap Toggle Extended (I think that was actually the original default). The N key simultaneously toggles snapping for both Track View and PRV, even if they are set to separate snap intervals. I never use the PRV control to disable snapping. Whether I am editing in the Track View or PRV, the N key is my single keystroke to toggle snapping on or off. Is this the functionality you are looking for?
  4. That may or may not have caused the unintentional pan change in the OP's particular case. But you brought up a very good point, and the mouse wheel behavior you are proposing for Console View is exactly the way it works right now in Track View. Because of this, I have never accidentally changed a control with the mouse wheel in Track View, only in Console View. You may want to start a new thread to focus on this particular issue.
  5. I had that problem once when I accidentally enabled input echo for all tracks at once. Is input echo enabled only for the track you are recording? Also, is the volume excessive only in your monitoring, or does the track meter also show a very high level?
  6. To stay within one take lane in Overwrite mode, try the following settings:
  7. To test this (in version 2022-06), I created three tracks: Track 1: A regular audio track. Track 2: Auxiliary track, using patch point named "My Patch Point 1". Track 3: Auxiliary track, using patch point named "My Patch Point 2". Then, in track 1, I clicked the pull-down to select the output. The following output options appeared: My two patch points are included in the output options list. Is this the feature you are wanting to see?
  8. Could you show a screen shot of the track? It would help if we could see what you are seeing. Also, an additional screen shot of the track with take lanes displayed would show us exactly how the takes are stacked. That may help us figure out what is happening.
  9. This signal flow diagram from the Cakewalk documentation may help you visualize the signal routing: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.07.html
  10. The "W" button in the control bar is not actually a toggle button. It doesn't have a mode to keep me from turning on write enables for various tracks. I can do that at any time. This all makes better sense if I consider the button in the control bar as simply a reset button that cancels all write enables that are currently turned on. It is a shortcut to let me cancel all write enables with one click instead of having to click the "W" button in each track individually.
  11. Press the "Pause/Break" key on your PC keyboard to toggle between slow and fast scroll updating.
  12. The same here. I always click and drag or insert values, except when I unintentionally change a value by trying to scroll while the mouse happens to be over a control. The one second delay they recently added can sometimes help, but I really wish there was a preference option to disable the mouse wheel from setting control values. Or, at least have the mouse wheel behave the same in Console View as it already does in Track View. In Track View, the wheel can adjust a control value only after the control has been selected by clicking on it. I would love to have that behavior for Console View , even if I had to go to Preferences and set it as an option. I never have wheel/control accidents in Track View.
  13. It is correct that the Revert action is just one level deep. It cannot step back through multiple changes. However, the behavior is not as simple as I expected. Using the current CbB version, 2022.02, I get the following behavior in Console View: 1. Move the mouse over a volume slider. Move the mouse wheel smoothly to adjust the volume up or down. Wait at least one second and then right-click the volume slider. Select the "Revert to" option. The volume reverts to the original setting. That is what I expected. 2. Move the mouse over a volume slider. Move the mouse wheel to adjust the volume up or down. Immediately (less than one second later), right-click the volume slider. The "Revert to" number will show the new setting, not the original. Choose it anyway, and it will revert back to the original setting. 3. Move the mouse over a volume slider. Move the mouse wheel to adjust the volume up or down. Immediately (less than one second later), move the mouse wheel again. Revert the setting. It will revert to what the original setting was before moving the wheel the first time. 4. Move the mouse over a volume slider. Move the mouse wheel to adjust the volume up or down. Wait at least one second and then move the mouse wheel again. Then tell it to revert. It will revert to what the level was before moving the wheel the second time. Using the Revert function can help recover the original setting after an inadvertent change, but it requires a bit of care. When I try to scroll the screen and it doesn't move, I have to resist the impulse to move the mouse wheel back and forth wondering why. Instead, I must immediately look at which control the mouse is over (hopefully I didn't move the mouse first!) and then revert the control. For me, I have found it useful to frequently save the mix scene so that I can recover all the settings reliably.
  14. One way to make FX scrolling smarter would be to do this: 1. If the mouse cursor is over the FX bin and the bin contents are taller than the FX bin rectangle, then the wheel will scroll the FX bin. 2. If the mouse cursor is over the FX bin and all FX contents are already fully visible (no need for scrolling the FX bin), then the wheel will scroll the entire Track Pane. Either way, the UI would respond to the wheel, and the behavior would be no mystery even to those who are new to this.
  15. Revert works great as long as I realize right away that I inadvertently changed a control. Another safeguard I take is to save the scene after making any important control changes. This saves all control settings, even the ones inside plug-ins. I have the Save Scene button on my control bar.
  • Create New...