The All In One Source Bitwig Information & Speculation Thread

[LawrenceF]

What a difference a day makes!

[pdxindy]

What a difference a day makes!

One day after Bitwig release...

[ThomasHelzle]

....I use rtpMidi too and it works with Bitwig and my Android Phone using "TouchDAW". With this, TouchDAW acts as a Mackie MCU Pro. Quite nice actually

Let me check loop Midi and see if it works with my script, if yes I'll release it on the Bitwig Resources Thread so you can see if it solves your problem even if a bit more convoluted than desired. Otherwise check out CopperLan, since it supports networking too... I never tried that part though.

Cheers,

Tom

Hmmmm...so is this "TouchDAW" MIDI over LAN from your phone? Probably WIFI but if so, then I should be able to get MIDI over LAN with the two computers. How is this set up on your system? Sounds interesting.

Actually Thomas, before you go to a lot of trouble, I haven't verified loopMIDI will not work...Like I said previously, I didn't have a lot of time to investigate.

With rptMIDI, BWS recognizes the port but will not send/receive data. I think I read somewhere it does not support MIDI clock.

I'm hopeful to have greater opportunity to mess with things over the weekend and so don't want you to waste your time. I'll have to let you know my findings.

Thanks!

Happy Musiking!
dsan

I uploaded the Controller Script to the Bitwig Ressources Thread here:
http://www.kvraudio.com/forum/viewtopic ... 6#p5693456

It is a generic Script one can use with every kind of keyboard or Midi Input in case the Midi Channels need to be available separately like this:



I originally wrote it for the first two CopperLan virtual Channels ("VMidi 1" and "VMidi 2") but it works with any kind of Midi Device.

I hope this is helpful for somebody

Cheers,

Tom

[hibidy]

What a difference a day makes!

One day after Bitwig release...

I'm pretty sure that is the one in Fresno.

[chilledpanda]

As I understand, Java is a memory hog, and you have to program it to prefection to make it almost as fast as C etc.

And one has to update Java on a regular basis, right? I guess I still have it disabled on my computer, I never see that little symbol anymore...

They more than likely have their own build/flavour of java runtime so it's not reliant on a user having a specific version installed, as will be the javascript api for it's plugins. The java will be only used for light weight processing, the gui etc.

The low level audio processing engine will be at minimum c/c++.

[dsan@mail.com]

........Question / Observation: Try this below, if you get a chance DSan...

Run some midi tracks with VI's and then stop the project and change the ASIO buffer size. When I did that here some of the Kontakt samples unloaded and don't reload. It's running fine here with about 10 instances of Kontakt 4 at 128 samples but that little thing was a momentary "gotcha", I had to reload the samples on about 4 tracks after I changed the ASIO buffer size.

I assume (it happened kinda fast so dunno) that when you turn off the audio engine it unloads the samples?

No point in me shouting bug if it's not happening to anyone else.

LawrenceF - yes, same here. 7 tracks consisting of Alchemy, Omnisphere, AD and 4 Kontakt 5 each with a KH Spotlight Strings instrument.

Played my clips. Stopped the clips. Opened preferences and changed buffer from 256 to 128.

This caused the audio engine to stop.

On restart of audio engine, Alchemy and the K5's had to reload their samples. Got an error with Alchemy that it could not find the library so had to point it to the library again (had to do this the first time so thought it would be good going forward. Guess not).

Bummer. The only good to come out of it is BWS seems to be fine at 128 samples. Not sure why I did not get the distortion that I had first gotten at 256 (that improved too after a bit of use).

Then, instead of changing the buffer settings I clicked the audio engine off and when turning it back on the same VI's had to reload their samples, and once again, Alchemy could not find the library.

It appears this situation is connected to the audio engine then.

So now I'm going to see if I can lower my sample rate another notch. Wish me luck

Happy Musiking!
dsan

[ras.s]

What a difference a day makes!

:hihi:

[dsan@mail.com]

.....I uploaded the Controller Script to the Bitwig Ressources Thread here:
http://www.kvraudio.com/forum/viewtopic ... 6#p5693456

It is a generic Script one can use with every kind of keyboard or Midi Input in case the Midi Channels need to be available separately like this:



I originally wrote it for the first two CopperLan virtual Channels ("VMidi 1" and "VMidi 2") but it works with any kind of Midi Device.

I hope this is helpful for somebody

Cheers,

Tom

Very nifty Thomas, Thank You

Works like a charm!

I am hopeful though the Bitwig guys get the missing MIDI functions implemented as soon as possible.

To be able to rename MIDI devices in a recognizable form will be much better. At this time I have 6 devices all named "MIDI Keyboard" and have no idea which is which (until I get used to how they are arranged in prefs).

More importantly to be able to send MIDI. All my generic devices have no "Out" options, which I do not understand.

Thanks again for your help!

Happy Musiking!
dsan

[dsan@mail.com]

@hibidy - Thanks for the good will wishes yesterday. Sorry I didn't have the chance to get back to you.

You may be happy to know - NOT ONE CRASH SO FAR!!!

And have been able to load much more VI than in Live before a BOOM!

Yet, there are some other issues I may not be able to get beyond. MIDI implementation does not seem to be BWS's best forte.

What it does it does well though! So far

Happy Musiking!
dsan

[hibidy]

@hibidy - Thanks for the good will wishes yesterday. Sorry I didn't have the chance to get back to you.

You may be happy to know - NOT ONE CRASH SO FAR!!!

And have been able to load much more VI than in Live before a BOOM!

Yet, there are some other issues I may not be able to get beyond. MIDI implementation does not seem to be BWS's best forte.

What it does it does well though! So far

Happy Musiking!
dsan

I'm glad to hear it. Amidst all the hyperbole yesterday it was VERY DIFFICULT to gauge where people are with it.

[ThomasHelzle]

Got an error with Alchemy that it could not find the library so had to point it to the library again (had to do this the first time so thought it would be good going forward. Guess not).

Happy Musiking!
dsan

No, that is actually a bug in Alchemy with Bitwig. I had high hopes that Camel Audio would be able to fix it before the release, but so far I haven't heard of them.
Alchemy never finds it's data folder and asks for it FOR EACH AND EVERY INSTANCE
So three Alchemy instances in a project and when you load it you get asked three times for the data folder ...
It is my impression that their way of finding the data is borked somehow, since Alchemy asks me in every app once for it. Normally it should only ask once on installation, since there is a link to the files in the plugin folder then...

Hopefully it's an easy fix.

Cheers,

Tom

[Echoes in the Attic]

I loaded Maschine into Bitwig and it looked like it was all the same window. Like the interface just continued and it was all one. I call it Maschitwig.

[ThomasHelzle]

.....I uploaded the Controller Script to the Bitwig Ressources Thread here:
http://www.kvraudio.com/forum/viewtopic ... 6#p5693456

It is a generic Script one can use with every kind of keyboard or Midi Input in case the Midi Channels need to be available separately like this:



I originally wrote it for the first two CopperLan virtual Channels ("VMidi 1" and "VMidi 2") but it works with any kind of Midi Device.

I hope this is helpful for somebody

Cheers,

Tom

Very nifty Thomas, Thank You

Works like a charm!

I am hopeful though the Bitwig guys get the missing MIDI functions implemented as soon as possible.

To be able to rename MIDI devices in a recognizable form will be much better. At this time I have 6 devices all named "MIDI Keyboard" and have no idea which is which (until I get used to how they are arranged in prefs).

More importantly to be able to send MIDI. All my generic devices have no "Out" options, which I do not understand.

Thanks again for your help!

Happy Musiking!
dsan

Yeah, I was confused by that as well, but if you load an external Instrument device in a chain, you see all the outputs that are available on your system. So it doesn't matter much if there is an output in the Controller for mere keyboards.

But to enable the output is supersimple for a controller if you should want to have it:

There is a line at the beginning of the script that reads:

Code: Select all

host.defineMidiPorts(1, 0);

If you change that to:

Code: Select all

host.defineMidiPorts(1, 1);

You also have an output.
Basically the first number is the number of inputs and the second is the number of outputs...

Cheers,

Tom

[hibidy]

@echos: haha!

[codec17]

I loaded Maschine into Bitwig and it looked like it was all the same window. Like the interface just continued and it was all one. I call it Maschitwig.

As vst? Cause it doesn,t appear in my vst list... also short circuit2 sampler... Rest of NI appears in the list...