5/1/2023 0 Comments Digico s21 offline editor![]() ![]() Let’s say you recall the gain from the first snapshot and then have the rest of the snapshots not recalling the gain and trim. You will now have all of your preamp values recalled from your snapshot.īut beware – this setting is off by default for a reason. If you want to make certain that your snapshot Gain values, I suggest you insert a new snapshot to the first snapshot position, turn on the Input Gain and Trim values in the Global Scope menu, and make sure that the rest of the snapshots have these values turned off (unless you are mixing with gains as well). If you are using snapshots in your sessions, the preamp gain information might not be recalled, if you do not turn that option on. This is meant to prevent your gain settings to change within a session when you change snapshots. However, you can find the option to recall Input Gain and Trim values from your saved session in your Snapshots > Global Scope menu. Not realizing that recalling a snapshot might not recall your preamp gain by default If you do not, the console thinks you are still making changes and the snapshot you have been working on will not be saved. A quick tip: create macros for Save Session and Update Current Snapshot functions, so you can quickly perform these actions without exploring the menus.Ĭreate Macros to quickly save sessions and update snapshots without going into the console menu. The rule is- save your snapshot before firing another snapshot. Make it a habit to regularly save your work every few minutes. The best approach is always to save both. There are two things that can be saved: the snapshot and the session. I can’t tell you how many times I have seen engineers recall their sessions, realizing that they forgot to save their work at the end of yesterday’s gig and they now have a different starting point than the one they hoped for. It is like relying on the word processor on your computer to save your work – sometimes those auto saved documents are missing the last two sentences you wrote. ![]() But in case something goes really wrong (like a power outage), you always want to have a session that you have saved yourself. However, you should always save your work as you make changes. Sure, you can rely on the fact that the audio engine is completely separate from the control PC and that the NVRAM chip will keep your audio going in case of major issues, or on the fact that the console creates sessions and backup sessions in the background. ![]() Not saving your workĭiGiCo consoles are built with redundancy in mind. Or somebody else might have been using the console (especially if this is hired from a rental company) and changed your session by accident. You always have the option of recalling the backup session that the console creates regularly, but it is way better to use common sense and make sure that the correct session is being used. With that in mind – always remember to load your session after a console reboot (preferably from a USB drive that you have) – it is one of the best ways of ensuring that your event will go smoothly. There could be a minor chance that the session got minutely corrupted if the shutdown procedure was not completed properly (maybe the power was cut before the shutdown process was completed) and the session will start giving you issues down the road. Probably 8 out of 10 issues I have had with users and their sessions arose from the simple fact that they set up their FOH, boot up a console that has been sitting in storage for a week and then transported to a venue, and dive into their work without reloading their last saved session. Not loading your session after console boots ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |