Quote - Thanks everyone!

Cool. I have a StarBird Command Base I picked up for a tenner in a charity shop last year.

Never seen that one before those, but the ship looks vaguely familar.
Maybe because it's rather Y-wing like.
Though a great bargain after looking at some of the prices out there!

Would also certainly offer to host this if anyone makes it, if thats required.

The space ship cost £10 - the command base was another tenner. The base is mostly cardboard, and I am surprised that it's not too battered. I knew of the ship, but the base was unknown to me, so I bought both.

Quote - HD?

do you have the StarBird?

if you do... can I ask a favour? I wanna model it.. but I never had one.. can you take reference pics?

Hi, I'll have to get it out from my storage unit, but sure. It needs photographing anyway.

Cool. I have a StarBird Command Base I picked up for a tenner in a charity shop last year. I should do something simialr.

This:
http://www.bugeyedmonster.com/toys/starbird/starbird/blowup/commandbase.jpg

In theory (note the word “theory”), it should be possible to make a rig in Poser that creates the anaglyph optically at the time of rendering. You’d need some very specific objects - effectively an anaglyph converted fro the camera you were using. You’d need to create a beamsplitter (which is a half-silvered glass mirror) to allow only 50% of the light through one side and combine it in such a way that the camerra sees the ready-made anaglyph.

Position this to the donny camera and parent it properly, and you’ll have a rig that can be moved, animated etc. without any need for Python intervention. It would only need one render cycle, and no need for specific software to combine the two images in post.

That’s the theory.

I tried this with my system. It’s not great, and I think that the camera is moving too quickly and sweeping too much which kind of kills the 3D for me.

http://www.youtube.com/watch?v=Nxc5ahkdj_U

I don’t have Windows running on the machine I’m using right now, so I faffed around in Final Cut Express and did some channel mixing. This is also a preview quality render. I may try it using ray tracing. That’s for another day.

Hi, all!

I’ve uploaded a newer version of the scripts. The folder you download replaces the folder you downloaded before. This version allows you to control the distance bertween cameras. There is a control on the Convergence Plane for this. Set this to the desired number and render.

Note that if you set the number too big, the scene may not work properly. It’s up to you to decide the best settings.

If you set the value and want to see the views from the left/right cameras, click on the Set Cameras button in the Python Scripts Window (or the Scripts Menu) first.

Quote - The script for image generation creates left and right images for parallel cameras. Compare to Hairy python script, this script offers a choice of the stereo base (distance between cameras) but the setting of the stereo window should be done in Stereo Photo Maker. In Hairy script, the stereo window is set by the convergence of cameras (not a bad approach).

The convergence issue has been something I’ve found out about from using my stereoscopic camera. On that (it’s a Fuji) you can adjust what it refers to as “parallax” - or stereo base. The problme with doing this post phot taking is that the image starts to be cropped width-wise as image data that won’t be included in the 3D image gets lost. I find this if I import my MPOs into conversion software and make the same adjustments there.

I have seen a lot of images out there which are very hard to look at - you really have to force your eyes to “see” the 3D, and most of the time it appears that this has happened because the stereo base has been adjusted so much that it starts to be meaningless to your biology (ie the distance between your eyes). I am a firm believer that there should be no eye strain at all, and that when you drop the red/blue filters over your eyes, the scene should “pop” without any extra work needed.

This has been my approach - keep the left/right cameras within a comfortable distance for the viewer (and for this, I mean the distance should be fairly close to the physical distance between your eyes), and let them do what your eyes do naturally to generate a 3D image in your brain - that is to swivel inwards to a point (usually the point of focus). Your brain then gets the two pictures and snaps it into some kind of sense.

That’s the methodology behind my scripts - trying to keep it as comfortable as possible for the viewer.

Quote - PS.

I wonder if you could write a script that simply placed the cameras.

When activate it would Asked Left or Right Camera, and then proceded to do the rest of it normally it would be a big help.

I.e I set up my scene, I hit Stereo Movie.

