Helpful ReplyImporting from an other DAW.

Author
Gerry 1943
Max Output Level: -88 dBFS
  • Total Posts : 148
  • Joined: 2014/09/26 11:23:12
  • Status: offline
2017/09/28 14:39:43 (permalink)

Importing from an other DAW.

Can anyone advise if it is possible to import work done in a different DAW and bring it into Sonar X3 producer?
IE: Studio One to Sonar.
If yes....how can this be done. I have tried a few ways without any success.
 
Regards.
Thank you in advance for any replies.
#1
karhide
Max Output Level: -81 dBFS
  • Total Posts : 457
  • Joined: 2007/03/30 04:22:13
  • Location: Southampton / Paris
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 15:18:32 (permalink)
It depends on what you want to import but my method is to export all of the tracks as wav files making sure they all start and end at the same point.  Then when you import the audio will all line up in the project and then you can mix.
 
This way you have to then recreate fx chains and things like that but normally I import in to Sonar to mix and want to start mixing with a clean slate. 

Studio: Sonar Platinum/Cakewalk by Bandlab Intel Core i7 32GB RAM Samsung Evo 1TB system drive Windows 10 64bit - RME FireFace UFX - Focusrite OctoPre MK II - Audient Mico
 
Mobile: Sonar Platinum/Cakewalk by Bandlab Intel Core i7 8GB RAM Samsung Evo 1TB system drive Windows 10 64bit - RME FireFace 400
 
Mobile2: Cakewalk by Bandlab Intel Core i7 8GB RAM 256 GB System Drive Windows 10 64 bit
 
http://www.karhide.co.uk/
https://karhide.bandcamp.com
#2
Slugbaby
Max Output Level: -33.5 dBFS
  • Total Posts : 4172
  • Joined: 2004/10/01 13:57:37
  • Location: Toronto, Canada
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 15:22:25 (permalink)
I normally do what Karhide suggests.  
 
You can also try exporting your project as an OMF file (it retains some of the project-related details) and then open that OMF in Sonar.   It should retain whatever details are relevant for both DAWs.

http://www.MattSwiftMusic.com
 
Dell i5, 16Gb RAM, Focusrite 2i2 IO, Telecasters, P-bases, Personal Drama for a muse.
#3
karhide
Max Output Level: -81 dBFS
  • Total Posts : 457
  • Joined: 2007/03/30 04:22:13
  • Location: Southampton / Paris
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 15:24:16 (permalink)
Slugbaby
I normally do what Karhide suggests.  
 
You can also try exporting your project as an OMF file (it retains some of the project-related details) and then open that OMF in Sonar.   It should retain whatever details are relevant for both DAWs.




I've tried the OMF method but found it does not give great results. 

Studio: Sonar Platinum/Cakewalk by Bandlab Intel Core i7 32GB RAM Samsung Evo 1TB system drive Windows 10 64bit - RME FireFace UFX - Focusrite OctoPre MK II - Audient Mico
 
Mobile: Sonar Platinum/Cakewalk by Bandlab Intel Core i7 8GB RAM Samsung Evo 1TB system drive Windows 10 64bit - RME FireFace 400
 
Mobile2: Cakewalk by Bandlab Intel Core i7 8GB RAM 256 GB System Drive Windows 10 64 bit
 
http://www.karhide.co.uk/
https://karhide.bandcamp.com
#4
Anderton
Max Output Level: 0 dBFS
  • Total Posts : 14070
  • Joined: 2003/11/06 14:02:03
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 15:32:29 (permalink)
Not 100% certain, but I think Studio One can import but not export OMF.
 
OMF is somewhat limited. Karhide's method is what I use. I export a raw WAV for each track but also one with any processing and such, so I can use either what another engineer thought was good or make my own changes.

The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
#5
Cactus Music
Max Output Level: 0 dBFS
  • Total Posts : 8424
  • Joined: 2004/02/09 21:34:04
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 15:40:57 (permalink)
If there is midi tracks involved then first Save the song from Studio one as a Midi file.
Then what I would do is have a copy of the audio folder from studio one on hand. 
Either that or export those from studio one as waves as mentioned above. This is harder to do if the audio is scattered all over the timeline. Best if there is a full track for each part starting at zero. 
Now OPEN the midi file in Sonar which will give you the tempo and what ever midi tracks were used. 
You can then insert the soft synth you will use. 
Now use the browser to drag and drop the audio files to newly created audio tracks in Sonar. 
Some nudging might be needed. 
 
 

Johnny V  
Cakelab  
Focusrite 6i61st - Tascam us1641. 
3 Desktops and 3 Laptops W7 and W10
 http://www.cactusmusic.ca/
 
 
#6
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 15:53:00 (permalink)
+1 to the above advice.
 
