brundlefly

I installed the trial and did a quick test using a project I developed to measure PDC. The test is sample-accurate and measured 9,984 samples (208 milliseconds at 48kHz) of delay. I didn't see any option to lower it by reducing the quality/precision of the processing, and no mention in the documentation of a delay. For good measure, I tried playing my RD-700NX through an input-monitored track with PDC Bypass disabled and the delay was horrendous and unplayable as expected. Notwithstanding that the web page claims "Real-time Processing", this plugin is only suited for post-processing of previously recorded audio at the mixing stage.

I was incidentally comparing Youlean and Sonar's numeric peaks recently and was actually surprised to see them reading identically because I'm pretty sure CW meters are not "true peak" (i.e. processing the samples as though converting to analog to find intersample peaks rather than just reporting the raw sample level). It's more likely the material I was metering just didn't have significant intersample peaks. I suspect calculating true peak on every track in a big project might add significant CPU load and would not be worth the overhead - maybe useful if it could just be selectively enabled on the Master bus which would usually be the only place it matters. In any case, I agree 1dB is a lot, and would make me suspect there might be some additional gain somewhere. Youlean is in the FX bin so any make-up gain, volume automation or post-FX Prochannel plugins could alter the track peak after Youlean sees it.

If the input to the external mixer is to separate mono channels, make sure they're panned hard left and right.

Did you change file Type to MIDI in the Save As dialog? Type 'Normal' is a Cakewalk project file with a CWP extension that other apps won't recognize.

In my view you can't go wrong using the free CbB until it will no longer activate because it's been fully superceded by Sonar. There should be plenty of warning about that to give you time to decide whether to subscribe to Bandlab, buy Sonar outright (if that ends up being an option) or port the (presumably few) projects you will have created in the mean time over to a different DAW. I'll also wager that even when activation is discontinued, you'll still be able to launch CbB and open projects to extract/export audio and MIDI, save plugin presets, etc. for some time to come; you just won't be able to save changes to the project file as is currently the case when not activated. CbB and Sonar have a good complement of VST FX already included, and I'm sure the bundled synth content will grow over time as the product is re-monitized. But, as has been suggested, few users restrict themselves to bundled VSTs for long, and that shouldn't be a major consideration in my view, given the vast number of free and inexpensive options available. The most important thing is that the DAW has a workflow that fits your compositional style and feels intuitive and inspiring.

Now there's a blast from the past... I had totally forgotten about that interlude.

A quick Google says EastWest instruments do not respond to CC7 by default (although I'm guessing it can be MIDI Learned). It uses CC11 Expression or possibly CC1 in some cases.

In case you're not aware, you can use drum maps with any MIDI OUT port whether physical or virtual; you just need to assign the Out Port in the Drum Map Manager. To assign all note numbers to the same port, hold Ctrl+Shift while assigning one. Newly added drum maps will default to the first available port, usually a physical one on your interface.

C:\Program Files\Cakewalk\Shared Utilities\Internal\ProChannelConcreteLimiter I bought it back in SONAR days so can't comment on it's availability in the new release.

This kind of stuff is very difficult to advise on without fully understanding the layout of the project, what you're trying to accomplish and the exact steps and moves you're trying to make to get there. I'm confident it's all explainable, but I would have to see the project. While starting over may still be the easiest course, depending on how out-of-whack (the technical term) things have become, I'm pretty sure I could fix the existing one if you care to share it.

The Bakers recently removed support for GS wavetable synths and also removed the TTS-1 multi-timbral soft synth at Roland's request. I can see that the ouput of the highlighted track is assigned to the UR22's out so, yes, I think you were listening to the Juno's output. Possibly it is no longer in the correct mode to act as a General MIDI synth. Also, ideally, you would want to add an audio track to the project to receive audio input from the Juno and echo it out to your monitors so you can record the Juno and monitor with plugin FX if desired. Then save the project as Type 'Normal' instead of MIDI so that it becomes a full-fledged Cakewalk project file. Re-saving as MIDI will lose all the CbB features and audio routing.

The pedal will cause the Juno to generate the CC64 sustain events that can be recorded in sound-on-sound mode in real time into the track with the MIDI notes. You'll hear the effect of the sustain messages acting on those notes as they play back so you can get the pedal timing right with a little practice. If some of them end up a little but to early or late, you can drag them around after the fact as needed in the Controller pane of the Piano Roll View. it's just a faster way to get the events into the track.

There is an option at the bottom of the Options tab of the Track View submenu called 'Stop at Project End' that will cause the behavior described in a new, empty project where the 'End' is effectively at 1:01:000. If you disabled it, the transport will run in an empty project. I always leave it disabled.

Try using the Channel, Bank and Patch controls in the MIDI track header (you might need to set the Track Control Manager to 'All' at the top of the Track View to see them or use the Track Inspector. The values you set there will be sent when the project is opened and every time Playback is started, and they'll written as events in the MIDI track when you Save As MIDI. https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.2.html

Is there anything else in the project, or just solo piano? Any chance something else is soloed with Dim Solo enabled? What instrument, and is it an Instrument track or separate MIDI and Synth audio? Possibly you inadvertently lowered MIDI or audio Volume in 'Offset Mode' (see the button to the left of the global Read enable in the Mix module and verify all Volumes are at 0dB when engaged). Preferences > Project > MIDI should be available regardless of the setting of Basic/Advanced radio buttons at the bottom of Preferences, but possibly it's limited by a Workspace (I don't think Workspaces have any bearing on Preferences, but saw this suggested recently.) I'm sure it's something simple. If all else fails, share the .CWP here with a snippet of MIDI.

I read this to mean Instrument track. Is that right, and what instrument?

Track View > Options > Stop at Project End

Glad to help.

Glad you got it sorted. Two thoughts: - Even though many synths will treat anything over 63 as pedal down, the convention for on/off values is to use 127 and 0, and I would recommend that so that the clip will 'play nice' with a synth that honors continuous pedal messages (a.k.a. half-pedaling) with variable damping should you ever happen to use one. Also, 0 and 127 give you the clearest representation. - I highly recommend getting a basic velocity-sensitive MIDI controller keyboard with a sustain pedal and starting to record in real time. Even if you have no keyboard skills at all, I wager you will quickly get to a point where fixing a wonky real-time recording is faster and yields a more natural-sounding result than drawing everything in with a mouse and trying to "humanize" it after the fact. Plus it's just way more fun and rewarding!

That's a key piece of information, and promising, but I'm not sure what to do with it since there doesn't seem to be any relevant setting on the interface and the only way CbB can record its metronome internally is via a Send from the Metronome bus to an Aux track which isn't something you'd be likely to set up accidentally or forget about when troubleshooting. To understnad better where the problem lies, I suggest the following: - Check if it happens with a new project started from the Basic template with no input plugged into the interface. - Check if it happens with the Alesis interface disconneted/powere down and CbB using onboard sound via WASAPI. - Set up the Alesis with a free/demo version of another DAW and see if the problem reproduces.

I'm guessing you have a positive (above 0dB) Volume set in Offset mode.

Might help to share your test project.

I have used it recently and not seen any of the mentioned issues. I just checked that project, did some temporary re-arranging and all seems good. Are you starting playback by the button in the Arrangements section? If you start playback normally by the Tranport module or Spacebar, the whole project will play through normally without regard to any arrangement. And the Event Overlap Threshold function you mentioned is present at the bottom of the MIDI tab in the Track View submenu.

I completely agree with this. In fact, "pricing" as stated was already a very poorly thought out strategy, but..... I also agree... but I think it's the hand-wringers who should not have said anything. ?

Probably best not to get in the habit of abbreviating it that way. The trolls will have a field day with it.