routing issues (midi+audio) [FIXED in 2.1.2]

even better:

it would be just great to have a midi feedback ON/OFF switch inside the Parameter Control box of every single parameter.

plus maybe also a generic one for the entire midi port... (?)

Hi!

> I can't make AudioMulch to remember my audio routing settings

Can you try describing exactly what behaviour you expect, and what behaviour you're seeing? I'm not exactly sure what you expect.

Note that the "open all channels" setting doesn't affect anything else in the settings dialog box. When checked, it just means that AM will open all channels of the device independent of which channels are selected in the settings.

> There is no MIDI OUTPUT setting options in AudioMulch

That's because there is not currently any MIDI output in AudioMulch (although this is coming in AM 2.2).

> but apparently,
> virtual MIDI loopback programs like LoopBE seem to detect that it has
> the same midi OUT port as its midi IN PORT

This sounds like a problem with the LoopBE feedback detection. AudioMulch does have MIDI Output for MIDI sync, you could check that that isn't configured to the same device. I usually use MIDI Yoke and have no trouble routing MIDI from other programs into AudioMulch. You could try that.

> So maybe there should be an option to totally disable midi output for each separate port

I'm not sure what you mean by that. This seems to assume that AM has MIDI out (which it doesn't).

> it would be great to be able to set midi OUT options in audiomulch,
> not only from audiomulch to the outside but also between Plugins and Modules

Can you elaborate on what you mean by this. I'm not sure I understand.

> it would be just great to have a midi feedback ON/OFF switch inside
> the Parameter Control box of every single parameter.

Also I don't understand this. Do you mean MIDI feedback for motorized fader controllers and such?

Hi Ross

OK, i'll try to better explain my problem :

Audio routing issue:

My RME audio interface has 18 I/Os but I want AM only to use 4 of them, so I set that so in AM's Audio Output devices and channels setting page by closing all the channels don't want to be used.

I would expect to allways find only those 4 I/Os opened each time I open AM,
but instead of that, all 16 I/Os are opened again every time.

as for the Midi issue, my mistake then, sorry

But as both loopBE and midiyouke where constantly detecting feedback problems with AM I supposed this last version of AM had some Midi Output habilitaded to allow data values to be sent back to physical Midi controllers for visual feedback
(yes, i mean for motorized faders and such).

After some more trial and some forced resets, now it just seems to work fine, no more feedback is detected... Strange tough, it really didn't work well before...

I must be loosing neurones by somewhere...got a find the leak.

Have a nice day, Ross !

>>>>>
My RME audio interface has 18 I/Os but I want AM only to use 4 of them, so I set that so in AM's Audio Output devices and channels setting page by closing all the channels don't want to be used.

I would expect to allways find only those 4 I/Os opened each time I open AM,
<<<<<

Yeah, that's what I'd expect too.

>>>>>
but instead of that, all 16 I/Os are opened again every time.
<<<<<

Is the problem that the settings are being reset when you restart the program? or is it just that AM appears to be opening all channels.

Thanks!

Ross.

when i restart AM all 18 iOs are opened instead of only the expected 4 I did set in the previous session

no other setting in AM is reset, just the audio IO settings

I think I know what you mean. Sounds bad. Would you mind emailing me a screenshot of the before and after states?

Just a note: we've determined that this is fixed in AudioMulch 2.1.2, which should be released on Friday.