Updated Faderport Support (Faderport XT - Alpha) - Page 7

mucknog · 08-18-2015, 06:46 AM

Wow, that was fast

I already tried, but there is no effect.
Other actions which have ID numbers like 40605 work just fine.

Any suggestions?

karbomusic · 08-18-2015, 06:53 AM

Quote:

Originally Posted by mucknog

Wow, that was fast

I already tried, but there is no effect.
Other actions which have ID numbers like 40605 work just fine.

Any suggestions?

Hmm... when I tested before posting it appeared to work fine and the action showed up in the undo list. SWS etc. have lots of constants for their ID so you might try a few obvious ones to confirm. I'll check to later when I have a chance.

karbomusic · 08-18-2015, 07:00 AM

Actually it doesn't seem to work, not sure why I've never noticed. If I can fix I will but not sure where these constants are stored and whether I have access to them.

As a workaround you may be able to create a custom action, that calls the action you care about, then call your custom action using the ID that gets auto created.

mucknog · 08-18-2015, 07:06 AM

Quote:

Originally Posted by karbomusic

Actually it doesn't seem to work, not sure why I've never noticed. If I can fix I will but not sure where these constants are stored and whether I have access to them.

As a workaround you may be able to create a custom action, that calls the action you care about, then call your custom action using the ID that gets auto created.

Thanks for your help, would be awesome if you could fix it.
I already tried the workaround. Problem is, if you put an action with non-number ID in a custom action. The new custom action has a non-number ID, too. So this won't work.

karbomusic · 08-18-2015, 07:12 AM

Quote:

Originally Posted by mucknog

Thanks for your help, would be awesome if you could fix it.
I already tried the workaround. Problem is, if you put an action with non-number ID in a custom action. The new custom action has a non-number ID, too. So this won't work.

To be fair, I just noticed my Faderport isn't working at all with XT, meaning I've changed something while doing unrelated stuff that makes my above tests invalid. I'll have to fix that and retest because I'm nearly 100% sure I had custom actions and/or SWS working just fine. I don't think they are treated as numbers or the non-number IDs should work in Reaper even without the Faderport but maybe that's not the case.

mucknog · 08-18-2015, 07:54 AM

Quote:

Originally Posted by karbomusic

To be fair, I just noticed my Faderport isn't working at all with XT, meaning I've changed something while doing unrelated stuff that makes my above tests invalid. I'll have to fix that and retest because I'm nearly 100% sure I had custom actions and/or SWS working just fine. I don't think they are treated as numbers or the non-number IDs should work in Reaper even without the Faderport but maybe that's not the case.

That's too bad. Have you tested in Reaper 5?
It seems that there have been changes in action IDs.
One custom action I made, and that worked with XT, had a number ID (55230) in Reaper 4.x
Now its ID is "_524757577013754386097bc08923d477" and it doesn't work.

karbomusic · 08-18-2015, 08:02 AM

Quote:

Originally Posted by mucknog

That's too bad. Have you tested in Reaper 5?
It seems that there have been changes in action IDs.
One custom action I made, and that worked with XT, had a number ID (55230) in Reaper 4.x
Now its ID is "_524757577013754386097bc08923d477" and it doesn't work.

Reaper 5 was where I tested this morning. I'll check whenever I get a chance to pull up the code.

karbomusic · 08-18-2015, 11:29 AM

I'm going to have to dig deeper and/or see if I can get a response from the dev team and/or another user here who does similar extension programming. From the faderport code I have to use SendMessage()/WM_COMMAND() to send actionID from the INI file back to Reaper which runs the corresponding action. SendMessage can't take strings AFAIK.

This made me wonder how custom actions could work in Reaper at all however... although a custom action gets a GUID type string, in reality that is backed by the action IDs of all the actions the custom action stands for so it would just send the underlying valid IDs.

I'll poke around some but in the meantime anyone who has the answer, don't be afraid to chime in.

