Glenn Stanton

yeah, i do this for most apps - esp if they have more than 100-200mb of samples. it keeps the OS drive free (and smaller), and keeps the active projects drive clear of the sample requests (from the third drive where content is stored). backing up the content is then simple. as @bitflipper pointed out, the apps are none the wiser. as a note - best to keep a record of the junctions in a (backed up text file) so if you do crash, it's easier to recovery (scripting becomes an option :-))

backing up files (daily and often) to separate disks (and/or clouds) is your friend. sorry for your loss.

you could use a "junction" (https://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/) to map a folder "C:\Program Files\Cakewalk\Dimension Pro\Multisamples" to a content folder on the S: drive. as far as the mapping of DLL & EXE, i think the normal location is in the "C:\Program Files\Cakewalk\VstPlugins\Dimension Pro" - you could probably remove the others in the sample folders and rescan. or rename those DLL and EXE to DLL.REM and EXE.REM (so they're not found by the app) and rename them back if things break.

also - if you record the drums to audio and leave the MIDI track enabled (so the audio and VSTi are playing together) you'll get this effect (most times). it usually reminds me to turn off the VSTi once i recorded them to audio (or if it's still on after i have frozen the tracks).

ok - so resetting the value to 1 - the resolution for the SV (1/16) now followed the global setting (1/8th) rather that the SV setting - in terms of drawing notes of a smaller grid, and expanding them did nothing to change the notes being drawn as overflow into other measures. changing global to 1/16th then allowed me to match the staff setting of 1/16th and draw the notes properly... as a bit of info: i generally don't use SV except to print some lead sheets or tab. i can see how the global grid versus SV grid lock-in would definitely be really annoying to folks who do use it extensively. so if this changes does unlock it, as i think it does, hopefully it will be useful...

i usually use Musescore, but in testing the Staff view w/ new settings done per @scook instruction re: Preferences, INI edit, value set to 0, then restart CwB. i created a blank project and added a MIDI track, then opened staff view. set the global snap to 1/16th, set SV to 1/4. drew some whole, half, quarter, and eighth notes. seems like i can independently set the resolution of Staff view versus PRV. i set the global value to 16th and the SV to 1/32nd and i can draw 32nd notes in the staff view on 1/32nd snaps. conversely i can draw 1/4 notes in PRV on 16th snaps. and 1/16th note on 1/16th snaps. setting global to 1/8th and SV to 1/4, in SV, i can see the contraction of notes (1/32 & 1/16) to fit the new grid. i can only draw 1/4 notes in SV, but can draw 1/8th (and shorter) notes in PRV on 1/8th grid. as some info: i was able to replace a rest with a note by clicking on the rest and it either replaced the rest entirely or added the note + a smaller rest. not sure if this is how it's supposed to work but it's seem logical to me 🙂 as a follow up - i didn't try to reset the value to 1. will do so and report back.

i was looking in the .idl file: MIX_PARAM_FX, // fx# fVal: 0/1 = enable state MIX_PARAM_FX_COUNT, // - int 0-65535 GetParam returns number of effects on this strip MIX_PARAM_FX_PARAM_COUNT, // f/x # int 0-65535 number of parameters for f/x # MIX_PARAM_FX_PARAM, // (FX,param) float 0/1 dwParamNum=MAKELONG(fx#,param#)

would be nice to have something like a MIDI "patch point" or MIDI "aux track" that instrument tracks could accept as an input... probably a new feature request though...

in the docs, it looks like the parameter index number is based on MAKELONG which creates the index # based on 2 factors...

Snap Offset may not be the answer for groove clipping... you probably (as noted already) do some manual tweaking of the initial sample to get it just right. "Snap offsets Snap offsets allow you to set a point other than the beginning of a clip as the “snap” point used by the Snap to Grid. A snap offset is the number of samples from the beginning of the clip. Snap offsets affect all edits that obey the Snap to Grid setting. Once the snap offset is added, you can set the Timer Ruler to SMPTE or MBT time. * Note: You cannot set a snap offset for a Groove clip."

it seems to be ok for me from a timeline perspective, but i do notice it takes a while to load up the processing icon, and sometimes not at all. i close the window and re-open, and then i get the icon or see the processed notes. but for me, the timeline matches what i'm seeing in the CwB window. Melodyne Editor 5.0.2.003

Izotope Vinyl - free and it can add those imperfections, erm, perfectly. https://www.izotope.com/en/learn/vinyl.html

that'll teach you to try and check mono compatibility! :facepalm:

ah, that is interesting. i use ilok a lot and had updated the software after i did the video drivers - so it would have been interesting to see if that would have also changed things. definitely not happy at the newer UI approach Izotope took which seems very sensitive to things is should be ignoring... but it's working again so i'm mollified for the moment...

USB connects are generally limited to a max of 500ma @ 5v - so using the power supply ensures full voltage and current to the electronics - pre-amps, converters, phantom power, etc can take more power than a USB connection provides (unless using the full-on PC USB 3 connectors... which requires the USB on your I/O to use it) and as a result, you may encounter additional audio distortion and perhaps jitter in the converters. may be subtle, may not be. on the larger units (i have the 1820) i definitely only run it on the power supply.

quick check - all inputs and outputs set to be in approx same listening volume? i.e. if you were to play pink noise in CwB and the playback software you're using, are they the same apparent level? as a note - it's always good to make sure all the playback software (CwB, Media Player, QT, etc etc) are all outputting the same volume - get a -12db pink noise WAV and run it through all systems - if you have a sound level meter - use it - and make sure everything playing back has the equiv volume level. (i'd suggest going further with detailed gain staging and calibration etc but for now, a quick check may be all that's needed for now).

it could be something in the VST interface on the Waves shell just go caught in the right moment to bomb something in memory. maybe turn off the Wave plugins and rescan the VST and try to load the project then. if it's the Waves plugins, it should allow the project to load since they won't be active. maybe reach out to the CwB support team via a support request and provide them with the dump file?

depends on what you do with it. i tend to set things so the spread is smaller rather than larger and position it from there. so bvox - i'd set around 20 width and up to about 60 on depth. with vox on 5 width and 50 depth. otherwise like any possible phase/polarity, you could run into masking problems. also ensure you're exporting from the master into stereo file (2.1 is effectively stereo with an option for an LFE channel which i leave off).

the load time for a project - a simple project with just the O9 on an audio track - about 5 seconds, and the plugin load/display etc times are all very fast for me once i update the drivers. i suggest also checking your permissions on the Izotope products, VST, and CwB folders as well as any PATH settings (command windows then SET command in case something is weird there).

my remote-workspace keyboard is an M-Audio Keystation 49 II - synth weighted keys, pretty quiet, class-compliant USB, and has the Mackie/HUI capability - but virtually no controls other than pressing the "advanced" button and selecting an option off the keys. has basic stop-play-record and cursor pad. https://www.m-audio.com/products/view/keystation-49

they seem to operate just fine - same as the standalone apps. prior to fixing it - they had the same issue for loading, menu operations, etc.

one consideration - using a surround buss - set it to 2.1 in the preferences, skip the LFE, and now you can set width, depth, and position of any stereo channel and position. depth for mono. be aware some plugins can misbehave on the surround buss so be careful to only put them on the stereo busses and channels. fyi, you can have several surround busses feeding into a master surround buss - so expanding ambience and effects beyond the "stereo" field can be managed separately... always check in mono though to see if collapsing those effects causes a problem to your mix - used judiciously, it's typically not an issue.

an option i use extensively - use the surround buss - i set the surround to 2.1, skip the LFE, and now any stereo buss or channel can be positioned L-R for width, depth, etc. mono channels are L-R position and depth only. one nice effect is to put some delay and reverb just "outside" of the main stereo space (say a width of 70) and put the reverb @ 90 in terms of depth, leaving the delay at 100 (slightly further out or deeper).

as a safety measure, leave the paging file at 1024Mb (1Gb) so if you run out of RAM the system can still support vital functions and let you turn things down (hopefully without crashing). otherwise, there is little impact on large RAM systems from having the paging file - however set it manually to approximate the same size as if it was system managed (e.g. if the system managed paging file is 3166Mb, maybe set it to min/max of 3072 or 4096).

i got a note this morning from Izotope support: the latest products (Ozone 9, RX7, etc) all use GPU extensively. so even though my laptop has only an Intel 4000 video component, the updated drivers definitely fixed it for me.