Notifications
Clear all

Vixen 3 MIDI input

12 Posts
4 Users
0 Reactions
24.6 K Views
Posts: 602
Guest
(@bwinter)
Honorable Member
Joined: 10 years ago

Yeah, I think some of the confusion is the workflows between vixen v xlights, and the fact that I have no concept of vixen, so what I'm saying may not translate over well.

Using my example in Carol of the Bells (to make things simpler), I assigned each icicle to a specific midi note. And that's one single effect on each icicle over the duration of the entire sequence. However, this effect can ONLY turn the icicle on/off based off the note in the midi-file. What would be beneficial, would be the option to define exactly what effect is played at each note. Instead of just on/off (for each icicle) at the appropriate note, I wish I could have had the ability to assign the effect (that is always applied to that icicle based off the note): either do a drop/chase-effect or a fade-to-off effect (which would be based off the duration of the note).

So I wouldn't necessarily want a different effect played at each note--just the ability to select WHICH effect is played (at all the notes). In xlights, I can't simply "swap-out" the effect. I had to use the midi-applied effect to see where the on/off is, and manually place my drop-effect over each note (for all the notes). This was the time-consuming part (and the part that prevented me from being able to go back and make any changes to the original midi file).

And true, most midi-files won't actually match the recorded audio file. However, it was a pretty simple task for me to go into a midi-editor, and make the minor tweaks necessary to align the midi and the recorded file. And I even added some additional notes that weren't in the original midi file, but knew that I wanted in my sequence--I was basically using a midi-editor to edit my sequence (and it really was a lot easier than trying to edit in xlights, other than the fact that each note was limited to on/off).


Reply
jchuchla
Posts: 8698
Topic starter
(@jchuchla)
Illustrious Member
Joined: 15 years ago

BTW, did you ever answer in the other thread which version of carol of the bells that was? (artist, album, name?) I haven't been able to find it.

Oh yes, this would be a completely different workflow. In Vixen, each note would be its own effect. We'd be creating some sort of mapping interface to assign an element or group to each note. (Vixen group/element = xLights Model/Node) If you wanted a whole icicle to turn on as a whole you'd use a pulse effect. If you wanted the icicle to drip, you'd use a chase effect. So if you wanted all of the "notes" on a whole verse, or a 16 bar section or whatever, you'd just select those effects over that timespan and swap them out to another effect. That's all regular existing Vixen stuff. Only the creation of the effects from midi would be new.

Quite honestly, after seeing your sequences, i'm surprised you did that in xLights. Your sequences look more like Vixen sequences than xLights sequences.


Reply
Posts: 602
Guest
(@bwinter)
Honorable Member
Joined: 10 years ago

Carol Of the Bells, George Winston, December (album)

Yeah, for that sequence, I was really wondering how other sequencing software would handle what I was wanting to do. And quiet honestly, it wasn't *that* time-consuming to drop in all my effects, using the midi-effect as a guide. It's just that I couldn't alter the midi file once I started (or if I did, I had to be very careful about what I changed).

I'll be curious to see how it gets implemented in Vixen, and to hear what other methods people could conceive using a midi file--especially if you're able to utilize additional data in the file.

Right now, I think xlights piano-effect (the only one I've been able to find that can use a midi-file) is really geared to displaying a piano on a matrix. The way I used it wasn't the way it was intended to be used. Basically, that whole sequence was just an experiment--all the way from making the icicles (economical, waterproof, diffuse), to the wiring schematic (how to simplify a wiring schematic that works for random placement in a tree), to how to adapt a midi file with a recorded audio file and get the lights sequenced the way I wanted. And it all only took a week.


Reply
jchuchla
Posts: 8698
Topic starter
(@jchuchla)
Illustrious Member
Joined: 15 years ago

Aah yes, George Winston. I hadn't thought to search that one.

i would think that we'd see more use from recording live midi input rather than reading files. I know people have asked for that. I could see people using a midi keyboard or other controller and "playing their effects into the sequence"

On the Vixen side, we try pretty hard to keep our mechanisms as abstract as possible so they can be as flexible as possible to fit many use cases. That's why we like to hear all the ideas before we start working on it.


Reply
Posts: 1
(@jezwold)
New Member
Joined: 11 years ago

Hi Jon,

This is something I've been interested in since learning about Vixen. I've been keeping an eye on http://bugs.vixenlights.com/browse/VIX-411 and even had a go messing around with the Live context and a MIDI library in my Git fork. To be honest I was a little overwhelmed seeing the Vixen source as a hobbyist developer and haven't made much progress/had the time recently.

I have a Novation Launchpad Pro (a 10x10 RGB MIDI grid controller) and a Novation Launch Control (16 MIDI encoder knobs plus some buttons) I'd like to use with Vixen. A common feature in many audio applications is 'MIDI learn' whereby a button is clicked (or global hotkey) to active learn mode, then a control on the UI is selected, followed by pressing a MIDI note or turning an encoder and then finally exit learn mode. The MIDI control is then linked to that UI control (which could be highlighted to indicate it is mapped). There is also a screen to edit/remove mappings.

To play live the way I imagined it could work is a slightly modified version of the sequencer, effect blocks could drawn on the timeline as normal and then be triggered on a MIDI event (using the learn mode described above), it should be possible to trigger multiple effect blocks at once. Combine that with being able to adjust the effect parameters in real-time with other MIDI encoders or notes and you have a whole lot of flexibility.

To record a live performance you could write a MIDI file of the incoming events which could trigger the effects again on subsequent playback, in fact you could make it work like a loop pedal where additional MIDI data is merged in each time you run through, tweaking parameters and building up the sequence. After completing a sequence in this manner you could then render your live sequence to a regular timeline based Vixen sequence where further adjustments could be made. I can't see it being easy to go back the other way, but would that really be needed?

In a separate project of mine I'm using the RGB lights on the Launchpad to display a preview of what the lights are doing, much like the existing built in preview window. I plan to have a 'pallet mode' whereby I can quickly select a colour from the Launchpad, it could also be used render gradients/brightness curves/effect previews in Vixen.

Happy to clarify my rambling or help in any way, thanks for the great work you guys do!

Cheers

Jez


Reply
Page 2 / 3
Share: