Thanks a lot!!! I really appreciate it.
Thank you Davide!!! Just a note… i have no life any more… i am just playing with Scaler 
The new categorization is Excellent.
Also added an additional variant of Wrapper. Scaller 3 is wrapped in a MIDI instrument for the possibility of hearing the Scaler sounds.
Liminal sphere allow multi out in ableton from there looper by including plugins called listeners which act as a go between from ableton and the app, why cant Scaler use a similar arrangement also Unify can route multi outs in ableton if a vst that has that functionality is hosted within unify.
new device published
Glad to see this Davide, is it not possible to also add some form of midi routing within ableton like liminal sphere do with listeners or unify does when hosting vsts that can route midi.
Cheers feom Bristle
I’m using your 1.0.1 wrapper and looked at your video. Are the sounds from your Kontact instruments or the Scaler internal sounds. I can only get it to play external instruments. Am I doing something wrong? Thanks in advance.
Scaler 3 Wrapper with Reciever - play only external instruments on all tracks
Scaler 3 iWrapper with Reciever - play Scaler 3 sound on track with Wrapper and external instruments on tracks with Reciever
Check all devices on m4l site
Oops. Sorry JRoot3D. Just noticed iwrapper. Great job! Thanks.
This issue might get resolved if somehow Scaler exposed some sort of a simple API that may be called from a M4L device and signal scaler to load / save its current state in a file with the same name as the ableton project… just an idea for @davide and his team…
Raise the ticket to Ableton Support with a request for Multi-Out MIDI Support
I was just registering to bring to the community some alternatives. With my solution Scaler is saving the current settings, there is no need for MaxForLive, there is no need to host Scaler in another different (paid) platform.
I solved using the already built in Virtual midi ports in OSX and PlugData (an amazing Open Source Project).
1- First, In your mac you need to activate the virtual port IAC Driver. Is already installed in your system. (I believe for windows there is something similar called midiloop, or something like that). This is a virtual midi cable, what ever you send to this midi-out port it will appear in midi-in.
-
Install PlugData, is an evolution of PureData but is made to be integrated in Daws as instruments and effects VSTs. Is a vissual programming language and you can build your own patches.
-
In your Ableton Live, load you Scaler 3 normally. Inside your Scaler 3 Mixer, and create several tracks. Forget the midi channel in the timeline view of Scaler3, focus in the Mixer View and add a PlugData FX
Before anything, change the midi settings of PlugData to send midi out through the virtual port only (disable the rest)
-
Create a PlugData patch like this one:
I was implementing a bypass for the audio FX information (adc dac) and what ever midi that come from the midi in (is only the midi information from that specific track) it will me sent to the Virtual midiport in the channel you specify (increase or decrease with the button. You can find the patch in this message (zip file) if you have problems to buid it.
For some reason, the peeople from scaler dont send (to the individual FX tracks) the same midi channel you set in the track timeline. AS far as i saw is always the channel 2, but with this hack you can send the track midi to the channel you want.
-
Go to Ableton, and enable to Track the virtual port
-
And finally, go to your Ableton track (with the instrument you want to play), selec “Midi From” the virtual port and choose the Channel you setup in Scaler.
Two messages for the scaler devs:
- It would be amazing if Scaler (hosted in Ableton) could write directly to the virtual midi port (with this solution we could avoid to use plugdata).
- If not possible, at least you could, inside Scaler, send to the individual mixer Track FX the same midi channel as the user select in the track timeline, with this solution we avoid the need to setup manually the channel in the PlugData plugin.
PS for Scaler Sales: Do you have discount coupons for contributions like this one? Im still in the trial of scaler 3 and checking if fits my needs.
PS2: I was taking screen shots of the process, but for some reason this stupid post editor was complaining about embeding media in a post. So no pictures.
midibridge.pd.zip (756 Bytes)
Hi Davide,
I have installed the LoopMidi product and, with one exception, it works fine with Scaler in Ableton.
In my test set I have one instance of Scaler running two Ableton instruments.
When I play Scaler directly it outputs to each of the Ableton instruments on discreet MIDI channels.
So, when I play from Scaler everything works fine. The routings are correct because the instruments are playing their assigned chords and melodies and the MIDI information for each Scaler track is not shared between the Ableton tracks.
But, when I run the set using Trigger Notes embedded in Ableton, only the Main Track’s instrument plays.
It is as though the Melody track doesn’t know Scaler is running.
Have you heard of anyone encountering this issue or do you know what the solution might be or, perhaps, I am missing something concerning Trigger Notes.
The LoopMIDI solution is straight-forward and appears to be a good solution until Ableton updates their DAW, but I would really like to use Trigger Notes to control Scalers output.
Thanks.
Why not just uploading the picture instead of embedding?
Hi @kkatzer it sounds like Scaler 3 is working as intended. Currently (as of Scaler 3.2) only the main track chords respond to MIDI trigger notes. However one of the recently revealed features in the upcoming Scaler 3.3 update is the ability to bind multiple tracks, which should allow you to accomplish what it sounds like you are trying to do, where while tracks (melody track etc.) accompany triggered main track chords.
Whilst this feature is currently in development, Davide posted a quick first look video recently on the forum. Scaler 3.3 First Look - Multi-Bind Performance (early preview)
Thanks for the update.
I look forward to 3.3.