David Baay

'Screenset' is catchier. ;^) There's a module in the Control Bar. https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=ControlBar.09.html

I thought the point was to do everything from the keyboard...? After D, D, using keyboard cursor keys work to scroll the PRV (or zoom with Ctrl).

Or you can just hit D, D to quickly toggle the multidock closed and back open. No?

I don't recall right offhand if X3 allowed stretching MIDI clips by dragging - I suspect not. But Cakewalk by Bandlab does, is free, and has many enhancements fixes over X3. You should get it: https://www.bandlab.com/products/cakewalk Otherwise, the old-skool methods are: Process > Fit to Time (if you know where you want it to end) or Process > Length (if you know how much longer/shorter it needs to be as a percentage of its current length)

D'oh! Fixed.

A beat is always a quarter note in Cakewalk. So in an 8th-note meter,the point half way between two 'beat' markers is .25. I am pretty confident this goes back to the inception of the function. Here's a thread from 2013 (three years before Platinum) in which I mentioned it: http://forum.cakewalk.com/tm.aspx?m=2921804 "(note that fractional beats are entered as decimal values not ticks, so 02:480 is 02.500)."

Clean Audio searches for projects that use the audio in the specified folder. The Global Audio Data folder doesn't have a project folder as a parent, so the only option in that case is to search everywhere. If you just want to clean up one project, and get its audio into a per-project folder, the thing to do is to open the projectin Cakewalk, Save As to a new project folder, and enable the Copy All Audio checkbox. Only audio that is actually referenced in the project will get copied. To clean the Global Audio folder of all audio no longer referenced by any project, use the Cakewalk Audio Finder tool. I do all my 'cleaning' with this tool as it's more powerful and flexible in terms of telling you what's what, and giving you options. See post #5 in the below thread for a 'primer' I wrote on how I use it: http://forum.cakewalk.com/Clean-Audio-Folder-still-broken-I-see-m3023320.aspx#3023681

Set Measure/Beat at Now uses decimal beat fractions. An 8th is .500. EDIT: Has forever worked this way, incidentally.

Glad to help, as always. My professional customers should be so appreciative. ?

As Chuck suggested, you can Ctrl+Shift+A to deselect everything. Alternatively, I've found that if you hover in the very narrow band of the timeline below the MBT scale, you won't get the selection marker tool cursor popping up when nearby.

Sounds like maybe you have ASIO4All installed...? I would uninstall it since you have a good interface with native ASIO driver. If that's not it, I would have to do some Googling. EDIT: Found some posts on the old forum indicating ""Generic Low Latency ASIO Driver (1 in 1 out)" is a Cubase thing: http://forum.cakewalk.com/Does-Anybody-Know-A-Better-Way-m3040170.aspx

Right-click > Split > Split at Selection option > Enter/OK Or hold Alt with the Smart Tool to get the Split tool and drag-select the region to be split out.

Glad to help. PM me a link to anywhere I can download. MS OneDrive or other cloud file store that you might already be using would probably be best, but Soundcloud is fine if it allows direct download. Or even your friendly, neighborhood Bandlab sharing facility. ;^)

