Forum Replies Created

Page 72 of 1040
  • Craig Seeman

    November 17, 2015 at 1:17 pm in reply to: streaming videos on my website/ compression issues

    Algebra. Solve for X. You either need to enter file size or data rate to find the missing variable.

  • Craig Seeman

    November 17, 2015 at 1:20 am in reply to: streaming videos on my website/ compression issues

    Basic math
    data rate times duration equals file size.
    A simple bit rate calculator can help.
    https://www.3ivx.com/support/calculator/
    You know the duration and you want final size to be 1 GB (for example) and it’ll figure out the bit rate for you.

    The best quality codec (one that will give you highest quality with lower data rates) would be x264, High Profile, CABAC entropy. Multipass encodes may look better as well but take much longer to encode. Probably .mp4 container would be best.

  • Craig Seeman

    November 13, 2015 at 5:18 pm in reply to: Best iMac configuration for 1080p editing in FCPX

    [Noah Kadner] “Also load up on the fastest GPU as that’s where FCPX pushes the hardware the most.

    That may be the Achilles Heal of the 21″ iMac. The top of the line is only an integrated Iris Pro. As more things move into greater GPU use, it’s going to become more important. If one’s FX compositing and rendering needs are light the Iris Pro can be OK though. It depends on the type of post work you do in producing the Docs.

  • Craig Seeman

    November 13, 2015 at 4:15 pm in reply to: Best iMac configuration for 1080p editing in FCPX

    [Jason Ferris] ” have been transcoding to pro res for years”

    If you’re doing docs or long form, you’ll be saving lots of time and drive space. FCPX does Optimize and create Proxies internally if you set it to so even if you have to do that, it’ll be faster than FCP7. You’ll be able to start editing while it transcodes. Not having to do it can be best if your system can handle it.

    [Jason Ferris] “best cost/speed configuration for hard drive?”

    Fusion is less expensive but SSD booting and starting FCPX is faster. Fusion, because of the way it’s managed, is reasonably fast given how it manages the use of it’s small SSD like space. Keep in mind that your media should still be on an external drive. SSD primarily impacts boot time and speed of program access. If you need to save a little or need more internal drive space this is one area you can compromise and go with Fusion if need be. SSD would be preferred though.

  • Craig Seeman

    November 13, 2015 at 5:03 am in reply to: Best iMac configuration for 1080p editing in FCPX

    “Best” would be the top of the line with all the best BTO options.

    27″, Quad i7, 32GB RAM, 1 TB Flash Storage (SSD). AMD Radeon 395x. That woud total about $4099.
    Add the Thunderbolt RAID as per the rest of your budget to use as a media drive.

    Top 21″ would be Retina, Quad i7, 16GB RAM, 512 GB SSD, But only has integrated Iris Pro GPU. That would be $2399.

    The non Retina 21″ models only have i5 processors so I wouldn’t consider them. You can certainly edit FCPX on them but they may have a shorter usable lifespan as camera codecs demand more CPU processes and certain features push GPU resources as well.

  • Craig Seeman

    November 8, 2015 at 4:22 pm in reply to: Transfering huge files footage, good server to do it?

    I haven’t had to transfer files that big but I’ve used Mega (not to be confused with the defunct MegaUpload) although actually the same owner.
    Free Account is 50GB so you’d want a paid account. I haven’t notices any file size limits. I’ve transferred individual files close to 10GB.

    https://mega.co.nz/

  • [Anita Fontaine] “One thing to keep in mind is that not all kinds of video compress the same. You may notice that the following types of videos result in higher levels of artifacts or other visual imperfections:
    + Slow, gradual pans
    + Abrupt motion, or prolonged rapid movement
    + High levels of grain
    + Moving or shifting particulate
    + Fades in and out”

    Basically an encoder looks within and across frames to toss out repeated data to reduce file size. If there’s rapidly changing data from frame to frame (and this include grain/noise) it will try to preserve those but only within the limits of the targeted data rate with some variability (based on Variable or Constant bit rate settings).

    This means areas where there’s large amounts of change from frame to frame are most susceptible to problems. Upping the data rate often fixes that. Your encodes certainly look good so it’s their encode that seems to be the problem. I’d say this especially since you’ve tried both meeting their spec and doing a very high all I Frame encode as sources for them.

    In your case I believe the issue goes beyond that though. In addition, I believe encoders uses analysis of the content to do its work. Mixing flat and and gradient (your subject’s skin for example) in a frame can also cause problems. That’s why I think you should show them the specific frames but, my hunch, they’re not going to tweak their encoder for your video. I can post parts of two frames if you’d like but, again, I don’t think they’re going to accommodate the issue.

    [Anita Fontaine] “Did you also see this version? final-blur-v4..I’m also thinking this version where we blurred the background is maybe the best? “

    It does look the best because the blur makes the background most similar to your character since the background is less flat.

    [Anita Fontaine] “Maybe I can find a custom player which looks better to at least post on my site?”

    You should be able to host your own encodes if your website host supports that or, otherwise, find a professional service beyond Vimeo (or YouTube). There are services that support custom encoding.

  • Craig Seeman

    October 28, 2015 at 6:59 pm in reply to: Does anyone think FCPX is NOT a Professional NLE?

    [Steve Connor] “Simple question, I just wondered if there is anyone left on here who thinks it isn’t?”

    Of course but…
    It depends on many third party assets
    Personally I don’t mind that but what it does mean is that for someone considering “professional” work they need a research assistant to put togther all the components. I think this actually hurts most in the less glamours “pro” markets such as corporate and very small shops where Apple’s lack of marketing makes it very difficult to find the third party tools needed by many of the purchasing decision makers.

    While most of the discussion here points to Feature Film and Broadcast, there’s not much marketing in the wider “pro” market either where FCPX may be well suited. In fact there’s not much FCPX marketing anywhere. It’s not like they’re pushing it to the Event or Corporate market, not even the “consumer” market.

    Or perhaps, we’re entirely wrong. FCPX still seems to be the Top Grossing program in the App Store and ranks Sixth in Top Paid apps. Since this is Apple’s sales vehicle for programs, they may consider the App Store their best and most appropriate marketing tool. A business goes there to get OmniPlan and they’ll find FCPX.

  • Craig Seeman

    October 28, 2015 at 6:14 pm in reply to: Stabilize compound clip

    Why image sequence support would be important.
    Make sure to use the FCPX feedback form.

  • Craig Seeman

    October 28, 2015 at 3:49 pm in reply to: installed FCP X but no prores codec

    Keep in mind that if you download the FCPX trial, you pay nothing. When the trial expires you keep the codecs.

    The OP mentioned using MPEGStreamclip so my thinking is if it’s encoding he’s interested in then Compressor is well worth the $50.

    I run into this all the time, primarily for my live streaming consulting. Their focused on live production rather than post. Usually they want to do a local recording in ProRes so I point out the FCPX trial route. If they need to post encode the local recording for VOD delivery I suggest getting Compressor which will also get them the codecs.

Page 72 of 1040

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