Personal View site logo
DaVinci Resolve 9
  • 179 Replies sorted by
  • vicharrisvicharris

    Yep, I couldn't see any washed out parts or it switching either.

  • shianshian

    maybe some timecode references, cuz I see no glitches whatsoever on the vimeo video, and the color and gamma look totally fine.

  • B3GuyB3Guy

    I'm just creeped out now. This is some seriously messed up stuff, whatever is going on. I'm working from an 8 Bit TIFF image sequence using Quicktime Pro (7). The TIFF sequence, of course, displays just fine, as does the H.264 file I create from it . . . but here's the catch-

    Only in windowed viewing. As soon as I go fullscreen, the color shifts and is incorrect. This must be the same issue that is causing the Vimeo encode to flipflop back and forth, whatever the "issue" actually is. I still have no idea.

    Attached is a comparison between windowed and fullscreen in Quicktime Pro (7). As I mentioned, these look like the two color modes that I see Vimeo switching between randomly.

    GOOD.jpg
    1911 x 552 - 84K
    BAD.jpg
    2560 x 757 - 119K
  • B3GuyB3Guy

    Well, I've acquired permission from the band to share the video footage with the forum in hopes that someone has a solution. This latest file cuts FCP out of the equation entirely. it is the 5DtoRGB ProRes 422HQ file, graded in Resolve and exported as individual 16bit TIFF images for each frame. I then used my newly-purchased Quicktime Pro (7) to export that TIFF sequence as an H.264 file via X.264 flavor of the codec.

    The TIFF images looked 100% accurate when played back in QT Pro (7), but the exported H.264 file is washed out when opened in QT.

    This is the same file that is uploaded here, AKA the "original" file.

    If someone with a few minutes could download it, and check it in QT/MpegStreamclip/VLC, that'd be awesome. The latter two programs seem to display it correctly.

    You will also notice that Vimeo jumps between "super washed out" and "kinda washed out" at random throughout the video.

    There is no sound.

    Password is: cpycpm

  • B3GuyB3Guy

    Seriously, all this color "science" stuff is ridiculous to wrap one's head around. YUV=YCbCr=CPbPr. Supposedly, It shouldn't make a difference whether YUV or RGB is uploaded to the web?

    I honestly am at square one with all this bull, and it is driving me up a wall. VLC and MPEG Streamclip seem to have no problem displaying my created H.264 files correctly, but Quicktime and Vimeo turn it into a sh*tshow, which has me genuinely pissed off. Nobody at Vimeo can tell me what is "wrong" with my files, and I'll be damned if I can find anything wrong with them myself.

    Eff video post-production. Eff it.

  • B3GuyB3Guy

    Oh. Well, that explains . . . wow. Ok.. ok. checks bank account for 30 spare dollars

  • shianshian

    QT Pro is QT 7 - not QT X which is dogshit.

    QT Pro is just the full featured version of QT 7 that allows encoding of all QT codecs, there is zero difference between it and QT 7 except you pay $30 to unlock all it's features,

  • B3GuyB3Guy

    As always, thanks to everyone her for the help/advice. Hopefully together we can figure out what I've done wrong and/or where the issue lies, for the benefit and future knowledge of everyone.

  • B3GuyB3Guy

    I've exported ProRes and used MPEG Streamclip, but MPEG Streamclip has nowhere to specify RGB versus YUV.

    I think the problem is before the NLE, when I come out of Resolve (ProRes 4444).

    At that point, I believe it is YUV (ProRes can be either from my understanding), and it stays YUV through the NLE and all the way through the H.264 conversion, because none of the programs for conversion (FCP/QT/Mpeg Streamclip/Handbrake) are able to see/specify the difference.

    I will give QT Pro a try, but seeing as it displays the ProRes files incorrectly, I rather doubt it will be able to convert them correctly. To be honest, I quite dislike QT Pro. I know some really like it, and use it to mate image to audio, etc. but it runs like crap and doesn't play back some stuff that QT 7 seems to handle fine, at least in my experience.

    Am I at least correct that web video should not be YUV?

    I may just contact Blackmagic to see what they say. At this point, Vimeo has actually expressed interest in my findings concerning YUV versus RGB.

  • shianshian

    Have you tried exporting ProRes and then using QT Pro for h264 export... I never do it inside an NLE... you always get shit.

  • B3GuyB3Guy

    I'm still having issues. There are so many dang settings in this crazy program, none of which have much explanation as to what they do. I understand it is a pro piece of software, but honestly!

    No thanks to Vimeo support or anyone else, I've tracked down what I hope is the problem. Now if only I could solve the problem! My grade looks wonderful in Resolve. I export ProRes 4444 and pull it into Final Cut Pro, and it still looks fine. Render the overlays (titles, grain), play back and it still looks fine. Now . . .

    Export with x.264/H.264 (I've tried both now more times than I can count), and the resulting file looks terrible in all QT-based programs. MPEG Streamclip sees it correctly, as does VLC. But Vimeo has assured me that whatever Quicktime sees is what their re-encode will spit out (so far I have found this to be true.)

    Upon careful investigation, VLC was able to tell me that my file is, in fact, YUV, not RGB.

    But I'll be darned if I can figure out how to avoid making a YUV file! Every setting in Resolve where I see any option for YUV, I have switched to RGB. No dice. The blasted file is still YUV at the end of the day.

    If anyone can help, that'd be fabulous. I'm just about ready to quit this whole affair. I love what Resolve does in-program, but it has otherwise proven to be a royal PITA.

    (Attached are screenshots from VLC and from Quicktime 7 respectively for comparison. Quicktime X of course crashes without even playing back the file.)

    Screen Shot 2013-10-28 at 3.21.53 PM.jpg
    1944 x 1089 - 198K
    Screen Shot 2013-10-28 at 3.23.46 PM.jpg
    1937 x 1096 - 219K
  • tinyrobottinyrobot

    @B3Guy Figured it out as I forgot. On the Delivery page, you have to set for all values in the color range.

  • tinyrobottinyrobot

    I am having a similar problem with B3Guy. I had problems with my gfx card, so I did a system restore and installed DaVinci Resolve Lite 9.1.6. I think this is the same 9 version installed before. What I see in Resolve and the output is totally different. Like B3Guy, Darks seem to be lighter and less contrasty in the output. What happened here?

  • B3GuyB3Guy

    Hi, All I'm having trouble with Resolve 9.

    It is not exporting the grade that I have currently done. It looks one way with in Resolve (even the preview as it exports), but the final file looks like a previous version of the grade.

    I have no idea why it is doing this, can't figure it out. I deleted the previous version, emptied trash, even saved the new file in a new location, and it has messed it up twice.

    The green one (yuck!) is the exported file that I'm getting, the other one is what I see in Resolve 9 before exporting. (screenshots)

    Bad.jpg
    1945 x 840 - 224K
    Resolve.jpg
    1648 x 711 - 170K
  • shianshian

    try reconnecting instead. they should be similarly named.

  • vicharrisvicharris

    Just updated with new version. Still does it. I'll wipe it and try that. It's odd. I have all the individual QT files that were graded. It sucks but I can just pull those into FCP and line em up in the timeline. Ghetto, but it works for now.

  • shianshian

    Sounds like something funky going on in Resolve. maybe try reinstalling it. I had some issues back in the day, and the reinstall fixed it.

  • vicharrisvicharris

    Oh shit, sorry ProResHQ all the way through.

  • shianshian

    what codec? - Both edit and export.

  • vicharrisvicharris

    OK guys, I've been looking for 3 hours online and can't find an answer so I'm going to throw out a problem here. I'm trying to bring back in footage from Resolve, into FCP7. I followed all the normal directions and for some reason, FCP hangs on the import. Sometimes at 0% sometimes 50%.

    Process: Edit in FCP

    Export XML using version 5

    Import XML in Conform

    Color

    Render Project using Final Cut Pro Round trip settings

    Go back in Conform, Export XML to same drive as all footage

    The when I try to import into FCP7, it just hangs.

    Hope that's enough info.

    Shouldn't be a computer problem as it's a newly built Hackintosh.

  • kankalakankala

    Was updated to 9.1.5, here's direct download link to Lite:

    http://software.blackmagicdesign.com/DaVinciResolve/Lite/DaVinci_Resolve_Lite_9.1.5_Windows.zip

  • GravitateMediaGroupGravitateMediaGroup

    Anybody that is knowledgeable with Resolve PM me or respond here if it's an easy fix. I'm having an issue with resolve only rendering a flat image instead of my grade. I wasn't having this issue until today so I'm guess I accidentally hit a keyboard shortcut that triggered this issue.

    UPDATE - Solved the issue. It was something to do with a LUT setting.

  • artiswarartiswar

    @tinyrobot - Right click and chose use local version for all clips (shift select them all).

  • tinyrobottinyrobot

    Question for Resolve users.

    I imported an xml from PPro that is one continuous clip with a razor tool cut that separates a white graphics and the video. In DaVinci, under Conform the "cut" clips are represented as separated clips while one video clip is in the Media Pool for both of them. In Color, two boxes represent the "cut" clips. I only want to grade the video portion and not the graphics portion, but whenever I do it, both clips take the same grade. I know it's because they are from the same media clip as represented by the orange arrow in the upper left corner. Is there a way to unlink them so the first one isn't effected by the grade?

  • Vitaliy_KiselevVitaliy_Kiselev

    Guys, will all related to resolve 10 go to

    http://www.personal-view.com/talks/discussion/6641/davinci-resolve-10#Item_3

Add a Comment