3 posts
Page 1 of 1
Odd behavior with Faderport. Some Protools sessions work with faderport touch mode and write automation successfully. Other sessions, including newly created clean sessions (default settings, all new bussing) will not write automation. Touch successfully gets set from the Fader Mode command on the Faderport, but does not write automation - - it just controls the volume level.

Problem shows up inconsistently in all my Protools sessions. IO and MIDI HUI interfaces are configured correctly.
User avatar
by eugenekim on Tue Jun 21, 2016 8:10 am
i'm having the same issue.

Faderport will control volume (I can hear the changes) but isn't writing automation

here's my specs:
protools hd 12
osx 10.11.4 (el capitan)
16gb ram

MIDI peripheral settings have been reset and restarted.

annoying
User avatar
by eugeneng on Mon Jul 03, 2017 10:48 pm
I am facing the same issue too. Everything works except writing automation. It's quite maddening considering that I bought this so that I can do volume automation!!

3 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 0 guests