Page 1 of 1

Put it in the RAM

Posted: Tue Aug 06, 2013 3:33 am
by zeitmeister
Hey,
I was thinking what would happen if Indigo were able to export the scene directly to the machine's RAM?
Optional, for sure?
Export would be a lot faster, and could nearly reach realtime-speed.
For efficiancy, Indigo could check and export only new meshes.

What do you think about that?

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 3:55 am
by Zom-B
You refer to the exporter writing directly into RAM not Indigo itself, right?!

I really like the idea, shouldn't cost any extra RAM at all and give some faster previews, where 10sec export + startup time is a lot if you do previews all the time!

So here is my +1 :)

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 3:59 am
by Voytech
Seems like a good idea for wip/preview renders. On a final render the extra 10s is not an issue when you're waiting a few hours anyway.

So yes, +1

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 4:24 am
by zeitmeister
Right.
As I said, in junction with the option only to export CHANGED meshes or textures.
Should be lightning-fast.

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 4:58 am
by Oscar J
Hell yes! +1

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 5:11 am
by OnoSendai
Using the c4d plugin already doesn't write to disk and uses RAM only

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 5:29 am
by zeitmeister
Really? But Export is as slow as exporting to the Standalone...

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 6:20 am
by Zom-B
OnoSendai wrote:Using the c4d plugin already doesn't write to disk and uses RAM only
For internal rendering yes... I usually still use the external version, since I can tweak parameters on the fly and take them over to C4D if they fit...

Re: Put it in the RAM

Posted: Tue Aug 06, 2013 10:30 am
by Oscar J
OnoSendai wrote:Using the c4d plugin already doesn't write to disk and uses RAM only
Could we still have it for the other exporters? :roll:

Re: Put it in the RAM

Posted: Mon Aug 19, 2013 6:55 am
by Mor4us
Zom-B wrote:
OnoSendai wrote:Using the c4d plugin already doesn't write to disk and uses RAM only
For internal rendering yes... I usually still use the external version, since I can tweak parameters on the fly and take them over to C4D if they fit...
Thats what i requested the Realtime Preview for Cindigo for ;)
That would make your exporting redundant, especially because there's a lot of features not yet supported in the indigo gui but in the exporters