ReaSonus FaderPort; Full FaderPort v2, 8 & 16 support with CSI

[diogobenjor]

Originally Posted by mixnmstrng

Hello, is there any function assigned to the footswitch in the faderport v2? if not, can you tell me in which file you can assign a function to a footswitch? thx

I'd be interested in that, too! Anyone?

[jadedsean]

Can someone here help me, after setting this up i have an issue. Everytime i try to write a different automation mode such as pan or mute once i touch the fader on my FP it resets to volume, meaning i can only use volume with this controller.

[Clegs]

The automation drawn in the Touch mode is a zagged, sawtooth-like up and downs line. I should be a smooth line that tracks the fader movement. Example: On volume automation this results in tremelo-like juttering. Note: The Latch and Write mode work perfectly as they should so it's probably just need a code correction. Hope this is fixed, as it's a much used function.

[Clegs]

Solo, mute, and fader don't affect multiple tracks when more than one track is selected.

Also, in the multiple tracks selected situation, you can't just clear solo or mute for those selected tracks, i.e., like a toggle (you can clear all throughout the project, but not just the multiple selected tracks).

It would be great to have these functions.

[Geoff Waddington]

Originally Posted by jadedsean

Can someone here help me, after setting this up i have an issue. Everytime i try to write a different automation mode such as pan or mute once i touch the fader on my FP it resets to volume, meaning i can only use volume with this controller.

Most likely .mst/.zon file related.

Please post the contents of your .mst and Track.zon files.

[Geoff Waddington]

Originally Posted by Clegs

The automation drawn in the Touch mode is a zagged, sawtooth-like up and downs line. I should be a smooth line that tracks the fader movement. Example: On volume automation this results in tremelo-like juttering. Note: The Latch and Write mode work perfectly as they should so it's probably just need a code correction. Hope this is fixed, as it's a much used function.

Most likely .mst/.zon file related.

Please post the contents of your .mst and Track.zon files.

[Geoff Waddington]

Originally Posted by Clegs

Solo, mute, and fader don't affect multiple tracks when more than one track is selected.

Also, in the multiple tracks selected situation, you can't just clear solo or mute for those selected tracks, i.e., like a toggle (you can clear all throughout the project, but not just the multiple selected tracks).

It would be great to have these functions.

We originally designed CSI to affect only one Selected Track to avoid unintended consequences when all Selected Tracks were not simultaneously visible on the Control Surface.

We are rethinking that decision, stay tuned...

[jadedsean]

Originally Posted by Geoff Waddington

Most likely .mst/.zon file related.

Please post the contents of your .mst and Track.zon files.

Could you explain how i should do that please?

[Geoff Waddington]

Originally Posted by jadedsean

Could you explain how i should do that please?

Did you set this up using the provided installer ?

[jadedsean]

Originally Posted by Geoff Waddington

Did you set this up using the provided installer ?

Yes i did.

[Geoff Waddington]

Originally Posted by jadedsean

Yes i did.

Ok, I'll see if I can find anything in the packaged files.

[jadedsean]

Originally Posted by Geoff Waddington

Did you set this up using the provided installer ?

Strangley enough i do not have a Reasonus folder in my directory. When i originally installed it it went into the standard path way but, i don't use this version so often so i made a portable install. First i deleted the old files from the standard version and then reinstalled the portable version.

[Geoff Waddington]

Originally Posted by jadedsean

Strangley enough i do not have a Reasonus folder in my directory. When i originally installed it it went into the standard path way but, i don't use this version so often so i made a portable install. First i deleted the old files from the standard version and then reinstalled the portable version.

Ah, Ok, this sounds more like an install issue, probably best to contact Navelpluisje, he's the one who wrote the installer.

[jadedsean]

Originally Posted by Geoff Waddington

Ah, Ok, this sounds more like an install issue, probably best to contact Navelpluisje, he's the one who wrote the installer.

Okay will do, thanks

[jadedsean]

Originally Posted by Navelpluisje

ReaSonus FaderPort
Currently working on a full working implenmentation of CSI for the Presonus FaderPort v2, 8 & 16. This will include an installer to:

• Install CSI
• Create a CSI ini file
• Add the CSI to the control surfaces in REAPER
• Add and register all actions needed
• Install all the files fo configuring the controler

