194,715 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 109 new user(s).
I bought MIR 24 with Roompack 2 and it's great! I'm using it as a DAW plug-in to DP 8. Only downside I'm finding is that each time I hit save on my DP project, it takes 4-5 seconds, and since I save frequently, the extra time adds up. I have all my VEP instances decoupled. Are there any settings I can change that might counteract this problem?
Thanks,
Peter
This is to add on to my original post. Saving in DP 8 using MIR24 as a DAW plug-in feels like saving with VEP coupled (and I always work with all my VEP instances decoupled). Since I have auto-save enabled, I'll often experience a several-second delay after I try to execute some command—either changing a value, hitting record, etc., because the program has decided to save at that moment. (Same delay happens when I save manually.) Is there some way to do the equivalent of "decoupling" MIR in this situation? Obviously this is mostly a question for Paul, Dietz, etc.
Thanks,
Peter
Great—thanks! Actually, as a follow-up thought—if I were using MIR within VEP on the slave machine that hosts my VSL library (instead of as a plug-in within DP), and if I were working in decoupled mode, would I not have this problem? My slave machine is a Mac Pro Quad-Core from 2006, hence my reluctance to do that. Plus I love the convenience of having it within the DAW.
Peter
Just tried to reproduce what you describe, and with 24 plug-ins active, I cannot experience the delay you report. Saving takes maximum 100ms here.
I suspect that you might have some other plugins in your project, that take a long time during saves. Could you please try to create a bare project with empty tracks containing a MIR plugin, to see if the saving delay still occurs?
Thanks,
Martin
Just tried to reproduce what you describe, and with 24 plug-ins active, I cannot experience the delay you report. Saving takes maximum 100ms here.
I suspect that you might have some other plugins in your project, that take a long time during saves. Could you please try to create a bare project with empty tracks containing a MIR plugin, to see if the saving delay still occurs?
Thanks,
Martin
Hi Martin—thanks for checking this out. Before taking your suggestion I tried something else. I had neglected to mention in my original post that I also had four instances of the Vienna MIRacle plug in my project, one on each of my four audio stem busses. As soon as I removed those, the saving delay problem went away completely. When I undid those removals one by one, each time a MIRacle plug was reinstantiated the saving delay got longer; when all four were back in the project, the saving delay was at its original length. BTW I'm using the latest versions of DP, VEP, and MIR 24. (The only other plugs in the project are Waves L3-LL Ultra, Rverb, and REQ 4—none of them have ever given me this kind of problem, and as I said, without MIRacle the problem went away.)
I'll PM you soon with either the DP file itself (if that's possible) or a link to the file (if not). Thanks again!
Peter
And in fact... you don't even need to download the file I just sent you to see what I mean about MIRacle. I just created a completely blank DP project. Then I added four aux tracks, making sure that each aux track had valid inputs and outputs assigned. Then I instantiated MIRacle on each of these aux tracks one by one. Each time I did so, the saving delay increased; after I instantiated MIRacle on the fourth track, the saving delay was as long as in the project file I sent you. This is true even though the only contents of this new project were those four aux tracks, each with one instance of MIRacle. No MIR, no other data of any kind.
Hope that helps,
Peter
