If it worked, I suspect it would look like this? (I set those markers manually)
FL Studio supports MIDI markers as well, I could manually create some…
And I have seen it use MIDI markers from third party .mid files, mostly for time signature changes information.
This irritates me as well. None of the DAWs I use seem to support this. I thought Cubase would since it has a chord track but no it does not, nor Ableton.
However this is no fault of Scaler but the implementation on the DAW side. Come on Steinberg - fix this!
Ok, after learning what is possible today, I want to re-iterate my original feature request, since current functionality, and its limited availability in various DAWs does not meet my need…
I would like the .mid file name that Scaler creates upon drag&drop export of MIDI chords from Scaler into DAW (currently by default “Scaler-Chord.mid”, or “Scaler-Chords-With-Markers.mid”) to be reflective of the chord name in case where I drag a single chord. This ought to be possible since Scaler controls the naming of the .mid file name it exports in drag & drop, and if I can manually capture the chords names in Scaler, that process step should be automatable as part of the said drag & drop operation. And it is clearly compatible with the DAWs, which all properly show the name of the .mid file imported.
My use case is that I frequently drag individual chords out of Scaler progressions (especially from the ever-so-cool modulations) into my performance clips, which are then mapped to one of the 64 pads on my MIDI controller (currently Maschine Jam, but could be Ableton Push, or Novation Launch Key, you name it). And then I play variations of the chords via MIDI controller pads that reflect the proximity of the musical chords in the way the key pads are layed out in 2D space.
I’ve tried in Studio one 5 and it doesn’t work, like you said I think it’s the fault of the Daw.
We tried this and found the frequent editing, merging, joining meant that our sessions were just a miss match of incorrectly labelled chord names and it was easier to be generic and allow copy and paste from scaler
2 Likes
The MIDI drag to Studio One is driving me absolutely IN-frIggin-SANE!
Yes. It is in Reaper the only one that appears automatically. In the others you have to follow the clipboard method
1 Like
I would like to be able to make a custom shortcut key for copying the chord names.
Then at least I could make a macro to copy/paste the chord name into Logic’s marker/arrangement track.
Thanks by the way for a fantastic plugin.
Welcome Sinko
I have only seen the functionality you refer to work in Reaper. In other DAWs it doesn’t work.
To have the chord labels you must copy, after selecting the chords ,. Then you open the clipboard and copy it to go back to the DAW and paste in the timeline where you want it to appear
I leave you a link that takes you to another article in the forum on this same topic
Thank you kindly. Yes that’s why in Scaler it would be great if you coud add a keyboard shortcut in the Prefs/Command area for a “Copy Names to Clipboard.”
It would be a lot more dependable than my macros below…
I’ve written 2 macros in Keyboard Maestro. One will copy the Chord Names to the clipboard (A workaround with a hotkey). Then it will open the Clipboard, space the chords out ready for easier copying to the Logic Arrangement track.
Does 2.7.3 still support chord names when dragging into Reaper? I can’t get it to work now, although it did in an older project. I’m thinking I might have used an earlier version in that project?
Yes, it does. Drag/drop the chords from any Section.
Well… Good to know 
I’m only getting the “Scaler-Chord-With-Markers.mid,” whether Export Midi Markers is on or off. Is there something in Reaper I should check?
I don’t remember what I did, but I certainly tweaked some settings. To be sure that your chord names are invisible because of colors, I would set the font color for Markers. I am pretty sure I did this, but don’t remember whether I did something more.
Maybe you’ll need to tweak some other colors, background color, for example.
Please try this and let me know.
Thanks for the suggestion. Coloring differently doesn’t make them show up. The dialog window in Reaper for MIDI file import that I can check to “import as project marker” creates the project marker OK and it’s colored by the Markers coloring you indicated. Just appears that no chord name is being brought in as a marker. I’ve been trying all kinds of stuff. Bizarre.
I am not sure if I already published something about it on this forum. Maybe I found the information on Reaper forum. It’s been a while.
Yep. I know what you mean. And I don’t remember doing anything special to get them to show previously – it just worked. I’ve appreciated your trying! FWIW, I just did a new portable install of Reaper to test it, and still don’t get the chord name in the midi item. Project marker continues to work fine. I wonder if it’s a label of some kind, that has a setting for postion. Oh, well… I guess it’s stumped the Devs, too.
Just a comment, which most Live users will be familiar with, but some not, so here goes, for them.
When you drag a midi file into a Live track it may not be evident that the name shown is taken from the ‘meta event definition’ FF03 in the track; the file name itself is not used. So the file title ‘Scaler-Chords’ is ignored. This is easily checked by renaming a file to ‘test’ and seeing that it has no effect.
If the Devs write the chord description as shown in each in section C to the FF03 slot, Live will then show them.
Of course, as @Bernd correctly pointed out in his initial post, this would only work for single chords, not progressions.
I was alerted to this because I succumbed to advertising and bough the Nikko chord pack, only to find that they had written lengthy copyright spiel into this section as opposed to the correct place (FF02), so the actual name of the file was not normally visible in Live. I had to write a script to read through vast numbers of mids to re-write the field.