Normalised/bitwig-control-scripts

M-Audio Oxygen 25 Bitwig script mod wheel and pitch bend assign issue

freshold opened this issue · 7 comments

freshold commented

Firstly, thank you very much for writing the Oxygen 25 script!

I've been using it and have a couple of questions:

  1. Is line 13 in the script supposed to be there?
  2. I can't seem to midi learn the Mod Wheel using this script? I know nothing about java and have tried to look through the code but can't figure out how to amend it to allow me to do this. I've been at it now for a few hours! It doesn't seem to make a difference what I do to lines 30 or 43, and I can't work out what other lines are relevant to this?

Can you help please?

Thanks in advance!

P.S. I've tried to experiment with creating basic scripts in order to learn how this all works but they don't even appear in the controllers menus. I know how to do my own version of lines 1 to 7 of your Oxygen 25 script correctly, so I'm guessing that Bitwig might have some sort of validation whereby scripts that contain any errors in the code aren't listed? My attempts more than likely contain errors, but I was hoping I could use trial and error and learning from my mistakes/bugs to work this out!

Normalised commented

Maybe @cheldt can help with the Oxygen script. As for creating your own scripts, where are you putting them and what names are you giving them?

cheldt commented

Hi

yep, line 13 is generating another naming scheme for autodetecting the
device.
There are 3 different versions:

Line 7 = "Oxygen 25"
Line 13 = "[1-9]- Oxygen 25"
Line 14 = "Oxygen 25 MIDI - [1-9]"

I copied these lines from an allready existing script in bitwig.
I think that every operating system is naming MIDI-Devices a bit
differently, so this is an attempt to cover all types of naming schemes.

First you could comment in line 56, restart bitwig and check which
debug-output for moving module-wheel is generated (cc-value)

Cheers
Christian

On 04/21/2014 05:46 PM, freshold wrote:

Firstly, thank you very much for writing the Oxygen 25 script!

I've been using it and have a couple of questions:

  1. Is line 13 in the script supposed to be there?
  2. I can't seem to midi learn the Mod Wheel using this script? I know
    nothing about java and have tried to look through the code but can't
    figure out how to amend it to allow me to do this. I've been at it
    now for a few hours! It doesn't seem to make a difference what I do
    to lines 30 or 43, and I can't work out what other lines are
    relevant to this?

Can you help please?

Thanks in advance!

P.S. I've tried to experiment with creating basic scripts in order to
learn how this all works but they don't even appear in the controllers
menus. I know how to do my own version of lines 1 to 7 of your Oxygen 25
script correctly, so I'm guessing that Bitwig might have some sort of
validation whereby scripts that contain any errors in the code aren't
listed? My attempts more than likely contain errors, but I was hoping I
could use trial and error and learning from my mistakes/bugs to work
this out!

—
Reply to this email directly or view it on GitHub
#1.

freshold commented

Hi,

Thanks for your reply.

How do I check which debug-output please?

If you mean to find out what CC number the mod wheel is, I checked that using Logic X, and it's CC 1, and the pitch bend wheel is CC 0. So I think I need CC 0 up to CC 109 to be freely mappable? However I can't seem to successfully amend the script to allow this.

Does that make sense?

Regards,

Jonnie

On 22 Apr 2014, at 09:02, cheldt notifications@github.com wrote:

Hi

yep, line 13 is generating another naming scheme for autodetecting the
device.
There are 3 different versions:

Line 7 = "Oxygen 25"
Line 13 = "[1-9]- Oxygen 25"
Line 14 = "Oxygen 25 MIDI - [1-9]"

I copied these lines from an allready existing script in bitwig.
I think that every operating system is naming MIDI-Devices a bit
differently, so this is an attempt to cover all types of naming schemes.

First you could comment in line 56, restart bitwig and check which
debug-output for moving module-wheel is generated (cc-value)

Cheers
Christian

On 04/21/2014 05:46 PM, freshold wrote:

Firstly, thank you very much for writing the Oxygen 25 script!

I've been using it and have a couple of questions:

  1. Is line 13 in the script supposed to be there?
  2. I can't seem to midi learn the Mod Wheel using this script? I know
    nothing about java and have tried to look through the code but can't
    figure out how to amend it to allow me to do this. I've been at it
    now for a few hours! It doesn't seem to make a difference what I do
    to lines 30 or 43, and I can't work out what other lines are
    relevant to this?

Can you help please?

Thanks in advance!

P.S. I've tried to experiment with creating basic scripts in order to
learn how this all works but they don't even appear in the controllers
menus. I know how to do my own version of lines 1 to 7 of your Oxygen 25
script correctly, so I'm guessing that Bitwig might have some sort of
validation whereby scripts that contain any errors in the code aren't
listed? My attempts more than likely contain errors, but I was hoping I
could use trial and error and learning from my mistakes/bugs to work
this out!

—
Reply to this email directly or view it on GitHub
#1.

Christian Heldt Mayflower GmbH
Gneisenaustraße 10/11 Tel.: +49 931 359 65 44
D-97074 Würzburg Fax : +49 931 359 65 28
christian.heldt@mayflower.de http://www.mayflower.de

Mayflower GmbH, Standort Würzburg
Firmensitz: Mannhardtstraße 6, 80538 München
Registergericht: Amtsgericht München, HRB 142039
Geschäftsführer: Gregor Streng, Björn Schotte,
Albrecht Günther, Johann-Peter Hartmann
—
Reply to this email directly or view it on GitHub.

cheldt commented

Hi,

yep that makes sense, but (there is always a but ;) )
the script currently assumes for all freely mappable controls (CC 02 - 109)
that the value range is between 0 and 128:

Line 104: userControls.getControl(index).set(data2, 128); <- here the
max value 128 is set

Maybe you have to use a different overload of "set()" or another
function, for mapping the modulation wheel.

Cheers
Christian

On 04/22/2014 10:42 AM, freshold wrote:

Hi,

Thanks for your reply.

How do I check which debug-output please?

If you mean to find out what CC number the mod wheel is, I checked that
using Logic X, and it's CC 1, and the pitch bend wheel is CC 0. So I
think I need CC 0 up to CC 109 to be freely mappable? However I can't
seem to successfully amend the script to allow this.

Does that make sense?

Regards,

Jonnie

On 22 Apr 2014, at 09:02, cheldt notifications@github.com wrote:

Hi

yep, line 13 is generating another naming scheme for autodetecting the
device.
There are 3 different versions:

Line 7 = "Oxygen 25"
Line 13 = "[1-9]- Oxygen 25"
Line 14 = "Oxygen 25 MIDI - [1-9]"

I copied these lines from an allready existing script in bitwig.
I think that every operating system is naming MIDI-Devices a bit
differently, so this is an attempt to cover all types of naming schemes.

First you could comment in line 56, restart bitwig and check which
debug-output for moving module-wheel is generated (cc-value)

Cheers
Christian

On 04/21/2014 05:46 PM, freshold wrote:

Firstly, thank you very much for writing the Oxygen 25 script!

I've been using it and have a couple of questions:

  1. Is line 13 in the script supposed to be there?
  2. I can't seem to midi learn the Mod Wheel using this script? I know
    nothing about java and have tried to look through the code but can't
    figure out how to amend it to allow me to do this. I've been at it
    now for a few hours! It doesn't seem to make a difference what I do
    to lines 30 or 43, and I can't work out what other lines are
    relevant to this?

Can you help please?

Thanks in advance!

P.S. I've tried to experiment with creating basic scripts in order to
learn how this all works but they don't even appear in the controllers
menus. I know how to do my own version of lines 1 to 7 of your
Oxygen 25
script correctly, so I'm guessing that Bitwig might have some sort of
validation whereby scripts that contain any errors in the code aren't
listed? My attempts more than likely contain errors, but I was hoping I
could use trial and error and learning from my mistakes/bugs to work
this out!

—
Reply to this email directly or view it on GitHub
#1.

Christian Heldt Mayflower GmbH
Gneisenaustraße 10/11 Tel.: +49 931 359 65 44
D-97074 Würzburg Fax : +49 931 359 65 28
christian.heldt@mayflower.de http://www.mayflower.de

Mayflower GmbH, Standort Würzburg
Firmensitz: Mannhardtstraße 6, 80538 München
Registergericht: Amtsgericht München, HRB 142039
Geschäftsführer: Gregor Streng, Björn Schotte,
Albrecht Günther, Johann-Peter Hartmann
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Christian Heldt Mayflower GmbH
Gneisenaustraße 10/11 Tel.: +49 931 359 65 44
D-97074 Würzburg Fax : +49 931 359 65 28
christian.heldt@mayflower.de http://www.mayflower.de

Mayflower GmbH, Standort Würzburg
Firmensitz: Mannhardtstraße 6, 80538 München
Registergericht: Amtsgericht München, HRB 142039
Geschäftsführer: Gregor Streng, Björn Schotte,
Albrecht Günther, Johann-Peter Hartmann

freshold commented

Hi,

Okay, thanks for this help.

The only problem is I have no knowledge about Java. I have very basic HTML knowledge from a few years ago, so know a little about coding, which is how I've figured out a tiny bit about this script, but I don't really understand what you have suggested.

I have found a script that allows me to freely map any of the controls including the mid wheel and pitch bend, but it doesn't have the transport controls working, or the track select or volume fader. Would it help if I sent you that script to look at?

Regards,

Jonnie

On 22 Apr 2014, at 13:10, cheldt notifications@github.com wrote:

Hi,

yep that makes sense, but (there is always a but ;) )
the script currently assumes for all freely mappable controls (CC 02 - 109)
that the value range is between 0 and 128:

