Yep go to your user library not your shared library
![]()
Note for Scaler 3.1 we are going to simply this whole process and allow batch import right in the user category. Aiming for some nice folder management right there too.
This is one area where I think we let our users down by not making the above clear. Please give us a few weeks to rectify and apologies.
Hey jay. If you are on a Mac the precised paths are:
It makes no logical sense that there was not a way of grabbing (importing) all user chord sets from Scaler 2 when installing Scaler 3.
If you can scan for plugins if multiple sorts this should he here. Having to go through and import chord sets 1 by 1 is a huge pain and shouldnāt att all be necessary!
I followed exactly the process outlined above for Mac OS and nothing shows up in scaler 3. Very weird.
I notice that scaler 2 chordsets are .xml and scaler 3 are .s3p I wonder whether this is my problem?
I have tried to import chord sets into scaler 3.0 please help
Hi @dreamsdewhappen, and welcome to the forum.
Posting this link in case it might help!
What you just explained drives me a lot more crazy than the way youĀ“d do it in Scaler 2, just sayinā¦
This is also where I found the chordsets; worked fine for me. Copied over 250 xml files and they show up just fine in Scaler 3
Hi Davide,
Thanks for following up on this, and good to hear that the preset issues that users are having are being addressed. To answer a question you asked earlier: yes, I happen to have a bunch of Scaler 2 files that are saved as āsessionsā. I am happy that Scaler 3 is moving towards a simpler file system. However, will a future update allow for the import/conversion of chords from Scaler 2 sessions to Scaler 3 chord sets, you think?
Hope my question is clear, and Iām not getting my terminology mixed up.
Hi @Hajee and Welcome to the forum. Not sure on ability to import sessions. Thereās lots on our roadmap and its a fine line between focusing on our existing users (which we primarily do) and also supporting development of the platform we have.
Thank you for the update!
This partially worked for me in 3.1 (~80% conversion), but some of my XML files are not showing in the āUserā folder. Is it normal for some v2.x chord sets to not be compatible with v3.x? Did anyone else have this experience?
Iāve tried several times today to get Scaler 2 chord sets to load in Scaler 3 and it just will not happen. I have the Musician Paradise 80ās pack for Scaler 2.5 and it works great there. Iāve copied to the ProgramData > Scaler Music > Scaler 3 > ChordSets > Imported as well as created a folder on the same level as Imported. The folders show up but no files show in Scaler 3. Iāve restarted Scaler and the system (Win 11 Pro). Running Scaler 3.1.2 and tired everything suggested here but no go. As stated works fine in Scaler 2.
Any of solutions in this chain and few more I tested, just not working in Scaler 3.20, Not in stand alone app or VST3 plugin version on MacOS 15.7.1 It seems that any of chord sets I have made in vesions 2.09 to 2.9.1r2.
Hi all,
Iād like to try and clarify the process of importing Scaler 2 chord sets into Scaler 3, including what canāt be imported. Iāve made a short video showing the process of saving a chord set in Scaler 2.9.1 and then importing it into Scaler 3.
Step 1: Saving chord sets in Scaler 2
Youāll notice in the video that when I save the chord set in Scaler 2, I select āSave Individual Pattern(s) as Chord Set(s)ā and leave āConsolidate Patterns in a Single Chord Setā unchecked.
Important: Scaler 3 cannot import
.xmlfiles that consolidate multiple patterns into a single chord set. Also, Scaler 3 cannot currently import full Scaler 2 sessions.
Once saved, the individual pattern is stored in the default user folder, which you can locate via User > Open Folder. If youāve moved your chord sets elsewhere, thatās fine - Scaler 3 doesnāt mind where the files are when importing.
Step 2: Importing into Scaler 3
In the video, I show two options:
- Importing a folder which contains the Scaler 2 chord set (this could be the entire folder containing all of your Scaler 2 chord sets).
- Importing an individual chord set (.xml file).
As per the Scaler 3 User Guide, here are steps to import:
- Navigate to the User category in the left panel of Section A.
(Tip: Drag Section Bās upper border to allocate more space to Section A if needed.) - With the User category selected, click the āImport Chord Setsā button.
- A file dialog will appear. Navigate to a .xml file to import a single chord set, or
select a folder containing multiple chord sets. - Click Open (or double-click the file/folder) to complete the import.
For more information, please check Browse Page > Section A > User Chord Set Management in the user guide.
I hope this helps. If youāve followed these steps and are still having issues (and youāre not trying to import a single chord set that consolidates multiple patterns or a full Scaler 2 session), please share screenshots or a short video of whatās happening - it will make troubleshooting much easier.
Hi folks
I didnāt have the time to read this tons of posts, so I donāt know if SOME users meant āchord progressionsā or ALL users meant some more complex stuff
In the first case you can use the Scaler 3 MIDI recognizer
In brief, put Scaler 2 in a track and Scaler 3 in another track then route the Scaler 2 MIDI output to Scaler 3 track
I used it for a complex chord-progression after I lost the Scaler 2 status
sorry if my post is useless ![]()
I recommend the official solution already provided, but for those who are curious about possible causes, I suggest checking the link below.
David kindly took a look at the xml file of one of my exported chord sets from Scaler 2 and found that there was a structural problem in the file, which happened to be easy to fix. I was able to use the same technique myself on a couple of other files and they then imported successfully into Scaler 3.
This was a few revisions ago, but the key point I want to make is that the problem was in the Scaler 2 export, not Scaler 3, and it persisted across multiple exports of the chord set of the same project.
