Daz Studio Can't Render UHD 4K (3840x2160)?

Gator

I have issues rendering a movie in 4K - it's always the same, the image is offset vertically about a 1/3 way through from the bottom.  The bottom part is all or strong with blue channel.  The top looks normal.  Then about 1/4 of the way through the movie, it shifts and corrects itself and looks OK.

When I use all the same settings and only drop the resolution down to 2560x1440, then it renders perfectly fine.

 

This is with multiple versions, currently running 4.23.0.1 and 4.22.016.  I also experimented a while back around January, with whatever current release at the time.

Gordig

Are you rendering directly to a video format, or rendering to an image sequence and then stitching the frames together? The latter option is strongly recommended, for multiple reasons.

Gator

Yes, in my render settings, I have set Render Type to Movie and then I would save to Uncompressed Frames.  

I'll have to try Image Series.

mikael-aronsson

It should of course work to render to video also, image sequences use lots of disk space but makes it easier to pause rendering and continue later and so on, for postwork it can help to render to images also, but that is not your problem.

Try with an image sequence and see if it looks ok, in that case there is something wonky with the video output (most video editors can import an image sequence and turn it into a video).

Try to render a video but just render a few frames and see if the problem is the same.

Check the log for any error messages

It sounds like a bug so a bug report might help also.

I guess it would not be memory related as the problem is in the beginning and fixes itself later, does it always fix itself on the same frame ? or is it different every time ?

It could be codec related, some codecs behave weird and need special settings to work well, not sure what codec it is using, I don't use iRAY.

Dark45

Gator said:

Yes, in my render settings, I have set Render Type to Movie and then I would save to Uncompressed Frames.  

I'll have to try Image Series.

Well if the image series works then you will be doing it the much better way. Think about a crash on frame 400 after 8 hours of rendering, image sequence will save your life.

Richard Haseltine

mikael-aronsson said:

It should of course work to render to video also, image sequences use lots of disk space but makes it easier to pause rendering and continue later and so on, for postwork it can help to render to images also, but that is not your problem.

The render goes to image sequencs anyway, but if you choose to output to a movie file they are turned into a video and deleted at the end. If anything rendering an image sequence should use a bit less disc space at peak.

Try with an image sequence and see if it looks ok, in that case there is something wonky with the video output (most video editors can import an image sequence and turn it into a video).

Try to render a video but just render a few frames and see if the problem is the same.

Check the log for any error messages

It sounds like a bug so a bug report might help also.

I guess it would not be memory related as the problem is in the beginning and fixes itself later, does it always fix itself on the same frame ? or is it different every time ?

It could be codec related, some codecs behave weird and need special settings to work well, not sure what codec it is using, I don't use iRAY.