If you look up "Export stems" it will give you a rundown of the options to get tracks out of Studio One (both with/without FX, etc.). The manual (page 170 of the Studio One 3 Reference Manual) is light on description, but there are more detailed YouTube posts. You can then "mass import" these into SONAR (they will be listed in the export folder with the prefix you chose at export) by selecting them all at the import dialog.

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#7
tlw
Max Output Level: -49.5 dBFS
  • Total Posts : 2567
  • Joined: 2008/10/11 22:06:32
  • Location: West Midlands, UK
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 16:42:18 (permalink) ☄ Helpfulby kevinwal 2017/09/28 17:57:45
The easiest way to avoid having to manually place imported audio clips along the timeline or having to ensure they all start at the beginning of the project is to use the “broadcast wave” format.

Broadcast wave format is the same as .wav only it includes a time-stamp telling any DAW that handles the format (Sonar does) at what time point the beginning of the audio file should be placed. So a file exported from one DAW as a broadcast wave should automatically be imported into Sonar at the correct time point.

Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board,
ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre.
Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
#8
Anderton
Max Output Level: 0 dBFS
  • Total Posts : 14070
  • Joined: 2003/11/06 14:02:03
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 20:01:06 (permalink)
tlw
The easiest way to avoid having to manually place imported audio clips along the timeline or having to ensure they all start at the beginning of the project is to use the “broadcast wave” format.



The only caution there is that if you're exporting individual clips, you need to identify the track with which they belong so the right clips can be dragged into the right tracks. I generally select all the clips in a track and export so they become a single, complete track. 

The first 3 books in "The Musician's Guide to Home Recording" series are available from Hal Leonard and http://www.reverb.com. Listen to my music on http://www.YouTube.com/thecraiganderton, and visit http://www.craiganderton.com. Thanks!
#9
slartabartfast
Max Output Level: -22.5 dBFS
  • Total Posts : 5289
  • Joined: 2005/10/30 01:38:34
  • Status: offline
Re: Importing from an other DAW. 2017/09/28 21:22:21 (permalink)
Implicit in what everyone is saying is that there is no way to simply move a project from one DAW to another of a different type, and then fiddle with the controls and plugins from the original, which is what everyone would like to do. What you can do is to move audio, and MIDI data. So before you get too deep in the weeds, you need to decide what work you intend to do on the imported stuff. Obviously you will not be able to use plugins or virtual instruments if you do not have them on your machine, and even if you do you will not be able to undo changes these have already made to the audio you are importing. In many cases (maybe most) you are better off getting unprocessed (clean) or minimally processed data if your plan is to use your DAW to finish the mix. Data that has had work done on the dynamics (volume) is much more malleable than data that has had effects like reverb applied for example. Clearly if someone has made a mess of the effects or frequencies of the audio, you are not going to be able to fix that much by importing the over-processed mess into your DAW.
#10
chuckebaby
Max Output Level: 0 dBFS
  • Total Posts : 13146
  • Joined: 2011/01/04 14:55:28
  • Status: offline
Re: Importing from an other DAW. 2017/09/29 14:00:17 (permalink)
After I complete every project I do a few things:
 
1- Bounce all tracks to clips (so I don't have 10 little clips in one track)
2- Clearly name each track (if not already done)
3- Clean Audio folder (to keep 200MB projects from becoming 5GB's)
4- Drag/export each midi track to a custom made midi folder (this prevents midi loss incase of project corruption).
 
With all this done, you can now drag and drop these tracks to another platform. OMF files do not save midi content.
The above procedure saves the raw tracks. One can also export gain or volume automation for an easier set up in the new platform.

Windows 8.1 X64 Sonar Platinum x64
Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
Focusrite Saffire 18I8 - Mackie Control
   
#11
Gerry 1943
Max Output Level: -88 dBFS
  • Total Posts : 148
  • Joined: 2014/09/26 11:23:12
  • Status: offline
Re: Importing from an other DAW. 2017/09/30 14:01:53 (permalink)
Thank you all.
#12
mudgel
Max Output Level: 0 dBFS
  • Total Posts : 12010
  • Joined: 2004/08/13 00:56:05
  • Location: Linton Victoria (Near Ballarat)
  • Status: offline
Re: Importing from an other DAW. 2017/10/01 02:20:57 (permalink)
chuckebaby
After I complete every project I do a few things:
 
1- Bounce all tracks to clips (so I don't have 10 little clips in one track)
2- Clearly name each track (if not already done)
3- Clean Audio folder (to keep 200MB projects from becoming 5GB's)
4- Drag/export each midi track to a custom made midi folder (this prevents midi loss incase of project corruption).
 
With all this done, you can now drag and drop these tracks to another platform. OMF files do not save midi content.
The above procedure saves the raw tracks. One can also export gain or volume automation for an easier set up in the new platform.


Maybe you could even bounce all the clips to tracks 🙄

Mike V. (MUDGEL)

STUDIO: Win 10 Pro x64, SPlat & CbB x64,
PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz.
Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2.
Monitors: Adam A7X, JBL 10” Sub.
Audio I/O & DSP Server: DIGIGRID IOS & IOX.
Screen: Raven MTi + 43" HD 4K TV Monitor.
Keyboard Controller: Native Instruments Komplete Kontrol S88.
#13
Jump to:
© 2024 APG vNext Commercial Version 5.1