I select Setup, and then Render just as I do with a still frame.

Then a dialog comes up and asks me, Left or Right Camera.  

I select Left Camera, and it goes to the normal poser "Make Movie dialog, lets me make my selections, and continue from there normally that would be great help.

When I hit "Make Movie it does it only for the Left Camera, then when I repeat the process and select Right Camera my setting will already be there, and do it again.

This would let the user make all the choices about how to render the image, check the first animation video before going on with the second one.

But it would automate setting up the cameras, so the two images would work together corectly.

Just an idea, like I said I have no idea how this works or if this is a practical idea.

Mike

 

Hi, I don't know how or if Python offers that level of control for rendering movies in Poser. I suspect that it may not do that. I have not seen a script that tajes options from you and then passes them back into the app's regular interface in the way you describe. It may be that all I can do is rig up the key frames and let you do the left/right rendering manually. I'll have to do some research on this subject. Thanks for the info on the software.

Oh, added the Script Menu option to my website. Next thing to think about is movies. I am not sure that I can auto render movies in the same way that I can do single frames using Python. What I think I can do is copy keyframe settings (focus depth, etc) from the Dolly camera to the left/right cameras. That will at least make it easy to render a left and right movie. Question - what do you use to make anaglyph movies once you do have the left & right movies?

Quote - Doing easy things the hard way!!!

I did what Adom suggested and it was even simpler then he said.

I removed all my other files, copied the StereoImages folder, that I had the script buttons in, to the Scriptsmenu folder and what do you know! 

An easy way to access Hairy's script!

I don't have a button on the Palette, but all I have to do it click on scripts at the top of the screen and the Stereo Images folder is right there.

When I click on it all or the options are available, Setup, Render, Reset, etc.

I've tried it several time and it works fine, I don't even have to hit Alt S or whatever.

Thanks to everyone for all the help!!!

Two weeks ago I asked if it was possible to create stereo images in Poser and now I'm doing it. Sounds like a TV commercial!

I now have 7 pairs of Anaglyph Glasses, and am driving everyone crazy saying "Hey, you gotta come and look at this". LOL

Now I'll get on with perfecting my still image technique, and then it's on to my real goal, creating a 3D Lucy movie.  I only started doing the video thing less then a year ago, and now I'm going to do it in 3D!

I'll have to send 3D glasses to all of the friends on my Lucy email list so they can watch it.  But the glasses are really cheap, I just bought 5 pairs for $10 shipping included, I have 4 different kinds, I'm going to decide which I like best.

Thanks again for the help.

Mike

Glad you got it working. Have fun and post your results!

Quote - Hi

Thanks I'll try and figure out how to do that.

I'm using Wordpad and I'm copying the insert directly from the article.

I'll look into the sexless quotes thing.

Mike

Wordpad will probably add in control characters (colour, font styles, etc) that may confuse the Python interpreter. If it can, tell it to save the file as plain text (not Rich Text). Or use NotePad.

Quote - Here is the message that I get...

D:Poser 8RuntimePythonPoserScriptsposerStartup.py:14: DeprecationWarning: Non-ASCII character 'x94' in file D:Poser

8RuntimePythonPoserScriptsmainButtons.py on line 11, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
poser.ExecFile(mainButtonsPath)

File "D:Poser 8RuntimePythonPoserScriptsmainButtons.py", line 11
poser.DefineScriptButton(9, ”:Runtime:Python:PoserScripts:CustomScripts:customButtons.py”, “Custom Scripts”)
^
SyntaxError: invalid syntax

 

Here is the complete mainButtons file...

 

import poser

