Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MB23C: VCA Automation issues
#1
Hi

I've been trying to add some VCA automation to my mix and I've noticed there is a tremendous string of "spikes" in the automation data. Since I was using a Faderport classic, I thought that it was dust in the potentiometer, and to my regret, I gave it up using it. (see attachment 1     )

Now I've been using the mouse with the FaderPort switched off and this behavior still repeats (see attachment 2     ).

Both screenshots are taken with a high level of zoom.

I don't know what is happening. Could it be a bug in MixBus?

Greetings
Rafael
Reply
#2
Attachment 2 looks like something is fighting against Touch automation.
Where you trying to pull VCA 6 all the way down ? Perhaps try Latch mode and see if that helps. Are you running 32Cv6.702 ?
I have tried to replicate this on macOS but cannot.
I would suggest you write support: mixbus@harrisonconsoles.com
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Reply
#3
(05-04-2020, 07:13 PM)Dingo Wrote: Attachment 2 looks like something is fighting against Touch automation.
Where you trying to pull VCA 6 all the way down ? Perhaps try Latch mode and see if that helps. Are you running 32Cv6.702 ?
I have tried to replicate this on macOS but cannot.
I would suggest you write support: mixbus@harrisonconsoles.com

I'm running the previous 6xx version (I didn't know there was a .702 verison)
Ok, I'll try Latch mode and write to support if this behavior still exists.
Thank you very much for your tips !

EDIT May -11- 2020:
It seems that updating to Mixbus 32c v6.0 .702 version solves this problem Big Grin
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)