Glenn Stanton

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.

double check your player app settings and general sound settings - W10 has a bunch of "enhancements" options which may be bypass via ASIO, but used by the player apps.

while the Nektar has the presets advertised, and the Roland (may be the older units made to work with CwB), you might be better served by getting a midi controller keyboard that has the keyboard feel you want and majority of the controls (e.g. a Noord), then hunting for some presets and/or making your own. or just get a really good keyboard and a separate controller (e.g. MPC, FaderPort, nanoController, etc).

one note - the Ozone 9 and related newer version of Nectar, RX7 - they are very very sensitive to your screen resolution settings and therefore the related patch levels for the graphics and screen resolution. i spent part of a month troubleshooting this: it would randomly work at the proper UI refresh rate (e.g. not take 5 seconds to load a menu!!!) when i set the UI to 1920x1280 or 1440x900, and then it would stop on the next reboot. eventually i noticed my intel drivers were about 3 years old, so i updated them and now it's stable at all resolutions. Ozone 7, Nectar 2, Trash 2, etc all worked fine so it was a very annoying problem to identify.

one thing i found - if you have OneDrive backup enabled, and the Melodyne separations were getting backed up to OneDrive (because by default the "separations" folder were in the user documents folder @$#%@%$^). this of course ended up causing locks while sync'ing a bunch of changing files. once i changed the path to a permanent home on a separate drive (editing the Melodyne XML file), it all works perfectly. Transfers end up in the project folders, or the permanent home location, depending on how i'm using it.

that is possible, however, after trying both the manufacturer "ASIO" drivers, a number of free ones, ASIO4ALL, etc, this one seems to be working well - very stable in performance, decently low latency (lower than my WASAPI, WDM, and MME). even my Musescore IO settings like it, and the Musescore IO doesn't like anything that has to do with audio output 🙂 so i removed all the other ones and have been using it exclusively for all things audio (disabled my normal audio drivers as well) for about 1 month now. i do agree though, that my home desktop machine with the specific UMC drivers, outperforms the generic drivers because i can get the latency down to 2ms (with the caveat that it's a terrible price on CPU - so i keep it around 5ms when recording) with my UMC1820 - all 8 tracks at one.

i'm using an inexpensive Behringer Q802USB mixer - stereo USB (@41K sample rate 😞) (the Q1002USB (more $) has a 48K sample rate 🙂) and I use the Steinberg low-latency ASIO drive that came with the free version of the Cubase 10 program (it's much nicer than the ASIO4ALL and some other ASIO programs in terms of reliability). it's about 10ms latency (20ms round trip) (adjustable up to 100ms), but with PDC enabled during record or simply monitoring via mixer the instrument live against the playing tracks/metronome, then shifting the track to match, it seems to be working ok, and the mixer was only $80 USD or so (and includes decent preamps + channel compression on 2 XLR ins, plus 2 stereo more line level etc inputs) so it's a reasonable compromise on audio I/O.

here?

plogue sforzando seems to have picked up all of the Dimension pro instruments all by itself, or maybe i added a path somehow? either way, it was very handy means of getting access to the audio clips in a lightweight host.

there was a detailed article a while back on how he exchanged tapes with Brad to get all the vocals done, then brought in a pro drummer to finish the recordings. very amazing.

unless it's a specific single track effect, i use an aux track or aux buss to share the effect and can automate it etc. but maybe adding an aux track next to the track that needs the wet/dry balance adjusted and perhaps automated, is the most direct way. one could also use the effects bin in the pro channel to possible do the same with the channel tools etc.

also, the PDC button will drop/bypass the latency from the plugins, which is what i use during recording (although i often skinny down the number of unmuted tracks as well to reduce overhead so i can get my latency way down during the recording)

you could use the headphone output into your 2i2, it's unfortunate it doesn't have a DI type output (e.g. like a LoudBox mini) where you can set the master volume off and have it connected via XLR etc...