Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Avid Media Composer MC6 and Blackmagic performance

  • MC6 and Blackmagic performance

    Posted by Rob Tinworth on March 19, 2012 at 3:03 am

    While it’s great that MC6 has opened up Avid to third party hardware, I’m not getting anything like the performance I’d expect running Avid MC6 with a Blackmagic Multibridge Pro. Scrubbing is a little sticky and trimming is super sticky.

    Switching off the external monitor returns scrubbing and trimming to smooth as a hot knife through butter, so the block is the video I/O not the drives.

    Is anybody else finding MC6 sticky with third party I/O? Or is this unique to my setup?

    Rob

    Rob Tinworth
    http://www.1021.tv

    Eduardo Serrano replied 14 years, 1 month ago 11 Members · 18 Replies
  • 18 Replies
  • Pat Horridge

    March 19, 2012 at 8:05 am

    I think it’s still early days for the 3rd party I/O solutions and Avids DX boxes fly in comparison.

    Pat Horridge
    Technical Director, Trainer, Avid Certified Instructor
    VET
    Production Editing Digital Media Design DVD
    T +44 (0)20 7505 4701 | F +44 (0)20 7505 4800 | E pat@vet.co.uk |
    http://www.vet.co.uk | Lux Building 2-4 Hoxton Square London N1 6US

  • Michael Phillips

    March 19, 2012 at 10:43 am

    It will be interesting to see the difference in performance between third party I/O vendors to see what is common or not between them. Based on that, one will be able to tell whether these limitations are in the third party implementation or the SDK itself from Avid. There are known limitations already listed in the Knowledgebase. Still early days, will be interesting to see what is served up in the second round.

    Michael

    Michael Phillips

  • Neil Patience

    March 19, 2012 at 1:48 pm

    Yes early days for this but its a great addition.

    I have a test set-up on an older MacPro with a Kona 3 running Lion and Avid 6.01

    I have only used it on smallish projects and a timeline of a couple of layers here and there and 12 – 15 mins tops. So nothing too taxing to come to any real solid conclusions.

    I use MC and Symphony on everything from Mojo’s to Nitris depending on where I am working so am used the to performance there. That said I was pleasantly suprised at the speed and smoothness of moving around the timeline with the Kona and trimming seems fine – again on a pretty basic level.

    I am looking towards Blackmagic for Resolve so its interesting to hear your experiences.

    best wishes
    Neil
    http://www.patience.tv

  • Michael Phillips

    March 19, 2012 at 2:16 pm

    I use a Blackmagic as well and for the most part, it works well other than the listed limitations as well as things like dual trim mode on the client monitor etc. But hopefully those things will get added to the SDK so third parties can implement and take advantage of them.

    Michael

    Michael Phillips

  • Neil Goodman

    March 19, 2012 at 2:42 pm

    On 10.6.8 i have the same laggy trimming and scrubbing, mostly with the caps lock key on. This is with the deckling extreme HD 2.

    At home on 10.7.2 everything is pretty smooth and snappy with the intensity extreme. It works just as smooth as my nitris at work with MC 4.

    Seems like those drivers are geared more for lion now.

    Neil Goodman: Editor of New Media Production – NBC/Universal

  • John Pale

    March 19, 2012 at 3:23 pm

    I have the Decklink Studio 2. Performance is generally very good with driver 9.0…I have had problems with 9.1 and 9.2, that render it unusable to me. Even with 9.0, there is an annoying bug…I get a crash with audio only files loaded into the source monitor with scrubbing turned on (caps lock).

  • Michael Phillips

    March 19, 2012 at 4:58 pm

    Yes, CAPS LOCK is a killer in all these scenarios. A perfect example of where does the issue lie:? The playback pipeline, the SDK, or the implementation of the SDK or a little of all three?

    Michael

    Michael Phillips

  • John Pale

    March 19, 2012 at 9:12 pm

    “Yes, CAPS LOCK is a killer in all these scenarios. A perfect example of where does the issue lie:? The playback pipeline, the SDK, or the implementation of the SDK or a little of all three? ”

    I don’t I have first hand knowledge but I have heard that AJA does not have these issues, only Blackmagic and Matrox.

  • Michael Phillips

    March 19, 2012 at 11:14 pm

    Good to know, perhaps someone with AJA hardware will chime in with their experiences.

    Michael Phillips

  • Eduardo Serrano

    March 20, 2012 at 1:37 am

    I have the same sluggish issue both with caps lock and in trim mode with my matrox MXO2 mini. It renders the unit basically unusable.

    Also, I have a sync problem between my various audio meters within avid.

    The interesting thing is that matrox has an even older partnership with the MC team than AJA. Well, let’s see if any AJA user chimes in with his impression.

    Ed.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy