Comments by Oddeo
This is such a beautiful device! All of the functions are laid out well on the Push. I'm quite sad to find that it's not working on my new Push 3 Standalone. Any insights as to why, or if the fix might be simple? I would so very much love to have this sequencer work in standalone mode.
Do you have any plans to make it Push compatible so that it could work on Push 3 Standalone?
I second the request for midi mapping. I understand that it makes undo less usable, but I crossed that bridge many moons ago. Being able to map a CC message to the Insert and Capture Scene feature would solve a workflow issue I’m running into with Touchable Pro.
Great device! The one issue I'm having troubles with is that live.banks does work correctly. I can add banks and add the parameters I want to those banks, but as soon as I save the device, Push 2's display updates the bank names correctly, but none of the parameters I mapped in the live.banks edit screen are showing up, completely differently parameters show up (in alphabet order). When I edit the device in max again and check the live.bank setting, the settings I originally made are still there, but Push still won't display or control those parameters.
Has anyone run into this issue and/or know a way to resolve it?
Thanks - Neil
Has anyone run into this issue and/or know a way to resolve it?
Thanks - Neil
Elbo, I greatly appreciate you taking the time to respond. Learning that the live.arrow object was the culprit was super helpful! parameter mode was already disabled on SSmooker's device. Since the incr/decr buttons are not important to me, I went ahead and just amputated them altogether. Which fixed the issue.
Regarding the live.dials that are not showing up in live.banks, I played around with it some more and still haven't figured out why some are missing. For me, it's not that big of an issue, as I do most of my TR-S8 tweaks on the actual unit, not Push, so I won't loose sleep over it. The initial program change was the main focus, and you helped me resolve that. Thank you again!
Regarding the live.dials that are not showing up in live.banks, I played around with it some more and still haven't figured out why some are missing. For me, it's not that big of an issue, as I do most of my TR-S8 tweaks on the actual unit, not Push, so I won't loose sleep over it. The initial program change was the main focus, and you helped me resolve that. Thank you again!
Elbo,
I'm using SSmooker's TR-8S version of your patch. Great patch, by the way.
My main question is about the Program Change on initialization. For some reason, any time I load my main template containing the TR-8S controller, it always starts on program 01-02 instead of 01-01. Any ideas why? (it seems trivial, but really jacks up my template workflow).
A less important question is about a live.bank I added to the patch. The bank names show up per my live.bank setting, but the controllers that I assign to each bank using live.banks do not show up when using the Push. Also, in live.bank I'm able to see all controls except for the controls for these:LT, MT, HT, RS, CC, RC. Any insights on the live.bank this too?
Thanks in advance for taking the time to help.
I'm using SSmooker's TR-8S version of your patch. Great patch, by the way.
My main question is about the Program Change on initialization. For some reason, any time I load my main template containing the TR-8S controller, it always starts on program 01-02 instead of 01-01. Any ideas why? (it seems trivial, but really jacks up my template workflow).
A less important question is about a live.bank I added to the patch. The bank names show up per my live.bank setting, but the controllers that I assign to each bank using live.banks do not show up when using the Push. Also, in live.bank I'm able to see all controls except for the controls for these:LT, MT, HT, RS, CC, RC. Any insights on the live.bank this too?
Thanks in advance for taking the time to help.
@killihu Any plans to integrate with Push? I would happily pay twice your price if I could do the main sequencing, probability and track length (poly) on the push. I use Skinnerbox Time, which is a great start, but your device would be king if it was push-friendly.
I just purchased the 2.0. Everything seems to work correctly except that the scrub cursor does not follow the track selection (up and down arrows). Scrub cursor stays on one track regardless of my up and down track selections. If I reach for the mouse and select a track or clip, the cursor follows right along, but that obviously defeats the purpose. Am I just missing something in the instructions?
Great device! Would love to see parameters automatically available for control. It would be great to tweak it using my Push2, rather than mouse clicks.
Also, I am curious. Does your version have any feature that PXT-Live does not have? I'm not trying to pin you two against each other,but I would be curious as to pros and cons of each.
Hi Crampe,
Thank you for the reply. I both agree with you and disagree with you.
There is still something in me that enjoys some aspect of the way I had to arrange using my old Korg Triton (maybe I am crazy). But I love being able to turn on the monitor, use my mouse and make fine adjustments for micro edit stuff.
I would love to see clips showing up horizontally in the arrangement view like they do vertically in the session view. As the arrangement plays, they scroll. You select a clip and hit duplicate it duplicates horizontally. You select a clip and hit delete, it deletes it. Etc etc. I think you get the idea.
I love the idea of not monitor for 80% of the work and being able to go over to the monitor and mouse when you really need to do some micro work or do some quick drag and drop.
I can dream. Either way, thanks for the reply.
Thank you for the reply. I both agree with you and disagree with you.
There is still something in me that enjoys some aspect of the way I had to arrange using my old Korg Triton (maybe I am crazy). But I love being able to turn on the monitor, use my mouse and make fine adjustments for micro edit stuff.
I would love to see clips showing up horizontally in the arrangement view like they do vertically in the session view. As the arrangement plays, they scroll. You select a clip and hit duplicate it duplicates horizontally. You select a clip and hit delete, it deletes it. Etc etc. I think you get the idea.
I love the idea of not monitor for 80% of the work and being able to go over to the monitor and mouse when you really need to do some micro work or do some quick drag and drop.
I can dream. Either way, thanks for the reply.
Hi Crampe,
Thank you for the reply. I both agree with you and disagree with you.
There is still something in me that enjoys some aspect of the way I had to arrange using my old Korg Triton (maybe I am crazy). But I love being able to turn on the monitor, use my mouse and make fine adjustments for micro edit stuff.
I would love to see clips showing up horizontally in the arrangement view like they do vertically in the session view. As the arrangement plays, they scroll. You select a clip and hit duplicate it duplicates horizontally. You select a clip and hit delete, it deletes it. Etc etc. I think you get the idea.
I love the idea of not monitor for 80% of the work and being able to go over to the monitor and mouse when you really need to do some micro work or do some quick drag and drop.
I can dream. Either way, thanks for the reply.
Thank you for the reply. I both agree with you and disagree with you.
There is still something in me that enjoys some aspect of the way I had to arrange using my old Korg Triton (maybe I am crazy). But I love being able to turn on the monitor, use my mouse and make fine adjustments for micro edit stuff.
I would love to see clips showing up horizontally in the arrangement view like they do vertically in the session view. As the arrangement plays, they scroll. You select a clip and hit duplicate it duplicates horizontally. You select a clip and hit delete, it deletes it. Etc etc. I think you get the idea.
I love the idea of not monitor for 80% of the work and being able to go over to the monitor and mouse when you really need to do some micro work or do some quick drag and drop.
I can dream. Either way, thanks for the reply.
Does your device display the current transport position anywhere on the push readout? This seems to be missing in over scripts, but seems mandatory for me. To me the reason I love push is that I have monitor turned completely off. Using push for arrangement editing would require such a read out.
Joe,
I run Live 64 and Max 64, so it is not that.
If you have JunoRouter running in MaxRuntime, you have your Juno MIDI selected in the pull down, you are using the most up to day version of Juno106Control running in Live, and the Function switch on the back of your Juno 106 is set to III, I am not sure how else to help you.
I don't understand why you have the routing you do, but that is your thing. My routing is Live (Juno106Contol) > 828 MIDI OUT > Juno 106 & MaxRuntime (JunoRouter) > 828 MIDI OUT > Juno 106
That is it. Works for everyone I know that uses it.
I sincerely hope you are able to figure out what is throwing your system off. If you do, please share in case someone else runs into the same issue.
Best of luck!
Neil
I run Live 64 and Max 64, so it is not that.
If you have JunoRouter running in MaxRuntime, you have your Juno MIDI selected in the pull down, you are using the most up to day version of Juno106Control running in Live, and the Function switch on the back of your Juno 106 is set to III, I am not sure how else to help you.
I don't understand why you have the routing you do, but that is your thing. My routing is Live (Juno106Contol) > 828 MIDI OUT > Juno 106 & MaxRuntime (JunoRouter) > 828 MIDI OUT > Juno 106
That is it. Works for everyone I know that uses it.
I sincerely hope you are able to figure out what is throwing your system off. If you do, please share in case someone else runs into the same issue.
Best of luck!
Neil
Do you have MIDI Function set to III on the back of your Juno?
Beyond that, I am not sure what else could be the issue.
Beyond that, I am not sure what else could be the issue.
Be sure to read all of the instructions and download the right items on this page: http://www.neilbufkin.com/NB/News/Entries/2012/6/30_Juno106Control_-_Big_Update_by_Fabrizio_Poce.html
I am not sure what the issue may be, as I am not experiencing this. I would go to my website and make sure you have all of the latest versions http://www.neilbufkin.com/NB/News/Entries/2012/6/30_Juno106Control_-_Big_Update_by_Fabrizio_Poce.html
I hope this helps.
Neil
I hope this helps.
Neil
I'm not sure. But if you try it, please let us know.
Great device! Thank you for sharing your work.
I believe the JunoRouter is frozen in the main download. If you need to download it individually, you can do so here:
http://www.neilbufkin.com/NB/News/Entries/2012/6/30_Juno106Control_-_Big_Update_by_Fabrizio_Poce_files/JunoRouter.maxpat
Enjoy!
Neil
http://www.neilbufkin.com/NB/News/Entries/2012/6/30_Juno106Control_-_Big_Update_by_Fabrizio_Poce_files/JunoRouter.maxpat
Enjoy!
Neil
Crap...that reminds me that I need to fix my website.
I am not at my computer, and it has been a while since I gave this any thought, but if I remember right, the router is saved in the file that is posted here. I believe you just need to unfreeze it.
I am not at my computer, and it has been a while since I gave this any thought, but if I remember right, the router is saved in the file that is posted here. I believe you just need to unfreeze it.
I think K-flux is a well designed device and find it to be a simple solution for quick beat sketching. In an ideal world it would better meet my work flow if the following features were added: (A) double the size/number/resolution of the beat grid (B) Leave the "on" and "accent" function of the main page, but add a tab with greater velocity control. (C) Add the ability to load a sample in parallel of each drum sound. This would add the ability to mix the K-device kick or snare, for example)with a sample kick or snare of your own.
Eventually I hope to see a MFL patch very similar to Logic's Ultrabeat. Now if I could just quit my "day" job I would get right on it.
Eventually I hope to see a MFL patch very similar to Logic's Ultrabeat. Now if I could just quit my "day" job I would get right on it.
alexlancaster, some of the standardized MIDI CC's (cutoff, eg, port time) might work, but it is definitely not designed for the Radias.
I meant to say 1.2 was NOT the most recent. Double Ooops...
I just realized today that the version I have had posted (1.2) was the most recent. There was in issue with the LED's turning orange instead of staying red as they are supposed to. Today I uploaded the version I thought I uploaded a couple months ago (1.3) which fixes the color discrepancy. Ooops.
Neil
Neil
jenz & zip,
Be sure that you have JunoRouter running in MaxRuntime. Without JunoRouter none of the SysEx will make it to the Juno.
There are detailed instructions on my website if you need them.
Chearz
Be sure that you have JunoRouter running in MaxRuntime. Without JunoRouter none of the SysEx will make it to the Juno.
There are detailed instructions on my website if you need them.
Chearz
I created this editor so that I could use Ableton Live?s automatic Macro mapping and MIDI Map to easily control and automate my Korg M3?s various parameters. The M3 Editor provided by Korg gives a great deal of control over the M3 when using a mouse. However, the M3 Editor plug-in is limited to just a small handful of parameters that can be automated. I personally would rather use a physical knob or button than a mouse. While the hardware interface of the M3 does give you a great deal of control, I do most of my production sitting in front of a computer now a days. On my desk and in my work area there is not enough room for the M3 to sit right in front of me, but there is enough room for a smaller MIDI controller (nanoKey & APC40 in my case). M3Kontrol gives me easy access to all of the parameters I use most on the M3 while staying within my production/recording environment.
EVERY function on the M3Kontrol GUI can be easily mapped to any physical controller and automated.
The Pads are set to a velocity value of 127. The way Ableton?s MIDI Map function works there is no way to map a key to the pads and retain the key?s velocity information (I tried).
The X-Y pad monitors your mouse button?s up and down value. This means if you grab the center circle with your mouse, move it in any direction and release the mouse button the circle will return to the center position. Note, the X-Y function on the actual M3 is not something that it turned on, per say, it is always on, the X-Y MODE button on the M3 just gives you access to it using the M3?s touchscreen. Since the X-Y pad on the M3Kontrol GUI gives you instant access to the X-Y parameters there is no need to turn it on. The HOLD button on the M3Kontrol functions much the same way the HOLD button on the actual M3 does, but does not turn no the hold function on the actual M3. (See the * note below regarding X-Y automation)
The GE Select menus function like you would probably expect. Do note that when in COMBI mode you must select the module you want effect using the GUI?s MODULE CONTROL button. In PROG mode the MASTER module control the GE functions. When switching from COMBI mode to PROG mode the MASTER module will be automatically select.
MACRO Mapping. M3Kontrol was designed to take advantage of Ableton?s MACRO mapping. The first 8 knobs on the left of M3Kontrol will MACRO map to any standard controller with 8 knobs or sliders (if Ableton recognizes it). If you have an APC40 or something similar the rest of the functions are automapped as well. On the APC40 click Shift + Device Control 2 to control the next 8 knobs, Shift+ Device Control 3 to control the ?KARMA Slider? knobs, Shift + Device Control 4 to control the X-Y parameters, the Program scroll, the GE Category and the GE scroll. (Note that by default the APC40 knobs send values of 0-127, so when trying to control the GE scroll using a knob you may not get desirable results (There are 3,199 GE?s in the list and only 128 values to the knob, get it?). Since the APC40 does have endless encoders this can probably be overcome with a custom patch.
As some of the corresponding CC's can be changed manually on the M3
Global page (i.e. pads, KAMRA sliders, etc) you may need to make a few changes in the patch. Click the M4L edit button to view instructions found in the Patching window. Anything that may need to be changed is highlighted in green. The knobs on the left are mapped to the parameters I use most, however, with a little editing you can change these to control the parameters you use most.
With the exception of the program change number, M3Kontrol is NOT bidirectional. If you make changes on the actual M3 these will be not be reflected on the M3Kontrol GUI. So, if you select a Program that has MFX2 turned on, the M3Kontrol GUI has this turned off by default, so in order to turn it off on the M3 you will have to turn it on in the GUI then off.
I hope M3Kontrol is useful to you in your setup.
READ THIS!!! For this patch to work properly M3Router.maxpat must be running in MAX Runtime. M3Router.maxpat comes imbedded in the M3Kontrol.amxd file. To access it click the Unfreeze button at the bottom left of the patch window. Max will create an unfrozen folder on your computer containing any dependent files (i.e. KARMA Logo, M3 Logo, and M3Router.maxpat) Place the M3Router.maxpat file where you can easily access it any time you plan to use M3Kontrol.
* Ableton records automation for X-Y movements, but is currently causing this specific automation to be disabled (the ?Back to Automation? turns on). I am not sure what is causing this behavior but am working to resolve the issue.
Enjoy!
Neil
EVERY function on the M3Kontrol GUI can be easily mapped to any physical controller and automated.
The Pads are set to a velocity value of 127. The way Ableton?s MIDI Map function works there is no way to map a key to the pads and retain the key?s velocity information (I tried).
The X-Y pad monitors your mouse button?s up and down value. This means if you grab the center circle with your mouse, move it in any direction and release the mouse button the circle will return to the center position. Note, the X-Y function on the actual M3 is not something that it turned on, per say, it is always on, the X-Y MODE button on the M3 just gives you access to it using the M3?s touchscreen. Since the X-Y pad on the M3Kontrol GUI gives you instant access to the X-Y parameters there is no need to turn it on. The HOLD button on the M3Kontrol functions much the same way the HOLD button on the actual M3 does, but does not turn no the hold function on the actual M3. (See the * note below regarding X-Y automation)
The GE Select menus function like you would probably expect. Do note that when in COMBI mode you must select the module you want effect using the GUI?s MODULE CONTROL button. In PROG mode the MASTER module control the GE functions. When switching from COMBI mode to PROG mode the MASTER module will be automatically select.
MACRO Mapping. M3Kontrol was designed to take advantage of Ableton?s MACRO mapping. The first 8 knobs on the left of M3Kontrol will MACRO map to any standard controller with 8 knobs or sliders (if Ableton recognizes it). If you have an APC40 or something similar the rest of the functions are automapped as well. On the APC40 click Shift + Device Control 2 to control the next 8 knobs, Shift+ Device Control 3 to control the ?KARMA Slider? knobs, Shift + Device Control 4 to control the X-Y parameters, the Program scroll, the GE Category and the GE scroll. (Note that by default the APC40 knobs send values of 0-127, so when trying to control the GE scroll using a knob you may not get desirable results (There are 3,199 GE?s in the list and only 128 values to the knob, get it?). Since the APC40 does have endless encoders this can probably be overcome with a custom patch.
As some of the corresponding CC's can be changed manually on the M3
Global page (i.e. pads, KAMRA sliders, etc) you may need to make a few changes in the patch. Click the M4L edit button to view instructions found in the Patching window. Anything that may need to be changed is highlighted in green. The knobs on the left are mapped to the parameters I use most, however, with a little editing you can change these to control the parameters you use most.
With the exception of the program change number, M3Kontrol is NOT bidirectional. If you make changes on the actual M3 these will be not be reflected on the M3Kontrol GUI. So, if you select a Program that has MFX2 turned on, the M3Kontrol GUI has this turned off by default, so in order to turn it off on the M3 you will have to turn it on in the GUI then off.
I hope M3Kontrol is useful to you in your setup.
READ THIS!!! For this patch to work properly M3Router.maxpat must be running in MAX Runtime. M3Router.maxpat comes imbedded in the M3Kontrol.amxd file. To access it click the Unfreeze button at the bottom left of the patch window. Max will create an unfrozen folder on your computer containing any dependent files (i.e. KARMA Logo, M3 Logo, and M3Router.maxpat) Place the M3Router.maxpat file where you can easily access it any time you plan to use M3Kontrol.
* Ableton records automation for X-Y movements, but is currently causing this specific automation to be disabled (the ?Back to Automation? turns on). I am not sure what is causing this behavior but am working to resolve the issue.
Enjoy!
Neil
synnack, thanks for the tip. You are right. since the .maxpat was not a file actually used in the .amxd file all I had to do was "add dependency"
The file has been updated. No need to go to the external link.
The file has been updated. No need to go to the external link.
I wrote JunoControl.amxd to make automating the Juno-106 much easier in Ableton Live. The knobs are set to automap like macro controller knobs (on the APC40 you can access the 8 knobs on the right by holding shift and pressing 2). To flip the switches up or down click on the text rather than the actual switch (i.e. + or - for the ENV POL).
With the exception of the program change display, this patch is unidirectional and will not sync to any changes made on the Juno-106 hardware. (If someone would like to put in the time to code this patch to be bidirectional that would be great)
To overcome the SysEx messaging issue currently posed by Live I wrote a router called JunoRouter.maxpat. This MUST be open in Max Runtime. Download it here: http://www.neilbufkin.com/Neil_Bufkin_2.0/Neil___Downloads_files/JunoRouter.maxpat
Suggested instructions:
Drop JunoControl.amxd on a MIDI track in Ableton Live
Drop an External Instrument to the right of JunoControl. Set the MIDI and Audio routings according to your setup.
Right click JunoRouter.maxpat and ?Open With? MAX Runtime.
Select the MIDI Port your Juno-106 hardware is connected to. Set this up in the Audio/MIDI application(Mac). (I am not sure what the procedure is for Windows OS)
That?s it.
All of the buttons and knobs can be mapped and automated using Live?s MIDI learn function.

There is one issue that I have not been able to figure out.....you have to click on a button or switch twice for the setting to be made on the Juno hardware (first click changes on the M4L GUI, second click changes on the Juno). This is my first M4L patch so if you know what the issue is with this please let me know.
I hope this patch is useful for you Juno-106 owners. It sure is for me.
Enjoy!
Neil
(Description is not showing up for some reason)
With the exception of the program change display, this patch is unidirectional and will not sync to any changes made on the Juno-106 hardware. (If someone would like to put in the time to code this patch to be bidirectional that would be great)
To overcome the SysEx messaging issue currently posed by Live I wrote a router called JunoRouter.maxpat. This MUST be open in Max Runtime. Download it here: http://www.neilbufkin.com/Neil_Bufkin_2.0/Neil___Downloads_files/JunoRouter.maxpat
Suggested instructions:
Drop JunoControl.amxd on a MIDI track in Ableton Live
Drop an External Instrument to the right of JunoControl. Set the MIDI and Audio routings according to your setup.
Right click JunoRouter.maxpat and ?Open With? MAX Runtime.
Select the MIDI Port your Juno-106 hardware is connected to. Set this up in the Audio/MIDI application(Mac). (I am not sure what the procedure is for Windows OS)
That?s it.
All of the buttons and knobs can be mapped and automated using Live?s MIDI learn function.

There is one issue that I have not been able to figure out.....you have to click on a button or switch twice for the setting to be made on the Juno hardware (first click changes on the M4L GUI, second click changes on the Juno). This is my first M4L patch so if you know what the issue is with this please let me know.
I hope this patch is useful for you Juno-106 owners. It sure is for me.
Enjoy!
Neil
(Description is not showing up for some reason)
Thank you! I have been hoping someone would post some Jitter work on here.
Very useful patch. This is something we have all been asking for for a long time.
I wish this device worked inside of an instrument rack (everything must be unpacked for it to work properly) so that I could save device-specific settings.
Overall, great job!
I wish this device worked inside of an instrument rack (everything must be unpacked for it to work properly) so that I could save device-specific settings.
Overall, great job!
Thanks for the response. Most max devices work fine: https://help.ableton.com/hc/en-us/articles/8506527153308-Push-standalone-Max-for-Live-Device-Compatibility
The other sequencers I use all work, but on one of them the parameters are not available in live.banks for control. For your device, however, all of the parameters are showing up just fine, which gives me hope, it’s just the sequencer clock that’s not running. I hope I can figure out how to get yours running, as it would be my primary work horse on the P3S.