compatibility usine 5.50

[headphoner]

Hi,

all modules from 5.25 will be compatible with 5.50?

Do you plan a date realease for 5.50 version?

Have a nice day

[senso]

fully compatible.
the V5.5 will be out this week!

[grego mondo]

Great !!

[La Tenaille]

3 hours left
I'm joking, take it easy

[runagate]

fully compatible.
the V5.5 will be out this week!

I have to admit I thought it, too, though I haven't the slightest idea what new features might be added.

I've got a couple of new input controllers,
(http://glovepie.org/blog/2010/01/08/hap ... -and-feel/)
(http://www.youtube.com/watch?v=0JtkoAH73n0)
(http://www.youtube.com/watch?v=2Uv9dWvC ... r_embedded)
a projected capacitive touch, ITO film and 3D touchless/volumetric HID developer kits wending their way through the mail and getting ready to be used in prototyping my giant post-midi/VST multimodal interface project I've spend a 16-month long hiatus away from making music to work continuously on, and Usine will be invaluable in routing/filtering/assigning all of that craziness to VST parameters and suchlike. I also still help that the Usine SDK will allow prototyping new-standard modules right inside Usine for a test environment.

[nay-seven]

cool project !
about the rock band 3 guitar controller, do you have it yet..?
i think about it since a while, cause guitar was my first instrument and i have some question about this
a simple midi cable is enought , right..?
how do you receive the midi information for each strings..? all in the same time or each strings on separate canal..? i mean i was used to play in DADGAD is this possible with it..?

[nay-seven]

ok, so I've found the informations :

so for those who want to know about the rock band guitar 3:

Octave: Increment and decrement octave are the left and right action buttons (X and B on Xbox).

Program change: Increment and decrement are the top and bottom action buttons (that’s Y and A on Xbox). Transmits on channels 1-6. No, really. There’s a program change message implemented on this thing. The default is 28, the patch for a clean electric guitar in General MIDI.

D-pad buttons switch functions for the pedal, from foot controller to channel volume to expression.

Pedals: Connect an analog pedal, and you can use continuous expression or volume. Connect a digital stomp (that is, one that’s either on or off, like the bass drum pedal), and you send a damper pedal / sustain message.

Panic: Mercifully, there’s an all notes off command issued if you press the Xbox Back, Start, and D-Pad right at the same time. (Hmmm – feels like ctrl-alt-del.)

MIDI channel: By default, the guitar transmits on channels 1-6 — that’s in order to transmit strings separately. Each of the six strings is a different channel.

Accelerometer transmits Modulation on the X axis, Expression on the Y axis, and Pitch Bend on the Z axis, and each can be toggled independently with shift (the Start key) + B, A, and X, respectively. (That’s a good thing, as controlling all three at once would be a little messy.)

Frets and strings: Here’s the tricky part, because you’re strumming something rather than playing a MIDI keyboard. There are two modes:

* “Strum mode.” Hold a fret, then strum the string. The note is sent when – and only when – you strum. The pitch is set by whichever fret is closest. That note is held until you change a fret.
* “Synth mode.” Strumming a string or changing frets will generate a note – meaning, if you like, you can use that fretboard as a 102-key keyboard. (Microtonal fans, go nuts.) Here’s the odd part, though – you need the strum to set velocity, so whichever strum you’ve last strummed is your current velocity. While it’s called “synth” mode, this is the only mode that allows hammer-ons and pull-offs.

[runagate]

I can't tell you any more about the guitar because the only actual 5-din MIDI-to-PC I have is on my (much-damned) CME VX5 which gives complete nonsense MIDI messages to Usine (and any other MIDI-In tracing app I've tried, too)

http://www.alsa-project.org/main/index. ... .15_detail

usb-audio: fix parsing of SysEx messages from CME keyboards
When CME keyboards send a SysEx message (e.g. master volume), the USB
packet uses a format different from the standard format. Parsing this
packet according to the specification corrupts the SysEx message itself
and can cause the following MIDI messages to be misinterpreted, too.
This patch adds a workaround for this case.

So at the moment I'm concentrating on 3D proximity sensors, multi-touch PCAP and ITO film, that damned Synaptics ClearPad that I managed to get quite some time ago now that I can reasonably expect to get its i2c/SMBus interface sussed into USB HID/Win7 Touch API data, and a bunch of other technical mumbojumbo. I'd rather be jammin'