Forum Replies Created

Page 1 of 33
  • Wickham Strub

    February 18, 2010 at 3:33 am in reply to: Ki Pro and Media 100

    Hey Jason,

    We had a customer a little while ago who said he was having trouble playing back media from the Ki Pro. He sent us the media and it played back fine on our systems.

    His system was fairly out of date at the time and I suspected that was a source of the problem. Unfortunately, I’ve been unable thus far to find out if he solved his problem.

    ~ Wick

  • Wickham Strub

    February 15, 2010 at 3:36 pm in reply to: Memory leak or memory allocation?

    WOW… That\’s a lot of clips with a resource-hungry filter applied.

    As for which side the actual problem is on, it\’s hard to say. Could be Boris, could be M100. Either way, it\’s not working for you.

    Do you have Vertical Render enabled in the Media menu? If so, does turning off help?

    Can you render the filters? Given your symptoms, I do not expect you to be able render them all at once but what about 1?10? 20? etc?

  • Wickham Strub

    February 11, 2010 at 11:38 pm in reply to: locating media in bins

    You can also select Programs and Bins in the Project window. The batch list will pull from all clips in all selected items.

    This is what you want to do in this situation.

  • Wickham Strub

    February 9, 2010 at 4:44 pm in reply to: P2 Import to Suite

    Frank,

    As Floh mentioned, M100 cannot currently handle AVC-Intra “natively”.

    As for the DVCPROHD clip, however, a clue might be gained by going to:
    “Media 100 Suite” menu > Project Settings > Codecs…

    In there, under the “HD” tab, see if “DVCPro HD” is greyed out in the drop-down menus. If so, that means that a codec component that can understand DVCPro HD is not installed. If installed, the component would be found in: MacHD\Library\QuickTime.

    Most often, they get there by installing Final Cut Pro. However, there are other solutions (Flow mentioned Calibrated Software) out there in the world.

    Hope this helps more than confuses.

    ~Wick

  • Wickham Strub

    February 8, 2010 at 5:12 pm in reply to: Very disappointed M100 long term user

    Well… I suppose we should be happy that people care enough about Media 100 to get upset over it. I choose to see that as a good thing.

    For those of you that didn’t get a notice about the webinar, I apologize. We sent the email using the same methods that we always have. No one was deliberately excluded and we’re looking into why some did not receive the invite.

    We are planning to send a “What’s Coming in v1.5” email later this week. When it goes out, I will post here so you can all look for it. If you do NOT get it, please let us know so we can track what’s going on.

    I’m going to start a fresh thread now with bullet points of the new features in v1.5. See you there.

    ~Wick

  • Wickham Strub

    January 28, 2010 at 8:14 pm in reply to: Time Code Burn In

    Well… if you double-click a clip into the Edit Suite then of course the Burn-in is showing source timecode. However, I’m sure you want it coming form clips in the Program. That you cannot do, sorry.

    Can you do me a favor and share exactly what the great advantage would be to have the source timecode. When I follow the idea through to the end I always end up realizing that the “Program” timecode from the burn-in points me to the correct clip in the timeline which then has it’s “Source” timecode when I double-click it into the Edit Suite.

  • Wickham Strub

    January 28, 2010 at 6:53 pm in reply to: Export File Crash.

    As long as we’re on this subject, let me give you all our guidelines for troubleshooting this particular complaint…

    —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —– —–

    When someone says, “It crashes when I try to export,” there are 3 points at which the crash is likely occurring.

    1. Go to the File Menu, choose Export, crash before Export dialog comes up.

    This is almost ALWAYS about a codec in MacHD/Library/QuickTime. Move any suspicious codecs out of their Log Out/In or Restart and try again.

    2. Go to the File Menu, choose Export, make your Export choices, click the “Export” button, crash before export really starts happening.

    This is almost ALWAYS the Media 100 “plist” file named “com.Media100.Media100Suite.plist” found at: YourUserFolder/Library/Preferences. Quit M100, delete that plist file, relaunch m100 and try again.

    3. Go to the File Menu, choose Export, make your Export choices, click the “Export” button, export starts and then crashes sometime before it finishes.

    This is almost ALWAYS much harder to figure out what it is. It could be memory, could be a drive problem, it gets murky. Luckily though Scenarios 1 and 2 are MUCH more common.

  • Wickham Strub

    January 23, 2010 at 2:58 am in reply to: .cr2 file import

    I think they probably will NOT import without some conversion. However, do some test on a few photos first to get the recipe right and then apply a Photoshop action to the files in a batch.

  • Wickham Strub

    January 23, 2010 at 2:55 am in reply to: .mov and M100 quicktime

    Yeah that’s me. Thanks for the kind words.

    They tricked me into becoming the Product Manager a couple of years ago.

    Hurry up and finish that project so we can sell another system will ya!? 😉

  • Wickham Strub

    January 22, 2010 at 10:14 pm in reply to: .mov and M100 quicktime

    If the music guy in on a Mac you can include the M100 Codecs installer.

    The Intel-friendly one is here:
    https://www.borisfx.com/login/m100_reg_form.php?action=m100CodecsIntel

    The PPC flavor is here:
    https://www.borisfx.com/login/m100_reg_form.php?action=m100CodecsPowerPC

    If that doesn’t help, try exporting to some other codec that the music guy can play on his system.

    File > Export > Other > QuickTime then click Options, there’s all kinds of choices in there. Also remember that they may not need the file to be full frame size, going with 480×360 can save a lot in file size.

Page 1 of 33

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