Forum Replies Created

Page 31 of 40
  • Hi Chris,

    I went from a single 867 G4 to a Dual 1.42 G4 with no problems regarding heat etc. As regards to speeding up things, the difference you will notice in render times for things rendered through media 100 won’t be that great as the vincent card is the bottleneck. It is faster, but not by much (In my experience anyway).

    Obviously things that work outside of Media 100 like AE, Cleaner, Bitvice etc are much faster.

    As regards the sonnet card, I know very little about them, but am pretty sure that a PCI-X card won’t fit into a G4.

    Hope that helps!

    K

  • Kieran Matthew

    May 25, 2006 at 6:14 pm in reply to: VHS transfer

    The best way to overcome the sync issue when bringing in sources such as VHS is to pass the signal through a TBC. The TBC provides a constant video signal even when its input is disrupted so digitising won’t stop even if you pause or cue the tape while you do it. I use a Panasonic WJ-AVE3 “effects channel” (the single channel version of their AVE5 vision mixer) that I picked up cheaply on e-bay for just this purpose.

    There was a thread a while back about using u-matic (another format with noisy sync) with media 100, that covered some other options for cleaning the signal up. Have a search of the forum and it should turn up.

    Hope that helps!
    K

  • Kieran Matthew

    May 25, 2006 at 4:38 pm in reply to: Quicktiem 7.1 & Security Update

    no problems on Media 100i!

  • Hi Jerome,

    Yep, flipping the image is easy with RED. Just lay your (reversed) clip on a timeline. Drag a RED comp or title over the top and hit edit. In RED, create a new video track, then use the rotation tools to correct the problem. Set an “X” tumble of 180 to flip the image. If you also need to flop the image, you can then use a “Y” Spin of 180.

    As it is a RED comp it will take a long time to render. After it is finished, you might want to “render range to bin” to fix the effect so moving/editing won’t lose the flip.

    Hope that helps
    K

  • Kieran Matthew

    May 17, 2006 at 6:34 pm in reply to: Exporting to Cleaner from Media 100

    Hmm… that’s odd. Try the following,

    1. Open and then save your settings. See if that has an effect.

    2. Open and save as a different name (add a 1 on the end). See if that works. (you can always delete the old and rename the new later)

    3. Try a fresh new setting and see if you can export to that.

    4. (straw clutching now) reintall Media 100 again now that cleaner is set up and see if that has an effect.

    Let us know how you get on!

    K

  • Kieran Matthew

    May 17, 2006 at 5:01 pm in reply to: Exporting to Cleaner from Media 100

    The best thing to do is re-install cleaner from the CD. This will put back any other files associated with Cleaner that were lost when the hard-drive died.

  • Kieran Matthew

    May 17, 2006 at 11:04 am in reply to: new M100 hardware/software…

    It is clear from this community that there is a desire to run FCP and Media 100 on the same “seat”. But, however vocal we might be, perhaps we are merely one section of media 100’s potential market.

    The new line up, is lets face it a huge leap forward and a sound foundation for the future of the company none of us want to see disappear. The comments we have made are not meant to suggest that the hard work and technical accomplishments have been in vain.

    That said, the issue, at least for some of us, still remains. But perhaps there is an alternative strategy (maybe one that M100 still has up its sleeve)

    Would it be possible to adapt Media 100 SW to run with standard AJA quicktime drivers ? That way instead of trying to run FCP on a turn key Media 100 system, Media 100 could be run on a Kona based FCP system. I appreciate that such a system would probably be locked to the Apple RGB colourspace and as such would present issues when used in conjunction with other media 100 products, but such issues are not insurmountable.

    Other vendors products (Discreet Combustion, After Effects etc) run on Kona hardware alongside FCP, so it is at least technically possible, isn’t it?

    Such a scenario would allow many of us, adrift in the growing sea of FCP, to contiune using and supporting the system we love whilst Boris/Media 100 rebuilds the brand.

  • Kieran Matthew

    May 14, 2006 at 2:58 pm in reply to: new M100 hardware/software…

    As you say, I think most Media 100 users are hoping that we can finally have universal hardware / cpus and be able to choose the interface to suit the particular job in hand, be it Media 100, FCP or whatever. This level playing field can only benefit Boris/Media100 in the long run.

    That said, from the early noises from Media 100 (and they are just early noises) regarding the situation, they are rightly or wrongly only interested in delivering the Media 100 driver for the OEM hardware at this stage and getting the new line-up to market. Whether this situation will change is anybody’s guess.

    What I am hoping for is that AJA themselves will step in to provide the missing drivers/ flash upgrdades that will allow the OEM hardware to work with FCP et al. Whether this will be allowed under the agreement they have with Media 100 remains to be seen.

    Let’s hope Media 100 doesn’t drop the ball …. again.

  • Hi Greg,

    Here’s what I think you need to do. Use the “juicer” thing you mention to render the sequences as regular Quicktime files. Next set up a composition in the graphics track above the video you want to overlay the sequence on – click on the graphics track, then select “new composition” from the tools menu. Drag the newly created composition to the right length.

    Now edit this composition with Boris FX. Create a track and change the track media to movie and use the browser to find your graphic that you exported previously.

    This should create a track with the graphic in it that can be sized, positioned, filtered as normal. If the QT file you rendered supports alpha channels (never tried!) then use the setting window to select the aplha type, otherwise use a key filter to handle the transparency. You can also set the graphic to loop (watch for extra frames as Mark mentioned) for as long as your composition lasts.

    Apply the effect and render. This *should* work, though I’m working from memory here. Let us know how you get on!

    K

  • Kieran Matthew

    May 12, 2006 at 11:41 pm in reply to: H.264 encoders

    I haven’t actually tried this properly, but it appears Compressor 2 can de-interlace and crop whilst converting to H.264. A quick test seemed to show it processing, but it was predicting an obscene amount of time for the batch to go through. Probably down to the 867 G4 i did the test on though.

Page 31 of 40

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