Jump to content

tonemangler

Members
  • Content Count

    120
  • Joined

  • Last visited

Community Reputation

35 Excellent

Recent Profile Visitors

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

  1. This is how I do it, with the take lanes hidden I drag select, right click and 'Bounce to Clip(s)' and then open the take lane view and right click the parent track and choose 'Delete Empty Take Lanes'. Usually when I finish a comp I don't need all those rejected takes. However, I always duplicate with events and archive the track before I 'Bounce to Clip(s)' just in case, this has saved me in the past. I make a folder called 'Archived' which is at the bottom of my project and I keep all duplicated tracks there. I don't know why but I prefer this method over 'Flatten Comp'. Cheers.
  2. Shift+G I am not aware of any one key combination that will do this, however under options you can configure Mouse Wheel Zoom Options. Personally I do not like simultaneous horizontal and vertical zooming but prefer only horizontal. Therefore I set vertical zoom to 1.000 and horizontal zoom to 1.500. You can set it to zoom at the Now Time or at the Cursor, but for what you want to do I would suggest Now Time, however you can experiment to see what suits you best. So with these settings you simply place the Now Time in the middle of the clip you want to zoom, press Alt+Mouse Scroll Wheel to horizontally zoom and then double click on an empty space in the track header for a full vertical zoom. This will fill the screen with the clip. Double clicking again in the track header will restore the vertical height to it's previous state. HTH Cheers.
  3. That works too, I've never used it before. More than one way to skin this cat!
  4. I believe the Slide function is only for moving audio and midi events and markers. The easiest way to do what you want is to select all tracks (Ctrl A), set Snap to full measure, engage Ripple Editing to All, and then simply drag the whole project by 2 measures. Afterwards make sure you disengage Ripple Editing. An alternative way is to select all tracks, click on Edit at the top, choose Cut Special, make your selections on what to cut (events and automation in this case), place cursor on the measure you want to paste, choose Paste Special and choose what to paste. Cheers.
  5. Maybe I'm stating the obvious here, but to select a region on a clip or an envelope you just click and drag on the clip or envelope, selecting on the timeline selects all tracks. I don't think this is a bug. It is very easy to make a selection and add nodes, simply click and drag on the envelope to make the selection and then move the cursor to the top of the clip until the icon changes to the envelope edit tool and then click and drag your mouse up or down. Nodes will be created automatically. This is a good tip that I also do sometimes, but TBH it's so easy to select a region and drag with nodes automatically created that I almost always do that. 🙂
  6. When I solo a track that has a send to a bus I don't have to solo the bus as well to hear it's signal. For example if I solo a vocal track with a send to a reverb bus I can hear the vocal and the reverb, I don't have to solo the reverb bus to hear the reverb. Solo Override seems to work correctly for regular tracks, but not for busses or aux tracks. Solo Override should not solo a track/aux track/ bus, that makes no sense. It should only prevent the muting of a track/aux track/bus when something else is soloed. However it seems busses do not mute when tracks/aux tracks are soloed so there is no need to engage Solo Override on them. That being said there are definitely issues with Solo Override when pertaining to busses and aux tracks.
  7. Instead of deleting nodes to create a more linear envelope you could use the pencil tool, in freehand or line mode, to trace over your controller generated envelope. However, as you say, it kind of defeats the purpose of using a controller. Jumps occur when no controller data is detected, so if you stop moving the controller at any time during the recording a jump will be generated. I'm not aware of a setting that will change this behaviour, however I don't use a controller so I could be wrong, someone with more experience may have a workaround. Good luck.
  8. If the backing track needs to be stereo you would need an audio interface with more than 2 outputs, however if the backing track can be mono then a 2 output interface will do. I didn't watch the whole video, but what I did watch indicates a scenario where a mono backing track is used. Mono Backing Track : When starting a new CbB Project there is a default of the following busses; Master, Metronome and Preview. Create a new bus called 'Backing Track'. Set it's output to 'Master". Now all audio tracks that are part of the backing track should be sent to the 'Backing Track' bus. Pan this bus all the way left and pan the 'Metronome' bus to the right. In the 'Transport Module' in the 'Control Bar' make sure the metronome is set to sound during playback (a playback arrow icon). Now feed the left (Backing Track) and right (Metronome) outputs of your interface to your in house mixer. Stereo Backing Track: In the 'Metronome' bus set the output to 3 or 4 of your interface. In Cakewalk that would be "left 'your audio o/p driver name' 3" or "right 'your audio o/p driver name' 3". Now send outputs 1 and 2 to the mixer for a stereo feed of the backing track and output 3 or 4 for a mono feed of the metronome. If you are not using the metronome for your click and instead have an audio track with the click recorded, simply send the click track to the metronome bus and do not engage the metronome to sound during playback. These scenarios assume you know the tempo of the backing track. If you need to find the tempo there are various ways to do that in CbB. I'll wait for a response if you need that info. Cheers.
  9. You can capture audio from YouTube using the loopback function. Loopback is simply taking the audio present at the outputs 1-2 of the Focusrite and looping it back into the loopback input drivers. In other words if the YouTube audio stream is present at the Focusrite outputs 1-2, then that audio can be captured by Cakewalk by BandLab using the input driver 'IN: Stereo Focusrite USB ASIO Loop 1'. Launch both CbB and YouTube. Create an audio track with it's input set to 'IN: Stereo Focusrite USB ASIO Loop 1'. Switch over to YouTube and start video. Switch back to CbB and hit 'R' for record on the audio track you just created. Good luck.
  10. Hello Rainer, firstly you should use the ASIO drivers from the Focusrite site as you noted above, and go to Windows Settings> Sounds and enter the Scarlett as your output device, that will tell Windows to use your Scarlett for YouTube. Loopback is for recording whatever you are hearing through the Scarlett (outputs 1-2). For example, after you have finished a mix you may want to record a stereo file back into your project, to do this create a new stereo track, choose IN: Stereo Focusrite USB ASIO Loop 1, arm the track for recording, press 'R' to record. Of course you could export the file and re-import which would be the same. Another example is if you want to convert a VSTi into an audio track. If after you programmed a bass track using a virtual synth and you want to convert it to an audio clip you can use the Loopback feature. First create a new audio track. Since this bass track is mono you can choose either the Left or Right Loopback, so 'IN: Left Focusrite USB ASIO Loop 1'. Solo the bass VSTi track you programmed, remember Loopback records the audio going through outputs 1-2 of the Scarlett, in this case it will be recording output 1 which is the Left Loopback. Arm the new audio track for recording and press 'R'. When finished you have a mono audio track of the bass guitar. You could also use the Freeze function for this. So any audio that is present at outputs1-2 can be recorded into CbB using the Loopback feature. This obviously means the outputs of your Master Bus must be routed to outputs 1-2 of the Focusrite. Cheers.
  11. Yes sometimes those digital gremlins play games just to drive us nuts!! Glad you got it sorted out.
  12. One way of doing this is to go to Preferences and set Nudge1 to 9.5 ms, and then perform a nudge back by selecting the clip and hitting the 1 in the number pad.
  13. There are several methods you can use to correct timing issues; Audio Snap, Melodyne or audio editing. Since a bass guitar, depending on how it's played, often may not have distinct transients and Audio Snap may have trouble accurately locating them, you would have to manually move and delete/disable transient markers to line up properly. Once this is done you can stretch the the offending notes to the proper timing. Once you are happy with the track, perform a bounce to clips to finalize. A smart tip is to duplicate the track and archive before you start as a safety precaution. The other method, which I find easier, is to insert Melodyne as a region effect, and simply use the time tool to move the blobs (notes) to the correct timing. There is a 'Quantize Time Macro' where you can select the offending notes or all notes and quantize them, however unless there are a lot of timing issues I would do it manually, just remember to either disable the snap to time grid icon within Melodyne (a small note in the upper right hand corner), or if you prefer you can set the time grid resolution to a specific value if you want the notes to snap 100% to the grid, at the cost of losing some human feel. The other method I use, if there are only a few timing errors, is audio editing. Split and trim the offending note, drag move to the correct time, and perform crossfades. To be honest this is the method I use most of the time. Cheers.
  14. This does sound strange, try right clicking the volume slider on the bus and disabling 'Read Automation' to see if automation might be the culprit. When right clicking on a fader/slider you are given the option to revert to the previous value, in your case you dipped the bus fader from '0.00 dB' to '-10.3 dB' and when you hit play for some reason the fader moved back to '0.00 dB'. When you right click the bus fader again it will give you the option to revert to the previous value which would be '-10.3 dB'. I believe this has something to do with control values you input when grouping tracks/busses. When grouping you can designate the range of a faders movement relative to other faders in the group, I've never used this feature however so I'm not 100% sure. I don't believe it has anything to do with your issue though. Another thing to do is check if you have inadvertently hit the 'Envelope/Offset Mode' button in the Control Panel, sometimes that can cause odd behaviour. Good Luck!
×
×
  • Create New...