Vienna Symphonic Library Forum
Forum Statistics

194,708 users have contributed to 42,932 threads and 258,000 posts.

In the past 24 hours, we have 8 new thread(s), 19 new post(s) and 106 new user(s).

  1. Home
  2. Software
  3. Vienna MIR & Vienna Suite
  4. MIRx in MIR Pro Plug-In state not restored after reload

  • MIRx in MIR Pro Plug-In state not restored after reload

    B
    B

    I've found something reproducible which seems strange to me.

    1. Start a new project in my DAW (Reaper).
    2. Add an instrument.
    3. Add MIR Pro Plug-In as an insert.
    4. In MIR Pro Plug-In, turn on MIRx mode.
    5. Select a MIRx Venue-Preset.
    6. Select the instrument icon.
    7. Select the "Appassionata Violins" Instrument Profile.
    8. Select the "Orchestra II" MIRx Preset Alternative.
    9. Save my DAW project, quit my DAW, restart my DAW, reload the project.
    10. The large pull-down menu in the MIRx Settings Window is showing the MIRx Venue-Preset which I'd selected previously, as I'd expect.
    11. Select the instrument icon.
    12. Now the MIRx Settings button next to the label "Current MIR Pro Icon" is not lit red. This is strange. Shouldn't it be lit red, since I had it lit red before and I didn't do anything which should change that?
    13. Click the MIRx Settings button next to the label "Current MIR Pro Icon", and that turns it red.
    14. Select a different MIRx Venue-Preset (this time Mozart Hall).
    15. Save my DAW project, quit my DAW, restart my DAW, reload the project.
    16. Now the large pull-down menu in the MIRx Settings Window is again telling me "Please Select a MIRx Venue-Preset". This is strange, and it's behavior inconsistent with what I saw in (10) above. Shouldn't it remember which MIRx Venue-Preset I've already chosen?
    17. Select the Mozart Hall MIRx Venue-Preset again.
    18. Select the instrument icon.
    19. Now the MIRx Settings button next to the label "Current MIR Pro Icon" is not lit red. This is strange. Shouldn't it be lit red, since I had it lit red before and I didn't do anything which should change that?
    Trying to recover settings which MIRx in MIR Pro Plug-In had forgotten is what I was doing when it crashed, as reported in my email under Case 152951.
  • DietzD
    VSL Team
    DietzD

    I will have to look into your repro-steps in depth as soon as I find the time, but for now I can confirm that MIR Pro (plug-in version only) sometimes doesn't set the MIRx sign for a perfectly MIRx-conform setting when re-opening a previously saved Project. This is a visual issue only and doesn't affect the sound, but it can cause confusion nonetheless. It has been listed as a bug already.

    Thanks for reporting,

    /Dietz - Vienna Symphonic Library
  • B
    B
    last edited
    last edited

    @Dietz said:

    I will have to look into your repro-steps in depth as soon as I find the time, but for now I can confirm that MIR Pro (plug-in version only) sometimes doesn't set the MIRx sign for a perfectly MIRx-conform setting when re-opening a previously saved Project. This is a visual issue only and doesn't affect the sound, but it can cause confusion nonetheless. It has been listed as a bug already.

    Thanks, Dietz. At your convenience, please consider that (16) in the list above describes an apparent bug which isn't exactly the same as the one you're confirming here; and to the best of my recollection, the "unhandled-exception" crash came when I was attempting to reset that particular setting.
  • B
    B
    last edited
    last edited

    @BachRules said:

    I've found something reproducible which seems strange to me.

    1. Start a new project in my DAW (Reaper).
    2. Add an instrument.
    3. Add MIR Pro Plug-In as an insert.
    4. In MIR Pro Plug-In, turn on MIRx mode.
    5. Select a MIRx Venue-Preset.
    6. Select the instrument icon.
    7. Select the "Appassionata Violins" Instrument Profile.
    8. Select the "Orchestra II" MIRx Preset Alternative.
    9. Save my DAW project, quit my DAW, restart my DAW, reload the project.
    10. The large pull-down menu in the MIRx Settings Window is showing the MIRx Venue-Preset which I'd selected previously, as I'd expect.
    11. Select the instrument icon.
    12. Now the MIRx Settings button next to the label "Current MIR Pro Icon" is not lit red. This is strange. Shouldn't it be lit red, since I had it lit red before and I didn't do anything which should change that?
    13. Click the MIRx Settings button next to the label "Current MIR Pro Icon", and that turns it red.
    14. Select a different MIRx Venue-Preset (this time Mozart Hall).
    15. Save my DAW project, quit my DAW, restart my DAW, reload the project.
    16. Now the large pull-down menu in the MIRx Settings Window is again telling me "Please Select a MIRx Venue-Preset". This is strange, and it's behavior inconsistent with what I saw in (10) above. Shouldn't it remember which MIRx Venue-Preset I've already chosen?
    17. Select the Mozart Hall MIRx Venue-Preset again.
    18. Select the instrument icon.
    19. Now the MIRx Settings button next to the label "Current MIR Pro Icon" is not lit red. This is strange. Shouldn't it be lit red, since I had it lit red before and I didn't do anything which should change that?
    Trying to recover settings which MIRx in MIR Pro Plug-In had forgotten is what I was doing when it crashed, as reported in my email under Case 152951.

    The bug specified in items 12 and 19 above is still present in build 5.3.13333.
  • B
    B
    last edited
    last edited

    @BachRules said:

    ... Now the large pull-down menu in the MIRx Settings Window is again telling me "Please Select a MIRx Venue-Preset". This is strange, and it's behavior inconsistent with what I saw in (10) above. Shouldn't it remember which MIRx Venue-Preset I've already chosen?

    In build 5.3.13333, I'm still getting cases where the large pull-down menu in the MIRx Settings Window is telling me "Please Select a MIRx Venue-Preset" even though I've already set it. This specific issue hasn't been acknowledged by VSL, so I don't know if it's being investigated.
  • DietzD
    VSL Team
    DietzD

    Thanks for reporting, and sorry for the inconvenience! We will look into this again as soon as possible.

    Kind regards,

    /Dietz - Vienna Symphonic Library
  • B
    B
    last edited
    last edited

    @BachRules said:

    ...Now the large pull-down menu in the MIRx Settings Window is again telling me "Please Select a MIRx Venue-Preset". This is strange, and it's behavior inconsistent with what I saw in (10) above. Shouldn't it remember which MIRx Venue-Preset I've already chosen?....

    Trying to recover settings which MIRx in MIR Pro Plug-In had forgotten is what I was doing when it crashed, as reported in my email under Case 152951.

    [IMG]http://i.imgur.com/kQp4ldA.png[/IMG]

    A month ago, MIR had forgotten the Venue Preset as described above, and when I tried to reset the Venue Preset, MIR crashed and brought down my DAW. I submitted the crash-dump under Case 152951, and VSL replied, "We are looking into the issue, and will keep you informed about progress." I've received no further reply.

    Two weeks ago, MIR again had forgotten the Venue Preset as described above, and when I tried to reset the Venue Preset again, MIR crashed and brought down my DAW again. I submitted the new crash-dump, this time under Case 153816. I've received no reply under that case.

    What have you learned from the crash-dumps? Did you receive the crash-dump I submitted under Case 153816?
  • DietzD
    VSL Team
    DietzD

    I just checked: The support-case is alive, the crash-dump is attached to it. Still I can't give you a more detailed answer right now, as the developer has other obligations ATM. Thanks for your patience.

    Kind regards,

    /Dietz - Vienna Symphonic Library
  • B
    B
    last edited
    last edited

    @Dietz said:

    ... I can confirm that MIR Pro (plug-in version only) sometimes doesn't set the MIRx sign for a perfectly MIRx-conform setting when re-opening a previously saved Project.....

    This was fixed in the update before the current one, if I recall correctly; but in the current version, this problem is back.