Project to create a Yamaha FS1R Controller/Editor
I am attempting to build a suite of tools in Max 7 for my Yamaha FS1R synthesizer which sits in a rack not too accessable from my seat.
Right now I have a functioning Max for Live device (amxd) that allows you to choose a Performance and control some parameters like attack, formant, cutoff, reverb, etc. All these parameters get mapped nicely to the Ableton Push’s display. The Performance list pulls from a factory presets list, and you can change the names in Max.
I am working on a Performance editor, but this requires sysex which does not play nice with Live, so it will be an OS X app. All it really does now is loads the current performance from the FS1R, and maps some of the parameters.
This is all posted at GitHub to encourage any other FS1R owners interested in contributing.Source Download https://github.com/tekfunk/FS1ReMOTE/archive/master.zipProject Page https://github.com/tekfunk/FS1ReMOTE
Hey I have FS1r and am keen to get a full max msp editor happening. Not personally interested in standalone or M4L device though. I can contribute. What's the plan of attack?
Joe
Yeah also interested in helping out, I was thinking about pretty much duplicating this:
With a M4L device(s) sending data via OSC perhaps to the "app", to get around the Live Sysex problem. Most parameters seem pretty controllable glitch-free when I use the app linked to above with a mouse...
I've posted up what I have so far, feel free to go and download and see if what I've done helps : https://github.com/tekfunk/FS1ReMOTE
FS1R Live is the Max for Live Device. This is working and good for performing once you have your sound designed already.
FS1R Edit is for the Editor. The 1st phase of creating this is making a Performance Editor that will request the current Performance and allow you to edit it. I am using FS1R Editor (good but slow and ugly) with midi monitor to learn all the sysex and parameters. So far It will request the Performance and maps out most of the parameters to my interface. The next steps will be to finish building the interface and mapping the rest of the parameters. Then the next step will be hooking up the editor to send the parameters as well. I have researched it and plan on getting sysex to work with the editor so it can be a M4L device, but want to get it working as a max patch (and app) 1st.
So again, download what I have, or even better, make a branch or fork of my work, mess around with it, and post it. We could keep track of it all on GitHub that way.
Hi Tekfunkdub, did you manage yet to get all those sysex strings into text file by any chance? Joe
I mean, there's this and all buttttt:
Anyone interested in completing some of this project? I just picked up an fs1r and would love to have M4L devices for editing and performance control. I'm new to building my own max devices, but have some experience coding in C and python, and would like to dig into this. It would be nice to have some partners to tackle this one...