Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Snow Leopard Testing Report Thread

Kaku Ito

Well-known member
Joined
Feb 20, 2008
Messages
2,803
Reaction score
3
Points
38
Age
65
Location
Chiyoda-ku, Tokyo
Website
www.dittok.info
I have just received the Snow Leopard when I came to the office.

I'm installing it to the spare volume I have repaired yesterday.
 
Interesting, upon installation, at the selection of the installation volume choice, I already see ATTO volume via R380 and Celerity. I guess they included ATTO driver at least (or was the Promise RAID uses ATTO so that the driver is the same?). I'll see what happens to Areca later.

The installation time prediction says 44 minutes.....
 
Can you verify (Once you're done installing, obviously) whether the RED FCS installer works? I seem to recall a few people who had the Beta 10.6 who it wouldn't work for...
 
I'm actually installing to a carbon copy of a system I'm using, so everything is installed including RED ROCKET. If this does not work well then I'd do a fresh install.

Count on me to figure out the gamma handling. I know the gamma issue is not a bug, instead it is how Apple decided to handle between RGB content and YUV content. The issues don't happen unexpectedly. I'm certain Evangelo would say the same thing. So, I will see how Apple changed the handling manner on display system gamma, gamma handling in application software, RGB and YUV conversion vise versa and gamma handling per format. These things appeared inconsistent (actually wasn't but auto gamma adjusting made it look like inconsistent), but they weren't so I will check how each area had changed in Snow Leopard.

Installation is done now.
 
It might be interesting to compare performance/stability of a clean install vs an upgrade install. I've always heard you should do a clean install on production machines. But it's such a pain in the butt. If upgrade is stable, that's what I'll be doing.
 
It might be interesting to compare performance/stability of a clean install vs an upgrade install. I've always heard you should do a clean install on production machines. But it's such a pain in the butt. If upgrade is stable, that's what I'll be doing.

Ben, it is a major pain to do a clean install as you have various software, plugins, documents, etc that all have to make their way back onto the fresh OS. But, in my opinion that is the only way to approach it when doing a major upgrade. Just make sure you have all of your installers and related information (serial #s, etc), compatibility reports, and of course have a clone of your current system ready to be restored if all goes wrong for some reason.

Set aside the time, do a clean install, and most likely your experience will be better. I've never been a big fan of installing a new OS over a previous OS. Just seems like you're asking for trouble.
 
So far so good.

ATTO R380 based RAID is working, FCP7 with FCS3 installer is working, I used log and transfer to ingest native, sent to Color, all working. The gamma is consistent on Clipfinder's project window and the edit look window (as long as you don't touch the parameters which the REDCODE 3.8 does not allow changes to show on the proxy), then in Color, it looks pretty much identical but slight difference in color balance (I guess Color go through additional process). However, the gamma in FCP looks 1.8ish now. FCP to show materials from 1.8 to 2.2 (just like multiplying master gamma), now it shows straight but it looks lighter. I will look into this more.
 
and the fun begins......

So far so good.

ATTO R380 based RAID is working, FCP7 with FCS3 installer is working, I used log and transfer to ingest native, sent to Color, all working. The gamma is consistent on Clipfinder's project window and the edit look window (as long as you don't touch the parameters which the REDCODE 3.8 does not allow changes to show on the proxy), then in Color, it looks pretty much identical but slight difference in color balance (I guess Color go through additional process). However, the gamma in FCP looks 1.8ish now. FCP to show materials from 1.8 to 2.2 (just like multiplying master gamma), now it shows straight but it looks lighter. I will look into this more.
 
As Steve pointed out, there are procedures if you're doing a clean install. I did clean installs the last two OSX updates, and both times I forgot something that caused me major headaches. Serial numbers go missing, etc. Both times I forgot to deactivate my copy of Final Draft, and trying to get tech support from them is like pulling teeth.
 
I have multiple machines and multiple boot volumes to do this test. We can see how well it handles the update fastest this way. I'm a integrator so am aware of upgrading procedures, but so far, this update is working better than 10.5.2 update that RAID companies had to rewrite the drivers.

After figuring out what works and don't then I would fresh install only the ones that certified to work. By the way, upon installing fresh system, some might think the migration software is not that reliable for migrating your accounts, I agree in certain extent. You should always make everything in working order, like apply disk utility fix the volume and the permission fixes.
 
On FCP gamma look being different from Clipfinder edit look (with old science) and Color, FCP only shows proxy look out of REDCODE 3.8 which lacks many metadata applied, my observation is only for R3D handling, not to judge the native FCP gamma handling with other QT codecs at this point. This is only for current RED environment.

Previous problem of R3D in Mac was that mainly, Color was looking at R3D as RGB material, then show R3D material as 1.8 on the screen and video output. This seems to be fixed so for the folks that use Color workflow. There are two ways older environment handled the rendering, output RGB material (including R3D) as DPX or RGB material as QT (more over in different codecs, it handled differently in gamma) the applied or didn't apply the gamma change. So, I will check how they are handled in the new environment.

And yes, new version of REDCODE that supports the new color science and support for the entire metadata will conclude the complete workflow.
 
KAKU THANK YOU.
Very cool findings.
 
Those of you upgrading to Snow Leopard should read this article about Snow Leopard's updated method of calculating file sizes.

Leopard and previous versions of MacOS used 1024 to calculate a GB... (1024 MB = 1 GB)

Snow Leopard will use a base of 1000 to calulate GB.. (1000 MB = 1 GB)

bytes obviously stay the same, but if you transfer a file from 10.5 or earlier to 10.6, it will show up as a different file size... See the article for more information...

Just thought this would be a good point of information for the community..

http://www.macworld.com/article/142471/2009/08/snow_leopard_math.html?lsrc=rss_main
 
Hi Jason, thanks for the info. That's very helpful.

Luis and Snow, my pleasure.

I realized now that metaSAN doesn't load after updating to Snow Leopard. I expected this but us metaSAN users have to wait until Tiger comes out with the supported version.
 
Hi Jason, thanks for the info. That's very helpful.

Luis and Snow, my pleasure.

I realized now that metaSAN doesn't load after updating to Snow Leopard. I expected this but us metaSAN users have to wait until Tiger comes out with the supported version.

Hmm... thats me... no snow for now then...
 
Evangelos,

I tried to install to make sure, but the 3.2 installer tells me that "3.2 only works with Leopard", so it is specifically made not to load in the other OS versions. I guess to avoid conflicts. Have you considered other SAN solutions? I'm wondering if fiberjet solution working on Linux server would have this kind of wait period dilemma.
 
Back
Top