navelpluisje / reasonus-install Goto Github PK

installer doesn't seems to do anything when clicking install reasonus

windows X64

How to reproduce:

1. Turn on touch automation for a given track
2. Move the fader while keeping your finger on it
3. Look at Reaper mixer GUI and notice how it loses "connection" with the touched fader, as if the touch was a one shot move and not continually held.

I tested to make sure this wasn't just a problem with my hardware unit, as I went into Studio One and tried the same fader with Touch automation.

Hello.

Thank you for creating ReaSonus.

The installer does not recognize my FPv2.

Universal Control was not running while I attempted to install ReaSonus. However, when I later started Universal Control, it correctly identified my FPv2.

Please see the attached screen shots that offer details of my gear.

Thanks.

Regards,
Jim

Is your feature request related to a problem? Please describe.

I have a FaderPort8 on the desk and a V2 by my e-drums. When I use Logic, both work at the same time. It appears that Reasonus only allows one. When I run the installer, it shows:

PreSonus - PreSonus FP8 - Port 1
PreSonus - PreSonus FP2

Describe the solution you'd like

When multiple devices are present, it would be great if they both worked.

Describe alternatives you've considered

Looks like I have to run the installer again to switch devices.

Additional context
n/a

Describe the bug
On FP2, "click" button should toggle metronome on and off but it doesn't do anything

To Reproduce
Steps to reproduce the behavior:
Simply press "click" and notice that metronome doesn't come on. Long press has no effect either

Operating System

• [] Windows 11

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ... v1.0.1
• Reasonus Resources: v1.01
• CSI (ReaSonus): 1.1

Expected behavior
metronome should toggle when pressing "click" button

Additional context
Reaper version 6.82
Faderport firmware v3.74
Faderport mode : unchanged from unboxing

Encoders do not aways working proper on slow and fast turns.

Describe the bug
attempt to run FaderPort Control from within reaper

To Reproduce
Followed instructions:

1. In the menu click Actions and the Show Action List…
2. Start typing reasonus faderport and press enter
   The plugin should appear now:

Doesn't run, instead I get:

Message in dialog box:
refFunctionAction.lua:135: attempt to call a nil value (field 'CF_GetCommandText')

Operating System

• [] Windows 10

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ...
• Reasonus Resources: ...1.01
• CSI (ReaSonus): .1.1

Expected behavior
expected to run FaderPort Control

Screenshots

Additional context
Thanks so much for this great.. whatever you call it, once it's running properly It'll be brilliant! Will be shouting you a few coffees for sure.

So the left becomes right and the other way around.

• Check if creating 2 zones for the shift buttons will work
  https://forum.cockos.com/showpost.php?p=2584033&postcount=65

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Operating System

• [] Windows 10
• [] Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ...
• Reasonus Resources: ...
• CSI (ReaSonus): ...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

I love what you have done here. But there is one small feature that I can't seem to get used to not having. In older fader port setups that I have used, it would work like this. If you use your mouse and click on a track in reaper, it would not only select the track, but it would scroll your track into view on the fader port. I've used the original Faderport for a long time and using a mouse was very essential to work quickly with only one fader. With this current setup, I have to select the track with my mouse to highlight the track on my faderport8 and then I need to select bank and use the control wheel or the bank buttons to find the track I selected. Using shift+bank speeds up the process a little bit but still. So an automatic banking feature would be killer. Especially if it could be toggle on and off.

I would also like to say that you have by far the best Faderport8 setup that there is out there for reaper, and I thank you for all your diligent work!

Copied the script and all instructions and most of the faders etc map BUT it's as though everything is a toggle. ie the channel strips show a low and high of 0 and 1 for faders although there is no constraint in the fader lines of code.

Is there a line one can add to set the lower and upper bounds of the fader (to force it to have 1-100 range)?

Thanks

Describe the bug
I cannot get Faderport 16 version 3.21 Build 16209 working with Reaper 6.81 and the latest version of SW & S/M v2.12.1 #3

To Reproduce
Steps to reproduce the behavior:

1. Set Faderport to Studio One Control
2. Start Reaper: Faderport 16 scribble tabs clear, faders move to zero position: "Lights are on but no one is at home"
3. Validate: MIDI devices - Faderport 16 MIDI disabled, Faderport 16 disabled or enabled makes no difference
4. Validate: All files in CSI are correct, the .ini file is correct, and all SW & S/M actions are correct
5. No functions are functional
6. Installed the latest version of Studio One and all features work perfectly

Operating System

• Windows 11 Pro | Version: 22H2 OS | Build: 22621.2283 | Experience: Windows Feature Experience Pack 1000.22662.1000.0

Versions

• ReaSonus Installer:
• ReaSonus Resources: v1.01
• CSI (ReaSonus): 1.1 (reasonus-edition0

Expected behavior
Installed the latest version of Studio One and all features work perfectly, I expect that at least most of the features work in Reaper 6.81. No features are functional.

The ReaSonus Faderport application only displays menu items: "HOME, INSTALL, and ABOUT" It is missing the "FUNCTIONS" menu selection item.

I uninstalled the ReaSonus app, deleted all files and folders, removed all registry entries, all cache files, and Windows references to ReaSonus, rebooted numerous times, validated Reaper 6.81 OPTION settings and SW & S/M actions.

I WILL PAY REAL UNITED STATES $$$ TO SOMEONE OR TO SOMEPLACE TO GET FADERPORT 16 TO WORK ON MY COMPUTER

I need it working as soon as possible, please

Screenshots

Faderport 16 before starting Reaper 6.81:

Faderport 16 after starting Reaper 6.81:

Additional context
If this is a known problem, I will still pay for someone to contact me, and stay with me in a video screen-sharing chat or phone chat, so I can guarantee that I have a working Reaper with the Faderport 16.

Describe the bug
A clear and concise description of what the bug is.
When moving the fader in the Touch mode it produces zagged up and down sawtooth-like lines in the automation envelope.
To Reproduce
Steps to reproduce the behavior:

1. Go to 'Create a volume automation envelope...'
2. Click on 'Touch automation button on Faderport 2, start play and move fader to draw automation, then let go of fader....'
3. Scroll down to '. Not applicable...'
4. See error: The automation written will be zagged up and down sawtooth lines.

Operating System

• Windows 10
• [] Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: v1.0.1
• Reasonus Resources: ...
• CSI (ReaSonus): ...

Expected behavior
A clear and concise description of what you expected to happen.
The automation drawn in the Touch mode should be a smooth line that track the fader movement. Note: The Latch and Write mode work perfectly as they should.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

The problem exists in a clean install shipped with Reasonus. I probably confused the issue by bringing up CSI 2.0, which I did only as a way of confirming that it was happening in a clean install of Reasonus, and not as a result of me going rogue and trying to fiddle around with using Reasonus in a CSI 2.0 install.

Here's the fix, 100% guaranteed.
Wherever you have a FaderX widget,

Widget Fader1
Fader14Bit e0 7f 7f
FB_Fader14Bit e0 7f 7f
WidgetEnd

A third line has to be added as such

Widget Fader1
Fader14Bit e0 7f 7f
FB_Fader14Bit e0 7f 7f
Touch 90 68 7f 90 68 00
WidgetEnd

To be blunt: touch automation is literally broken in the version you have online right now.

Thanks again for the hard work! I've been wanting to use my Faderport in Reaper for a very long time, and until Reasonus, I didn't have that spark of inspiration to get started. I've made the switch and will not be looking back!

Updated to REAPER v6.80 and experienced a significant loss of functionality. I can no longer scrub, solo/mute tracks, change/jump between markers, select channels, select sections, arm/disarm channels, or select Channel Bus features. Rossetta causes Reaper to bug out causing clicks and pops, therefore I had to use Reaper in the normal mode. I've eliminated clicks and pops but now cannot use my Faderport 16 Controller.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade to REAPER v6.80
2. Don't use Rosetta.
3. Experience Loss of functionality.

Operating System

• Max OS: 13.4 (22F66) M1 MAX

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: Rv1.0.1

Expected behavior
Should be able to maintain controller functionality. Faders still work, and master playback/record features still function. I was really happy with the software as it made working in Reaper just amazing. Totally heartbroken right now. This software was such a godsend.

Describe the bug

When I hit the play/pause button, the playhead is moved, and that's it. Other transport controls work.

To Reproduce
Steps to reproduce the behavior:

Hit the button

Operating System

Mac OS Sonoma

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ...doesn't say
• Reasonus Resources: ...1.0.1
• CSI (ReaSonus): ...1.1

Expected behavior

I would expect the play/pause button to work just like the transport control in the reaper window.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Describe the bug
Using the latest Firmware for the Faderport 8 (3.74) and the latest Reaper Version (6.81) you have to set up the faderport as a CSI device in Reaper before installing Reasonus.
The Reasonus installer stooped with a disabled button called "install"

My first Idea to finish the installaiton was to setup the Faderport in Reaper first, maybe that's why it was not recognized by the Reasonus installer.
I tried the following:
A) Control/OSC/WEB -> Add -> Control Surface Mode: PreSonus Faderport, Midi input: PreSonus FP8, Midi output: PreSonus FP8

