I’ve had to built a new computer running Windows 10.
Cubase Pro 13 has been reinstalled. Also installed is software for M-Audio M-TRACK 8 and Universal Control for the FADERPORT 16.
Setting up the Mackie control in the studio setup is now slightly different to previous version of Cubase according to PreSonus instructions.
If I move the faders in the MixConsole, The Faders will move on the FADERPORT Controller BUT… if I move a fader on the Controller. it will not control those on the MixConsole…
Have I missed something.
Thank You for taking the time to read this.
Hi,
The setting in Cubase i smore or less the same for many years.
Could you attach a screenshot of your setting, please?
Hi,
I can see Mackie Control and Mackie Control 2, which is OK. Could you select them and attach screenshots? What MIDI Input Ports do youuse for them?
Make sure, you don’t use the FaderPort MIDI Inputs for any of the Quick Controls, please.
FADERPORT is only used in this way. It has previously worked but now I’m struggling with it.
I’m also in the process upgrading windows to version 22H2 as it was before. Tried windows 11 but had same problem and came back to W10 thinking it was that.
Hi,
It looks correct.
I believe so but I can’t work out why it’s only one way…
Hi,
Click on the Monitor in the MIDI Port Setup on the line of the Faderports and inspect, what does the hardware send.
Cubase keeps freezing on me. Also earlier, it froze while playing and couldn’t stop it. only way was to shut Windows down…
Nothing seems to be happening…
A naughty plugin maybe?
Do you think I need to reinstall Cubase?
at the moment not using any although there are some that I think I need to install… 
OK… I’ve had a major breakthrough. Last night while I was laying in bed, I had a think about it.
This is a new build ‘mini’ pc and because it doesn’t have a lot of ports in comparison to my original, I bought a USB hub to help out.
This morning I connected the FADERPORT directly into the pc and fired up Cubase…
The FADERPORT is now working as it should…
But who would have known the the simplest things are quite often the most overlooked.
I wonder if that is also the cause of Cubase freezing occasionally… We’ll see… Thanks all who took an interest…
2 Likes
UPDATE - The first USB Hub I used was a Powered type.
I tried a non-powered type USB Hub and that works fine with both FADERPORT and Audio Interface.
I then tried a different powered USB Hub which also didn’t work…
Conclusion - It’s seems that using your FADERPORT Production Controller is ok when plugged into a USB Hub so long as it’s not a powered Hub. I do have to say though that this is true in my case…
Hope this is of some use to you…
2 Likes
Hi,
That’s interesting, I would expect exactly the opposite.
I wouldn’t have thought it made any difference at all. Up to yet I haven’t even had any freezing either…
I think it must have something to do with the midi communication. The Audio Interface output works fine in the Powered Hub but I haven’t tried recording anything through it…
I’ll stick with the non powered Hub for them both just to save me from any potential issues…
Wow. Thank you for posting your experience. I have a Faderport 16, working with Cubase 12 Pro trough a powered USB hub. I own a Cubase 13 license, but haven’t installed it yet, as I wanted to finish some projects with C12 first. Good to know where to search for solutions when I start working with C13.
It’s all a bit weird I know. Maybe in your situation, all will be good. It may be that my is now a ‘mini pc’ but at least my experience will help you or someone else…
1 Like