Cool. So you have your Timing Offset back to zero, and everything is good? If 10.9ms is a round trip time with ASIO buffer at 128 samples, you might have to shell out to find a USB interface that does much better. I use a MOTU PCI-based interface that runs smoothly with a 32-sample buffer, and delivers an actual measured RTL of 2.3ms. RME is the only company I know of that gets close to that with USB. 8-10ms with a 128-sample buffer is more typical (3ms each way for the I/O buffers plus 2-4 ms for A/D/A conversion and 'hidden' firmware/hardware buffers.

A few thoughts: First, I agree that there is really no better way of approaching the arranging process, except that it might be simpler to use lanes of one track for the different sections of the original guitar part, rather than different tracks. Second, you might want to consider getting the timinng locked in first so that you can then copy tempo changes when duplicating sections, rather than having to map the tempo multiple times. While Melodyne and Cakewalk's own Audiosnap tempo mapping features can be helpful. I still find that manual tempo mapping using Set Measure/Beat At Now is more flexible, more precise, and ultimately doesn't take much more time (and possibly less) vs. all the massaging of tracks that may necessary to get the 'automatic' process to deliver the desired result. And, yes, once you have a good tempo map, you can 'smooth' or completely 'flatten' the tempo varations by enabling Audiosnap Clip Follows Project in Autostretch mode on the original track(s), and then adjusting or deleting the tempo changes that were needed to make the timeline follow the audio. If you're only going to add MIDI parts, it's easier to leave the tempo variation intact and quantize the MIDI to the variable tempo, but if you're going to record audio, it can be tough to follow someone else's tempo changes, and harder to tighten up the timing after the fact without introducing undesirable audio artifacts. That caveat applies to flattening the tempo of the original recording as described, but if it ends up being only one part in a multitrack mix, the artifacts will be masked to some extent, and it will making recording more parts with good timing much easier. I've posted many times about using Set Measure/Beat At Now to align the timeline to audio (or MIDI) on the old forum.cakewalk.com, and you can Google my old username, brundlefly, with 'SM/BAN' against site:forum.cakewalk.com to find them. It's pretty straightforward but there are some extra tricks for dealing with free-form or rubato intros, pick-up beats, rhythms that deliberately hit off the main quarter-note beat, etc.. This is the real world stuff that the automatic processes don't handle well. If you're interested in trying this, the best way for me to explain the process might be to share an example of what you're starting with, and I can map it (or part of it) for you, and tell you the steps I took.

Does it happen if you play the whole thing through from the start without interruption or looping? My first guess would be some plugin has unsynced randomness in realtime that does not occur (or occurs less frequently) with offline rendering. You might try bypassing some FX to determine the culprit, and then Google for similar reports on the web at large or the vendor's forum for possible solutions. You migth also experiment with different ASIO buffer sizes, and see if maybe that's a factor. If you have a non-zero bouncebuffsizemsec= parameter value specified in AUD.INI that's different from your real-time buffer size, that might explain why the issue doesn't manifest when exporting.

Okay, so here's my best guess as to what's needed: By default, Cakewalk is set to 'Always Echo Current MIDI Track' so that when you play on your controller keyboard, you hear the soft synth assigned to the currently focused Simple Instrument track. But then that's the track that will be displayed in the Piano Roll, hiding others by default. So, to see one track in the PRV while you perform on another track, you have several options: 1. Click the Input Echo on the instrument trakc you want to hear to force Input Echo on even when the track is not focused. This will alow you to focus the drum trakc in the PRV, and still be able to hear the instrument your playing. 2. Show both tracks in the PRV together by Ctrl selecting their track numbers in the PRV tracks pane at the right. The unfocused drum notes will be grayed out but still visible so long as you havethe vertial zoom set correctly. Things get more complicated if you have a durm map on the drum track, but the concept is the same - keep from losing sight of the drum track's MIDI when the focus is elsewhere. 3. Open the drum track in a PRV, and lock the view so it doesn't change when the focus moves away. There are probably other options, but these come immediately to mind. I kind of like option 2 because it will let you see where your live input notes are landing relative to the existing drum notes as Cakewalk shows a 'confidence recording' preview of the new notes in red. Hope that helps, or at least sheds some light on concepts that are good to know in any case.

This is your problem. That's 35ms at 44.1kHz to get the sound out of the Minilogue through Cakewalk and back to your monitors. Most people would find that to be an 'unplayable' amount of latency for performing in real time on a keyboard. If it's not, it's because your monitoring directly or closer to directly than through Cakewalk. But you'll be performing to a metronome click, and recorded audio or soft synths that are late vs. the MIDI grid by the output latency, so your recorded MIDI will be laid down late, unless you use a Timing Offset to compensate. But even when your recorded MIDI is on the grid, the reponse of the external hardware synths is going to be delayed by the full round-trip latency, and sound late relative to the metronome and playback of existing audio that is only delayed by the output latency. Timing offset will allow you to compensate for these dalays either on playback or on recording, but not both, because the sync error is different depending on what you're doing. The bottom line is you need to get a harware interface with native ASIO drivers that can operate without pops/clicks/dropouts at a total round-trip latency down around 6-8ms (or less). I would think the Behringer should get close to that without Voicemeeter in the picture. I don't know much about it, but any layer of software you put in between Cakewalk and your interface's native ASIO drivers can only cause trouble.

1. You can change the selection range by directly dragging the start/end marker rather than setting the Now time and then using another shortcut to set From/Thru= Now 2. You can click and drag a time selection to a new start time, rather than having to re-select the same range somewhere else. That said, I've also be a little frustrated by having the selection marker cursor get in the way of clicking nearby to set the Now time. Two ways to deal with this other than de-selecting all are: 1. Enable Left/Right Click sets Now in track view options, and click in the clips view to set Now (loses selection). 2. Click in the very narrow section of the timeline below the scale where the selection cursor doesn't appear

One long ago fix for this with SONAR was to 'repersonalize' by holding Ctrl+Shift while launching.

Yes, if track gain and volume controls remain at 0dB, the input and output meters will initally show the same thing. But that doesn't generally last for long because the input level that gives you a good signal to noise ratio from your external sources, and a good input level for FX to behave nominally in the box, is probably too high a level to mix with other instuments. So the output volume is almost always going to be pulled down from what you recorded at some point, and unless you set the Playback meters to be pre-fader, they're going to reflect that.

I was responding to: I see now that "it" in that sentence is referring to the low input level, not the difference between input and output metering levels.

No, I meant it has no effect on the change that occurs when you switch between armed (record meters) and disarmed (playback meters). The input level at the interface will be that same either way. So something is happening inside Cakewalk to make the metering change.

Collapsing it doesn't completely close the view. If you undock it and close it, the check mark will clear. But you should probalby be able to close it by unchecking it in the menu, which isn't possible.

Setup of the DI box shouldn't affect what shows in your meters in SONAR when armed/disarmed. All that matters is the level at the interface input. Cakewalk will record that level regardless of any settings (unless the interface mixer applet is modifying it). And it will play back that level so long as no gain or volume changes are applied at any level (clip gain, track gain, FX I/O gain, track volume, bus gain/volume). A Pan law with -3dB/-6dB center can lower the playback level if you have mono interleave set on the track, but won't ever raise it. I recommend you start with the simplest possible record and playback configuration with input monitoring, making sure your record and playback metering settings are identical (except playback meters will probably be post-fader - fine so long as Volume fader is at unity). Then record single transient pulses and look at the numeric peak indicator as well as the meter while you make external/internal changes one at a time to see what effect each has.