Forum Replies Created

Page 34 of 40
  • Firstly check the field dominance of the imported track – this can be done by dropping down the track and clicking on the “face” track, the field order should come up in the settings window.

    Also check the local project settings of the Preferences pane. There’s a setting called “better quality field rendering” – try with this on or off and see if it makes a difference.

    Lastly are you rendering within media100, (i.e. applying the effect and returning to media 100 and then rendering) or exporting from RED? I find that rendering from within Media 100 saves time and often looks better.

  • You need to use the “media 100 bin browser” function from within RED, it can be slow to update, but it gets the job done.

    Simply select this function from the track’s drop down menu (the one that’s T for text, or V1 etc) once imported it becomes a movie clip and is handled in the same way.

  • Although it’s understandable why you couldn’t open an SW or HD created program in “i”, it is still a shame that they didn’t fix it so you could re-open an “i” program that had passed through SW for rendering – when I read the release this is what I thought they’d done, and was genuinely excited at the prospect.

  • Kieran Matthew

    March 6, 2006 at 2:10 pm in reply to: Media 100hd and Boris Red 3GL

    Hi,

    These are just a few suggestions from my own experience with RED 3GL, you may well have been down these paths already.

    Firstly, check the field dominance settings are correct for Media 100 use, both in the general preferences and in the track settings – sometimes they get altered by preset effects.

    Secondly have a look at the local project settings in the Preferences, particularly the “better quality field rendering” – I have noticed that this setting, though recommended by Boris, sometimes has an adverse effect on some renders. Try a test with it on and off and see what happens.

    If the “jiggles” are caused by interlace noise, the 1:2:1 deflicker option can help, though this does produce softer output.

  • Kieran Matthew

    February 28, 2006 at 6:38 pm in reply to: Anyone tried the export to ipod in 8.2.3?

    Hi all,

    I have now experienced the error and it seems to come from whether there is audio in the timeline or not. If you export video only it works.

    Not much use, granted, but it’s a start!

  • Kieran Matthew

    February 28, 2006 at 6:35 pm in reply to: media100 and after effects

    Re: the Ipod issue, It appears (on my system at least) to be an audio issue. I can successfully export if there is no audio (or if the audio checkbox is un-ticked in the export options), but get the param error crash if there is.

    Hope that helps.

  • Hi,

    I had a similar problem a while back and it was cured by downloading and installing the software codecs from Media100.com.

    I don’t know if it will cure your issue, but it is worth a try!

  • Kieran Matthew

    February 25, 2006 at 7:17 pm in reply to: Preventing Slow-Mo Render in M100i

    Yep, I’m in PAL land, but I’ve just repeated the test and this time it worked flawlessly! I’m sure I didn’t do anything differently, but who knows.

    Still it works! Blimey – you learn something new everyday!

  • Kieran Matthew

    February 25, 2006 at 6:30 pm in reply to: Preventing Slow-Mo Render in M100i

    Hi Gary,

    When I tried this, Cleaner reported that it couldn’t find the media for the file – which is consistent with the way (I believe)that Media 100 deals with MotionFX.

    Did you export as by reference or as self contained? I’m guessing here, but if you export as Self contained wouldn’t Media 100 just render the files as it was exporting?

  • Kieran Matthew

    February 25, 2006 at 5:08 pm in reply to: Anyone tried the export to ipod in 8.2.3?

    Just tried an export and all went well for me. I don’t have an iPod, but the file compressed well (albeit quite slowly) and then played back in QT player OK.

    Anything unusual about your set-up?

Page 34 of 40

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