Presonus Faderport 8/16 native supported bitwig script - No group tracks No hierarchical mode!?

[giftmusic]

I recently purchased a Presonus Faderport 16 controller specifically because it was listed as "officially supported" for Bitwig. I am writing to report a significant issue I encountered while using. The problem is that the native Faderport script doesn't allow you to control channels within a group channel. This prevents anyone from using the Faderport script to control all channels!
As a temporary solution, I have been using the Faderport in Mackie MCU mode, driven by moss but its not ideal, and kinda buggy since its not officially supported as a mossgrabber script. I am eager to utilize the native Faderport Bitwig script once the issue with group channels track control is resolved.
having a simple flat mode (hierarchical) where every track is directly accessible would be super easy.
I am confident in the Bitwig development team's expertise, and I believe that addressing this matter will greatly enhance the functionality and experience for Faderport users. As of right now its not truly supported if you cant access all the channels. As anyone discovered a workaround or a fix? Thank you!

[slackhead]

I recently purchased a Presonus Faderport 16 controller specifically because it was listed as "officially supported" for Bitwig...... As of right now its not truly supported if you cant access all the channels. As anyone discovered a workaround or a fix? Thank you!

I have a Faderport 8 and experience the same issue with groups. I've pretty much stopped using it for now and keep checking new versions for changes. Was very disappointed that it wasn't addressed in V5.

I have emailed support about this some months ago but did not receive a response. Perhaps if you and others were to email and highlight the incomplete implementation they will put some effort into fixing it.

[giftmusic]

Yes, I think we all need to hit them with a support ticket at once with these issues and maybe they fix it.

[slackhead]

Yes, I think we all need to hit them with a support ticket at once with these issues and maybe they fix it.

Please let us know if you get a response.

[giftmusic]

After the new release of Bitwig 5.1 and nothing about fixing this issue I sent another request asking to fix this issue. Please do the same. Letting them know there is many users out there requesting should bump this up to get fixed.

[Kirkwood West]

isn't this in the open source extension?

https://github.com/bitwig/bitwig-extens ... /faderport

If I had a Faderport I would check it myself and submit a fix.

[giftmusic]

Yes, looks like it. What does that mean though? How do I get someone to fix these issues? I have already contacted Bitwig and no one seems to care over there. Thank you.

[Kirkwood West]

Yes, looks like it. What does that mean though? How do I get someone to fix these issues? I have already contacted Bitwig and no one seems to care over there. Thank you.

Possibly either do it your self or recruit someone with a Faderport and knows how to do it. I would look into it if I had one

[giftmusic]

How about I send you mine? Private message me please.

[Qsonic]

I does work in my setup, I can go into groups and control tracks and sends, I can even go levels deeper(groups in groups)
What is verry annoying is that communication (focus) between Bitwig and Faderport is easeley lost. So you have to refocus the connection.
Workaround: You need to map ´open’ en and ‘close group’. I did it to the buttons on my faderport. You also need to map a button to focus the mixer ( when connection is lost)
It feels a little clumsy but it has al lot of protentional. I a situation that there is no loss of focus. I hope that stability in the connection will improve.

[Kirkwood West]

I does work in my setup, I can go into groups and control tracks and sends, I can even go levels deeper(groups in groups)
What is verry annoying is that communication (focus) between Bitwig and Faderport is easeley lost. So you have to refocus the connection.
Workaround: You need to map ´open’ en and ‘close group’. I did it to the buttons on my faderport. You also need to map a button to focus the mixer ( when connection is lost)
It feels a little clumsy but it has al lot of protentional. I a situation that there is no loss of focus. I hope that stability in the connection will improve.

Wicked way to work thru the problem..

I wonder if it’s the connection itself? Are you running through a hub or anything like that? I usually have issues when I’m using more than 3 usb midi devices on a hub

[Qsonic]

How would you do it?

No hub, straight in to the PC with USB.

With out of focus/lossing connection I main: The folder Icon on the track needs to be black to make the open and close group signals form the mixer to Bitwig work. When you jump between bitwig windows the channels are stil grey but the little icon is not black any more. Then there is no respons when i try to enter a group or get out of a group. When I focus the bitwig window, teh litte icon turns black again and I can go in and out groups

[giftmusic]

Does anyone here know how to train chat GPT to read and learn the Bitwig API code? if so, I bet all of us could create our own custom scripts! We wouldn't have to rely on half baked and older scripts for our devices. Please let me know if anyone knows how this would be done. Thank you!