Device panel sharing thread (Bitwig remote controls for devices)
-
- KVRist
- 39 posts since 28 Sep, 2023
Can anyone check that as well? I deleted all my device infos from the bespoke devices folder in the library settings folder. Created one new device profile which can be recalled when opening Bitwig again, but I have sofar been unable to trace its actual location. Strange. Really strange.
- KVRAF
- Topic Starter
- 37375 posts since 14 Sep, 2002 from In teh net
Don't forget these are invisible files in an invisible folder so you need to change a setting in the OS to see them (or use a browser that does this like Forklift on Mac)thomba wrote: Thu Oct 30, 2025 11:10 am Can anyone check that as well? I deleted all my device infos from the bespoke devices folder in the library settings folder. Created one new device profile which can be recalled when opening Bitwig again, but I have sofar been unable to trace its actual location. Strange. Really strange.
Also apart from CLAP plugins they don't tell you which plugin the remote control is for - so what I do is as soon as I make one is set the browser to show the most recent file at the top, then compress it with the plugin name and the plugin ID code in the ZIP filename so I don't lose track of it
-
- KVRist
- 39 posts since 28 Sep, 2023
Yes. That I know. I have basically transferred all the folder containing the information to my desktop. Leaving the bespoke folder empty. Than started Bitwig created one new editor definition. Saved it, the required folder remained empty. Closed Bitwig. Opened it again. Opened the plugin that I used to create the editor settings. And it worked. But still no sign of any file in the devices folder.
- KVRAF
- Topic Starter
- 37375 posts since 14 Sep, 2002 from In teh net
That might be a sign they have changed how this works and remote controls are now stored elsewhere but they should be warning users if they have done this - or it might be due to a bug
- KVRAF
- Topic Starter
- 37375 posts since 14 Sep, 2002 from In teh net
It looks like there is a beta 4 - maybe that fixes it?
- KVRAF
- Topic Starter
- 37375 posts since 14 Sep, 2002 from In teh net
Found the changeling for beta 3
Fixes
DAWproject files open again (a regression from v5.x) [39435]
Dragging an automated device now brings the automation with it [39463]
Double-click to delete a clip automation point is possible on the Arranger
Correct automation value is always displayed when hovering over a Hold point [39439]
The Detail Editor Panel no longer updates the play start marker when working with Launcher clips
Dragging Launcher clips to the Arranger no longer gets the length wrong [39445]
Drawing automation from the track area into a clip no longer messes the clip [39448]
Editing automation events while they were being recorded now avoids crashes and other reasonable mayhem [39152]
Curve Editor: Tool names in the context menu are no longer so long
Crashes Fixed
Fixed crash when editing a clip automation point on the Arranger [39402]
Fixed crash when navigating time selection cursor in Track context of the Detail Editor Panel [39412, 39423]
Fixed crash when copying a time range of clip automation [39443]
Fixed crash when dragging an Arranger time selection past multiple tracks, automation lanes [39388]
Fixed crash when deselecting audio clips [39390]
Fixed crash when double-clicking into a note editor with the Time Selection tool [39462]
Fixed crash when slicing a sample with multiple takes at onsets [39406]
Nothing that suggests remote controls have deliberately been changed so this is more likely a bug - can't see it mentioned in the beta 4 log either though so it may be no one has reported it yet
Were they working in Bitwig 6 beta 2?
I believe Bitwig 6 is meant to be bringing 'improvements' to remote controls such as per project and track remote controls so maybe that is behind this change and this is the transition period but if so they need to make that clearer to users
Fixes
DAWproject files open again (a regression from v5.x) [39435]
Dragging an automated device now brings the automation with it [39463]
Double-click to delete a clip automation point is possible on the Arranger
Correct automation value is always displayed when hovering over a Hold point [39439]
The Detail Editor Panel no longer updates the play start marker when working with Launcher clips
Dragging Launcher clips to the Arranger no longer gets the length wrong [39445]
Drawing automation from the track area into a clip no longer messes the clip [39448]
Editing automation events while they were being recorded now avoids crashes and other reasonable mayhem [39152]
Curve Editor: Tool names in the context menu are no longer so long
Crashes Fixed
Fixed crash when editing a clip automation point on the Arranger [39402]
Fixed crash when navigating time selection cursor in Track context of the Detail Editor Panel [39412, 39423]
Fixed crash when copying a time range of clip automation [39443]
Fixed crash when dragging an Arranger time selection past multiple tracks, automation lanes [39388]
Fixed crash when deselecting audio clips [39390]
Fixed crash when double-clicking into a note editor with the Time Selection tool [39462]
Fixed crash when slicing a sample with multiple takes at onsets [39406]
Nothing that suggests remote controls have deliberately been changed so this is more likely a bug - can't see it mentioned in the beta 4 log either though so it may be no one has reported it yet
Were they working in Bitwig 6 beta 2?
I believe Bitwig 6 is meant to be bringing 'improvements' to remote controls such as per project and track remote controls so maybe that is behind this change and this is the transition period but if so they need to make that clearer to users
-
- KVRian
- 718 posts since 4 Feb, 2017
Why not use beta 4, which was released 4 weeks ago?thomba wrote: Thu Oct 30, 2025 10:32 am Just toying around with Bitwig 6 Beta 3. All my control panel settings are do not show up. Although my devices folder is full of them. Might that be a bug? Do I have to do anything the "reinstall" them. thanks
I did not have any problems in the previous betas, though.
Everything is still working the same as in Bitwig 5. The device files are still stored in the same way and location as in Bitwig 5:
../Bitwig/Library/.settings/devices (where .settings is a hidden folder).
- KVRAF
- Topic Starter
- 37375 posts since 14 Sep, 2002 from In teh net
I've reached out to support to clarify what is happening and they say nothing has been changed re location or format so it sounds like maybe just a glitch on your system?
- KVRAF
- Topic Starter
- 37375 posts since 14 Sep, 2002 from In teh net
-
- KVRist
- 451 posts since 21 Jul, 2001
Just added the vst3 panels shown below. Mostly from Audiority, Softube and UAD:
Arturia CZ V (vst3).zip
Audiority Blue Face (vst3).zip
Audiority Chief Chorus (vst3).zip
Audiority Distortion 1 (vst3).zip
Audiority Goat (vst3).zip
Audiority Green Reaper (vst3).zip
Audiority Heavy Pedal (vst3).zip
Audiority Space Age 55 (vst3) bw6.zip
Audiority Space Age 555 (vst3).zip
Audiority Space Station UM282 (vst3).zip
Eventide Crushstation (vst3).zip
Exponential Audio Symphony (vst3).zip
Gforce oddity v3 (vst3).zip
JMG Lofinity(vst3).zip
PSP Chamber (vst3).zip
Softube - Dimension (vst3).zip
Softube - Echoes (vst3).zip
Softube Bad Speaker (vst3).zip
Softube Fix Phaser (vst3) bw6.zip
Softube Model 101 (vst3).zip
Softube Model 77 reverb (vst3) bw6.zip
Softube Model 77 reverb (vst3).zip
Softube Model 80 (vst3).zip
Soundtoys Spaceblender (vst3).zip
UADx Galaxy Tape Echo (vst3).zip
UADx LA-2A (vst3).zip
UADx Opal (vst3).zip
UADx PolyMAX (vst3).zip
UADx Pultec EQP-1A (vst3).zip
UADx Pultec HLF-3C (vst3).zip
UADx Pultec MEQ-5 (vst3).zip
UADx Pure Plate (vst3).zip
Wave Alchemy - Pulse (vst3).zip
Xoxos Bong (vst2).zip
Note that the UAD synths have not much options for device control, so their panels miss a lot of controls.
link: https://1drv.ms/f/c/c7595e03205a06de/Ug ... E2ZyrQTF_4
Arturia CZ V (vst3).zip
Audiority Blue Face (vst3).zip
Audiority Chief Chorus (vst3).zip
Audiority Distortion 1 (vst3).zip
Audiority Goat (vst3).zip
Audiority Green Reaper (vst3).zip
Audiority Heavy Pedal (vst3).zip
Audiority Space Age 55 (vst3) bw6.zip
Audiority Space Age 555 (vst3).zip
Audiority Space Station UM282 (vst3).zip
Eventide Crushstation (vst3).zip
Exponential Audio Symphony (vst3).zip
Gforce oddity v3 (vst3).zip
JMG Lofinity(vst3).zip
PSP Chamber (vst3).zip
Softube - Dimension (vst3).zip
Softube - Echoes (vst3).zip
Softube Bad Speaker (vst3).zip
Softube Fix Phaser (vst3) bw6.zip
Softube Model 101 (vst3).zip
Softube Model 77 reverb (vst3) bw6.zip
Softube Model 77 reverb (vst3).zip
Softube Model 80 (vst3).zip
Soundtoys Spaceblender (vst3).zip
UADx Galaxy Tape Echo (vst3).zip
UADx LA-2A (vst3).zip
UADx Opal (vst3).zip
UADx PolyMAX (vst3).zip
UADx Pultec EQP-1A (vst3).zip
UADx Pultec HLF-3C (vst3).zip
UADx Pultec MEQ-5 (vst3).zip
UADx Pure Plate (vst3).zip
Wave Alchemy - Pulse (vst3).zip
Xoxos Bong (vst2).zip
Note that the UAD synths have not much options for device control, so their panels miss a lot of controls.
link: https://1drv.ms/f/c/c7595e03205a06de/Ug ... E2ZyrQTF_4