This could be my lack of reading the documentation but at the moment, I have no idea how to get the number value that goes with custom action guids if there is such a mapping and I think I need those in order to call them from the extension but could be missing something obvious here.

mucknog · 08-18-2015, 09:36 PM

Thanks karbo!

Just to be certain, that this isn't only true for me.
Have all your custom & SWS command IDs changed, since v5, too?

For example:
Custom action IDs now look like -> _33dd5baf86ada447995c5828483eb4a0
SWS action IDs like -> _S&M_ALLIN_FX_LEARN_CHp

I'm not 100% certain, but this seems to be true since Reaper version 5.

Greetz

karbomusic · 08-18-2015, 10:05 PM

Quote:

Originally Posted by mucknog

Thanks karbo!

Have all your custom & SWS command IDs changed, since v5, too?

My V4 action IDs have the same pattern, integers, GUIDS and constants. However, I have some faint memory of some ID's changing but don't quote me.

karbomusic · 08-18-2015, 10:10 PM

I just found the problem that you may have already mentioned. In V4 there is a Cmd ID and a Custom ID. In V5 the Cmd ID is now Command ID and has the guids and integers combined. There appears to be no way to get the underlying Cmd ID; will see if it is discoverable.

karbomusic · 08-18-2015, 10:32 PM

