Req: ASIO-Channel I/O Selection (EXE)

[sunsynth]

in addition 2:

ASIO Devices selectors! very useful as the MIDI I/O ones etc.

I/We need an 'ASIO-Channel I/O Selection' like in SAVIHost from Herman Seib!

see manual: http://www.hermannseib.com/documents/savihost-manual.zip

[aliasant]

I have been thinking the same.

Right now Im a bit annoyed cause I installed Cubase to test with and that bugger installed 2 extra fake ASIO things so whe I start my little .exe plugin it starts with the wrong damn ASIO meaning I have to manually go in and change it everytime.

Need a better way to do this.

In that exe I have built a selector switch for inputs and outputs but that will only work on my specific setup.
So.

A selector that lists all possible ASIO in/out would be nice. One for each of course.

[sunsynth]

yeah: then we can do it like here: http://synthmaker.co.uk/forum/viewtopic.php?f=7&t=8764

just let it autofind the Audiodriver... and IN/Out Cons!

[mwvdlee]

I vote for this one too!
In fact I think this may be the single most important missing feature for executables.

The developer should have a modules, analogue to the MIDI device selection, to allow smooth integration within the user interface.
Additionally, the developer should have the option to remove the menubar from the executable.

- Allow using multiple (separate) devices (i.e. if you have one ASIO device in your MIDI controller and another one in your recording hardware).
- Allow multiple (separate) channels for input and output (i.e. mix, monitor, metronome, tuning signal, 5.1/7.1/etc.)
- Allow it to be fully integrated in the developer-created user interface.
- Remember the prefered audio driver.
- Allow "automatic" selection of prefered audio driver (i.e. scan for the first line with "Audio 8" in it, otherwise the first line with "ASIO").
- Allow the developer to assist the user in selecting audio devices and integrate help functionality.
- Allow the removal of the menu bar.

It could be implemented pretty much identical to how MIDI devices can be selected, just an added "channel" integer and int array and it looks pretty much the same.

The only issue I can think of would be how to determine whether it's standalone or plug-in. With a simple boolean module, this issue could be solved.

I've made a quick mockup of what I think the modules could look like. It's not particularly spectaculair or special, and neither should it be. Can't upload to this forum, so here's a link to a file I uploaded on my website:

That's an OUT connector on the right. You know, for when it's a plug-in, it needs outs. And yes, it would also need an in and a selector module; I forgot Actually, you wouldn't even need the selectors and multiplexers if you'd just wrap the VST-only module inside an executable module with all the device plumbing

[sunsynth]

Hi Martijn,

good ideas... exactly what i'm looking 4!

i just referred malc to this thread in a mail!

Cheers,
Walter

[DigitalWhiteByte]

+1

[trogluddite]

+1.
Fed up of having to use a host just as a means of sorting out audio routing.
Also this...
http://synthmaker.co.uk/forum/viewtopic.php?f=5&t=8694&p=60841&hilit=exe+outputs#p60841

The Luddite

[attic]

Has this changed at all? Is there a way to reliably select ASIO input for an .exe that will translate to other users sound cards?

[trogluddite]

I have been using my 'Driver Setup Window' method for a while now - the user chooses their device/inputs/outputs (max. 16 channels supported) first time the .exe loads, the settings are then saved and automatically restored for subsequent loads (with the option to re-open the window and change settings later).
Works well on my systems (Yamaha mLAN, various MB chips via ASIO4All), and sunsynth seemed pleased with the results on his machine.
You can find the .osm HERE.

I think that something like this is the best option for translation between systems, as the user input allows for people who use unusual hardware configurations. For example, in my system, I avoid using channels 1 and 2 for music-making (they are shared with windows' system sounds) - chan.7 & 8 are my main sequencer outputs.

The only down-side is that there is no way for a schematic to test how many ASIO inputs there are, so the settings window will show tick boxes for channels that don't really exist - but selecting non-existent channels does not seem to cause any problems (so far!!). Sunsynth had a cood idea to do input selection by 'Auto-learn' (i.e. listening for audio), and you can find an example of that in the same thread.

If you think the idea is sound, but are having trouble with the .osm, or need a simpler version, let me know - I'd be glad to help you adapt it, and I'm always interested to test the compatability with alternative hardware.

[attic]

EXE IO Modules v7.osm Ah thanks Trog. Well that looks really professional. I will let you know how it works on my Motu 2408mk3. I really had one of those WTF moments when I first started looking into this. SynthMaker is brilliant but I couldn't understand why this one wasn't implemented right from the start. I think one of these days I'm going to read all of your posts end to end starting with whenever you arrived here that way I can shortcut the learning curve.

Trogluddite's Profile
Total posts: 1998
(2.59% of all posts / 1.83 posts per day)
Most active forum: Help
(532 Posts / 26.63% of user’s posts)

Thats impressive and such a large number of posts in the help forum. I think Outsim should give you their next upgrade free.

Thanks
Attic

[trogluddite]

Thanks,
Though it does make me wonder if I should get out of the house more!

[attic]

Yes you should get out more. I do my best work after a long walk, some fresh veggies and a cup of coffee. Its the being 40 thing. A pint now than doesn't hurt either.

[trogluddite]

Oh yes, for sure. I am sure i only have my health because I have always loved nature, wildlife, camping etc. - those things always seems to do a good 'deep clean' that gets the muck out from between the brain cells.