Feature Request..."Input Assignment Freeze"

One thing that I find to be "unfortunate" is that you can't make changes to a project template for a device that you're not connected to without losing the channel mappings.  For instance...  Let's say you're recording multi-track from a 32 input live board with a built in interface that is only available to you when the board is out of the truck and at the venue.  Wouldn't it be nice to add time saving bits to your project template so you can save time when you're at the venue...and later on in the studio when you find yourself adding the same plugs and stuff to the same channels.  However...you can't because of the time crunch when you're "at the show"...and...if you try to change the template when you're not connected...you lose all your channel mappings...which is a PITA when dealing with 32 channels.
 
Is there a software (or hardware) way to emulate a given interface so you don't need to have the actual device connected?
 
All it would need to do is present the right number of channels with the correct names and all...with perhaps the option to pump pink noise or some sort of signal on selected channels.
 
Is such software or hardware already available?
 
If not...does anyone see a market for such a device?
 
Or...perhaps the solution would be on the SONAR side.  Have an option to just let the inputs "float" if there isn't presently a device that supports them.

OldTimerNewComer
So do you mean some kind of rotating receptor that knows a lot of setups/Brands?
Well now were talking protocol which would require folks(businesses) with
crossed purposes to agree. Possible? Certainly.
 

 
I was mostly brainstorming about a problem that I want a solution to, that might also turn into an opportunity to get my hands dirty coming up with a solution.
 
Coming up with the firmware would require a bit of reverse engineering with each target device.  I doubt that device makers would be interested in expending any resources other than possibly publishing the interface that is already exposed by their hardware.
 
The simplest solution however (and the one that wouldn't require a "per device" solution)...would be to just have SONAR sidestep the need to have the interface there in the first place.

Maybe I just need to do a SONAR feature request.

No, but also willing to "get dirty hands" if someone else is.
I presently do not need this feature but know people who might.
 
Mel

I think ASIO interfaces have unique ID numbers or something...this triggers vague memories of trying to find out why you can't aggregate most ASIO interfaces. But I'm no expert on this, hopefully someone else is.

I just made a template for my Tascam us1641 with 14 tracks plus spdif, plus 2x midi. 
It took a few minutes using certain shortcuts like insert multiple tracks, outputs etc. But after about 10 minutes I have a template that has all of the Tascam in and outs mapped to 18 tracks and ready to roll. Complete with a master and a reverb bus and all sends ready and muted. 
 
At the recording session I simply load the templates in and name each one and use SAVE AS to make say 16 - 20 projects,, takes another 10 minutes. I leave all those open and minimize them so they are ready to go. 
A 32 track template would take a little longer but no big deal. 
And yes you need the device hooked up to make the first template and I can see that it would be an issue if you don't have it at home, so it's really a matter of showing up and giving yourself time to do this at the venue. 
 

I'm thinking that the simplest and most straightforward solution would be to have an option in SONAR to "lock" the input mappings.  The way it appears to work now is that SONAR "helps you out" by automatically remapping all the inputs to inputs that actually exist.  This is kinda pointless on a live recording where...once it's recorded...you aren't inputting anything else.  All that's left is the mixdown.
 
So...once the mixdown is done and you're happy with all the plugs and settings and stuff...you should be able to strip out all the audio and save it as a template...but now the inputs don't match up.
 
I suppose that, once you have the template fully tweaked (post mixdown), you can then take it back to the board and reassign the inputs...but that's time consuming and (more importantly) error prone if your track and input numbers aren't strictly consecutive.  That falls down when you want to have a stereo track for the keys and another stereo track for the toms...and the wireless mikes are on another page.
 
So...Feature Request..."Input Assignment Freeze"