EDIT 12/30/15: If you are on Mac and/or want a few new features which I have not added for either OS, please see the following thread where The_Nimaj has added both Mac/PC support and some of the additional features asked for in this thread. I see no reason not to consider his current build the latest and greatest.
Now if we could just talk Cockos into moving this into the product officially it would save all these special instructions. wink, hint, nudge.
------------------------
Based on yhertogh's previous additions (thanks!) I have added additional Reaper support for Faderport. Here are all the features including what yhertogh already had... Ability to assign custom actions to the following buttons:
If you create your own custom actions which is a chain of other actions you can run complicated macros with a button etc.
Other features
Auto Scroll, Shift Latch, MCP View, Select Last Touched. See this thread for more information.
Installation
1. Copy reaper_csurf_fpxt.dll and reaper_csurf_fpxt.ini to \Reaper\Plugins and delete the existing reaper_csurf.dll.
2. In reaper go to Options > Preferences > Control Surfaces
3. Highlight and remove the existing PreSonus FaderPort Control Surface in the list (if you already had Faderport installed previously).
4. Click Add and choose "Presonus FaderPort XT" from the list. If this exact choice isn't in the list, make sure the dll is in the \reaper\plugins directory and Reaper has been restarted!
5. Choose FaderPort for both the MIDI Input and MIDI Output and click OK twice.
6. The XT version of FaderPort is now ready to use.
Customization
All customizations are in the INI file (reaper_csurf_fpxt.ini) here are the defaults but the entire point is that you can make them do what works best for you:
==============================================
MCP_VIEW=1 (default=1, enabled, Autoscroll works)
SHIFT_LATCH=1 (default=1, enabled, shift latch works)
AUTO_SCROLL=1 (default=0 disabled, if you press next channel on faderport it may fall onto a hidden track)
SELECT_IS_TOUCHED=1 (default=1 enabled, when creating a new track, make the new track also the 'last touched track')
ACTION_PUNCH=40222 (set start point)
ACTION_PUNCH_SHIFT=40172 (Go to previous marker/project start)
ACTION_USER=40157 (insert marker at current position)
ACTION_USER_SHIFT=40173 (Go to next marker/project end)
ACTION_LOOP=1068 (toggle repeat)
ACTION_LOOP_SHIFT=40915 (set end point)
ACTION_FOOTSWITCH=40073 (play/pause) ACTION_FOOTSWITCH_SHIFT=1013(record)
ACTION_MIX=40078 (toggle mixer visible)
ACTION_MIX_SHIFT=41077 (toggle show all floating windows except mixer)
ACTION_PROJECT=40861 (go to next project tab - cycle)
ACTION_PROJECT_SHIFT=40295 (zoom out project)
ACTION_TRANS=40259 (toggle transport visible)
ACTION_TRANS_SHIFT=1134 (tap tempo)
==============================================
To customize just grab the action ID you need from reaper and change it in the INI file for the button you wish to customize. If the action IDs are not visible in the actions list in Reaper, be sure to right-click anywhere in the actions window and choose "Show action IDs". Find your action, its corresponding ID, change it in the ini file, save it, restart Reaper.
5.10.13: This is no longer considered alpha/beta and all links in this thread point to the release version
For now it can be downloaded below. Both x86 and x64 versions are included in the same .zip file. Be sure that you extract the correct 32bit/64bit version that matches your version of Reaper. I'll check back and fix whatever is busted tomorrow evening.
I can't test it out until this weekend, but... FOOTSWITCH SUPPORT!
Thank you, my new best friend
In hindsight, I probably need to add shift support to the footswitch which I haven't done yet. I didn't think that was useful at first but with the ability to latch the shift button, it becomes more useful to have the footswitch perform different functions via shift such as changing to record instead of play when shift is latched. Might add that in the next day or so.
EDIT: Forget the above, I just added shift+footswitch. I also updated the first post and download accordingly.
__________________ Music is what feelings sound like.
Last edited by karbomusic; 11-09-2011 at 08:02 PM.
Currently there seems to be no way to hook up any controller to the pre-fx volume or pan envelopes. You can't flip the fader the control anything but the volume actually.
An OSC controller might be able to do it, but the Faderport isn't a general midi controller so that cannot(yet) be hooked up either.
The problem is that the pre-fx envelopes have no LEARN capability, like the normal volume, pan and mute, but at least those have midi cc/osc actions.
Might be a good request for the next v5 cycle.
Right now you're left with controlling the fader on the envelope control panel with the mouse.
Right now you're left with controlling the fader on the envelope control panel with the mouse.
I'm working on "regular" envelope access via volume fader but since none of that is in the original FaderPort code, it's taking me some time to figure it all out and do some tests. That and the fact that I'm very unfamiliar with the API so it's very slow going until I get over the initial WTF hump.
I'll be much closer once I get GetSelectedTrackEnvelope() implemented and working.
__________________ Music is what feelings sound like.
Interesting, thanks for the help. Still getting the hang of Reaper so didn't realize that wasn't possible. I work as a programmer in real life though so I'm going to start digging into the API pretty soon.
Still considering going with the FaderPort given the amount of great work you guys seem to be doing on it.
Interesting, thanks for the help. Still getting the hang of Reaper so didn't realize that wasn't possible. I work as a programmer in real life though so I'm going to start digging into the API pretty soon.
Still considering going with the FaderPort given the amount of great work you guys seem to be doing on it.
Welcome fellow dev me too, well I'm rather mostly a debugger in WinDbg as of late but I still do a fair amount of "above of the compiler" stuff here and there. I already know I'm simply not declaring the functions I need properly because their addresses in the resulting assembly call instructions are bogus. I should have it worked out before too long but not before Christmas.
__________________ Music is what feelings sound like.
Hi guys, does any one here is running fader port over win xp64 bit? i can´t find my faderport in reaper x64 over XP64, does any one have any advise? it works fine over win7 64bit, but not over xp64. cheers.
I have had issues with my Faderport (4.62 version of Reaper). This thread solved the problem. Download the link in the first post, insert the file into the Reaper / Plugins folder. Also, deleted the csurf.dll file that comes with Reaper upgrades. So, I might have to go back in and delete that file with each upgrade, but will be worth it to continue working with Faderport. Thanks guys who posted here. You are all way over my head with the programming and looking forward to trying out some of the additional functionality you have all added.
Hi guys, I'm new in the forum and happy Reaper user since a couple years... i'd like to know if someone has succesfully compiled the code/found some workaround to achieve the same results as this plugin for OSX? I searched deeply in this forum, and found nothing. I don't want to think about going back to windows after 10 years just to use this little but powerful dll...(and I'm really considering it) Thanks everyone!
Hi guys, I'm new in the forum and happy Reaper user since a couple years... i'd like to know if someone has succesfully compiled the code/found some workaround to achieve the same results as this plugin for OSX?
Unfortunately, not that I know of. I wonder, if I were to clean up the code all nice like if Justin would ever consider migrating these changes into the default csurf/faderport support. It's a longshot, but the code that others, then I added has been extremely stable for several years now. I don't think there has been a single crash to my knowledge since I first updated it in November of 2011 so we at least have a good track record.
However, I did hack some of the code in out of ignorance so it would likely require a full day of work to formally take what we have done and properly merge it assuming we had any chance whatsoever of it happening. I'm sure I added some code outside the Faderport C++ file before realizing how everything was structured and since it was mostly for me at the time, I worried less about coding it properly against the paradigm. It also isn't 100% user friendly (aka the ini file has to be edited directly).
I do think though that it vastly expands on the default support for Faderport and I personally couldn't live without it.
__________________ Music is what feelings sound like.
Last edited by karbomusic; 07-22-2014 at 07:44 PM.
Thanks Karbo for taking time to reply, great to hear directly from you. You definitely did an AMAZING job for the community. Thank you.
Still, I think many Osx users are using the Faderport with the limited default functionality...so I totally agree with you, it would be AMAZING if Justin could add your code to the default Faderport support. It truly would be a GIANT improvement for a lot of people (including me).
What do you think we can do as a community to make this happen?
I bought a faderport just recently to use with reaper.. worked ok, but was expecting more.. then I found this thread, and now it works great.. thanks mister karbo.
this morning I did an upgrade for the firmware of the faderport, had not done that yet. the motorized fader stopped working after that. I had to roll back to and older firmware to get it working again.. this has nothing to do with reaper or the faderportxt . just wanted to tell for people having the same problem.
Based on yhertogh's previous additions (thanks!) I have added additional Reaper support for Faderport. Here are all the features including what yhertogh already had...
Thanks a lot!
When selecting "output" pan is controlled from the fader. Is this intended?
Ok, I see:
Quote:
Added support for disabling Output button flip mode (vol/pan) and assigning custom actions instead.
Assign custom actions to both Output and Shift+Output.
Default behavior is flip.
That's how Output works for me. Boy, panning with the slider or knob is so much better than with a mouse. I wish the pan knob worked better though. It's jerky and when it's working it only does 2 dB increments although that seems to be endemic to the unit.
I've read you can replace the pot to fix the jerkiness.
I wish there were a way to implement fine control, perhaps by toggling shift.
I added code, configurable via faderport ini file, to make the output button and pan knob more worthwhile since by default it flips PAN/VOL between knob/fader:
Output Button
ACTION_OUTPUT
ACTION_OUTPUT_SHIFT
Both the defaults are 0 which keeps the default vol/pan flip mode behavior. Changing ACTION_OUTPUT to any value other than zero enables both Output and Shift+Output and also disables flip mode. Set it to any action ID and it will run that action. Set it to 1 or 2 to enable two special master track options. Here are some examples:
Faderport output button selects master track and deselects all other tracks. Shift+Output toggles master track visibility:
ACTION_OUTPUT=1
ACTION_OUTPUT_SHIFT=41209
Faderport output button gives faderport control of the master but does not deselect other tracks. Shift+Output toggles stereo/mono on the master track:
ACTION_OUTPUT=2
ACTION_OUTPUT_SHIFT=40917
Faderport output button displays the FXChain for the master track, Shift+Output toggles FX bypass for the master track.
ACTION_OUTPUT=40846
ACTION_OUTPUT_SHIFT=16
* Note that ACTION_OUTPUT=0, ACTION_OUTPUT=1 and ACTION_OUTPUT=2 are special values. All other values other than 0, 1, or 2 should be an action ID.
Pan Knob
PAN_SCROLLS_TRACKS
PAN_SCROLLS_TRACKS=0 (Default) Faderport behavior of pan L/R
PAN_SCROLLS_TRACKS=1 Pan knob scrolls back and forth through tracks.
As you can see above there is a lot of hidden goodness depending on what you want and is all configurable in the ini file (see first post for info, I'll back port subsequent feature additions back to the first post soon). Don't forget that the 8 buttons just above the transport are configurable to an action ID you wish. For example on mine "Mix" toggles the mixer, "Trns" toggles the transport and so on.
Quote:
Boy, panning with the slider or knob is so much better than with a mouse. I wish the pan knob worked better though. It's jerky and when it's working it only does 2 dB increments although that seems to be endemic to the unit.
I've read you can replace the pot to fix the jerkiness.
I wish there were a way to implement fine control, perhaps by toggling shift.
Also, FYI on my setup pan is very smooth but it is 2 percentage points not dB?
__________________ Music is what feelings sound like.
Last edited by karbomusic; 01-07-2015 at 02:52 PM.
Karbomusic you are a lifesaver.
Just got a Fader port, using a 64bit PC w/Windows 8
Cldn't get it to work. Installed your patches & it's working like a charm. Can't thank you enough
Best,
Cam
Quote:
Originally Posted by karbomusic
Based on yhertogh's previous additions (thanks!) I have added additional Reaper support for Faderport. Here are all the features including what yhertogh already had... Ability to assign custom actions to the following buttons:
If you create your own custom actions which is a chain of other actions you can run complicated macros with a button etc.
Other features
Auto Scroll, Shift Latch, MCP View, Select Last Touched. See this thread for more information.
Installation
1. Copy reaper_csurf_fpxt.dll and reaper_csurf_fpxt.ini to \Reaper\Plugins and delete the existing reaper_csurf.dll.
2. In reaper go to Options > Preferences > Control Surfaces
3. Highlight and remove the existing PreSonus FaderPort Control Surface in the list (if you already had Faderport installed previously).
4. Click Add and choose "Presonus FaderPort XT" from the list. If this exact choice isn't in the list, make sure the dll is in the \reaper\plugins directory and Reaper has been restarted!
5. Choose FaderPort for both the MIDI Input and MIDI Output and click OK twice.
6. The XT version of FaderPort is now ready to use.
Customization
All customizations are in the INI file (reaper_csurf_fpxt.ini) here are the defaults but the entire point is that you can make them do what works best for you:
==============================================
MCP_VIEW=1 (default=1, enabled, Autoscroll works)
SHIFT_LATCH=1 (default=1, enabled, shift latch works)
AUTO_SCROLL=1 (default=0 disabled, if you press next channel on faderport it may fall onto a hidden track)
SELECT_IS_TOUCHED=1 (default=1 enabled, when creating a new track, make the new track also the 'last touched track')
ACTION_PUNCH=40222 (set start point)
ACTION_PUNCH_SHIFT=40172 (Go to previous marker/project start)
ACTION_USER=40157 (insert marker at current position)
ACTION_USER_SHIFT=40173 (Go to next marker/project end)
ACTION_LOOP=1068 (toggle repeat)
ACTION_LOOP_SHIFT=40915 (set end point)
ACTION_FOOTSWITCH=40073 (play/pause) ACTION_FOOTSWITCH_SHIFT=1013(record)
ACTION_MIX=40078 (toggle mixer visible)
ACTION_MIX_SHIFT=41077 (toggle show all floating windows except mixer)
ACTION_PROJECT=40861 (go to next project tab - cycle)
ACTION_PROJECT_SHIFT=40295 (zoom out project)
ACTION_TRANS=40259 (toggle transport visible)
ACTION_TRANS_SHIFT=1134 (tap tempo)
==============================================
To customize just grab the action ID you need from reaper and change it in the INI file for the button you wish to customize. If the action IDs are not visible in the actions list in Reaper, be sure to right-click anywhere in the actions window and choose "Show action IDs". Find your action, its corresponding ID, change it in the ini file, save it, restart Reaper.
5.10.13: This is no longer considered alpha/beta and all links in this thread point to the release version
For now it can be downloaded below. Both x86 and x64 versions are included in the same .zip file. Be sure that you extract the correct 32bit/64bit version that matches your version of Reaper. I'll check back and fix whatever is busted tomorrow evening.
There also seems to be an issue where the mix button can only close the mixer and won't open it. Is this a known issue?
Thanks!
I must say it works as "advertised" here with WinXP x86 and Reaper 4.75 x86. Also, my pan knob works pretty much flawlessly, too. Only sometimes it skips a bit. That's a known "feature" I'm afraid. I read somewhere that replacing the pan potentiometer with a more quality one works, but I never bothered replacing it.
__________________
Goodnight, thank you, and may your God go with you.
There also seems to be an issue where the mix button can only close the mixer and won't open it. Is this a known issue?
Thanks!
Shouldn't be but I'll check. Do you have this entry in the ini file?
ACTION_MIX=40078
40078 = "toggle mixer visible" so make sure that action ID matches the action ID in Reaper, I expect it should but I'd double check. You could also test that action directly in Reaper and make sure it works since all FaderportXT does is call that action ID.
__________________ Music is what feelings sound like.
This is fantastic. I'm late to the party but thanks for doing this.
I had a trouble getting the Faderport up and running. I know it's an older piece of kit and I just got it today. I had to install the firmware from an older computer because my current one uses USB 3.0 and it wouldn't work.
Is there a way to set the pan knob as jog wheel for scrubbing through a track?
I just bought the Faderport a few days ago and I'm really glad I found this thread. Also I second - using the knob as a jog wheel would be fantastic.
Thanks for your work!
With the recent release of REAPER 5, are there any additions or changes in functionality for a device such as this? I've been considering buying one of these for a while, but once I had read that there's no way to write FX parameter automation (right...?), I hesitated.
Are there any other controllers similar to this? I've heard of the Faderport, and the... I want to say, Alphaport? Discontinued, I read.
Hope you're all enjoying the new release!
Cheers
EDIT 12/30/15: If you are on Mac and/or want a few new features which I have not added for either OS, please see the following thread where The_Nimaj has added both Mac/PC support and some of the additional features asked for in this thread. I see no reason not to consider his current build the latest and greatest.
Now if we could just talk Cockos into moving this into the product officially it would save all these special instructions. wink, hint, nudge.
------------------------
Based on yhertogh's previous additions (thanks!) I have added additional Reaper support for Faderport. Here are all the features including what yhertogh already had... Ability to assign custom actions to the following buttons:
If you create your own custom actions which is a chain of other actions you can run complicated macros with a button etc.
Other features
Auto Scroll, Shift Latch, MCP View, Select Last Touched. See this thread for more information.
Installation
1. Copy reaper_csurf_fpxt.dll and reaper_csurf_fpxt.ini to \Reaper\Plugins and delete the existing reaper_csurf.dll.
2. In reaper go to Options > Preferences > Control Surfaces
3. Highlight and remove the existing PreSonus FaderPort Control Surface in the list (if you already had Faderport installed previously).
4. Click Add and choose "Presonus FaderPort XT" from the list. If this exact choice isn't in the list, make sure the dll is in the \reaper\plugins directory and Reaper has been restarted!
5. Choose FaderPort for both the MIDI Input and MIDI Output and click OK twice.
6. The XT version of FaderPort is now ready to use.
Customization
All customizations are in the INI file (reaper_csurf_fpxt.ini) here are the defaults but the entire point is that you can make them do what works best for you:
==============================================
MCP_VIEW=1 (default=1, enabled, Autoscroll works)
SHIFT_LATCH=1 (default=1, enabled, shift latch works)
AUTO_SCROLL=1 (default=0 disabled, if you press next channel on faderport it may fall onto a hidden track)
SELECT_IS_TOUCHED=1 (default=1 enabled, when creating a new track, make the new track also the 'last touched track')
ACTION_PUNCH=40222 (set start point)
ACTION_PUNCH_SHIFT=40172 (Go to previous marker/project start)
ACTION_USER=40157 (insert marker at current position)
ACTION_USER_SHIFT=40173 (Go to next marker/project end)
ACTION_LOOP=1068 (toggle repeat)
ACTION_LOOP_SHIFT=40915 (set end point)
ACTION_FOOTSWITCH=40073 (play/pause) ACTION_FOOTSWITCH_SHIFT=1013(record)
ACTION_MIX=40078 (toggle mixer visible)
ACTION_MIX_SHIFT=41077 (toggle show all floating windows except mixer)
ACTION_PROJECT=40861 (go to next project tab - cycle)
ACTION_PROJECT_SHIFT=40295 (zoom out project)
ACTION_TRANS=40259 (toggle transport visible)
ACTION_TRANS_SHIFT=1134 (tap tempo)
==============================================
To customize just grab the action ID you need from reaper and change it in the INI file for the button you wish to customize. If the action IDs are not visible in the actions list in Reaper, be sure to right-click anywhere in the actions window and choose "Show action IDs". Find your action, its corresponding ID, change it in the ini file, save it, restart Reaper.
5.10.13: This is no longer considered alpha/beta and all links in this thread point to the release version
For now it can be downloaded below. Both x86 and x64 versions are included in the same .zip file. Be sure that you extract the correct 32bit/64bit version that matches your version of Reaper. I'll check back and fix whatever is busted tomorrow evening.
The footswitch is totally ignored.
Is it occur to you as well?
I never used any of the newer versions after I handed off the code, but it worked back when I had it I thought. I can test when I get a chance to confirm since I still use my original version. Are you using a standard momentary footswitch like for a keyboard?
__________________ Music is what feelings sound like.
Just finally got myself a Faderport "Classic". Really nice piece of kit and loving it so far.
Only problem is that I'm not able to get the Faderport to follow selected track in REAPER (ie I can only select tracks with the Faderport, it can't follow the track I've selected with the mouse).
Reading this thread it looks like it's a firmware thing - it seems that 1.3.8 is the "golden" firmware. I checked mine and apparently it was v1.00 (according to their Universal Control app) so I took a punt and ran the updater. It's updated to v1.45 but I've still got the same problem.
Wondering if this is definitely a firmware issue, even with the latest version? If so, does anyone know where I can find a copy of 1.3.8 to downgrade to? Can't find one anywhere online :|