David Baay

Selection determines what is included in the mixdown, and Source determines where in the signal chain the mix is captured for writing to file. If you want everything in the mixdown, you should select nothing, and CW will include everything by default. If you're getting silence, you must have a partial selection of the project (either tracks or time range) that does not contain any audio content. 'Entire Mix' is All hardware audio ports combined. This can be problematic if you have a headphone mix or something going to a second output pair. I recommend always choosing Buses as the source, and selecting just the Master bus.

I've done a ton of MIDI editing in the last week, including dragging/nudging large selections of notes and editing velocities, and have not seen any unexpected behavior. But all clips were independent. I just did some quick testing with linked clips and could not reproduce any error. Seems something is missing from the recipe or it's project specific or possibly dependent on some particular setting like having Non-Destructive MIDI Editing enabled (I generally don't). I also use the Blend Old and New setting for Drag and Drop. I would also suggest restarting Cakewalk and/or rebooting as it sounds like something might have become corrupted in RAM. But if you reproduced the issue with SONAR, maybe not. To me that also suggests it might be project-specific. If this dated back to SONAR and was a common problem, I would expect to have seem more reports of it,

So it was recorded from a real-time performance with a MIDI guitar controller or a pitch-to-MIDI convertor? If it really sounds that 'mechanical', I would expect more than just quantization of start times was done. In any case, the answer is "not really", especially if strumming was involved. As has been discussed many times, 'humanization' of hard-quantized (or even worse, mouse-entered) MIDI takes a lot of work and the results are unlikely to be fully satisfactory. I almost always keep unquantized archives of tracks/projects to avoid unrecoverable problems like this; shame on the producer for not preserving the raw performance somehow.

Only thing I know of that can definitely cause that is attempting export to MP3 in real time; real time streaming and encoding to MP3 have not been compatible in the past but I haven't re-tried it for a long time. Related to that, I can imagine that having too low or high an ASIO buffer might also cause problems with MP3 encoding since that is used as the default 'chunk' size for processing. If you've made changes ASIO buffer, that might explain variable results. If that's the case, setting an appropriate value for BounceBufSizeMsec could address it. Some interoperability issue with a particular plugin is always a possibility as well. And in any case of distorted output I always try disabling the 64-bit Double Precision Engine.

It probably doesn't "have"' to be, but it provides a way to open Arranger/Tempo/Video views by dragging with a mouse. I could wish for some narrow dividing lines and/or labels to make it clear where to drag to get which view and I do more often use keyboard shortcuts than dragging to open views. I wouldn't be against having an option to hide if completely.

I have kind of a mental block against spending more than $200 on any single transaction for music software... her name is Andrea.

Same boat. I put it off getting Kontakt all these years because I'm generally not that big on purely sampled instruments, and things like Prism and Alicia's Keys I had bought separately only needed the Player. But then I would occasionally see deals on interesting instruments that required Kontakt Full so I took the plunge getting it with a crossgrade deal from Morphestra last year. And now I went for Komplete mostly to get all the other synths that - like Prism - aren't just sample players, but have some life and character to their sounds. The standard package includes all but 2 of the 16 that are in Ultimate. But mostly I just have GAS this week. ;^)

I'm stumped, but it's definitely system-specific - not happening everywhere.

What if you disable Input Echo and change the inputs on the MIDI tracks to None? If that doesn't do it, It would be easiest to see a copy of the project to diagnose it.

Strange. Performance Module metering options are working as expected here on my laptop with Windows 10 Pro, and on my main DAW with Windows 10 Home. I don't have a good idea what might cause this other than dependency on some other CW config setting or interoperability issue with some third-party software/firmware/hardware. Doesn't seem to be a widely experienced issue, but I would guess most users are not changing the setting very often.

It's possible a project or template has somehow become corrupted in a way that's not visible from the UI. Rebuilding templates from scratch periodically is not a bad idea though I understand it could be a big (and error-prone) task in this case. Sometimes a project can be fixed just by rebuilding individual tracks and their routing. Even if it's a visible misconfiguration that you're just not seeing. sometimes rebuilding a track is the easiest solution.

Are you saying you have two hard-panned mono tracks that show similar output level at the track meters and play back balanced in real time, but when you export, the rendered file is not balanced? What are you using to listen to the export? Have you tried re-importing to Cakewalk or Audacity to confirm the levels are wrong in the file? If you're exporting 'Entire Mix' hardware bus levels could be off, but that would also affect live playback. Or you could have an unbalanced send to a second hardware output (e.g. headphone mix) that is getting included in 'Entire Mix' In any case, I recommend bouncing the Master bus to a new track within Cakewalk to understand better where the problem is occurring. If that bounce looks good, and the exported file is bad, then the problem is with your Source selection at export.

i think I understand the problem now. I often rehearse with tempo delay in the studio while the transport is stopped, and it syncs to tempo just fine with the transport stopped. But in the case of a delay, the timing of the taps is based on the time that audio arrives at the input so it automatically 'starts' when the first key is hit. This is not necessarily the case with a gate, and it sounds like the particular one you're using depends on the project clock to 'know' when to start, rather than the arrival of the first audio transient. You might just need to find a different plugin that can trigger on audio.

Although Cakewalk may not be the best platform for live performance in all respects, it can certainly stream real-time audio with FX applied while the transport is stopped. I would have to test to be sure, but so far as I know, tempo -based FX will sync to the project tempo that is currently in effect at the Now time where the transport is stopped/paused even if it's at time zero and the project has just been opened without starting playback.

I think we'll need to see a copy of the project/template to have any chance of figuring this out, but I don't have any of the EastWest stuff. Can you reproduce the problem with some other multitimbral synth? I have Kontakt, Sampletank and Aria Player.

For anyone that doesn't have everything Waves, and just wants a few pieces: - Get another 10% off with code YNY23. - You can buy 2 and get 2 free with each order so don't buy more than 2 at a time. - Note the fine print: "Free plugin selection must be completed within 72 hours from the time of purchase."

Best wishes, Gary. Sweet photo.

Can't help you, but wanted to share my favorite handpan video:

My guess is it would take additional code to deliberately exclude the FX bin from obeying the '1-second rule', and this simply wasn't considered. It's only noticeable because the FX bin is the first object your cursor encounters when passing out of the clips pane into the tracks pane and it's big.

I think you are mis-remembering in this particular case; Slide Over to Make room has not worked correctly for well over a decade if it ever did; down-stream clips that didn't need to move would move and would move to the right even when you were dragging something to the left. Ripple Edit addressed this and many other case where Add Measures, Delete Hole and related actions would not deliver expected results. For the most part, the old ways still work (or still don't work) as they used to when Ripple Edit is disabled.

