Bitwig Resources

[Echoes in the Attic]

Given that we will likely see many user scripts and probably many commercial offerings for different controller scripts, it would be great to have a sticky in this forum for Bitwig resources in general. One place for people to paste links to controller scripts or other resources like tutorials and patch libraries.

Sticky this?

--
Edit Dom: Yes, sticky!
We will add a section on our website for such things in the future, but for now lets just collect this stuff here as we go!
If it gets too long, i can do some cleanup...
--
Edit Tom:
I will clean out this thread now and remove chatter and non-ressources as well as outdated posts.
Please use it for posting resources only from now on, for questions and discussions open a new thread on the main forum. This is not the place to ask general questions!

And please remember that this thread goes back to the initial release of BWS in 2014, so some of the older information and scripts may be outdated! So you may want to browse it from the end to see the fresh content first....
Thanks

[ThomasHelzle]

Great Idea Echoes!

I'll start off with my AKAI MPD18 Controller Script:
It's auto-detecting the device (if you press the "Detect available Controllers" Button in Preferences/Controllers) and configured to translate Polyphonic Aftertouch to Timbre. Nothing fancy otherwise - it's a rather plain device after all.

This of course only works if you set the Pads in the MPD18 to produce Polyphonic Aftertouch via the AKAI Editor tool and save the Settings to the Device. This needs to be done for EVERY PAD!
By default it's set to Channel Aftertouch which doesn't translate to Timbre.

This then allows you to play the per-Voice modulation live and record it as Timbre like so:



Edit: All my Scripts are now in my Github Repository at:
https://github.com/ThomasHelzle/Toms_Bitwig_Scripts
Please download the latest versions from there ("Download Zip" Button).

Extract the file "MPD18.control.js" to your
"C:\Users\Username\Documents\Bitwig Studio\Controller Scripts\akai" Folder (or equivalent on Mac/Linux).
The next time you start BWS you should have it as an Option in Preferences.

Let me know how it works for you!

Cheers,

Tom

[Ogopogo]

deleted

[ThomasHelzle]

I posted these Wallpapers on the epic Bitwig thread already, but thought maybe some people missed them so I'll repost them here:

Bitwig Logo Wallpaper 3D:




And a version closer to the new Bitwig Studio Colours:




And third a Bitwig Packshot Closeup Photo:


If you rightclick them, your browser should offer you to save them. They are fully HD so should look good on most devices.

They are free for personal use as Wallpapers.
For commercial use, please contact me to get a license.

Enjoy!

Tom

[ThomasHelzle]

And another one:

Generic Controller Script with separated Midi Channels

I worked with Processing a while ago and implemented some generative Algorithms that send out Midi via CopperLan on several channels at once. In Bitwig, those are all merged into one, which created a rather horrible cacophony...

So I created two Controller Scripts for the virtual Midi Channels - called "VMidi 1" and "VMidi 2" in accordance to the default names of the first two virtual channels in CopperLan (http://www.copperlan.org/) that separate the 16 Midi Channels into separate Devices.

But those are actually generic, so you should be able to use them with any keyboard or midi device in case you want to separate the midi channels.

There is one drawback though: since Bitwig 1.0 has no selector for the channel, it basically shows 16 Midi devices in the dropdown. So if you add multiple of those, the dropdown is getting rather long
That's why I only install one such device normally...



Edit: All my Scripts are now in my Github Repository at:
https://github.com/ThomasHelzle/Toms_Bitwig_Scripts
Please download the latest versions from there ("Download Zip" Button).

You should extract it to:
"C:\Users\YourUsername\Documents\Bitwig Studio\Controller Scripts" Folder (or equivalent on Mac/Linux).

Then select it for your Controller in Preferences and you should be good to go.

I wrote a bit about what the Script does and how it works here:
http://www.kvraudio.com/forum/viewtopic ... 6#p5699286

Cheers,

Tom

[ThomasHelzle]

I created an Intro-Level-Tutorial on how to create your own Controller Scripts to overcome the current limitation with the "Generic Midi Keyboard" Controller not allowing for User defined Device Naming.

With the help of this, you could for instance have a "Korg Wavestation" or a "Doepfer LMK3" instead of several "Midi Keyboard"s in a Row...

You find the Tutorial here:
http://www.kvraudio.com/forum/viewtopic ... 9&t=407092

Cheers,

Tom

[dsan@mail.com]

Here's a link to a script for Axiom Pro 49 keyboard in case anyone needs it (about mid-way down the page):
http://www.kvraudio.com/forum/viewtopic ... 2&start=15

Note: It works for playing into a VST track; haven't fully tested it but does do "Learn" to control track parameters.

Happy Musiking!
dsan

[ThomasHelzle]

Surround Setup for Sends

Disclaimer: I am aware that this is not "real" surround support in BWS.
It's just something I use to "sit inside the sound".

I somehow really enjoy listening to sound in surround (I have four monitors around me) and wondered if I could use the nice XY container to pan sound around the room.

And yes, we can



The principle is simple:
First I have a XY container which I only use for modulation.
In it's Post FX Slot I put an Instrument Layer in which I dragged two "Tool" devices.
After each Tool I put a Hardware FX, the first one has it's "Audio Out" set to the two front speakers, the second has it set to the back speakers.
The X axis of the XY controller modulates the pan of both Tools so that they move the full way from left to right in unison.
The Y axis modulates the Amplitude of Tool 1 (which is set to -18 before the modulation) with a value of +18 and the Amplitude of Tool 2 (also set to -18 beforehand) with a value of -18.
Now you can pan between for speakers with the XY pad

Here's the preset:
Toms Surround Setup

If you use my preset, make sure you set the correct Stereo Output for Front and Back in the two Hardware FX Devices according to how your system is set up.

I use it on sends...

Cheers,

Tom

[ThomasHelzle]

Although I hardly expect anybody else still using one:

Here is the Script I use for my ancient Doepfer LMK3 Keyboard:

Doepfer LMK3 Controller Script

I don't use any masterkeyboard functionality with it, but if you do and need channel separation, let me know.

Cheers,

Tom

Edit: All my Scripts are now in my Github Repository at:
https://github.com/ThomasHelzle/Toms_Bitwig_Scripts
Please download the latest versions from there ("Download Zip" Button).

[marvotron]

I just started working on a nanoKontrol script and i've setup a github repository here :

https://github.com/Normalised/bitwig-control-scripts

If anyone (Thomas?) wants a place to store their scripts let me know your github name and i'll add you as a contributor.

[ThomasHelzle]

mljakobsen posted this and I thought it belongs here -
Maschine Controller Script for Bitwig!:

Check this out !

http://www.native-instruments.com/forum ... pt.218359/

Cheers,

Tom

[ThomasHelzle]

Since this comes up pretty often:

Until we have direct Midi Mapping from Track to Track, you may have to rethink how you approach certain situations in BWS:

Plugins that need Audio and Midi both can be used, if you:
a.) Route an Audio Track Output to a Hybrid Track.
b.) Put the VST that needs both Audio and Midi Input on the Hybrid Track. It can receive Midi and hold Midi Clips while receiving Audio from the Audio Track. So in a way it's the other way around from other hosts, routing the Audio instead of the Midi Data.


Midi Arpeggios, -Generators, -Modifiers:
Often you don't need Midi routing in BWS where in other hosts you would, since you can simply put your midi VSTs on the same track in front of your instrument.


I don't have a "clean" solution for recording the output of midi Generators, Arpeggiators, Sequencers, but it can be done with tools like LoopMidi, CopperLan and similar Virtual Midi Cable Devices. You send out the Midi from a "Hardware Instrument" device you put at the end of your chain to such a Virtual Midi Cable and on another Track you use the input from the same Virtual Midi Cable to record...

I hope this helps!

Cheers,

Tom

[ThomasHelzle]

Blue Cat Audio "Remote Control":
http://www.bluecataudio.com/Products/Pr ... teControl/

This is an affordable solution for people who want to send out rich data to external instruments.
Put it in front of the Hardware Instrument Device and you are able to control/send all kinds of Midi Data to the external Device.
I only tried the Demo, but was easily able to map one of the Controls to a Macro Knob and modulate it with an LFO, thus driving the ModWheel on my Yamaha CS1X.

Blue Cat's "PatchWork" could also be interesting for more involved setups...

Cheers,

Tom

[lem8r]

Here is my Akai APC20 controller script https://github.com/lem8r/bitwig_apc20
Read the manual for all Shift+Button combinations.
For LED feedback in note mode put Hardware instrument plugin inside FX layer container, select APC20 for midi output and choose channel 10.
I will commit bugfixes and maybe new features so check for updates.

Also there is APC40 script to keep it in one place https://github.com/stylemistake/bitwig_apc40

[ThomasHelzle]

I just updated my Reaktor Ensemble "Toms Midi Mangler" to v005.
It now should let all Midi through that isn't getting mangled and the Note-Hangers are gone too (thanks Lee!).



It is a "replacement" for Lives Random Pitch and Velocity Tools and adds Note Probability and a Note Range as well as the ability to keep notes inside a Scale, all in one convenient Tool.
Full Version of Reaktor required. I used Version 5.9 to create it.

More Information and Downloads on the thread:
http://www.kvraudio.com/forum/viewtopic ... 9&t=406683

Cheers,

Tom