Mu updated for Live 9, access chains, auto device select!

[xmonsta]

ok, so I have emailed support and waiting to see what they have to say before uploading anything to the library.

Cheers for all your comments.

[Macciza]

So, I actually got sent a copy of your work from someone and am having a bit of a look into it all . . .
Initially it does not seem to be working; iMac i7, Mac OSX 10.8.3, Live 9.0.1 Trial (not upgraded from 8 Suite yet) Max 6.1(full license, full install) . . .
Will have to investigate further and see what you have done . . .
Cheers
MM

[xmonsta]

Are you using live x64? Mu doesnt work with live x64

Do you have the two ".js" files in the same folder as Mu.amxd ? These are required to run this version of Mu. The /Max Audio Effects/ Folder inside your live library is where Mu.amxd should be.

Works fine for me. Tried on several systems. Mac OSX Lion, Win 7 etc. Live 8/9 Max 5.1.9 +

Is there any chance you can be more specific, on what is not working? Have you tried opening up the "Max Window" to see any errors, by right clicking the top bar of the live device?

[Macciza]

Hi
I know a bit about Max and Lemur setup . . .
Yep 32bit Live and Max . . .
.js files copied as well .. . .

There is a problem with your Mu.path edits throwing an error -
Will look into it and report back either here or vi PM if you prefer . . .
Cheers
MM

[xmonsta]

No problem to talk here.

Could you describe the error in more detail? What's it saying in the max window? What is causing you to think that its Mu.path that's the problem?

First thing I would check is that you have deleted any old versions of Mu. It could be picking up an old version of Mu.path.maxpat? - this was the fix implemented to make it work on Max 5.1.9 + . I dont see how it would work differently on our systems, they are identical, apart from the Mac OSX (which I very much doubt would cause differences).

One way of checking that youre not picking up an old version, might be to click on the "view code" part of the amxd, while it is not open in the max editor. Then click on "p devices", "Mu.deviceeditora /deviceA" , "p_devicename_to_jzlibPath" and finally "Mu.path" - this way you can see whether you are using a previous version, or the edited one. In any case, its essential to ensure that you dont have any remaining files from the old version.

I dont think its going to be possible to put the files anywhere other than your Max Cycling74 folder any more. This is because it now uses "absolutepath" in Mu.path.

On your Mac this should be:

/Applications/Max 6.1/Cycling74/

So:
/Applications/Max 6.1/Cycling74/Abstractions/
/Applications/Max 6.1/Cycling74/DeviceControllers/
/Applications/Max 6.1/Cycling74/Externals/
/Applications/Max 6.1/Cycling74/jzmls/

Also, I would recommend checking what you have in your Max search path. Maybe you have put some Mu files in a different location and linked to them in there?

[Macciza]

Hi
Sorry have not had time to have a really good look yet . .
I'm pretty ok on Mu set up / Max setup and their various workings etc . . .

A few comments though:
Re: Mu.path fix implemented for it to work on 5.1.9 - Do you mean for Live 8 or Live 9 here? Mu 1.2 / Live already worked with 5.1.9 . . .
Also Mu.path already returned an absolute path even though it did not use the 'absolutepath' object . . .
Also whilst 'debugging' objects (message boxes, test code etc) are good whilst debugging, they are best removed before 'release' . . .

Re: Install locations - Those sub-folders should not be split apart like that - they should be within the Mu 1.x/Resources folder . ..
Mu (traditionally) gets an absolute path to there and then finds the folders from there . .
This is also the standard Max approach to dealing with add-on packages, otherwise things would be extremely messy if everything did this . . .

Aah - I had another quick explore of operational differences between Max 5 and Max 6, and I think I may have found a fundamental error in Max 6's response.
Will consult a few people and get back to you all later - but at this point it seems an object in 6 is not returning the same values as in 5, which is the source of the 'not loading device jzml's' problem . . .

Will worry about the other stuff later once I have gotten this part of the equation sorted

Cheers
MM

[xmonsta]

Actually you're right, my bad, Max 6 is where Mu.path started messing up, not 5.1.9. Yes, there was a fundamental difference between one of the objects in Mu.path that came in with Max 6, which is why I changed its operation.

You can put the files in /Resources/ if you like, it'll work either way. I just prefer to have them split up, easier to access when I'm making changes.

I've tested on several systems Win/Mac different versions of Live/Max, friends systems etc. and it works just fine, as long as the set up is correct.

[xmonsta]

Ive contacted Liine support by email. but they're giving me no reply. Therefore, unfortunately, it appears I am not permitted to give the files to the community, upload to the user library etc.

It would take too long to explain how to create the "chains access" and "auto device select" functionality (took around 1 month to build and uses the new Javascript Liveapi). However, since Max is an open system for editing, I can suggest how you might go about fixing your own Mu to work with Max 6 and therefore Live 9. Its a very easy fix and doesnt take long (5 mins).

[*]If you have purchased the full version of Max - Open "Mu.path.maxpat" (inside your /Abstractions/Mu/ folder) to edit it.
[*]If you dont own the full version of Max, you wont be able to edit the file directly, so you will need to do it inside Live, by opening the .amxd device in edit mode. Then doubleclick on the objects "View µ code", "p devices", "Mu.deviceeditor /deviceA" , "p_devicename_to_jzlibPath" and finally "Mu.path" Also "Mu.path" will open in read-only mode (you may see the padlock in the left hand corner greyed out, or a strange pen-tool). In order to edit it you will need to go to, "File/Modify Read-Only" in your toolbar.

Delete everything inside Mu.path apart from the brown inlet box at the top and the green outlet box at the bottom. If you can't edit anything it means you are not in edit mode, so press CMD on your keyboard (CTRL if you're on windows) inside the Mu.path patcher and left click anywhere inside the patcher. Now you should be able to move objects around, edit etc.

Create the following objects: (all of these are just plain objects, except for the message box, which is noted beneath, all are connected on the left-hand outlet/inlet, unless specified otherwise)

[loadbang]
(Mu.path.maxpat) <- messagebox
[absolutepath]
[regexp (.*\\/)(.*)]
[zl ecils 1] <- 2nd outlet from above regexp, goes into 1st inlet of zl ecils
[tosymbol]
[regexp (.*)(Abstractions/)]
[zl slice] <- 2nd outlet from above regexp, goes into 1st inlet of zl slice

Finally connect left output of zl slice, to a patcher "outlet", this looks like a green square object with an O inside it.

Go to "File/Save", to Save the Mu.path patcher.

Now your Mu should work and load the devices properly.

If it's not working, go to your Mu.amxd, DONT open it in max edit mode. Instead, doubleclick on the interface, the objects "View µ code", "p devices", "Mu.deviceeditor /deviceA" , "p_devicename_to_jzlibPath" and finally "Mu.path" to check whether it is loading the changes you have made correctly (sometimes there are weird problems where max stores the old patcher, instead of using the new one you edited). If it is still using the old patcher, try to make the changes again, saving the Mu.path patcher, while you're inside it. It's important to save the Mu.path itself (and not the Mu.amxd) because this is a standalone patcher file that gets included within the parent amxd. The way I sometimes resolve these problems is to save the Mu.path patcher and then make a slight change in Mu.amxd (like moving an object one pixel to the left) and saving the Mu.amxd, basically saving both the Mu.path and the Mu.amxd

If it's still not working, you could connect the uppermost inlet (the brown square box with an "i" in it), to the left hand inlet of the messagebox, containing "Mu.path.maxpat" . This will ensure a bang message is sent to the messagebox, thereby outputting the relevant path, when Mu needs it. Mine works just fine without this.

The previous way of getting the path used the following objects and caused Mu not to work after Max v6 and therefore Live 9 (because it requires Max 6). I suspect that the "t path" object was the culprit here, going into "thispatcher".

For your reference, here is the previous way Mu.path.maxpat used:

[inlet] [loadbang] <- both connected to "t path" object beneath.
[t path]
[thispatcher]
[tosymbol] <- connected to right outlet of above this patcher
[regexp (.*)(Abstractions/)]
[zl slice 1] <- connected to 2nd outlet of above regexp
[outlet]

Anyway, good luck with it. Sorry, I can't share the other changes. I'm loving Mu. Ive been using this for weeks now and my workflow when making music has been greatly improved by this wonderful toy

Happy music making!

[Macciza]

Hi
The best way to do it is with it a single Mu folder, with every thing under that - that is 'standard practice' for easy install / versioning/ maintenance etc
Also it is how most other substantial packages do it - it helps to avoid potential namespace collisions etc . .

It is also how the original was setup and how the scripting /patching etc is structured -
Then all you need is one absolute path, and subfolders are referenced to it . .

I think the best thing to do with this project would be for you to post your work to this thread so every one can get involved . .
There are a few people who's work is already included in what you have produced who would likely contribute to it further . .
I had a bit of a chat with some of the Liine people about it all, though no absolute decisions were made . .

So please just post it here and I will look at making the thread 'sticky' and we can all work towards a final version . . . .

Cheers
MM

[Macciza]

Hi
As I said before I do know a bit about Max - have been using it off and on for about 15 years or so , since about V3 on an old LCIII back in about 1998 . . .
I have the full version of Max/M4L obviously and my complete install is probably pushing 4 gigs with all the additional extra content . . ..
For most of the past year I was helping handle email support, if you had sent it in earlier in the year it would have come to me . .
I also updated the Lemur manual for them and wrote the InApp Editor Guide etc in addition to being a Forum moderator . . ..
MM