[SOLVED] Faderport connection problem in Mixbus32C 7.1.97

[jonetsu]

Hello,

The Faderport used to work as the proper Faderport ports would appear in the drop down menus when configuring.

This time around the only 'ports' that are shown are : x-virtual-keyboard and physical_midi_input_monitor_enable.

While the Faderport ports are clearly shown in the MIDI ports.

How to enable the Faderport ?  Is there a new way ?

Thanks.


   

   

   

[Dingo]

It might pay to download 7.2 I know there were some machine control fixes.... might fix it for you.

[RayMasse]

Hello,

The Faderport used to work as the proper Faderport ports would appear in the drop down menus when configuring.

This time around the only 'ports' that are shown are : x-virtual-keyboard and physical_midi_input_monitor_enable.

While the Faderport ports are clearly shown in the MIDI ports.

How to enable the Faderport ?  Is there a new way ?

Thanks.


+1 here

[jonetsu]

It might pay to download 7.2 I know there were some machine control fixes.... might fix it for you.

Hi.  Still the exact same result as shown above.  The MIDI display will actually show the faderport even when the Faderport is physically disconnected.

I used the Faderport for so many mixes in previous versions of Mixbus32C.  

That support is now seemingly broken.  Is there any way to bring it back ?

[Jostein]

It might pay to download 7.2 I know there were some machine control fixes.... might fix it for you.

Hi.  Still the exact same result as shown above.  The MIDI display will actually show the faderport even when the Faderport is physically disconnected.

I used the Faderport for so many mixes in previous versions of Mixbus32C.  

That support is now seemingly broken.  Is there any way to bring it back ?

Strange. It works for me as usual with 7.2 on Kubuntu 20.04. Is there any chance that your Faderport is broken?

EDIT: BTW: I'm using Faderport 1.

[jonetsu]

Jostein wrote:

"Strange. It works for me as usual with 7.2 on Kubuntu 20.04. Is there any chance that your Faderport is broken?

EDIT: BTW: I'm using Faderport 1."


It does register with Bitwig, as shown below.  I'm using Xubuntu 18,04 (did not change/modify this OS at all, for music production) and Faderport 1 as shown in the screenshot above.

I do not know any other means of checking it out than by listing the USB devices:

% lsusb
[...]
Bus 003 Device 003: ID 194f:0201 PreSonus Audio Electronics, Inc.
[...]

And by seeing Bitwig's reaction.  The power adapter was not connected to the Faderport as it serves only to power the fader.  The power supplied by the USB interface is enough for everything else.

USB cable unplugged from Faderport:


   



USB cable plugged :


   

[Jostein]

I get the same as you on lsusb. However, I find the name of the device unusual, has always been like that on your system?

I attach how it looks in my MB32C and Reaper.

[jonetsu]

Jostein wrote:  

"I attach how it looks in my MB32C and Reaper."


There's one detail in there that made me remember something : a2j

That's about two years I haven't used the Faderport.  I forgot about the need to run a2j before running Mixbus32C as it needs that to be able to recognize the Faderport ports :

% a2j_control ehw start
--- enable export of hardware ports
--- start

And when exiting Mixbus32C a2j has to be terminated so that Bitwig can see the MIDI ports.  So I've made two aliases for that:

alias A2J="a2j_control ehw start"
alias KA2J="killall /usr/bin/a2jmidid"

It now works as it should !