-
Posts
4,384 -
Joined
-
Last visited
-
Days Won
5
Everything posted by David Baay
-
How do I revert to the previous version of Cakewalk Sonar
David Baay replied to ccondon23's topic in Cakewalk Sonar
By any chance do you have a large .zip file stored on your desktop or in any path that that Sonar might be touching? If so, try moving it to another folder or another drive entirely. More generally, check disk activity in Windows Resource Monitor and see if any large file is being read. -
Sonar VX64 is so good, but what about PX64??
David Baay replied to Guillermo Diaz's topic in Cakewalk Sonar
If you had any paid version that included them you should still have them or can re-install...? -
Comping with multiple lanes really needs to be done in the Track View and, as recently discussed, is not well-suited to working with MIDI. Because MIDI is fully editable in ways that that audio is not (though Melodyne gets you pretty close), it's generally easier to make the necessary edits to one decent take (or maybe a compilation of several sequential takes) than to try to piece together a performance from many parallel takes.
-
move Feature Suggestion: "Move clip in track"
David Baay replied to Mauro Gaspa's topic in Feedback Loop
Move to Folder is two clicks and doesn't include specifying whether to move or copy since the latter is not possible. To move/copy clips you'd either need a third click or two diffent menu options for Move to Track and Copy to Track. Then at some point you're probably going to want to be able to choose wether to move/copy clips in multiple tracks to one track or to multiple tracks with the same relationship. This option and more are already covered by the Paste Special dialog. I suppose the value of saving a click or two and not having to touch the keyboard with a no-frills context menu option might depend on how often you use it. My workflow would not benefit meaningfully. -
I can't reproduce a crash adding Spire VST3 as an Instrument track to a project that already has a Spire VST2 Instrument track. But your description of adding Spire with only the MIDI source would not create a Synth audio track to host the output of Spire VST3 in the rack. If you do that manually and then make the two tracks into an Instrument track after the fact, do you get a crash at any point?
-
Not sure how you reached that conclusion. Admittedly I don't normally do a lot of synth automation but I have a number of projects that do, and they are working fine and have been for years. As a sanity check, I also just added some filter and LFO automation to the Spire VST3 test that I created for my reponse to the OP in this thread and it's working fine as well. The Serum demo only installs the VST2 so I can't test that one. I see that CW Support is looking into your issue with Serum. Somehow I doubt the reponse will be "Sorry, we haven't been fully supporting VST3 for the last 10 years but we'll get right on it." I kind of liked the results of my test so I'm attaching it for your listening pleasure. Spire VST3 Parameter Automation Demo.mp3
-
A quote from my "MIDI Comping Challenge" post back in 2013 on the old forum (from a super-secret members-only subforum [wink, wink, nod, nod]): "Ultimately, though, I think the answer is that you just can't (and don't need to) comp MIDI in the same way that you comp audio, and that the classic methods of editing MIDI - fixing bad pitches, velocities, start times and durations directly and selectively copy-pasting where needed - are likely to work better in most cases. But since the tool exists, and I'm a MIDI guy, I thought I should give it a go. Maybe over time it can become smart enough to work as seamlessly and intuitively as audio comping."
-
I do everything in sound-on-sound mode with manual lane-muting as needed. I also seldom use loop recording as it can also be unsuitable for MIDI recording because if you hit a note a hair early at the end of one take instead of the beginning of the next, it gets truncated. Another place where a little AI is needed.
-
I've answered this question in the past, but maybe not for you. The assumption when comp recording is that a new take is intended to replace some or all of the previous takes in that that were presumably inferior in that section, so it automatically makes splits in all the other clips and mutes them. If you subequently decide that one of the earlier takes is in fact superior in that section, one click promotes that other clip. If only one part of it is better than some previous clip, you can always swipe with the Comp tool to break up the section further and promote the appropriate clips for each. The automatic splits are just intended to facilitate the work of replacing not-so-good material with better material. A long time ago, not too long after comping and comp-recording was implemented, I posted a "Take the MIDI Comping Challenge" demo project that had a set of raw takes with no comping and a comped set in another track showing the goal. That goal was achievable only by an excrutiatingly complicated series of comping moves, but was easy to obtain by manually editing MIDI the old-fashioned way. One of the Devs chimed in confirming my conclusion that the Comping workflow was not intended for MIDI and was generally not suited to it in many cases. As for swiping (or Ctrl-clicking selected clips) with the Comp tool to heal the splits, my recollection was that this would work for MIDI if you had Non-Destructive MIDI Editing enabled so that the clips are abutting. If NDME wasn't enabled, the empty space between notes would be cropped away so the clip boundaries were no longer abutting and couldn't be healed. That said, I just checked this and it already wasn't workng in Platinum 17.10 so either it never worked and my memory is faulty, or it got broken way back. I wouldn't have noticed because I never try to Comp MIDI. 😜 EDIT: MIDI comp split healing worked in X3. IIRC, that's when comping was implemented.
-
Cool. Glad to help. FWIW Sonar now has a function to Backup/Restore Settings that basically includes all of Preferences.
-
move Feature Suggestion: "Move clip in track"
David Baay replied to Mauro Gaspa's topic in Feedback Loop
Right-clicking, selecting Move or Copy and specifying a destination track is at least two clicks as well. This is potentially only marginally more efficient and not worth crowding the context menu with more options in my view. -
Make sure you have 'Use ASIO Reported Latency' checked under Record Latency Adjustment in Preferences> Audio Sync and Caching. This corrects for Input Latency automatically and should generally be enabled all the time as it is by default. usually a small Manual Offset it also needed to get sample accurate compensation, but you're not likely to hear that small error easily. Even missing the ASIO Repoted latency adjustment would cause a lot less than half-second delay which makes me think some plugin delay is involved. EDIT: Your screenshot suggests you're using WDM driver mode or maybe even WASAPI, try switching to ASIO under Preferences > Audio > Playback and Recording.
-
Not seeing a problem with the demo VST3 I installed relatively recently - v 1.5.17 build 5324.
-
move Feature Suggestion: "Move clip in track"
David Baay replied to Mauro Gaspa's topic in Feedback Loop
Or select the clip, use whateve shortcut you have bound to set Now=From (if you don't, bind one; it's indispensible), focus the target track and Ctrl+C, V or Ctrl+X, V as needed. -
Are you using an outboard ASIO interface? These often have a physical Direct Monitor button but sometimes it can be in a mixer/console app included with the interface. If you're using onboard audio it would be in the settings if supported. If the delay is actually a full half-second, that suggests a PDC -inducing pluging might also be involved. I see in your screenshot that you have some aux tracks which may be involved. On re-reading, I'm a little unclear what this double-negative construction is saying, but I think I was right to interpret it as "Until I disable Input Echo"...?
-
Hmmm.... okay. A couple of things: I see now you're talking about Region Muting clips (a.k.a. Mute by Time) in the TV as opposed to muting notes individually in PRV mode of the TV or muting whole clips. But that doesn't really change things. The bottom line is that clip-muting (whether whole clips or regions) and note-muting are two different methods of muting MIDI and they are not mutually exlusive. If you mute a note(s) both ways, you have to unmute it both ways to have it become fully visible and audible. I think that explains your 'unexpected' cases (EDIT: other than the 'hard to see outline' issue which I agree needs to be addressed). You're expecting the two methods to use the same mechanism and to display the same, and they're not by design.
-
Comping and Comp-recording is really not suited to MIDI because you can't split overlapping MIDI clips and have the start of one note cross-fade into the end of another smoothly as they would with audio. The truncation is inevitable in the absence of some fancy AI to preserve note durations across split points and glue notes that are on the same pitch. With MIDI you really just need to record sound-on-sound and do the editing manually. Even with audio if you split a note in one lane that isn't in the other lane, you're going to get some truncation. Comp-split and punch points need to be chosen to avoid this. I should add that nothing is really being lost as Comping is all done by slip-editing. If you heal the splits or move them to reveal the MIDI that's been cropped out of existence, you'll find it's all still there.
-
Likely your interface has Direct Monitoring engaged so you're hearing both the direct signal and the slightly delayed input-monitored signal from CbB due to interface latency. You just need to disable one or the other. If you aren't monitoring with track FX, you might as well stick with the Direct Monitoring through the interface.
-
Changing buffer size suddenly does nothing
David Baay replied to steve trusty's topic in Cakewalk by BandLab
It's most probable you've added some plugin that has a big look-ahead buffer requiring Pluding Delay Compensation. If it isn't on the track you're recording or on a bus in its path the output, you can enable the PDC [Override] button in the Mix module to temporarily override delay compensation on Input Monitored tracks. Otherwise, if it is in the path of that track, you'll have to disable or remove the plugin. BTW Sonar has a feature not available in CbB that allows you to hover over active plugins to see how much delay they're adding, if any - very handy. -
@Scott C. Stahl Yesterday, I tried loading the project I had resaved from CbB wth a couple changes (including unlocking screenset 1 so I could save layout changes) into Sonar. It was still hanging on "Loading tracks and clips..." , but I walked away without killing it, got busy with other things, and discovered this morning that it had finished loading successfully at some point. I have no idea how long it took but, as Sasor's post suggests, it does seem to be more of a load-time issue than an actual load-failure. With that understanding, I saved a version with all the audio clips deleted, and found that it loaded promptly. Interestingly, just Archiving tracks was not sufficient. It sounds like msmcleod has this on the run already, but I might experiment with more selectively deleting clips in certain tracks or bouncing/freezing their edits (especially Melodyne) to see if I narrow down the specific source of the trouble. Of course this is all happening with 'dummy' flatline audio replacing the actual audio files, but that doesn't seem to have any bearing.