Mono Input/Output Friendly names

2015/03/11 19:34:34

Dave Modisette

This rant describes my feature perfectly.

DeeringAmps
This is just a rant, nothing so see here!
Since everyone seems to "accept" that Sonar does NOT handle "loop and punch" properly I'm on to a new (old) issue.
<rant>
WHY CAN I NOT CREATE MONO & STEREO INPUTS!
I'm sure its some kind of OS driver thingy, but COME ON!
Input 1 is INPUT 1, for cris sake.
A REAL console has 4, 8, 16, 32 101; whatever inputs.
Channel 1 is Channel 1, not 1-2 left, 1-2 right, 1-2 stereo.
I know the crap has been beaten out of this dead mule, but GD it.
FIX the GD thing!
</rant>
Thanks for listening, I feel much, much better now...

TTFN,

T

SPlat is the only DAW I own that cannot properly display mono inputs like a true console would display them. I have 18 inputs and not all of them are stereo. In fact most of them are mono. I would like to have friendly names like "Avalon 737, UA-M610, UA-6176, UA-710, JoeMeek, Vintech-3" and not some nonsense like "Avalon 737 - UA-6176 Left."

Thanks.

2015/03/11 19:39:31

Dave Modisette

Maybe we need an Input/Output manager along the lines of the plugin manager?

2015/03/11 21:29:58

stevec

Dave Modisette
Maybe we need an Input/Output manager along the lines of the plugin manager?

+1

A dialog for assigning I/O names would be nice, even for interfaces without a ton of connections. And why not include MIDI I/O in the mix. Oooh.... and maybe export/import to an external settings file for portability. I wonder if something like this might help for those cases where interface connections change depending on boot sequence...

2015/03/12 03:07:36

lfm

Dave Modisette
Maybe we need an Input/Output manager along the lines of the plugin manager?

+1

Something to abstract ins/outs a layer from hardware - something that follows project and simplify moving it to another system - just edit ins/out layer what goes to what hardware. And you can name them any way you like.