John Heagy
Forum Replies Created
-
[Jerry Hofmann] “Apple came up with an alternative to the xserve Raid when it went away,”
Yes, Promise storage and Xserve RAID EOL were announced in the same news release. This gave customers an immediate alternative – not a good alternative – but it made clear Apple’s commitment to Xsan.
If Apple thinks a MacPro is a server alternative they are sadly mistaken. If they plan on announcing PC server support for OSX Server later, then I question their marketing smarts. Do they think people will walk back across that charred bridge? I suppose, but clearly not the way to do it.
Raise your hand if anybody thinks the control freaks that run Apple would be at all interested in supporting hardware they can’t control?
John Heagy
-
[Jerry Hofmann] “Space? Well you gotta be kidding here. Side by side is possible”
I work in a 200,000sq/ft facility and space is an issue. Data centers are only so big and expensive… racks, cooling, computer flooring, etc.
Example: We have a six Xserve Episode cluster that occupies a mere 10.5″ of rack space. It’s all MacPro equivalent would consume the entire rack.
So no… we are not kidding.
John
-
[Jeremy Garchow] “I’d look at CatDV if fcp srvr isn’t doing the job. “
CatDV and FCP Server are both Java apps. Java’s future on OS X is in doubt.
https://www.macnn.com/articles/10/10/21/tech.on.path.to.completely.abandonment/
Certainly a series of disturbing announcements for anyone who relies on Apple for enterprise operations.
Seems if it doesn’t run on iOS… it’s kicked to the curb.
-
Will has it right. This is bad news for FCP users. It portends the end of OS X Server, Xsan, and FCP. We have 50+ Xserves… we’re screwed.
I have long hoped that Apple would certify a few PC servers to run OS X Server. The lack of this companion accouncment ala Promise, and the MacPro Migration guide, pretty much puts a stake into that.
I predict someone is designing a MacPro to 1 RU enclosure kit with dual power supplies as I type.
John Heagy
-
[Jeremy Garchow] “Use them as a SAN controller. ;)”
Don’t even joke about that! Using a G5 as a metadata controller is akin to hauling nitro glycerin in a horse drawn carriage across a cobblestone street.
-
I wouldn’t expect any FCP news.
I’d be thrilled with 64 bit Quicktime news though! Quicktime X is a hollow shell.
-
[walter biscardi] “Card 1 is repetitive just like Tape 1 is repetitive”
The one difference being “Card 1” can be the exact same card used over and over, where “Tape 1” would be new tapes. Someone would have to keep labeling new tapes “Tape 1” to get into trouble.
We all agree, I just wanted to make that distinction.
John Heagy
-
That’s a bit of conflicting advice. Are you suggesting Card 1, Card 2, etc… or, what I’d assume is a non-repeating “Master Control Number” for “Tape Name”? I would not recommend “Tape” names that repeat like “Card 1” obviously would.
Even though FCP is, unfortunately, filename based – there are a few third party tools that will save your bacon and link via Tape and TC, not to mention some DI workflows still use EDLs. These will only work if all your media has unique tape names and TC, so it’s “good form” to do just that.
John Heagy
-
Erik,
If the bug is a gamma shift, remove the following from /Library/Quicktime
AJACodec
AJAUncompressedCodecand restart
John
-
Yeah that would make the list. I wish camera manufactures would include a “break” button that does the stop/start in one. Pressing stop then start does invite the possibility of the cameraman getting “out of sync” and stopping when he’s shooting and visa versa. I think we’ve all seen the 1 hr shot from inside the camera case. A “break” button would be safer.
Unfortunately with the Ki Pro Mini being a separate recording device… this will only encourage the “keep it rolling” attitude.
John Heagy