https://wiki-de.dmxcontrol-projects.org/api.php?action=feedcontributions&user=Steiny&feedformat=atomDeutsches DMXC-Wiki - Benutzerbeiträge [de]2024-03-29T07:36:56ZBenutzerbeiträgeMediaWiki 1.33.0https://wiki-de.dmxcontrol-projects.org/index.php?title=Lektion_22_Tut3&diff=2142Lektion 22 Tut32012-03-03T13:23:03Z<p>Steiny: Änderung 2141 von Steiny (Diskussion) rückgängig gemacht.</p>
<hr />
<div>{{Hauptüberschrift<br />
| logo = Im-aim.png<br />
| ueberschrift = Erste Schritte: {{PAGENAME}}<br />
}} <br />
<br />
{{DMXC3_lesson}} <br />
<br />
= Überblick =<br />
<br />
In dieser Lektion erklären wir, wie Du Presets verwendest. Durch die Wiederverwendung von Presets bist Du effizienter bei der Programmierung Deiner Show. <br />
<br />
= Lektion 22: Presets (Voreinstellungen) =<br />
<br />
=== '''Zusätzliche Themen (von beta testern)''' ===<br />
<br />
*<br />
<br />
== Übung ==<br />
<br />
*Erstellen...<br />
<br />
== Zusätzliche Links ==<br />
<br />
*<br />
<br />
== Zertifikat ==<br />
<br />
Zurück zum Anfang [[Lektion 1]] <br />
<br />
<br> <br />
<br />
__NOTOC__ __NOTITLE__ <br />
<br />
[[de:Lektion 22|de:Lektion 22]] [[en:Lesson 22|en:Lesson 22]]</div>Steinyhttps://wiki-de.dmxcontrol-projects.org/index.php?title=Lektion_22_Tut3&diff=2141Lektion 22 Tut32012-03-03T13:22:01Z<p>Steiny: /* Lektion 22: Presets (Voreinstellungen) */</p>
<hr />
<div>{{Hauptüberschrift<br />
| logo = Im-aim.png<br />
| ueberschrift = Erste Schritte: {{PAGENAME}}<br />
}}<br />
<br />
{{DMXC3_lesson}}<br />
<br />
= Überblick =<br />
<br />
<br />
In dieser Lektion erklären wir, wie Du Presets verwendest. Durch die Wiederverwendung von Presets bist Du effizienter bei der Programmierung Deiner Show.<br />
<br />
= Lektion 22: Presets (Voreinstellungen) =<br />
<br />
=== '''Zusätzliche Themen (von beta testern)''' ===<br />
<br />
Presets are very similar to cues. You can create them in the same way, see Lesson 8. Similar the the button "Create cue" here you find the button "Create preset". You can use presets to store different values for the parameters of your fixtures. You can store:<br />
<br />
moving light positions<br> colors of RGB Pars<br> combination of gobo, shutter on and color<br> generic chasers (where you later only replace/modify the color)<br> or simply intensities of your conventional fixtures<br> etc. <br />
<br />
The big advantage of using presets is, that it's referenced data. That means, whenever you record a cue using presets, not the actual values, but a link to the preset is stored. So keep in mind, if you change your preset, all cues that use this preset will use the new values. A simple example where presets can rapidly speed up programming would be: You've recorded a color of your cyc wash as a preset and used this preset in five cues. If you later decide to modify the cyc wash a bit, you just need to update one preset instead of five cues. However if you just want to change the color in one cue you can do that by overwriting the reference with manual data. (i hope!)<br />
<br />
DMXC3L13 Preset.jpg<br>Recording Presets<br />
<br />
To record a preset (=^record entries in programmer or parts of it) use the "Store Preset" Button in presets window. The programmer filter will show, which gives you the ability to choose what to record. See Lesson 8 (TODO: Add link here, ...) how to use the programmer filter. After you pressed OK in the programmer filter, a new preset will be recorded. You can now use F2 to rename it.<br>Modifying Presets<br />
<br />
If you want to modify an existing preset, select the preset you want to modify and click on the arrow right of the "Store Preset" Button. A menu will pop up, where you can choose how to modify the preset. Options are explained in the following<br>Replace<br />
<br />
Replace will remove all existing entries from the preset and save everything that is in the programmer to the preset.<br>Merge<br />
<br />
Entries that are not in the programmer but in the preset, are not touched. Existing entries will be updated and missing ones will be added<br>Append<br />
<br />
Entries that are in the programmer but not in the preset will be appended to the preset. Entries that are in the programmer and in the preset, will stay untouched in the preset.<br>Substract<br />
<br />
Entries that are in the programmer and also exist in the preset will be removed from the preset. However keep in mind, not the new value is substracted from the old, but the whole property will be removed from the preset.<br>Deleteing Presets<br />
<br />
You can delete existing presets by selecting the preset you want to delete and then press Delete or in the presets window use Edit -&gt; Delete Preset<br />
<br />
<br>Applying Presets<br />
<br />
You can "drag&amp;drop" a preset into your cue list. A new cue is created. You can set timing and triggers for this cue. The name will stat with "--&gt; ", however you can rename it to what you want. The complete preset will be played back when you use this cue.<br>Applying Presets for Selected Fixtures Only<br />
<br />
Select the fixtures you want to apply your preset to. Then doubleclick on the preset you want to use. The entrys will show up in the Programmer Window. Keep in mind, if you store this to a cue, not the actual values are stored, but a reference to this preset. So if you change something in you preset, everywhere you used this preset the changed values will be used<br>Applying Selected Properties of Presets<br />
<br />
It is also possible to use not the whole preset, but only a selected property from the preset. Select all fixtures and drag&amp;drop the preset to the property you want use in property grid. In the programmer the values for the property will show up<br>Applying Selected Parameters of Presets for Selected Fixtures Only<br />
<br />
You can also apply only a selected property of your preset to selected fixtures only. First select you fixtures then drag&amp;drop the preset to the properties you want to use in the property grid. The value for the selected property for the selected fixtures will show up in the programmer window<br>Applying Multiple Presets to All or Selected Fixtures<br />
<br />
TODO<br>Applying a Preset for Fixtures that are Not in the Preset<br />
<br />
Also you can use a Preset to set a property of a fixture that has no value stored in the preset to a value from the preset. First a short example: A preset with some RGB Pars set at a color. Later you want that you moving lights change to the same color as your RGB Pars. You can either remember or look up this color. Actually there is a third possibility, select you fixtures, in this example you moving lights, and move your preset (drag&amp;drop) to the property grid, now hold Ctrl down and drop your preset to the color property of your fixture. The color of your fixture will be set to the last found value of the used property in your preset.<br />
<br />
<br>Shortcuts<br />
<br />
Of course there are shortcuts that help to increase save time working with presets. But keep in mind, if you use Shortcuts the programmer filter will not be used.<br />
<br />
<br>TODO<br />
<br />
TODO: some paragraphs sound odd, going to change that later ...<br> TODO: add some better explanation what presets are. <br />
<br />
Excercise <br><br />
<br />
== Übung ==<br />
<br />
*Erstellen...<br />
<br />
== Zusätzliche Links ==<br />
<br />
*<br><br />
<br />
== Zertifikat ==<br />
<br />
Zurück zum Anfang [[Lektion 1]] <br />
<br />
<br> <br />
<br />
__NOTOC__ __NOTITLE__ <br />
<br />
[[de:Lektion 22|de:Lektion 22]] [[en:Lesson 22|en:Lesson 22]]<br />
<br />
<br></div>Steinyhttps://wiki-de.dmxcontrol-projects.org/index.php?title=Remotefehler&diff=2138Remotefehler2012-02-29T23:25:55Z<p>Steiny: </p>
<hr />
<div>Bei dem versuch eine Remoteverbindung mit einem Server zu erstellen treten oft fehler auf. Diese Fehler sind hier aufgelistet um es dir leichter zu machen diese zu beseitigen.<br> <br />
<br />
= Error when opening the connection!<br> =<br />
<br />
== RemoteHost not Pingable (Client Rechner antwortet nicht)<br> ==<br />
<br />
Nach dem Versuch eines Verbindungsaufbaues zum Kern von DMXControl 3.0 erscheint folgende Fehlermeldung:<br> <br />
<br />
[[Image:Remotefehler3.PNG]]<br> <br />
<br />
Die Fehlermeldung weißt auf ein Problem mit der Firewall des Client Rechners hin. <br> <br />
<br />
Behoben werden kann diese durch: <br />
<br />
*deaktivieren der Firewall auf dem Client Rechner<br />
*Firewall so einstellen das DMXControl hindurch kommt<br />
<br />
----<br />
<br />
== Unable to contact RemoteHost<br> ==<br />
<br />
Du drückst Connect und in der GUI es erscheint der folgende Fehlermeldung,<br> <br />
<br />
[[Image:Remotefehler2.PNG]]<br> <br />
<br />
bedeutet dies das, dass der server nicht gefungen wird.<br> <br />
<br />
----<br />
<br />
== Interner Fehler beim Server<br> ==<br />
<br />
Du drückst Connect und in der GUI es erscheint der folgende Fehlermeldung,<br> <br />
<br />
[[Image:Remotefehler1.PNG]]<br> <br />
<br />
dann schallte die Firewalls aus!.<br> <br />
<br />
----<br />
<br />
== Eine vorhandene Verbindung wurde vom Remotehost geschlossen<br> ==<br />
<br />
Du drückst Connect und in der GUI es erscheint der folgende Fehlermeldung,<br> <br />
<br />
[[Image:Remotefehler4.PNG]]<br> <br />
<br />
dann wurde wärend des Verbindens der Server deaktiviert.<br> <br />
<br />
----<br />
<br />
== Ungültiger URI<br> ==<br />
<br />
Du drückst Connect und in der GUI es erscheint der folgende Fehlermeldung,<br> <br />
<br />
[[Image:Remotefehler5.PNG]]<br> <br />
<br />
das bedeutet das der Hostname / IP-Adresse nicht existiert oder gefunden werden kann.<br></div>Steiny