maybe the_man361 is talking about the Max for Live examples? you can find bits of them in /patches/m4l-patches/Tools resources/M4L.PitchScale.bpatch.maxpat and M4L.PitchModes.txt.
however, chris, can i just say that your scalemaster is like the big daddy, and it is completely awesome, and demonstrates a really musical way of presenting all the logic, and congratulations, and thanks very very much.
Oh yeah, I remember now... I think I that example has been around for a long time. ScaleMaster goes well beyond that patch. For example, I have gone out of my way to make sure I don't have any "harmonic mysteries" in ScaleMaster. I used conundrums, instead.
I got some email asking me if there was a good way to limit the scales that are in the scale menu. I do have some plans along this line, but in the mean time, I thought I would show people what the current interface in my Gyre program looks like for scale selection.
Right now the scale selection stuff is too tied to the rest of the program and the block controller I'm using it with, but I do have some plans to try and extricate it.
I have to ask... any chance of sharing that sweet looking Guitar Mode Viz in your Gyre app? That is Brilliant! How did you ever get that to work? Different colls per string or is it a single matrix with the setting saved?
@ Chris... ah right... so does the 'p scalemasterdata' address sub pathes then? do I have to put your 'scalemaster' folder' in a certain place in the max file path?
what to I connect to what? I see the 'bpatcher' box is sitting there and the 'p scalemasterdata' to the right of it... how to I connect it between my incoming midi data and then send it to the imput of the 'vst~'
@carltaylor43, If all you plan on using are the quantizers (NoteQuantizeSimple_BP, NoteQuantize_MIDI_BP and NoteQuantizeDegree_BP) only they need to be in your path. The [p scalemasterdata] sub-patcher I added to your patch contains all the data that the quantizers need to work, and it does not need to be directly connected to anything.
The top level patcher [Scale_Master2] has a couple examples in the lower right quadrant.
@Roman: ScaleMaster doesn't deal with anything other than standard tuning, it just constrains notes to specific note patterns in equal temperament. It will work over MIDI or between a note source and a VST plugin.
also, vst~ instruments, last i checked, don't take straight note numbers in Max - you need to do some processing to turn them into proper MIDI/VST note events - check out the qs.vstizer abstraction in here: https://cycling74.com/tools/grosse-quickstart/
i found that using js it was a lot easier to handle this sort of translation than max, even with my dismal js skills!
Hi everyone, sorry to bring back a post from 2012! I'm trying without luck to get Scale Master to work.
If I load the main ScaleMaster2 max patch and patch up the notein through to the noteout in the examples section (bottom right) I can verify that scale master is quantizing - however it seems stuck in major. Selecting a different scale in the drop down box does nothing (see screenshot).
Can anyone help with where I'm going wrong please? I've tried the stripped back examples above and there's definitely something funny going on - I can't for the life of me get it come out of major.
I have the whole ScaleMaster 2 folder (and subfolders/patches) etc. in both my Max 7 library folder and in my Projects/patches folder so they should, to my knowledge, be within my Max search path.
I'm coming back to this after a week or so and have realised that the Max Console is displaying two errors when I open the patch:
Coll - refer: User ToTable12Name is not a coll
Coll - refer: UserToTable36Name is not a coll
I can't find where these coll's are / are meant to be to see if I can figure out what's going wrong. Any help greatly appreciated. I'd really like to get this scale database working for my patches.
All the best,
I also tried this out and I have some problems.
I sort of got it working when I moved all the files to the same folder as my main patch.
But for some reason it does not read all the scales?
For example; I can use it with the scale for "Fifths" or "PentaMaj" just fine but if I try to use "Octaves" or "Fourths" it just returns the error message "refer: Fourths_12 is not a table".
I do not really get this.
All scales are in the same master txt document, why can it read some of them and not others?
I found the structure of the whole patch a bit confusing.
Just wanted to try scale quantization and I guess this patch do a lot more things than that...