BIG GREEN BAR (when trying to export to m4v with compressor)???

[Alec Eagon]

Does handbrake have the same “Frame Control” capabilities as Compressor?

I am only exporting .m4v (“h.264 for Apple Devices”) on a recommendation that it can really help avoid gamma/color shift issues, since many an attempt with Squeeze has still rendered unsatisfactory results.

Thanks
Alec

Alec E.

[William Carr]

This forum is unmatched to learn how to get a step forward, figure what steps we’re taking that might be broken, and quite frequently, what workarounds will get us where we need to go.

I hope someone answers your very specific query. In the mean time, folks have taken time to give you some very decent ideas here.

It seems you’re saying, if that original workflow recommendation is not carried through in the manner you intend, the compression quality will be unacceptable.

When you say “Every digital video I’ve ever worked with ends up looking better on the web the less compressed it is before the final for-the-web crunch (yes even on Apple devices).”, you are stating the obvious. Less compression looks better. You want the best and least compression possible, as do we all.

The fact is there are many ways to make an h264 for the web that yield excellent results. I do a lot of uploading final projects to Vimeo; their thoughtful recommendation is to make a 1280×720 h264 at about 5Mbps. Why not just try that from your ProRes using Compressor or Streamclip or AUNsoft or whatever and upload to Vimeo with privacy on and see how it looks. It will probably look great.

[Eric Strand]

No, Handbrake doen’t have frame control capabilities, but it does have presets for Apple Devices and uses the x264 codec, which is superior to Apple’s version of H264. It will make a great looking file from ProRes HQ.

As William Car says, [William Carr] ” their thoughtful recommendation is to make a 1280×720 h264 at about 5Mbps. Why not just try that from your ProRes using Compressor or Streamclip or AUNsoft or whatever and upload to Vimeo with privacy on and see how it looks. It will probably look great.”

[Alec Eagon]

I am very sorry if I came across as ungrateful for the workarounds. I really do appreciate them.

I probably don’t have as much experience as you, but I have uploaded my fair share of videos to Vimeo as well employing countless methods and test using Squeeze 8, Adobe Encoder, Mpeg Streamclip, Compressor, VLC, Handbrake, QT7 and others.

For the last year I have been working with mostly Apple ProRes (HQ) film scans. The last project I worked on I spent two weeks working overtime with said programs to produce a satisfactory result on Vimeo…my conclusion?…(and again, this is just speculation since I am not a programmer or engineer), because of the nature of image capture via randomized grain and the latitude of film, achieving a workflow [Film > ProRes (HQ) > Vimeo] that produces a satisfactory result is incredibly difficult and requires a ton, and I mean a ton, of experimentation.

I am experimenting, following up on a lead with this whole .m4v Compressor Export thing, thus I am simply trying to get to a point where I can get this program to work the way it should, to actually do what it says it can do on my hardware setup.

Again though, I really appreciate the workarounds as they will undoubtedly provide me with other leads to follow in the future if this one doesn’t work out.

Alec E.

[Alec Eagon]

Yes, there is NO green bar when I open the FCP Ref file or when I open the Self Contained FCP Pro Res(.mov).

I appreciate the obvious questions. I make a lot of obvious mistakes.

Alec E.

[Alec Eagon]

Okay great. So, on that thread I posted at the top, someone else mentioned that they were having a similar problem with their Compressor on their 12-core (like me) but not with Compressor on their laptop. I just exported the same file to .m4v with Compressor on my laptop (4-core) and it was successful.

What sort of issue could this be between a 12-core processor and Compressor? …or might this just be coincidence?

Alec E.

[Immanuel Heims]

Hello from Germany,

I’m encoutering the exact same problem here on my MacPro 5,1 12-core machine. Before I had a MacPro 3,1 8-core and it worked flawlessly with Compressor resizing footage using Frame Controls. So, it seems to be Hardware-related. I also installed only FCP 6.0.6 and Compressor 3.0.5 on a fresh Mac OS and it produced the same green bars. It doesn’t matter which format you use as a source or destination. It also works with Frame Controls ON as long as the Image Size is 100% source. If it’s a different size, the artifacts suddenly appear.

Any ideas on solving this problem?
Thanks a lot!

creative media & more, Germany
Videography ❘ Postproduction ❘ Media Design ❘ Photography
MEHR ALS BEWEGTE BILDER. BILDER, DIE BEWEGEN!

https://www.immanuel-heims.com
https://vimeo.com/heims/albums/sort:alphabetical/format:thumbnail

s.d.g.