Old 03-15-2019, 10:28 AM   #1
bapu
Human being with feelings
 
bapu's Avatar
 
Join Date: Mar 2009
Posts: 23
Default Faderport 16 - works in Reaper?

Anyone actually using it?

No 'speculations' please, I would like to hear from actual owners letting me know it works in Reaper as well as the classic Faderport.

FYI: I am using a Faderport classic right now.

EDIT: I have had the FP16 for jus about a year now
__________________
My Regards,
My grandsons call me Bapu. You can call me that or Ed.
I'm all about the Am bass note.

Last edited by bapu; 05-03-2020 at 06:01 PM. Reason: bought an use the FP16
bapu is offline   Reply With Quote
Old 03-17-2019, 02:27 PM   #2
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,784
Default

Using the FP16 in Mackie mode with the vanilla Reaper MCU driver.

I only use the faders for volume and the knob on pan.

Double press of select buttons clears track selection and selects that track. Single press of select buttons adds to track selection.

That‘s it. The automation buttons work.... iirc. I use other stuff to control that though. Play, Rec, Stop is fine too.

The CSI project will make this controller even more useful, but it‘s not locked down on basic syntax yet.

Good faders. Good buttons. Good calbration setup. Check the manual for details.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16CSI
"My ego comes pre-shrunk" - Randy Thom

Last edited by airon; 03-17-2019 at 02:47 PM.
airon is online now   Reply With Quote
Old 04-26-2019, 11:49 AM   #3
bapu
Human being with feelings
 
bapu's Avatar
 
Join Date: Mar 2009
Posts: 23
Default

So far no go.

I'm the latest version of Reaper.

Of course I've chose the MCU setup in the FP16. There are 3, one for LOgic, Cubase and Sonar. I chose SONAR.

Nothing works in Reaper or Cakewalk by BandLab (aka SONAR).

It of course works in Harrison Mixbus and Studio One Pro 4.
__________________
My Regards,
My grandsons call me Bapu. You can call me that or Ed.
I'm all about the Am bass note.
bapu is offline   Reply With Quote
Old 04-26-2019, 12:45 PM   #4
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Faderport 16 works just fine for me using MCU controller and Logic setup. I have a few customisation actions setup for some buttons but mainly just use the volume controls, click and repeat buttons and pan pots.

You need to set up two controllers...FP16 for the in/out midi ports for controller 1 and MIDI2FP16 for the second controller. You might need to add an offset of 8 on the 2nd driver.

I actually have the FP8 and 16 set up at the same time using 24 faders in total.
__________________
inertia is offline   Reply With Quote
Old 04-26-2019, 12:54 PM   #5
bapu
Human being with feelings
 
bapu's Avatar
 
Join Date: Mar 2009
Posts: 23
Default

Quote:
Originally Posted by inertia View Post
Faderport 16 works just fine for me using MCU controller and Logic setup. I have a few customisation actions setup for some buttons but mainly just use the volume controls, click and repeat buttons and pan pots.

You need to set up two controllers...FP16 for the in/out midi ports for controller 1 and MIDI2FP16 for the second controller. You might need to add an offset of 8 on the 2nd driver.

I actually have the FP8 and 16 set up at the same time using 24 faders in total.
That did it. It works now. And I got it working in all my DAWs now (Reaper, Cakewalk by BandLab, StudioOne 4 and Mixbus 32C).

Just need to remember to switch modes when I switch DAWs.
__________________
My Regards,
My grandsons call me Bapu. You can call me that or Ed.
I'm all about the Am bass note.
bapu is offline   Reply With Quote
Old 04-26-2019, 01:35 PM   #6
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by bapu View Post
That did it. It works now. And I got it working in all my DAWs now (Reaper, Cakewalk by BandLab, StudioOne 4 and Mixbus 32C).

Just need to remember to switch modes when I switch DAWs.
I am going to start working on an MCU specific Faderport 16 driver that will hopefully get some of the other buttons and scroll stuff working a bit better, as well as send track colours to each channel.
__________________
inertia is offline   Reply With Quote
Old 04-27-2019, 12:54 PM   #7
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,784
Default

If you need a tester, I use the FP16 every day.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16CSI
"My ego comes pre-shrunk" - Randy Thom
airon is online now   Reply With Quote
Old 04-30-2019, 04:22 AM   #8
tpulse
Human being with feelings
 
