can't export 8K video.

1st got to 15% then I saw Resolve had closed. Tried again while watching and it got to 72% and closed.

Logs + system specs (the nfo thing)

1st got to 15% then I saw Resolve had closed. Tried again while watching and it got to 72% and closed.

try first to render an intermediate codec like DNX/Prores and from that one go to H264/H265.

I assume (having no other info) that your system in underpowered for what you want to do.

I would expect a 8k video to need at least 12gb vram with bare minimum of grading on it.

What GPU do you have?

I’ve seen the same card crash when exporting straight into H.265.
Do what Walter suggested or render into Cineform.

System is a Dell XPS PC. 32G RAM, Win 11, Processor 12th Gen Intel(R) Core(TM) i9-12900, 2400 Mhz, 16 Core(s), 24 Logical Processor(s), 2T solid state C: drive. NVIDIA GeForce RTX 3060. Videos are on Internal Seagate 16T Ironwolf.

I built based on the recommendation of a friend's suggestions. He does 8K though its difficult. His system is 3 years older and I went a little further and he thought I should have no problems.

Videos are on Internal Seagate 16T Ironwolf.

Fwiw, source media playback from a single spinning disk is sub-optimal... maybe try changing your Delivery Page > File tab > Render Speed setting to something like 10fps. If there's any file IO type issue at play then that should give your spinning drive a little more time.

Current setting is Quicktime H.264
I see DNxHD, DNxHR and goPro cineform, but not DNX/Prores

not DNX/Prores

I'd love to have that as an option - for all three platforms!

So while waiting for further insight, I started a 4K video, which I've made many of, and on the 2nd go through in cut mode to trim more I got a spinning circle, and it is locked up. Wanted to check the task manager performance I had open on the 2nd monitor, but the full screen of Resolve clip blocks so I can't.

Hmm. Did you already try to remove all USB devices except keyboard and mouse (in case you have any)?
If not, do so, make a fresh install, restart the computer and try again.

System is a Dell XPS PC. 32G RAM, Win 11, Processor 12th Gen Intel(R) Core(TM) i9-12900, 2400 Mhz, 16 Core(s), 24 Logical Processor(s), 2T solid state C: drive. NVIDIA GeForce RTX 3060. Videos are on Internal Seagate 16T Ironwolf. I built based on the recommendation of a friend's suggestions. He does 8K though its difficult. His system is 3 years older and I went a little further and he thought I should have no problems.

Why do you believe you need 8K? Where is this going to be shown? I honestly don't see the point.

I have no problem with 4K, because it's actually a real distribution medium you can see, on TV and in theaters. 8K to me is more of a camera acquisition format... and even then, we generally advise clients crop to 4K during final color.

does your friend who is doing 8K have the same amount of VRAM?

.
I have no problem with 4K, because it's actually a real distribution medium you can see, on TV and in theaters. 8K to me is more of a camera acquisition format... and even then, we generally advise clients crop to 4K during final color.

Something I've been wondering about related to this. Is it better to (i) grade the 8K video in a 4K timeline or (ii) grade in an 8K timeline and then export as 4K or (iii) actually crop the clips using Input Sizing and work in a 4K timeline? I’m guessing the main advantage of ii or iii would be it's easier to work with in terms of playback. Is there any difference in quality of the final exports?

Current setting is Quicktime H.264
I see DNxHD, DNxHR and goPro cineform, but not DNX/Prores

what I meant:

use DNx at teh best quality in Windows machines
use ProRes at the best quality on Macintosh machines.

and why you need 8k in the first place?

I see there are more replies here after I got involved in another problem with a 4K project needing proxies. That was solved and exported.
Coming back to this 8K project, now I am having playback problems, that I don't remember having when I originally added clips, cut, transitioned etc. The problem was just in exporting. I may have made changes, such as choosing Nikon Camera Raw setting I found, smart caching, performance mode or other things that I thought would help the other problem. So currently it is taking over an hour to create proxies that I didn't even use on the creation before because it played OK then. Now, one of the times I tried playing it, it just closed after a couple of seconds, so something changed for the worse.

