search

jamoma / JamomaMax

Implementation of Jamoma for Cycling'74 Max:
http://www.jamoma.org
41 stars 9 forks source link

second max instance #961

Open avilleret opened 8 years ago

avilleret commented 8 years ago

in j.modular help file, it is ask to open a patch in a Max runtime runtime doesn't exist anymore with Max 7. So I opened a new instance of Max 7 with open -n -a "Max" and load the patch. Then I got a lots of errors when changing or receiving a parameter. Here is a log of some of these :

sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _status = 'orphan' WHERE _path = "~/dev/JamomaMax/Jamoma/examples/remote communication/minuit"
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _modified = '2015-11-17 18:51:30', _status = '' WHERE _id = 5952
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _filtertext = "Which allows the control of parameters in myApplication: This j.modular binds on i-score (see i-score.org) or with a j.remote: with messages: This is an overview of all the Minuit requests. All of this is happening under the hood for the end user in normal usage, though, for debugging reasons, it can be important to understand how Minuit works. Observe value changes Observe the creations and destructions of objects in myApplication Listen to myApplicatio
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _modified = '2015-11-17 18:51:30', _status = '', _desc = "", _tags = "MSP", _text = "flonum  j.parameter decimal_param @type decimal Which allows the control of parameters in myApplication: p i-score This j.modular binds on i-score (see i-score.org) protocol/setup ip 127.0.0.1, protocol/setup port 13579, name, protocol/setup loadbang j.modular i-score Minuitflonum  j.remote my_application:/my_float loadmess 1toggle  activity $1 p Minuit or with a j.remote: with message
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _paths SET _signature = '0d234c488387932a52f0bbd01c2ccef3' WHERE _id = 283
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _tags = 'MSP' WHERE _id = 5952
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _tags = 'MSP' WHERE _id = 10807
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _tags = 'MSP,abstraction' WHERE _id = 10817
sqlite_exec: 5 (database is locked)
sqlite_exec_query: UPDATE _things SET _tags = 'midi,MSP' WHERE _id = 10818

I don't know if this is a Jamoma issue or a Max one (which may not support two instance at the same time)

tap commented 8 years ago

This looks to me like a Max issue with multiple copies of Max trying to access the same DB on disk (which would be bad).

avilleret commented 8 years ago

one workaround seem to duplicate the Max application bundle (with copy and paste)

tap commented 8 years ago

Yes, this will work. The database name on disk is derived from the path/name of the Max application that is launched.

best, Tim

On Tue, Nov 17, 2015 at 1:57 PM, Antoine Villeret notifications@github.com wrote:

one workaround seem to duplicate the Max application bundle (with copy and paste)

— Reply to this email directly or view it on GitHub https://github.com/jamoma/JamomaMax/issues/961#issuecomment-157488038.

lossius commented 8 years ago

But a better solution would probably be to redesign this example so that it doesn't depend on the user duplicating the Max application. That's just backwards....

bltzr commented 8 years ago

How would one do that ?

As Jamoma namespace spans all over one Max application, there’s no way to have two separate Minuit devices in one Max instance… Or we could use jamoma4pd, but that requires installing the whole shebang...