- Posts: 130
- Joined: Thu Sep 15, 2016 3:08 am
One of the most asked questions has got to be — “is my machine powerful enough for Resolve?” The answers generally move folks toward wanting/needing lots of power. Also, there seem to be many posts about which GPU card to buy/use. While there’s nothing wrong with owning a hot machine, I’ve seen posts on other forums where people say they can't try Resolve because their computer "isn’t powerful enough.” That's a marketing negative for BM.
1) On my 15” MBP with Nvidia 750M, the primary place Resolve IS VERY slow is decoding h.264 media. While FCPX will play 2 streams of 4K XAVC WITHOUT needing to generate or use either a proxy or an intermediate codec, Resolve stutters along. Transcoding is necessary — which means an unfortunate wait.
2) But if one must wait -- what level of machine is really needed to run Resolve? How about a $900 tablet?
>>>> DETAILS: The Samsung Galaxy TabPro S has an Intel Core m3 Dual-Core 2.2GHz (Turbo) 6th generation processor with a Intel HD Graphics 515 GPU driving a 12-inch 2160×1440 pixel SuperAMOLED screen. For RAM there’s 4GB and for storage there’s a 128GB SSD. The Galaxy TabPro S is 693 grams. The tablet has a detachable keyboard. <<<<
3) Oddly, I could not download from BM to the tablet. So I downloaded using my Mac and dropboxed it to the tablet and installed it. Zero problems other than needing QT! I then dropboxed over test files including one 2K RAW file. (Yes, it deBayered as one would expect.)
4) In May — the tablet was a “mother’s day” gift — I began editing with Resolve using 480p24, 4080p30, 720p30/60, 1080p25, and 2160p24 (from Canon C300 mk2).
I learned to make full use of the fantastic new Optimization tools available. My test goal was playing graded footage at the correct framerate (green lite on). ALL formats met my test goals. (With UHD the green lite did flicker a bit. For all formats the green Iite flickered -- usual -- for the first second.) I exported my tests and uploaded them to YouTube.
4) Here is what I learned: V12.5 did not protest my Intel GPU or lack of “Open anything.” It ran without crashing. I was able to “cast” my screen to my HDTV via a Roku. (Very nice feature.)
5) The Core 6 was designed for a fanless tablet! (I didn’t initially know this.) I was able to edit SD for 6 hours—until the battery ran down. However, with UHD, run-time before either the display became corrupted or Windows TEMP ALARM caused Resolve to terminate, was 5 to 10 minutes. (Now I wonder about a cheap lightweight WITH a fan.)
6) My conclusion: the $900 tablet MAY BE fine for learning Resolve and/or editing SD or 720p. ( I edited p60 at p30 -- see why in my YouTube notes. However, I could directly edit p60.) Editing 1080p24 was time limited.
7) THE BIG PROBLEM >> even at the startup screen media I had been using would show-up as Media Offline! A bug? Fixed?
8) This week my Samsung Pen finally arrived and I was able to work without a keyboard using only pen and touch. The experience was normal in the sense Resolve behaved as Resolve. The odd part was walking around with a 1.5 pound device while grading.
NOTE: graded with a Timeline wipe and TRACKING POWER WINDOW (sorry for the yellow):
NOTE: graded using Keyframes.
NOTE: 2160p24 with simple FX
NOTE: my grade focused on the back wall which was my error. Very short because my summer location has 0.5Mbps upload speed that locks-out all downloading.
PLEASE READ EACH DESCRIPTION because I describe how to use optimization which is relevant to all computers.
NOTE: pictures of tablet being used in Vegas with Sony FS5 4K XAVC and with 4K monitor.
Perhaps this is not news to you. It certainly was a surprise to me. Comments very welcome.
1) On my 15” MBP with Nvidia 750M, the primary place Resolve IS VERY slow is decoding h.264 media. While FCPX will play 2 streams of 4K XAVC WITHOUT needing to generate or use either a proxy or an intermediate codec, Resolve stutters along. Transcoding is necessary — which means an unfortunate wait.
2) But if one must wait -- what level of machine is really needed to run Resolve? How about a $900 tablet?
>>>> DETAILS: The Samsung Galaxy TabPro S has an Intel Core m3 Dual-Core 2.2GHz (Turbo) 6th generation processor with a Intel HD Graphics 515 GPU driving a 12-inch 2160×1440 pixel SuperAMOLED screen. For RAM there’s 4GB and for storage there’s a 128GB SSD. The Galaxy TabPro S is 693 grams. The tablet has a detachable keyboard. <<<<
3) Oddly, I could not download from BM to the tablet. So I downloaded using my Mac and dropboxed it to the tablet and installed it. Zero problems other than needing QT! I then dropboxed over test files including one 2K RAW file. (Yes, it deBayered as one would expect.)
4) In May — the tablet was a “mother’s day” gift — I began editing with Resolve using 480p24, 4080p30, 720p30/60, 1080p25, and 2160p24 (from Canon C300 mk2).
I learned to make full use of the fantastic new Optimization tools available. My test goal was playing graded footage at the correct framerate (green lite on). ALL formats met my test goals. (With UHD the green lite did flicker a bit. For all formats the green Iite flickered -- usual -- for the first second.) I exported my tests and uploaded them to YouTube.
4) Here is what I learned: V12.5 did not protest my Intel GPU or lack of “Open anything.” It ran without crashing. I was able to “cast” my screen to my HDTV via a Roku. (Very nice feature.)
5) The Core 6 was designed for a fanless tablet! (I didn’t initially know this.) I was able to edit SD for 6 hours—until the battery ran down. However, with UHD, run-time before either the display became corrupted or Windows TEMP ALARM caused Resolve to terminate, was 5 to 10 minutes. (Now I wonder about a cheap lightweight WITH a fan.)
6) My conclusion: the $900 tablet MAY BE fine for learning Resolve and/or editing SD or 720p. ( I edited p60 at p30 -- see why in my YouTube notes. However, I could directly edit p60.) Editing 1080p24 was time limited.
7) THE BIG PROBLEM >> even at the startup screen media I had been using would show-up as Media Offline! A bug? Fixed?
8) This week my Samsung Pen finally arrived and I was able to work without a keyboard using only pen and touch. The experience was normal in the sense Resolve behaved as Resolve. The odd part was walking around with a 1.5 pound device while grading.
NOTE: graded with a Timeline wipe and TRACKING POWER WINDOW (sorry for the yellow):
NOTE: graded using Keyframes.
NOTE: 2160p24 with simple FX
NOTE: my grade focused on the back wall which was my error. Very short because my summer location has 0.5Mbps upload speed that locks-out all downloading.
PLEASE READ EACH DESCRIPTION because I describe how to use optimization which is relevant to all computers.
NOTE: pictures of tablet being used in Vegas with Sony FS5 4K XAVC and with 4K monitor.
Perhaps this is not news to you. It certainly was a surprise to me. Comments very welcome.