|
|
Dec 9, 2011 at 9:23am
how to include deviceviewer object (the midi setup) in a patch/standalone (Max6)
i didn’t try to do it in a standalone but it doesn’t even work in a patch.
The object is not found when loading the patch again.
And also important: it is not fully customizable, attributes like color, textcolor, font,… are simply locked, why?
it needs to be included in a standalone here, and of course adopted to a given color theme.?
on Win 7, latest max
|
|
|
Dec 9, 2011 at 10:08am
And the midi setup window itself, is it a patch or is it not a patch?
What is managing the autoresize of the deviceviewer object in this window?
|
|
|
Dec 10, 2011 at 8:02pm
please, some help is badly needed. has nobody ever had problems with it?
Can I have access to this menu in a standalone without using the max options menu?
will it work?
|
|
|
Dec 10, 2011 at 8:52pm
I don’t think it’s a patch per se (like the DSP Status window is), but am not totally sure. Can you simply use [midiinfo] and [umenu] to let the user make selections for ports etc?
|
|
|
Dec 10, 2011 at 9:41pm
No, sometimes you have to disable the “Microsoft Synthesizer” output, or it receives from a midiout even if that is assigned to another device. basically because of that bug and the solution by switching off the “MS synthesizer” output, i want to implement the midi setup window.
what now works, at least by saving the midi setup as a patcher and use that in the patch. strange
edit: doesn’t work in a standalone, not includable hmm back to zero
I’m still interessted how this works and why it is not customizable.
thanks.
|
