Solved Drag and drop MIDI issue (Plugins?)

[lowerfreq]

Hello,

Issue started today when trying to drag and drop vst3 instruments from a plugin window to the arranger window.

Example: Dragging a drum groove from EZDrummer to the arranger window results in a general midi file but not the actual midi groove from the EZDrummer window...

Same for other vst3 instruments...

Any ideas?

Thanks!

 

[Number6]

Probably not the issue but just checking.
Are you running any audio apps (i.e. studio one) as administrator?
If so....don't.

 

[lowerfreq]

Thx for the thought... Not running as admin at this point. Only change to S1 was I downloaded and installed the beta version of Scoring tools for the Macro Organizer...wanted to try it before purchasing... I'm not blaming you, Lukas, I'm just just troubleshooting. How does one uninstall a macro and/or extension in S1?
Thx again...

 

[Trucky]

I doubt it's related to the Scoring Tools 2 beta but here's where to uninstall it...

I'm running Scoring Tools 2 (1.9.9.4 beta release) and not having any drag and drop issues with EZdrummer 3.

 

[lowerfreq]

Thanks... I will uninstall just to check. Didn't get a chance to use Scoring Tools but it looked useful in conjunction with keyboard shortcuts.

 

[lowerfreq]

Uninstalled Scoring Tools and still no luck with drag and drop, so that wasn't the problem...and now I can't even select any events with the mouse tools..!

I opened an older project in Studio One 6.6 and drag and drop is working fine... hmmm. I would like to avoid reinstalling S1 7.2 if I can avoid it but will do it if its the best solution. Everything was working fine the last time (a couple days ago)...Any other thoughts? Thank you for your help.

 

[Trucky]

Your signature lists Studio One 7 so be sure to download and install the latest Studio One 7.2.1 release...

Can you post screenshots of your settings in Studio One 7 Options -> Locations for:
User Data, Soundsets & VST Plug-ins?
Also please confirm that the "Scan at startup" option for VST Plugins is enabled.

Having both Studio One 6 and 7 installed on your computer should not be a problem and makes it easier for testing purposes.
I have Studio One 4, 5, 6 & 7 clients and have each of those versions installed on my computer so I'm able to support them.

 

[lowerfreq]

Does anyone have any tips/suggestions for the best practice of consolidating all vsts in one location for S1 7.2 ? Unfortunately, they are on two different drives and in many different folders. When I've tried to consolidate in the past(vS1 6), I ran into a bunch of problems where the plugins were expected to be in the old location and wouldn't function correctly. Some vst manufacturers seem to be a little precious about where they must be located... does this make sense? Thx...

 

[OutrageProductions]

VST3 should only exist in the Steinberg recommended default directory, VST2 can be consolidated EXCEPT for WAVES, as they are picky about where they live.

 

[lowerfreq]

Start up scan option was already enabled. The current locations for User Data, Soundsets & VST Plug-ins is as follows:

User Data: F:\Songs 2025
Soundsets: H: Studio One Soundsets
VST Plugins: Various folders on two drives... way to many tbh... I posted another thread about consolidating these, thinking multiple locations might be the problem.

Thx!

 

[lowerfreq]

Thank you... I will try your suggestion!

 

[Trucky]

Start up scan option was already enabled. The current locations for VST Plug-ins is as follows:
VST Plugins: Various folders on two drives... way to many tbh... I posted another thread about consolidating these, thinking multiple locations might be the problem.

Yes, I'd agree that's your problem.
All your plugins should be installed to the default locations on the C: drive...

C:\Program Files\Common Files\VST3
C:\Program Files\VSTPlugins
C:\Program Files\Common Files\CLAP

 

[Number6]

I don't know about CLAP.
Let's be clear here you can choose any folder or drive as long as it is organised and installed correctly.
The exception is (annoyingly) VST3, that drive and file path must not change as per Steinberg recommendations.
It's a good idea to install 32 bit plugins to a separate folder so they can be easily excluded (or better still don't install them).

 

[Jemusic]

I have found from years of experience (on Windows) that installing plugins in the very default locations as per Trucky’s recommendations results in the least issues with them being found. There is no actual need to install them anywhere else as they are not large files and they don’t take up much space. The moment you start installing them in other locations is when trouble will usually start. Even when you point the plugin scan there it will often not work.

Large synth and sample libraries yes for sure. External drives are fine because you can point the instruments to those locations easily and they will be found.

 

[lowerfreq]

All makes sense... begs the question though as to why at this late date am I having the issues. I've had these things in their current locations for over 5 years.
Maybe it's time to upgrade the computer, though that would be a costly endeavor. I guess it's pay me now or pay me later


Thx all...

 

[Number6]

I have found from years of experience (on Windows) that installing plugins in the very default locations as per Trucky’s recommendations results in the least issues with them being found. There is no actual need to install them anywhere else as they are not large files and they don’t take up much space. The moment you start installing them in other locations is when trouble will usually start. Even when you point the plugin scan there it will often not work.

Large synth and sample libraries yes for sure. External drives are fine because you can point the instruments to those locations easily and they will be found.

Honestly never had an issue either. As long as you have a strategy to install them in specific locations.where you want (VST 3 the exception) and not all over the place (years of experience too).

 

[lowerfreq]

No success. Still having the same issues (dragging a midi file only opens a new song and not being able to select/swipe events in the arranger window with mouse tool) after trying your suggestions and updating S1 to the latest version. Also opened a support ticket with Presonus...

 

[lowerfreq]

After numerous back and forth correspondence with Presonus support, the issues were solved, though I am not sure exactly what the real problem was... at this point, I'm not concerned, though generally I would like to find out the root causes of problems so I know how to tackle them if the were to pop up again. Anyway, a combination of reinstalling S1, updating S1 a bunch of times, checking computer info files, BIOS etc. , and we're good to go.
Support seems to get a bad rap a lot of the time, but I will say I have had very competent reps in my dealings with them, so a shout out to all working in that branch of Presonus... Salud! Thread solved.