Random runtime crashes

[chucky]

I should add here that , this did not work in all situations, in fact I would have a render start and using this technique and after an hour and a half the render would crash anyway.
I have abandoned this technique as it's better to crash right away than after waiting and hoping.
It's not just mov's and avi that cause this but also any sound file. Of course the scene needs to be fairly complex before the bug starts to occur, so you are normally safe if the scene is fairly simple.

[freddykrueger]

Hey,

I just posted above you about the audio and did not put two and two together to realize that you are having the same problem. I have a 6 core processor and I get that error any time I try to render anything with sound. I wanted to make a ten minute clip, and that was a BIG NO NO. Obviously smith micro told me I was running out of resources. I really doubt that. I can handle Maya rendering at very high levels and complexity and here I am stuck with a 2d program that can't hold a candle to photoshop yet I am running out of resources???

Either way, I hope they get this multi processor shit squared away quick because I am loosing precious time and money.

[chucky]

I feel for you FK ,it seems that none of these issues occur on small pieces/ hobby play, or generally mucking around.
It's only when the job becomes truly 'pro' that the headaches start.
Many layers and groups in conjunction with various media files on a powerful new machine, I think that sums up the general scenario of high probabilities of a render crash.
I know ASPRO is inexpensive, I think it's great, but not with the bugs, they totally undermine the positives and certainly disqualify the 'PRO' badge of honour.
It used to be great when this was Mike's little domain; he was in charge and could respond directly to us, that way there was less uncertainty about the product and it's development.

[freddykrueger]

The biggest hurdle, other than the sound is 3d complex scene that I am working on. Apparently 16gigs of ram and 6core processor just can't handle the complex move.

I can't remember any other program that was this horrible when it comes to bugs. I might have to downgrade to 6 or 6.5 I believe, just to get stuff done by the deadline.

[adam_r]

I am using AS7PRO and am running 64bit Windows 7 with a 6core processor and 8GB RAM. My program crashes all the time, but I may have worked out a cause and am hoping some tech experts might be able to help and this may relate to OP's problem.

My computer should be able to use up to 8GB RAM while I am using it, and for everything besides AS it runs fine. What I have noticed though, AS only crashes if it processes to 1,130,000 K, even though there are still a tonne of resources left available.

The crash only occurs at this number.

So, I presume the program, because of the way it was built (i.e. being 32bit) was not built to take advantage of large processors or RAM with 64bit.

My question is; is there a file(s) in the program I can edit so AS uses more RAM?

...and mine only occurs in "pro" projects, I assume becuase they use more RAM.

[Rainer]

My first post - or I think I might have been a member years ago. Anyway, Adam, if you are still there, and everyone on having render problems on large projects, try downloading and running Large Address Aware from http://forums.techpowerup.com/showthread.php?t=112556 on AnimeStudioPro.exe. See that site thread for further details and why this might help.

[adam_r]

My first post - or I think I might have been a member years ago. Anyway, Adam, if you are still there, and everyone on having render problems on large projects, try downloading and running Large Address Aware from http://forums.techpowerup.com/showthread.php?t=112556 on AnimeStudioPro.exe. See that site thread for further details and why this might help.

This has so far 100% completely fixed the problem. I have done some more observations, and it seems AS (on my system) needs to get to approximately 2,750,000K before it begins the rendering and only peaked at about 2,813,000K (using some codecs peaked skightly higher, but never above 3GB) during the process. This occured for 18000, 1800 and 120 frames. I haven't tried higher, but I will test later. 18000 (10 mins 30FPS) is as high as I need anyway for one block of video.

Thanks a heap Rainer!!

[Yosemite Sam]

I know this is an older thread, but I just have to say to anyone getting crashes during rendering, or the "runtime error", the above mentioned software really works.

I had large sections of animation that had many, many particles, and AS would crash nonstop. Same with multiple audio files. But now ASP runs like a champ when rendering. This software simple allows ASP (a 32 bit program) to have access to up to 4 gigs of Ram when rendering -- and it really makes a difference. Specifically when you have a 64 bit system with a lot of Ram.

[chucky]

Hi Yosemite.
I have not seen this issue for a long long time, as far as I know it was cured several releases ago.

[Yosemite Sam]

Maybe they did, but I started getting EXACTLY what you described in your op. And there was no rhyme or reason to it. I'm just happy that I can now render large files with tons of extras, and never have to worry about crashing. I render a 1000 frames at a time now (.mov, animation/none) and it's awesome.

I'm using the latest release with all the updates/patches, and a pretty powerful system, so I don't know why it was happening to me, but I'm just glad the Large Address Aware software solved my problem.