Jump to content

David Baay

Members
  • Posts

    3,319
  • Joined

  • Last visited

Everything posted by David Baay

  1. I should add: If you really need to paste rather than drag, snap the Now time to the start of the selection, hit the shortcut for Go To (mine’s non-default) change just the measure, Ok and paste. Go To defaults to current Now time so the beat:tick will be correct.
  2. Assuming you want everything to be on their respective bars/beats as well as their absolute start times, you need to do the following (after aligning the first clip to the video): - Snap the Now time to the beginning of that first clip (assuming it's cropped to the first audio transient), and SM/BAN that point to the nearest measure (probably 2:01:000). Don't worry that this is going to temporarily throw the timeline wildly out of sync with the rest of the project, initially. - If there is a clip in the project starting at some known bar, snap the Now time to that clip and SM/BAN it to the bar it should be hitting (+1 if you started at 2:01). If there are no easily-found audio/MIDI 'landmarks in the the piece, play the project, count out 8 measures, and stop the tranport near the downbeat that should be 9:01. Tab to the downbeat transient (or MIDI note) or visually set the Now time there with snap disabled, and SM/BAN that to 10:01 (assuming you started at 2:01). - If the audio was recorded to a click, the whole thing should now be in sync with the timeline. If it varies, you can set additional points as needed to get the timeline in sync everywhere. - If you want the first measure to be at the same tempo as the first measure of music, you can set a matching tempo at 1:01:000 without affecting anything that happens after the point you snapped in the first step. The one issue I foresee is if the start time is very shortly after 1:01:000, CbB won't be able to set a high enough tempo for the first measure to bring 2:01 back to that absolute time. In that case, you might need to set the meter of the first measure to 1/4, and change it back to 4/4 (or whatever it is) at 2:01.
  3. Set the To/By switch in the snap module to By. Then things snap 'by' the snap resolution from wherever they are.
  4. Seeing "retrim" in your sreenshot made me do some Googling. Had never actually taken the time to research much about SSDs. Haven't read the whole thing, but found this article to be accessible and nicely illustrated: https://www.techspot.com/article/2600-ssd-trimming-explained/
  5. Whether you hear a single dropped buffer depends on the material. I can often hear the resulting click/pop from a single late buffer pretty clearly on a soloed track in a project that's pushing the limits at the current buffer size. But you don't need to worry about what gets exported in any case as offline rendering is not subject to the processing time constraints that lead to late buffers when playing back in real time.
  6. Back before SONAR X1 was released, the default shortcuts for From=Beginning and Thru=End were Ctrl+F9 and Ctrl+F10. I restored these shortcuts when they were removed because I had over 10 years of muscle memory invested in them. I did the same for From=Now (F9), Thru=Now (F10), Go to From (F7) and Go to Thru (F8). At the time, there were no shortcuts assigned to any of these by default so far as I know. I was never aware of Shift+Alt+F6 and don't know when that might have been implemented. I suspect it's a one-off, and default shortcuts for the other permutations mentioned above were never re-defined. I recommend you create your own for all of them using whatever key combos make sense and are not already assigned to something else you need.
  7. Mine started doing flaky stuff like that before it went completely belly up - mainly just not producing any output, even with a firm key press.
  8. "I was wrong; it's actually badass." 'nuf said. My only complaint is that watchers might be more convinced of its badassness if he showed something like the Gloss EQ flyout instead of Sonitus compressor and the Step Sequencer instead of Step Recorder.
  9. @Bill Phillips I realize this is an old thread, but found it interesting because I have long recommended taking a binary approach to isolating a problematic plugin as the page you linked describes. But with CbB, you can launch the project in "Safe mode" by holding Shift as you click it from File > Open, and then choose to enable only half the plugins as you are prompted for each. This can still take some time, but at least you only have to worry about the ones that are actually used in the project.
  10. Seems your keyboard is sending some non-standard character code or maybe some third-party app is modifying it...? I was just using Normalize (to -12dB) yesterday, and checked Transpose just now, and I don't see this issue with either of them. Minus key in the top row enters a "-", and minus key on the Numkey pad decrements the current value by one.
  11. Ctrl+C ?? The question was how to move the clip; so, yes, cut-paste.
  12. Ctrl+X, select the marker in the Markers View, Ctrl+V.
  13. That's been my main use also since I'm not much of a soloist... but neither is BiaB as it turns out. 😜
  14. Good thought, but this thing just doesn't expose audio inputs in CbB no matter what is or isn't associated with it in the way of tracks.
  15. Intantiating a VST instrument as an insert FX in an audio track is supported in CbB for compatibility with legacy projects that used that architecture before the Synth Rack was implemented, but it's not the preferred method now, and can actually lead to issues such as stuck notes among other things. You can insert a synth in the rack without associated tracks being created either by clicking the + button in the synth rack or by Insert > Soft Synth in the main menu and unchecking the options to create tracks. When an Audio track has a synth output assigned as Input, it becomes a Synth track. Or you can insert an 'Instrument' track which is a combined MIDI an Audio track with an associated synth connecting them. An Instrument behaves like an Audio track and shows mostly Audio controls (other than the Input which is a MIDI port/channel). You can access all the 'hidden' controls of an Instrument track via the MIDI and Audio tabs at the bottom of the Track Inspector. Instrument tracks can help simplify your project. You can convert existing separate MIDI and Synth tracks (one of each) into an Instrument track by right-clicking one of the selected tracks and choosing Make Instrument Track. And, finally, note that it's also possible to create one Instrument track per output of a multitimbral synth. You can read up on all of this in the Ref. Guide.
  16. The Readme says: - VST3 plug-in now declares inputs as "side-chain" (aux) to work around certain lame DAWs But I do not see a sidechain input being exposed in CbB when instantiated as either a Synth or an insert FX though the plugin properties show 'Max used inputs: 2' which would usually indicate the plugin has a sidechain input. Other VST3 instruments I have with sidechain inputs work fine, so it seems to me it's TX16Wx that's 'lame'. 🙊 Old threads I found about this suggest it has only ever worked with Reaper, but they may be outdated and the sidechain works with some 'lame' DAWs, but not good ones like CbB. 😁
  17. No, but I do know that Cakewalk have never excluded/included individual features or functions in the different 'tiers' of SONAR. They have only ever been differentiated them by the amount of bundled content, and I expect that to continue.
  18. Yes, that makes sense. You might want to go into the Registry and remove that virtual ASIO device for good measure. Just delete the FL Studio folder under HKEY_LOCAL_MACHINE\SOFTWARE\ASIO There is no risk associated with doing this; I do it all the time for Realtek and other apps that add these bogus drivers, but if you're concerned, you can export the registry key before making changes.
  19. Utilities > Cakewalk Audio Finder Tool (CWAF) will also show you what files are used by which projects. It will likely show that all the clips in the Audio folder are in fact referenced by the project. Most likely there are tiny slivers of clips left over from deleting with incompete clip selections. Unfortunately those can be hard to find in a complex project. If you know which files should no longer be referenced by name, you can select each track/lane one at time, right-click and choose Associated Audio Files. If you see one of the 'unused' file names in the list, you can start searching that track/lane for it. If you do a partial selection of a track/lane - even an apparently empty region - you can right-click and choose to see Associated Audio Files and it will show if there's something there or more than the one file you expect. Since it's possible (though unintended) for clips to be layered on top of eachother in the same lane, you'll need to check regions with visible clips as well. Once you narrow down the area, you can zoom in and scroll around to find the troublemaker(s). If the problem involves layered clips, you might have to move 'known' clips to another lane temporarily to find hidden ones. I realize this is a pretty ugly solution, but it's the only way I can think of to track them down.
  20. As noted, it's showing only a 240-sample RTL for a 256-sample buffer. That's just not possible. With no hardware latency, the I/O buffers alone will give you 512 samples round-trip latency. It's typical for hardware/firmware/drivers to add 200-400 samples to this. Your own video shows a reported RTL of 742 samples with a 256-sample buffer. That's likely missing the ADA converter latencies which will typically add another half to a full millisecond each way although some manufacturers are better about reporting everything to the DAW. I'm not sure why the RTL in the screenshot was initially so far off the mark. The 829-sample Reported figure mentioned later by the OP sounds more like it.
  21. Yes, and that's more on the order of what I would expect for a 256-sample buffer on a USB interface. The Total Round Trip of 240 samples in your screenshot made no sense.
  22. TTS-1 is a full 16-channel Multitimbral GM instrument. Like all GM instruments drums are on channel 10 by default. All other channels default to piano, but can be changed.
  23. Sorry. Glanced to quickly; thought you were on the Audio Driver page. MME is correct for most MIDI interfaces. As mentioned, Manual Offset is on the Audio > Sync and Caching page. Easiest way to set it accurately is to download and run the free CEntrance Latency Tester with an audio cable patched between an input and an output on your interface. Then set Manual Offset as the Measured Latency minus Reported Total Round Trip. https://centrance.com/driverfolder/CE_LTU_37.zip
  24. How did you go about that, exactly? So far as I know, SI Drums offers only a basic kit with no percussion or other sounds. It's not a General MIDI instrument. EDIT: TTS-1 offers a full GM drum kit, and there are many free drum synths available that will include at least some percussion.
×
×
  • Create New...