Anim8or Community

I noticed that in scene mode selecting the camera view via the menu (View->other->camera01) is not the same as selecting the 'Camera' via Num-1. 'Camera' does not equal 'Camera01'. Transparency is handled differently between the two(?). 1348 doesn't allow you to select 'Camera', via the menu and 'Camera' seems to handle things properly.

And compared to 1345 (and earlier) and 1348, I'm getting different handling of textures in the display. One example, among several, is attached.

Is this because of the shader fix in 1348?

Otherwise 1348 looks good!

I’m working on an experimental multicore rendering script for movies. It splits an an8 scene timeline into segments and then renders the segments in concurrent instances of Anim8or.  The segments can then be rejoined using a program like VirtualDub FilterMod. An avs file is also generated for ingesting the video into programs that support Avisynth, if installed.

Depending on the amount of memory, number of cores and scene complexity, the script can substantially reduce movie rendering times.

If nobody has something similar and there’s an interest, I’ll post it when ready. Obviously I can't guarantee it will work on every variety of system.

Couldn't find a topic on this already but in the scene mode, selecting 'View'->'Camera' is not the same as selecting "View"->'Other'->'Camera01'. (I want to render multiple camera angles.)

1. 'Camera01' does not hide light sources, 'Camera' does,  and neither camera hides the other's camera.

2. More importantly, when rendering a movie using any numbered camera (eg 'Camera01', a "User" view), the first frame rendered seems to be that last frame viewed in the editor, NOT the first frame of selected range or of 'All' frames, almost as if the first rendered frame is from a buffer.

Seen this with Scanline and OpenGL. Using 1318. Non-User views seem to render first frame OK.

{Also, would vote for anti-aliasing for OpenGL rendering!}

In trying to see why your animation script crashes Anim8or for me (build 1318, Win 7 64 bit) I discovered, at least for me, the following:
1. Start a new project.
2. Go to Scene mode and create a Controller under World and assign a new Key in the time line.
3. Save and close the project.
4. Reopen the project.

Anim8or crashes either on opening the project or when selecting Scene mode. This is in part why your script fails for me.

Doesn't seem to matter if it's a boolean controler or float, first key frame or later.

I atttached an example an8 file.

Thank you for the response.

The pano width had no effect.

In fact a new, untouched project has the same problem: hangs on 2nd render. On two different machines. The Win 7 has opengl, the xp doesn't so used scanline. Tried differing codecs and file names, etc.

I'm using the version from the link on his page. Not a problem with Anim8or_1269.

A separate question (at least for me) is why the same project on a 32 bit machine consumes almost half as much memory as on a 64 bit machine. Searched the forum and haven't seen any authoritative statement on memory limitations

One would think 64 bit would have more available memory but not if it consumes twice as much. (My issue is that the extra memory consumption seems to interfere with rendering, that is, a large project may render on a 32 bit machine, but not on the 64 bit.)

I can imagine technical reason for 32/64 differences like byte alignment but it is disappointing if true.

Belated update.

My crashes now seem(?) related to going in and out of sleep and hibernation modes while using a solid state drive with TRIM enabled.

Files were being corrupted.

I've turned TRIM off for the last several weeks w/o problems with hopes this is the answer.

Steve

First, found this so-far-working work-around for me: Render something that doesn't crash (one that I removed the 'offending' texture from), close that an8 file, then open a crasher an8 within same Anim8or session. And tho I often get a message "dll initialization failed" before getting to the Video Compression selection, it seems to let me render OK. Works so far on both problem projects.

Second, looking at the crash report, seems "StackHash" is a Data Execution Prevention exception which can be turned off in Windows. So maybe one of my codecs is goofy. Will investigate. Not as good as first fix above since only works on one project.

Before finding these two above things, I wrote these answers to your questions:

Crashes with any codec since it crashes before I get to select one, and with any of the three renderers.

I tried at 720x1280 and it crashes the same -- before selecting a codec. (Intention was to render with opengl and use the big frame size for antialiasing.)

Other files (like the one that I removed the 'offending' texture from) renders ok at the big sizes.

If this just my problem, OK.

Did try XP mode and run as admin. Tried no multithread and set process affinity to one processor.

Here's the crash report:
Problem Event Name:   APPCRASH
  Application Name:   Anim8or_1264.exe
  Application Version:   0.9.8.2
  Application Timestamp:   5864366c
  Fault Module Name:   StackHash_bc7e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   10061d51
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   1033
  Additional Information 1:   bc7e
  Additional Information 2:   bc7ed343cd08601ea4a68f4f11772834
  Additional Information 3:   b10d
  Additional Information 4:   b10d69c7a4b8c862ade0ad8a0f22fe9f

Yikes!

Thanks.