lfo2k wroteUVI Falcon V1.61 does not work with S1 V4.1 (gets black listet)
But it does work in S1 V3.56

Who is to blame now? UVI or Presonus?

If an ilok plugin gives me trouble I make a point of checking for an update to License Manager then do a reset of the blacklist. Worth a shot.

I dont get the point...

I did now reset my settings folder in S1, because i did hope this will help the falcon to fly again.
After showing S1 again where my plug-ins are it starts scanning the 120 plug-ins like forever, and they dont appear in the S1 Browser.

After closing and opening S1 again i get this





bleep? And whhhhyyy???

This reset is first thing presonus support recommends every time

Even a complete reinstall of S1 4.1 did not solve the prob

I did remove the Plug-Ins from the folder. Restarted S1, closed it again. Did insert a couple again in the folder, startet S1 it keeps failing in investigation from the plug-ins. Even for melodyne.

Whats wrong with you Studio One?

Same procedure with 3.5.6 works fine. Everything works

^ Did you read my post? Remove the plugin folders, scan/reset blacklist and restart, then put them back in, rescanning and resetting the blacklist and restart.

Otherwise I suggest you start a new thread for your specific issue.

Yes i did read your post, did remove all paths to all folders, reset blacklist. At next restart the basic folders are inserted from S1 itself again, and it fails in loading melodyne and all plug-ins in the default folders.

Its Win7 64Bit, Studio One 4.1 64Bit if this helps the maybe reading devs

lfo2k wroteYes i did read your post, did remove all paths to all folders, reset blacklist. At next restart the basic folders are inserted from S1 itself again, and it fails in loading melodyne and all plug-ins in the default folders.

Its Win7 64Bit, Studio One 4.1 64Bit if this helps the maybe reading devs

If you have an Nvidia card and Windows 7 please read this thread:
viewtopic.php?f=151&t=30274

You may need to wind back your Nvidia drivers or update to Windows 10.

Otherwise please start a new thread and/or contact support.

Thanks for your effort! : )
I dont have a nvidia. I did open a ticket since i dont come any further.

dannylegrand1 wroteIf they would only now ad a pipeline system for external synths it would be great....
So fed up needing to ad multiple tracks to record my external synths....
Just for that I went back to cubase and Ableton...


https://answers.presonus.com/22832/stud ... ent-plugin

Same here. If the powers that be cared about this one iota, it would have been done years ago.

+1 - tbh I've given up with this being implemented, it is so long overdue!

MisterE wrote

dannylegrand1 wroteIf they would only now ad a pipeline system for external synths it would be great....
So fed up needing to ad multiple tracks to record my external synths....
Just for that I went back to cubase and Ableton...


https://answers.presonus.com/22832/stud ... ent-plugin

Same here. If the powers that be cared about this one iota, it would have been done years ago.

My guess is this won't happen because Studio One uses it's own, custom, more controllable MIDI language and it wouldn't be compatible with external synths because of that. Just my guess though. I could be wrong. I've been wrong before.

gregghart wroteMy guess is this won't happen because Studio One uses it's own, custom, more controllable MIDI language and it wouldn't be compatible with external synths because of that. Just my guess though. I could be wrong. I've been wrong before.

You could say the same about softsynths then, strangely they work Regardless Studio One supports MIDI IN and MIDI OUT as well and Audio in and Out. That's what DAWs do.

The real reason why it hasn't been done is it hasn't been prioritised. The best way for that to happen is to vote the feature up in the feature requests forum (just 178 votes right now, I've voted it up myself even though it doesn't really effect me).

gregghart wroteMy guess is this won't happen because Studio One uses it's own, custom, more controllable MIDI language and it wouldn't be compatible with external synths because of that. Just my guess though. I could be wrong. I've been wrong before.

Yes, your guess is wrong Studio One would be fully compatible with external synths. It just has to be done. It hasn't yet.

