Hi lads,
I bought a Presonus Faderport 16 for use within Reason. It works so far with the remote for Mackie extender (version right in my case) so
I can control "16 SSL-Faders" if I create and select a mastertrack automation within the sequencer (the scope for the devices I deleted).
Panorama selection i.e. for each track does not work so far; some Buttons has to be re-programmed via "remote-override".
A fully integrated controller would be nice but perhaps I did a bad choice?!... coloured "select" buttons conformitiy to the track color...
instinctive using of knobs and buttons....etc, that would be nice
I wrote to the support of Propellerhead nevertheless to the support of Presonus....
Presonus answer:
Technical Support April 12, 2018 22:04
Hello Christoph,
We have provided units to other DAW manufacturers to allow them to develop native implementations for the FaderPort 8 and FaderPort 16. Unfortunately this is at the discretion of the DAW manufacturer.
Currently 3rd party DAWs can utilize MCU support for functionality, however, as you are experiencing currently DAW manufacturers will implement MCU support differently and as such the functionality also changes.
We recommend contacting your DAW manufacturer if you would like to see a native implementation for the FaderPort 16.
Thank you.
Max Stratmann
Technical Support Rep
Propellerhead answer:
Hey Christoph,
Hmm not much I can do here I'm afraid. I haven't used the controller myself and I thought the Mackie Universal Control thing did the trick but seems not.
Can't say much about this I'm afraid but I'll forward your thoughts to our developers.
Best regards
Lars
Product support
Propellerhead Software
Seems I've to wait (for Years?) , but is there any LUA-Programmer, who would like to drive away the tedium itself.....
Christoph
Reason 10 and Presonus Faderport 16
-
- Posts: 13
- Joined: 28 Nov 2018
Just wanted to say a quick thank you for taking the time to create this tutorial. I (unfortunately) just placed an order for the single channel Faderport v2 to use with Propellerhead Reason 10.2, assuming it was supported. Is there any hope that I'll be able to get it running with a decent amount of functionality in tact, or should I be thinking about a return? Any advice would be kindly appreciated!
It's my opinion that Propellerhead needs to be doing this. They used to leave this to music manufacturers but as Reason wasn't particularly popular at one point, the music manufacturers stopped bothering and it was left to Reason users to make their own.
Propellerhead should budget for this and employ someone to do it. Choose some key MIDI controllers from major manufacturers and some specialised ones such as Launchpads and mixer controllers like the Faderports. PH have wasted money on projects like Drop To Propellerhead in the past. I can't imagine they'd have to spend more than €5k a year on MIDI controllers and you could outsource the actual scripting.
Propellerhead should budget for this and employ someone to do it. Choose some key MIDI controllers from major manufacturers and some specialised ones such as Launchpads and mixer controllers like the Faderports. PH have wasted money on projects like Drop To Propellerhead in the past. I can't imagine they'd have to spend more than €5k a year on MIDI controllers and you could outsource the actual scripting.
-
- Posts: 13
- Joined: 28 Nov 2018
I've only been looking into this for the past few days, but I feel like you're probably right. What I heard from Presonus, is that they provided Propellerhead with units, so all they would have to do is map it out, but Propellerhead just sat on them. I mean, the single channel Faderport is a great, well known add-on, especially for bedroom producers, which, I would guess, is the majority of Reason's userbase. I just can't figure it out. Does anyone else have any light to shed on this? The only response from PH quoted earlier in this thread doesn't sound very professional to me. More of a, "Bummer, dude. Better luck next time!"
Hi.
If all the buttons work from the top of the head, editing the MCU remote map is quite easy.
What you edit in the remote, will be kept for every project, and you won't need to reprogram via remote overdrive.
Check this tutorial on propellerheads blog:
https://www.propellerheads.com/blog/control-remote
Good Luck!
If all the buttons work from the top of the head, editing the MCU remote map is quite easy.
What you edit in the remote, will be kept for every project, and you won't need to reprogram via remote overdrive.
Check this tutorial on propellerheads blog:
https://www.propellerheads.com/blog/control-remote
Good Luck!
- jetpilot00
- Posts: 51
- Joined: 27 May 2017
Harrison has already programmed the Faderport 8 and 16 to work, almost, identically as it would in Studio One. It's quite impressive. It has come down to PH not using the manpower to create the mapping for their users. Pretty sad.
***If life is a song, I've just passed the guitar solo.***
-
- Posts: 1
- Joined: 22 Sep 2019
I've just gone ahead and purchased the Faderport 16. Has Harrison posted this his work?jetpilot00 wrote: ↑24 Jun 2019Harrison has already programmed the Faderport 8 and 16 to work, almost, identically as it would in Studio One. It's quite impressive. It has come down to PH not using the manpower to create the mapping for their users. Pretty sad.
-
- Posts: 1181
- Joined: 11 Apr 2019
Old post but AGREED. Now, my Nektar is fantastic and I wouldn't trade it for anything but I had the faderport 2018 and it was dreadful inside of Reason with the exception of simply assigning things. (which it wouldn't remember the next time I used it )
It seems as though reason Studios has not created a solution to this, because I believe the whole point of Reason Studios is to have a complete, fully functional in-software mixer, based off of the SSL 9000k analog mixing desk. This is what makes reason studios so unique.
-
- Information
-
Who is online
Users browsing this forum: No registered users and 7 guests