Vous consultez actuellement la version originale de l'article de MusicRadar.com. Une traduction en français sera bientôt disponible.
12 online collaboration tips
When it comes to media and communications, technology means that the conventional boundaries of distance no longer apply. So why not take advantage these advances to write and produce music with people anywhere in the world?
To successfully collaborate online, there are a number of things you need to consider. Here are twelve pointers to help you on your way...
For more on online collaboration, pick up Computer Music issue 182 - on sale now.
Don't keep quiet
Working with lots of people on a project can be really interesting, as it allows for a potentially much larger range of influences and ideas. But there is also a danger that you can lose your way. If you feel like the project has lost direction, speak up and let the group know.
Make sure you do this in a friendly way, with concrete examples to back you up - having a SoundCloud reference of how the project sounded at an earlier point will help!
Use remote storage
High-quality stereo audio files can be a hassle to send back and forth over the net due to their large size. If you change one part, you could just resend that bit, but it gets confusing fast as the recipient loses track of what's going on.
Avoid all this hassle by using Dropbox to keep projects in sync across multiple machines and users. The default free allowance is usually enough for one project.
Bounce wet and dry
When bouncing a channel with huge amounts of reverb or delay, it's usually worth bouncing a version without those heavy effects as well. These kinds of things can be very subjective, and it's easy for somebody to get frustrated with a part and start to dislike it if they can't adjust it or even hear a dry version.
Watch the levels
When bouncing channels, be careful not to overdrive either the master output or the input levels into any plug-ins, as this can result in digital clipping and a different response from the plug-ins respectively.
Give it a chance
If somebody suggests a change to something you're used to hearing, it can be extremely difficult to view the new version as anything but inferior.
To banish this problem, try living with the change they've suggested for a day or so, working on the track with it in. We're not saying that they're always going to be right, but sometimes you need to let things bed in before you can be objective about them.
Specify a format
Always check what format somebody wants their files in before you send them. Some DAWs offer 32-bit export, but others don't allow 32-bit files to be imported, for example. A problem as simple and easily avoided as this can utterly derail a planned studio session.
Cut out silences
If you're working with lots of bounced tracks, you might find your hard drive buckling under the pressure. First, consider upgrading to much faster solid-state storage. If this is a no-go, try slicing any significant gaps out of each audio file in the arrangement. That way your hard drive won't be accessing every bounce simultaneously for the whole track.
Specify software versions
When collaborating with somebody using the same DAW, make sure that you're working with the same version. Many DAWs aren't backward-compatible, so this could mean that the person running the older version won't be able to open files saved in the newer one. It's easy to overlook this issue, so make sure you ask ahead of time.
Save out samples
Watch out for plug-ins that reference sample banks, as even if you tell your sequencer to save a project and all of its assets, they won't be included. Obvious examples include Native Instruments' Kontakt and Battery.
To get round this, save your sampled patch out and share this with your partner too.
Check for licences
A lot of soundbanks are copy-protected these days, including many Reason Refills and sample libraries. Make sure you check that your partners have the required licences – if not, it's time to bounce again.
Don't be afraid to work in different DAWs and just swap bounced parts. Some people work best using multiple platforms (moving, say, from Live to Logic), so let each producer play to their (and their DAW's) strengths. If you hear something that you'd like to edit, make a note and let your partner know.
Break it up
If you and your partner find yourself constantly disagreeing over what sounds best, things seem forced and difficult, you never finish any projects, or things just clearly aren't working, then don't waste your valuable music-making time continuing the partnership.
Collaboration should be fun, rewarding and productive; you should bring the best out of each other. If this isn't happening, find somebody else to work with.