tpulse's Avatar
 
Join Date: Aug 2009
Posts: 272
Default

Ehat exactly can you do with FP8 on reaper ? . How inegrated is Reaper with Faderport8 and if possible how can i add my custom commands on the "control surfare", i mean i would want to
show mixer, toggle fx monitor on off, metronome etc
tpulse is offline   Reply With Quote
Old 04-30-2019, 07:07 AM   #9
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

I suppose for such stuff to be decently working you would need "CSI" (see the appropriate thread around here).

-Michael

Last edited by mschnell; 05-01-2019 at 05:33 AM.
mschnell is online now   Reply With Quote
Old 05-01-2019, 12:35 AM   #10
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by tpulse View Post
Ehat exactly can you do with FP8 on reaper ? . How inegrated is Reaper with Faderport8 and if possible how can i add my custom commands on the "control surfare", i mean i would want to
show mixer, toggle fx monitor on off, metronome etc
Fader, pan pots, metronome, automation, arm, mute , solo, repeat all work out of the box.

You can add MIDI triggers to the action list to customise some button presses.

It really needs a native mode controller like Harrison Mixbus has for it to be fully featured. I think Mixbus nearly covers everything with a few problems here and there while MCU mode in Reaper seems to be around 60% coverage.

The CSI isn't good enough yet to drive the FP8/16 effectively.
__________________
inertia is offline   Reply With Quote
Old 05-01-2019, 05:35 AM   #11
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

Quote:
Originally Posted by inertia View Post
The CSI isn't good enough yet to drive the FP8/16 effectively.
While CSI is still in Alpha, it's not "handy" to be set up, but what do you mean by "drive the FP8/16 effectively" ?

-Michael
mschnell is online now   Reply With Quote
Old 05-02-2019, 10:28 AM   #12
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,784
Default

The whole CSI syntax is yet to be locked down. It's promising to a high degree.


A better MCU driver would definitely give us one more easy, out of the box, working option. The experience gained can be later put in to an equivalent CSI setup, as soon as CSI can accomodate that. It would give a lot of people who do want to use CSI a good starting point.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16CSI
"My ego comes pre-shrunk" - Randy Thom
airon is online now   Reply With Quote
Old 05-02-2019, 11:26 AM   #13
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by mschnell View Post
While CSI is still in Alpha, it's not "handy" to be set up, but what do you mean by "drive the FP8/16 effectively" ?

-Michael
I mean it doesn't work properly with the Faderport and still doesn't send anything to display like track names, volume, pan information. I managed to get the volume sliders to work but then it started behaving erratically. The unit isn't recognised in native mode with the CSI (when i tried it) and has to be run in MCU mode which has its own limitations.

I am not slating the project at all but there's no point recommending it to frustrated users who are not satisfied with the MCU protocol. Like you said, it's in alpha.

I am moving my mixes to Harrison Mixbus because it supports the FP16 in native mode and is pretty much fully featured.

Presonus won't make a dedicated Reaper MCU mode like they have Logic, Sonar and Cubase and the Logic mode with the latest firmware is actually worse thatn the 1.10 firmware and standard MCU mode they offered. Presonus claim Reaper are developing a native driver but its the first I have heard about it. Hopefully, they don't mean CSI.
__________________
inertia is offline   Reply With Quote
Old 05-13-2019, 09:30 AM   #14
kingriot
Human being with feelings
 
Join Date: May 2019
Location: London
Posts: 4
Exclamation Faderport 16 NOT working with latest reaper - Presonus transcript

Hi all,
unfortunately I can't get the Faderpot to respond as it should in Reaper (latest version updated May 12th 2019) - I have reached out to Presonus a number of times and even they have given up.

Here below the full transcript - Hopefully this will keep Reaper users from purchasing the unit for now..It's an unfortunate situation as we I can't really tell when and if Reaper/Presonus will allow for such integration and while I adore the faderport as a hardware unit I just can't experience the same workflow I have in Reaper in Studio One - Reaper is, to me, a much more well thought daw and it sort of feels like even though the Faderport is allegedly a MUI universal controller (aka no problem with Reaper on paper) customer will be forced to eventually transition to Studio One... Stuck between a Rock and a hard place!

p bonanno Thursday at 00:37
How do I set up my Faderport 16 with Reaper?

Avatar Technical Support Thursday at 16:27
Hello Bonanno,

To use your FaderPort within Reaper you'll first need to ensure the FP is set to MCU mode.
Power off the FaderPort
Hold the first and second "Select" buttons on the FP
Power the unit back on
Once the unit has powered up and displays "Select Control Mode" across the top of the scribble strips you can release the Select buttons
Select "MCU"
Press the eighth "Select" button ("EXIT" will be displayed on the scribble strip above this Select button)
You are now in MCU mode on your FaderPort and will remain in MCU mode even if you power the device off. To change to a different mode execute the steps listed above but select a different mode (such as HUI or Studio One mode).



Step 2 - Configure a Control Surface within Reapers Preferences
Open Reaper
Click the "Options" drop down menu and select "Preferences
Click on "Control Surfaces" within the Preferences menu
Click "Add"
Select "Mackie Control Universal" as Control Surface mode
Select "PreSonus FP" as your MIDI input and MIDI output

p bonanno Friday at 00:04
Hi, I just tried the above with my new Faderport 16 and it did not work
Also, "exit" was on my 7th select button, not the 8th

Technical Support Friday at 17:08
Hello p,

Please send me your computer's System Info file.

*NOTE: If you own PreSonus hardware, you will need to have your PreSonus hardware attached to the computer by USB or FireWire and powered on when you do this.


p bonanno Friday at 17:41
Hi Nick,
thanks for your prompt response, much appreciated.
FYI my equipment list is:
Reaper 5.977
Focusrite Clarett 8Prex
and the new Faderport 16 obviously

PC has Win 10 and it's a dell G5 i7

not sure whether you needed these info but just in case
Please find in attachment the file

Best Wishes

Pete

Cheers

Technical Support Friday at 20:22
Hello P,

Thank you for getting back with us.

The NFO file shows your Faderport shows as connected and installed.

Have you tried different USB ports?


Id also like you to test the unit within Studio One, its Native DAW.
This will determine any Hardware Failure.


Let me know if you have any questions.



Nick Maggio
PreSonus Technical Support Rep

p bonanno Friday at 20:28
Hi Nick,
i have just tried and it does indeed connect to studio one and responds as it should

i guess the unit is absolutely fine then... the problem is still with reaper then

what would you advice as next step?

Avatar Technical Support Today at 14:54
Hello P,

Thank you for getting back with us,

At this point we would recommend reaching out to the Manufacturer of the DAW in question.
Reaper support for the Faderport is conducted within their Forums.
https://forum.cockos.com/showthread.php?t=170036
There may be some more information within those forums.
Please let me know if you have any more technical issues?

Best,

Nick Maggio
PreSonus Technical Support Rep
kingriot is offline   Reply With Quote
Old 05-14-2019, 03:34 AM   #15
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,784
Default

Here's what I did just a few days back. I've been using the Faderport16 for mixing for months now. I'm using Windows 7 x64.
  • Hold down BOTH the SELECT buttons of the two left-most channels while switching on the unit. This is just to check you have the proper mode selected, which is

  • Logic MCU mode. There are several variants of MCU mode, and that one worked for me.

    You select that by choosing MCU first, then a submenu appears and you pick Logic MCU. Then if necessary, select the Restart button.

  • Start up Reaper, bring up the preferences / Midi Devices

  • Two midi devices are presented by the Faderport16 in the input section.
    PreSonus FP16 and MIDIIN2 (PreSonus FP16)
    For both, make sure they are not configured for control and input. When you're using control surface plugins, you have to keep those two flags clear.

    The same applies to the two output devices in the output section on this page.
    PreSonus FP16 and MIDIOUT2 (PreSonus FP16)
  • Now go to the preference section Control/OSC/web.

  • Click the Add button

  • Select Mackie Control Universal from the dropdown menu

  • For MIDI input select the first device presented by the Faderport 16
    PreSonus FP16
  • For MIDI Output select the device with the same name.
    Keep the surface offset at 0, size tweak at 9. Those are the defaults. The three checkboxes can stay cleared.

    Click ok to close. That's the first.

  • Click the Add button again.
    This time select Mackie Control Extender.

  • The MIDI devices this time are
    MIDIIN2 (PreSonus FP 16) for MIDI input
    MIDIOUT2 (PreSonus FP 16)
    for MIDI output
  • The Surface offset (tracks) should be set to 8. Size tweak 9, checkboxes cleared.

  • Click ok and have fun.



Hope this helps.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16CSI
"My ego comes pre-shrunk" - Randy Thom

Last edited by airon; 05-14-2019 at 03:39 AM.
airon is online now   Reply With Quote
Old 05-14-2019, 11:26 AM   #16
kingriot
Human being with feelings
 
Join Date: May 2019
Location: London
Posts: 4
Exclamation Faderport 16 NOT working with latest reaper - Presonus transcript (Follow Up)

Quote:
Originally Posted by airon View Post
Here's what I did just a few days back. I've been using the Faderport16 for mixing for months now. I'm using Windows 7 x64.
  • Hold down BOTH the SELECT buttons of the two left-most channels while switching on the unit. This is just to check you have the proper mode selected, which is

  • Logic MCU mode. There are several variants of MCU mode, and that one worked for me.

    You select that by choosing MCU first, then a submenu appears and you pick Logic MCU. Then if necessary, select the Restart button.

  • Start up Reaper, bring up the preferences / Midi Devices

  • Two midi devices are presented by the Faderport16 in the input section.
    PreSonus FP16 and MIDIIN2 (PreSonus FP16)
    For both, make sure they are not configured for control and input. When you're using control surface plugins, you have to keep those two flags clear.

    The same applies to the two output devices in the output section on this page.
    PreSonus FP16 and MIDIOUT2 (PreSonus FP16)
  • Now go to the preference section Control/OSC/web.

  • Click the Add button

  • Select Mackie Control Universal from the dropdown menu

  • For MIDI input select the first device presented by the Faderport 16
    PreSonus FP16
  • For MIDI Output select the device with the same name.
    Keep the surface offset at 0, size tweak at 9. Those are the defaults. The three checkboxes can stay cleared.

    Click ok to close. That's the first.

  • Click the Add button again.
    This time select Mackie Control Extender.

  • The MIDI devices this time are
    MIDIIN2 (PreSonus FP 16) for MIDI input
    MIDIOUT2 (PreSonus FP 16)
    for MIDI output
  • The Surface offset (tracks) should be set to 8. Size tweak 9, checkboxes cleared.

  • Click ok and have fun.



Hope this helps.
Hello mate,
thank you so much for the prompt response tremendously appreciated.
I shall be getting back in the studio tomorrow and will let you know how it goes.
Just to make sure i understood correctly...
by "Two midi devices are presented by the Faderport16 in the input section.
PreSonus FP16 and MIDIIN2 (PreSonus FP16)
For both, make sure they are not configured for control and input. When you're using control surface plugins, you have to keep those two flags clear.

The same applies to the two output devices in the output section on this page.
PreSonus FP16 and MIDIOUT2 (PreSonus FP16)"

do you mean leave those options disabled?

Thank you and have a nice evening

BEst Wishes

Pete
kingriot is offline   Reply With Quote
Old 05-16-2019, 03:40 AM   #17
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Unfortunately, the FP16 on Reaper in Logic MCU leaves much to be desired.

The FP8 with older firmware works much better when it just had a stock MCU mode and not MCU variants. I cannot see anyway to downgrade the FP16 to this firmware though.

The FP16 still works but there's many things that are incorrectly mapped.

We really need a proper "Studio One mode" driver to fully utilise the Faderport correctly. Harrison Mixbus works amazingly well with the Faderport in Native mode. Ardour has source code available for the Faderport 8 that might be a good starting point for a Reaper conversion.
__________________
inertia is offline   Reply With Quote
Old 05-16-2019, 04:31 AM   #18
kingriot
Human being with feelings
 
Join Date: May 2019
Location: London
Posts: 4
Default

Quote:
Originally Posted by inertia View Post
Unfortunately, the FP16 on Reaper in Logic MCU leaves much to be desired.

The FP8 with older firmware works much better when it just had a stock MCU mode and not MCU variants. I cannot see anyway to downgrade the FP16 to this firmware though.

The FP16 still works but there's many things that are incorrectly mapped.

