Questions & Answers

Studio One 4.1 Permanent Midi Controller Mappings

+2 votes
563 views
asked Nov 27, 2018 in Studio One 4 by ma43 (600 points)
Hi,

I'm stuck. I have used Logic for 20 years or so. Recently I had some underload performance issues. On a whim, I download the demo of St One. Same virtual instruments about 25% of the CPU usage. Why? How? Don't know! That's not my question.... (Sorry...)

I thought I would try St One on a serious project. My idea of hell is changing DAWs after 20 years. Things went pretty well after some initial swearing, but there is one thing I can't figure:

*Getting St One to remember my Basic Controller Assignments permanently between sessions. The stuff that I never want to change...*

In Logic I have all my bread and butter commands mapped to an NI Jam. Delete, Cut, Nudge, Cycle (sorry loop) on off, even save project/song — about 60 mappings in all, that are all muscle memory settings for me. I used the External Device Control Editor in St One and mapped just about all of them. A more pleasant task than with Logic. My "FOCUS" was Global. Worked on actual music for five hours or so, saved the song, went to bed. This morning St One has *LOST* all sixty assignments. I think this may have something to do with the relationship between projects and songs, but I'm still a newbie with this software and am not sure. I did a trawl of the forums and manual but can find nothing substantial.  I tested a few things with projects this morning, and the mappings are still lost on reload.

Questions:

1) Is there any official way to backup/saving to file the controller mappings as reprogramming 60 is painful and frustrating. (I read of some people finding the correct files on their HD an doing it that way. That seems a bit hacky to me.)

2) How can I make St. One reliably remember my permanent mappings between sessions? (I also saved the song as a template. The settings are still lost on reload...)

Thanks for reading,

Cheers,

dRiftminD
...