What are the exact symptoms of "don't work"? In the absence of an actual bug, a change in behavior after close/re-open would usually be due to having incorrect focus, selection, tool or some other program 'state' that is not compatible with what you're trying to do and is not saved as part of the project. Pretty hard to diagnose without having the project in front of you or steps to reproduce it. All I can say is that these unexpected things do happen to me, but I can pretty much always find the cause and correct it without having to shut down.

I can reproduce that, but only while the cursor is over an FX bin after leaving the clips pane - hovering over any other part of the tracks pane works as expected, and once I've scrolled in the tracks pane, it works when over an FX bin as well. And I can confirm Platinum did not have this quirk. Had not noticed it until I went looking for it. I guess I just don't normally stop over the FX bin when scrolling in the tracks pane. P.S. I'm on Windows 10.

I finally broke down and got another 10% off with code NERDS10.

Indeed, it would be good to download the Ref. Guide and do some reading. - The Event List shows controllers in red to distinguish them from notes. - You can select in the Event list by sweeping the mouse down the far left column of the view, and delete the selection by Edit > Delete (Delete key will only take the currently focused one). - Select by Filter works by filtering the current selection so you should start by selecting the whole clip in the track view in this case. EDIT: By the way, base don that Event List, it looks like a volume fader/knob on your SY777 might be 'jittering' and sending superfluous controllers almost constantly which is going to cause various problems. You might want to look into disabling it or routing it to an unused channel if possible. Or try exercising it to clean it up and/or find a position where it doesn't jitter.

Cakewalk doesn't render the metronome when exporting or bouncing, even in real time. You need to arm that aux track and record the click first. Then you can include the click track in an export