DAWs and Scope

[spacef]

That's great news Auricle

[Gatam]

Very good tips mehdi !!
but you can't use and write automation in your daw with this technic
If i want to change some eq during my mix and write it in my automation lane.
if i want to play with a dry/wet knob for a delay mix and so on ...

[spacef]

It's true, you can't write automation as the CCs are temporarily assigned to this or that Eq or device so it is "volatile" assignments... The only thing it gives you is hardware control over those parameters that are currently assigned (that's why I'm trying other stuff...).

[auricle]

Ah yes, I see the problem.

The only way around this is to choose carefully what parameters need automating. It's going to be a very rare track that needs all 119CC automating. The problem is controlling it with hardware as well.

[spacef]

exactly...
Having 100% hardware control is a nice and desirable thing, but it is still preferable and more logical to assign only those CCs that you need for such and such project. Actually i find it quicker and more flexible/efficient than any other technic based on multimbrality (in my opinion).
14 bit midi might change this paradigm...(not even talking about OSC which is also powerful but need compatible hardware, which are often more expensive)

[Gatam]

A good direction should be to reserve, let say, 30 or 50 first CC (cc 1 to 50) for all sort of control template (eq, delay, comp, synths etc etc ..)
and have cc 51 to 119 reserve for automation lane

So when you need to automate something in real time with your controler, you use your CC template (1 -50) and write the parameters you need in your sequencer
When it's finish, you just copy/past and change your cc automation assignment to a free CC slot (51 to 119)

[auricle]

A good direction should be to reserve, let say, 30 or 50 first CC (cc 1 to 50) for all sort of control template (eq, delay, comp, synths etc etc ..)
and have cc 51 to 119 reserve for automation lane

So when you need to automate something in real time with your controler, you use your CC template (1 -50) and write the parameters you need in your sequencer
When it's finish, you just copy/past and change your cc automation assignment to a free CC slot (51 to 119)

Now that sounds like a good idea!

[siriusbliss]

siriusbliss:

If you route out to Scope; how is the external hardware routing insert necessary? Like, do you have the direct out of the Scope mixer looped back to Samp to advance/delay a track prior to Scope?

I DO have external effects (old Eventide and Digitech) that I will occasionally route out to - which I tell Samplitude to ping for latency compensation. But for the internal routing, Samplitude only needs to see the ports in Scope, and no compensation really necessary.

By the way, I'm also finding Xite to be much 'tighter' in this regard. I have the ULLI turned way down.

Also, on occasion I route sub groups out of Samplitude and render stems through Scope to fresh tracks in Samplitude. Not always necessary since Samplitude has a great freeze function where I could just spit out .wavs (or whatever) for use in other platforms. It's also a great approach for mixdown.

re: OSC, etc. - I see this as the next leap for S/C to gain a headway into the present industry, since MIDI is still valid for everything BUT automation (IMO). Guys doing film or video post work that have a LOT of automation cues and quick adjustments tend to avoid MIDI due to jumpy response, or lack of resolution. Again, I'm not a huge automation user, but am planning on doing some more wild live interactive performance developments next year (with yet-to-be-released controllers I'm still co-developing) that will require high-res response.

Greg