Cannot import midi files into scaler 3.
Tried converting Ableton clips to midi file (.mid)
Tried drag and drop everywere, including the midi editor in the arrange section.
Is there a way to do this ?
Love the program, but this should be prioritized.
There is already a midi editor.
I’ missing something here ?
Thanks
Welcome to the forum. Hit the record button, change the profile to MIDI Detect and click the folder icon to load your MIDI file
Hi Davide, thank you.
I know that.
In scaler 2 you could drag a midi file and it would detect it.
In scaler 3 it’s not working, and having even a midi editor this time i would expect seamless workflow with midi.
Let’s hope for updates ?
That kind of workflow with detection is cumbersome if you have a lot of material to process.
Let’s prioritize importing midi next 
4 clicks instead of 1 D&D, and if you have MIDI/AUDIO files in multiple folders/plugins, the process is slowed down more
this is another case where SC3 worsened/slowed down a process that was easy and fast before
One of the many cases, unluckily
I am only getting the first chord of the midi file to show up when importing a file. Any ideas of what I am missing?
I tried this today with a leadsheet from Melodyne extracted from a audifile of a vocal created by SUNO with my own lyrics. The lead sheet is imported to Ableton Live and looks good. Same with Cubase. Drag and drop the midi from the Cubase track to their chord track works good.
In Scacler I get nothing. No chord is detected. None Nada.
Leadsheet.mid (3.1 KB)
As in you are trying to drag and drop the file on S3 or load it via MIDI Detection? The latter you can do the former will work in S3 1.0.7 out tomorrow.
1.0.7 (Scheduled May 15, 2025)
Improvements
Fixes
Other@davide
I tried to import it via the Midi Detection as described in the manual and on videos. When I select the midi file nothing happens.
Michael
to be more clear:
This file doesen’t force Scaler to do nothing
Leadsheet.mid (3.1 KB)
This one works fine
AkkordeAusMelodyne.mid (5.0 KB)
I did some testing on the file you supplied and strangely it was only 3 kilobytes and doesn’t work in several MIDI software I tried including Scaler 2 and Scaler 3. I was able to extrapolate the chords using Logic Pro and then export as a MIDI file which then worked correctly in S2 and S3. So something about your Leadsheet.mid file doesn’t contain enough data to be a fully compatible MIDI file:
Incomplete Information:
MIDI files consist of events that instruct an instrument to play certain notes, durations, and other parameters. If a file is too small, it might be missing these essential instructions, resulting in silence or incomplete playback
Hi Davide thanks for the info. I will get in contact with Celemony and tell them your investigation if you allow me. Ableton Live, Cubase have as well no Problems
Michael
@davide
MIDI files don’t have to be big and the file “leadsheet.mid” is a correctly formed MIDI file. It’s got the header chunk and one track chunk containing MIDI events and timestamps. (I’ve done more than a bit of MIDI programming in my time…)
It loads fine in Studio One, Cubase, Reason and in various online MIDI file analysers.
For example, MIDI file analyzer reports
Number of notes 78
Notes range C4-Fs5
Time signature 4/4
Beats per minute 116
Tracks
1. 1 78 notes; C4-Fs5
So I think there is a bug in Scaler 3. I’d suggest asking your MIDI dev person to look at that file and also ask them if Scaler 3 can handle Type 0 MIDI files.
Danke, have send the file to Celemony support.