Forum Replies Created

Page 240 of 245
  • Floh Peters

    April 22, 2005 at 2:25 pm in reply to: Bad Boris titles in HD

    Hi Tim,

    after some tries I was able to reproduce your problem. It is related to the “Draft quality” setting in the Media settings. If you want to render titles it seems like you have to deselect “Draft quality” to make sure your title gets rendered okay. I haven

  • Floh Peters

    April 22, 2005 at 2:10 pm in reply to: M100 sw Public Beta — Real time issues

    Do you have “Vertical render” turned on? This is probably the arrow you getting from vertical render…

  • Floh Peters

    April 22, 2005 at 1:52 pm in reply to: Bad Boris titles in HD

    It works OK for me. You could send me a timeline with a title that shows the problem (only the timeline, no media files). And tell me your media settings.

  • Floh Peters

    April 22, 2005 at 9:33 am in reply to: MEDIA 100 SW ?

    You can find a download link in this thread.

  • Floh Peters

    April 22, 2005 at 7:25 am in reply to: M100 sw Public Beta — Real time issues

    Media 100 HD and sw use a new color coding for realtime/non-realtime settings. Blue dissolves with a yellow bar on top are realtime as long as your CPU is fast enough, and they should play fine in your timeline. If you use “render all” the system should not render the dissolves. Here is a document explaining the new color coding in the timeline.

  • Floh Peters

    April 22, 2005 at 7:09 am in reply to: Problems resizing photos with Boris in OSX

    HDR stands for High Data Rate or something similar. At some point back in time Media 100 only supported 4:1 compression (150/180k NTSC/PAL), and to get the best result with this compression you were able to choose between different compression algorythms. I think with V2.5 or V3 Media 100 introduced HDR and compression up to 2:1 (300/360k). This only works with the HDR setting, all the other compression settings still went only up to 150k, although the data rate could be set higher. So HDR was the recommended format since at least V3, and with the switch to V8 and OSX the “old” settings are only there for legacy reasons. There is no reason why you should not work in HDR; in fact you will get a much better image quality.

  • Floh Peters

    April 21, 2005 at 11:11 pm in reply to: Problems resizing photos with Boris in OSX

    Do you use BorisFX from within the Media 100 i timeline? Then make sure that your Codec settings in Media 100 i are all set to HDR. The other codec formats can cause these problems.

  • Floh Peters

    April 21, 2005 at 10:51 pm in reply to: Transcoder isn’t working. 🙁

    I still would recommend installing the software codec instead of the Transcoder. You are able to write to Media 100 i codec as well as read Media 100 i files with Alpha channels. Both features are not supported with the Transcoder.

  • Floh Peters

    April 21, 2005 at 10:43 pm in reply to: media100 sw wish

    Rithg now with the beta version of the software you cannot use FireWire I/O. But on the Media 100 sw page it says: “Although it currently does not capture or output to tape without the HDX video I/O board, all the other functionality of the Media 100 HD is there and ready to use. As we continue to develop the Media 100 sw, it will support Firewire capture and output from a range of DV and HDV decks”
    So FireWire support is planned and hopefully will arrive soon.

  • Floh Peters

    April 21, 2005 at 10:40 pm in reply to: Transcoder isn’t working. 🙁

    What is happening if you try to open the movie in QuickTime player? Have you tried installing the Software codec?

Page 240 of 245

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