Timothy Gassen
Forum Replies Created
-
Thank you, Bill — that is exactly what we were hoping to find! 🙂
And Daniel, Encore previous to CS6 had a bug that rejected some 2-pass VBR blu ray compliant files — this was a random and intermittent problem that many users suffer through, including me. It was an Encore bug for several YEARS, lol. I really do hope it is fixed also on the PC side…
And the Enore project-size bug is ongoing it seems. Encore will report a Blu ray project as being MANY GBs larger than the actual encodes, menus, etc. This would be OK if it actually would burn to folder or disc correctly — but it is reporting our current 21.93 GB project as 27 GB and thus too large to burn!
Other than lowering our encode size needlessly, wasting many GB of open space on a blu ray, in order to “fool” Encore into buring a disc, is there any work-around? (If you build to a disc image, it says the project is then 24.1 GB, still too large to burn.)
A 21.93 GB project is within disc headroom safety margins — it SHOULD be able to burn to a 25 GB blu ray, shouldn’t it?
Thanks for any help.
Timothy Gassen
Director/Producer -
Thank you again for all your help, Floh. I’ll get your clips back into a Mac ASAP and I’m excited to see them!
Timothy Gassen
Director/Producer -
Floh,
I’ve uploaded a zipped folder with some small test Media 100 QT files and a READ ME file here:
https://www.sendspace.com/file/9blvap
Click on the blue box midway down the page that says “click here to download from sendspace” to avoid the spam links.
Let me know if this works for you, and thank you again for your help!
Timothy Gassen
Director/Producer -
Floh,
Would you like me to e-mail you privately with a file link location, or post it here? Thanks again for your help!
Timothy Gassen
Director/Producer -
Many thanks for your kind offer to help, Floh!
Perhaps this a simpler (smaller file) way to test: I send a still frame (or short QT export) from my PC Media 100 for you to import into your Mac Media 100, then you export as an uncompressed QT file for me to compare?
Timothy Gassen
Director/Producer -
Many thanks for your thoughts, Gerry!
I’ve had to use Avid and now FCP for specific productions, but Media 100 (on the PC side) is by far the most productive NLE I’ve ever used. I really hope I can avoid having to build a FCP system – there is nothing about it I find superior.
Getting quality QT out of any system is a priority to me — we certainly cannot control how users have their own displays set, but as the creators we should be able to export an image-accurate final master file or tape!
Yes, I’ve heard that Boris FX is very powerful (and complex/non-intuitive) — I’m betitng an FX work I’d do with a new Media 100 would be done in AE and Magic Bullet, so those workflows are what I am investigating with a new Media 100…
Thank you again!
Timothy Gassen
Director/Producer -
Hi Floh,
Good to hear from you — I’ve read MANY helpful posts form you!
Gamma shift with FCP QT files is a widely known issue for years now — basically QT and FCP add a gamma tag to QT on export (or on import of DV footage through firewire, some say), and the resulting export files (and DV tape output) are noticably lighter (gamma shifted) than the original footage. I am not referring to how computer screens and TVs display differently — the gamma shift can be seen in encodes for web video, DVD, bluray and master export files at full resolution. Gamma can display incorrectly on both Macs and PCs and in applications on both platforms. (See my recent post in the FCP forum explaining this again and again, lol.)
Ater reading hundreds of online posts and talking with numerous FCP users — there appears to be no fix other than adjusting the gamma on export through Compressor.
With my Media 100 on PC I can export gamma-correct QT AND excellent quality to DV tape through firewire that look exactly like my timeline and original footage. It appears I can do neither in FCP.
Since I’ll only be doing tape-out for legacy media with a new Media 100, file-only export is obviously important — so I was wondering if the new Media 100 was able to export gamma-correct files.
Thank youu again for your help!
Timothy Gassen
Director/Producer -
FYI: To turn on Quicktime legacy codecs in Snow Leopard: open Terminal then “Shift + Command(⌘) + N” and enter the following code:
qtdefaults write LegacyCodecsEnabled yesAfter more test encodes, P-JPEG is not working for our SD footage. There is no control for field dominance in the export to P-Jpeg, and it appears to be upper-dominant, causing obviuous confilict with our lower-dominant SD footage.
M-JPEG quality is good, but a shame that in order to use the gamma correction on export that we have to go through Compressor, and can’t do a straight QT Export or use Conversion…
FYI: After tests, a gamma correction of 1.3 in Compressor appears to make our final QT files have the same gamma as the original master footage…
Timothy Gassen
Director/Producer -
Thank you, all, for sharing your thoughts with me.
Gary, when you wrote, “You’ll be able to use Boris with some cool fx but requires a lot of rendering, learn FCX instead.” — did you mean “learn After Effects instead” or that you prefer Final Cut X instead of Media 100?
And since third-party apps like AE and Magic Bullet can’t run inside Media 100, I’m interested to hear how users here are round-tripping files for FX work out and back in to the latest Media 100.
And after weeks of searching I still can’t find an answer for what NLEs, if any, can import & export gamma-correct QT files. After talking with many FCP users (at TV stations and other professionals) it seems that FCP cannot do this essential task. In a tapeless world this seems to be a major problem!
So, if I’m not going out to some kind of tape format, can I make gamma-correct master output files from Media 100?
Thank you again, all for your help!
Timothy Gassen
Director/Producer -
Rafael (and all),
Thanks again for your responses and patience as I try to learn & figure this out!
As for P-JPEG vs M-JPEG, I found this, credited to “Sam Bushell,
QuickTime Engineering” – “If you’re compressing non-interlaced content, use Photo JPEG. If you’re compressing interlaced content in software in the abscence of any hardware or expected hardware, you should choose Motion JPEG A.”Again, I am not an expert and I dont’ know which codec is appropriate, so I’ll try more P-JPEG tests along with M-JPEG…
BTW, we were able to (after much hoop-jumping) re-insert the M-JPEG codec back into Compressor. We must not be running the newset version of QT, where that option isn’t allowed…
As for our DV out problem: Yes, we changed our sequence to a better codec for the edit, but I thought it needed to be copied back to another sequence and re-rendered as DV before it could be sent back through firewire to a DV/DVcam deck? We did try sending to firewire from our uncompressed-codec sequence and it DID go to firewire, but again in what appears to be the “draft quality” that we got from our DV sequence. Again, the video played from our timeline looks OK — the video sent through the firewire has additonal “mosquito-noise” artifacts. All our settings are set to Full/Best…
Thank you all again for your thoughts and suggestions!
Timothy Gassen
Director/Producer