Standalone does not show bach objects

[Electrumpet]

Dear list,

I have build a few standalones that use bach objects (bach.circle and bach editor). They become greyed out in the applications.

Everything seems fine during the build. See a copy of my MAX window under this mail.

They are subpatches in a larger patch with tabs. I am working on an interactive syllabus idea.

I use MAX 7 (newest version) on MACOS 10.9.5 and I have tried with Bach both in the packages folder in de documents and the packages folder inside the application folder.

Any ideas?

Best, Hans.

Starting Build for tuningVisual.app...
Processing script...
Copying External panel
Copying External textbutton
adding Windows x86 external bach.circle to collective
adding Windows x64 external bach.circle to collective
Copying External bach.circle
Copying External message
Copying External umenu
Copying External ftm.mess
Copying External bucket
Copying External number
Copying External metro
Copying External counter
Copying External loadmess
Copying Patcher bach.times.maxpat
adding Windows x86 external bach.expr to collective
adding Windows x64 external bach.expr to collective
Copying External bach.expr
adding Windows x86 external bach.portal to collective
adding Windows x64 external bach.portal to collective
Copying External bach.portal
adding Windows x86 external bach.args to collective
adding Windows x64 external bach.args to collective
Copying External bach.args
Copying External comment
adding Windows x86 external bach.ratnum to collective
adding Windows x64 external bach.ratnum to collective
Copying External bach.ratnum
Copying Patcher bach.r2mc.maxpat
adding Windows x86 external oscillators~ to collective
Copying External oscillators~
Copying External buffer~
Copying External uzi
Copying External peek~
Copying External !-
Copying External button
Copying External mtof
Copying External ftm.object
Copying External ftm.list
Copying External ftm.copy
Copying External prepend
Copying External togedge
Copying External zl
Copying External ftm.print
Copying External gbr.fire~
Copying External waveform~.mxo
Copying External dac~
Copying External gain~
Copying External meter~
Copying External toggle
Copying External cycle~
Copying External times~
Copying External adsr~
Copying External dspstate~
Copying Patcher note.maxpat
Copying External live.text
Copying External append
Copying External iter
Copying External ftom
Copying External ftm.editor
Copying External chromax
Copying External ftm.buffer
Copying External deferlow
Copying External delay
Copying External gbr.ola~
Copying External pipe
Copying External fpic
Copying External polybuffer~
Copying External combine
Copying External groove~
Copying External sig~
Copying External send~
Copying External receive~
Copying External adstatus
Copying External ftm.vecdisplay
Copying External gbr.addpartials
Copying External gbr.schedule~
Copying External cycle
Copying External radiogroup
Copying External matrixctrl
Copying External ftm.iter
Copying External tab
Copying External !/
Copying External ioscbank~
Copying External line~
Copying External ftm
Investigating Audio Status.maxpat...
Saving Patcher Audio Status.maxpat...
Copying External substitute
Copying External pak
Copying External speedlim
Copying External js
Copying External bgcolor
Copying External universal
Copying External ubutton
Including File interfacecolor.js
Copying External led
Copying External spray
Copying External buddy
Finished script.

[danieleghisi]

Hi,

this has been already discussed here:
viewtopic.php?f=2&t=491&p=1825&hilit=standalone#p1825

There will be a new tutorial about standalones in the next bach version.

[Electrumpet]

Hi Daniel,

Thanks for the as always very quick reply, I did not realise that the standalone was a package just as MAX itself is... Your trick in the other post helped of course. It would be nice to have something automated to pick those parts of the package that are really needed during the build process though since the increase in size is substantial and I don't want to cherry pick every time I update the standalone (and do it for both MacOs and Windows)... Something like ftm.mxo perhaps?

Best, Hans.

[danieleghisi]

Hi Hans,

I'd like that too, but it should be something Cycling'74 guys implement on their side --- and that might require to explicitly state some dependencies (for instance, bach abstractions depend on the bach objects they contain, and the objects themselves depend on some extensions, such as bach.mxo, and so on; not to mention cage abstractions depending on the bach library, etc.).

At present, the safest way is to always copy the whole package (of course removing documentations and tutorials).

d