Mel Matsuoka
1
COW Coin
Forum Replies Created
-
I reported this same issue a few days ago:
https://forums.creativecow.net/readpost/3/942755
Glad to know it’s not just me!
-
[Matt Galuszewski] “I have a short duration (2min) sequence setup for preview files as ProRes HQ, 1280×720, 25p. The clips are all MXF from a Canon XF300. Some of the clips are green screen over a Premiere generated color matte.
When I export this sequence directly from the export window or by queuing to AME I see no problems exporting to any flavour of ProRes.
I went back and inserted some new Premiere generated color mattes and also had no problems during export.”
My source media is 1080p23.976 ProResHQ. Try it with ProRes source clips, not MXF. I’ve replicated this behavior on every machine I’ve tried it on.
-
Doesn’t matter if I render first, or if I kill all the renders before exporting.
The GPU shouldn’t be playing into this error, since as I mentioned I’ve tried dropping into non-GPU MPE mode, and it doesn’t change the behavior.
-
[Eric Hansen] “why did BMD recommend against 32GB of RAM?”
If I recall, it was a memory bandwidth/timing issue that affected performance in Resolve 8 (when it wasn’t a 64-bit app).
-
[Al LeVine] ” Cannot match frame a freeze frame in the viewer, or change a freeze frame’s duration. Because I work in animation, I freeze frame quite a bit. In FCP 7, I would SHIFT+N to create a freeze frame, then drag out a duration.
Seems the only solution I can find is to export a JPEG still, then bring it back in… a lot of steps.”You’re working too hard 🙂
You can freeze a clip by right clicking on it in the timeline and choosing “Frame Hold”. You can extend the length of the freeze by using the Rate Stretch tool and dragging the outpoint to however long you want it.
-
Thanks Laco, it never occurred to me to use an EDL to bring in selects. Thanks for reminding me of this!
Only problem though, is that the Clip Task Manager does not appear to want to copy DNG files in this manner. The “remark” column just flat out says “dng files cannot be copied.”
Argh.
-
Paid professional support for software tools is *so* 1990’s!
(or at least that’s the impression I get, the way the rest of the industry is going…)
Count me in as someone who WANTS to pay for his tools, and the requisite professional level support that’s generally required for them.
That said, the BMD Resolve team has been incredibly responsive and generally timely with the support they’ve given me since the Da Vinci acquisition. I’m very impressed. Although I do wish they offered a more solid and sustainable revenue model (read: higher prices for the software and/or paid support contracts) that does not depend on the success of the BMD Cinema Camera or Decklink cards in order to maintain the development of Resolve itself.
-
[John Pale] “You have 3x 570 cards??
This may be a PCI bandwidth issue.
Try running with one card to test if performance improves. Premiere can only make use of one card for CUDA anyway.”
The other 2 570’s are in an external Cyclone PCIe chassis, both in x16 slots. Though it’s definitely worth testing this without the Cyclone in the equation to see if it changes anything. Although it would seem crazy to me that it would, since I cant imagine simple JKL shuttling requires a lot of CUDA processing power, if at all, considering FCP7 can do this just fine.
In any case, the problem also occurs on our other editor’s machine, which is running the AJA Kona3 board, with a single GTX570 in it (i.e. no PCIe expansion at all), so I seriously doubt that it’s a PCI bandwidth issue. But I’ll still give it a shot, just to eliminate it as a possibility.
-
[Tom Daigon] “You are running the most up to date Plugins (2) from AJA right?”
Yes. Latest Kona CS6 plugins are installed
There is no CS6 specific plugin driver for Decklink hardware, unlike AJA, but I am running the latest Decklink drivers as well.
-
Also, this JKL lag does not occur in FCP7 or Avid MC6.x, using the same hardware configs.