Bitwig

zotune · Post by **zotune** » Thu Dec 18, 2014 1:20 am

Usually when recording, the engine just crashes. I am using Generic Midi Device as it is not officially supported.

I am completely unable to get Bitwig going again unless I turn Axiom completely off or wait 5 minutes or so. The engine on icon just loops endlessly. Works fine with Cubase using the same setup.

turbo_kev · Post by **turbo_kev** » Thu Dec 18, 2014 9:32 pm

Hi I use the axiom pro 49 in generic mode with no problems
the version of bitwig I use is 113 RC 1

I am just busy mapping the faders and knobs
Oh what joy. I hope some clever sod writes a script
to map everything else
cheers
kevin

zotune · Post by **zotune** » Sun Dec 21, 2014 5:29 pm

Everytime I record something with MIDI. It crashes the audio engine.

Restart works when using Windows Drivers from Axiom Pro, but the synth remains dead (nothing happens unless I restart Bitwig and Axiom).

Using M-Audio's own driver causes me not to be able to reopen the project until it cools down for 5 minutes.

zotune · Post by **zotune** » Tue Dec 30, 2014 4:24 am

Report I sent to M-Audio support:

Bitwig crashes when recording with this keyboard. Your Axiom 1.1.1 Driver 5.10.0.6002 crashes the entire Bitwig audio engine, and I'm unable to reopen the music project in Bitwig without unplugging the keyboard. If I use the Windows Drivers, only the audio engine crashes, and I can reopen the project - but I still lose work upon recording.

Please look into this, or I have to switch to another manufacturer. I know it's your driver for the following reasons:
1. Bitwig never crashes without Axiom Pro 49 connected
2. Bitwig crashes differently when using the "Windows Default Driver" instead of "Axiom 1.1.1 Driver 5.10.0.6002".
3. I'm unable to reopen the project with "Axiom 1.1.1 Driver 5.10.0.600" (it just hangs forever, and I have to restart my pc or unplug Axiom Pro 49). With the WIndows Default driver however, it reopens the project as expected (still crashes in the first place though, and the Axiom Pro 49 still has to be powered off and on again in order to record in Bitwig. I reckon your driver is more or less the same only it automatically restarts the driver if it crashes).

Steps to reproduce:
1. Install your Axiom 1.1.1 Driver 5.10.0.6002 on a Windows 7 machine (x64 SP1)
2. Download Bitwig Studio
3. Put a debug on your drivers
4. Record a lot of midi audio

What is expected:
MIDI to be recorded in Bitwig music project

What actually happens:
Bitwig Audio engine crashes

turbo_kev · Post by **turbo_kev** » Tue Dec 30, 2014 8:48 pm

Hi like I said before im ok with my axiom pro 49, no probs at all
apart from having to map the controllers myself. it works perfectly
im on win 7 ultimate 64 bit and I have the keyboard in GMPATCH setting

something strange going on at your end

zotune · Post by **zotune** » Wed Dec 31, 2014 4:05 am

Is there any way to reset the keyboard? How do I set it in GMPATCH setting?

turbo_kev · Post by **turbo_kev** » Wed Feb 25, 2015 1:26 pm

just press the LOAD button and then use the + - keys to scroll through the patches

it works for me no probs but you wont be able to use the transport controls, until some nice chap or chapes writes a script for it

but you can use midi learn from bit wig to map the knobs and faders

cheers
kev

turbo_kev · Post by **turbo_kev** » Sat Feb 28, 2015 5:11 pm

I just checked and I have driver version 5.10.0.5134

Bitwig

KVR Audio

Axiom Pro 49 crashes Bitwig