Audio Engineering

349 readers

1 users here now

A place to discuss all things audio engineering! Please keep discussion civil and professional.

founded 1 year ago

MODERATORS

myhobbyismagnets@lemm.ee

Sound Technical Rider Patch List (lemmy.world)

submitted 4 months ago by PsyKiere@lemmy.world to c/audioengineering@lemm.ee

4 comments fedilink hide all child comments

Hello! Is it good practice in a technical rider patch list to group the violins for example under one line when there are a good number of them for better readability or should I give each one a line. For example the format would be: Input: 1-12 | Instrument: Violin 1 | Number: 12 | Microphone: ...

Also is there a particular order of instruments that should be followed?

Thanks!

top 4 comments

sorted by: hot top controversial new old

[–] extremeboredom@lemmy.world 3 points 4 months ago* (last edited 4 months ago) (1 children)

Better to break them down. And I don't know about your specific case, but standard festival patch is usually:

Drums

Guitar

Bass

DI (synth, keys, tracks)

Strings

Horns

Vocals

[–] PsyKiere@lemmy.world 3 points 4 months ago

Thanks!

[–] Sequentialsilence@lemmy.world 2 points 4 months ago (1 children)

Every input should be its own line on the input list.

Standard input order is rhythm, melody, harmony, Vox. That’s not to say you should split your violins up between melody and harmony, but your Cello’s are typically more melody focused than your violins are. (Thanks Pacabell). Everything builds on what comes before it, so whatever your foundation is comes first, which is usually rhythm. Next comes the feel, or melody, then comes all the sparkle and flavor in the mix or the harmonies. If the foundation is messed up, it doesn’t matter how nice the sparkle is it will fall apart.

Hope that helps.

[–] PsyKiere@lemmy.world 1 points 4 months ago

Thanks!