Jump to content

Glenn Stanton

Members
  • Posts

    2,136
  • Joined

  • Last visited

Everything posted by Glenn Stanton

  1. pretty sure it's been stated by Bandlab folks that once the new products are established, the CbB authorization process will shutdown and the CbB product will no longer be operational after the authorization expires on your system.
  2. i took the original AD2 drum map, and i made copies for different MIDI sources since each of them had decided to use "alternate" notes for things. so if i source my MIDI from Hookpad, Musescore, Toontrack, or some other MIDI library, i know to just open the AD map i edited. i'm not sure this is the best approach as it has taken 10-15 minutes for each one to adjust the note # in the source to the AD note #. so maybe just bite the bullet and take the baseline AD drum map and tweak it for your source(s). and just ignore the ones you're not likely to use or simply remove them if you aren't concerned with some of the articulations being played.
  3. correct, the conversation was whether or not the bounce to mono and/or collapse to mono created a gain over the original stereo...
  4. simple experiment - collapse a stereo track into mono - level? collapse a stereo clip into mono - level? generally collapsing stereo into mono is a 3db gain. track, clip, buss, etc. of course final level is determined by content of L+R. so do the test with noise to assess the new level correctly - note that pan laws (like -3db center) can also impact the perceived results. ? e.g. i take a -18db stereo noise clip, bounce to mono = -15db noise clip.
  5. Use external software instruments vs. built in tones - Tutorials - Scaler Plugin - Community Forum https://forum.scalerplugin.com/t/use-external-software-instruments-vs-built-in-tones/14398
  6. for me - my vocals or other non-singers - i just use the take lanes with comping on. for other people who can actually sing? i switch to "store in separate tracks" and then comp from there. i find the separate tracks provide me with more safety and re-use options. easy enough to switch settings but a definite workflow change...
  7. learned something new! i hadn't noticed those tabs on the bottom of the track inspector when viewing an instrument track (mainly because i don't use them often) but it's really handy to be able to switch between the audio and MIDI views.
  8. so for my understanding - you use the loopback feature to play the tracking you are performing to? my thinking is - you have one track per mic + one track for the desktop audio (presuming you want that recorded from whatever the source is). 8 mic sources (each mono) and 1 desktop audio (stereo). 9 tracks. what is the desktop audio source? if you don't need to directly monitor, then leave your drum source tracks with their echo off. if you need need to monitor both - then i'd use the live monitoring feature of the IO unit and blend the desktop and drum audio into your headphones directly and then record (echo off) the 9 tracks. again avoiding any latency in your monitoring. as far as phase concerns there is "polarity" (the switch on each track which is 180° flip) and then there is "phase" which is a more complex topic and usually you'll need some timing adjustment plugins or specialized plugins (like Waves InPhase etc) to adjust (as each mic can pick up other drums and the distances are causing time arrival differences which could be causing the phase issues.
  9. since my synth rack is almost always open, i just click on the + and pick my synth and select my options off the dialog. maybe i would use the add track for an audio track as it has the add bus option. but most times i'm using my project templates.
  10. check the dialog to ensure the audio track is being created along with the MIDI track.
  11. using preferences you can change the HW settings... ? glad it worked! i suggest getting in the habit of separate audio and midi.
  12. and yet when i take your file, create a MIDI and audio track and set it up - works fine. maybe stop using the simple instrument track. problem with Kontakt (1).cwp
  13. worked for me. i created a MIDI track and dragged your MIDI over, set the ch to 1, opened kontakt with a synth. a new audio track with the output to st1+2.
  14. it's because you're not using Kontakt... you're using Komplete Kontrol... load up Kontakt on your synth rack and it will work...
  15. maybe when you copy them, your channel settings are copied? and if those don't align with Kontakt then they won't sound. check the copied MIDI track channel settings vs the Kontakt settings for that instrument. otherwise, i have no idea why it's not working...
  16. next - go to your synth rack (Alt+9) and add it my preference is separate MIDI and Audio tracks but do whatever works for you load the drum kit you want and then add your MIDI sequence for the drums - drag and drop grooves, manual entry, step sequence, etc etc
  17. basically it's a MIDI vst - so it should go into one of your VST directories that you scan with your plugin manager. then this:
  18. so if you enter a number of notes manually, and they play, then you copy those and paste them into a new measure - do they still play? and if you copy them into a new track - same?
  19. maybe check to see if the notes are playable by some other VI? like SI-strings has a wide range of notes covered to see if they're in range? check to see if the notes have velocity? that they are of sufficient duration to sound what the synth is set to?
  20. i sometimes use the CSHumanize MidiFX Plugin but only for minor velocity changes. i find the timing bits feel too coarse even in small amounts, so for the timing bits i'll either adjust by hand or use the normal quantize tools. it would be really nice if the new CAL was based on Javascript-like scripting so blocks can be explicit, full array, object, and prototype support etc versus depending on the indentation models used in other languages... lol you could then write proper text-formated "libraries" for controlling not only the app but plugins etc...
  21. press and hold down shift as you open the project to bypass the plugins. see if it opens. then load each plugin until it breaks. don't use that plugin until you fix it.
  22. are you running Windows 7? the last updated driver for the IO26 appears to be 13 years ago in 2010... and was for Windows 7 which has a different audio architecture than Windows 10 and later. iO|14 & iO|26 - Windows 7 Drivers [v3.5.3.8671] Adds supports for 32-bit and 64-bit versions of Windows 7. Updated by Alesis 06/16/2010. and maybe follow their troubleshooting guide in case there is something flakey with the FW device - drivers? hardware degrading? Troubleshooting FireWire Driver Installation (rackcdn.com) https://7132afa424c2f1a2ab6d-54d68a14e2e7c1f76563a2d8c3e9fd82.ssl.cf2.rackcdn.com/1563/documents/firewire_installation_troubleshooting.pdf if its critical for your work, then maybe check out some new IO units which can be had for under $400 w/ 8 channels. Behringer, Presonus, Tascam, and others make decent quality 8 ch units for USB 2/3. even a pair of 4-channel USB units of the same brand can typically use the same ASIO driver.
  23. i use the master as the feed to my monitors and i may move the volume up and down there. having a separate "print" with pre-fader send means even if i forget to reset the master to 0, the print output is set to 0 for the rendering. the print buss (and all others which might feed the main h/w out are set to "none" unless i'm specifically using them, in which case the master gets set to none and i set the other buss to the h/w output, or if i'm using a separate h/w for headphones (e.g.), then i just set the outs to those and leave as is, then use my monitor controller to mute the room monitors if i'm going to use the headphones. technically, if i wanted to just mute and unmute from the DAW, i'd have a "monitor" buss (another pre-fader send from master) for the room monitors so i can just mute and unmute rather than switch none or h/w out, but i just didn't want another buss... lol ? DAW template - 01 - process.svg DAW template - 02 - mix.svg DAW template - 03 - workspace.svg
  24. I believe JohnnyV had the best option - exclude in CW using the plugin manager, they're still available (in case you need a VST2 version if the VST3 is misbehaving) but hidden w/o being uninstalled. many plugins updater apps, if you uninstall the VST2, will see the configuration as "broken" and reinstall them. so, by excluding them, the updates can happen as expected, but the exclusion setting in CW means they're not visible. and it also means if you have apps which only support VST2 (but not VST3), they still have access to those plugins...
×
×
  • Create New...