Result: The installation button can be clicked and the MIDI In and MIDI out is recognized by the Reasonus installer, and the done message was displayed for about 2 seconds.

=> Reaper starts but the Faderport is not working and displays the message: "waiting for host" in Studio One mode

B) I removed the previous Faderport under: Control/OSC/WEB and then -> add -> Control Surface Mode: Control Surface Integrator -> Reasonus Faderport, FaderPort 8

Result: The FaderPort awakes and displays the track names. It looks like it's working really good now.
Thanks a lot for this great tool!

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Operating System

• Windows 10

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: -
• Reasonus Resources: v1.0.1
• CSI (ReaSonus): 1.1 reasonus edition

Expected behavior
The faderport installation should work without setting up a Control/OSC/WEB device in reaper first or the installation manual should clarify this step.

Additional context
This is my first time trying the faderport
In the settings under midi devices all entries with Faderport in it are disabled for input and output

I just want to mention this to help others facing the same problem installing Reasonus.

I am wondering if this software is being worked on anymore? I had an issue close to year ago and opened a ticket but still have no response. I now have another issue but it seems nobody is posting here anymore. Am i wrong?

Using the latest version of Reaper DAW and the latest version of Reasonus. I have gotten my faderport 16 to sync up and work with Reaper on windows 10. But all my tracks that were once hidden in the mixer window are now and always showing no how matter many times I hide the tracks not needed. Everytime I sign into Reaper, the hidden tracks are visible in the mixer again in reaper. Please help. Thank you in advance.

Lou

• Backup existing install and add new files
• Convert CSI.ini from V1 to V3

Describe the bug
Transport Controls:
Play button activates Play & Pause together
Loop button does nothing
Rewind button returns instantly to cursor
Fast Forward button plays back starting from cursor
Record button Plays back from cursor

Sends mode:
Faders move both send volume and track volume at the same time in both Individual and Global settings.
Pan moves track pan, not send pan
Receiving track Arms when Solo Clear button is pressed

Operating System

• MacOS 10.15.7
• Reaper 6.73

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: v1.0.1
• Reasonus Resources: v1.0.1
• CSI (ReaSonus): 1.1

Expected behavior
As per the documentation

Within csi it is possible to use the focussed fx param to adjust.

This functionality should be active when the [Link] button is pressed/active.
Display shpuld display the next info:

• fx/instrument name (csi change)
• param name
• param value
• valuebar?

I want to install reasons for my Faderport v2 (newest firmware) today. I downloaded the newest Version of ReaSonus Faderport 1.0.0 . If I launch the app ReaSonus it seems like the app didn't found the midi device and I can't install reasonus. I attached a screenshot. Also i can't set the path for Reaper. like its described in the documentations.

Operating System

• [] Max OS 12.1
• M1 Pro

Thanks a lot

Hi,
my first thoughts:
In the installing instructions would be fine to mention to select Control Surface Integrator in preferences (instead of Presonus V2 2018 which is available as well)

Bugs:

• RTZ doesn't work
• holding Solo or Mute not have momentaly mute/solo function as in Studio one (nice to have:)
• when opening a project the buttons Bypass and Channel are active (lightning)
• when close the project buttons Bypass and Fast Forward are lightning

Anyhow, thanx for a good job :-)

Describe the bug
-My Faderport v2 firmware is v3.51 (latest)
-My Reaper install is v6.73
-My SWS Extensions is v2.12.1.3
-Faderport v2 is disabled in MIDI devices
-Issue: Not all buttons work. The fader works, the transport does too. None of the function buttons do anything. I have attempted to troubleshoot by using the Action "CSI Toggle Show Raw Input from Surfaces". I can see CSI logging things like the fader, transport buttons but the "Shift" key isn't logging and as a result, none of the function keys either. In short, I am expecting the Faderport v2 to behave as the documentation indicates in section 4, but it doesn't.

Operating System

