andrea agostini

Some (hopefully easy) questions about how to make the bach library more Max6-friendly:

1 - How can I have my objects and patches appearing in their own custom palettes as tabs in the Object Explorer, along with their SVG icons? It worked flawlessly in Max5, and we can't figure out how to achieve it in Max6 - the issue has already been raised in 

https://cycling74.com/forums/custom-object-palette-max5-not-working-in-max6

2 - The smart autocompletion is very cool, but I wish it to show bach.* instead of bach.times. I have both this

max db.addvirtual alias bach.* bach.times;

but the autocompletion still shows me bach.times… what should I do?

CLASS_ATTR_ATTR_PARSE(c,"foo","basic",_sym_long,flags,"1")

for my basic attributes, will it do bad things in Max 5, as long as I build everything against the SDK 5.1.7?

https://cycling74.com/forums/topic.php?id=41800

https://cycling74.com/forums/about-attributes

1 - How can I have my objects and patches appearing in their own custom palettes as tabs in the Object Explorer, along with their SVG icons? It worked flawlessly in Max5, and we can't figure out how to achieve it in Max6 - the issue has already been raised in https://cycling74.com/forums/custom-object-palette-max5-not-working-in-max6

2 - The smart autocompletion is very cool, but I wish it to show bach.* instead of bach.times. I have both this
max db.addvirtual alias bach.* bach.times;
and this
max objectfile bach.* bach.times;
but the autocompletion still shows me bach.times… what should I do?

3- If I add the line
CLASS_ATTR_ATTR_PARSE(c,"foo","basic",_sym_long,flags,"1")
for my basic attributes, will it do bad things in Max 5, as long as I build everything against the SDK 5.1.7?

Thanks for your patience… and btw
bump https://cycling74.com/forums/topic.php?id=41800
and bump https://cycling74.com/forums/about-attributes

explorer-autocompletion-and-basic-attributes-in-max6

2. If you start typing, you'll find that "times~" is in the autocompletion from MSP too. *~ is added in addition to times~ but doesn't replace it. At this time that's the way the system works -- there is no way "unlist" the times~ object. The same applies to your bach.times object.

1. You need a qlookup file to define the metadata for your external. The qlookup file must be named such that it ends with "obj-qlookup.json" and is placed in the 

 folder. For TapTools I have named the file 

. Here is an abridged version of that file's contents, including a UI object:

{
  "tap.comb~": {
    "digest": "Sweet sounding comb filter",
    "module": "msp",
    "category": [
      "Tap.Tools",
      "MSP Filters"
    ]
  },
  "tap.verb~": {
    "digest": "Reverb in a box",
    "module": "msp",
    "category": [
      "Tap.Tools",
      "MSP Effects"
    ]
  },
  "tap.dragwindow": {
    "digest": "Define a region of a window as a handle for dragging the window",
    "module": "max",
    "category": [
      "U/I"
    ],
    "palette": {
      "category": [
        "Interface"
      ],
      "action": "dropfile",
      "pic": "dropfile.svg"
    }
  }
}


As you can see, it references an SVG file which is then used for the icon.

2.  If you start typing, you'll find that "times~" is in the autocompletion from MSP too.  *~ is added in addition to times~ but doesn't replace it.  At this time that's the way the system works -- there is no way "unlist" the times~ object.  The same applies to your bach.times object.

1.  You need a qlookup file to define the metadata for your external.  The qlookup file must be named such that it ends with "obj-qlookup.json" and is placed in the Cycling '74/interfaces folder.  For TapTools I have named the file taptools-obj-qlookup.json.  Here is an abridged version of that file's contents, including a UI object:

Thank you very much Tim - for the other answers as well!

Thank you very much Tim - for the other answers as well!
aa


sorry to annoy you again... 3. and 2. work perfectly, but 1 doesn't.

I have downloaded the latest trial version of TapTools (great work btw, I'll definitely take advantage of the birthday offer!) but they don't show up in the Object Explorer either... I'm on Max 6.0.7, OSX 10.6.8... Does it make any sense to you? What can I be doing wrong?

sorry to annoy you again... 3. and 2. work perfectly, but 1 doesn't. 

... if I add stuff to the original obj-qlookup.json file it works, but frankly this is not what I want to do...

and, btw, is there a way to add my own module to the explorer? (I guess not...)

... if I add stuff to the original obj-qlookup.json file it works, but frankly this is not what I want to do...
and, btw, is there a way to add my own module to the explorer? (I guess not...)

It's really important for us to add our objects in the max6 explorer window.

https://cycling74.com/forums/reference-xml-not-compatible-with-max-6-anymore

Please Tim, tell us what's your tricks to make it work?

Same problem for me..
It's really important for us to add our objects in the max6 explorer window.
related post : https://cycling74.com/forums/reference-xml-not-compatible-with-max-6-anymore
Please Tim, tell us what's your tricks to make it work?
Thanks in advance !
eliott.


Well, this is embarrassing. It appears that I never checked-in the code for the multiple-qlookup! Ugh. We'll try to get it into a future version.

Well, this is embarrassing.  It appears that I never checked-in the code for the multiple-qlookup!  Ugh.  We'll try to get it into a future version.

Will it also be possible adding custom modules, besides Max, Msp, Jit, etc.?

Yes, this will possible. It will not be in Max 6.0.8 but should (can't promise, but fingers-crossed...) be in Max 6.1.

Yes, this will possible.  It will not be in Max 6.0.8 but should (can't promise, but fingers-crossed...) be in Max 6.1.

 file support doesn't seem to be added to the new Max 6.0.8 Version,

Hi,
Multiple obj-qlookup.json file support doesn't seem to be added to the new Max 6.0.8 Version,
I'm wrong ?
Thanks.


You are correct. It will not be in Max 6.0.8 but should (can't promise, but fingers-crossed...) be in Max 6.1.

You are correct.  It will not be in Max 6.0.8 but should (can't promise, but fingers-crossed...) be in Max 6.1.

Hello Tim, what's the current situation now that Max 6.1 has been beta-testing?

The information will be included in the new Max 6.1 SDK, to be released when Max 6.1 is no longer in beta.

explorer, autocompletion and basic attributes in Max6