Saved states won't load when using scaler3 as midi effect plugin

Scaler 3 Support
,
1

Hi – new scaler using here getting started with scaler3 in logic pro x 11.2.1.

Before diving into the issue itself, I’m going to briefly lay out what I’m trying to accomplish, since this may be expected behavior with the issue being my workflow.

Goal: I want to be able to use scaler’s “Detect Audio” feature on an audio file, capture the chords it detects, then be able to hear those chords through a software instrument of my choice prior to laying them down as midi in my DAW.

To try to achieve this, I’ve set up scaler as an audio effect plugin on my audio track so that it can receive the audio input signal to use the “Detect Audio” feature. From here, I wasn’t sure how else to get the detected chords to play through a track utilizing my software instrument other than to save it and open it up in a scaler instance as a MIDI effect plugin, which then routes into my software instrument (this is my current setup for when I want to use scaler with a software instrument but don’t need to use the detect chord feature, but I’m curious if there might be some alternative workflows that would work better here). However, when I try to load the saved version with the chords detected, none of the chords or any information from that instance show up. (Note that it does correctly load when using scaler as a audio effect plugin or instrument plugin)

So, I’m wondering if this is expected behavior, and whether I could get around this by changing my general approach.

2

Hi @rae, welcome to the forum and thanks for your post.

However, when I try to load the saved version with the chords detected, none of the chords or any information from that instance show up. (Note that it does correctly load when using Scaler as an audio effect plugin or instrument plugin)

That’s interesting – I just tested saving a preset using Scaler 3 Audio and was able to successfully load it via Scaler 3 Control, so it does seem possible.

Just checking: have you dragged the detected chords to the Main Track (Section C) before saving the preset? Scaler won’t retain detected chords displayed in Section A in a preset - only chords added to the Main Track are stored. If you haven’t already, try dragging them down before saving.

As for your workflow, here are a couple of suggestions that might help:

Option 1: Use Live Sync

  1. Detect chords using the Scaler Audio plugin (as you’ve been doing).
  2. Drag the detected chords to the Main Track (Section C)
    *Tip: Click the ‘I’ (Input Monitoring) button on the channel with the Scaler Audio plugin to hear the detected chords.
  3. Create a new MIDI track in Logic with your preferred software instrument.
  4. Add Scaler 3 Control (MIDI Effect plugin) to that new track.
  5. Set the Scaler Audio instance as the Leader. The Scaler 3 Control instance will become a Follower and inherit the Leader’s Main Track.

For more on Live Sync, check the Scaler 3 User Guide: Introduction > Recurring Features > Live Sync (p. 20)

Option 2: Use Logic’s Side Chain Feature to Detect Audio via the Instrument Version

  1. Create a new MIDI track and add the Scaler 3 Instrument version.
  2. At the top-right of the plugin window, use Logic’s Side Chain menu to select the audio track you want to detect.
  3. Scaler will now receive that audio input – you can detect chords just like you would in the Audio version.
  4. Once detection is complete, drag the chords to Section C and use your preferred third-party VST instrument directly on your Main Track

Hope some of this helps. Let us know how you go! Cheers

3

Thanks for the reply, Steven.

Yes, I have the chords in section C.

Hmm, I’ve recorded a few screen grabs for extra clarity, which can be accessed here

I’m noticing that when I save an audio or instrument instance, it wants to save it in the “Scaler 3 Audio”, and when I use scaler control, it wants to save in the “Scaler 3 Control” directory, but I don’t think that should be having any impact?

I’m also noticing that the inverse is an issue as well – The content doesn’t load in an audio or instrument instance if I’ve saved it while using an instance of scaler control.

Thank you for the workflow suggestions! I was just watching a tutorial on live sync the other day, that seems like exactly what I should be doing. Still curious if we can solve this issue with the saved presets in the meantime.

4

Hi @rae, thanks for your reply and for providing the screen grabs – very helpful, and now I can see what’s going on.

You’re using Logic’s Audio Units preset system, whereas I initially thought you were referring to Scaler 3’s internal preset system. Apologies if I misinterpreted your original post.

Without having properly tested this on my end yet, it does seem like Logic may be treating the different plugin types separately, which could be affecting preset recall. We’ll look into this further, but in the meantime I’d recommend using Scaler 3’s internal preset system instead.

You can find more on that under Header Section > Presets, on page 24 of the User Guide.

Great to hear Live Sync seems like the right move for your workflow :slight_smile: