ai:dos_and_donts
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| ai:dos_and_donts [2020/03/11 11:04] – [The 10+ commandments of Ai wellbeing] icke_siegen | ai:dos_and_donts [2020/03/11 13:19] (current) – icke_siegen | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| * **In Ai, start with creating the Screen Fixtures first, and add projectors later.** Strictly this was a more serious issue in earlier versions but still bears some relevance. In order to avoid performance and other problems always start wth creating your screen fixtures, and only after them add the projectors. | * **In Ai, start with creating the Screen Fixtures first, and add projectors later.** Strictly this was a more serious issue in earlier versions but still bears some relevance. In order to avoid performance and other problems always start wth creating your screen fixtures, and only after them add the projectors. | ||
| * **Use AiM. Use AiM. Use AiM.** Whenever possible use the AiM codec, even for still images and for audio files. In earlier versions the use of MP3s was highly problematic. Nowadays at least they run and can be controlled. But Ai is optimised for using the AiM codec, and adhering to this rule reduces potential confusion and problems. | * **Use AiM. Use AiM. Use AiM.** Whenever possible use the AiM codec, even for still images and for audio files. In earlier versions the use of MP3s was highly problematic. Nowadays at least they run and can be controlled. But Ai is optimised for using the AiM codec, and adhering to this rule reduces potential confusion and problems. | ||
| - | * **Test. Test. Test.** Not only before your show starts but ideally even before getting into the venue, you have setup and tested your system as close as possible to the original situation: outputs, screens, projectors, even adaptors (e.g. DVI-fiber), contents, timecode sources, control inputs (Artnet, MIDI...). Of course you cannot test and prepare every eventuality. But the more you have tested and prepared in advance, the lesser headache and distress are caused by last-minute changes (which will come anyway). | + | * **Test. Test. Test.** Not only before your show starts but ideally even before getting into the venue, you shall have setup and tested your system as close as possible to the original situation: outputs, screens, projectors, even adaptors (e.g. DVI-fiber), contents, timecode sources, control inputs (Artnet, MIDI...). Of course you cannot test and prepare every eventuality. But the more you have tested and prepared in advance, the lesser headache and distress are caused by last-minute changes (which will come anyway). |
| * **Know how to remote-control your server.** If the server is setup on stage and you control it from FOH via Artnet or even Synergy then have another computer at the ready which is linked to your server with a VNC or some other RDP clone. This gives you a great way to view what's actually going on with your server, lets you quickly change some settings etc. | * **Know how to remote-control your server.** If the server is setup on stage and you control it from FOH via Artnet or even Synergy then have another computer at the ready which is linked to your server with a VNC or some other RDP clone. This gives you a great way to view what's actually going on with your server, lets you quickly change some settings etc. | ||
| * **Save often, save regularly.** Saving is very easy - simply double-tab the Ai diamond. Make a habit of doing so frequently while programming, | * **Save often, save regularly.** Saving is very easy - simply double-tab the Ai diamond. Make a habit of doing so frequently while programming, | ||
ai/dos_and_donts.1583924695.txt.gz · Last modified: 2020/03/11 11:04 (external edit)