Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro A nice comment from Matrox Support

  • A nice comment from Matrox Support

    Posted by Petros Kolyvas on January 26, 2012 at 12:46 am

    Have a look at this folks:

    We will investigate this with our engineering department. However, please note Premiere does not have a 1080psf@23.98 preset. Therefore, 1080psf23.98 files may not be 100% compatible with Premiere CS5.5. I will need to confirm this and let you know further updates.

    This is an answer I received from Matrox support querying a bug in the Matrox capture utility that is incorrectly packaging 23.976PsF files as interlaced. The only thing that involved Premiere was that I caught the mistake there when I noticed some files were being mistakenly noted as drop-frame timecode and that sequences became 29.97 sequences when I used the Match Settings option to create the sequences.

    Clearly something was up with the files the Matrox capture utility was creating.

    Am I wrong to be a little terrified that Matrox support doesn’t understand that PsF is a transmission mechanism for progressive video via interlaced hardware/interconnects/equipment and that the files created from “properly received” 23.976PsF signals are true progressive-format 23.976 files?

    They seem to be under the distorted impression that PsF is a file format (oh dear!)…

    I continue to wonder if I’m in any way wrong here, it isn’t even close to my first kick at the can, but one starts to question one’s self!

    Progressive format file -> PsF through HD-SDI on PsF compatible equipment -> Progressive format file

    Thanks for any light someone can shine on this.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

    Petros Kolyvas replied 14 years, 3 months ago 4 Members · 7 Replies
  • 7 Replies
  • Tom Daigon

    January 26, 2012 at 1:08 am

    AJA! AJA! AJA! They understand video.

    Tom Daigon
    Avid DS / PrP / After Effects Editor
    http://www.hdshotsandcuts.com
    Mac Pro 3,1
    8 core
    10.6.8
    Nvidia Quadro 4000
    24 gigs ram
    Maxx Digital / Areca 8tb. raid
    Kona 3

  • Petros Kolyvas

    January 26, 2012 at 1:42 am

    Thanks Tom! We are/were heading that way… this did help seal the deal though. 🙂

    We were looking at AJA for edit “B” for some time as a replacement to an aging Matrox MXO setup (not the MXO2 the discussion above caused); now we probably go whole hog and get AJA cards for both…

    The MXO2 went up for sale after that conversation with tech support. With what we can get the MXO2 with MAX for used, the LHi will cost very little as an upgrade/crossgrade and Media Encoder on a Quad or Six core mac as almost as fast (sometimes faster!) than “MAX” and isn’t tied to MOV containers (I prefer MP4). Bonus.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Bob Auiler

    January 26, 2012 at 10:58 am

    Petros,

    You might be wise to wait until CS6 is released to see if the Premiere/AJA performance issues are addressed before equipping your suites with AJA hardware.

    AJA timelines are very sluggish compared to the native timelines in Premiere, also the source monitor doesn’t play out on your external monitor and the AJA setup in Premiere preferences is very unintuitive. These problems are unlike AJA and I assume they are working to resolve them.

    Bob Auiler | bob.auiler@mvpcollaborative.com

  • Petros Kolyvas

    January 26, 2012 at 2:04 pm

    Hi Bob,

    Thanks for the note.

    Part of what we do is use our Video I/O for in-studio chroma key and/or interviews – for which we need a card that can acquire 1080p23.98PsF reliably (in AJA’s case I believe we’d use their applications VTR Exchange.)

    I believe all cards are sluggish on the timeline in Premiere – the MXO2 was nearly unusable so we would only playback sequences on it when it was time to do CC and the edit was nearly complete.

    We also still use FCP7 for legacy projects and plan on running future versions of FCPX alongside Premiere Pro/Production Premium so the reason to move to AJA is both about reliable video capture in addition to monitoring.

    We’re been struggling with the MXO2 for years now and it’s just not worth it (for me anyway – mileage will vary) to continuing using a device that I can’t/don’t trust to work the way it should.

    Again though, thanks for the heads up!

    All the best,
    PK


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Tom Daigon

    January 26, 2012 at 2:37 pm

    [Bob Auiler] “also the source monitor doesn’t play out on your external monitor and the AJA setup in Premiere preferences is very unintuitive”

    Sorry Bob, I respectfully disagree. I get Source playback through my external monitor with Kona 3. And I find familiarity with most ANYTHING (GUI) makes it more comfortable. Ive been using AJA products for many years and find the GUI easy to understand and work with.

    Tom Daigon
    Avid DS / PrP / After Effects Editor
    http://www.hdshotsandcuts.com
    Mac Pro 3,1
    8 core
    10.6.8
    Nvidia Quadro 4000
    24 gigs ram
    Maxx Digital / Areca 8tb. raid
    Kona 3

  • Chris Borjis

    January 26, 2012 at 5:30 pm

    I get Source playback as well, through my external monitor with Kona-LHe.

  • Petros Kolyvas

    February 6, 2012 at 10:06 pm

    A Kona LHi and KLHi breakout box arrived today as a replacement for the MXO2 with MAX in our “big” room.

    What a breath of fresh air. We get full-speed, full-res playback of 1080p content off the Premiere timeline and the kind of performance we’d wanted from Matrox but never got.

    Sure, we’ll have to do without MAX, but on our two most recent workstations, we could outpace MAX with Media Encoder anyway and we didn’t like sending out MOV files to clients on Windows.

    It’s early days yet, but at least the VTR Exchange application is miles and miles more useful (and more reliable) than the Matrox Vetura capture utility and produces correct/non-broken 23.98 files from 23.98PsF sources. The “Classic Control Panel” is also much more useful and straightforward than the Matrox System Preference pane in my humble, but oh-so-tired-of-the-MXO2 opinion. Having a snapshot of the IO setup and formats is very useful.

    The only downside we’ve discovered so far is that for all the fun we made of Matrox including a paltry 1m cable with its unit, the 5m KLHI tether is $250! Oh well, it’s worth the pain and the cables that shipped with the unit fit, just barely, in our current setup.


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

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