Jump to content

Glenn Stanton

Members
  • Posts

    1,626
  • Joined

  • Last visited

Reputation

954 Excellent

About Glenn Stanton

  • Birthday June 8

Recent Profile Visitors

3,357 profile views
  1. thanks. i get the same behaviour - the kick produces 8 empty tracks + 1 with the notes. and definitely has the type 0 flag. the hats produce the expected number of separate tracks and is type 1. the kick MIDI only has the 1 track marker, and i'm not seeing in Hex editor what is causing the additional tracks. then again i'm not a MIDI format expert by any means... 🙂 MIDI files from DRUMTRAX do the same thing as the Goran files, whereas Groove Monkee MIDI imports as expected. type 0 single track, type 1 however many tracks. @msmcleod any thoughts on why some MIDI files are causing the extra track inserts? COU_192 is DRUMTRAX (generates extra tracks) COU_192.MID
  2. is it possible to share one of the MIDI files? presumably any length of the MIDI (like a 1 measure fill) will present the same issue?
  3. so basically each MIDI file regardless of type is creating a MIDI track for each instrument - kick, snare, hh, tom1, tom2, etc crach 1, ride etc? or are the extra track CC only and not MIDI notes on them?
  4. @John Vere did a whole video on inexpensive IO units
  5. typically the audio is going to be the variable tempo. unless someone really went out of their way to humanize any MIDI sequences. you may be entering the world of "audio snap" 🙂 or the world of "remix" where you convert the instrument audio to MIDI, quantize it etc and use virtual instruments to recreate it, then tweak the vocal and solo parts over that...
  6. best bet is to only comp based on the performance quality and then use something like melodyne etc to tweak gross timing, and then inphase or align2 etc to get the final phase alignment. or go to the 3 mic trick 🙂 basically use the tool for what its best at.
  7. @msmcleod could a VST3 preset be used with a VST2 plugin? perhaps if the controls for each are effectively the same but i'm not use if it's using an internal id for a given control or just the control name.
  8. the challenge is the "takes" in physical form are not in parallel. they are part of the long WAV file, and takes are simply time marked sections of that file which are then shown to you in parallel. so trying to tweak the takes "in time" are generally not easily done - either through programming or physically altering the file -- which is the option Max shared. the other option is not to use take lanes and record each take to a separate track. if using this option, you can end up with a lot of tracks - so i like to export the instrumental part (wher the arrangement is mainly settled) and then use that in a separate projects for vocals only (i may do the same for tactic soloing as well). then once you've comped things, export the tracks and insert them into your main project.
  9. no worries. just keep in mind that once you step beyond the first few recordings and now you want the higher quality, or acoustic mic etc, there are many inexpensive IO units which will give you audio + MIDI etc greatly expanding your options.
  10. after adding the image, save the file as a CWP (normal), then go to the folder (i have one called "templates") and make a copy of it. then renamed it "mytemplate".cwt (where "mytemplate" is whatever you want to call it - use 00, 01, 02 in front of the template name to make them sort to the top -- e.g. "00 record template" "01 mix template" "02 master template" etc) so: create or edit the new or existing template.CWP file insert the image into the notes section of a NORMAL project save as CWP copy & paste the CWP (so you can go back and edit it again later without starting over) rename the copied CWP to the template name (usually remove the word Copy) and extension of CWT copy the CWT into the \common\project templates and the \core\project template folder if you need to revise the template, then follow steps 1-5 and ignore step 2 (you already did)
  11. check for the Windows and OS related updates as well. the supposedly backward compatible redistributables can be the cause. like today for me - new KB updates on the OS - so a quick run of the redistributables and rescan VST to be sure. everthing seems to be running normal. i just get into the habit of doing this to avoid finding out i have issues when i'm working on a live project...
  12. are you connecting directly to the PC USB port or via a hub? many IO units do not like hubs. also check - is it possible the USB port is disabled? maybe plugin some other device to see if its active? do you have another IO device or could borrow one to see if it's something else in the system?
  13. the only challenge (assuming all other steps are possible and my thought was auto-hotkeys) is selecting the track template. i don't believe there is a generic track template which is used by default when simply inserting a new track.
  14. and every other audio program as well 🙂 so, it's not even showing up in the device manager at all? sound controllers? software devices? audio inputs and outputs? there are several sections it could appear under.
  15. maybe your device has died? maybe you need to get the latest drivers from Presonus and reinstall it? maybe there are some troubleshooting steps on the Presonus site? if it's not showing up in the Windows device manager, then you need to fix that first. https://www.fmicassets.com/Damroot/Original/10001/OM_2777700106_AudioBox-Go_EN.pdf https://www.presonus.com/en-US/interfaces/usb-audio-interfaces/audiobox-series/2777700106.html
×
×
  • Create New...