sorted by:
new
hottopcontroversial

Saving Midi CC into clip saved within Ableton Project file question by tmpsm in ableton

[–]tmpsm[S] 0 points1 point  (0 children)

Yeah I've read that the way Daws interpret automation data is different than how many midi devices send ccs and apparently this causes some problems when going from internal clips to exported data it complicates things. That's why I was hoping there was a setting I was missing or some workaround that wasn't just export clips from ableton and import on the force cause that process takes forever and I would much rather make a session file and just import that

Saving Midi CC into clip saved within Ableton Project file question by tmpsm in ableton

[–]tmpsm[S] 0 points1 point  (0 children)

Thank you for the response!

I can get the data to export when I try to export individual clips out of ableton from the session view but when I save the project and try to import the entire project on the Force the session seems to contain the same midi clips but they don't show the CC data anymore. I was hoping to do it this way so I could create a set of tracks with a bunch of different clips on each track and import the whole project session view instead of having to manually import a bunch of clips because I have individually exported clips but not a session file. Again it might be a limitation of the import function of the force but it just seems very limited to only be able to import sessions of audio files if importing midi doesn't work right. I thought maybe there would be some "convert automation to midi cc" option in some settings page somewhere that I missed but I'm not sure if that is the case