Joakim Ziegler
Forum Replies Created
-
Just a word of warning, QTChange has what’s probably the worst user interface in the history of the Mac. But it’s still pretty useful, and it’s worth the 25 dollars I paid for it. Just don’t expect it to be intuitive. Or pretty. Or sane. Or not headache inducing.
—
Joakim Ziegler – Postproduction Supervisor -
No, as I said, if you change this in QT player and then save the file with QT player (Command-S), it fixes the problem for at least some other third-party software. It actually alters the settings in the file on disk. ProTools, for instance, will display blurry, low-res DV files if this options is not set, but will display them just fine after doing this.
Although Resolve might not respect this setting, it’s still a setting in the QT file, not just in QT Player.
—
Joakim Ziegler – Postproduction Supervisor -
Does the Retina support mean it’s no longer necessary to run the 1920×1200-like resolution setting on the MBPr Retina? It’d be nice to be able to step down and not use up all the VRAM for that…
—
Joakim Ziegler – Postproduction Supervisor -
I don’t know about the rest of the problems, but the “half-res” looking thing you’re seeing in QuickTime Player is usually fixed by setting playback to high quality. (Properties (Cmd-J), select video track, then Visual Settings and select the “High Quality” checkbox, then save the file). This is often not necessary in many Apple programs, but is necessary to get third-party software to show the file correctly. I’ve had this problem with ProTools in the past, for instance. Note that I haven’t tried it with Resolve, but it’s worth a shot.
—
Joakim Ziegler – Postproduction Supervisor -
While I’m unsure about EasyDCP, many programs misinterpret Rec.709 and use the rec.709 camera encoding curve as a decoding curve for the material. This is wrong. Rec.709 material should be decoded using a 2.2-2.4 gamma curve, not the rec.709 encoding curve. I know some DCP authoring software gets this wrong, including DoReMi CineAsset, which we use.
This would explain why things look basically correct if you interpret the input files with an sRGB curve. sRGB is not a pure gamma curve, but its overall gamma is about 2.2, so it would look much closer to correct than the rec.709 encoding curve.
Your “rec.709” monitor which you’re using to color correct has 2.2-2.4 gamma, so that’s why it basically matches.
What you’re seeing is correct, but you should try to use a gamma 2.2-2.4 curve instead of the sRGB one in your DCP authoring software to be 100% correct. sRGB should not be used. Experiment with gamma values between 2.2 and 2.4 to find the one you’re happiest with. I think we’re using 2.3 at the moment for this.
—
Joakim Ziegler – Postproduction Supervisor -
Peter, this sounds promising. I’d love to know more if/when you upgrade to Mountain Lion. How old is the IBM LTFS package? How often do they issue upgrades?
—
Joakim Ziegler – Postproduction Supervisor -
I totally agree, this is very annoying. It’s not annoying because there’s a lag between the UI monitor and the video output, the lag between the UI monitor and the video output is just a symptom of the bigger problem, which is that there’s a 12-13 frame delay between any operation you do and the result being displayed.
This is the single area where Resolve is not equal or superior to most other DI systems, in my opinion. Pretty much all others are instantaneous (or rather, with a delay of perhaps 2-3 frames at the most).
You get used to it, but it’s still annoying, and slows you down, especially when you’re doing fine color adjustments.
—
Joakim Ziegler – Postproduction Supervisor -
Any more news on this? It’s been a while…
—
Joakim Ziegler – Postproduction Supervisor -
No, I’ve actually kind of put it on hold for the moment, since I can’t find good info. I talked to a guy from BackupWorks.com who said he had mostly sold HP drives for LTFS on Mac OS, but he couldn’t give any more info. HP definitely seems to be the most common, but as you say, not officially updated. The IBM implementation seems better supported, but I’ve not been able to find anyone who’s actually used it.
I’d really love to hear from other people here who have more experience.
—
Joakim Ziegler – Postproduction Supervisor -
Discovered the backup forum just after posting this, so apologies. If anyone here has experience, I’d still love to hear it, though.
—
Joakim Ziegler – Postproduction Supervisor