Shut down Resolve, power cycled mini-monitor = this time it froze the computer Opened up a previous project at 23.98 = worked fine, picture on screen, Desktop Video shows 23.98 Quit and Restarted Resolve = still no picture Power Cycled the mini monitor = still no picture Same as last time - 29.97, Non Drop, Scale Entire Image to Fit (default0 New Project, Same thing, but set scaling to Center Crop with no seizing, result = no picture Left scaling at default - scale entire image to fitīrought in SMPTE Color Bar to new Edit timeline Set up a new blank project and put it at 29.97 and ticked the box for drop frame. Now it pops up seemingly at random but I'm sure there's a reason for it. Prior to updating to Resolve 17 and updating the Desktop Video I never had an issue, I stuck around on 16 for a long time. Software: Resolve 17.4.2 Build 9 (orig presented on 17.3.1 Build 5), Desktop Video 12.2.1 (also tried 12.1) (often I'll have the Mini Monitor plugged into a BlackMagic EGPU pro, but I took that out to troubleshoot) Signal flow goes like this: 2017 iMac - TB3toTB2 Adapter - BlackMagic Mini Monitor - HDMI cable - TV Works in Media Pool, works in timeline, colors fine. Update - I created this project in Resolve 16, imported it into 17 database, and then when I bring in both sets of problematic footage and create timelines in this project they work fine, can color them, no problem at all. Appears to only be an issue with 29.97 footage, but I have other 29.97 projects that work ok, like a 1920x1080 ProRes 4444 at 29.97 non-drop (in a different database). I've also run into the same problem with 1920x1080 29.97 Dropframe footage that's ProRes422HQ inside an MXF wrapper, won't show on my screen. I have a classic Mac Pro running Resolve 16 over a Decklink Mini Monitor PCI card and it worked on there with the same footage just fine, so that's how I got around that issue during the project. But of course I can't do that because it's 23.98 and I need to output 29.97. However when I open a previously working 23.98 project and create a new timeline and put the same footage in that it shows up on the screen fine. This is from a cut up ProRes Export in a 1080p timeline. For example I've had 3200x1800 ProRes422HQ 29.97 non-drop that wouldn't output to the screen, not when playing clips back from the media pool or creating a new timeline from them. It appears to occur only on some 29.97 projects created in Resolve 17, but works fine on 29.97 projects created in Resolve 16 and imported into Resolve 17 I have a black magic UltraStudio mini monitor (thunderbolt 2) that on certain footage is not putting out signal to my 1080p screen, but otherwise almost always works. I hate to crosspost, but I posted this on the Black Magic Forums a week ago and got no answer when they used to be right on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |