how do I include DSP status in a standalone?
When I make my standalone, DSP-status is not present in the menu, only MIDI-setup and overdrive. How do I include DSP status in my standalone?
There may be a better way, but a possibility is to had an additional menu item using [menubar] that would bang a message [; dsp open]
I included a dac~object and when I double clicked that, I got a bunch of errormessages (missing objects and so on). It doesn't have to be in the menubar but I need to have the DSP status window.
If you ad an object ["DSP Status"], including the quotes, that should do it.
_
johan
look in the helpfile for the 'adstatus' object.
there are lots of options there.
do you mean this :
Yes, but the problem is that all the objects of the DSPpatch are missing. When I make my standalone and then doucleclick on DSP, it opens the DSP window but panels and other objects are missing, that is the big problem. How can I include the whole DSP patch?
Do as I said...
_
johan
If you want the actual Max/MSP DSP Status window, you need to copy the DSP Status.maxpat into your standalone application. You'll find it in your Max application folder->Cycling '74->interfaces.
Control-Click on the application icon of your standalone and select "Show Package Contents." Copy the DSP Status.maxpat into Contents->support->interfaces. Now you have a DSP Status window in your search patch no matter where the application gets placed.
BTW, these instructions are for a Mac. I don't have a PC, but it's my understanding that the contents folder is in the same folder as the application, so the process is very similar.
theoretically the dsp status patch is © cycling74 ... but i would recommend to just copy it and include it as patcher-in-patcher. and while you are on it, you could also improve it a bit or erase some functions you dont need. you can also use it to loadbang a desired initial status for your app,. which is, btw, especially useful while still working on the patcher ...
-110
I would call it a bug, that these objects are not included in a standalone automatically as soon a single MSP object is in the patch.
All the workarounds are fine, you can also include the objects while building, but I think that should not be necessary...
Stefan
I figured out all of the above with the status window and everything. I need to have it so that a user can have access to this to change inputs and outputs. I'm trying to avoid having the dac in the window that the user has to double click on. Is there a way I can adjust input/output sound using Umenus? If so, can you help me out? I've got a umenu setup just fine to have the user decide on a MIDI input controller. I just need audio dealt with now...
Have a look at the [adstatus] help file, it seems like that might be what you need.
lh
nightstick wrote on Fri, 24 April 2009 17:10I figured out all of the above with the status window and everything. I need to have it so that a user can have access to this to change inputs and outputs. I'm trying to avoid having the dac in the window that the user has to double click on. Is there a way I can adjust input/output sound using Umenus? If so, can you help me out? I've got a umenu setup just fine to have the user decide on a MIDI input controller. I just need audio dealt with now...
there are many ways of opening a patcher from disk or a patcher in patcher, no need to click on dac.
the audio IO patch is also a patcher in the maxmsp install, which you can also just copy, put it into a [p], and modify it.