Forum Replies Created

Page 2 of 2
  • Thomas

    June 7, 2006 at 11:07 am in reply to: Media 100 HD codec issue with AE

    It was an AE settings problem. Nothing to do with M100 codec. With an apple F on the clip in AE bin, and desactvation of fields order, everything look perfect again. It is strange that this setting doesn’t look good by default. Anyway, i’m happy again.

    Tommy

  • Thomas

    April 27, 2006 at 11:18 am in reply to: some things i saw for myself

    Great & exiting news. As an Hdx happy user i feel better hearing this. But please, people at Boris/M100, don’t loose the opportunity to come back in the market with some essentials features in V11 :

    1. A real match frame & JKL navigation. I don’t care personnaly but an Avid editor can’t work in M100 without this.
    2. DV IN & OUT (you only mention DV In in your post)
    3. DVC PRO HD / P2 & 24 frames timeline support.
    4. OMF support (i can’t believe this feature disapeared)

    Wishes for future releases :

    1. The ability to share the AJA hardware with different software (FCP, Premiere Pro) by acquiring the M100 license only. Huge commercial potential.
    2. A real professionnal color correction tool and/or the ability to use third party plugs-ins as color finesse.

    Tommy

  • Thomas

    March 29, 2006 at 11:17 pm in reply to: Exporting from Edit Suite

    Export from edit suite by ref (extremely fast), then encode with bitvice or toast (or DVD studiopro but with this one you have to check before the black levels of your clip), then author in DVDSP and burn. Why H. 264?

    Tommy

  • Thomas

    March 28, 2006 at 11:40 pm in reply to: HD and OMF

    No OMF in HD, you’re right. We call that a downgrade i guess. We all absolutely need it.

    Tommy

  • Thomas

    December 2, 2005 at 5:37 pm in reply to: Bug report in M100 HD

    I still work using the media 100i codec. It’s certainly the reason. I’m gonna try to use the HD codec for SD project. But i’m wondering if i can still work with SATA and Firewire 800 drives without data rates issues. I don’t use my SCSI Raid for years now in M100. The silence of the G5 is too confortable.

    Tommy

  • Thomas

    June 23, 2005 at 4:13 pm in reply to: Outputting a composite signal in M100 HD

    I’ll check that Floh. It wasn’t my configuration at all (i used ref out for composite directly to the VTR). SDI 2 (composite out doesn’t give me any signal). It seems completely wired to me that we can do it with the Y cable (i tought it was luminance only). Anyway, i was in a hurry so i did the export to FCP as a DV PAL file and changed the gamma levels in it (1,41 more gamma) and the image looks OK. Now i can do easy master to DVCAM tape and the image quality is much more better than with composite. I wish i could do it directly in M100. I had 3 different versions of 52 minutes documentary to master and i took the day to do something that could have be done in 2 and a half hour. It is urgent for all of us to get firewire In&Out in M100 don’t you think.

    Thanks for the tip, i’ll use it for VHS

  • The Vincent 601 is an older card that work with analogic signal (square pixels 768/576 in pal mode). Media 100 realised a 720 enabler under os 9 (until V.7.5) that allows the Vincent card to play perfectly medias digitized in 720. The problem is that when you digitize directly in 720 with this card, the image quality is not quite good. In fact it’s unsuable. I tought at a time that the problem was resolved under OS X (V.8.x), but unfortunately it’s not. So the card has to be used in 768 in digitize mode to work correctly. It’s not such a problem regarding the fact that new HD and SW systems recognise those medias directly and convert them in 720 in real time. Nevertheless it’s better to get a P6000 board for two other reasons also (DV Option and Lossless capabilities).

    Tommy

  • Thomas

    May 7, 2005 at 12:02 pm in reply to: Audio Post Production (Media 100i to ProTools)

    We never used the OMF option anyway. The simpliest way for us is to export all audio tracks seperately using the solo mode before exporting from edit suite (we put a sync beep on each track 50 frames before the first image of the program). In Protools we import each tracks and then recreate all the regions putting away all the empty area). And then you can mix. It supposes that you prepare very well the audio editing before you go to Protools because you can not access the source audio file (as you can with OMF export), but it definitevely works very well (above all for mixing process). At the end of your work in protools, you bounce everything in stereo an then import it into M100 for mastering to tape.

  • Thomas

    April 22, 2005 at 4:18 pm in reply to: MEDIA 100 SW ?

    Ok, good to know for imovie (never used it yet !). Let’s get in touch if we find the solution. Maybe M100 could send us an explanantion for this problem, because they don’t mentionned it anywhere (just saying that we can natively use DV files in real time -which is not true, they need to be updated before- and in no cases to be rendered). In the same time, i really hope that the black level differencies between FCP & M100 could be resolved soon (i guess this is more an FCP problem), maybe with QT 7

  • Thomas

    April 22, 2005 at 2:54 pm in reply to: MEDIA 100 SW ?

    Thanks for the link Floh. I’ve just installed SW in my powerbook and it works great. But i have a little problem concerning also HD version of M100 about clips coming from FCP. I can import them and they are updated fast enough when the clips from FCP are exported before as self contained from FCP. Then they use the FCP icon in the finder. If they are just digitized in FCP – then they use the quicktime icon – they have to be rendered in M100 and are destroyed by the compression. I’ve cheked the settings in M100 of course before importing the clips. It’s becoming a real issue for me, especially In SW where i would like to use footages digitized in FCP. I can’t figure what’s happening. Any idea ?

Page 2 of 2

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