Flame 9.5

[jonhollis_vb]

Hi all, i have just had loaded flame 9.5, anyone got any feedback about it yet…. i havent qquite fathomed out the layer paint yet but everything else is looking good in batch. i will keep you posted on this thread if i come up with any problems.
the first one was with AIT data archives, discreet people had to come with a handwritten patch to get it to load the images from the AIT archive. otherwise all is good.

jon hollis

[Anonymous]

9.5 .. lucky you! 😆

[jonhollis_vb]

yes i guess so, i gathered from the lack of replies that maybe not many people were running it yet. i still have good things to report, no major issues as yet. a good release (i think, dont hold me to that)….

[Anonymous]

less issues the better.. still on 8.5 and no history 😥

Any new features your using alot?

[jonhollis_vb]

i stopped using history on 9.2, because it slowed everything up so much. so i must try it again. paint in batch is great, importing quicktimes (when it works) is good. everything seems faster ( i had to upgrade the ram). do you have the master keyer in version 8, thats really good.

[John Montgomery]

jonhollis wrote:

i stopped using history on 9.2, because it slowed everything up so much. so i must try it again. paint in batch is great, importing quicktimes (when it works) is good. everything seems faster ( i had to upgrade the ram). do you have the master keyer in version 8, thats really good.

The app is much more stable with 64 bits and more RAM, especially in batch.

And I’ll say that history stability and robustness should be much improved. I spent a good deal of time helping them test this (since I had problems in the previous release). I know that there were many things that were found and fixed which should help things out.

As a first step in trying history again, how about trying to use history with the “Keep None” option…this will track your setups and what you did to a clip, but not keep any of the source clips or intermediate clips which you used. You’ll still need to keep track of clips manually, but it is a good first step in getting used to history.

[paul_round]

Hey Jon,
I use the master keyer all the time, it gives as good as key as keylight

Paul
Peerless

[jonhollis_vb]

Hi john

thanks for that i will try using history again. i do have a bug with the video not working (when launching flame, then having to go into input clip before it will lock the vbob) and then it works fine.

i can get the motion estimation timewarp to work very well, but it is early days yet, any tips for good results.

and Hi paul, long time no see, yes i like the master keyer better than all the others, nice asnd simple and great results. i like the easy solutions!!

jh

[Anonymous]

Yeah I have the master keyer… very nice.. simple… and has speeded up some work.. but Keylight still rocks… most of the car stuff I’m doing with hair all over the place is “click” done 😆 very happy… allows more play time for making shots work….

Really want Furnace though…

[sidewalksurfing]

hey guys

just loaded up flame951 here in nyc. right off the bat – thank god for auto detect file extensions in ‘Import Image’ module – saves SOOOO much wasted time / keystrokes.
Also the import PSD file format and being able to keep individual layers RULES. ( i know it’s been around since v9, but we upgraded straight from 8.5.4) I was a little disappointed to learn i would need to purchase more RAM for both machines. We are running with 2.5 gigs and have experienced relentless crashing in batch due to insufficient ram (according to discreet…) How much is everyone loading up their boxes with? 3gigs – more? what is that buying me if i do more than 3 gigs? anything at all? also – now we have to upgrade ALL of the sparks, which is not a problem for sapphire but we were also using v1 of furnace which doesnt exist as a 64bit spark. that and the increased RAM means a bit more than we bargained for $$$$ – wise.

so, yeah it’s good to have a optical flow / motion estimation TW native to flame.Of course, discreet has to bury it in batch or in the editing subModule of TW on the desktop. why can’t it just be an additional setting with the ‘Progressive / interlaced’ buttons in desktop TW? It also seems to lack additional fuctionality that KRONOS has, but it seems pretty good so far and i guess judging by the ‘technology demo’ at NAB ’05, those things will arrive.

i have yet to dive into batch paint, however it seems to only be something that can feed a node – not have a node fed into it. huh. whatever. finally, i’ll never understand why discreet continues to change the interface in odd little ways everytime there is a major upgrade. who asks for this stuff? rearranging buttons in the play module AGAIN. rearranging the export queue buttons and placement? what a drag. Who actually requeseted that the system exit button be changed to ‘FLAME EXIT’ i would rather have that time spent on incorporating a true field based TW. or new particle system.

ok, to end on a high note, i will say that also having TEXT module in batch is really great. I’m sure there are a few other cool things… just haven’t got to them yet…

tim
suspect nyc

[jonhollis_vb]

Hi

interesting you should mention upgrading ram and batch crashing before. i had laods of ram before and had to buy more as we needed 3 gigs. batch always crashed all the time before. we installed more ram, but the tech guy said i had had enough ram but it was in the slots in the wrong order. apparently this would cause crashing. so now i have loads more ram (more than i wanted) and it is all in the right slots and batch doesnt crash anymore. SOunds like i could have saved a lot of crashes and time wasted if someone had got it right in the first place……

anyway 9.5.1 going very well, even the paint ‘keep one’ bug has been fixed.

jh

[patdawg]

jonhollis wrote:

Hi

SOunds like i could have saved a lot of crashes and time wasted if someone had got it right in the first place……

jh

I can say that memory crashes are a thing of the past now on smoke 64-bit with 5GB of RAM. So, the memory definitely helps…at least on smoke.

[danmargules]

has anyone run into problems with this? even though I went through the pdf manual and followed their steps on how to consolidate and delete history.. I still seem to be having problems deleting projects after I’ve archived them.

what I am getting is something that looks like this:
ERROR: VOLUMEMGT! Unknown file h1136852994_443416_. Continue removing it? Y/N

then I have to sit there forever continuosly pressing Y for a very long time, have found no way around this.

Am I missing something?

[BKM]

danmargules wrote:

has anyone run into problems with this? even though I went through the pdf manual and followed their steps on how to consolidate and delete history.. I still seem to be having problems deleting projects after I’ve archived them.

what I am getting is something that looks like this:
ERROR: VOLUMEMGT! Unknown file h1136852994_443416_. Continue removing it? Y/N

then I have to sit there forever continuosly pressing Y for a very long time, have found no way around this.

Am I missing something?

Known Bug… soon fixed in a QFE.

A pain I know.

BKM

[danmargules]

thanks BKM, was getting no answers from my Discreet rep.

[Author]

Posts