Jump to content

Andrew C

  • Posts

  • Joined

  • Last visited

Profile Information

  • Location
    Arizona USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Andrew C's Achievements

Advanced Member

Advanced Member (3/8)

  1. Dude that's funny! I got a laugh out of that one, although I'm sure it wasn't funny for you. I'm sorry you had to deal with such an a**hole. I deal with stuff like that all the time in my day job and can't believe what kind of crap people will try to pull. A good story though to showcase what an ungrateful bastard looks like. Andrew
  2. This is a pretty cool thing to know. I'm not sure if or when I would use that, but it is something I probably wouldn't have ever figured out how to do myself. I love this forum! AC
  3. Yes, I know what you mean about using object automation to increase workflow. It is a very quick way of doing things and to be honest with you, I have never been a big fan of having my faders moving all over the place by themselves with track automation. Again, that is why I personally like to automate volume at the object level. It leaves me free to adjust my faders right down to the last second before I pull the trigger and mix down to stereo. My previous DAW had the ability to make ALL automation pre-fader, whether it be track or object, so you could automate like crazy and your faders wouldn't move, if you chose to select that option. This is probably the only feature I miss from my previous DAW, but the rest of it was garbage.
  4. byxx, I personally will freeze a MIDI object when I need to do a volume automation or volume change ONLY on those specific objects. I prefer doing things this way because volume changes on the object level are pre-fader, meaning that the fader will not move with those volume changes. You will hear the volume change, but it will not be seen as fader movement. I will tell you why this is important to me: I can still raise the volume up or down for that entire track with the mixer's fader even after the object's volume has been automated. On the other side of the coin, If you were to bounce the entire track to audio and then do volume automation changes, your mixer fader will be locked to the volume which has been written in the automation line. You cannot continue to "mix" with the fader after automation has been written. There always seems to be a time where I still want to be able to control the track's overall mix volume after I automate certain things, and this is why I try to do my major volume automation at the object level. And to answer your question about TRACK automation on MIDI objects: Yes, track volume automation on MIDI objects is controlling the audio volume, not the MIDI velocity. I hope I explained this satisfactorily without making it too confusing.
  5. One workaround is to freeze the MIDI object, and then you can adjust it's volume in the object editor. Also, you can apply object volume automation on it once it is frozen, whereas volume automation does not work on MIDI objects. Freezing a MIDI object is essentially a fully-reversible bounce to audio. You can always un-freeze the object back to MIDI to edit it.
  • Create New...