Daz Studio 4.7 Rendering movies memory access violation
Giichil
Posts: 36
I have Timeline for creating basic poses, and I'm awaiting smoothing out the movie making process until I get Animate2. Why even go buy crazy if I can't get the thing to work?
Daz movie making has had extremely long rendering times. I'm talking (just for seconds of animation) 7 hours of sleep and 6 hours of work before I get home, excited that the thing has finally finished only to find that it failed all that time was wasted.
So with the promise of faster render times, I bought Movie Maker DS 4.6 edition, said to work with Daz 4.7
(If any mods need to check purchase history, it's on another account. But that account is associated with a name I don't want public so I post with this one. I can message you from that other account to confirm.)
Anyway, render times were indeed faster but the same problem persists. I am unable to save the movie. It happened once with a 5 second animation. Never again would it let me render a movie. So I narrowed it down to 1 second to discover the problem faster. None of the other movie compression options work. They just flat out tell me I can't. So the only two are Microsoft movie options.
Here is from testing only 7 seconds. I can't render any animations anymore after the first one I made.
Every single time, I get this:
Microsoft RLE (The Compression type you selected could not be initialized. Please select another compression type.)
Error exporting video file: Operation failed
Microsoft Video 1 (C Exception: Memory Access Violation - Attempted to write memory at address 0x253bd000)
Error exporting video file: Operation failed
(C exception: Memory Access Violation - Attempted to write memory at address 0x1aecd000)
Error exporting video file: Operation failed
Intel IYUV Codec listed twice (C Exception: Memory Access Violation - Attempted to write memory at address 0x198ffd000)
Error exporting video file: Operation failed
Fraps Video Decompressor (The Compression type you selected could not be initialized. Please select another compression type.)
Bandi MJPEG Video Decoder (The Compression type you selected could not be initialized. Please select another compression type.) Error exporting video file: Operation failed
Bandi MPEG-1 Video Decoder (The Compression type you selected could not be initialized. Please select another compression type.) Error exporting video file: Operation failed
Full Frames Uncompressed (C Exception: Memory Access Violation - Attempted to write memory at address 0x0ab4d000)
Error exporting video file: Operation failed
I have two 8GB sticks of RAM, 471GB free on my 1TB drive. I don't understand these memory access violations.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Most people who do animations, render a an image sequence, and then put it together in post work as a movie format.
If a render fails, it is a simple matter to start from that failure, and continue until done. That way nothing is lost, and no time is wasted.
Yes, but Daz has Timeline, Animate 2 (what I'm buying next) and Movie Maker DS 4.6 edition (that I recently bought on the other account).
It has the option under render setting to render movie instead of render still image.
I don't even think I'd be able to take just still image renders of an attempt to move (or speak when I get animate2 and use with Lip Sync) and then just add the pictures together in something like Windows Movie Maker. The motion or speaking would be off.
That's the whole reason I just want to animate movies under the render movie option in Daz.
An image sequence will give exactly the same result (with the addition of options like having an alpha channel and adding sound) as rendering to a movie file - in fact that's what DS does, it renders an image sequence and then stitches it together at the end as a separate step (which means that if DS crashes the image sequence should still be in the temp folder until you restart).
Oh, indeed? Template.. templates.. what directory is that usually in?
You can find the location of the Temp folder in Edit>Preferences (Apply menu>Preferences, I think, for Macs). The frames, in png format, are in the render subfolder there.
Interesting. So I just tried making a movie in Daz Studio 4.6. Without Movie Maker 4.6 edition, because I can't run 4.6 on DAZ 4.6??
I checked the temp folder.
C:\Users\Owner\AppData\Roaming\DAZ 3D\Studio4\temp\render
It appears that out of 778, uh frames? Keyframes? Out of 778 images, only 710 through 778 are there.
When Daz 4.6 rendered the movie and actually finished, the movie was almost completely black.
And then I'm assuming the 710 through 778 are the ones that appear with the character moving.
The character rendered under Daz 4.6 was black and textureless over black background.
They were not originally meant to look like that. It is a bug.
So, even though I bought Movie Maker 4.6 Edition, it's not available under the plugins for Daz 4.6
(once again, I'll confirm with the account I purchased it with for any mod requesting me to do so)
Daz 4.6 isn't an option to render movies then.
I can't piece together the images and shorten them to try even a semblance of character motion.
How is this supposed to work whenever I buy Animate2 and use with LipSync?
Memory exception errors for all movie render options in Daz 4.7, no Movie Maker 4.6 in Daz 4.6
This is getting pretty frustrating.
I don't have Movie Maker, but if it's a plug-in does it need a serial number, and if it does did you enter it (in Help>About Installed plug-ins) and restart DAZ Studio?
I don't think Movie Maker 4.6 had a serial number. This is an old topic, but if someone responds on it I probably won't have to make a new one. I'm wondering what to do with the perspective view camera. See, I can render 26 seconds before failure as long as I don't use Movie Maker's intended window to render. Which is strange, but I can render animations or images faster if I have the Movie Maker "prop" simply existing with eye-closed to invisible in the background and completely avoid the useless (to me) Movie Maker tab.
Anyway, my problem with the primitive camera is that after I save a .duf scene file and close, then open Daz later and open that .duf file, the primitive camera is reset. It won't stay in the original position. I can't do proper seamless timeline animation by simply combining 26 second films together if I don't have the camera stay in the exact same position it used to be. On earlier versions of Daz, the camera was in the Scene tab and I could adjust it the same as any other object. But relying on my eyes and memory? That only leads to choppy film.
I only wish I could adjust it with pre-written parameter translations and rotations. Maybe there's a way, right?
Perhaps some tab I never opened?
I don't think Movie Maker 4.6 had a serial number. This is an old topic, but if someone responds on it I probably won't have to make a new one. I'm wondering what to do with the perspective view camera. See, I can render 26 seconds before failure as long as I don't use Movie Maker's intended window to render. Which is strange, but I can render animations or images faster if I have the Movie Maker "prop" simply existing with eye-closed to invisible in the background and completely avoid the useless (to me) Movie Maker tab.
Anyway, my problem with the primitive camera is that after I save a .duf scene file and close, then open Daz later and open that .duf file, the primitive camera is reset. It won't stay in the original position. I can't do proper seamless timeline animation by simply combining 26 second films together if I don't have the camera stay in the exact same position it used to be. On earlier versions of Daz, the camera was in the Scene tab and I could adjust it the same as any other object. But relying on my eyes and memory? That only leads to choppy film.
I only wish I could adjust it with pre-written parameter translations and rotations. Maybe there's a way, right?
Perhaps some tab I never opened?
Create a new camera with the option to use current transforms -- the Perspective view is not a real camera and doesn't get saved with the scene the way a real camera does. Create the new camera first thing -- you can even have a default amera created utomatically when you start a new scene (Edit > Preferences > Scene).
I bought Movie Maker just now, I get the same Errors as Giichil. There seems to be no solution, right? So Movie Maker doesn't work well, but is still sold?
Not sure if this will help or not... Not 100% familiar with the plugin.
Sounds like it needs to use compatibility mode for windows 7. Since it is all the codexes, which windows now intercepts and uses hardware on the CPU to process for audio/video/zipping. In windows 7, those things were not available as intercepted services. The memory it thinks it is using is virtual, and it seems to be trying to physically write where windows tells it that it is actually located. DMA is no longer direct, unless the program is 64-bit. It is virtual values, recycled per program... they all think they are writing to the same 0-4GB of ram, though some are in front, some are in the upper range that normal 32-bit programs can't actually write to, due to being 64-bit values. Forcing windows-7 compatibility, or lower, will make that program ONLY operate in physical RAM-space, and not use the chips intercepted code acceleration for those audio/video/zipping functions. (Thus it will run slower too, as it is forced to use standard code not hardware.)
Unless you have a bum codex-pack from FFDshow, which replaces the real codex with free garbage encoders and decoders. They are outdated and unsupported by just about everything now. https://en.wikipedia.org/wiki/Ffdshow
RAW is what you want to save all video as, which is just a "timed case" for the individual images, a "pack" or "container". Use an external encoder to compress that to whatever you want later.
VLC will come with FFDshow, not the real H.264-codex you need for standard video. "Apple quicktime" is the ONLY location you can get the real H.264-codex, buy installing apple quicktime player. (H.264 is the standard for MP4, AVI, MPG, QT, DIVX, XVID, etc... any other is junk. Those are just more containers, all the same exact thing underneath the hood, if you want compatability and no crashing.)
https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC
@JD_Mortal:
Thank you very much for your quick help! What I'm just wondering about is if I'm the only one with these problems. My system is quite "normal" I think; Win7 is updated, DS 4.9 works well with NVIDIA Iray and so on, so I think there is not too much junk on my computer or too many tricky settings. I tried to install my old DS 4.6 - the same errors. So I'm getting more and more to the point that I guess Movie Maker is not thoroughly tested on different systems as it should be.
In Poser, everything works fine.
I don't disagree with that. :P
But Daz3D's failure seems to be tied to that plugin, with relation to the codex's.
Do you have the 32 or 64 bit versions of daz and movie maker? I see there is individual installs for both.
(I wanted this, just for the panoramic 3D feature.)
Also note: Daz3D has a few bugs related to memory-access violations, which are unresolved and random. This might help them locate one of them, as it is seemingly persistent. Along the rendering pipeline.