Helpful ReplySonar collab best practices

Author
jkoseattle
Max Output Level: -79 dBFS
  • Total Posts : 556
  • Joined: 2004/10/21 16:29:48
  • Status: offline
2017/07/12 17:33:24 (permalink)

Sonar collab best practices

I am planning on working on a piece with someone else remotely. We both have Sonar. But we don't own the same instruments. This piece is going to be for a medium-sized jazz band of about ten players. The plan is for us to take turns back and forth working on the arrangement in Sonar, probably by sending the cwp back and forth via email (then when we're done, we'll export it to Sibelius or whatever, but that's out of scope for this post).
 
What is the best way of doing this, so that we can seamlessly go back and forth and be hearing essentially the same audio as we work? I assume there is some recommended best practice among folks who do this regularly. I've only ever worked on my own projects, but on the occasions when I've sent a project to someone or they to me, it's always a bumpy ride getting the instruments all in place.

Sonar Version: Platinum  
Audio Interface: M-Audio Delta
Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
Soft Synths: EastWest PLAY Symphonic Orchestra
MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
Check out my work here
#1
highlandermak
Max Output Level: -86 dBFS
  • Total Posts : 214
  • Joined: 2016/03/22 11:33:04
  • Location: Illinois
  • Status: offline
Re: Sonar collab best practices 2017/07/12 18:15:27 (permalink) ☄ Helpfulby Zargg 2017/07/12 20:20:12
Google drive is your friend. I do this all the time and have a generic Google account which I store all my projects on. As long as the other remote users have the same DAW and hopefully as a bonus have all the same effects its easy. Store all the audio files and projects in there own separate folder on your Google drive and share with others.The scary side is with this capability forces you to allow others to have access to the files (you can dictate who has access to what access from single files to full directories). So with it comes the danger of other users deleting files by accident so backing up on a regular basis is a good practice.  Also create Subs busses and bounce all subs to a main sub. This allows ease of transition for those with different audio interfaces. 

Computer: CYBERPOWERPC Gamer Xtreme VR GXiVR8140A Gaming PC
OS: Genuine Windows 10 64 bit (Most current updates)
CPU: Intel Core i7-8700K 3.7GHz 6-Core | Intel Z370 Express Chipset
Graphic: NVIDIA GTX 1080 8GB
USB: 6 x USB 3.1 | 2 x USB 2.0 | 1x RJ-45 Network Ethernet 10/100/1000
Storage: 240GB SSD+2TB HDD
Application(DAW): Studio One 3 Pro and SONAR PLATINUM - Version (Most current update)
Audio Interfaces: PreSonus Studio 192 and Focusrite: Scarlett 6i6 (Most current updates)
#2
jkoseattle
Max Output Level: -79 dBFS
  • Total Posts : 556
  • Joined: 2004/10/21 16:29:48
  • Status: offline
Re: Sonar collab best practices 2017/07/12 20:44:39 (permalink)
Thanks. Unfortunately, the real problem is the fact that we have different instruments on our systems. File sharing is the easy part.

Sonar Version: Platinum  
Audio Interface: M-Audio Delta
Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
Soft Synths: EastWest PLAY Symphonic Orchestra
MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
Check out my work here
#3
highlandermak
Max Output Level: -86 dBFS
  • Total Posts : 214
  • Joined: 2016/03/22 11:33:04
  • Location: Illinois
  • Status: offline
Re: Sonar collab best practices 2017/07/12 21:14:00 (permalink)
jkoseattle
Thanks. Unfortunately, the real problem is the fact that we have different instruments on our systems. File sharing is the easy part.


Define different instruments on your system. Are they virtual instruments or live instruments being recorded on tracks?

