Colin Nicholls

HOT DAMN

It's not a bug so much as it is the Sonitus Suite not keeping up with "improved" security constraints in later versions of Windows.

I bet if you run Cakewalk as Administrator, you can save the presets you want. Then they are available in later sessions without Admin privileges. There's a hack you can do to lower the privilege level required to write to the specific ini file used by Sonitus, if this is a convenience you want. See scook's post below.

>> Any chance they're being overidden at the Colors level? Hi @malborinatiro, welcome to the forum. If you read your quoted text carefully, you'll see that this, indeed, was the case!

Glad to help!

Does Addictive Keys respond to CC:7:-Volume ? I checked the manual and it indicates that : AUTOMATION: The following parameters can be automated in Addicitve Keys: Channel Volume (Instrument Ch 1, 2 and 3, FX1, FX2, Master) FX Sends 1 and 2 for each Instrument Channel Master Channel Filter (Hi/Lo) ... So it might be that it expects you to explicitly assign a CC to a specific instrument channel to automate volume. I'm not a AK user, so I could be off-base.

Choose "custom installation" and de-select the bits you don't want. But to be safe, I recommend installing the whole thing. Then re-install Cakewalk By Bandlab.

I've never ever used controller 7 (MIDI volume) in my projects, so just for kicks I created a new project and dropped in an instance of Pianoteq. I then recorded some notes and opened the PRV, and added the CC : 7-Volume controller and drew some values. What I see is shown here: (animated gif removed to free up space and because it was no longer useful. Sorry!) You can see the notes I've created, and the CC:7 values I added, first with Snap quantizing and then with Snap disabled (smooth curve). Then I scroll to the left outside the borders of the current clip, and add some addditional controller events. Then I use Right-Click-Drag to select the events. Does this help? >> I'm trying to "paint" a line and it won't paint it, the way I'm used to seeing it do this. Instead as I drag my mouse, it generates a green rectangle, which does nothing --- or at least nothing I care about. Check Snap settings, just in case >> Near as I can figure, Velocity controls the volume at the mixing console whereas Volume controls the volume of the instrument itself. That's not how I would describe it. Velocity has nothing to do with Mixing Consoles, and everything to do with a binary value describing the attribute of an individual note - and how it is respected (or interpreted) is up to the module responding to the information stream. (MIDI controlled lights, anyone?)

@marled, if practical I would be willing to apply the required pitch shift using V-Vocal. It may not be of interest seeing as no-one can actually purchase V-Vocal if they don't already have it, but the offer stands. In case it is not clear, this is just so that you can add another data point to your tests.

You, sir, are brilliant. That was it. Screen Set 1 was somehow selected and locked. I must have pushed a random key at some point that made this happen. (Possibly the "1" key). It had to be *something*. I've never been a fan of Screen Sets.. They just never gelled with my workflow, at all. This is a second time I've been bitten by them. Hey, @Noel Borthwick, I finally found a use for Lenses! I created a Lens that removes Screen Sets! 🙂 Thanks as ever to the Bakers for giving us "such stuff that dreams are made of"

I figure you didn't also trial V-Vocal because you don't have X2 or earlier?

I'm not sure how to describe this, but at some point, Cakewalk stopped remembering how i last left the project and is opening it as it was several weeks ago: The position of the vertical scroll (i.e. which track is positioned at the top of the View; the track folders' open/close state; the last VSTi property window opens It does remember the position of the NOW time, and all my edits are there, of course. But no matter how I scroll or collapse or arrange the tracks, then SAVE, when I next open the project it is back to the starting state. I don't know what I've done to make this happen. I can't believe it is a bug but if anyone out there has any insights, please share! It's annoying.

I don't think you need to freeze the track... if you select all the MIDI notes you can use the Ctrl-Drag on the end of the clip to scale all the notes. I've done this for short phrases, never an entire track! But it might work.

Huh, I never noticed that. Sorry for the incomplete answer., @D Chance Gold. I recently re-installed everything on my DAW but, of course, I installed Platinum first.... Of course, scook was on the ball as usual.

You should be able to download the installer for the Studio Mixing FX Suite from your Cakewalk Account under https://www.cakewalk.com/My-Account/Products under SONAR Platinum.

I don't disagree with you, but I'm not sure there is much that you could do to make it easier to use - except perhaps to have the list available by default. You can show it by pressing the "Show List" button: How would you improve this display of Tempos in a project?

@jkoseattle, you don't see this little >> arrow?

Will do. No, that option is not enabled. However, today I learned that the "Project" section in Preferences only displays if you have a project open. Are they Project-specific settings? I guess they are. Huh.

Yeah, @Noel Borthwick, I know, I know.... FYI, it just happened again and everything happened according to my prediction: Layla control panel indicated signal (and I could hear it when unmuted the direct RT monitoring, of course); no activity in the DAW meter until I toggled the input channels on the track, at which point normal operation returned. When it happens, it happens immediately after stopping playback. (not recording). So far, this morning it's always been upon reviewing the latest take (playback only) that I realize the input echo isn't working. Seems to be quite prevalent this morning. The thing to do now would be to switch to the Focusrite 6i6 for a bit and see if I ever get it happening there... Also just FYI, the option in Preferences > Audio > Playback and Recording is unchecked: [ ] Disable Input Monitoring during playback Summary: OK, given that this totally can't be debugged by BandLab without reproducing it against a modern audio interface+driver, I may stop posting updates here unless I can do that. As Noel gently hints, this wouldn't the first quirk I've dealt with using the ECHO Layla 3G but, damn, even so, I love that interface.

@David Baay, I don't think I see meter activity but I wouldn't swear to it. I'll double-check that next time it happens. When it does, I'm going to do the following: Check the Layla Control Panel for meter activity (prediction: I'll see positive signal level) Check the Cakewalk Track Meter (prediction: no activity) Switch input channels on the specific track (prediction: input echo restored) In the meantime, it's good that I've got a lot of guitars to record/track 🙂

It happened again this morning. Yes, I'd been tracking some guitar but each time I stopped transport, I'd playback and also check that Input Echo was working. It was. Then suddenly, after a short period, it wasn't. I have no reason to think it was consequential to recording the take. Instead of Run/Stop audio engine, I tried a few other things: toggle input echo on the current track (no change; could not hear guitar) select a different track (same IO input) and toggle input echo (no change) scroll up to a completely different track with no FX in bin, but same IO input; toggle Input Echo (still no sound) Turned on my Roland Keyboard (VK8) and temporarily changed the IO input from "In 7+8" to "In 5+6"; enabled input echo and played a few notes: SUCCESS Restored the input to "In 7+8", COULD HEAR INPUT OK, go back to the guitar track and enable input echo: I CAN HEAR GUITAR So, in summary, I think that forcing Input Echo to operate on a different set of inputs may have restored normal Input Echo operation. (Let me stress that all these tests are with the ECHO Layla3G control panel muting the direct monitoring. I'm only listening through the DAW outputs.) So that was interesting. I'll keep working and see if I can isolate the exact steps to make it happen.

Hi @David Baay, thanks for the great suggestions. I pretty much exclusively use the Layla3G in ASIO mode. I while back I completely switched to the Focusrite 6i6 for some trials but returned to using the Layla. I've never used anything but ASIO mode since it became an option back in... whenever. In my last post, I spoke too soon: I indeed did experience the non-echoing Input Echo behavior earlier this evening. It might well have been immediately after recording a take - I will be trying to reproduce that. Also, very good idea about trying the Focusrite interface to see if the same thing happens. Intend to do that also, but was waiting until I had a clear set of reproducable steps. It's funny you should mention alternatives to Spacebar for starting and stopping playback and recording. I've noticed that Spacebar seems prone to mis-starts or bursts of static instead of normal playback, whereas using the mouse to click the transport button is less prone. I haven't tracked that down in any detail, yet, but it seems strange. (All this makes it sound like I'm having multiple issues but the truth is, my system is behavior pretty well and I'm happy making a lot of progress on my projects. )

Yes, absolutely. It was that experience that prompted me to write up a post about it. I haven't experienced it again in the last 24 hours, for what it's worth, but I'm sensitized to it and paying attention in case it happens again.

It must be pretty subtle... unless it has to do with the Ozone 9 rectangle in the FX bin being blue, but that might be related to a feature I've never used. I'm really not familiar with half of what's included in the product *sigh*

I've experienced it both with plugins and without. I don't know what to tell you other than what I've experienced, as described above. Toggling the engine restores input echo on the misbehaving track.