This all in just 2 mouse clicks.

Documentation: https://navelpluisje.github.io/reasonus-faderport/
Installer: https://github.com/navelpluisje/reasonus-install/releases/latest

Control Surface Integrator (CSI)
ReaSonus uses a custom build of CSI v1.1. There are a lot of things added for the FaderPort. Here is a list of the extra's added:

• Support for all display types of the FaderPort
• Added a track number action
• Text alignment and invert colors for the display lines
• Added the value bar
• Added the VU meters
• Fixed the track colors

If you have other surfaces running on CSI v1.1, they just keep working. All existing functionality has been kept as-is

CSI v1.1 has been discontinued and it's doumentation has been removed.

ReaSonus will be ported to CSI v2 as soon as possible. There are some things which also need to be fixed in CSI v2 to make the FaderPorts work well with v2. I will try to update on this process in this thread

Current Version (v1.0.1)
Version v1.0.0 has been released. This new major version adds the ReaSonus FaderPort control to manage your function keys and mix management filters. Fixed an issue with the encoders and a lot more.
Read all about this release

Version v1.0.1 resolves a bug where the midi devices were not loaded on installing. Read all about this release

Known Issues
Known issues can be found here

Report Issues
The preferred way of reporting issues is via Github. This way the thread does get less cluttered and gives me a better insight of open issues, without the need to scroll through the thread.
You can report issues here


This post will be a living document.

Edit: Changed the version

Hey man can you please help me? After setting this up i have an issue. Everytime i try to write a different automation mode such as pan or mute once i touch the fader on my FP it resets to volume, meaning i can only use volume with this controller.

[creator31]

Originally Posted by jadedsean

Everytime i try to write a different automation mode such as pan or mute once i touch the fader on my FP it resets to volume, meaning i can only use volume with this controller.

Hi jadedsean,

I had a similar problem where I thought I'd installed everything correctly, but possibly not.

It was a while ago, and I can't remember the details, but I had to remove the Faderport from the Preference Control/OSC/web, leaving the CSI in place. Sorry for the lack of details (my brain is a swamp), but maybe it can help...

[smoochdaddy]

Hi, I tried to set up reasonus and reaper and am not able to open to any of my projects in reaper . I went into non plugin safe mode and reaper will not open that way either. I appearently created a bad CSI ( I think its called in preferences, ( you know the section where you can create a reaper remote for you tablet) that section. I am new to reaper. so please bare with me. I addd the osi controller to run reasonus that way.

I went into safe mode- no plugin mode I mean and reaper wont open. I also re istalled reaper, and also turned of the faderport 16. I cant open anything in reaper except the splash page where i can get into safe mode. How do I get to preferences and delete the reasonus, CSI that I created?

Please help.

Thanks you so kindly in advance.

Lou

****ALSO IT MIGHT BE CALLED CSI. Im trying to oadd a controller for reasonus. But want to remove the CSI It was set up incorrectly and causing reaper to not to open.

[jadedsean]

Originally Posted by creator31

Hi jadedsean,

I had a similar problem where I thought I'd installed everything correctly, but possibly not.

It was a while ago, and I can't remember the details, but I had to remove the Faderport from the Preference Control/OSC/web, leaving the CSI in place. Sorry for the lack of details (my brain is a swamp), but maybe it can help...

Thanks for the advice man but i still have the same issue, i don't know why though.

[Geoff Waddington]

Originally Posted by smoochdaddy

Hi, I tried to set up reasonus and reaper and am not able to open to any of my projects in reaper . I went into non plugin safe mode and reaper will not open that way either. I appearently created a bad CSI ( I think its called in preferences, ( you know the section where you can create a reaper remote for you tablet) that section. I am new to reaper. so please bare with me. I addd the osi controller to run reasonus that way.

I went into safe mode- no plugin mode I mean and reaper wont open. I also re istalled reaper, and also turned of the faderport 16. I cant open anything in reaper except the splash page where i can get into safe mode. How do I get to preferences and delete the reasonus, CSI that I created?

Please help.

Thanks you so kindly in advance.

Lou

****ALSO IT MIGHT BE CALLED CSI. Im trying to oadd a controller for reasonus. But want to remove the CSI It was set up incorrectly and causing reaper to not to open.

Does ReaSonus have an uninstall function ?

What operating system are you on ?

[smoochdaddy]

Hi I am on windows 10. And yes I'm gonna try that. Uninstaller for reasonus.

[jsikkema]

Looking for info on how to use custom action (or existing actions) to use the faderport v2 fader to adjust the send volume on a selected track. I see in the docs it says its possible but i don't see any other info on this. thanks!

[diogobenjor]

Originally Posted by jsikkema

Looking for info on how to use custom action (or existing actions) to use the faderport v2 fader to adjust the send volume on a selected track. I see in the docs it says its possible but i don't see any other info on this. thanks!

If I understood correctly this doesn't apply to FP V2, only the 8 or 16 fader version, but me too would love a sends-on-fader feature for my V2 too!

[Clegs]

First, thanks so much for making the Faderport a workable alternative.
Example of issue: Open a volume automation envelope, arm automation and hit Touch mode button on Faderport, press Play and move fader to write automation. The volume line drawn is a jagged up and down sawtooth line. Note that the Write and Latch mode work perfectly. Also, note that I put a comment in the Github bug reports a while back but got no answer.

[grinder]

I have faderport 1
I only need to push record!
will a version of yours at least enable me to do this?
Windows 11 has thrown the Faderport off I think it will only turn on and off.

Grinder

[grinder]

Anybody out there?
Love to read a reply I can not record acoustically otherwise
I need to record from another room?
What version should I use for a Classic v1 Presonus Faderport?
I think I have a usb 2 entry etc on my newly assembled very fast computer with windows 11.
Anybody?
Thanks

Grinder


https://soundcloud.com/steve-maitland-1/highway-73

[stevo58]

Hi - this looks great. I am sorry for this bonehead question.

When starting the installer (1.01), after setting the path correctly, no MIDI ports are found. I deleted all obsolete ports from the preferences (old interfaces, old controllers) and made sure the faderport ports are disabled. SWS is installed. I rebooted several times, no change. FP is in StudioOne mode. OS is Win10; Reaper is 6.79, interface is RME 802. Any help is appreciated.

steven

Edit: hold on. I just realized the FaderPort has an ancient firmware version (1.1, I bought this used). I’m updating and will try again.

[grinder]

Is this of any use to you? I'm omn windows 11 and have a card for USB2.
Mine is a classic v1.
"https://forum.cockos.com/showthread.php?t=170036&page=12

Grinder

[stevo58]

So, I managed to update the firmware - an exciting process. Thanks to Nick at PreSonus tech support, I learned that I have to use an old version (3.64) of the Universal Controller to update the firmware, as apparently it just won't work with my version of Windows 10. I asked if there was any reason to attempt to further update to the absolutely newest firmware, and he told me no, the version I have now installed is solid.

But it hasn't changed my problem - no midi ports are shown on the install screen, and the button is inactive.

I can use it in Mackie mode, which is better than nothing. But I would really like to use the full functionality.

I have disabled the FP ports. I have uninstalled ReaSonus and deleted the directory several times. No luck.

SWS is version 2.12, the only version presented for download. Is this correct? Any tips?

Note: the Functions entry doesn't appear on the installer.


EDIT:

Well, my recording PC is not on any network, and I haven't updated it in two years, as I like to avoid unpleasant update surprises from Microsoft. I decided it was time, though, and now everything works as advertised. FYI: I was using OS build 18362, and it just doesn't work with that build.

thx
Steven

[grinder]

Good to hear well done!

Grinder
https://soundcloud.com/steve-maitland-1/highway-73

[stevo58]

So, this works pretty darn swell.

I’d like to second the foot switch request a couple of pages ago. I’d been using the original FaderPort for the last X years, and had the foot switch set up to start recording (when the shift button was active). The foot switch, though, is something that should be configurable.

Steven

[Funkybot]

Originally Posted by stevo58

So, this works pretty darn swell.

I’d like to second the foot switch request a couple of pages ago. I’d been using the original FaderPort for the last X years, and had the foot switch set up to start recording (when the shift button was active). The foot switch, though, is something that should be configurable.

Steven

This is still CSI-based so you should be able to add the Footwswitch.

Look for the .mst file, open it in a text editor, and first check to see if the Footswitch is there. Search the word "footswitch" or something. If no, then...

Open up Reaper, go to the actions list, search for "CSI Toggle Show Input from Surfaces".

Run that.

Now, press the footswitch. You should see a message appear in a ReaConsole window. Shouold be something like (first one might be press, the second one might be release - note: the messages you see may be different):

90 66 7F 
90 66 00

If you get that far, you just need to create a new Footswitch widget in the .mst file. Let's say the messages you saw, looked exactly like the ones in the example above. In that case, you'd add this to the bottom of your .mst file...

Widget Footswitch1
  Press 90 66 7F 90 66 00
WidgetEnd

Save that. You've just added the footswitch. Now just open the buttons.zon in a text editor and assign Footswitch1 to whatever you'd like. Example:

    Footswitch1 Record

Save that. Now run the action "Control surface: Refresh all surfaces" or restart reaper.

That should be it.

[grinder]

Steveo 58
Your firmware update?
I looked up Presonus and could not find this version.

"So, I managed to update the firmware - an exciting process. Thanks to Nick at PreSonus tech support, I learned that I have to use an old version (3.64) of the Universal Controller to update the firmware,"

Can you please point me in the right direction for this?

Stevo70 (Grinder)

[stevo58]

Grinder:

Go to support - Driver downloads - select your OS, then click the “Show/hide all software versions …” below the OS drop-down


‘58’ is birth year, so I’m either five years behind, or twelve years ahead of you.

[grinder]

Many thanks stevo58!
Ha Haa 70 years young.....
Still have a job can not fit everything in every day, I am not bored.

Grinder

[stevo58]

@Funkybot:

Thanks for the help. I found the hex sequence (using CSI toggle show raw input from surfaces”). The problem I have is there is no buttons.zon anywhere on my disk. I added an FP8_buttons.zon in the appropriate location (the FP8 zone files are installed in two locations, so I added at both) but there was no effect. I guess I will have to wade through the CSI documentation, unless someone can give me a tip. I confess that, after forty years of IT, it’s gotten very difficult for me to wade through documentation, but I want this bloody foot switch to work.

[dadada]

Currently if I navigate track selection using the Faderport in "Bank" mode using the Next Prev keys my Reaper TCP remains unchanged. Is there a setting which would make the TCP follow the Faderport? So if I navigated on the Faderport so that my first track on it is "Guitar", the first visible track in my TCP would be "Guitar" as well?

[dadada]

And another question:

Is there a way to keep any fader from moving?
Sometimes when recording, I'd like to toggle off the fader movements of Faderport so I don't hear the moving faders.


Currently I unplug the USB cable, when done I plug it back in and this does not require a reaper restart. But I hope there is a more elegant way?

I thought there might be a reasonus action to enable/disable the port but it seems there is not. Any ideas how I could do this?
If there is no way, maybe I suggest to add such an action? Toggle "recording mode" where no fader moves...

[airon]

You could write your own zone for that. It takes a little study to know how they work.

One way to achieve this is to create a copy of FP8_Channel.zon and name it something like FP8_Channel_nofader.zon .

Then change one of the shortcuts in FP8_Navigators.zon or add your own to activate your new zone at will.

What shortcut that is is up to you.


FP8_Channel.zon contains what the faders do is defined for normal track operations. Your modified version FP8_Channel_nofader.zon will contain your changed behaviour.

Modify the zone file. Instead of

  Shift+Fader|        TrackPan
  Fader|              TrackVolume
  FaderTouch+Fader|   TrackVolume
  FaderTouch|         TrackTouch

you could put in

  Shift+Fader|        NoAction
  Fader|              NoAction
  FaderTouch+Fader|   NoAction
  FaderTouch|         NoAction

That way the Faders won't do a thing, but the displays will still work. Just reactivate the normal Channel zone with the Channel button to reactivate them.

[dadada]

Amazing- thanks so much for those details, I’ll try this approach for sure!

[dadada]

@airon do you happen to know if there is any way for me to customize something in Reasonus so that I get longer tracknames?

A) Make the type slightly smaller
and/or:

B) get two rows of text for tracknames, even if that means making track number and especially panning info substantially smaller. The line visualisation of pan position would be all I need, I'd love get right of the big <C> if that gets me longer filenames.

Is there a template for the display information I can potentially customize?

Thank a ton!