Forums > MaxMSP

how do I include DSP status in a standalone?

April 5, 2009 | 9:43 pm

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?



Ch
April 5, 2009 | 10:05 pm

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]


April 5, 2009 | 10:11 pm

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.


April 6, 2009 | 12:41 am

If you ad an object ["DSP Status"], including the quotes, that should do it.

_
johan


April 6, 2009 | 12:51 am

look in the helpfile for the ‘adstatus’ object.

there are lots of options there.



FP
April 6, 2009 | 9:34 am

do you mean this :

– Pasted Max Patch, click to expand. –

April 6, 2009 | 12:56 pm

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?


April 6, 2009 | 1:26 pm

Do as I said…

– Pasted Max Patch, click to expand. –

_
johan


April 6, 2009 | 3:25 pm

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.


April 6, 2009 | 4:30 pm

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


April 10, 2009 | 7:25 am

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


April 24, 2009 | 3:10 pm

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…


April 25, 2009 | 3:39 pm

Have a look at the [adstatus] help file, it seems like that might be what you need.

lh


April 25, 2009 | 4:23 pm
nightstick wrote on Fri, 24 April 2009 17:10
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…

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.


April 25, 2009 | 7:03 pm

if you include the ‘standalone’ object in your patch, then open it"s inspector and click ‘Audio Support’ this will include the DSPStatus… window automatically(all you have to do is have an open message to dac~ after that, no need to put dac~ in GUI presentation just the ‘open’ message and obviously you can use trigger to turn that into whatever message you like (i.e. ‘DSP’, etc.)).

with this technique, you still need to include the spray.mxo and textbutton.mxo objects when you build into a standalone… according to error messages i get, i agree with Stefan, probably should be included automatically.

Also, Audio I/O patch is actually a subpatcher in DSP Status.maxpat so you don’t need to include Audio IO patch(which is named dspio.maxpat).

In case you need to take a closer look, both of those patches are located in app folder: Max5/Cycling’74/interfaces

but you don’t need to include them just include ‘standalone’ object with ‘audio support’ clicked on within its inspector and then simply include textbutton.mxo and spray.mxo
found here: Max5/Cycling’74/max-externals. (no need to make dac~ visible either, just the message to ‘open’)

and ya, using ‘adstatus’ object to make your own custom window is also a good idea.

just replying because i spent hours changing the colors of my DSPStatus… so i figured i’d chime in.


Viewing 15 posts - 1 through 15 (of 15 total)