Forum Replies Created
-
Posts
-
ultimind wrote:I’ve seen this done and it’s indeed a very quick way of archiving. You have to be EXTREMELY careful while mounting and unmounting the drives though. You can VERY EASILY fry a drive if you’re not careful. I saw two 300gb archives fry because they were mounted improperly. XFS is a very poor file system for archiving. It’s far too fragile.
It shouldn’t be a problem… what exactly happened? As long as you do unmount them and use “scsiadminswap” to quiesce the SCSI bus while you unplug them it should be fine. XFS is a very robust file system, I guess frying the bridge chip is more likely…
NFS is a bit shitty on Irix. I find it works much better for single large files than loads of little ones like image sequences, it’s definitely worth tar’ing things up if you have the space. Maybe even tar’ing directly to the NFS mount might work.
someone2006 wrote:would I be able to connect this array and use it normally? Like, have it work as a Stone array, format it to StoneFS and live happily ever after? Even with v9?You couldn’t use it as a Stone, no, the disks in Stone arrays have special and magical stuff in the firmware, normal disks won’t work. You could use it with the 2 gig file based framestore stuff in version 7, providing the array and the Octane have all the right plugs and whatever.
I don’t work for Discreet, but I do hear that they frown slightly at license transfers, where frown==charge you loads to continue the support contract or get upgrades. But a second hand Flame 7 is still very worth having, lucky you 😉
I found that link ages ago via Google, it’s amazing what nooks and crannies their spider gets into.
Rob’s right, anything above 7.6 won’t work at all without a Stone… but if you’re spending enough to get newer than that, you can probably get a Stone out of pocket change 😉
For earlier versions you can use any storage that works with an Octane, so internal disks, external SCSI or FC JBOD arrays with Irix’s XLV software RAID, external hardware RAID arrays as long as Irix supports them, even IDE disks with SCSI bridges. If you get a really fast single disk (think 15k Cheetah) you can just about scrape single-stream SD playback, but… really, don’t.
Check out this link from an old Discreet FAQ, there’s a limit of 2 gigs per file-based framestore without a special license. You could create several 2 gig ones and switch between them but that’s kinda annoying…
Flame 7 should be okay without a stone, you can use a file based framestore up to 7.6 IIRC. But bear in mind that fast framestores are what makes Flame work so well, so if you don’t want to use a Stone, a fast disk array would still be cool.
As for upgrading things… Flame 7 should run on any graphics you can put in an Octane, but check your license to see if it’s locked to a particular kind – the feature string might have MX in it for MXE graphics for example. Upgrading CPUs, RAM, disk is all no problem. Moving it to another machine should to possible if you swap the machine’s SysID button over, which is hidden away on the back of the frontplane, looks like a battery.
blumediaprojekt wrote:we’ve been archiving to file on SATA drives w/scsi adapter hooked to internal scsi bus of our octanes for over a year now!Shiny! Do you mean a little bridge board on that back of a SATA disk, going in the front of the Octane above the system disk, or an external enclosure on the external SCSI bus? Either way, what bits did you use? I didn’t know there was cheap SATASCSI stuff out there.
Wow, sounds like d2 took their sweet time in doing a public release then… I wonder what coolness they have in their internal versions now that we’ll see in years to come …
Check out the Cascading Expressions bit in the manual. It’s really neat, you can do that whole thing in one go by selecting the channels in order in Info view, then typing an expression like “SelectionOrder * z_depth.position.z”. That would put “1 * z_depth.position.z” on the first thing you selected, “2 * z_depth.position.z” on the second, “3 * z_depth.position.z” on the third and so on. Saves oodles of time… when you can remember to do it 😉 As well as SelectionOrder there’s CascadeChannel which is replaced by the name of the previous channel in the selection, easy to make a string of axes that follow each other about or whatever.
If you just want exactly the same expression on lots of channels you can just select ’em all in Info view and hit Expr.
You should. It should be called “InDISCREETions”…
Sorry… I’ll get my coat 😉
t wrote:But Nuke has had a mac version for 2 / 3 years nowMore like, err, three months… http://www.fxguide.com/article316.html 😉
I found it rather *lacking* in features rather than the reverse. And really slow.
ultimind wrote:Another tidbit: Many of Discreet’s Mac people who worked on Combustion went to Apple to work on Motion.I thought people had worked out that this wasn’t the case, and it just happened that the Combustion team were working in the same building as the Motion people at one point?
How are the mighty fallen 🙁
Yeah, more Sparks are always good 🙂 I’d be interested to know how you implemented Bokeh defocusing if you can tell…
Sadly you can only output one clip at a time from a Spark so you’d need one for each layer you wanted. Still, I’ll have a play.
5.
Vympel wrote:sorry for the Off topic
but this FFI and Smoke systems actually is limited to 12bits per channel, when import log files to convert to linear space, 12bits is a little to accomodate the range of “light” of this files in linear space? Or the tools for color correction of FFI can work normally in log space being necessary only a view LUT?Everything in Flame is designed to work in linear space. You can use it in log space but the results will likely be very strange unless you really know what you’re doing. Generally there’s no reason to try and do that, 12 linear bits is not really all that terrible for normal-type things.