Device panel sharing thread (Bitwig remote controls for devices)

[aMUSEd]

Added FabFilter:

Timeless
Volcano
Saturn

next - Revival (or maybe not - stupid automation assignments all have the same name!!) and the rest of the GRMs (probably just the stereo ones)

[aMUSEd]

Added the rest of the GRM-Tools - ie the ones not in Creative which was already done - minus Spaces, which I don't have, and the EQ. Also I only use the Stereo versions.

Also added iZotope Vocalsynth and a basic one for Loom (not much you can map)

[aMUSEd]

Added NewSonicArts Granite and Audreio Revival

[lxegs]

Are GRM tools interesting (except creative bundle), considering what plugins i have already ?

i tested the demo versions a long time ago .....

[aMUSEd]

Oh yes

[aMUSEd]

Added:

Turnado
Argotlunar
NI RC24
NI RC48

[Echoes in the Attic]

Good stuff here. I'll try to do some as well soon.

Question on the Reaktor ensembles. Although you wouldn't be able to share a default mapping, we could still share presets with mappings for a given ensemble right? And then you could browse presets for that after loading the preset with the mapping you want? I save all my instruments as Bitwig presets anyways as staring points.

[aMUSEd]

Good stuff here. I'll try to do some as well soon.

Question on the Reaktor ensembles. Although you wouldn't be able to share a default mapping, we could still share presets with mappings for a given ensemble right? And then you could browse presets for that after loading the preset with the mapping you want? I save all my instruments as Bitwig presets anyways as staring points.

Yeah you could do preset level mappings for particular ensembles, but one for Reaktor as a device wouldn't make sense.

[Echoes in the Attic]

Good stuff here. I'll try to do some as well soon.

Question on the Reaktor ensembles. Although you wouldn't be able to share a default mapping, we could still share presets with mappings for a given ensemble right? And then you could browse presets for that after loading the preset with the mapping you want? I save all my instruments as Bitwig presets anyways as staring points.

Yeah you could do preset level mappings for particular ensembles, but one for Reaktor as a device wouldn't make sense.

Yes of course. But I think it would still be totally worth it to share presets if Reaktor ensembles with mappings in this thread. Monark, razor etc.

And actually that got me thinking, wouldn't just sharing presets be easiest for the other vsts as well? Then a user can just save as default right? Or maybe the import of defaults isn't that complicated anyways. I didn't don't try yet.

[aMUSEd]

Yeah that would be another approach but I like the flexibility offered by having both device and preset level panels available. Kore did the same thing (although device mappings were not as user friendly)

[r4ns0m]

Edit: wrong place to ask, posted a new thread instead.

[aMUSEd]

Added:

The Drop
Bloom
Valhalla SpaceModulator
Valhalla FreqEcho
Fracture XT
Frostbite
LFOTool
PSP Echo
Audiority Grainspace
2C Aether
Adaptiverb
Reflex+ 3

[aMUSEd]

Aether was difficult - there seem to be a fair number of plugins that Bitwig 2 struggles to map from the plugin GUI - it only works from the generic param list, which makes it extra hard when params are also poorly named as is the case with Aether.

Is this a Bitwig 2 bug, I can map from the gui in Kore for Aether and all the other plugins I've encountered this with?

[aMUSEd]

Here are presets for the Reaktor ensembles Rounds, Kontour and Monark (not snapshots - just mapped to controls)

https://dl.dropboxusercontent.com/u/564 ... embles.zip

[lxegs]

added NI FORM (1.1) presets