Line 104: userControls.getControl(index).set(data2, 128); <- here the
max value 128 is set

Maybe you have to use a different overload of "set()" or another
function, for mapping the modulation wheel.

Cheers
Christian

On 04/22/2014 10:42 AM, freshold wrote:

Hi,

Thanks for your reply.

How do I check which debug-output please?

If you mean to find out what CC number the mod wheel is, I checked that
using Logic X, and it's CC 1, and the pitch bend wheel is CC 0. So I
think I need CC 0 up to CC 109 to be freely mappable? However I can't
seem to successfully amend the script to allow this.

Does that make sense?

Regards,

Jonnie

On 22 Apr 2014, at 09:02, cheldt notifications@github.com wrote:

Hi

yep, line 13 is generating another naming scheme for autodetecting the
device.
There are 3 different versions:

Line 7 = "Oxygen 25"
Line 13 = "[1-9]- Oxygen 25"
Line 14 = "Oxygen 25 MIDI - [1-9]"

I copied these lines from an allready existing script in bitwig.
I think that every operating system is naming MIDI-Devices a bit
differently, so this is an attempt to cover all types of naming schemes.

First you could comment in line 56, restart bitwig and check which
debug-output for moving module-wheel is generated (cc-value)

Cheers
Christian

On 04/21/2014 05:46 PM, freshold wrote:

Firstly, thank you very much for writing the Oxygen 25 script!

I've been using it and have a couple of questions:

  1. Is line 13 in the script supposed to be there?
  2. I can't seem to midi learn the Mod Wheel using this script? I know
    nothing about java and have tried to look through the code but can't
    figure out how to amend it to allow me to do this. I've been at it
    now for a few hours! It doesn't seem to make a difference what I do
    to lines 30 or 43, and I can't work out what other lines are
    relevant to this?

Can you help please?

Thanks in advance!

P.S. I've tried to experiment with creating basic scripts in order to
learn how this all works but they don't even appear in the controllers
menus. I know how to do my own version of lines 1 to 7 of your
Oxygen 25
script correctly, so I'm guessing that Bitwig might have some sort of
validation whereby scripts that contain any errors in the code aren't
listed? My attempts more than likely contain errors, but I was hoping I
could use trial and error and learning from my mistakes/bugs to work
this out!

—
Reply to this email directly or view it on GitHub
#1.

Christian Heldt Mayflower GmbH
Gneisenaustraße 10/11 Tel.: +49 931 359 65 44
D-97074 Würzburg Fax : +49 931 359 65 28
christian.heldt@mayflower.de http://www.mayflower.de

Mayflower GmbH, Standort Würzburg
Firmensitz: Mannhardtstraße 6, 80538 München
Registergericht: Amtsgericht München, HRB 142039
Geschäftsführer: Gregor Streng, Björn Schotte,
Albrecht Günther, Johann-Peter Hartmann
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Christian Heldt Mayflower GmbH
Gneisenaustraße 10/11 Tel.: +49 931 359 65 44
D-97074 Würzburg Fax : +49 931 359 65 28
christian.heldt@mayflower.de http://www.mayflower.de

Mayflower GmbH, Standort Würzburg
Firmensitz: Mannhardtstraße 6, 80538 München
Registergericht: Amtsgericht München, HRB 142039
Geschäftsführer: Gregor Streng, Björn Schotte,
Albrecht Günther, Johann-Peter Hartmann
—
Reply to this email directly or view it on GitHub.

freshold commented

Also, from your first reply:

Line 7 = "Oxygen 25"
Line 13 = "[1-9]- Oxygen 25"
Line 14 = "Oxygen 25 MIDI - [1-9]"

Line 13 isn't "[1-9]- Oxygen 25", it = host.addDeviceNameBasedDiscoveryPair([name], [name]);

Line 12 = "[1-9]- Oxygen 25"

So, is Line 13 supposed to be there? It looks like a blank version of Line 14.

cheldt commented

There is a variable called "name", which is filled in line 12.

var name = i.toString() + "- Oxygen 25";

  • "i" is set from 1 to 9 inside the for() block.
  • "+" concatanates i and "- Oxygen 25"
    result is e.g. "1- Oxygen 25"

The variable is later used in line 13.

On 04/22/2014 04:21 PM, freshold wrote:

Also, from your first reply:

Line 7 = "Oxygen 25"
Line 13 = "[1-9]- Oxygen 25"
Line 14 = "Oxygen 25 MIDI - [1-9]"

Line 13 isn't "[1-9]- Oxygen 25", it =
host.addDeviceNameBasedDiscoveryPair([name], [name]);

Line 12 = "[1-9]- Oxygen 25"

So, is Line 13 supposed to be there? It looks like a blank version of
Line 14.

—
Reply to this email directly or view it on GitHub
#1 (comment).