We really need a proper "Studio One mode" driver to fully utilise the Faderport correctly. Harrison Mixbus works amazingly well with the Faderport in Native mode. Ardour has source code available for the Faderport 8 that might be a good starting point for a Reaper conversion.
Hello both, I just executed the procedure and whilst I got some things to work I'd have to agree with Inertia... only time will tell I guess! I still believe the faderport 16 has some of the best layouts out there for a daw controller - we need a brave programmer to sort us out!
kingriot is offline   Reply With Quote
Old 05-16-2019, 06:44 AM   #19
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

Quote:
Originally Posted by kingriot View Post
we need a brave programmer to sort us out!
Supposedly no need for "programming". Appropriate configuration files for CSI should do the trick.

-Michael
mschnell is online now   Reply With Quote
Old 05-16-2019, 10:51 AM   #20
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by mschnell View Post
Supposedly no need for "programming". Appropriate configuration files for CSI should do the trick.

-Michael
The CSI is alpha software and doesn't work with this yet and isn't even fully featured.

I tried the latest build again today and I can't even get the FP initalised correctly. I get midi sounds when moving the faders lol. Also, it doesn't retain the surface or zone settings when I g back into the config editor.
__________________

Last edited by inertia; 05-16-2019 at 11:33 AM.
inertia is offline   Reply With Quote
Old 05-16-2019, 11:48 AM   #21
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,090
Default

Quote:
Originally Posted by inertia View Post
I am going to start working on an MCU specific Faderport 16 driver that will hopefully get some of the other buttons and scroll stuff working a bit better, as well as send track colours to each channel.
If you need any help getting started, let me know.
__________________
Beta software https://stash.reaper.fm/v/38349/CSI%20beta.zip Donate GeoffWaddington.ca
Installation / documentation / source https://github.com/GeoffAWaddington/...ntegrator/wiki
Geoff Waddington is offline   Reply With Quote
Old 05-16-2019, 12:15 PM   #22
airon
Human being with feelings
 
airon's Avatar
 
Join Date: Aug 2006
Location: Berlin
Posts: 10,784
Default

Quote:
Originally Posted by kingriot View Post
Hello mate,
thank you so much for the prompt response tremendously appreciated.
I shall be getting back in the studio tomorrow and will let you know how it goes.
Just to make sure i understood correctly...
by "Two midi devices are presented by the Faderport16 in the input section.
PreSonus FP16 and MIDIIN2 (PreSonus FP16)
For both, make sure they are not configured for control and input. When you're using control surface plugins, you have to keep those two flags clear.

The same applies to the two output devices in the output section on this page.
PreSonus FP16 and MIDIOUT2 (PreSonus FP16)"

do you mean leave those options disabled?

That's right. If any of those two options are ON, you can't use it with a control surface plugin.
__________________
Dialogue/FX Editor & Re-Recording Mixer
(Video)Using Latch Preview - Faderport16CSI
"My ego comes pre-shrunk" - Randy Thom
airon is online now   Reply With Quote
Old 05-16-2019, 12:54 PM   #23
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

Quote:
Originally Posted by inertia View Post
The CSI ... doesn't work with this yet and isn't even fully featured.
This supposedly is untrue.

But it's true that in the current state there is no decent documentation for CSI, and hence you might not be able to get it running for you without additional help from the forum.

-Michael
mschnell is online now   Reply With Quote
Old 07-11-2019, 02:49 PM   #24
fredmatthew25
Human being with feelings
 
fredmatthew25's Avatar
 
Join Date: Apr 2013
Location: Tampa, Florida
Posts: 26
Default

For me, the Classic faderport - thank you Kenny Goia for the tip, is hit or miss.
fredmatthew25 is offline   Reply With Quote
Old 07-11-2019, 10:32 PM   #25
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by mschnell View Post
This supposedly is untrue.

But it's true that in the current state there is no decent documentation for CSI, and hence you might not be able to get it running for you without additional help from the forum.

-Michael
I've tested it many times and it's not suitable for use with the Faderport. Scribbles don't work and the units lose connectivity if Reaper loses focus. The basic transport buttons are working and the faders but not much else. It also needs to be used in MCU mode, so no improved functionality there over the other drivers.

I've actually gone over to Studio One 4 and Mixbus for my mixes now.
__________________