Computer: CYBERPOWERPC Gamer Xtreme VR GXiVR8140A Gaming PC
OS: Genuine Windows 10 64 bit (Most current updates)
CPU: Intel Core i7-8700K 3.7GHz 6-Core | Intel Z370 Express Chipset
Graphic: NVIDIA GTX 1080 8GB
USB: 6 x USB 3.1 | 2 x USB 2.0 | 1x RJ-45 Network Ethernet 10/100/1000
Storage: 240GB SSD+2TB HDD
Application(DAW): Studio One 3 Pro and SONAR PLATINUM - Version (Most current update)
Audio Interfaces: PreSonus Studio 192 and Focusrite: Scarlett 6i6 (Most current updates)
#4
paulo
Max Output Level: -13 dBFS
  • Total Posts : 6218
  • Joined: 2007/01/30 05:06:57
  • Status: offline
Re: Sonar collab best practices 2017/07/12 21:26:20 (permalink)
Not sure that I understand the problem. 
 
Make sure that all the tracks on the shared .cwp are rendered to audio with any non sonar FX applied and it should sound the same for everyone.
#5
jkoseattle
Max Output Level: -79 dBFS
  • Total Posts : 556
  • Joined: 2004/10/21 16:29:48
  • Status: offline
Re: Sonar collab best practices 2017/07/12 21:32:37 (permalink)
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.

Sonar Version: Platinum  
Audio Interface: M-Audio Delta
Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
Soft Synths: EastWest PLAY Symphonic Orchestra
MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
Check out my work here
#6
Zargg
Max Output Level: 0 dBFS
  • Total Posts : 10666
  • Joined: 2014/09/28 04:20:14
  • Location: Norway
  • Status: offline
Re: Sonar collab best practices 2017/07/12 21:36:20 (permalink)
jkoseattle
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.


Then you would have to decide which type of sound you are going with during composition, and use the one with the best samples at the end. Perhaps use TTS-1 as standard synth while composing?
All the best.

Ken Nilsen
Zargg
BBZ
Win 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII
Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
 
#7
paulo
Max Output Level: -13 dBFS
  • Total Posts : 6218
  • Joined: 2007/01/30 05:06:57
  • Status: offline
Re: Sonar collab best practices 2017/07/12 21:49:19 (permalink)
Zargg
jkoseattle
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.


Then you would have to decide which type of sound you are going with during composition, and use the one with the best samples at the end. Perhaps use TTS-1 as standard synth while composing?
All the best.





 
This would seem a sensible route for a midi only project. Your original post referred to "hearing the same audio" which is what threw me.
#8
Zargg
Max Output Level: 0 dBFS
  • Total Posts : 10666
  • Joined: 2014/09/28 04:20:14
  • Location: Norway
  • Status: offline
Re: Sonar collab best practices 2017/07/12 21:58:24 (permalink)
paulo
Zargg
jkoseattle
These would be virtual instruments. It will all be midi, no audio tracks, no live instruments at all.


Then you would have to decide which type of sound you are going with during composition, and use the one with the best samples at the end. Perhaps use TTS-1 as standard synth while composing?
All the best.





 
This would seem a sensible route for a midi only project. Your original post referred to "hearing the same audio" which is what threw me.


Me too
Which was why I marked the first reply as helpful. It answered the OP's originally formed question.

Ken Nilsen
Zargg
BBZ
Win 10 Pro X64, Cakewalk by Bandlab, SPlat X64, AMD AM3+ fx-8320, 16Gb RAM, RME Ucx (+ ARC), Tascam FW 1884, M-Audio Keystation 61es, *AKAI MPK Pro 25, *Softube Console1, Alesis DM6 USB, Maschine MkII
Laptop setup: Win 10 X64, i5 2.4ghz, 8gb RAM, 320gb 7200 RPM HD, Focusrite Solo, + *
 
#9
arlen2133
Max Output Level: -78 dBFS
  • Total Posts : 601
  • Joined: 2010/05/20 00:09:27
  • Location: Inland Empire, CA
  • Status: offline
Re: Sonar collab best practices 2017/07/12 22:29:42 (permalink)
Hi Jim,
I do compositions predominately in MIDI and when I've collaborated with others using Sonar, I always record my portion down to an audio track.  That way, if they can't get the exact settings I have (for some reason), they will have my bounced version in the project as reference.
Just a thought...
 
By the way, love the music man! 
Great stuff!

Arlen
aka
Mr Grant
my music


