I am afraid not. We are able to convert Hog II showfiles to Hog III however effects, macros and programming on custom fixtures does not convert i ma afraid.
Well, just no midi notes to control fader... all the other midi functions are there, it's perfect... But for a show, the guy at keyboards, drum machine and samplers control intensity level of fader through midi notes. And I want to test the hog3 on this show. So Cat West of High End Systems have a solution, creat a comment macro in a cuelist that tells Fader X to crossfade to Y% ... So, no worry, just a work of adaptation. except this, the hog3 has really what I wanted to see appearing more than on the hog2
Is there anything that you would like to see added or handled differently than it was in Hog 2?
Thanks.
MIDI-IN Support for MIDI-IN was great on the Hog2, I was able to get the desk connected to most media-control-units I got in touch with that were able to send MIDI. MIDI-notes for fader values were also a nice thing I used every now and then. A possibility to send a fader value with just one MIDI-note instead of sending 2 notes would be great. I've had to build weird setups with a laptop with MIDI-IN and MIDI-OUT to convert MIDI-messages in situations when the sender of the MIDI-Notes needed to be able to control fader intensities without somebody changing cues in the desk - some systems can only send one note for each event. Since this function would block a lot of MIDI-notes just for the faders, you should maybe map the control of the faders on a seperate device-id and add an option in the control panel to enable this function since some people might get confused as they are used to have the desk listening to all device-ids by default in the past.
MIDI-OUT I was triggering Arkaos a lot out of my cuelists in the Hog2 to run the video in sync to my show (programming one cuelist for each song). It was a lot of work to type all the notes in the comment-fields. It would be nice if there were some kind of shortcuts to trigger MIDI-Notes. Like "ON8" and "OFF8" instead of typing MSh1/9008FF and MSh1/9108FF in situations when you only have one MIDI-Out device. A possibility to see, what notes are triggered within a cuelist and when they are released would also be helpful. I know that some other cuelist on the desk might also send a MIDI-Note, but such a view on only one cuelist would help a lot to find typos and forgotten note-off-messages when you are programming a show that is running off of one list.
Hello, For midi-in… it’s really like Jan. On hog2 I use midi-notes to control fader values, and actually, I have a laptop to transform a solo midi note in a ctrl and a midi note. So having juste one note to control the fader value could be great. (Jan, happy to see that I am not the only one to do it). And like on the hog2, to be able to control all the fader even without the wings and the extensions. Well, it is the first striking thing which comes to my mind I don’t really use the midi-out.
Tom, For MIDI OUt you should have something in the logs from a long time ago where I asked to have something akin to a MIDI Notes fixture type, something that could actually be "cued". Is that still in there?
hmm.. being able to have a "dummy midi-note lamp" to control midi-notes like a gobo-wheel sound like an interesting idea...
But how should that work in detail? We have 127 notes and each has a velocity... a fixture with 127 channels? Or a fixture with just one channel: velocity. You could patch as many fixtures as midi-notes are needed. that sounds better! Might be a very nice feature when you are triggering external hardware/prorams like Arkaos. As I think back of typing all those notes in comment boxes, a simple "901@127" would have saved a lot of time Jan
I really like your idea of a cueable MIDI message fixture. I'm not seeing a bug currently open, so I want to get some more details from you and then I'll open a new feature request.
I assume we'd want to add 2 fixtures. One to send MIDI continuous controller data and one to send MIDI notes.
Continuous controllers send 2 pieces of information. The first is the Controller Number and the second is the Value. I think one possible implementation would be to have the controller number on one wheel and the value on another. We would also want a slot for transmit enable / disable. If the value changes and transmit is enabled, the value is transmitted. If transmit changes from disabled to enabled, the current value would be transmitted.
MIDI notes are a bit more involved. There are both note-on and note-off messages. Note-on messages contain the MIDI channel number, the key number, and the velocity. Can you give me an idea of what information you need for the devices you're working with? I'm not sure how much of this we need to implement and I can see things getting complex pretty quickly.
Let me know what you think of this. I'm sure we can come up with something that would work.
@tom To keep it simple but not loose any functionality: define that 0 is not off, 1 to 128 is note on and the velocity. When you "patch" the fixture, you define what note (key) and what MIDI channel it is. Once it's patched, the behaviour should be just like a desk channel as I wrote earlier: 901@0 is note off, 901@56 is not on with a velocity of 55.
If I needed 70 keys I'd just patch 70 of those "MIDI note fixtures" to keys 0 to 69 and trigger my visuals this way - can't think of anything easier, it would just be perfect for Arkaos. Other people need to give input on other software...
I was thinking it would be easiest to come up with a fixture that wouldn't have to be patched. This would keep us from having to completely re-work the patch screen to add a "MIDI Universe" patch system.
Being able to cue the triggering of MIDI events makes logical sense to me. Having to patch these MIDI fixtures seems a bit confusing. We want to make sure that we implement features in a way that is logical and easy for users to understand.