Last edited by inertia; 07-11-2019 at 10:42 PM.
inertia is offline   Reply With Quote
Old 08-03-2019, 05:16 PM   #26
CloseToTheEdge
Human being with feelings
 
CloseToTheEdge's Avatar
 
Join Date: Jul 2006
Location: Close to the edge, down by a river
Posts: 212
Default

Where might I find the most compatible settings for Reaper and Faderport 16?

It was working a few months ago, but now it positions the faders at -10 instead of unity. I'm using MCU/Logic as the setup with Mac Mojave 10.14.5.

Thanks!
__________________
óRegistered REAPER user

Last edited by CloseToTheEdge; 08-05-2019 at 10:21 AM.
CloseToTheEdge is offline   Reply With Quote
Old 08-14-2019, 06:26 AM   #27
Grandude1
Human being with feelings
 
Join Date: May 2019
Posts: 1
Default My work around.

It would be nice to have CSI working but until that day comes I've been using Klinke v0.6.4.1 and the Faderport 16 in mcu mode Sonar. I can do pretty much what I need to do. It's not without some quirks but it is quite usable for me. I would love to see the Faderport 16 in native mode become more accepted across the board with all the DAW makers.
Grandude1 is offline   Reply With Quote
Old 12-10-2019, 10:27 AM   #28
BorsingPhoto
Human being with feelings
 
BorsingPhoto's Avatar
 
Join Date: Jun 2012
Location: Fayetteville, TN
Posts: 164
Smile

[QUOTE=bapu;2108298]Anyone actually using it?

I use FaderPort 16.. All 16 Faders works.. 2 Mackie Control Universal, 1st Surface offset (tracks) =0 / Size tweak =8..

2nd Surface offset (tracks) =8 / Size tweak =9..

Just works
__________________
BorsingStudios.com represents aspiring new talents on a budget by offering studio time/on-line marketing support in the true "spirit of Cockos".
BorsingPhoto is offline   Reply With Quote
Old 05-03-2020, 04:41 PM   #29
mickmacneil
Human being with feelings
 
Join Date: May 2016
Posts: 2
Default

Quote:
Originally Posted by bapu View Post
Anyone actually using it?

No 'speculations' please, I would like to hear from actual owners letting me know it works in Reaper as well as the classic Faderport.

FYI: I am using a Faderport classic right now.
Yes, it works, but could be better. Cant see track names on first 8 channels
mickmacneil is offline   Reply With Quote
Old 05-03-2020, 05:59 PM   #30
bapu
Human being with feelings
 
bapu's Avatar
 
Join Date: Mar 2009
Posts: 23
Default

Quote:
Originally Posted by mickmacneil View Post
Yes, it works, but could be better. Cant see track names on first 8 channels
Been using it now for just about a year.
__________________
My Regards,
My grandsons call me Bapu. You can call me that or Ed.
I'm all about the Am bass note.
bapu is offline   Reply With Quote
Old 06-12-2020, 11:50 AM   #31
siniarch
Human being with feelings
 
Join Date: Jun 2018
Posts: 195
Default

Quote:
Originally Posted by inertia View Post
I've tested it many times and it's not suitable for use with the Faderport. Scribbles don't work and the units lose connectivity if Reaper loses focus. The basic transport buttons are working and the faders but not much else. It also needs to be used in MCU mode, so no improved functionality there over the other drivers.

I've actually gone over to Studio One 4 and Mixbus for my mixes now.
Please, please take the following statement with the best intentions and what I truly want is for people to realize the powerful abilities of CSI and how it can help everyone in the future. Tone is very hard to convey over text and I'm hoping the following doesn't come off as an attack and more as spreading of information.

But I purchased a QCon Pro G2 unit and initially it didn't work. I tried Klinke, and PoweredByMoss (both of which are great and very kind of the developers to share btw), until I found CSI which is way more configurable. I tried using the pre-made files from the QCon Pro X which should be similar. Initially didn't work at all and later found out that some files were missing. Once I got those files, it worked better. But really what I had to do was to dissect what the Pro X configuration files were doing, and re-build a configuration file for the Pro G2 unit. I basically have every single button working on the my G2 unit and many I've customized to exactly what I want. I'm still tweaking it, but compared to the lack of support and functionality from the manufacturer's protocols, this is night and day.

So, you may be right in that CSI might not work out of the box currently, but that is because someone hasn't taken the time to create files that will utilize all it's options (scribbles, buttons, faders, etc..) The CSI project allows you to map any Midi Surface to commands in Reaper, but it doesn't have every controlled configured. The guys making it are great people, Geoff is incredible and spending lots of his time working on it. (not selling it btw. Just giving it to people to use) but he doesn't have every controller out there. Therefore, it's up to the users who want to integrate their own controller to map it and provide that mapping so others that need it can get a starting point and then configure to their liking from there.

Unless I'm missing something and the fader port 16 doesn't give access to the scribbles or something similar, it should work with CSI. But someone has to make the initial time and effort investment in order to do that. If you would like to do that yourself, I'll be happy to help with my limited knowledge of it. But we can get on the phone or skype and show you what I did for my controller.

But to say that CSI doesn't work with FaderPort is inaccurate and it may prevent others from taking the time to configure it. Which in essence will prevent any people in the future from ever using the FaderPort 16 with reaper. Because they read it wasn't possible. (again, unless I'm missing something with the faderport being somehow restrictive to access some of it's functions. but I doubt it)

So perhaps it's better to state it as, The CSI project doesn't have a currently pre-mapped configuration file for the FaderPort 16 and I either don't have the time to figure it our or the desire to. But if someone does, please let me know and I'll give it a try.

Geoff or anyone at the CSI project that thinks I've misspoken, please feel free to correct me and I'll update my message. Perhaps I'm not aware of a faderport limitation you guys are.
siniarch is offline   Reply With Quote
Old 06-12-2020, 12:49 PM   #32
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

Unfortunately ReaPack does not yet have a Category for CSI config files.Otherwise, those that do exist would be easy to find for everybody.

-Michael
mschnell is online now   Reply With Quote
Old 06-13-2020, 11:37 PM   #33
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by siniarch View Post
Please, please take the following statement with the best intentions and what I truly want is for people to realize the powerful abilities of CSI and how it can help everyone in the future. Tone is very hard to convey over text and I'm hoping the following doesn't come off as an attack and more as spreading of information.

But I purchased a QCon Pro G2 unit and initially it didn't work. I tried Klinke, and PoweredByMoss (both of which are great and very kind of the developers to share btw), until I found CSI which is way more configurable. I tried using the pre-made files from the QCon Pro X which should be similar. Initially didn't work at all and later found out that some files were missing. Once I got those files, it worked better. But really what I had to do was to dissect what the Pro X configuration files were doing, and re-build a configuration file for the Pro G2 unit. I basically have every single button working on the my G2 unit and many I've customized to exactly what I want. I'm still tweaking it, but compared to the lack of support and functionality from the manufacturer's protocols, this is night and day.

So, you may be right in that CSI might not work out of the box currently, but that is because someone hasn't taken the time to create files that will utilize all it's options (scribbles, buttons, faders, etc..) The CSI project allows you to map any Midi Surface to commands in Reaper, but it doesn't have every controlled configured. The guys making it are great people, Geoff is incredible and spending lots of his time working on it. (not selling it btw. Just giving it to people to use) but he doesn't have every controller out there. Therefore, it's up to the users who want to integrate their own controller to map it and provide that mapping so others that need it can get a starting point and then configure to their liking from there.

Unless I'm missing something and the fader port 16 doesn't give access to the scribbles or something similar, it should work with CSI. But someone has to make the initial time and effort investment in order to do that. If you would like to do that yourself, I'll be happy to help with my limited knowledge of it. But we can get on the phone or skype and show you what I did for my controller.

But to say that CSI doesn't work with FaderPort is inaccurate and it may prevent others from taking the time to configure it. Which in essence will prevent any people in the future from ever using the FaderPort 16 with reaper. Because they read it wasn't possible. (again, unless I'm missing something with the faderport being somehow restrictive to access some of it's functions. but I doubt it)

So perhaps it's better to state it as, The CSI project doesn't have a currently pre-mapped configuration file for the FaderPort 16 and I either don't have the time to figure it our or the desire to. But if someone does, please let me know and I'll give it a try.