Cakewalk by Bandlab, Sonar Platinum (2017.09) & X3e , Windows 7 64 bit, Intel I5 3.4 Ghz, 32 Gbs RAM, Saffire Pro40, various pres and VSTi's.

#10
g_randybrown
Max Output Level: -40 dBFS
  • Total Posts : 3522
  • Joined: 2003/12/24 11:30:04
  • Location: Las Cruces, NM, USA
  • Status: offline
Re: Sonar collab best practices 2017/07/12 23:29:06 (permalink)
Agreed, Jim's stuff is way underrated!
I'd like to throw in a question since you guys are discussing collaboration.
Would there be issues if the 2 collaborators were using different bit rates (ie 16/44 vs 24/48) or would Sonar catch it and change the other guys bit rate?
 
Thanks very much,
R

G. Randy Brown 
Windows 10, 64 bit, Platinum
Intel Core i7-3770S
Asus P8Z77-V LK mobo   
4X8GB Corsair XMS3 memory 
500 GB Crucial BX100 SSD (OS)
two WD Black 1 TB HDD
SAPPHIRE DUAL-X 100314-4L Radeon HD 6970 2GB 256-Bit GDDR5 
Presonus AudioBox 22VSL
youtube.com/crystalclearnm
#11
highlandermak
Max Output Level: -86 dBFS
  • Total Posts : 214
  • Joined: 2016/03/22 11:33:04
  • Location: Illinois
  • Status: offline
Re: Sonar collab best practices 2017/07/13 00:00:29 (permalink)
A good practice is to keep the bit rates the same. You run the risk of having acidental downsamples or upsamples at the final mix.

Computer: CYBERPOWERPC Gamer Xtreme VR GXiVR8140A Gaming PC
OS: Genuine Windows 10 64 bit (Most current updates)
CPU: Intel Core i7-8700K 3.7GHz 6-Core | Intel Z370 Express Chipset
Graphic: NVIDIA GTX 1080 8GB
USB: 6 x USB 3.1 | 2 x USB 2.0 | 1x RJ-45 Network Ethernet 10/100/1000
Storage: 240GB SSD+2TB HDD
Application(DAW): Studio One 3 Pro and SONAR PLATINUM - Version (Most current update)
Audio Interfaces: PreSonus Studio 192 and Focusrite: Scarlett 6i6 (Most current updates)
#12
highlandermak
Max Output Level: -86 dBFS
  • Total Posts : 214
  • Joined: 2016/03/22 11:33:04
  • Location: Illinois
  • Status: offline
Re: Sonar collab best practices 2017/07/13 00:02:25 (permalink)
My personal recommendation would be if possible 24/48 but that is a personal preference and a life long debate :)

Computer: CYBERPOWERPC Gamer Xtreme VR GXiVR8140A Gaming PC
OS: Genuine Windows 10 64 bit (Most current updates)
CPU: Intel Core i7-8700K 3.7GHz 6-Core | Intel Z370 Express Chipset
Graphic: NVIDIA GTX 1080 8GB
USB: 6 x USB 3.1 | 2 x USB 2.0 | 1x RJ-45 Network Ethernet 10/100/1000
Storage: 240GB SSD+2TB HDD
Application(DAW): Studio One 3 Pro and SONAR PLATINUM - Version (Most current update)
Audio Interfaces: PreSonus Studio 192 and Focusrite: Scarlett 6i6 (Most current updates)
#13
g_randybrown
Max Output Level: -40 dBFS
  • Total Posts : 3522
  • Joined: 2003/12/24 11:30:04
  • Location: Las Cruces, NM, USA
  • Status: offline
Re: Sonar collab best practices 2017/07/13 00:04:13 (permalink)
Thanks

G. Randy Brown 
Windows 10, 64 bit, Platinum
Intel Core i7-3770S
Asus P8Z77-V LK mobo   
4X8GB Corsair XMS3 memory 
500 GB Crucial BX100 SSD (OS)
two WD Black 1 TB HDD
SAPPHIRE DUAL-X 100314-4L Radeon HD 6970 2GB 256-Bit GDDR5 
Presonus AudioBox 22VSL
youtube.com/crystalclearnm
#14
dubdisciple
Max Output Level: -17 dBFS
  • Total Posts : 5849
  • Joined: 2008/01/29 00:31:46
  • Location: Seattle, Wa
  • Status: offline
Re: Sonar collab best practices 2017/07/14 05:01:53 (permalink)
If it was me, I would do include midi ans bounced audio too. The collaborator can sub instruments that sound close based in the bounce and still have midi data to work with
#15
Sir Les
Max Output Level: -67 dBFS
  • Total Posts : 1182
  • Joined: 2012/07/09 04:56:19
  • Location: MONTREAL, QUEBEC, CANADA,
  • Status: offline
Re: Sonar collab best practices 2017/07/14 13:05:10 (permalink)
Some times it is not a constant exchange over to another system.
 
Here I used 2x allen and heath r 16 desks tied together.(on one system)(was not stable, but if it was)..according to the manual I must use 96k settings for this to work to get 32 tracks of input ...on pc using firewire setup.
 
So sometimes it is hard to follow all the intel of what is best.
 
So, if so more issues with gear/software plug ins and or plug in instruments come into play...
 
yah pick a standard both have that works for both or all involved in the project of midi if only midi is being sent back and forth.
 
If the master maker, feels his instruments are justly serving the ideal idea, and the other partner does not have same instrument plugs...render to wave, but keep the midi track muted , and make a note or foot note to read into what is what...where is, and why put.
 
And then they can import knowing all is there, plus what you made stems of for from.
 
That way he or she, or other can pick it up, where you left off...midi or wave...(wave can now be made to midi, and midi to wave) so they say....I think doing it more so proper so all in conveyed as the conceptual idea be brought forth in or on all sides.
 
So that, wave to midi is less a mess, but is possible also, is to reduce the transients and harmonic content, as some one said on these forums helps.
 
 
So with all that..(and that is also alot to take into consideration now possible in mind...getting to know what is owned and what is being used, should be made standard on both sides....if not possible...most if not all other methods are here posted...?
 
Well no, fly over, go to, or bring in by bus of car or subway, plane or boat,...or ask ed to borrow the submarine ...and no nukes please...we need to keep the sheep silently grazing in peace!.
 
 
Cheers.
 
 
 
 
 

1. Intel 5960x 3.5mhz , ASUS x99 deluxe u3.1, Asus Thunderbolt ex II,   G skills f4 3000 Memory 32GB , ADATA ssd 250GB Main Drive, Lots of WD Red 7200 Mechanical Drives with Black Drives, 14x multi optical Drive, LG Multi Blu Drive,  2X Extern WD Mybooks usb 3.0, AMD r7 270 video card, Motu 828x TB , Motu Midi XT.
2.  USING MAC PRO, as win 10 has damaged 2 x99 systems 8.1 is also to blame for the final burnout trying to roll back!
 
3.  Something Wonderful: https://1drv.ms/f/s!AlHkRy9cXBbYpQNvVBCt8r7fQ5PS
#16
jkoseattle
Max Output Level: -79 dBFS
  • Total Posts : 556
  • Joined: 2004/10/21 16:29:48
  • Status: offline
Re: Sonar collab best practices 2017/07/14 19:24:41 (permalink)
Thanks everybody, this is good info. Based on our own conversations as well as advice from everyone here, I built a TTS-only setup, and sent it over, and it all played back fine. Since the end goal here is printed music for a live band, that otta do us. Thanks again!

Sonar Version: Platinum  
Audio Interface: M-Audio Delta
Computer: Dell i5 3.1 GHz, 12Gb RAM, Windows 10 64-bit
Soft Synths: EastWest PLAY Symphonic Orchestra
MIDI Controllers: M-Audio 2x2 MidiSport Anniv Edition
Settings: 16-Bit, Sample Rate 44.1k, ASIO Buffer Size 128-1024, Record/Playback I/O Buffers play:256k, rec: 64k, Total Round Trip Latency 48 ms  
Check out my work here
#17
Jump to:
© 2024 APG vNext Commercial Version 5.1