Forum Replies Created

Page 27 of 40
  • Kieran Matthew

    July 7, 2006 at 7:22 pm in reply to: FCP on AJA-OEM based Media 100 HD…

    Hi Bobby,

    From the Digital Garage Group in the UK. They were the company hosting Media 100 (and Boris) at the Broadcast Live show recently. They did a routine sales follow up and that nugget of info came out.

    K

  • Kieran Matthew

    July 6, 2006 at 6:28 pm in reply to: FCP on AJA-OEM based Media 100 HD…

    Hi Bobby,

    I haven’t ordered my HD kit yet as I was waiting for the confirmation. I too am having the “which version” blues, though I think I’m plumping for the HDe as I already have RED and feel that the only advantage to the HD Suite (the SD upconversion) I can live without. The possibility of the 2K just brings visions of horrendously expensive drive arrays.

    K

  • Kieran Matthew

    July 6, 2006 at 9:45 am in reply to: FCP on AJA-OEM based Media 100 HD…

    I can’t take the credit for testing (sterling work by a media 100 reseller) but I am happy to share the news!

  • Kieran Matthew

    July 6, 2006 at 9:06 am in reply to: Media100 – WMV 16×9?

    Try installing (or reinstalling) the media 100 software codec. It worked for me, Cleaner started to behave itself again after I moved up to QT7. I make 16:9 WMVs with cleaner all the time, have had no problems since.

    K

  • Kieran Matthew

    July 4, 2006 at 11:44 pm in reply to: floh buying new M100 HD & FCP

    Hi Greg,

    With regards to the G5, yes. You could either buy a second (SATA) internal HD or partition the one it comes with.

    As for the other questions. Yes unfortunately this is all speculation at the moment.

    I am reliably informed that FCP has been made to run on the Beta version of Media 100 V11-AJA as a proof of concept, but the thing is the Beta version ran on standard off-the-shelf Kona hardware, not the OEM hardware that the retail version ships with.

    From looking at the hardware specs on AJA’s website it does appear that the OEM HDe card is the same as the Kona LHe retail system for FCP, but until someone actually gets their hands on one to test we won’t know for sure. There are any number of reasons why the shipping systems wouldn’t be able to run FCP, from BIOS, to encryption codes, to just plain can’t. Again until someone gets one and tries it, we just don’t know.

    Media 100 isn’t testing this configuration. Even if they were it would be unlikely that they could publicly endorse it, or even acknowledge the possibility. Chances are their agreements with AJA would forbid it.

    However there are many other people who have a keen interest in finding out one way or another whether this is a practical possibility and it is to them we look for firm answers.

    When will we find out ? Soon. The new systems are hitting the streets as we speak. Keep watching the cow, when the news breaks, it’ll break here first!

    K

  • Kieran Matthew

    July 4, 2006 at 10:02 pm in reply to: floh buying new M100 HD & FCP

    Hi Elliot,

    The issue is that the drivers for the AJA card are different for Media 100 and FCP. They conflict if the two drivers are installed at the same time.

    The easiest solution is to have a dual boot system. i.e. either two hard drives or two partitions on one hardrive with the (same) OS installed on both discs. In one you install the FCP ‘Kona’ drivers, in the other the Media 100 ones. If you want to use FCP, you boot the mac into the OS version with the FCP drivers by choosing the start-up disc in the preferences, or for media 100 the other.

    Other (untested) options have been suggested including a script to swap the drivers over by parking one on the desktop, (much like the scripts used to swap the Media 100 codec component) after which you reboot. This would allow one single OS installation which might be simpler to manage, especially with updates etc.

    Either way you won’t be able to use Media 100 and then launch FCP (or vice versa) without rebooting in between.

    Hope that helps

    K

  • Kieran Matthew

    June 30, 2006 at 5:18 pm in reply to: buying new media 100 hd version 11 or FCP?

    Hi CleverMoniker,

    I think you are spot on there. It’s the confirmation os the 2K bit that I was after. If this is one of the hardware features Rob mentioned for future use then this is good news. Media 100 finally future proofing itself? This just gets better and better!

    K

  • Kieran Matthew

    June 30, 2006 at 3:55 pm in reply to: buying new media 100 hd version 11 or FCP?

    Hi Rob,

    So out of interest, which OEM card is the HD Suite based on ?

    It seems from the comparison sheet that there aren’t that many reasons to plump for the HD Suite over the HDe (especially if you are already a RED user). Could you give us a list of the advantages of the HD suite ?

    BTW, are you aware that the analogue IO error is on the hard-copy brochures as well ?

    Thanks !

    Kieran

  • Kieran Matthew

    June 30, 2006 at 1:27 am in reply to: buying new media 100 hd version 11 or FCP?

    The current SW version is AFAIK exactly like the integrated software (just minus IO of course). Coming from FCP or premiere it will feel simpler (and in a lot of ways is). Media 100 lacks a lot of the advanced compositing features found in FCP and the like, as Boris software like RED is expected to be used instead. This hand-in-hand approach is probably why Boris bought Media 100 in the first place!

  • Kieran Matthew

    June 29, 2006 at 11:42 pm in reply to: buying new media 100 hd version 11 or FCP?

    Hi Mathias,

    From a quick look at the AJA website and Media 100’s brochure, it looks like the HDe solution is indeed equivalent to the Kona LHe, but the specifications of the HD Suite don’t seem to match any of the cards listed on AJA’s retail or OEM site (note Media 100’s 8 channel analogue output and 8 channel AES IO – compared to Kona LHe’s 2 and 2, and Kona 3’s complete lack of any analogue side). This could mean that the HD suite is a custom card?

    K

Page 27 of 40

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