Oh yea, which firmware version? And if you decide to update it, check above because 1.3.5 breaks stuff...
Quote:
For issues with faderport firmware (such as 1.3.5 known to have issues):
-> Remove faderport from reaper.
-> Confirm the firmware number: If its not 1.3.8 go to the following link.
See link for version 1.3.8 http://support.presonus.com/entries/...fader-solution
-> Delete reaper_csurf.dll and keep the XT dll instead.
-> Reboot, add everything back as FaderPortXT
Be careful though, their firmware makes me nervous.
__________________ Music is what feelings sound like.
Best time thus far, slow time at work, contractors begging for stuff to do, official move is Monday but I'm trying to get the studio and electronics rooms moved before then. As I told the wife, I sleep whereever the gear and Internet connection is and I'm cutting it over Friday @ 8:00AM
__________________ Music is what feelings sound like.
Just to clear some things up, here, some lights [usually Output] stay on when I quit Reaper, too. But I sort of got used to that. Sometimes it turns off all the lights properly. However, Reaper initialises the Faderport properly and that's far more important.
To add to this, I used the Faderport with Cubase 5 and its Faderport driver on a couple of occasions and some of the lights also stay on when I quit Cubase, so it must be Presonus' problem. But let's be completely honest - it's just a "cosmetic bug". I'm also using 1.38 firmware.
Happy holidays everyone! Don't get drunk *too less*! It's bad for health.
p.s. very busy holidays here, too. But today I just had to say "enough! :/". Today and next two days I'm just going to carouse and do nothing else. Damn!
__________________
Goodnight, thank you, and may your God go with you.
To add to this, I used the Faderport with Cubase 5 and its Faderport driver on a couple of occasions and some of the lights also stay on when I quit Cubase, so it must be Presonus' problem. But let's be completely honest - it's just a "cosmetic bug". I'm also using 1.38 firmware.
Thanks for chiming in DuX! That (concerning the light)makes what I see make more sense. The more I think about it I want to think that way back when you and I were troubleshooting this I eventually found an occurrence on my Faderport but there was no rhyme or reason to it, I just happened to notice it was on but had closed Reaper maybe an hour before. Never been able to repro and it being firmware related certainly adds up to what we've seen.
__________________ Music is what feelings sound like.
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.
Hey there, forum newbie here. I'm wondering if there is a way to have the pan pot scroll tracks while still having the output button allow the fader to control the pan for the selected track.
Hey there, forum newbie here. I'm wondering if there is a way to have the pan pot scroll tracks while still having the output button allow the fader to control the pan for the selected track.
Thanks!
I don't think I added that. I want to think if PAN_SCROLLS_TRACKS=1 it is kind of global. Whenever I get settled down from moving I'll look. It's one of those things where I have to pull it up and dive in for a couple days. However, if it does work it would be by using the following settings but fair warning it may not:
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.
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.
Yea, seems to be a problem with certain units. You see it, JHughes sees it but I for some reason don't see it. I heard the same about replacing the pot.
__________________ Music is what feelings sound like.
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.
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.
Yeah that's what is in my ini file. When I try to open the mixer it just flashes on for a second and disappears
Yeah that's what is in my ini file. When I try to open the mixer it just flashes on for a second and disappears
Try running the action from within Reaper only since that's all Faderport does is run that action. In other words you should be able to test and confirm minus Faderports participation.
__________________ Music is what feelings sound like.
Window View Buttons doesn´t work with Faderport XT
Hey Karbo,
thanks for that great job, but the Window View Buttons (Mix, Proj, Trns) doesn´t work.
Can you help or take a look at your config?!
In Cubase everything works fine!
thanks for that great job, but the Window View Buttons (Mix, Proj, Trns) doesn´t work.
Can you help or take a look at your config?!
In Cubase everything works fine!
Thanks and greets
Marek
See the first post since in Reaper you can make those buttons do whatever you wish but you have to add the corresponding actions to the ini file.
__________________ Music is what feelings sound like.
The Ini is correct, but nothing happens. It´s the same behaviour like other people already told in this chat.
As I asked the other poster who didn't reply back... Run the same action from within Reaper and not with the faderport button to make sure it works properly minus Faderport. I know it works, I'm sitting here doing it right now and they work as expected with the actions and the buttons.
__________________ Music is what feelings sound like.
Sorry man, if you mean the action list by that?! Yes, that´s works fine for every command!
Then something else is wrong, see screen cap above showing it working with 4.77 and make sure you followed the instructions exactly including deleting the default reaper csurf.dll. If transport works but other buttons do not, it is usually because that wasn't properly deleted; aka it is being used and XT isn't actually loaded.
__________________ Music is what feelings sound like.
That sounds very much like the action is running twice (because the action toggles). I can't reproduce that behavior though.
You might try assigning that same action to some other buttons as a test in the event the newer Faderports made some change I am unaware of. What firmware are you running?
You might also try testing some actions that don't use a toggle behavior just to narrow things down.
What if you depress Mix and don't let up?
__________________ Music is what feelings sound like.
Saw you mention working on automation lanes controllable from the Faderport
I was wondering if you made any progress with the GetSelectedTrackEnvelope()
That would make this already awesome mod even better!
Does this only work if you are running on Windows?
I see that .dll files only seem to refer to Windows.
I'm running Reaper 4.77 on OS X 10.8.5, just got my Faderport today and don't have any issues - works perfectly, but the Window View buttons seem to be redundant. Found this script on the Stash and this thread.
Is there a work around? I'm fairly new to Reaper and haven't fully explored the tinkering aspects of it beyond the SWS add-on.
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
Linear Mode
