Wheel als LTP, während Stimmung läuft

Hallo Thorsten -

Diese Frage ist ein bißchen kompliziert, auf Deutsch zu antworten. Ich danke Florian M. für die Übersetzung.

Auf Englisch:

Congo is a Preset style console with HTP behavior for intensity. This is how it is designed. In order for channel levels from the keypad/wheel to "win" over higher levels, the manual levels are ported into the A field in LTP fashion. When the levels within A are static, this is easy to do. When there is an ongoing crossfade, the current levels in A are being replaced by the levels in B. This makes an LTP calculation very difficult as the LTP winner would always be the incoming preset, meaning you would have no manual control at all. This is why it is difficult to use the wheel to fade a level during a crossfade and it is why the CAPTURE mode is offered. The Capture mode creates a higher priority state for manual levels in the A field - the LTP behavior you seek. There is a channel format in Live called "Captured Channels" - you might want to open another Live tab (TAB & LIVE) so that you can leave it in that format. It will show you all the captured channels and hopefully help to remind you when channels need to be released.

Und auf Deutsch:

Congo ist eine sogenannte Preset-Konsole mit HTP(Höchstwert)-Berechnung für Intensitäten. Dies ist das Konzept der Konsole. Damit die Stromkreiswerte mit der Tastatur oder dem Stellrad über die aktuellen Registerwerte beliebig (höher oder niedriger) gesetzt werden können, werden die manuellen Werte in das A-Register in LTP-Verhalten übernommen. Dies ist sehr einfach wenn die Werte in A statisch sind. Falls dort eine Überblendung läuft, werden die aktuellen Werte aus A durch die Werte in B ersetzt. Dies macht nun eine LTP-Berechnung sehr schwierig, da die einblendende Stimmung immer der gewinnende LTP-Anteil wäre und damit überhaupt keine manuelle Kontrolle mehr möglich wäre. Deshalb ist es schwierig einen Wert mit dem Stellrad während einer Überblendung zu beeinflussen. Deshalb haben wir die Funktion CAPTURE eingeführt. Die CAPTURE-Funktion setzt die manuellen Werte in A in eine höhere Priorität – das gewünschte LTP-Verhalten. In LIVE gibt es eine Ansichtsoption (Gehaltene Kreise) – durch TAB&LIVE kann eine zweite LIVE-Ansicht geöffnet werden, um diese dauernd in diesem Format zu belassen. Dort werden immer alle gehaltenen (im CAPTURE-Modus befindenden) Stromkreise angezeigt und du wirst immer daran erinnert welche Kreise noch released werden müssen.

Danke -

Sarah

Löst Bitte das Problem, ist die einfachste und normalste Bedienung bei fast jeden Pult, gerade bei dieser Preisklase sollte es kein Problem sein, die Hardware macht es nur die Software noch nicht, KEIN Capture.!

Congo: Einfache Bedienung!!, Einfach Spass haben.

Hi there,

I mentioned this topic several times in discussion... An operaor should always have full control to channels even during fades!!

Couldn´t you realize an "auto capture" if channels are grapped by the wheel during fades, that will have an "auto release" when  the next fade will be started.This should not affect normal captered channels. I´m shure it is not that complicated, and it will be a big step ahead.

Would you travel with an aeroplane if you knew that  the captain couldn´t take over control during an automated phase?

Best wishes from munic

Tobias Löffler

Hi all,

I also agree with Thorsten and Tobias. Why do I have to wait until the fade is finished?

After the fade is finished, it's no problem to grab a channel and set another level with the Congo, so why is this not the case DURING the fade?

If the operator realises that channels are too bright or dim during the running fade, he can't do nothing at all. (And, to be honest: In real life, you wouldn't think about capturing channels, because this'll not be quick enough!)

Best,

Mario

It sounds like you're comparing to a "Programmer" style console.
In that style of console, the "Programmer" always overrides absolutely everything - and thus you have to 'clear' the programmer before you can hit Go in order to get the recorded result.

This gives you exactly the opposite problem - the levels do not fade to the recorded values when you hit GO, unless you do something 'special'.

Congo, as a Preset-based console, makes the basic assumption that recorded levels are likely to be the most important.
Thus levels always fade to recorded values every time you hit GO, unless you do something 'special'. (eg Capture, Masters/Independents)

In both cases, the 'special' operation - using Capture or clearing the programmer - is extremely fast, so you can still do what you need very quickly.

Finally, there's no reason you can't stay in Capture mode all the time if you think it's likely that you'll want to do this.

It sounds like you're comparing to a "Programmer" style console.
In that style of console, the "Programmer" always overrides absolutely everything - and thus you have to 'clear' the programmer before you can hit Go in order to get the recorded result.

This gives you exactly the opposite problem - the levels do not fade to the recorded values when you hit GO, unless you do something 'special'.

Congo, as a Preset-based console, makes the basic assumption that recorded levels are likely to be the most important.
Thus levels always fade to recorded values every time you hit GO, unless you do something 'special'. (eg Capture, Masters/Independents)

In both cases, the 'special' operation - using Capture or clearing the programmer - is extremely fast, so you can still do what you need very quickly.

Finally, there's no reason you can't stay in Capture mode all the time if you think it's likely that you'll want to do this.