dgmulf / twister4bitwig Goto Github PK

The MFT template loads just fine from the MidiFighter Utility, but putting the corresponding *.bwextension in the Extensions folder for Bitwig has no effect. Bitwig does not "see" it and does not load it. Nothing appears in Settings > Controllers, and there is no successful load message during Bitwig startup. This is on a Windows 10 system with Bitwig 2.5b7.

So.... trying to use Bitwig's Mappings Browser Panel seems to work correctly when you click any control in the UI and twist a knob in the User page. The assignment gets made and looks correct. But when you exit the Mappings Browser Panel, the knob doesn't actually do anything at all. I've tried it on track volume controls, on automation knobs in standard Bitwig devices and in 3rd party VSTs, and nothing happens.

Oddly, the only VST Synth with an internal MIDI mapping feature that seems to work fine with your controller so far is VPS-Avenger. All knobs in the User page are recognized by Avenger and work perfectly with its internal MIDI mapping. Even momentary toggle buttons in the UI respond perfectly to a knob press (toggling ON while held, then toggling OFF when released). But Pigments (by Arturia) does not recognize nor respond to the knobs in the User page at all. Like, it doesn't even "see" that you're twisting the knob, so it never makes the internal MIDI assignment to any of the CC numbers in the User page.

System Deets:
Windows 10 Pro, i5 2500, 16 GB RAM, Audient iD14, Geforce 1080
Bitwig 2.5 Beta 7 (and also in Beta 8)

Hello,
When using Device Mode and Knob 1 to select tracks I've noticed it skips grouped folders.
After manually enter the group (w/ mouse or keyboard), Knob 1 track selection will stay confined inside the group and cannot leave the folder by scrolling.
Is this by design or am I using it incorrectly? Thanks!

Running Win10x64 / BWS 3.2.8

After finding your entry in Settings > Controllers > Add, the "DJ TechTools Midi Fighter Twister" controller panel is added to the list of controllers in Bitwig, but by default the two MIDI input/output dropdowns are empty. Nothing works until a user notices these aren't assigned to a piece of hardware and selects "Midi Fighter Twister" from both drop-downs.

Not a huge issue, but worth mentioning in whatever install/setup doc you create for new users. Also, I'm certain that pawnbroker's original controller script did not require this manual config step. And Moss' "Ableton Push 2" controller script didn't require this either.