Forums > MaxMSP

*~: no such object???

March 13, 2006 | 4:51 am

Hi there,

Have been attempting to build a standalone exe application, and when I load it up the max window says: error: *~: No such object.

It repeats this 100 or so times, since this object exists in each of the 8 poly~ objects.

Will I need to use a different object for this operation, or could I download the *~ object (even though it isn’t an external) and at it to the build script?

Any help would be much appreciated!

thanks.
Toby


March 13, 2006 | 6:07 am

If you’re getting that message, I’d recommend checking where the *~
file is on your computer. Have you moved any of the externals, etc.
folders around? (unfortunately searching for *~ is a bit obnoxious, as
* is a wildcard…)

*~ is pretty important, so it shouldn’t be one of those that the build
script "might" find. Chances are you’ve moved something out of the
normal path where Max expects it to be and this is causing the problem.

Peter McCulloch


March 13, 2006 | 8:25 am

"*~" is an objectmapping found in the audio-objectmappings.txt inside the /Cycling74/Init folder….

so if you need to search for this external it’s real name is "times~"


March 13, 2006 | 8:25 am

you could also try to reinstall MaxMSP


March 13, 2006 | 3:02 pm

Ok cheers for that. When I renamed the ‘*~’ object to ‘times~’ it no longer came up with the error message and the audio worked.

However now there seems to be two problems with the patch that did not exist before converting it to a standalone application:

1. The decay of each beat (it’s a drum machine) is at most a few milliseconds. Maybe this is a problem with the poly~ object or something?

2. It runs far less smoothly – is there a way of changing DSP settings in standalone mode? – vector sizes etc.? Does performance usually decrease in standalone mode. Before converting the CPU usage was around 10%, however there seems also to be no way of viewing usage data in standalone mode.

Thanks!


March 13, 2006 | 3:44 pm

In Max, do a Save As… on the DSP Status window, store the copy any
place convenient, and include the copy in your standalone.

Or just take the parts of the DSP Status you need and copy/paste them
into your patch.

Or, better still, use the Litter Starter Pack extra "Running CPU
Usage" for more detailed readings. (URI below.)

Inspectors are just Max patchers, you can open any of ‘em and take
what you need for your own work.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine | +–> Litter Power & Litter Bundle for Jitter
|…………………………………………….
p@castine.de | iCE: Sequencing, Recording, and Interface Building
pcastine@gmx.net | for Max/MSP
pcastine@bek.no | http://www.dspaudio.com/ Extremely cool
4-15@kagi.com |…………………………………………….
| home|chez nous|wir|i nostri http://www.castine.de/


March 13, 2006 | 4:02 pm

Cheers that sorted the Cpu problem out beautifully. Didn’t realise you could edit the dsp window.

As regards the poly~ problem, has anyone had a problem with incorporating this object into a standalone program before? It’s probs just an error in my patch.


March 13, 2006 | 4:52 pm

On 13-Mar-2006, at 17:02, Toby Scott wrote:
> Didn’t realise you could edit the dsp window.

This was hard to ignore in earlier (Mac OS-based) versions, which
sported a lock-widget-thingy in the title bar of all editable
windows. Even on OS X there is at least the pill sitting there
quietly, whispering, "click on me. please." Windows is not quiet so
obvious, but if you chance to wander through the View menu, the Edit
command is enabled. FWIW.

Basic rule of Max #3: *every* window is editable.

> As regards the poly~ problem, has anyone had a problem with
> incorporating this object into a standalone program before? It’s
> probs just an error in my patch.

I’ve used poly~ in standalones with unmitigated success. I am
inclined to concur with your analysis (i.e. problem in the patch) but
without seeing it, one can but speculate.

– P.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine | +–> Litter Power & Litter Bundle for Jitter
|…………………………………………….
p@castine.de | iCE: Sequencing, Recording, and Interface Building
pcastine@gmx.net | for Max/MSP
pcastine@bek.no | http://www.dspaudio.com/ Extremely cool
4-15@kagi.com |…………………………………………….
| home|chez nous|wir|i nostri http://www.castine.de/


March 13, 2006 | 5:21 pm

On 13 Mar 2006, at 16:52, Peter Castine wrote:

> Basic rule of Max #3: *every* window is editable.

Basic rule of Max #3a: except the status window.

("Clear" doesn’t count…)

nick rothwell — composition, systems, performance — http://
http://www.cassiel.com


March 13, 2006 | 6:59 pm

And then there are also the few remaining Alerts: stack overflow,
PACE, etc.

I know there are the exceptions to to the rule, otherwise life
wouldn’t be interesting. But the first thing people need to learn is
rule #3.

Sort of like learning to avoid parallel fifths, so that you can then
learn the exceptions to the rule.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine | +–> Litter Power & Litter Bundle for Jitter
|…………………………………………….
p@castine.de | iCE: Sequencing, Recording, and Interface Building
pcastine@gmx.net | for Max/MSP
pcastine@bek.no | http://www.dspaudio.com/ Extremely cool
4-15@kagi.com |…………………………………………….
| home|chez nous|wir|i nostri http://www.castine.de/


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