|
Init Des Messages Midi, à l'ouverture d'un projet |
|
|
|
Tue 21 Feb 2012, 12:17
|
![](http://en.440forums.com/forums/uploads/av-419.jpg)
SuperHero
![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif) ![*](style_images/en/pip.gif)
Group: Members
Posts: 2,192
Joined: 05-Apr 01
From: PUYVERT - FR
Member No.: 419
![](style_images/en/spacer.gif)
|
je ne mets pas mes songs en lecture, car je n'utilise que l'Environnement pour jouer les Instru en live. et déclencher des notes à l'ouverture du projet n'est pas possible à mon avis, Dommage car il eut été pratique de configurer ses Mutes depuis Logic en combinant les Notes. Mais les Dumps depuis la table fonctionnent plutôt bien. La contrainte est qu'il faut un deuxième câble midi, puis d'abord enregistrer les snapshots dans Logic. Alors mon idée était d'enregistrer 1 Dump par piste mutée, donc 16 Dumps que je pourrais combiner depuis Logic en mutant les Objets des Dumps correspondant aux pistes que je ne veux pas muter. (oui, c'est.. paradoxal!) Ainsi, il suffirait de muter/démuter les Objets depuis Logic sans avoir à refaire un Dump général pour chaque songs et futures songs. Voici un exemple avec la piste 14 mutée (Objet du Dump 14 démuté): ![](http://tutu13.free.fr/liens.jpg/Studiomaster%20Mutes.png) Mais il y a problème, les combinaisons de Dumps pour certaines pistes marchent bien, d'autres sont foireuses. Exemple: Pistes 1,2,3,4,5 mutées. Dès que je démute le Dump 6 pour muter la piste 6, ce sont les 6,7,8 qui se mutent à la fois. Y a un binz que j'comprends pas. Ci-dessous un extrait du manuel, partie midi: As already mentioned, the Classic 8 features MIDI muting as standard. The first thing to do is set up the MIDI channel for communications, using a rotary switch adjacent to the MIDI In, Out and Thru sockets on the rear panel. Once the system is switched on via the MIDI switch on the front panel, mute information is sent as Note Off and Note On data on MIDI notes 1 to 32 for the channels, and 101 and 102 for Aux 1 and 2. Note On equals Mute On. Unlike some systems, which use non-latching buttons for the channel On switches, the Mixdown Classic 8 has normal latching buttons. These must be in the channel On position before mute data can be played back into the console -- green status LEDs show the mechanical status of the switch. A red LED shows whether or not the channel is muted, so when both LEDs are on, you know the channel is being muted via MIDI. Some older sequencers don't handle very long Note On events very happily (you have to feed them an extra one occasionally just to stop them timing out), but most current sequencers should be fine, and the great advantage of such a simple system is that it's very easy to edit the mute data in your sequencer. You can either set up the mutes as snapshots, then dump them to the sequencer one at a time using the Dump button, or you can run the mix in real time and record note data straight into the sequencer by pressing the console's mute buttons. By working on a few mutes at a time and doing each pass on a separate sequencer track, editing is simpler -- and you can always merge the data to a single track when you're happy with it. If you start a mix mid-song, there's a good chance that some of the mute data will be wrong, because the sequencer won't know what mutes were last set, and it will stay wrong until the relevant mutes are next updated. To get around this, Studiomaster have used the same system adopted for their P7, where mute data is also sent out as bursts of MIDI controller information every second or so. When editing mute data in the sequencer, the controller data must be discarded, otherwise you'll have two conflicting sets of mute instructions. New mute controller data is output from the mixer's MIDI Out when you next play the sequence data back into the console. For those without a sequencer, it is possible to set up one mute snapshot and switch it on or off using the MCM On button.
|
|
|
|
2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)
0 Members:
|
|