Glenn Stanton

ah you want the background of the clip to change, in my exmaple the content of the clip follows the color. David has the idea on the color of the clip background so setting it. if that isn't working, it may also be that the new Sonar themes are not quite there yet ?

thanks! i fully understand mix scenes. i don't use them because my workflow is better without them. that said, if at some point i want to change, i may go back to using them like i did what? 5-6 years ago? i just find the workspace thingie more quickly configures the space and tools for a given step and let's me switch rapidly with depending on any coupling to the project file.

that was the link i posted earlier...

so you're saying the track color is not applied to the new clips after you're done recording them? or you're saying that while you're recording they're dark gray? for the former - turn on the track colors. for the latter? no idea possibly a feature request.

in general, the clips use the track color setting: in the preferences, i check the "show strip colors" to make the tracks use the color (the small knurb on the left end is where you select the color for the track).

i never use the mix scenes. i use the workspaces instead since they transcend the projects... but whatever works for you will, erm, work for you..

the VST3 is a Steinberg specification which is licensed directly via Steinberg. if you develop to those specs and test rigorously, then the plugin should work in almost any DAW. https://steinbergmedia.github.io/vst3_dev_portal/pages/VST+3+Licensing/Index.html

for sure. i have several templates - a "raw" one for when i need just a couple of instruments ready to go, a "record" template which has all of the tracks, insturments, etc ready and wired - i simply remove tracks and instruments versus adding them (most times), and a "mix" template which mirrors the record template w/o any of the instruments or MIDI tracks - everything goes into the mix template as audio (like when i do client mixes). i also have a "master" template for assembly of 2-tracks and either individually or as a "album" layout the tracks and do most of the required "paperwork" as leveling/eq/compression needed in small bits. and a "compose" template which has a couple of instruments and some "generator" tools. i also have a couple of variants of the record/mix which are using SSL, API, or NEVE plugins to simulate the "console" effects like channel strips vs independent plugins. i use the SSL one a bit more tha the others as clients will share their projects and many have some specific SSL settings they really like and i want to recreate those. then i switch views with custom workspaces for tracks / console views, busses / console views, or just drag the busses/tracks back and forth on console view. very fast (for me). some examples: DAW template - 01 - process.svgDAW template - 02 - mix.svgDAW template - 03 - workspace.svg

maybe your keystroke setting got removed? if you right-click on the clip and select "Region FX -> Melodyne -> Create Region FX" what happens?

weird because i just updated them yesterday and they're working fine in my Sonar & CW - True Dynamics, True Iron and KClip3. and yes, some companies are blaming CW for their poor implementation of the latest VST3 spec - and some of those need to have the .vst3 folder extension removed so they work. but many of the properly implemented ones work fine.

both google, onedrive, some stuff into dropbox and very rarely icloud for some clients

i use a 4TB SSD called "cloud" and except for my C:\ documents folder (OneDrive by default), all the other stuff is backed up there. i sync from my local drive to the cloud drive, then the cloud services sync to/from there. cost - an external USB drive (~$200)? the benefits? i have a local backup of my stuff + the clouds. and my source materials are never at risk from the cloud services doing weird stuff.

so, you have your serial number and activation #'s handy? then you run the standalone version of the app as admin? you enter the serial number and activation #'s. then what happens? you get an error?

so -- using WASAPI will work as will ASIO4ALL. the UMC22 doesn't have a native driver like my UMC202HD or UMC1820. https://mediadl.musictribe.com/media/PLM/data/docs/UMC/QSG_BE_0805-AAR_U-PHORIA-Series_WW.pdf

yes, so why fight it?

i'm still waiting on the free version of a Pro Tools professional version, since i've used it since the late 90's and since i've paid enough into it over the last quarter of a century... not holding my breath though...

so, in terms of the understanding established to some degree on this forum: SONAR (all caps) = SONAR and derivatives from pre-Bandlab days. Sonar (proper case) is the new DAW product from Cakewalk (a Bandlab brand). think of it as "case sensitive programming"

generally speaking - if you're doing sound library or video work - use 48K/24. while most modern same rate conversions can be fairly transparent, i'd go native just to avoid the extra work and any artifacts.

damn Beatles! always so loud are they! always making the girls scream they are! [your best yoda voice]

check in your plugin manager - select the VST or VST3 grouping and select "show excluded"

and also keep in mind that ASIO4ALL works just fine - when you have everything else set correctly - and remove all those extra ASIO things from your system.

an important step - decide which sample rate you want to work with - 44.1 or 48? (or some folks go 88.2 and 96). then make sure ALL of your Windows system settings, your ASIO, applications, etc settings are ALL using the same sample rate. this does a couple of nice things - one - all your apps now use the same sample rate so things won't mysterious be trying to flip around, and two - nevermind, there is no two. so check your Windows audio settings - both playback and record. in my system (being a dinosaur) i have them set to 44.1 (and 24-bit / 32-bit (not that i use 32-bit)). then my ASIO for the IO is set to 44.1 then my CW is set for, yep, 44.1 and 24-bit, and in the audio settings, i have 24-bit, 24-bit, and 24-bit. and voila! almost never a problem because all sample rates are aligned. now, that said, some products have proven problematic if they demand a different sample rate (like synths that are just so good they only will work with even # sample buffers and only 48K - or some only in 44.1K on rarer occasions where i do run 48K). but i have simply learned to avoid those products now...

did you re-scan the plugins? i would be surprised the VST dll weren't also installed but maybe you just need the plugins refreshed.

that would explain it. the preview files only showed up the first time i exported from Sonar even though the boxes where unchecked. and now, checking after the same project and several other exports - no preview files. so that's the answer. still, it would be preferably to never exported them unless checked... ?

yeah, my Alvarez K Yiari DY-85 is going to get the treatment next. just need to spend sometime to find the right parts...