• [10.13.6] Mac OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: no version displayed (weird?)
• Reasonus Resources: 1.0.1
• CSI (ReaSonus): 1.1 (reasonus-edition)

It seems you have been here these days (have you?), please go to Reaper Forum and clarify that ReaSonus is not working with current CSI version. There is a massive confusion about your ReaSonus install. I am shure people understand if you are too busy to keep up with the changes, but please remove the impression that everything works like a charm, cause it does not.

Thanks.

Describe the bug
THE SOLUTION - Must do the following: Go to Reaper Preferences>Control /OSC/Web>ADD, then from dropdown menu choose Control Surface Integration (CSI). The Pages=ReaSonus Function and Surfaces= Faderport V2. ReaSonus worked perfectly as described.
The Problem prior to finding the Solution: Followed Faderport 2 and ReaSonus instructions to the letter, but the Faderport doesn't react at all. Steps: Chose Faderport Studio One mode (next+pwr up+solo) and updated Faderport firmware. Booted Reaper and disabled Faderport 2 midi input and output, then closed Reaper. Downloaded and installed Reasonus (it found my Reaper files, which were in the default Reaper location); clicked Save. Connected Faderport USB and power and powered up. Booted Reasonus and clicked Install. Reasonus recognized Faderport 2 input and output, and I clicked Install. Booted Reaper. No life in Faderport and no connection with Reaper.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Operating System

• Windows 10
• [] Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: v1.0.1
• Reasonus Resources: ...
• CSI (ReaSonus): ...

Expected behavior
Faderport to be connect to Reaper after installation.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Describe the bug
There is no connection to Faderport8. Installation went fine, but no connection. I have checked Control/OSC/web under preferences and there is no CSI installed.

To Reproduce
Steps to reproduce the behavior:
Just followed installation procedure

Operating System

• [] Windows 10
• Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer:
• Reasonus Resources: v1.0.1
• CSI (ReaSonus): 1.1 (reasonus-edition)

Expected behavior
Faderport should connect to Reaper
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
none

Describe the bug
Unable to edit plugins using the Faderport 16 controller after firmware upgrade via Universal Control for Faderport 16 FW Version 3.21. Yes...I restarted the computer and powered off/on the Faderport 16 Unit.

To Reproduce
Steps to reproduce the behavior:

1. Update Faderport 16 to FW V 3.21 via Universal Control.
2. Reboot unit and computer.
3. Open a Reaper Session with plugins.
4. Select a track with a plugin.
5. Click on Edit Plugins on Faderport.
6. See NoMap error on the Faderport Display.

Operating System

• Ventura 13.0.1 Max OS

Versions

• Reasonus Installer: 1.01

Expected behavior
Should be able to Edit Plugins with the Faderport 16 Controller.

Screenshots

Additional context
Reasonus is pretty killer so far.

Describe the bug
I make a time selection in the timeline. But then, if I'm in 'section' navigator, the time selection gets deleted if I press'prev' or 'next'

Operating System

• [] Windows 10

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ...
• Reasonus Resources: ... v1.01
• CSI (ReaSonus): ... CSI 2, as far as I can tell. I updated to 2 this morning.

Expected behavior
A clear and concise description of what you expected to happen. - I didn't expect my time selection to disappear. In fact, if I use my keyboard shortcuts to move from one marker to the next, they also land on the start and end of the time selection.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Describe the bug
Installed Reasonus, restarted Reaper, no go. My faderport 16 was working with pretty good but limited functionality in MCU/Logic mode, now it's in Studio One mode as directed in instructions, it's 'waiting for host'.

OK I MIGHT HAVE FIXED THIS- SEE BELOW

Operating System

• [] Windows 10

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ...
• Reasonus Resources: .1.01
• CSI (ReaSonus): 1.1

Expected behavior
Expected a working control surface. It was working before in MCU mode but only 8 tracks not 16, also couldn't automate mutes though that could be user error. Now it's not connected but is 'waiting for host'.

Additional context

What do I choose in Preferences/Control Surfaces/OSC/Web control? Anything?
Update: I chose Control Surface Integrator, a new option added by the install I assume? There were no instructions that this needs to be chosen. Suggest adding this to instructions.

Hi, in Faderport V2, when master track is selected, if you solo it, you can't unsolo it whith the button.
Thanks for your work!

Would it be possible for the Flip button in V2 to control the send volume of a selected track? Prev, Next and Encoder would scroll thru the various track sends, while the fader would controle the send volume, similar to a "Sends on Fader" function on a mixer!

I've installed V1.0.1 on Windows 10 64-bit. I'm using the single Faderport V2 and everything looks great except the touch automation only works when the fader is moving. When I stop moving the fader (but still touching it) it jumps back to the current automation levels and starts following what's already there. I apparently have the latest firmware (v3.51). Anything else I can check?

Describe the bug
A clear and concise description of what the bug is.

I ran the Reasonus installer. The first time I chose the wrong file location for resources, so I deleted the file in Appdata and ran the installer again. This time it recognised my Faderport 16 and gave me the message 'Done'.

I launched Reaper, but the Faderport did not respond and still says 'Waiting for Host'. It is in Studio One mode

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Operating System

• Windows 11
• [] Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: V1.01...
• Reasonus Resources: ...
• CSI (ReaSonus): ...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Here is my reaper-midihw file

[mididevcache]
on0=Microsoft GS Wavetable Synth
oa0=
ot0=1684272781
on1=FF800 Midi Port 1
oa1=
ot1=1684272781
on2=MIDI Mix
oa2=
ot2=1684272781
on3=PANORAMA P1
oa3=
ot3=1684272781
in0=PreSonus FP16
ia0=
it0=1684272781
in1=FF800 Midi Port 1
ia1=
it1=1684272781
in2=MIDI Mix
ia2=
it2=1684272781
in3=PANORAMA P1
ia3=
it3=1684272781
on4=PreSonus FP16
oa4=
ot4=1684272781
in4=MIDIIN2 (PreSonus FP16)
ia4=
it4=1684272781
in5=MIDIIN3 (PreSonus FP16)
ia5=
it5=1684272781
on5=MIDIOUT2 (PANORAMA P1)
oa5=
ot5=1684272781
on6=MIDIOUT3 (PANORAMA P1)
oa6=
ot6=1684272781
on7=MIDIOUT4 (PANORAMA P1)
oa7=
ot7=1684272781
on8=PANORAMA P4
oa8=
ot8=1684141702
on9=MIDIOUT2 (PANORAMA P4)
oa9=
ot9=1684141702
on10=MIDIOUT3 (PANORAMA P4)
oa10=
ot10=1684141702
on11=MIDIOUT4 (PANORAMA P4)
oa11=
ot11=1684141702
on12=MIDIOUT2 (PreSonus FP16)
oa12=
ot12=1684272781
on13=MIDIOUT3 (PreSonus FP16)
oa13=
ot13=1684272781
on14=
oa14=
ot14=0
on15=
oa15=
ot15=0
on16=
oa16=
ot16=0
on17=
oa17=
ot17=0
on18=
oa18=
ot18=0
on19=
oa19=
ot19=0
on20=
oa20=
ot20=0
on21=
oa21=
ot21=0
on22=
oa22=
ot22=0
on23=
oa23=
ot23=0
on24=
oa24=
ot24=0
on25=
oa25=
ot25=0
on26=
oa26=
ot26=0
on27=
oa27=
ot27=0
on28=
oa28=
ot28=0
on29=
oa29=
ot29=0
on30=
oa30=
ot30=0
on31=
oa31=
ot31=0
on32=
oa32=
ot32=0
on33=
oa33=
ot33=0
on34=
oa34=
ot34=0
on35=
oa35=
ot35=0
on36=
oa36=
ot36=0
on37=
oa37=
ot37=0
on38=
oa38=
ot38=0
on39=
oa39=
ot39=0
on40=
oa40=
ot40=0
on41=
oa41=
ot41=0
on42=
oa42=
ot42=0
on43=
oa43=
ot43=0
on44=
oa44=
ot44=0
on45=
oa45=
ot45=0
on46=
oa46=
ot46=0
on47=
oa47=
ot47=0
on48=
oa48=
ot48=0
on49=
oa49=
ot49=0
on50=
oa50=
ot50=0
on51=
oa51=
ot51=0
on52=
oa52=
ot52=0
on53=
oa53=
ot53=0
on54=
oa54=
ot54=0
on55=
oa55=
ot55=0
on56=
oa56=
ot56=0
on57=
oa57=
ot57=0
on58=
oa58=
ot58=0
on59=
oa59=
ot59=0
on60=
oa60=
ot60=0
on61=
oa61=
ot61=0
on62=
oa62=
ot62=0
on63=
oa63=
ot63=0
in6=MIDIIN2 (PANORAMA P1)
ia6=
it6=1684272781
in7=MIDIIN3 (PANORAMA P1)
ia7=
it7=1684272781
in8=MIDIIN4 (PANORAMA P1)
ia8=
it8=1684272781
in9=PANORAMA P4
ia9=
it9=1684141702
in10=MIDIIN2 (PANORAMA P4)
ia10=
it10=1684141702
in11=MIDIIN3 (PANORAMA P4)
ia11=
it11=1684141702
in12=MIDIIN4 (PANORAMA P4)
ia12=
it12=1684141702
in13=
ia13=
it13=0
in14=
ia14=
it14=0
in15=
ia15=
it15=0
in16=
ia16=
it16=0
in17=
ia17=
it17=0
in18=
ia18=
it18=0
in19=
ia19=
it19=0
in20=
ia20=
it20=0
in21=
ia21=
it21=0
in22=
ia22=
it22=0
in23=
ia23=
it23=0
in24=
ia24=
it24=0
in25=
ia25=
it25=0
in26=
ia26=
it26=0
in27=
ia27=
it27=0
in28=
ia28=
it28=0
in29=
ia29=
it29=0
in30=
ia30=
it30=0
in31=
ia31=
it31=0
in32=
ia32=
it32=0
in33=
ia33=
it33=0
in34=
ia34=
it34=0
in35=
ia35=
it35=0
in36=
ia36=
it36=0
in37=
ia37=
it37=0
in38=
ia38=
it38=0
in39=
ia39=
it39=0
in40=
ia40=
it40=0
in41=
ia41=
it41=0
in42=
ia42=
it42=0
in43=
ia43=
it43=0
in44=
ia44=
it44=0
in45=
ia45=
it45=0
in46=
ia46=
it46=0
in47=
ia47=
it47=0
in48=
ia48=
it48=0
in49=
ia49=
it49=0
in50=
ia50=
it50=0
in51=
ia51=
it51=0
in52=
ia52=
it52=0
in53=
ia53=
it53=0
in54=
ia54=
it54=0
in55=
ia55=
it55=0
in56=
ia56=
it56=0
in57=
ia57=
it57=0
in58=
ia58=
it58=0
in59=
ia59=
it59=0
in60=
ia60=
it60=0
in61=
ia61=
it61=0