And yeah, it's always a good idea to vote for a feature request.

BobF wrote
I just replicated this in Win10. Studio One vanishes after a brief delay.

I'll submit a report on it.

Hi --
Just ran into this same problem! Hadn't tried to merge a stereo file until yesterday.
I have submitted a ticket.
But I'm curious to know if the issue was addressed somewhere else or resolved for you.
Thanks --
Lisa

jazzundso wrote

gregghart wroteMy guess is this won't happen because Studio One uses it's own, custom, more controllable MIDI language and it wouldn't be compatible with external synths because of that. Just my guess though. I could be wrong. I've been wrong before.

Yes, your guess is wrong Studio One would be fully compatible with external synths. It just has to be done. It hasn't yet.

And yeah, it's always a good idea to vote for a feature request.

I would if I considered proper mixer support for external instruments a feature but that is something every other major DAW has long ago decided is a necessity. Fine. I got my money's worth out of 2.6 which is still viable for audio productions. Now I've abandoned Presonus just as surely as they've abandoned anyone who wants to get the most out of their external instruments.

With Studio One you can still work very successfully with external instruments. I have up to 9 external instruments that most often form a major part of many productions that I do.

I work with the midi tracks until close to the mix down stage. Then you create audio tracks for each of them and print the parts to audio. (In real time) It is advisable to do this anyway before a mix. I just mute the midi parts and pop them In a folder for later reference.

Then the printed external parts are all there and ready to process just like the other audio tracks.

What I would like though is while the external instruments are in midi mode it would be nice if all the Faderports actually saw them which they don't unfortunately. Eg be able to arm, record, solo, mute etc...

If this request to create a single track for external midi/audio solves that issue then I am all for it. For me the Faderport not seeing any external tracks is a bigger issue than having to create audio tracks and print the external parts. You don't need any special Pipeline features to do this either. It is not much different.

MisterE wrote

jazzundso wrote

gregghart wroteMy guess is this won't happen because Studio One uses it's own, custom, more controllable MIDI language and it wouldn't be compatible with external synths because of that. Just my guess though. I could be wrong. I've been wrong before.

Yes, your guess is wrong Studio One would be fully compatible with external synths. It just has to be done. It hasn't yet.

And yeah, it's always a good idea to vote for a feature request.

I would if I considered proper mixer support for external instruments a feature but that is something every other major DAW has long ago decided is a necessity.

The feature request on answers.presonus.com is already a suggested solution for the problem ("plugin for external instruments"). In general it's more interesting what the user intends to do than how the user would think of a possible solution for the problem.

We all know that the topic "External instruments" is much bigger. So if you vote for this feature, it shows that you're interested in the whole external instruments topic. It seems you are.

BobF wrote

tommikujala wroteIs there a bug in "merge to stereo file" command in browser, when you select two mono audio files and right click. Crashes here on S1 4.1 mac OS X 10.13.6

I just replicated this in Win10. Studio One vanishes after a brief delay.

I'll submit a report on it.

Does anybody care about this problem?
I've heard nothing from Support about my ticket.
I uninstalled 4.1 and reinstalled 4.0.
I hope this will only be temporary.
: (

Jemusic wroteI work with the midi tracks until close to the mix down stage. Then you create audio tracks for each of them and print the parts to audio. (In real time) It is advisable to do this anyway before a mix. I just mute the midi parts and pop them In a folder for later reference.

Then the printed external parts are all there and ready to process just like the other audio tracks.

Yes, that workaround exists (Lokefly also pointed it out) now and has existed since Day One of S1 and I used it to record a whole bunch of tunes. Problem is, I could have created those parts a lot easier and quicker if I was working in any other major DAW. Those projects were audio-dominated, so I put up with the external instrument workaround; however, my current and next projects will be MIDI-dominated and use a bunch of hardware synths, and I just can't endure any more workaround frustration.

It's too bad cause I was very comfortable with the rest of the program.