poser.DefineScriptButton(1, ":Runtime:Python:poserScripts:PhilC:Wardrobe Wizard P8:Wardrobe Wizard Menu.py", "Wardrobe Wizard")
poser.DefineScriptButton(2, ":Runtime:Python:poserScripts:GeomMods:geomModButtons.py", "Geom Mods")
poser.DefineScriptButton(3, ":Runtime:Python:poserScripts:Utility:utilityButtons.py", "Utility Funcs")
poser.DefineScriptButton(4, ":Runtime:Python:poserScripts:SampleCallbacks:callbackButtons.py", "Sample Callbacks")
poser.DefineScriptButton(5, ":Runtime:Python:poserScripts:RenderControl:renderButtons.py", "Render / IO")
poser.DefineScriptButton(6, ":Runtime:Python:poserScripts:MaterialMods:materialModButtons.py", "Material Mods")
poser.DefineScriptButton(7, ":Runtime:Python:poserScripts:PrintInfo:printInfoButtons.py", "Print Info")
poser.DefineScriptButton(8, ":Runtime:Python:poserScripts:CreateProps:propButtons.py", "Prop Samples")
poser.DefineScriptButton(9, ”:Runtime:Python:PoserScripts:CustomScripts:customButtons.py”, “Custom Scripts”)
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

 

If this makes sense to you guys I'm open to suggestions.

Mike

I’ve not seen these errors, and I’ll put my hands up and say that I’m not a Python expert - I’m usually ghrubbing around with JavaScript and the like. However, it looks like your quotation marks are wrong. Look at these two lines from your script:

Quote - poser.DefineScriptButton(9, ”:Runtime:Python:PoserScripts:CustomScripts:customButtons.py”, “Custom Scripts”)
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

In your edited version for button 9, the quotes are curly - “” - often called typographer’s quotes. When writing code, you don’t use these. It’s likely that your editor put put these in automatically. You need to switch this feature off - something you’ll need to find out how to do for your self. It will probably be in preferences.

You need to be using what are known as sexless quotes - "" - so your line should look like this:

Quote - poser.DefineScriptButton(9, ":Runtime:Python:PoserScripts:CustomScripts:customButtons.py", "Custom Scripts")
poser.DefineScriptButton(10, ":Runtime:Python:PoserScripts:clearButtons.py", "Clear Buttons")

Python is also sensitive to tabs and indentations - they have special meanings to the interpreter, so ensure that you don’t have any leading spaces or tabs in your buttons files.

Also pay attention to the software you are using for editing the Python scripts. Use a plain text editor - I think NotePad should do the job on Windows. Always save the file as a plain text file, not as Rich Text. Rich Text embeds layout and colour instructions in the file which may cause the Python interpreter to fall over too.

EDIT: Just tried your added line on a buttons file here, and I got the same error. Using sexless quotes fixed the problem.

When Apple moved from PPC Chips (G3, G4, G5) to Intel, it meant that no code built for older Macs would run on the newer Intel architecture. Developers were encouraged to create what was called universal binaries - applications would contain code for both architectures. Apps that were PPC only would be run through a translation layer known as Rosetta - which converted PPC code to Intel code. Lion does not support Rosetta, so PPC only apps won't work. The expectation now is that there is either an Intel native code version of the software, or that it's been abandoned.

Quote - I’ve no way of testing this on Windows, so I’m stabbing in the dark a bit here.

Hope you can get it working on older versions, sadly no go on P6 PC, as I'd like to try using your excellent idea with a tri-layered prop I've made which fakes DOF.

The best I can do is provide an earlier prop which was part of my development cycle. It started in the version of Poser prior to Poser Pro 2010, so it may do the job. It gives you three cameras and the convergence prop. If this works, then you’ve atleast got a starting point to play with.

http://www.worldofpaul.com/anaglyph/olderversion.html

Download, put it in your Runtime/Library/Props folder. Hopefully this will work, but a lot of the Python magic won’t be there - you’ll need to copy camera settings manually. Sorry, but this is about as far as I can go for older versions. I’m running Mac OSX Lion now, and that’s a bit problematic for Poser pro 2010. I doubt it will run P6 as that will be PPC code, which Lion does  not support.

You will need to edit the python file that makes the buttons to point to my buttons.py file if you want the Python Scripts button to stay permanent.