![]() Sometimes they speak during the moves from one part of the stage to the other so i don't want the sound to change in one step, i need a fade. So when an actor move from one part of the stage to another (which is not to often since basically there is 3 parts on the stage and mostly when they go from one to the other, they stay there for a while) i need the sound to follow them. If he's on the center, i need the sound to come from the center speaker. If the actor 1 is on the left, i want the sound to come mainly from the left speaker. ![]() I need the sound of each actors coming from the place he is. I have 2 actors on stage with lavalier microphones and 3 speakers : left,center and right. > Micpool : Here is the description of what i need to be done. Knowing the practical outcome the poster wishes to achieve is easier than tackling everything as a pure engineering problem. Often there is a much simpler method of achieving something which will have the same subjective result for an audience than a solution that is more complete and universally applicable in engineering terms. Knowing why someone wants to do what they are just describing as a sequence of engineering events is often part of finding solutions in applying technology for artistic ends. I think there is a big difference between an objective description of the way you want 2 program's to interact with each other and a description of what you are trying to achieve e.g increase the level of a mic from its current level by 10dB when a. Is there another (simpler) way to achieve what i want? ![]() That's not very practical since i have to track every fader's positions to be sure that the start position is always the same as the end position of the previous cue. Right now, i use control change to do a time fade to a new fader position but i also have to set the start position of the fader. I need to create a fade from the last position of one fader to a new position. What i want is control some mikes's faders i have in MainStage. > I want to control MainStage with Qlab using Midi. > If you go back to Patrick's first post on the thread you will see what he is trying to do: On Friday, Ap3:04:28 PM UTC+1, Rich Walsh wrote: I can't see a way of doing that with MIDI.īy the way, it would be a lot easier to answer questions if you didn't delete everything that had gone before in the thread each time. I guess you're actually trying to do what absolute Fade Cues do – which is go to a destination from any given start point. In Live you can set the mode to "Relative (Signed Bit)", which will make the fader jump up in steps each time you send the CC 127, and down for CC 0 – but this still isn't going to do what you want. This is the only mechanism I can currently think of that stores just final value, not the journey to that value too (which MIDI CC must). Even with a Yamaha mixing desk the best you could hope for is a bunch of highly targeted scene memories that do fades to specific levels on specific faders. I can't think of a way of getting round the absolute relationship between CC value and fader position – you'll just need to make the effort to keep track of where you last faded to. ![]() No, it seems it doesn't work as advertised I guess because it assumes you can't have moved the hardware controller without sending MIDI – which is what QLab is effectively doing with a new cue. Maybe using control change is not the right way to do that? Any idea? Or i have to change the Midi cue and make it going down (127 to 0) but i'm almost back to square one that way, i have to look to previous midi cue before programming the next midi cue. For example if my MainStage fader is on 50 and the midi message send a fader movement from 0 to 20, the MainStage fader never move because it never cross 50. But also, even if that bug was solved, the problem is that it only works if the midi cue send a fader level that is in the range of the actual MainStage fader value. That's very odd and sounds like a bug to me. It seems that it only works if i have moved the fader with the mouse before using a midi cue. But if i send another midi cue again, the MainStage fader comes goes all down to 0 again before going up. The fader only move when it reaches the same value the fader was on MainStage. It works when i set a fader with the mouse on MainStage and then i send a Qlab Midi cue control change. I have tried that but it doesn't work so great. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |