Hello,
I'm using Dune in Samplitude, and the plugin causes my Midisport MIDI driver to hang when I shut down Samplitude.
This only happens whenever I have input monitoring engaged in a track where Dune is inserted when I close the host.
I'm not sure if this is a problem with Dune vs Samplitude, or Dune vs the Midisport driver, but Dune is the only plugin
I've seen that causes this issue.
Here's a screenshot of Process Explorer after closing Samplitude when input monitoring is active:
I have to close the 'usbmm4x4-0' handle in order to terminate Samplitude (Sam.exe), or else I have to wait up to 10
minutes before the task is automatically terminated. In that case I get this error/warning in the Event Viewer:
The error in the Event Viewer leads to the selected registry entry in this screenshot:
There's no other workaround (that I've found) besides closing that handle. It's extremely awkward so I hope there's a fix for this!
System:
Samplitude 11.2.1
Win XP SP3
M-Audio Midisport 4x4 MIDI interface
Sandy Bridge i7 2600 based computer
Regards,
Tobben
Dune 1.35 locks MIDI driver on host shutdownModerators: Christophe, Mark
7 posts
• Page 1 of 1
Dune 1.35 locks MIDI driver on host shutdownYou do not have the required permissions to view the files attached to this post.
Re: Dune 1.35 locks MIDI driver on host shutdownDune does not access your MIDI or Audio driver, this communication is entirely handled from the host side.
Have you tried if this problem occurs in a different host as well? Admin - Synapse Audio Software
Twitter - www.twitter.com/SynapseAudio Facebook - www.facebook.com/SynapseAudioOfficial
Re: Dune 1.35 locks MIDI driver on host shutdown
Yes, that was somewhat misleading from my side. There must be something about Dune that freaks out Samplitude, or the other way around. Samplitude has a "variable" buffer scheme, and some plugins does not like that, usually because they're never tested properly in this host. Shortly said, there is the usual ASIO buffers and additionally the so-called VIP buffers which are usually much bigger in order to provide plenty overhead for processing plugins with high latency/variable CPU load. However, I've never had any plugin cause the host to "lock" the midi driver on shutdown. IOW, it doesn't "appear" to be a buffer issue, seems more like some problem that occurs when releasing the plugin from memory when monitoring is engaged. As mentioned, there's no problem when input monitoring is inactive as far as I can tell.
I just tried briefly in Reaper but I couldn't reproduce it there. I'm not familiar with Reaper so I don't know if there are any settings that are vital, but it closed without any problem with active input monitoring... One thing I noticed is that I had to arm the record button to get live input, and there was no sound when I hit play and I tried to play along. Don't know if this matters, but in Samplitude there is input on playback also without armed recording (depending on the settings). Regards, Tobben
Re: Dune 1.35 locks MIDI driver on host shutdownOk, some progress here...
It turned out that the issue is coming from the fact that Dune calls GdiPlus.dll, and something goes wrong when the plugin is released from memory. The midi driver lock only happens when I have one or two old Elemental Audio plugins in the master bus, but it's ok with another plug from the same series. IOW, some really bizarre conflicts that were very hard to pinpoint... Anyhow, I tried various GdiPlus.dll versions without any luck, and then I did some adventurous experiments. I ended up removing GdiPlus from the WinSxS folder (what a mess that is..) and placed it directly in System32 instead. Then I injected the dll according to the registry method described here: http://en.wikipedia.org/wiki/DLL_injection - and suddenly it all fell into place. No conflicts or locked midi drivers anymore... Edit: I found a command line dll injector so I can simply start Samplitude and inject GdiPlus.dll from a batch file. Works perfectly fine and I avoid gettting almost all programs to load GdiPlus. Kinda odd solution but I'm happy that it completely eliminates the issues (so far at least). Regards, Tobben
Re: Dune 1.35 locks MIDI driver on host shutdownOk great! We'll check if there's anything in the GDI+ code that could be changed.
Orion used to employ a variable buffer scheme too, so all our instruments and plugins should work with it. Fixed buffer is better though, more compatible, and the plugins have to chop the buffers anyways. If both sides do it, it wastes CPU. Admin - Synapse Audio Software
Twitter - www.twitter.com/SynapseAudio Facebook - www.facebook.com/SynapseAudioOfficial
Re: Dune 1.35 locks MIDI driver on host shutdown
Indeed, Dune has no problems at all with the buffer scheme in Samplitude. I'm not familiar with Orion's buffer scheme, but I suspect it was different (?). The buffers are set track per track in Samplitude. There are lots of variations here, but I'm typically using a scheme where tracks are Economy (big buffer) by default, but a track is automatically switched to low latency (ASIO buffer only) once the monitoring button is engaged in the track. Plenty headroom to process "playback" tracks while having automatic low latency monitoring simultaneously. Additionally, VST plugin buffer size can be set to full buffer, or restricted to use only ASIO buffer. I can also decide to use ASIO buffers only for all tracks, but it always results in higher CPU load compared to the variable/split buffer scheme.
Thanks, but please don't use too much energy on that. I'm pretty sure it's just some strange phenomenon that for some reason occured on my setup. I have tested the fix that I mentioned above with all my plugins, and it's rock solid. I can't break Dune/Samplitude no matter how hard I try, so it's all good now. There's another thing you could check though, if you don't mind: If I remove Dune from memory and load a new instance - the memory usage is increasing with 5-6 MB each time. Likewise, if I have i.e two tracks with Dune in each track - I get no decrease in memory by unloading one of them, and ca 13 MB increase if I reload Dune in the same track insert. This increase is also constant each time I repeat the unload/reload procedure. This seems odd to me as I can't reproduce that with any of my other plugins. It's not a very big deal as I can minimize Samplitude by clicking the taskbar button and release all wasted memory, but there seems to be a memory leak in Dune unless I'm having another "isolated issue" here... Best regards, Tobben
Re: Dune 1.35 locks MIDI driver on host shutdown
Ok great! Nevertheless we did check Samplitude prior to releasing Dune 1.4 but no issues here. Perhaps it is just this particular driver combination. Also note we'll likely abandon Windows GDI+ in favor of faster, customized code in the future, so this problem will disappear then, too. Admin - Synapse Audio Software
Twitter - www.twitter.com/SynapseAudio Facebook - www.facebook.com/SynapseAudioOfficial
7 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 197 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |