Uhm... this is sort of aetherial subject... more than speaking of avi materials, this is another workaround. I'll try to be as clear as possible, but the idea itself is cloudy, I hope I'll be able to explain it right.
So assume you want to add some kind of monitor to your a8r scene, and that you want it to display the frames of a movie. You would use avi materials if you could, otherwise you could do the trick using several materials and single frames from the movie.
In the attached zip there is the project and the pictures used to make the small gif animation attached separately.
The upper animation is made by sliding the "tape" in scene mode, the lower one is made with a morph target and a controller (by the way, once you set a controller for a morph target anim8or won't allow you editing it any more, at least it does so for me - clicking on its track doesn't pop up the edit key dialog).
So this approach has several negative sides.
- needs separate frames;
- needs a material for each frame;
- the tape that exceeds the viewport must be hidden by something else.
Variations of this technique can be made using an extruded regular polygon and sticking the frames to its faces, finally animating it by turning it about its center. Another variation could be to use single objects (simple planes) to store each image and then adding them all to a figure where, using one bone for each image, you can make each image to stand in front of all the others during each different frame.
The last approach is the most expensive as number of different things you need to set up in the project, but if you can automate a bit the process of manually editing a .an8 project file, this all becomes really fast. The most important advantage of using the last variation is that you don't need to hide the rest of the tape (the frames hide each other). In other words you can fit the animation in a flat plasma monitor inside of your scene
Here I come to the most interesting issue for me. The blue boxes sideways in the animation should hide the rest of the tape.
What if I could tell it that everything falling inside of that blue boxes must not be displayed/rendered?
It would need something like a material attribute tagging it as "empty space", "transparentizer" or whatever, and its result would be to ignore everything that falls inside of it. I think that this check could be done using the same "odd/even" test used when raster-filling an irregular poligon.
More or less in the same way, it would be a very useful animation feature to be able to set a material as an object exchanger.
Once again this is not so easy to explain, but I'll try.
Take the disc cutter I put in the WIP forum as example, and imagine the same work made in this way:
- object1: one object representing the white block.
- object2: one object (a figure or a morphed object) representing the hollow block and the disc.
- object3: one object, eventually a simple plane, set with a material tagged "changer" or whatever.
I put object1 in the scene and I put object3 between object1 and the camera.
I set a property of object3 telling it that object1 must become object2.
Now, when the renderer scans the lines of the viewport, it can tell if it is intersecting object3. If it does, it simply replaces object01 with object02 and renders that pixel as if the objects were actually exchanged.
I thought that this could lead to several problems. First of all, if object2 is not truly into the scene, it would share and use the tracks of object1. Fine until you don't want to use two figures and different animations.
I went to imagine this variation. Both object1 and object2 are put in the scene, and in the same spot of the scene. Object3 has two different special materials, one tagged A and the other tagged B. When the scanline intersect material A it displays only object1 and visaversa, crossing B only object2 will be visible. This is sort of adding a special kind of object to the whole system, as you'd need to tie object1 to material A *inside of object3 properties*.
I hope I've made it clear enough even for those who are not so accustomed to anim8or finesses and coding in general. I could make it all more transparent with some diagrams if needed.