I can't believe there isn't an easier way to get these (maybe I've been away too long). I had to run an action that dumps them but it didn't dump the custom IDs, just the SWS stuff.

The action SWS/S&M: dump action... (there are two of them SWS and non-SWS) which will save them as a file. However, it only appeared to save what was in the filtered action list so I had to filter to find it, select it, then clear the filter and run the action to dump. Once I did that it created the file below but since I don't know what matches and what doesn't you may have to run it on your machine.

http://www.wallsonic.com/public/posts/Main_SWS.txt

Hopefully you can access ^that. Let me know if you can make that work or your own export of IDs work. I really wish Cockos could add a single action that just dumps every action in Reaper to the clipboard. If one already exists other than the above, I'm overlooking it.

mucknog · 08-19-2015, 08:08 AM

Karbo, you are awesome!

First I tired to use your dump. But those IDs are linked to completely different actions in my Reaper version.

I did my own export, and it all works splendid now, SWS and Custom all fine.

It's too bad there's not a tab in the action viewer for the Cmd IDs.
Well, I'm not complaining, your solution works.

Thanks a lot!

karbomusic · 08-19-2015, 08:31 AM

Sweet!

Quote:

It's too bad there's not a tab in the action viewer for the Cmd IDs.

My exact thoughts... FYI that we are trying to find out if there is a better way...

http://forum.cockos.com/showthread.php?t=165221

mucknog · 08-22-2015, 10:21 PM

Hi Karbo,

I got one question / request...

I think the option to scroll tracks with the pan knob is really useful and quick.
The "Output" button is already customizable, would it be possible to make all "Channel Select" buttons be customizable, too.
I mostly never use Bank+Left/Right, especially when selecting tracks with the pan knob.
It would be genius if you could e.g. pan left/middle/right with those buttons.

Is this possible, and would you take the time to implement?

Cheers & thanks again

Jeronimo · 08-26-2015, 08:20 PM

So, this is not possible to be ported for Macs?
We had luck with the Alphatrack plugin being ported from Win to Mac. I guess this one is different...

stinky634 · 10-16-2015, 10:51 AM

I've used this awesome tool for a while now. I did run into a snag that is probably unrelated at all to the XT version of Faderport, but I figured this would be the place to find the answer since you all know what you are doing:

After a fresh PC install after some hardware upgrades, everything is working perfectly except I cannot get the motorized fader to work. I wouldn't mind because it still functions and everything, but if I select a channel in reaper that lets say is at -20 db, but the fadrport is at 0 db, and I happen to bump my desk or cause any sort of accidental movement on the FP, it will jump that channel in reaper. Sometimes it even bgs out where it'll stick to wherever the FP is set at.

I don't quite remember all the steps th first tme I installed FPXT, so I dont remember if I had this issue before or not, but can't seem to find an answer. FP is plugged into power and works flawlessly otherwise.

Edit: Next time I should read the included instructions from Presonus. I was installing drivers through a 3.0 USB port, plus probably shouldn't have been using an external hub as well. Installed through a 2.0 port and without the Hub. Works perfect even back through the Hub and 3.0 port.

TLsound · 10-23-2015, 06:48 AM

Hey Karbo,

I've been reading a lot about about your upgrade on the forum and since I recently bought a FaderPort, I would love to use the extra features with it.

But I'm still confused if there is really no way to get this working on a Mac?

Thanks for the hard work!

cheers Thierry

karbomusic · 10-23-2015, 06:55 AM

Quote:

Originally Posted by stinky634

Edit: Next time I should read the included instructions from Presonus. I was installing drivers through a 3.0 USB port, plus probably shouldn't have been using an external hub as well. Installed through a 2.0 port and without the Hub. Works perfect even back through the Hub and 3.0 port.

Thanks for the update and glad you got it working!

Quote:

Originally Posted by TLsound

But I'm still confused if there is really no way to get this working on a Mac?

Thanks for the hard work!

cheers Thierry

I'm sure it would probably work, I just don't have the Mac knowledge or compiler environment to try.

Jeronimo · 10-23-2015, 12:04 PM

In this Alphatrack thread there are people able to port this plugin. They did for the Alphatrack.

I just don't remember exactly who that was, but almost sure the OP was part of it.
http://forum.cockos.com/showthread.php?t=81889

karbomusic · 10-23-2015, 12:35 PM

Quote:

Originally Posted by Jeronimo

In this Alphatrack thread there are people able to port this plugin. They did for the Alphatrack.

I just don't remember exactly who that was, but almost sure the OP was part of it.
http://forum.cockos.com/showthread.php?t=81889

Thanks, I'm familiar with RuairiAU's thread/work, good stuff. However, the salient point is that I don't have a Mac or Mac compile environment to even start compiling for Mac. I'm happy to share the code with anyone who demonstrates the resources and ability to do so though but it's been a few years now though and no takers who have returned to the thread with results.

EDIT: I suppose the most ideal resolution would be for me to go back and clean all the code up and ask if the devs will include this into the product for default faderport support but I have no idea if that is possible since I took over someone else's work and also have no idea of cocko's internal design standards and way of doing things. My hunch is that Justin could have a few laughs at my code then massage it to get it official in a couple of hours. However, that brings further development to a halt or we just end up with yet another XT version which would be far too confusing for users.

G-Sun · 11-01-2015, 03:06 AM

In Studio One Faderport is integrated so we can assign the motorized fader to most parameters.

Like here:

This is very handy, when anything else than vol/pan needs a hand on.

Is it possible to get this sort of integration in Reaper as well?

(btw: I'm very thankful for the current implementation of Fadrerport

)

G-Sun · 11-12-2015, 03:41 AM

I have problem with fader-movements not being recorded properly.
When I go into touch, it only sets trim-level.

When I started on a clean project, everything seems fine,
writing vol-env as it should.

Edit: My bad.
Vol env. arm was not checked.

The_Nimaj · 12-03-2015, 06:21 PM

Quote:

Originally Posted by karbomusic

However, the salient point is that I don't have a Mac or Mac compile environment to even start compiling for Mac.

I'd be happy to give it a go. I'm fairly new to Reaper and the SDK but I've been dabbling with modifying the current faderport driver. The least I could do is try and get your code to compile.

karbomusic · 12-03-2015, 08:14 PM

Quote:

Originally Posted by The_Nimaj

I'd be happy to give it a go. I'm fairly new to Reaper and the SDK but I've been dabbling with modifying the current faderport driver. The least I could do is try and get your code to compile.

I think you'd have to address the reading of the INI file first thing. I'm guessing you'd need a directive that tells the compiler to use the Mac or Windows code based on the OS the compiler is running on.

Otherwise, can you access a repository such as TFS or GitHub? If you are serious about making it work, it would be nice to be able to check it back in to a branch to keep things in sync. Not sure if I can make that work with my current setup but would be nice if so. In the meantime, PM me and I'll get you a copy for now as zip.

Let me know

micwalt · 12-30-2015, 04:19 PM

Hey there,
Longtime Reaper user here--love it!
Just got a Faderport, but I'm on a Mac--so no footswitch. Bummer!
Just wondering if anyone's figured anything out for Macs.
Everything else seems to work great, but I'd really love the footswitch option for guitar punches.
Thanks!

karbomusic · 12-30-2015, 04:22 PM

Quote:

Originally Posted by micwalt

Just wondering if anyone's figured anything out for Macs.

YES!

http://forum.cockos.com/showthread.php?t=170036

I updated the first post in this thread to reflect this so enjoy.

achase4u · 01-01-2016, 06:27 PM

Just stopping in to say thanks for the great driver here. I got my Faderport a few days ago and love it, but needed more functionality and this gives it. Many thanks. A real fader is SOOO much nicer if you ask me.

DutchDoctor · 02-09-2016, 10:35 PM

Thank you for all your hard work! I will be sure to donate. I purchased my faderport today also.

----

So current behaviour lets me select any track with my mouse, and the faderport will snap to either fader position, or volume/pan automation. I also want to be able to select ANY automation lane and have the fader snap to control/read that.

This should be standard functionality imho, it would make for such a fast and intuitive workflow.

Click any track, or automation lane, control the parameter. Easy.

I know I can map any button on this thing to any Reaper action ID using this XT config, but I can't seem to control what the fader controls, or what feeds the motorised feedback.

Any thoughts?

The_Nimaj · 02-19-2016, 05:34 AM

Quote:

Originally Posted by DutchDoctor

Thank you for all your hard work! I will be sure to donate. I purchased my faderport today also.

----

So current behaviour lets me select any track with my mouse, and the faderport will snap to either fader position, or volume/pan automation. I also want to be able to select ANY automation lane and have the fader snap to control/read that.

This should be standard functionality imho, it would make for such a fast and intuitive workflow.

Click any track, or automation lane, control the parameter. Easy.

I know I can map any button on this thing to any Reaper action ID using this XT config, but I can't seem to control what the fader controls, or what feeds the motorised feedback.

Any thoughts?

Hi,

Please visit this http://forum.cockos.com/showthread.php?t=170036 thread, download the version from there and make any feature requests/ bug reports there as well.

Boogaloo · 03-02-2016, 02:23 PM

My FP seems to be behaving fine in all respects, though I'm not sure what the default behaviour is for selecting its 'focus' regarding touching other controls and not selecting channels.

For instance, if I scroll to select (or mouse select) a channel so it's highlighted, the FP updates to the right fader levels. If I move off with the pan/scroll or mouse to another channel, all good.

However, if I touch (not even move) a pan control on another channel, that doesn't highlight that channel, but my FP behaves as if it had and will then control that channel. Is this normal?

Does this have any bearing on something I'm trying to do, which is use the Output (or Mix) button to launch the FX chain for the selected channel?

ACTION_OUTPUT=40291

This seems to work, so long as I mouse select, or scroll select *and then* touch the fader for the channel on my FP (or click on a panpot). If I just pan/scroll to a select a new channel, hitting Output only shows the last channels' FX chain.

It's piddling, but it gets confusing when I'm expecting my highlighted channel to be in focus and I'm off changing another fader, and the show FX chain for selected channel would be soooo helpful.

Win7/64, back to old firmware from the Presonus support link (the update broke me).

Fantastic work mate, much appreciated.

karbomusic · 03-02-2016, 02:26 PM

Quote:

Originally Posted by Boogaloo

My FP seems to be behaving fine in all respects, though....

Not sure if you saw the new thread...

http://forum.cockos.com/showthread.php?t=170036 thread

BartR · 10-30-2018, 12:08 PM

Quote:

Originally Posted by karbomusic

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.

http://forum.cockos.com/showthread.php?t=170036

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:

MIX, PROJ, TRNS, PUNCH, USER, LOOP, FOOTSWTICH, SHIFT+FOOTSWITCH
SHIFT+MIX, SHIFT+PROJ, SHIFT+TRNS, SHIFT+PUNCH, SHIFT+USER, SHIFT+LOOP

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.

DOWNLOAD: FaderPortXT.zip

The footswitch is totally ignored.
Is it occur to you as well?

karbomusic · 10-30-2018, 12:45 PM

Quote:

Originally Posted by BartR

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?

Ben Zero · 12-20-2018, 07:32 PM

Hey guys

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 :|

Big thanks

Ben

karbomusic · 12-20-2018, 07:38 PM

Sent you a PM.

Ben Zero · 12-20-2018, 08:12 PM

Thanks karbo.

No luck so far downgrading the firmware, unfortunately. The updater stalled/crashed fairly quickly... it just hangs after a few seconds and stays there.

I wonder if downgrading is actually possible? Anyone know if there's a way?

Cheers

Ben

karbomusic · 12-20-2018, 08:15 PM

Quote:

Originally Posted by Ben Zero

Thanks karbo.

No luck so far downgrading the firmware, unfortunately. The updater stalled/crashed fairly quickly... it just hangs after a few seconds and stays there.

I wonder if downgrading is actually possible? Anyone know if there's a way?

Cheers

Ben

I'm surprised it crashed actually, never seen that before. Have you tried repowering and reconnecting the FP to the computer so it's completely reinitialized and completely reconnected? Just curious if there is some communication failure over USB - also make sure Reaper isn't running obviously.

However, I can't be sure the issue you are having is due to the driver you have now, the main issue I remember with 1.3.5 was the fader would jiggle around and not work and 1.3.8 fixed it (maybe other issues I don't remember though). Also which FPXT driver did you download from these threads? Mine is pretty old but the latest is here: https://forum.cockos.com/showthread.php?t=170036

