Jump to content

Glenn Stanton

Members
  • Posts

    2,202
  • Joined

  • Last visited

Everything posted by Glenn Stanton

  1. it should be something you can set up in any modern DAW - i have a few "listen" busses - a "-12db" (quiet mix checking - pre-fader off master) and "master" (feeds room monitoring & basic 2-track bits), a "NX / VSX / Sound ID" for room simulation in headphones (also pre-fader send), and a "print" buss pre-fade off the master for final export.
  2. the dither adds a noise component (not detail) to the LSBs (avoiding a "quantinization error" when truncating digital values) when you convert from (say) 24-bit to 16-bit (i.e. dropping the bottom 8 bits). if you're doing final mix in prep for mastering - leave dithering off and send in same resolution you are mixing in. if you're trying to produce an MP3 (etc) directly off the mix, then pick one of the POW dithering options. note: the results will not be as good as say the Ozone or WaveLab etc dither options. S1 vs CW vs etc may likely have different dithering options and aliasing filters. it is interesting that no matter what we do - noise is always going to be part of audio ? some reference: What Is Dithering in Audio? (izotope.com) https://www.izotope.com/en/learn/what-is-dithering-in-audio.html
  3. one caveat for clip gain - it can impact how effects behave - so things like compression and saturation (or guitar amp sims etc) can end up behaving differently so consider you may have to do some compensation on those to accommodate the changes in clip gain. one reason to do the clip gain automation (sort of dynamic equalisation) before inserting and setting up any effects which can be impacted by those changes.
  4. here's one not so obvious - but i think was installed recently during one of the MS Edge updates - "Realtek audio effects" in "software components" - before: random clicks and glitches, after disabling: clean again. drove me nuts for a couple of days.
  5. +1 on the install -- also - i keep all my Spitfire content on my content drive under a single folder -- this way whatever login is used, the content is the same for all users.
  6. and you downloaded the latest LABS app / Spitfire manager? when you contact Spitfire support - did they give you any suggestions?
  7. a simpler solution is use anti-spam filters & rules - new users need to wait 8 hours before posting or read the "rules before posting" sticky and click "like" etc would likely prevent a lot of spamming.
  8. if they're wall warts, you're likely better off replacing them with a properly made power supply which has the correct ground, chassis ground etc. to reduce/prevent hum and provide stable voltage (although in some cases, a variable supply option can be useful to "stress" the electronics to get some additional bandwidth on the effects or some additional smoothing to the saturation.
  9. works fine on my CBB on Windows 11. not using an older version of CW so no option to test it
  10. well, high caffeine tea, red bull, etc all can work when the brain is thinking correctly and the hands type out dumb*ss stuff... ?
  11. ... ignore me - too little brain hand coordination this morning before coffee...
  12. remember to do a MIDI export as well to capture tempo (if any) changes etc
  13. as long as they're on and active when you start CW, you should see the same list each time. i know for me (like just now) if i forget to turn on my Komplete Kontrol S49, it's missing from my list ? if i exit CW, turn on my S49, open CW, it's all good again.
  14. +1 -- a means of viewing detailed project information esp on plugins... not necessarily all the settings (very nice to have though) but at least the plugin and patch name, or for CW plugins, the settings as well ? generally speaking when i make enough changes to a preset or from scratch, i save it as a preset of it's own - either for generic re-use, or if project specific - then a project "abbreviation" added to its name and/or saved to the project folder if its an option.
  15. you could use Waves Studio Rack to create parallel also... but sometimes having the plugins serialized is the end goal... then again, when you have 16 cores and 11 are used at any one time -- is that a problem? ?
  16. not sure the difference between the H/W vs buss. but congrats! i'm a big fan of the export dialog. the options for tracks, stems, and in my case, i have "PRINT" buss which taps off the master pre-fader so i can adjust the master level (monitoring) and not impact the final buss output. then i set up tasks to export tracks or WAV rough mix (if record template), or WAV and/or MP3 2-track files (if mix template).
  17. i used to set up a dedicated Melodyne folder on my project drive for all separations -- but it looks like it changed in the not too distant past as i was checking the settings and found i could not change it! this is annoying since my documents folder is on my OneDrive which means if i forget to pause it, it will be conflicting with the synchronization functions. so i'll also need to exclude my cache folder from the AV as well. then found in the help file: Please note: The location of the audio cache is predetermined and cannot be altered: Windows: C:\Users\USERNAME\Documents\Celemony\Separations. macOS: /Users/USERNAME/Library/Caches/com.celemony.Melodyne/Separations
  18. thanks for this! do you have a HW controller device to manage adjusting the CC or using a mouse? or some combination? in my mind, have a MIDI controller with a number of knobs set to CC # would make initial changes "easier" and then zoom in and adjust for more detail.
  19. i liked it. one consideration - maybe also speak to how some of the instruments have articulations (and/or key switches) which may assist in the creation of more realistic / fuller performances (trills, legatos, staccatos, slides, etc etc) (i noted in your event list in the article: Virtual Orchestra Composition and Production by Guest Author Jerry Gerber (soundbytesmag.net) https://soundbytesmag.net/virtualorchestracompositionandproductionwithjerrygerber/ -- you had patch changes / notes about the articulations ? )
  20. there are some references floating around but it's easier just to see the file types it supports via the standalone app: the ARA code doesn't seem to care about the audio depth as it's just coordinating the process - Melodyne itself uses the transfer and separation folders to store individual snippets (one good idea is to periodically it clean up).
  21. fair enough - the proper HW is going to be better for sure. ? for me, the times i use "low latency" for live recording (vocals, guitars, etc) -- the 6ms RTL is fine. ? 20 seconds to align any skewed tracks and done ?
  22. that's because they're called "UMC Driver" ? basically in their downloads, lower units clearly show ASIO4ALL as the driver, and all the bigger units they call the UMC drivers. i can go as low as 8 samples (0.5ms) on my 202HD unit but typically don't go lower than 64 samples which is about 1.5ms each way so about 6ms total round trip. and only use it when recording live stuff. otherwise for mixing and virtual instruments, i just keep it at 2048 samples (about 100ms round trip).
  23. nope, it's definitely not ASIO4ALL. ? its a real ASIO driver which works most excellently.
×
×
  • Create New...