You can both just work off the same current project file without any need to do a conversion every time you want to work on any edited file that has new additions, etc. Use either Reaper or Samplitude, not both. Reaper needs Studio time and that means Supporting Studio hardware Just a few I know there are many others but those should be added ASAP (This is a big Reason why Samplitude is good)
Controller interfaces support( mixers, Faders) it is horrible right now. Multiple Interfaces at the same time ( the reason why I wanted Reastream fixed so I can run 2 reapers with 2 different interfaces sending audip back and fourth)
native VCA groups enough talk enough excuses PUT THEM IN It took 1 message from me to Justin to get the damn Reastream Localhost issue resolved, meanwhile not one person even pushed the issue that now solved at least 20 different usages. Reaper really needs to get mature and be in the Studio, and that means supporting the studio hardware and have studio features Not sure if Magix will add VCA groups from Sequoia to Samplitude.
Samplitude pro x3 bugs update#
If Samplitude gets an update for VCA groups then I can use Samplitude for live use. Now that Sequoia has VCA groups Protools is taking an ass beating on the higher end Studio use.
Samplitude has always been the better Daw of all of them. Then, when needed, mastering in Reaper, normally making the final steps in Sam again.ĭo not even attempt to knock down Samplitude or Sequoia.
Samplitude pro x3 bugs plus#
Mixing ITB in Reaper or OTB with a Soundcraft console and outboard gear plus Reaper as an outboard VST host (mainly for reverbs). My usual workflow is tracking in an Alesis HD24 on location. and then import the EDL into Reaper for mixing. I sometimes still use Sam for session preparation, trimming, cleanup, etc. Oh, and the pan laws are reversed, but that ¡s a minor issue fixed in a minute. You can export/import EDL sessions between Reaper and Sam. It can be tweaked to taste to suit your preferred workflow. but IMO, Reaper's flexibility is superior. Stability and sound quality are not an issue in both DAWs, so choose whatever fits you better. I prefer the workflow and customization possibilities in Reaper by far. I still have it and use it sparingly mainly for the clean up suite (and buit-in de-noise tools) and final mastering steps and CD indexing. I was a Sam user before jumping to Reaper. He was very impressed with how stable Reaper is and how easy it is to get nearly any VST we ever have used to work and how easy Reaper seems to work without using huge system resources. I would appreciate any feedback if there is something I am missing about Samplitude before I commit to using it for colaborating with my dear friend. I hate to consider learning another DAW but I have to admit I was rather impressed with the workflow in Samplitude. Is there any problem with Samplitude I am unaware of? we both use midi quite a bit and in that regard Samplitude seems quite strong. Of course the cost of Reaper is far less than the Samplitude but he offered to buy me Samplitude. I will use Samplitude or he will use Reaper. Just when I was settling down and trying not to keep looking at every DAW on the planet we have to decide how we will work together after he returns home. to my surprise he dazzled me with a program I am surprised I hadn't heard more about, Samplitude Pro X suite. I hadn't told him that I was using Sonar less and Reaper more but. I expected to dazzle him with Reaper, back in the day we both used "Texture", an old but great sequencer. I am working with an old friend I was in a Band with in the 80s.