Is there a guide to midi routing for Scaler 3 with Ableton?
When creating several tracks inside Scaler 3 (Main, Bass, Sequence for example) and then giving each it’s own Midi Channel output, the corresponding midi tracks in ableton (set to CH1/2/3 etc) are not receiving any midi at all. Monitor is set to in.
The only option that gives an output is to chose Scaler 3 as the midi Source but then that plays all the Scaler 3 tracks inside one ableton midi track. So Main, Bass and sequence are all sending the midi at the same time to one track which is not what I need.
I don’t use a lot of VSTs so was hoping to do this so I can work with Ableton stock sounds as I write my music.
But you could use Scaler 2 well in ableton still with syncing mutliple instances which is a feature they have removed or hidden.
None of the current advertising or media has suggested there will be any features removed from Scaler 2 nor do they suggest that Ableton would have any limitations. In fact they list ableton 1st in the list of daws Scaler 3 is compatible with.
If you like Scaler 2.X more. There is no law to stop you using Scaler 2 further. Scaler 2.0 was not that great either. But over the years the scaler team added all those wonderful features for free. Same is going to happen with Scaler 3.0. The new plugin might not have all the bells and whistles you want, but it was time get to the market with it.
Also the scaler team did everything possible to make sure people knew what to expect. There were a lot of videos to watch and learn how Scaler 3.0 works.
Using Ableton live is a choice. When I bought it, I knew it would not manage midi routing like other professional DAWs. It is not exactly a secret. That is the reason I also work with Reaper and Cubase which can do this easily.
Watched all the videos pre release and didn’t see any of them advising that funcionality would be limited by certain daws.They have advertised the product as compatible with Ableton.
I can of course continue to use Scaler 2 but not everyone has the funds to throw away on products that don’t meet expectations. Also without feedback such as mine and the other threads about this matter the manufacturers would perhaps be unaware to provide other funtionality as time goes on.
I have the same problems with Bitwig that has a better routing than Ableton
There are situations where the embedded mixer and its strange routing is a problem, for example if you want that SC3 send its output to Channel 1 and 2, currently impossible if the plugin to drive is inside SC3
Not all noise-producers ( ) have the same needs and workflow
But you are right; using SC3 is not mandatory
And the same applies to SC2 or any other tool, BTW
I respect your opinion but disagree on this. It was clearly stated version 3 could be used as version 2 but that is not the case. I personally don’t have the money or time for multiple DAWs and have to selectively spend my money as I did with the upgrade fee to V3.
It is well know that MIDI routing has limitations in Ableton but being able to sync multiple instances of Scaler 2 was well used and discussed in training videos. Not having this feature in V3 breaks a lot of workflows for people, so it is more than just a convenient feature.
If Scaler 3 has made the decision to move forward (due to it’s radically different design) and away from v2-era sync instances - that is their call.
And as others have already stated - if the new way of routing does not work for your workflow OR your DAW due to built-in shortcomings - v2 is still 100% usable and you can stay with that.
But to be fair the Scaler crew - I followed this rollout with great interest but nowhere did I ever see any documentation stating that every single exact bit of v2 functionality was to be 100% replicated in v3.
If this was stated somewhere - I am happy to be wrong.
“It works only if you use SC3 to drive external plugins”
Which seems to deprecate the need to have synced instances. And yes - I realize this is a DAW specific routing capability. In Studio One this is easy peasy.
But I have not found any evidence of SC3 allowing us to “route” a 10 track internal composition that uses 10 third party VSTis and send that to the DAW. That is not a thing.
That is a fair statement - but don’t read too much into it.
I read “You can use it just like Scaler 2” and think - “Nice - I can load v3 it in my DAW and build a chord progression and drag it to the timeline - just like I did in v2”. Check.
I do not read this thinking - "Purchasing v3 will (with a 100% guarantee) replicate everything that was technically possible in v2
People have different views. In no way did I understand it as - "Nice - I can load v3 it in my DAW and build a chord progression and drag it to the timeline - just like I did in v2”.
I understood it as for what was said…i.e. “You can use it just like Scaler 2”.
Completely agree that everyone will have their own take.
Just watched the bit in the video you linked. Nowhere in there is any evidence of 100% replication of all S2 function and certainly not syncing instances or anything like that.
If you were seriously basing Davide simply saying (in a pre-release video) “You can use it just like Scaler 2” and took that to mean “everything” exactly like Scaler 2 - that is an assumption you made and now need to be good with.
And let’s take a breath here - it’s early day 1 of this. I am sure Davide will swing by when the dust settles and give everyone some clarity soon. But that does not mean you will be able to use V3 in precisely the same manner as v2.
Again - there is no requirement to upgrade. If you did upgrade and this “difference” (amongst many others that I am sure are yet to be discovered) doesn’t work - seek a refund and there you go.
I might do that but I think some of us just want to be able to use what is an incredible tool in the way we want to or have been used to as per our understanding of pre-release information. That’s what we’re trying to get to the bottom of. And we “clearly” didn’t know until we upgraded.
Your language seems to suggest that you’re offended in some way and I’m sorry if that’s the case. No has said “100% replication” though apart from yourself. You seem to have an expectation and an understanding and others have a different view. My understanding of “You can use it just like Scaler 2” and “The passmark for me was always that you can use it just like Scaler 2” is just as it’s written. My workflow uses ‘Sync’ on hundreds of projects and it has worked well. It seems others have workflows that they expected to work and they currently do not. I think you’re the first one to mention refunds also. I’m sure most will understand that it’s early days and there will be issues to iron out but I don’t think you should dismiss different ways of working as less important than yours.
It disappointing, IMO SCaler 2 is better in many areas. I don’t think it’s crazy to expect an improved version of software to retain its core functionality. But some things are just harder or not possible.
Certainly not dismissing your workflow in any way.
But your language seems to suggest that you have been “wronged” in some way by the arrival of v3 - when i reality - you simply made assumptions that did not come to pass.
) have the same needs and workflow