Glenn Stanton

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...

well without more details it will be tricky but for #1 -if you open session drummer and then select in the programs list, the kit, and it loads: then you should see the kit and related parts in the session drummer settings. this should be the kit you then hear if you use the MIDI track to play the kit, or using the step sequencer to write the MIDI, or import MIDI clips, etc. as far as why you are getting things out of sync - no idea without more details.

nice! one thing i highly recommend, i put this on my 2003 MIM Strat - the zero fret ("zero glide") nut. really gets your action down and intonation is excellent now. i did a bit of filing on a couple of frets to get it just right. so even with old fingers, it easy to play and enjoy! https://www.stewmac.com/luthier-tools-and-supplies/materials/nuts-and-saddles/zero-glide-nuts/

if you got the Fender Squire tele, then you could afford the b-bender and some humbuckers too.... ?

John -- you gotta start charging more at the gigs to cover your winter hobbies ?

i believe the asset files were something in a version of CbB and then in a subsequent version were no longer used. so some projects may have them. but as far as i could tell there was no detriment to removing the them.

unfortunately LUNA is still just a beta on Windows, just ran the update today and now some things work better, but i suspect it will still be a while to stabilise for it to be fungible on Windows for more serious folks.

yes, and some other products, like several audio editors, do not respond well to improper vst3 plugin development. and it's easy to spot ? a bunch of the VST3 plugins with the new .vst3 folder extension work fine in CW, and a bunch don't.. then suddenly they work after an update from the vendor... dunno. i do know bugging the vendor (repeatedly if needed) seems to solve it in many cases...

so might be a bug - generating the files when the project preview is unchecked, in my example, in both the WAV and MP3 export settings. unless the preview files are generated regardless so the start screen function. one interesting thing - when i first open the dialog the preview box is grayed out. when i did a "recall settings" for each task, the box was then "available" - however - this only occurs by default on all source settings except entire mix. otherwise it's grayed out until you recall the task settings... so busses, tracks, clips etc exports the box is grayed out. makes sense if i'm exporting anything other than 2-tracks...

it's because not all developers have correctly updated to the new Steinberg VST3 spec so some apps work fine and a bunch do not. so follow the advice from Outrage to remove the .vst3 on the folder and rescan, and bug the plugin company to fix it.

no, in the box VI don't need an audio interface per se - but you likely want to hear things - so some interface even if it's only the built-in audio IO is needed for monitoring. for example in a recent project w/ 8 VI and 22 tracks (mostly drums) i simply arm all the audio output for those instruments and press record. sip some beverage and then it's done, disarm the tracks and voila! 22 audio tracks.