Geoff or anyone at the CSI project that thinks I've misspoken, please feel free to correct me and I'll update my message. Perhaps I'm not aware of a faderport limitation you guys are.
The post I wrote was now a while ago (like 7 months ) and a lot has happened since then.
I actually presented Geoff with the scribble code for the FP16 for the CSI and the CSI is now better supporting the FP16 and a lot of progressions have been made since the time of writing my initial post. There is one forum user who has spent a lot of time getting fundamentals working but there's still a lot of hiccups to iron out. I am still hopeful that the CSI will be the ultimate driver for this surface in the future but still thing that target is someway off.

I stand by the comment I made at the time because, at the time, the CSI was not working well with the FP16 and there were too many bugs to make it useful. Disconnecting and not reconnecting when Reaper lost focus was a show stopper for me. I have had some brief dialogue with Geoff and by his own admission he encouraged me to continue working on my own driver to get the best out of the Faderport.

I have my own native driver for the FP16 but have decided not to release this in its current form just yet because I don't have the time to finish it to a standard that the community would find useful as it is built to satisfy my mixing needs and primarily was written to get most things working like it would in S1 and fix the problems that are present when using it in one of the several MCU modes the unit can be switched to.

I would be happy to upload the code to a public repo if anyone wants to pick up from where I am at.
__________________
inertia is offline   Reply With Quote
Old 06-14-2020, 03:24 AM   #34
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

Quote:
Originally Posted by inertia View Post
I would be happy to upload the code to a public repo if anyone wants to pick up from where I am at.
For the benefit of all of us, please do talk to Geoff and CFillion about using GuitHub / ReaPack !
Thanks,
Michael
mschnell is online now   Reply With Quote
Old 06-14-2020, 01:08 PM   #35
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by mschnell View Post
For the benefit of all of us, please do talk to Geoff and CFillion about using GuitHub / ReaPack !
Thanks,
Michael
The code is already at Github, it's just set to private right now.
__________________
inertia is offline   Reply With Quote
Old 06-14-2020, 02:29 PM   #36
Pompeysie
Human being with feelings
 
Join Date: Aug 2019
Location: UK
Posts: 60
Default Faderport V2

Do any of you have any tips for a new FP V2 owner?

Managed to get some of the functionality working with Reaperís new support but scroll/zoom doesnít work and a few other buttons. I have started playing with CSI BUT I think Iím finding the same issue mentioned here re. the limitations with the units MCU versions.

Iím sure we can crack this (he says, hopefully)

Simon
Pompeysie is offline   Reply With Quote
Old 06-14-2020, 02:32 PM   #37
mschnell
Human being with feelings
 
mschnell's Avatar
 
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 9,521
Default

Quote:
Originally Posted by inertia View Post
The code is already at Github, it's just set to private right now.
OK so it would be easy to publish it with ReaPack.... if ReaPack would be enabled to support CSI config files.
-Michael
mschnell is online now   Reply With Quote
Old 06-15-2020, 08:28 AM   #38
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by mschnell View Post
OK so it would be easy to publish it with ReaPack.... if ReaPack would be enabled to support CSI config files.
-Michael
I am not the one to talk to about the CSI config. My driver is written in C++, it has nothing to do with CSI.
__________________
inertia is offline   Reply With Quote
Old 06-15-2020, 05:11 PM   #39
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,090
Default

Quote:
Originally Posted by inertia View Post
I am not the one to talk to about the CSI config. My driver is written in C++, it has nothing to do with CSI.
Hey @inertia, thanks again for that code snippet for the scribble strips, worked a charm

Just to avoid confusion, CSI is also coded in C++ in case anyone thought different.
__________________
Beta software https://stash.reaper.fm/v/38349/CSI%20beta.zip Donate GeoffWaddington.ca
Installation / documentation / source https://github.com/GeoffAWaddington/...ntegrator/wiki
Geoff Waddington is offline   Reply With Quote
Old 06-16-2020, 10:43 AM   #40
inertia
Human being with feelings
 
Join Date: Oct 2013
Posts: 695
Default

Quote:
Originally Posted by Geoff Waddington View Post
Hey @inertia, thanks again for that code snippet for the scribble strips, worked a charm

Just to avoid confusion, CSI is also coded in C++ in case anyone thought different.
I just wanted to distinguish between writing config files for CSI and uploading them to Github and a compiled controller. I didn't mean to insinuate you were writing yours in Borland Pascal or something similar
__________________
inertia is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 03:04 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, vBulletin Solutions Inc.