Ben Zero · 12-20-2018, 08:24 PM

I think I'm following the right procedure but I'll definitely try again.

Just to check, the file is very small and the updater says it'll download the new firmware. So I'm guessing that's the problem - it's not downloading from anywhere!?

I'm using the standard REAPER driver at the moment but I know that should work with following track selection, as I have a mate doing the same thing. Earlier in this thread I read that firmware does seem to be the issue here (I planned to explore the custom Faderport REAPER drivers once I'd first got it all working properly in its default way).

karbomusic · 12-20-2018, 08:35 PM

Quote:

Originally Posted by Ben Zero

I think I'm following the right procedure but I'll definitely try again.

Just to check, the file is very small and the updater says it'll download the new firmware. So I'm guessing that's the problem - it's not downloading from anywhere!?

Good observation but I think download means "to" the faderport from the computer. Did you literally see "download" and if so can you screen shot that?

Quote:

I'm using the standard REAPER driver at the moment but I know that should work with following track selection, as I have a mate doing the same thing.

Just tested, that's correct.

Quote:

Earlier in this thread I read that firmware does seem to be the issue here (I planned to explore the custom Faderport REAPER drivers once I'd first got it all working properly in its default way).

If someone else had the same issue and that fixed it then it's entirely possible. However, when I ran the installer I didn't get the impression it was downloading anything from their servers - but I couldn't run the last step because I didn't want to actually reflash mine - hence my wondering where the term download appeared. Also for firmware, 1.2 MB is on the large side, the actual driver is likely small and the rest is the installer bits.