Keeping a rehearsal guide easy to follow
Keeping a rehearsal guide easy to follow
Our demo is moving to another editor for the next revision. There is a texture I want them to assess, but describing it as strange or metallic feels too vague to be useful. I would rather send a precise observation than prescribe a fix. I would begin with the exact filename and revision date. The passage can be described with a start and end timestamp. I came across suno shimmer as a possible term while reading about generated audio, although I am not sure it fits this particular sound. The note should separate observation from interpretation. The headphones or speakers used could be recorded in the note. The editor should receive both the source and the relevant excerpt. The first handover should leave room for the editor's own assessment. What else belongs in a concise report like this?
Кто сейчас на конференции
Сейчас этот форум просматривают: нет зарегистрированных пользователей и 0 гостей