FaderPort 8 and FaderPort 16 General Discussion
10 posts
Page 1 of 1
Sometimes, when I load an instrument plugin, FP16 loses the contents of the OLED displays.

After analyzing the communication with a MIDI monitor I found the reason for these issue:

Normally Studio One is constantly sending „A0 00 00“ to the FP16 (every second) to ensure the connection.

BUT: whenever loading an instrument plugin, Studio One STOPS sending „A0 00 00“ UNTIL the plugin has completed loading. If the loading process lasts too long (more than a few seconds), FP16 is reset (timeout) and deletes the contents of the OLED displays.

What can I do to fix it?

Mac OS 11.6.1, Studio One 6, Mac Pro Late 2013, 32 GB RAM, 1 TB SSD
User avatar
by Bbd on Tue Jul 13, 2021 6:58 am
What UC version are you running?
Does the FP16 have the latest firmware installed?
Contact support.

Bbd

OS: Win 10 x64 Home, Studio One Pro 6.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 32GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
User avatar
by ftafner on Tue Jul 13, 2021 9:40 am
Meanwhile (after updating) everything on the latest version.

But the issue still remains.

Mac OS 11.6.1, Studio One 6, Mac Pro Late 2013, 32 GB RAM, 1 TB SSD
User avatar
by Bbd on Tue Jul 13, 2021 1:08 pm
OK then please contact Support.

Bbd

OS: Win 10 x64 Home, Studio One Pro 6.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 32GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
User avatar
by ftafner on Wed Jul 14, 2021 7:12 am
Bbd wroteOK then please contact Support.


Done already.

But besides, maybe another user here notices the same issue. Would be interesting to me to know if I'm the only one ;) posting.php?mode=quote&f=337&p=268144#

Mac OS 11.6.1, Studio One 6, Mac Pro Late 2013, 32 GB RAM, 1 TB SSD
User avatar
by Bbd on Wed Jul 14, 2021 9:44 am
I own the FP16 and have not scene this issue before.
Please post back what support says about it.
Thanks.

Bbd

OS: Win 10 x64 Home, Studio One Pro 6.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 32GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
User avatar
by ftafner on Wed Jul 14, 2021 2:03 pm
Bbd wroteI own the FP16 and have not scene this issue before.

Do you use plugins that demand very much RAM (e.g. Superior Drummer 3)?


Bbd wrotePlease post back what support says about it.

Yes, I'll do.

Mac OS 11.6.1, Studio One 6, Mac Pro Late 2013, 32 GB RAM, 1 TB SSD
User avatar
by Bbd on Wed Jul 14, 2021 4:20 pm
I do use Superior Drummer 3. Have not seen it interfere with FP16.
Let us know what Support says.
Thanks.

Bbd

OS: Win 10 x64 Home, Studio One Pro 6.x, Notion 6, Series III 24, Studio 192, Haswell CPU: i7 4790k @ 4.4GHz, RAM: 32GB, Faderport 8/16, Central Station +, PreSonus Sceptre S6, Eris 3.5, Temblor 10, ATOM, ATOM SQ
User avatar
by ftafner on Thu Jul 15, 2021 3:19 am
Support has got all the facts and is working on it meanwhile. I'll tell you what they say.

Meanwhile - if you'd like to support me - you could do me a little favour:

With the use of a MIDI monitor app you could verify if Studio One does the following also in YOUR equipment:

Normally Studio One is constantly sending „A0 00 00“ to the FP16 (every second) to ensure the connection. BUT whenever loading an instrument plugin, Studio One STOPS sending „A0 00 00“ UNTIL the plugin has completed loading.


Why? Maybe there's a difference between Studio One on Mac and Windows (I see that you are using Windows while I use a Mac) ...

Mac OS 11.6.1, Studio One 6, Mac Pro Late 2013, 32 GB RAM, 1 TB SSD
User avatar
by ftafner on Wed Aug 11, 2021 5:44 am
You asked me to let you know what the Presonus Support says.

I had a very sad experience with those guys. They could not help me, because they only went through their standard question list (e.g. "Do you use the latest software versions", etc.) and did not REPRODUCE the situation on THEIR computers.

Instead of that they told me: "You have very many things connected and many things installed. Too many things installed really". From my point of view this is nonsense. I do use many apps on my system, but never had ANY big problems with OTHER applications.

The only thing that was useful was their hint to take another computer and try it there. By doing this I saw the same issues as before. So the assumption of the support was that my Faderport must be defect.

I don't agree with this. I do have experience with MIDI and programming, so I decided to code a test app to explore the way Faderport 16 communicates with Studio One.

And that is what I will do in the next weeks. I will inform you about my results.

Mac OS 11.6.1, Studio One 6, Mac Pro Late 2013, 32 GB RAM, 1 TB SSD

10 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 9 guests