Bitwig

gravy · Post by **gravy** » Sat Oct 11, 2014 10:34 am

Line 365
cursorTrack.selectNext();

Line 370
cursorTrack.selectPrevious();

solves problem 3 in my post, 5 up from this one.

I was wrong. The correct procedure is to use shift, octave transpose buttons which already perform the function I thought didn't work. Sorry, didn't work that out earlier.

It seems the intention of the original:
trackBank.scrollTracksPageUp();
is to move all the mixer controls down eight tracks at a time.

This functions ok.

gravy · Post by **gravy** » Sat Oct 11, 2014 11:28 am

With the E2 rotary encoder the issue is this one here on Line 99: "B?01??"

Without it E2 functions but no mod wheel. With it, the reverse.

If I change it to something else like "B201??" (or probably anything else then both work but obviously I am messing with something I don't understand... Will try now to see what this note input is meant to be picking up.

ThomasHelzle · Post by **ThomasHelzle** » Sat Oct 11, 2014 12:53 pm

As I said, I didn't write this script myself and initially thought I could offer you a quick fix - which didn't work out so well

- but at least I now understand most of what the script does.
I also think the docs are very confusing, it took me a while to understand what's what. Like you, I missed several things initially.
I hope to be able to continue with the overhaul next week.

Beat Clock works fine for me on Linux with the arpeggiator.

Cheers,

Tom

P.S. the thread turned a bit wild with all this back and fourth. Could you make one post with a list of problems you still see (and edit it when necessary) so I can work from a clean slate? Thanks!

gravy · Post by **gravy** » Sat Oct 11, 2014 3:58 pm

Yeah - sorry about that - will do.

It sounds like you're not having the errors on lines 96 and 100?

Graham

ThomasHelzle · Post by **ThomasHelzle** » Sat Oct 11, 2014 4:06 pm

Did you remove the controller from preferences and re-insert it? Does it show two input dropdowns and one output?

Cheers,

Tom

gravy · Post by **gravy** » Sun Oct 12, 2014 12:58 am

Started bitwig and removed impulse 25 device, quit bitwig.

Deleted the old script and fresh download to be sure.

Start bitwig, autodetect. Inputs are Impulse Midi 1 and Impulse Midi 2. I select 1 only. Output is Impulse Midi 1 only.

The keyboard does not function. It is not locked up though. The script console shows a problem straight after Called init():
Wrapped.java.lang.IndexOutofBoundsException: Index 1, Size 1 (Impulse, control.js#96).

Tried the same procedure with Impulse Midi 2 as the input . Result is the same.

ThomasHelzle · Post by **ThomasHelzle** » Sun Oct 12, 2014 6:39 am

You need to select both inputs for now, Impulse Midi 1 in the first input slot, Impulse Midi 2 in the second input slot (Autodetection for Linux will come

). Otherwise the second input is missing and you get that error.

As I said, this script is beta and not finished yet.

Cheers,

Tom

gravy · Post by **gravy** » Sun Oct 12, 2014 8:03 am

Ahh... Discovered something new there. For me, the second input slot is only available if I manually add the control script, rather than autodetect.

I will create the new thread shortly.

ThomasHelzle · Post by **ThomasHelzle** » Sun Oct 12, 2014 8:33 am

Yeah, autodetection on Linux is not finished yet, sorry.

But there is still a random element in this script or the controller that gives me erratic behaviour.
Each time I work on it it seems to behave differently. The pads were sending on a different channel from the keys initially, now they send on the same channel as the keys...

This is much more work than anticipated and will have to wait until I have more time.
Again, I'm sorry, I'm pretty much baffled by this thing.

Cheers,

Tom

gravy · Post by **gravy** » Sun Oct 12, 2014 9:02 am

No apologies necessary Tom. You've done quick work and it would be unrealistic to think you could make Impulse 25 scripting your full time occupation. Come back to it when you're ready.

Thanks heaps for the help so far and the script is already much improved for my own needs.

I just hit enter on the consolidating thread:

Edit - fixed link - hopefully

http://www.kvraudio.com/forum/viewtopic ... g#p5924368

krankyone · Post by **krankyone** » Sun Nov 30, 2014 2:21 am

The mod wheel issues are also happening for me in Ableton Live. My solution was to set the default channel for the keyboard from 1 to 3 so that everything matches the mod wheel on channel 3. I usually set a track channel to "all." which is why I never saw this before. I only stumbled onto it when I wanted to direct the drum pads to a vst using channel 2, and everything else to another vst using channel 1. When I did this the modwheel stopped being received by the vst.

laz · Post by **laz** » Tue Aug 07, 2018 9:42 pm

I know its an old threat but i will answer MAYBE for someone else having troubles.

1st of all you can change the parameter of the modwheel like on sliders,buttons,rotary and pads.

Step 1.
Press control on your Impulse.
Step 2.
Move your modwheel and on the screen you what type of message it sends. CC must be shown. If NOT the you can change this setting with DATA rotary.
Step 3.
Then press the (+) button and it shows the CC number. 1 is the default for modwheel. If NOT the you can change this setting with DATA rotary.
Step 4.
Press again the (+) button and it shows the MAX value. Set it as desired.
Step 5.
Press again the (+) button and it shows the MIN value. Set it as desired.
Step 6.
Press again the (+) button and HERE is the Midi channel.Set it as desired.

Hope this helps other people too.

Bitwig

KVR Audio

novation impulse modwheel on channel 3 rather than channel 1