![]() ![]() At least as far as any "critical" viewing goes. Which is why around "here" a lot of folks stay the heck away from it. play differently depending on which codec is used in Quicktime. always play like the original in PrPro, and since I changed the nVidia setup default they play the same in VLC, but. Quicktime treats the same output into different codecs differently. And that you as the "content provider" cannot control.Īfter changing the default nVidia control panel setting to assume 0-255, VLC seems to behave properly on my machine. Throw in the typical gamma mismatch between Quicktime and most anything else, you've got two variables that are WRONG. Given that many nVidia chipped cards set up with an assumed 16-235 range, and shrink all other material down into that range, there's a problem right there. with appropriate settings on the export, it SHOULD match the original. You can check if PrPro is exporting other than expected by bringing an exported clip back into PrPro. on all devices that will show your material. You cannot control those variables in other machines run by other people. it wasn't that PrPro had done a bad job, but that the gamma used by the video player was a bit different. it suddenly and completely matched the "original" example set side by side with the "bad export" example. In other threads when someone provides an example of "bad" export by PrPro, another user has taken the "bad" clip, changed the gamma inverse to what the used video player typically does, and gee. different video players treat gamma a bit differently. Now, let's throw on top the gamma question. as of course does contrast (the last two are linked, of course, as far as "data" goes). the darks just ain't so dark, the highlights mush, and the color tends to flatten a bit. Unless a video player (such as that within PrPro) insists on doing it's own thing, that will "rule" what happens. Similar to the note above in this thread by another person, my video card (EVGA GTX-770/4Gb of course nVidia based) installed itself using it's own default setup for video programs: 16-235. ![]() the issue is that the gamma or the outer-range of signal have been changed by a video player. The issue isn't that the color has changed in the file. Hopefully this doesn't turn out to be a bug but I don't think it is, because I use mpeg-2 several times a day when I export for broadcast and I haven't ever had it wash my video out in any media player at all unless my GPU settings weren't correct. Before they looked terrible though and Premiere looked okay. Video used to be washed out on my PC too but once I found the 16-235 and changed it then all my media players looked correct. Also could you upload a small test file that I could check on my system? The reason I don't think it would be good to make the color darker is because I'm thinking this is probably a GPU/OS on your specific machine possibly causing the issue. There are a couples settings mac's have that make things look washed out. Scroll to the bottom of the post there is also one towards the middle that might help. Unless their is some wierd bug going on here.Īlso often times with mac's you need to check the following settingsĬheck this too. ![]() I'm not sure how to weak this on a mac though but you need to make sure your colors aren't set to 16-235 because that's what I'm starting to suspect, because I haven't ever had issues with mpeg-2 appearing "washed out". Do you have a NVIDIA graphics card? Sometimes when people have NVIDIA GPU's and they have their color range set to limited 16-235 it causes stuff in their media players to look washed out. Since you're having issues with mpeg-2 I know something wierd is for sure going now. According from how they made it sound on provideo and the one other site I read it on anyways. But Premiere isn't affected/fooled by this like most media players are. I've always just assumed Premiere was somehow correcting it, because when I export my video to mpeg-2 for playback on our server it looks like it looked in Premiere.įrom what I have read though the reason the Quicktime format does this when using the h.264 codec looks and looks washed out is because of a incorrect gamma tag. However when I import ProRes files into Premiere they don't appear washed out, but when I play them in Quicktime or VLC they do appear washed out. I've never experinced a gamma shift when using the standard h.264 format option in Premiere, however if you have already used that option and you're still having issues then I have no clue what is going on. A couple of the articles I posted are supposed to "fix" the problem although I haven't ever tried any of them myself. If you read around the net a lot of people have had this issue with h264. mp4 container? If you used the Quicktime h.264 the option itself is flawed. Did you use Quicktime's H.264 export option? Or just standard h.264 using the. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |