Vienna Symphonic Library Forum
Forum Statistics

194,355 users have contributed to 42,916 threads and 257,956 posts.

In the past 24 hours, we have 2 new thread(s), 9 new post(s) and 80 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. MIRacle plugin acting strangely in Logic

  • MIRacle plugin acting strangely in Logic

    D
    D

    When invoking the MIRacle plugin in Logic, I notice that I can't move the EQ parameters around in the graphic display.  The parameter numbers change accodingly but the display does not update.  The display and the parameters seem to update correctly in both VEP 5 and also in Sibelius 7.  Also, after changing the numbers directly in the parameter boxes below the display, the display does not update.

    Not sure whether this is an OS problem, a Logic problem or a plugin problem.  Before anyone comes in and starts blaming Logic, I'll note that other plugins (including Vienna MIR Pro) work correctly in Logic in this regard.

    OS X 10.8.2, Logic 9.1.7, VEP 5.1.11548
  • M
    M

    That's a good catch on your part.

    I tried Logic 9 and as you've said, the EQ parameters do not move in the graphic display.

    I tried Pro Tools 10 and the EQ parameters DO move in the graphic display.

    Here we go again.... Just when I was ready to consider migrating projects back to Logic from Pro Tools.
  • M
    M

    Correction, correction, correction...

    Using Logic 9, I decided to build a large (MIR Plugin) template just to see EVERYTHING on the same MIR stage.

    When I added MIRacle it worked properly. The EQ parameters did infact move as they should. Odd because earlier they did not.
  • D
    D

    It works for me once I insert a VI Pro2 instrument to one of the instrument channels and also insert MIR Pro on that channel.  And it continues to work after setting that instrument to no plugin.  So this is very odd, but is workable I suppose.
  • M
    M
    last edited
    last edited

    @dbudde said:

    It works for me once I insert a VI Pro2 instrument to one of the instrument channels and also insert MIR Pro on that channel.  And it continues to work after setting that instrument to no plugin.  So this is very odd, but is workable I suppose.

    Hmmmm, interesting combination. You're in the United States, are you old enough to remember the Ford Pinto?

    If one was unfortunate enough to be rear ended, while their foot was on the break, the left turn signal was flashing,

    and the air conditioner was running......... The Pinto burst into flames.

    Keep an eye on your Mac.  [:P]
  • D
    D

    Yes, I remember that Pinto issue.  

    As for the plugin issue, it seems as long as you insert the instrument and MIR pro before inserting MIRacle then MIRacle works fine in Logic.  So it seems there is still some dependency between these programs for initialization or something.  They were once fully coupled as part of VE Pro, now are supposedly separate plugins.  

    For what it's worth, the first time I ran Logic after installing the most recent MIR/MIRacle plugins, MIRacle failed the Logic plugin validation.  But after rerunning it, it passed.  So there is something going on that is not getting initialized correclty.
  • M
    M

    Forgive my attempt at humor, but I thought that was funny.

    Not so funny, I concur with your findings in Logic... Unfortunately, Logic may once again not be playing nice with VSL.

    In Pro Tools 10, I simply opened a new session, assigned MIRacle to the Master Channel, and it worked properly.

    No MIR, and no VI Pro 2.

    I'm still working on that Logic / MIR Plugin Template. If the end result does not overtax cores or CPU in Logic, I will happily return.

    Don't know about you, but for me the good news is I have no need for MIRacle without MIR, so as you've said, it works (sort of).
  • M
    M

    MIRacle's damping and eq graphs will not update unless the channel has processing enabled. Logic tends to turn off processing on certain channels, depending on if they are active or not.

    I have now changed the behavior, so that the graphs behave properly in Logic. Next update will contain the fix.
  • D
    D

    Thanks Martin.