Strategies to integrate emote plug-in into DAW workflow?

Home Forums Products Rackmount Strategies to integrate emote plug-in into DAW workflow?

  • This topic is empty.
Viewing 2 reply threads
  • Author
    • #116148

      I’m currently creating a dummy track with a single instance of emote to load the correct settings with my song.  My brain would gel with the mental model a bit better if I could have an emote instance per track that is routing to or from the H9000.  Is there any harm in running multiple instance of emote plug-in?

    • #156055

      It seems like the H9000 works ok with multiple instances controlling. I’ve definitely had the stand-alone and AAX one active at the same time and didn’t notice any errors.

      I’ve made a mono Aux track template in Pro Tools that I recall for sessions with Emote as the only insert and all of the Functions mapped for automation. I then use a Window Assignment to recall the plugin window throughout the mix and normally just work with the one interface. For keeping track of the routing & what FX is on which send I add notes to the comments field on the PT tracks and so far have been running 2-3 stereo chains on the first three engines to allow for multiple FX and 4 stereo algorithms on the Fourth engine which are generally a 2016 and some delays that are more general settings for the mix. This is in my normal mix setup (the returns are all built in a template session and then I just delete any unused ones).

      When using it ‘creatively’ writing all of that goes out the window and I’ll usually insert I/O directly on the track I’m working on.


      Hope some of that is useful!

    • #156086

      I think I’d get cockeyed with more than one emote instance in my DAW. Better to label the tracks in the track notes. 

Viewing 2 reply threads
  • You must be logged in to reply to this topic.