Describe the bug
I installed the Reasonus 1.01 but nothing changes in my FPv2 (single fader). The bypass, shift, link, channel, scroll, master, click, section and marker buttons don't work.

The fader has the same behavior since before installing Reasonus. I have Presonus FaderportV2 selected in Control Surface Tab. I don't know if "Reasonus Faderport" should appear on the tab but nothing appears for me.

To Reproduce
Only installing Reasonus

Operating System

• [] Windows 10

Versions

• Reasonus Installer: ...
• Reasonus Resources: 1.01
• CSI (ReaSonus): 1.1

Expected behavior
I thought the Faderport buttons would work fully, just like in Studio One.

Screenshots

Describe the bug
I have a new Faderport, all going well with Reasonus so far except I can't go from 'Section' to 'Channel'.... when I press 'channel' it doesn't activate... I have to go to 'scroll' and then to 'channel'.

To Reproduce
Steps to reproduce the behavior:

1. Go to '.Section..'
2. Click on 'Channel....' .... nothing happens.

Operating System

• [] Windows 10

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ..
• Reasonus Resources: ...v1.01 .
• CSI (ReaSonus): ... 1.1 (reasonus edition)

Expected behavior
A clear and concise description of what you expected to happen. - If I have 'section' sellected, and I press 'channel', I expect 'channel ' to be activated.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

It does not show up in the installer as midi in/out...

Describe the bug
ReaSonus installer launches fine, but doesn't present me with the option to select the midi device, only presents me with 00

I believe that this is the same bug that fuux84 encountered, so I will attach my reaper-midihw.ini file. Until then, ReaSonus is sadly not working.

Operating System

• [] Mac OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: Darwin Universal v1.0.1
• Reasonus Resources: v1.0.1
• CSI (ReaSonus): 1.1 (reasonus-edition)

Expected behavior
Should give me the option to select my faderport device to initiate installation, but it does not.

Additional context
Reaper-midihw.ini: I have changed the file extension to TXT so I can upload it to github
reaper-midihw copy.txt

Describe the bug
Not finding the FaderPort using Faderport v2. I actually know the problem but I don't know how to fix it. I set the wrong folder on the first screen of the install. I used Procmon etc.. to attempt to find where the installer is storing this data but not luck. Even found somehting in regedit for HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\TypedPaths named url2 which appears to be it but didn't seem to make any difference.

On your installer I click the developer tools and can see where it's lookng for the .ini file in the wrong place. This is my mistake I just can't figure out how to fix it. Hopefully you still a bit active on this project!

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Operating System

• [] Windows 11

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: 1.0.1

Expected behavior
Hoping this work for me to get this Faderport working.

Screenshots

Additional context
Add any other context about the problem here.

Describe the bug
A clear and concise description of what the bug is.

When I install Reasonus everything works as described until I choose CSI in the control surface area. When i choose CSI Reasonus does not apear in the pages section and I do see Faderport 2 in the surface section.
It may be because of this reason that when i choose another automation lane besides volume nothing works. Instead if i choose Pan automation and the volume gets reselected and i can no longer do anything except volume automation.
To Reproduce
Steps to reproduce the behavior:

1. Go to '...' Unfortunatley it seems the installer does not work correctly on my device so it would be difficult to reproduce it.
2. Click on '....'
3. Scroll down to '....'
4. See error

Operating System

• [] Windows 10 I am on this OS
• [] Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ... 1.01
• Reasonus Resources: ...
• CSI (ReaSonus): ...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Add hardware sends to the sends list

Hello, I was trying on my latest veroin of Windows 10 reaper to use reasonus . I added the osc controll, i think that is waht it is called, or it is CSI (CONTROL SERFICE INTIGRATOR) in reaper. But when it asked me in the reaper preferences to add my faderport or the csi control of my faderport 16, reaper crashed. Now I cant get back to the preferences in reaper to delete the csi that I added. How do i get back into reaper without reaper crashing?

Lou

When no track color applied, the track color becomes orange. This needs to be a black or white'ish color

In the FaderPort v2 zone files the Undo and Redo are missing

I'm running the .exe installer with wine.
The reasonus app runs.
I insert the reaper path.
Then the "install" button remain inactive.

Operating System
Ubuntu studio
Reaper 6.78
sws installed

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: .1.01

I try with a friend to do the same install on another computer on Ubuntu studio and the issue is exactly the same.

Thanks for helping, Reasonus seems so nice!!!!

Is your feature request related to a problem? Please describe.
ioStation 24c is not supported. Installer does not detect it.

Describe the solution you'd like
Support the ioStation 24c as a variant of the Faderport v2. It is essentially a v2 with an audio interface bolted on.

Describe alternatives you've considered
Cocko's Faderport v2 settings work out of the box with the device, but without the enhancements you have created.

Additional context
reaper-midihw.ini output:

[mididevcache]
on0=Microsoft GS Wavetable Synth
oa0=
ot0=1684602848
on1=Arturia KeyStep 32
oa1=
ot1=1684602848
on2=3- ioStation 24c MIDI Out
oa2=
ot2=1684602848
in0=Arturia KeyStep 32
ia0=
it0=1684602848
in1=3- ioStation 24c MIDI In
ia1=
it1=1684602848
on3=ATM SQ
oa3=
ot3=1684538724
on4=MIDIOUT2 (ATM SQ)
oa4=
ot4=1684538724
in2=ATM SQ
ia2=
it2=1684538724
in3=MIDIIN2 (ATM SQ)
ia3=
it3=1684538724

Describe the bug
If you enter a text in the field "Display Text" in the Mix Management of Reasonus Fader Port Control which is followed by a dot you will no longer able to change the display text.

To Reproduce
Steps to reproduce the behavior:

1. Open Reasonus Faderport Control
2. Goto "Mix Management"
3. Go to 'Display Text' and enter a text followed by a . (dot, e.g. GUITARS.)
4. Save Filter
5. Open Reasonus Faderport Control again and switch to the Tab where you entered the text followd by a dot
6. Error: Display Text field is now empty. Changes (entering new Text) are not applied when saving filter. Old entry ist shown in channel-display of Faderport unit.

Operating System

• Windows 10
• [] Max OS

Versions
Versions can be found on the About page of the installer

• Reasonus Installer: ...
• Reasonus Resources: ...
• CSI (ReaSonus): ...

Expected behavior
New Text entered in the display text-field should be applied.

Screenshots

Additional context
Nothing