spacef wrote: Sat May 11, 2024 1:49 am
Hi all,
I am switching to reaper because I find it much better than what I was using previously (Cubase, then Studio One).
It is really ugly but it sounds better (illusion ? levels are better, sound of the devices is the same, i do not have the issues I had with studio one (sequences recorded from scope synths sounded less good ijn studio one, stuff like that).
Well DAW apps process zeros (0) and ones (1) and in theory don´t sound different.
I recognized different pan-law by default settings made the difference and possibly quality of summing algorithm itself too.
spacef wrote: Sat May 11, 2024 1:49 am
Also, all action shortcuts can be assigned to midi, which is really cool to control the transports when the main window is not in focus (ie, plugin or other windows are opened/focussed).
there are still a few things I have not tested or that are less intuitive than on other daws, but I think I will keep it.
I´m not a Reaper power user up to now,- but it´s one of the most complete applications.
Coming from other DAW apps makes it somewhat difficult to use, just because it´s based on actions and there are a lot of right-clicks and so on.
MANY Protools users switched over to Reaper because of it´s audio features already and when Reaper-MIDI was still mediocre.
But since some time, MIDI got a lot of love.
Interaction of MIDI notation-, list- and piano roll editors is not perfect like in Logic unfortunately,- but it´s usable already.
I appreciate Reaper handles MIDI SysEx and I also doubt they will ditch VST2 (and program changes) like most others do w/ VST3.
And it runs on Linux !
When SCOPE ran on Linux,- Reaper and SCOPE were my prefered combo.
spacef wrote: Sat May 11, 2024 1:49 am
I have not explored scripts, and just use a "Flogic" theme that is good for me.
I never went that deep too,- and my experience is,- using the default theme is the best idea (at least for me).
Updating themes is one more task I´d like to avoid.
IMO, the default theme leaves enough tweaking possibilities for the track control panel and mixer.
3rd party skins often don´t work w/ something you´ll find out too late,- some of the SWS extensions actions which don´t get updates too often p.ex..
spacef wrote: Sat May 11, 2024 1:49 am
Also, what is this 64 bit Reaper Asio driver ? it seems to work fine with Scope 32 FLT driver, but I guess it does not do 64 bit as scope is 32 ? or I am missing something ?
You don´t need the Reaper "ReaRoute" ASIO driver at all,- I unticked it´s installation.
Reaper and SCOPE always worked fine using the SCOPE/XITE ASIO driver (SCOPE 5.1 and SCOPE 7).
That rules for my Win7 Pro x64 Pro DAW machine as well as SCOPe v7 32Bit on my Win7 Pro x86 HP server tower w/ SCOPE PCI hardware.
I myself, I got ASIO issues w/ Studio One Pro and Traktion Waveform 64Bit as well as some virtual instruments when not running in a host,- "standalone" instead,- the Arturia synths p.ex..
I don´t use Reaper ASIO ReRoute ´cause it adds latency to any other ASIO driver running on top,- SCOPE ASIO or RME (Raydat / Babyface)
For me, it´s the better idea running any SCOPE standalone und route audio via ADAT and MIDI bi-directional between SCOPE and a DAW machine running RME multiclient ASIO driver,- both synced via wordclock and MIDI.
Bud