Forum Replies Created

Page 1 of 2
  • Colin Mcfadden

    June 11, 2014 at 2:47 pm in reply to: Clipwrap won’t finish processing

    Hi Bobby – I’m one of the ClipWrap developers. The best way to diagnose this would be to send us a console log during one of these hung conversions – usually it means we’re having trouble reading some bytes from disk, but perhaps something else is up.

    Launch the “Console” application (in Applications/Utilities) and then select “All Messages” from the left. Click the “clear display” button and then launch clipwrap and transcode a file. After it finishes, the console window should be full of text. Cut and paste that into an email to me, support@divergentmedia.com.

  • Thanks for the tip Shane.

    That error usually indicates a bad SD card or a bad reader.

    If you hold the option key while clicking the ‘convert’ button ClipWrap, it’ll change to saying “Force” and will try to ignore errors like this. Sometimes that allows the file to parse (though there could be bad chunks) – since you say the file plays ok in preview, it may be recoverable.

    Additional things to try – copy the full folder structure off the SD card to your hard disk . Does Finder complain about the copy? You can also try converting individual MTS files to narrow down which one is causing problems (Given the progress indicator there, probably the first file in the span).

    And feel free to contact us directly, support@divergentmedia.com.

  • We (ScopeBox) get frames at the same latency that a hardware output device (like a blackmagic card) would, so you’re looking at about 1 frame at worst.

    Because we get the uncompressed frame from FCPX, there’s relatively little additional overhead to running ScopeBox with ScopeLink (since we’re not having to decompress frames and such).

    We’ve got a free two week trial at https://www.divergentmedia.com/scopebox if you want to try it yourself, or shoot me an email if you have questions.

    -Colin
    divergent media

  • Colin Mcfadden

    December 19, 2013 at 9:20 pm in reply to: FCPX 10.1 locks up…

    Hi folks – Just wanted to jump in here. First off, we’ve got a fix against 10.1 pending. It should be out later today, but if anyone wants it right now, shoot an email to support@divergentmedia.com.

    Regarding doing a “ScopeBox Lite” or similar for ScopeLink, it’s definitely something we’ve considered. As a small company, it’s risky to make a move downmarket (you can’t really walk that back) so we’re very cautious in that regard. Obviously Apple has put a lot of pricing pressure on the pro video market with their aggressive pricing. For now, we’re comfortable saying that the feature set we deliver is worth the $99, but we’re always interested in ways of putting our applications in more hands.

    -Colin
    divergent media, inc

  • Colin Mcfadden

    November 14, 2013 at 10:35 pm in reply to: Howdy from ClipWrap

    There are two ways to store h264 I frame offsets in a QuickTime file. Premiere and iMovie like it one way, FCPX another. The files work either way, but you won’t get as fast performance if you mix incorrectly.

  • Colin Mcfadden

    November 14, 2013 at 9:22 pm in reply to: Howdy from ClipWrap

    This is an old thread – none of that stuff is relevant nowadays, as we’ve got a special dropdown in the app now to select the optimization.

  • Colin Mcfadden

    March 20, 2013 at 7:00 pm in reply to: Sony AVCHD Ingestion problems!

    If you want to drop us a line at support@divergentmedia.com, we can dig in (if you can also provide a sample mts) – it’s possible for there to be slightly inconsistent durations of audio and video tracks when moving things to QT, but it’d be odd for it to be the same amount for every file.

    -Colin (divergent media support)

  • Hi John – Just so I’m clear, did you enable the “allow framerate adjustment” setting in ClipWrap and then set a new value in the dropdown?

    If you’re not having luck, shoot me an email at support@divergentmedia.com and maybe we can grab a sample file from you to confirm with here.

    -Colin (divergent media)

  • Colin Mcfadden

    December 17, 2012 at 6:06 pm in reply to: Howdy from ClipWrap

    ClipWrap doesn’t support MOV->MTS conversion, though it may be possible using a tool like ffmpeg. I’m not sure if the issue described in that thread is related – it sounds like he may not have followed the steps to enable the special conversion mode.

    -Colin

  • Colin Mcfadden

    December 17, 2012 at 5:46 pm in reply to: Howdy from ClipWrap

    Hi Truls – I’m not sure I follow your question entirely, but if you use ClipWrap with the settings from:
    https://www.divergentmedia.com/blog/fullpost/clipwrapppro6

    the rewraps should perform just like MTS files. The only exception is that with very long files, we’ve seen a Premiere bug that causes it to reindex the files routinely. We’ve got a case open with Adobe on this issue, and hopefully they’ll fix it in a future update. (This issue impacts all long-gop quicktime files, not just clipwrap files)

    -Colin

Page 1 of 2

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