Forum Replies Created
-
Posts
-
How long is your timeline? Are their SFX on every shot? What is your reformat/resize from?
BKM
I can tell you what Smoke is missign from Flame. So if you know what Flint is missing then you can compare the two.
Smoke lack a TRUE Batch module. Smoke can only enter batch or BFX via the timeline, which really isn’t a big deal if you are timeline savy and just enter BFX with alot of black clips. Thre maybe some issues with matte channels as BFX does suppot matte outputs back to the timeline… but only as matte contianers.
Smoke lacks Particles and deform nodes in Action. Maybe some other Action tools… but largely it all there.
There may be a few other little things… but the products are very close.
I would think that a 2K Smoke would do you good. Only a 2K Smoke has Batch.I am not sure that a Flint would be better… a Flame might.
BKM
If it’s the same as Smoke… Then it’s hotkey (comma) ad hover over the clip the cursor should turn to a slip icon 0_0.
BKM
The reason I asked about being wired or wiretapped, is that I have lost media(red frames) when I Tether Clips via wiretap. There are certain instances, like I/O, switching projects, etc. That will cause a frame purge.
There is a bug in SW 2008 that causes wiretapped frames via Tether to not be flagged properly with the right reference count. It may be a similar case with your wired material.
Was it background wired by any chance? Foreground wire is rock solid. Background had issues I believe.
Again this may not be related, but it does sound like similar issues.
The work around for my Tehter clips, is to not do any I/O, or project switching while transfering. Then copy all the clips from one library to a NEW library. This will automgically force the frame reference count to increase and the system will not purge the material accidentally.
I believe that this issue is resolved in 2009. But I would verify that.
BKM
The library with missing media… was the media wired or wiretapped into it?
BKM
This library with missing media… was it by any chance Wired or Wiretapped in??
BKMIn the same shell that you lanuch Flint from… type…..
setenv DL_FORCE_IC
then launch Flint, that should force an Integrity check.
BKM
I have had the odd crash for no reason from time to time. Some are kind of predictable.. like if I have a large rez file in Action and press the Keyer button.. it may crash to shell. But then again, it may not.
I may have 2 crashes in 8 hrs. and I am running on IRIX with 4 gig RAM.
Try and upgrade to SP2 then… it can’t hurt. All in all, it seems to be as stable as any other Smoke release. I thin kin some ways (IRIX) better then 2007. That crashed on my system when I would walk away from the machine… when I came back, I was looking at the shell.2008 has been much better in that aspect.
BKM
Are you on Linux or IRIX? Did you ever run 2008 SP1? I saw no real fixes for Smoke in SP2. And since we have standalone systems, I haven’t upgraded from SP1.
BKM
I have Tether as we are P2 house and I need it to get clips into Smoke.
I have been very happy with it. it is a very solid app. Not buggy or crashey.We use P2 log Pro to make Qts on our Mac and then simply transfer to a Smoke Project Library. Quick and Easy.
BKM
I’ve brought back old Smoke v6 Archives back into 2008 with no problems. Some odd things might happen like history setups acting odd due to bugs in an older version.. but nothing that wouldn’t have already been there.
I have never heard of anyone having a problem between IRIX and Linux. The Flame/Smoke software is still the same.. and they have always tried to keep archives backwards compatible.
BKM
Does your font have any spaces or odd characters in the name or path? Sapces will cause the font to not be found and replaced witht he default font.
And did someone change the default path for fonts? You can change that in preferences.
BKM
It’s my understanding that you no longer need a WIRE license for any system v2007 and up.
Wire still exists and is installed with the Flame/Smoke software.
BKM
I received this from P2log about an update… Maybe it has something to do with it. If not it’s an FYI.
BrianThe new QT 7.3 changed (slightly) how null values within the MOV file header are defined. Apple, for some unknown reason, departed from the long standing zero (0) designator for a null setting–now a minus one (-1) value = null. This small change (which may have been an oversight?), causes QT Player and any QT based application attempting to play the MOV file to fail since the QT engine no longer knows what action to perform when a zero designation is encountered.
Since MOV files already existing with a zero designation are no longer playable, it is unclear at this point whether Apple will fix the problem in later QT updates or not. There are numerous applications providing QT files that may have been affected by this problem, and you may have many older QT files created by Apple applications that will not open due to this problem.
2008 IS the last release on IRIX….
Autodesk’s development roadmap is focused on delivering the most innovative and competitive grading, editing and effects solutions available – solutions that leverage the latest in computing, storage and networking technologies; pushing the limits of system throughput. Autodesk is focusing on Linux platforms as we feel it offers the best performance, stability and overall cost of ownership.
In many cases software that is tuned for new platforms cannot provide an acceptable level of performance on older platforms, or the older hardware is no longer supported. It is for this reason that Autodesk advises that it will be phasing out development and product support for the platforms identified below.
Hardware Platforms: Last Certified Releases
The 2008 systems software releases are expected to ship in the fall of 2007 will be the last releases to be supported on these platforms:
Products Affected
PlatformsInferno, Fire, Backdraft, Backdraft Conform
SGI Onyx 350Flame, Smoke, Backdraft, Backdraft Conform
SGI Tezro