Audio Settings for Application
Hello All,
I have a quick question. I've have built a patch and have put an audio setting button on with the dac, etc...
I save (of course), then go to make an application of the program, mainly if I want to use my patch on a computer that does not have Max/MSP on, i use MXF files on computers which do have MAx/MSP on.
But in my application, the audio settings do not come up, which is really weird. This is with the application NOT the max collective file.
Any ideas on how to sort this? i have also put a picture up to show you what i mean
On Aug 3, 2008, at 11:41 AM, raja wrote:
> This is probably a bug(or an as-of-yet-un-fully-developed
> functionality(i.e. the builder script is not including necessary
> files, etc.)).
The DSP Status dialog is really just a patch. If it's included, the UI
should show up in a standalone:
Chris Muir
cbm@well.com
http://www.xfade.com
On Aug 3, 2008, at 2:28 PM, raja wrote:
> Chris, this is true, however, it did not behave like this in 4.6.
I don't have Max 4 on this machine, so I'm not sure, but I think that
the DSP Status dialog wasn't a Max Patcher in Max 4, but rather
included in the MSP code.
-C
Chris Muir
cbm@well.com
http://www.xfade.com
On Aug 3, 2008, at 4:43 PM, raja wrote:
> Hey, do you happen to know the exact location of that patch in the
> Max5 folder?
Cycling '74/interfaces/
-C
Chris Muir
cbm@well.com
http://www.xfade.com
Thanks very much for all your help
It is true though, i did not have trouble in Max 4, with the DSP status. Very odd that it is popping up now with that problem, by hey, thats life.
I too will also seek in emailing them to say about the problem.
It is not too big of a deal if you work with the MXF format in runtime. But if go on a computer that doesn't have runtime, it makes it a little bit more difficult. Especially if you need a friend or others to test your patch/program on their own machines
Ahhh, one more question, when is the new pluggo coming out?
would love to get my hands on that little baby and start making plugins again.
But in the mean time, i will stick with rewire
Cheers again
Stumbled on the same problem, but I also found a workaround:
If you create an object called "DSP status" in your patch (WITH the quotation marks because there's a space in the name), the necessary stuff is automatically included when you build the application.