In answer to some questions this is an upgraded Dell computer, $2500 spent on the expectation to be able to do this, based on the recommendations of my friend who does similar nature videos, including 8K on a computer 3 years older. I went above some of his specifications or at least equalled. Video may often have to be zoomed so the higher the quality the less noticeable degradation.

When I have watched training videos I often get bogged down in procedures that are irrelevant to what I am doing. for example maybe 30 minutes on matching a dubbed voice to video. There are no humans, no dialog. I have several years of backlogged unused clips since I had to spend much of last year rebuilding a web site that took years to create, after GoDaddy destroyed it in a failed migration. In the last few weeks, I've gone from about 2500 to 3000 unused clips to finished projects using most, with only about 300 remaining. When I encounter a problem, I prefer to try to find a video addressing my concern rather than spending hours on what presently lacks relevance, in which time I could finish a dozen or more projects. I much appreciate when a solution is offered that solves some problem.

Now I am reading in the manual about proxies and optimizing, but had to back up and search to find where the options menu in the edit page viewer.

An now I see that while writing this, as Resolve was only creating proxies, it closed again.

Bummer, Rob. Appreciate you chronicling your journey. One thing to keep in mind with performance is that the specific codec of your 4K and 8K footage will have a huge bearing on performance. Add to that that if your GPU does not have a large amount of VRAM, Resolve will misbehave (or crash). I've also found that if smart caching is enabled, you will find that while background caching is ongoing, your timeline playback performance will suffer, depending on what is being cached. It's a deep rabbit hole. Sometimes proxies will help if the source codec won't playback easily (for example, if your source is HEVC 10-bit 4:2:2, all but the most recent machines will struggle just to playback the source, even before applying any effects or color grading). If the proxy media, however, requires more bandwidth than the disks can support, playback will suffer again.

You are not very helpful while we are trying to understand your problem.
1. Please tell us how much VRAM you have, so we can try to evaluate your chances for export.
8K is extremely challenging for most GPUs.
2. Do you really need to deliver 8K or are you using that resolution at the source only to have good quality when zooming or panning?

My humble laptop can handle 12K BRAW in an UHD timeline pretty well, even if not always smoothly. But an 8K timeline? I don’t think so, I didn’t even try.

The RTX 3060 has either 8 or 12GB VRAM, that's not enough to comfortably render an 8K timeline with effects/grades. It can even struggle with 4K timelines in some situations when using a lot of temporal effects.

I those 8K sources are in a GOP codec, it'll be too much for that GPU.

I those 8K sources are in a GOP codec, it'll be too much for that GPU.

He would be better to shoot in 4K oversampled H.265 than shooting 8K H.265 on the Z9. Quality is even better out of the camera and Resolve would handle it better as well. He hasn’t said why he is trying to grade in an 8K timeline and what he is trying to deliver but I suspect he doesn’t need 8K delivery. As you say, trying to understand the issues with such a dearth of information is very difficult. Also the queries and info are scattered across several threads.

Uli Plank, that was a good suggestion. I had a lot of external HDs connected. I disconnected and the 8K video played smoothly again. And then I went to export. Last failure was at 0%. this time it looked like it was going to finish as the fartherst before was 72% and it was at 89%. Then a message popped up, ' cannot access graphic card'. And it closed.

I am shooting 8K nature video, much of birds and cannot always be as close as desired, hence zooming in resolve for a larger image and thus retaining more detail.

if removing external drives is an improvement, it points to a problem with your power supply.
I understand perfectly fine why you want 8K sources, but that doesn’t mean you need a timeline in 8K. If you’d work in HD, you could even zoom in by a factor of 4.

I had about 8 external drives besides the 3 internal ones. I tried once more without the external drives. I wondered why the video played smoothly with green light, but not export. I closed all other programs and windows that were open. And also since the 2nd monitor had the full screen video playing, I set the video clean feed to none. I watched while the export proceeded and approached the highest before, 89%. It continued and completed! I could hardly believe.

I am shooting 8K nature video, much of birds and cannot always be as close as desired, hence zooming in resolve for a larger image and thus retaining more detail.

This makes sense but only if you are rendering to a lower resolution than 8K. If you zoom in on the 8K video you will lose quality rendering it at 8K as you are effectively upscaling.

Congratulations on your successful render in any case.

Having nothing else open and only one active display is always recommended if your GPU is close to it‘s limit.
You should be able to monitor it with GPU-Z (free).

I copied the project setting of the successfully rendered and exported 8K video to another I was having trouble with and it also succeeded. Also with no other windows open and not using the 2nd monitor for viewing full screen. Then I started a new project with those settings, with clips from the same time and place and settings. It was shorter, but failed at a point where I got a message that access to the graphics card was denied. I looked this up and found this page with possible solutions. https://www.technewstoday.com/fix-appli ... -hardware/

I went to Nvidia and downloaded a new driver and installed and did several of the other recommended things. exporting failed almost instantly. Updated Windows and tried again, instant failure. I don't know what's going on.

I've gone back over all of the replies and have some questions. If I export at DNxHD and then re-export at 265 (does this mean importing the export?) is quality lost?

When I looked at the filed tab of the delivery page for the suggestion about lowering the rendering speed to 10, I don't see any render speed menu.

On this last failed export project, I was having some unsteady playback, so I closed the 2nd monitor window and set the timeline to 4K. Was this useful, then exporting at 8K, and is quality affected.

Is it useful to set the monitor playback lower than the timeline? I had left at 8K.

I am just not understanding why the longer project, with more grading, and speed changes, played more smoothly and exported, while this has such problems.

Exporting in a mezzanine codec, like DNxHR or Cineform (or ProRes on the Mac) will produce no visible degradation if the final output is H.264/265. You can even use the better encoders in HandBrake.

Lowering the render speed is under Advanced.

If your export setting is at a higher resolution than the timeline, quality will suffer. But I still don’t get why you need 8K on export.

You can switch off monitoring completely while rendering.

Since you are working too close to the limits of your GPU, all kinds of unpredictable behaviour can happen.
If you need 8 K output by all means, get a GPU with 24 GB VRAM.

You will find the render speed on the Deliver page in the File tab.

thanks, I set render to 10 and then exported. It went fast and then I went to look at the video in media player. It looked like the 1st frame, then jumped to the end. I went back to the timeline and it looked like the video track was darker than I remembered. It played hesitantly, then Resolve closed.

I guess I thought that because my friend and I shoot the same type of subjects, even the same ones sometimes and he can export at 8K, and suggested I try, I thought I would since my computer was bought with this in mind, earlier in 2022, while his is 3 years older and I matched or exceeded his specs. But he said he doesn't grade or use transitions or speed changes and I have a watermark and a copyright track. His videos look great on youtube. Photographically we have similar equipment though he shoots Canon and I, Nikon. But Canon doesn't yet have a camera to match the full-frame Z9, unless they caught up.

I really don't know what is going on now. I had left the room on the previous render, so I don't know how long it was. I tried again, using the DNxHD while going back to maximum on the render speed. It finished in about 1 second and there is no video, just the title page at the very end.

The timeline tracks look darker than usual (like grayed out) but they are not disabled and in edit mode it plays, though jerkily and closed before.

You have marked a range. Press Option + X.
Do yourself a favour and cover some of the basic training, offered for free by BM.

So I exported in the DNxHD. Do I now reimport that to export at 265?

Use HandBrake for final encoding. It has the better encoder (x.264/265) and better control over size vs. quality.

Shoud this have been a problem, exporting at 3840x2160? It failed and Resolve closed.

So I made dozens of easier videos, and finally came back to this one, to see where I was. I tried exporting at 8K and watched and when it got to about 24%, I could hear the hard drive revving up. then it stopped and closed. It seemed too complicated to save and a lower resolution and then at a higher resolution. so I tried something else. I moved the clips from the 14T internal Seagate Ironwolf drive to the 2T solid state C: drive and relinked the clips there, and tried again. When it got to about 60%, I was a little worried as I heard the revving sound, but this time it died down and finished 100%. So this seems to be the solution, at least in this case.