I’ll comment that from a workflow perspective one might already have an elaborate layout taking up all of Section C, a layout that you ideally only want to perturb after you have fully auditioned the changes elsewhere (e.g. in Sections A and/or B).
I know we can save/load chord sets from disk (excellent!), and with this capability and some care in how we proceed we can avoid permanent loss of carefully constructed configurations.
So, it’s not a question of “user can’t do”, but it is a question of “most convenient (and efficient) for user to do”. It is definitely most convenient (and efficient) to be able to play a loop anywhere, anytime you want to. In this program, as currently organized, that would mean in Sections A, B, and C.
In no way am I saying this is the highest priority “must do next” item, but it might be low hanging fruit from the implementation POV (famous last words!).
@sj1 Your 2nd quote in the thread nailed my thoughts on this topic. I appreciate the prioritization requirements of any dev effort and I also know that the process is fluid
as ideas and insights into use-cases change.
As David says:
This kind of feature is not about a prescribed workflow or a specific product vision or use case, but instead it is about features that compliment the most scenarios (likely or unlikely). Since Scaler lends itself to exploration and stumbling onto the unexpected, something as utilitarian as looping everywhere playing is available seems a reasonable feature list candidate.
Would you have a DAW that only allows volume control on certain types of the tracks? “its easy, just bounce your midi track to audio and then you can set the level.” is not something you’d likely ever hear.
While UI impact/decisions have to be taken into consideration, Looping is something that happens all the time and all over the UI for reasons only known by the user in that moment. For at least some of us, Section C is where you go to build, tune and play your progressions. Section B is where you go to explore and tune chord voicings and variations while Section A is where you begin searching for and exploring foundational sounds and patterns. In all three cases, efficient looping makes all the difference to the user experience.
So true - I bear the scars and lack of hair for all the ‘only a quick fix’ that have cost endless man days, hassle with the client base, and of course loss of money
Thanks for the feature addition. From comparing subtle voicing differences to finding patterns that work best with certain instruments, Auto Play fundamentally changes how quickly and easily we can explore the huge world that is Scaler.
It also makes for a great synth experimentation tool.
A bit late to the party, but have I missed something here? I just clicked on Autoplay in Section A and it looped, and continued playing when I selected different chord sets from the Songs and Artist menus.
So what will adding a loop button in Section A add?
You did not miss much. The looper (A & B Sections) is just that…a simple looper. What it enables however, is a simplified and seamless way to explore the countless variations that exist w/in Scaler w/out needing to constantly click play. You can start playback and make changes to your heart’s content…something not available before Auto Play.
Depending on how you calculate it, Scaler contains hundreds of thousands of potential variations (@yorkeman can give you the #s). For some us, exploring those variations is a big part of using Scaler. Nothing earth shattering, but very helpful for those of us constantly on the hunt for those happy accidents. When Scaler inspires itself…or fun with recursion - General Discussion - Scaler Plugin - Community Forum
This feature just makes it that much easier.
It doesn’t loop for me. I’m using the latest Scaler 2.7 and the latest Logic Pro. How did you get it Section A to loop? Section C loops fine but even though I have DAW Sync on it won’t loop. Any advice would be greatly appreciated.
Normally, you right-click on the Play button in section A (1). You’ll see AutoPlay:on (2) and the section will loop.
By right-clicking on Play once again, you toggle autoplay.
@Miki Thanks for getting back to me. Yes I know about right-clicking. I actually had Scaler back when you had to right-click on Section C too. I’ve been right-clicking (Section A), tried all sorts of things. I’m using Scaler as a MIDI FX not as an instrument. It worked OK in in Section A before I upgraded to Scaler 2.7. I was hoping the 2 subsequent updates would fix the problem, but they did not. Is there something else I could be missing?
Sorry to hear that looping doesn’t work for you. I’ve just reconfirmed and it all works for me, ven after using audio detect, but as I have a Windows installation I probably can’t help much with this. However just to confirm you say
I assume it is v 2.7.2 that you have installed?
It may help to know which OS you are using as I believe that there may be issues with some of the Apple OSs although I don’t think this has come up as an issue with the OS before.
May I suggest that you could also upload a screenshot of the Main page and a copy of the Scaler state as this may help someone to resolve yout issue.
Yes I’m using Scaler 2.7.2 and MAC OS 12.6.2 Monterey. I’ve attached a screenshot with a very simple project with just one track with a synth instrument and Scaler 2.7 as a MIDI FX. Thanks @ed66 !
Hi @jamieh . To me the whole reason for the functions in SECTION A is to try different things out. So it really slows things down if I have to stop and copy every single iteration down to SECTION C. It would slow things down so much that it would be unusable. (And by the way it used to work for me before upgrading to 2.7)
Hi @mykelnoah111111 sorry to hear you are having trouble with this.
We are having trouble reproducing what you are experiencing as it seems to be working as expected on our end. We are running 2.7.2 on Monterey with the latest Logic also.
Are you running on an Intel chipset or M1?
Could you please download the 2.7.2 installer again from plugin boutique and reinstall it if you have not tried this already.
I understand what you are saying but it takes less then a couple seconds to select all chords on A and choose copy to Pattern 1. If you are looping through all the chords that takes time anyway.
Besides the update did anything else in your chain change? Logic version, OS?
@jamieh, Sometimes work-arounds are necessary, and may even be desirable in some cases where the applicationm does not completely fit an individual requirement; so don’t give up on them, please.
As for the time in this case; 12 x 3 seconds is still less than a minute, and you were trying to find a solution to an individual problem: auto-play not working in section A for @mykelnoah111111. Even @ClaudioPorcellana 's half a hundred is only 50 x 3 seconds, which is less than three minutes.
