Apple will no longer be selling maintenance for Shake and no further software updates are planned as we begin work on the next generation of Shake compositing software. While we're excited about the innovations we can bring in the future, we understand you have a business to run today that requires Shake. To that end, we will provide all Maintenance customers with the following three options:
A. Customers can continue with end-user e-mail support, as well as SDK support for the duration of their Maintenance contract.
B. Customers may elect to cancel their Maintenance and receive a pro-rated refund for the unused portion. Existing software licenses would continue to function according to the Software License Agreement. Maintenance customers that wish to cancel their contract must do so by July 23, 2006.
C. Additionally, Maintenance customers may choose to license the Shake 4.1 Source Code for $50,000. The Source Code license includes a 5,000 seat volume license of Shake 4.1. This offer is designed to help facilities with significant Shake investments maintain a reliable and controllable visual effects pipeline. Maintenance customers that wish to license the Shake 4.1 Source Code must do so by July 23, 2006. Apple reserves the right to refuse any maintenance customer source Code access.
I like shake, but it's never really fit in amongst the other Apple apps. But to EOL it for their (rumored) own app seems short-sighted. It's more likely people will migrate to Nuke in the meantime, which has jumped ahead while Apple has mostly let shake wither on the vine.
A year since version 4, and we've got bug-fixes and an universal binary. Whee.
This is mainly a problem with the new resource-fork friendly rsync (I assume you're using -E). It can't/doesn't compare the resource forks, and so simply just recopies all files that include them. It's sort of the safer action (makes certain what you're syncing to matches) but, as you've found, gets quite irritating in certain instances (for example, it continually recopies my 2GB VPC image). Here's hoping they fix this in a new version.
L&S was the last Disney project to be produced by the Florida skunkworks (out from under the thumb of Eisner). Despite efforts to push his in-house projects, "The Emperor's New Groove" and "Treasure Planet", L&S proved what the animators were capable of without Eisner's excessive micromanagement. The response: elimination of the Florida studio, under the guise of cutting costs.
is whether Sony has managed to solve the compression problems of getting an HD signal on a dv tape. Footage from the GR-HD1 has nasty compression artifacts which has preculded anybody from getting too excited about using it.
My money's on no, but it's still cool to see companies working at getting these products to market. The next few years are gonna be exciting for filmmakers as desktop HD comes online.
Yeah, get FCP. The AG-100 is a good cam, as are Canon's GL2 and Sony's PD-150's. All can be had for around $2-3k, and are worth the upgrade over single CCD cams, esp. for short filmmaking. Remember to blow another $500-$1k on some long-life batteries, a car charger, a good fluid-head tripod, plenty of tapes, a boom pole + mike, a set of basic filters, and a sturdy case to carry everything around in.
I wrote a dinky X-Wing knockoff engine back in high school. It was just before the Voodoo 1 and the whole hardware revolution, so everything had to be done in software. The math was a bitch, but once I got going at it...dizzam!
After that, I quit bothering in calc class. Got a D- and a 5 on the AP BC exam. Official quote from the teacher to my mother: "I wish he'd failed."
At the very least, boobies should be displayed for a minimum of a second. Slow-motion is acceptable, however speeding-up is generally not (an exception for art such as "A Clockwork Orange" is given). In addition, kisses between female co-stars are not only allowed, but encouraged.
That's just how it started...I needed a little 'geek' fix now and then. And then a little became more and more, till now a little ain't a little no mo'.
But it's all good. My friend Randy says he's going to show me something called 'crack'. He says it's a thousand times better than the internet. I told him he's never visited stileproject. I'll be back soon with the results.
Teamhasnoi writes "John F. Kennedy was not a homosexual," but then seems to lead down a number of contradictory paths in his analysis. However, they ultimately lead to the same end.
He begins his analysis by diving in the historical intrepretation of homosexual textual analyis: namely, a problematic desire to defend "traditional" heterosexual orientation as a thesis to with homosexuality is offered, in the Hegelian didactic, as anti-thesis. However, the problem with this standpoint is that it is, in Fruedian terms, obsessed with sex and the id. There must exist a synthesis of the two, a standpoint that defines itself as being outside of homo/hetero-sexual concerns.
From establishing this 'meta' didactic, it allows us to recontexualize Teamhasnoi's original statement as being much less about John F. Kennedy and more about himself. He merely uses JFK as a cultural symbol to deliberately cloud the debate and hide his own personal influence upon the text: or, in other words, he is using JFK as a metaphor for himself.
However, upon this basis, the arguement comes full circle. By deliberately using a cross-cultural metaphor as symbol, Teamhasnoi draws attention to our usage of language as a signifier and the inability, as Metz put it, for the signifier to signify itself. In the end, Teamhasnoi is arguing not why we fear homosexuality within ourself but rather how we as a society define these terms and use them as tools to frame this debate. From both within and outside this context, we are ultimately forced to reexamine both our and Teamhasnoi's frame of reference in order to recontexualize both ourselves and and society at large. Ultimately, Teamhasnoi's debate invites us to reconsider what humanity, society, and politics, using the metaphor of JFK, truely mean.
Damnit! And I just got my degree in critical studies! Ahh well...I knew it was BS when I started. The trick is realizing that so is everything else.;-)
Sorry if I didn't make that clear...yeah, I'd be willing to go. It's my life-long dream to go to Mars. Hell, I'd do it without the radiation shielding. I could prob. make it, "The Man Who Sold the Moon" style.
Most of the radiation comes from periods of sunspot activity. These can be detected and the crew given a warning so they can get into a radiation shield area for a few hours. All this would require is a small lead coffin/shield at some point on the ship. In addition, the water supplies can be arrayed to provide protection as well.
Yeah, it's not perfectly safe. I (and I'm sure many others) would be willing to take the risk, though.
Apple will no longer be selling maintenance for Shake and no further
software updates are planned as we begin work on the next generation of
Shake compositing software. While we're excited about the innovations we can
bring in the future, we understand you have a business to run today that
requires Shake. To that end, we will provide all Maintenance customers with
the following three options:
A. Customers can continue with end-user e-mail support, as well as SDK
support for the duration of their Maintenance contract.
B. Customers may elect to cancel their Maintenance and receive a pro-rated
refund for the unused portion. Existing software licenses would continue to
function according to the Software License Agreement. Maintenance customers
that wish to cancel their contract must do so by July 23, 2006.
C. Additionally, Maintenance customers may choose to license the Shake 4.1
Source Code for $50,000. The Source Code license includes a 5,000 seat
volume license of Shake 4.1. This offer is designed to help facilities with
significant Shake investments maintain a reliable and controllable visual
effects pipeline. Maintenance customers that wish to license the Shake 4.1
Source Code must do so by July 23, 2006. Apple reserves the right to refuse
any maintenance customer source Code access.
I like shake, but it's never really fit in amongst the other Apple apps. But to EOL it for their (rumored) own app seems short-sighted. It's more likely people will migrate to Nuke in the meantime, which has jumped ahead while Apple has mostly let shake wither on the vine.
A year since version 4, and we've got bug-fixes and an universal binary. Whee.
-b
What you're looking for is Darwine.
Maybe he was dictating it...
Have you ever tried typing in a password after a gallon of beer?
That's not a bug, it's a feature!
It's okay. I've read that this gene is never passed on to a subsequent generation.
;-)
Just because a gene never gets a chance to express itself doesn't mean it can't be carried on. Correlation, not causation.
Re 3:
This is mainly a problem with the new resource-fork friendly rsync (I assume you're using -E). It can't/doesn't compare the resource forks, and so simply just recopies all files that include them. It's sort of the safer action (makes certain what you're syncing to matches) but, as you've found, gets quite irritating in certain instances (for example, it continually recopies my 2GB VPC image). Here's hoping they fix this in a new version.
Solarian II is available for OS X now.
The 3D game was spectre. BZflag sorta captures the gameplay but not the level design.
Another classic of the time period, updated for OS X, is Oids.
L&S was the last Disney project to be produced by the Florida skunkworks (out from under the thumb of Eisner). Despite efforts to push his in-house projects, "The Emperor's New Groove" and "Treasure Planet", L&S proved what the animators were capable of without Eisner's excessive micromanagement. The response: elimination of the Florida studio, under the guise of cutting costs.
That'll teach 'em to be original.
is whether Sony has managed to solve the compression problems of getting an HD signal on a dv tape. Footage from the GR-HD1 has nasty compression artifacts which has preculded anybody from getting too excited about using it.
My money's on no, but it's still cool to see companies working at getting these products to market. The next few years are gonna be exciting for filmmakers as desktop HD comes online.
Yeah, get FCP. The AG-100 is a good cam, as are Canon's GL2 and Sony's PD-150's. All can be had for around $2-3k, and are worth the upgrade over single CCD cams, esp. for short filmmaking. Remember to blow another $500-$1k on some long-life batteries, a car charger, a good fluid-head tripod, plenty of tapes, a boom pole + mike, a set of basic filters, and a sturdy case to carry everything around in.
;-)
Good luck
-Brett
I wrote a dinky X-Wing knockoff engine back in high school. It was just before the Voodoo 1 and the whole hardware revolution, so everything had to be done in software. The math was a bitch, but once I got going at it...dizzam!
After that, I quit bothering in calc class. Got a D- and a 5 on the AP BC exam. Official quote from the teacher to my mother: "I wish he'd failed."
Not yet out of alpha, but soon: AbiWord.
A very impressive project.
No, it is I who would make the best choice.
-Achilles
Nietzsche: "God is Dead."
God: "Nietzsche is Dead."
Nietzsche: "Some are born posthumously!"
At the very least, boobies should be displayed for a minimum of a second. Slow-motion is acceptable, however speeding-up is generally not (an exception for art such as "A Clockwork Orange" is given). In addition, kisses between female co-stars are not only allowed, but encouraged.
Smoke while you are doing so!
Don't know if you want to risk doing it, but there do exist region hacks to allow you to 'reset' your dvd region code.
But how quickly and in what direction?
In six months when she's making you her bitch with the railgun in deathmatch we'll see who's laughing. Go granny go!
That's just how it started...I needed a little 'geek' fix now and then. And then a little became more and more, till now a little ain't a little no mo'.
But it's all good. My friend Randy says he's going to show me something called 'crack'. He says it's a thousand times better than the internet. I told him he's never visited stileproject. I'll be back soon with the results.
Teamhasnoi writes "John F. Kennedy was not a homosexual," but then seems to lead down a number of contradictory paths in his analysis. However, they ultimately lead to the same end.
He begins his analysis by diving in the historical intrepretation of homosexual textual analyis: namely, a problematic desire to defend "traditional" heterosexual orientation as a thesis to with homosexuality is offered, in the Hegelian didactic, as anti-thesis. However, the problem with this standpoint is that it is, in Fruedian terms, obsessed with sex and the id. There must exist a synthesis of the two, a standpoint that defines itself as being outside of homo/hetero-sexual concerns.
From establishing this 'meta' didactic, it allows us to recontexualize Teamhasnoi's original statement as being much less about John F. Kennedy and more about himself. He merely uses JFK as a cultural symbol to deliberately cloud the debate and hide his own personal influence upon the text: or, in other words, he is using JFK as a metaphor for himself.
However, upon this basis, the arguement comes full circle. By deliberately using a cross-cultural metaphor as symbol, Teamhasnoi draws attention to our usage of language as a signifier and the inability, as Metz put it, for the signifier to signify itself. In the end, Teamhasnoi is arguing not why we fear homosexuality within ourself but rather how we as a society define these terms and use them as tools to frame this debate. From both within and outside this context, we are ultimately forced to reexamine both our and Teamhasnoi's frame of reference in order to recontexualize both ourselves and and society at large. Ultimately, Teamhasnoi's debate invites us to reconsider what humanity, society, and politics, using the metaphor of JFK, truely mean.
Damnit! And I just got my degree in critical studies! Ahh well...I knew it was BS when I started. The trick is realizing that so is everything else. ;-)
Sorry if I didn't make that clear...yeah, I'd be willing to go. It's my life-long dream to go to Mars. Hell, I'd do it without the radiation shielding. I could prob. make it, "The Man Who Sold the Moon" style.
-Brett
Most of the radiation comes from periods of sunspot activity. These can be detected and the crew given a warning so they can get into a radiation shield area for a few hours. All this would require is a small lead coffin/shield at some point on the ship. In addition, the water supplies can be arrayed to provide protection as well.
Yeah, it's not perfectly safe. I (and I'm sure many others) would be willing to take the risk, though.
Yeah, that's prob. the case. However, I can pretend I had an affect. My C skills are more oriented towards OpenGL, unfortunately.