Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
When Leopard gets to the very final stages, won't the developers that get the seeds see the secret things? or does Apple hide them some how? or are the developers sworn to secrecy or what? Can someone please answer this question for me??

Apple will probably have a version seeded to developers that will fix most of the bugs and have almost everything but the top secret stuff. Then, awhile later, Apple will have a presentation where they show off all the new stuff and maybe even give a release date, though that usually happens after the Golden Master. Then after that they'll release a new seed with all the good stuff and release it once they're sure it works and can get enough copies made and mailed. They probably already have internal designs almost ready to go. Almost.
 
I can't wait for Santa Rosa and Leopard to be released, because that is when I will finally shed the shackles of Windows and buy myself my first gorgeous Mac (a MacBook)! Forcing myself to wait for them both is killing me though...

In regards to Time machine, is it possible to exclude certain things from being backed up. For example I don't really want to waste space backing up my itunes library songs since they're technically backed up on my ipod.

And, since Time Machine incrimentally saves data, can a lot of changes be saved above the base backup in a small space? How good would a 320Gb drive be to back up around 80Gb of data?
 
One thing we forgot to notice is the release of the iPhone in June. At WWDC we will see even more of the iPhone, since we still don't know much about the OSX that is being run on the iPhone. We'll see OSX Leopard on Macs, and OSX leopard on the iPhone.

It's going to be an interesting next couple of months for Apple. Steve Jobs he's going to be rolling out some great stuff for the Mac, and I know he will keep that promise.
 
I can't wait for Santa Rosa and Leopard to be released, because that is when I will finally shed the shackles of Windows and buy myself my first gorgeous Mac (a MacBook)! Forcing myself to wait for them both is killing me though...

In regards to Time machine, is it possible to exclude certain things from being backed up. For example I don't really want to waste space backing up my itunes library songs since they're technically backed up on my ipod.

And, since Time Machine incrimentally saves data, can a lot of changes be saved above the base backup in a small space? How good would a 320Gb drive be to back up around 80Gb of data?

I believe there is an option to back-up certain things. Time-Machine is smart with saving space, I'm sure of that.
 
Hmmmm I think there is some odd numbers here. I am an old TV Engineer, and I remember one of the issues with NTSC vs Analog RGB or y/R-Y/B-Y was that NTSC could only display about 4 million colors while component analog could display about 4 times that. I also know that LCD panels were even more limited.

I think that since we have gone digital, we have gotten used to far fewer colors. This was made possible since the human eye is reeeeeaaaaalllllyyyy adaptable to adjusting to color and not telling the brain about it.

I could see the need for component 10-bit digital and it truly surprises me that with such technologies and the draw of FCP, that the Mac does not natively support this without special drivers.

In my opinion, this locks OS X into being a good platform for DV ( 4:1:0 ) and not native D1 or better ( 4:2:2:2 )

I hope Apple fixes this in Leopard or better.

Max.

I think as far as color accuracy, you may or may not get the right colors on your monitor, depending if your video hardware supports overlays (most cards do, I don't know if MacOS X uses that though).

Today AMD/ATi video cards (and maybe high end nVidia cards) do support 10 bit output so if you connect an HDTV to it, you may be able to double check your work as is. However, the OS is still limited to 8 bits per component natively.

As for NTSC, the NTSC standard from 1953 is a pretty large color gamut. However, what is commonly called NTSC today is really SMTPE-C which has a gamut comparable to sRGB. NTSC(1953) is better than SMTPE-C except for some light greens and dark blues and purples.
 
I have not heard anything about any improvements in color management in Leopard. However, I am not sure Leopard actually needs much improvement in the operating system itself; Tiger (and I think Panther as well) supports many color spaces (including Lab) for use in programs through Quartz. I am also pretty sure that floating-point values are used to describe these, so I am pretty sure that the possible detail level is much higher than 8 bits per component. In addition, ColorSync allows 16 bit per component information. So, there may be no lacking at all in Mac's color management innards, but instead in the software that uses it.

It should be noted, actually, that color management is still much better on Mac, I believe, than it is on Windows. Correct me if I'm wrong (been awhile since I've worked with Windows color stuff) but doesn't windows only natively support 24-bit and sometimes 32-bit per pixel RGB (meaning 8 bit per component)? So therefore it is not Mac which is inferior to Windows, it is the software written for it.

Colorsync uses 16bit precision to do colorspace transformations. Windows ICM 2.0 does something similar. That's a good thing in general, for accuracy, but there are also other factors that should be taken into consideration such as the profile connection space.

Supporting a color space is not the same issue as the operating system allowing the hardware to express itself more colorfully. Mac does have better color management features than Windows, and Colorsync has a lot of useful utilities to look at profiles. However, Windows Vista brings a new proprietary(created by Canon) CMM called Windows Color System, whose goal is to make the CMM smart, and ICC profiles dumb. One of the things it does better is that can convert black levels in CYMK profiles automatically (right now you have to use either devicelink or Adobe's Black point compensation setting), and it uses a new color model due to profile conversions called CIECAM'02. But, despite all this advancement, the tools to set the settings are very weak, and few companies take advantage of WCS at the moment.

Perhaps Apple can upgrade Colorsync to be more capable than the ICC v4 guidelines or at least include a few more utilities.

Windows natively supports 32 bit rendering (GUI+ supports alpha channels) but that's as far as it goes. It's still restricted to 8 bits per component, using the alpha channel for transparency effects. Video cards like the high end Quadro series and Fire GL series do offer high bit internal rendering, but you have to use OpenGL programs like 3d Studio Max or Maya, but nevertheless, what you're seeing on screen is the effects of 8bit per channel.
 
BTW, what is Time Machine exactly?

I know Windows Vista supports shadow copy natively, where it can save copies of previous versions of the files you use. For example I open up a photo, change it a bit and then save it. If I don't like the edits I can go back to the older copy and work from there.

Is Time Machine something similar?

I think it would be cool that versioning software is builtin to the OS.

As a former system adiministrator, I hated to look up old back up tapes to find files that that the employees screwed up and wanted the original verseion. So something like this would be a good thing.
 
BTW, what is Time Machine exactly?

I know Windows Vista supports shadow copy natively, where it can save copies of previous versions of the files you use. For example I open up a photo, change it a bit and then save it. If I don't like the edits I can go back to the older copy and work from there.

Is Time Machine something similar?

I think it would be cool that versioning software is builtin to the OS.

As a former system adiministrator, I hated to look up old back up tapes to find files that that the employees screwed up and wanted the original verseion. So something like this would be a good thing.
Basically you can do this but instead of just photos, you back up your whole system onto an external HD for example, and then if you want to keep the exact same system you have now, but also the copy of one document saved e.g. two months ago, then you can just save that one file.
 
I think as far as color accuracy, you may or may not get the right colors on your monitor, depending if your video hardware supports overlays (most cards do, I don't know if MacOS X uses that though).

Today AMD/ATi video cards (and maybe high end nVidia cards) do support 10 bit output so if you connect an HDTV to it, you may be able to double check your work as is. However, the OS is still limited to 8 bits per component natively.

As for NTSC, the NTSC standard from 1953 is a pretty large color gamut. However, what is commonly called NTSC today is really SMTPE-C which has a gamut comparable to sRGB. NTSC(1953) is better than SMTPE-C except for some light greens and dark blues and purples.

Ahh, SMTE-C, I remember when this was brought out. You are right, except that for the Human eye, the GREEN was the most vibrannt improvement, and then, the change was applied to the displays ( phosphor in the CRT at the time ).

Still, the limiting factor for NTSC was the color was put on a 3.58MHz subcarrier, which, besides causing issues in the image, was a limiting factor in the color depth. Again, the eye is pretty incredible.

I am sorry for the trip down ancient history lane... Thank you for the explanation on what the OS natively supports, vs. what the hardware can do.

This still bothers me some, but I guess if you have the right hardware, such as a BlackMagic SDI Input card, and a ATI Display card, you could have a workAround for hi-perf video work.

Max.
 
Actually... It can... set your CRT to 60Hz and see...

Nevermind.. caught the delayed sarcasm.

Max.

Just for those who are curious about the limits of human eye vision:

"The [United States Air Force], in testing their pilots for visual response time, used a simple test to see if the pilots could distinguish small changes in light. In their experiment a picture of an aircraft was flashed on a screen in a dark room at 1/220th of a second. Pilots were consistently able to "see" the afterimage as well as identify the aircraft. This simple and specific situation not only proves the ability to percieve 1 image within 1/220 of a second, but the ability to interpret higher FPS." -from whispers.ausgamers.com/wiki quoting a poster from Valve's Steam forums.

From that website, the author states that our eyes don't see in Frames Per Second but rather it interprates events based on distance, motion, so it sees more in terms of streams of information rather than "separate still scenes" per second. Things like persistence of vision (how long it takes for an image to fade from our eye, which is why film works well at 24 fps since we don't see the intermediate black frames) and colors affect the way see things.

So as far as hardware and games go, a higher refresh rate and FPS in games will lead to smoother appearence of motion that the majority will subtly notice, and the more critical will appreciate.
 
Nevermind.. caught the delayed sarcasm.

That's good. :) What I don't understand is why these "the human eye can't..." myths keep getting repeated when you can easily see the limitations of 24 bit color and you can easily see the difference in fps far beyond 30, etc. I mean, it's not like you have to take it on faith or anything....

--Eric
 
About Time Machine, you can choose which files/folders that you do NOT want to back up. There were some screenshots of Time Machine's System Preference panel and it showed a box with a + and - button above it, and the + is for adding what you DON'T want to back up and the - is to delete something you said that you don't want to backup but now do. I'm sure Apple will do other things to be more intuitive and space friendly.
 
Apple may have several different branches for Leopard, perhaps even separate ones for bug-fixing, features, and the developer preview. The builds that we are seeing are meant to give developers access to APIs so that they can try out new features.
Apple also releases the same builds to non-developers through Apple Software Customer Seeding (aka AppleSeed). I've been in the program since the Cheetah seed and many of us test the OS with our own applications and workflow on a wide variety of hardware setups (and do not test the lower level developer related stuff). True, Apple has several branches internally but what they build and then send out are stable milestones to that point with a list of focus areas which we test and provide feedback on. It is a rarity for them to send out builds with a lot of functionality disabled so that we can test out some very specific areas (I recall it was done only once early in the Tiger Server seed).

I've read on some other sites about conspiracy theories that they are just seeding fakes to keep developers off guard but if that were true, then this would be defeating the purpose for those us in the customer seeding program using the system out in the wild on a daily basis so that Apple can acquire the necessary feedback to address issues their internal QC engineers cannot find via their battery of tests. Apple will release the stuff they are still hiding when they feel it needs to be released to allow us to test.
 
I've read on some other sites about conspiracy theories that they are just seeding fakes to keep developers off guard but if that were true, then this would be defeating the purpose for those us in the customer seeding program using the system out in the wild on a daily basis so that Apple can acquire the necessary feedback to address issues their internal QC engineers cannot find via their battery of tests. Apple will release the stuff they are still hiding when they feel it needs to be released to allow us to test.

I don't think Apple is releasing "fakes". I just don't think Apple is releasing everything. They don't really have a need to demonstrate new features such as UIs early. There is not much to "test" here, and not much developer stuff which relies on this.

I still think that the main reason which bugs have not been fixed in these newer builds (though I have not seen them, so I really don't know) is that Apple simply doesn't want to merge their branches too often. I think that merging development and production branches caused problems for them when iTunes had resources hinting at the iPhone.

Still, I think Apple is probably quite interested in the bug reports from developers. However, they are probably not so interested in bug reports which they have already fixed in their development branch. Supposedly, the list of known issues between this build and the one before are almost completely identical. If Apple had been doing anything, you'd figure a few of these had been fixed... So, most likely, Apple already has them fixed elsewhere. Or else, knows perfectly well how to fix them but is currently focusing their effors elsewhere.
 
That's a scandalous statement. Anyone who works with color and printing knows about the CIE LUV/LAB chart that shows the gamut of average human vision. A typical display only shows about 2/5 of all possible colors that a human eye can see. While a video card can provide 256 shades of color per component, a lot of the viewable colors will be repeated because of the limitations of the display. Also contrast is another issue that needs to be addressed. Our eyes have incredible dynamic range, a monitor doesn't. HDR displays can use the extra bits to encode brightness levels (or more colors that appear brighter or darker).

It is true that our vision is limited to about 2 million colors, but what you see on screen is cut to about 800,000, maybe less, assuming a fixed brightness level.

Just to clarify, we were talking about software limitations of color reproduction. Simple fact is that human eyes do not see beyond 24-bit (10 million colors). What you are talking about is the addition of alpha levels. Sorry if I am coming across as pedantic but this is how it is and it seemed like everyone was continuing to spread disinformation.

It would be great if someone could enlighten us non-developers what the "a" in the build number means. Is that typical?
 
Just to clarify, we were talking about software limitations of color reproduction. Simple fact is that human eyes do not see beyond 24-bit (10 million colors). What you are talking about is the addition of alpha levels. Sorry if I am coming across as pedantic but this is how it is and it seemed like everyone was continuing to spread disinformation.

I am not talking about alpha levels. Alpha levels are simply just mathematical constructs to do color blends rapidly in hardware. (Or if you're using Photoshop, they are just 8 bit grayscale images that can affect the output of the other RGB channels) This is useful for games, and video editing software, and even for things like transparency on the desktop User Inteface. I am talking about color gamut. When you get a chance, look up in the wikipedia terms like color gamut, CIE LAB, etc. Then you will have a better understanding of what I am talking about.
 
Wait

Could you guys ever think that the Aperature prediction was a mistake. That the Leapord is all about the big announcement on April 15th. At NAB?:confused: ;)
 
Leopard

Could you guys ever think that the Aperature prediction was a mistake. That the Leapord is all about the big announcement on April 15th. At NAB?:confused: ;)

This is quite possibly the case, in that it will take the Leopard environment to demo new apps such as FCP, FCE, Logic 8, and who knows what else?:rolleyes:
 
Funny AvSRoCkCO1067, Your Avatar does not look like the Cherry Creek store... Of course, I guess, since there is not one in Golden, you must have to dream of the perfect Apple Store. :D

Max.

I've been to the 5th Avenue Store. It was nice - I prefer Cherry Creek, though, because it's not as crowded :)
 
I don't think Apple is releasing "fakes". I just don't think Apple is releasing everything. They don't really have a need to demonstrate new features such as UIs early. There is not much to "test" here, and not much developer stuff which relies on this.
BTW, it wasn't on this site the conspiracy theory about Apple possibly seeding fakes. I just find some of that stuff being thrown out on other sites way off from the reality with the way Apple has handled Mac OS X seeding since Cheetah (much more mundane than people think). But yes, at this point in time, the cosmetic related stuff isn't important even for us non-developers to test as opposed to finding and reporting problems with the actual functionality of features in the OS and how a variety of applications work with regards to compatibility, performance, etc since there is only so much Apple can test in their lab (they can't duplicate the wide variety of situations which exist out there). If Apple has UI and Finder related changes in the works but are holding them off for maximum impact, I think it will end up showing up closer to when the OS is nearer to GM (given how quickly actual details of the latest build has surfaced, it is understandable why Apple isn't going to divulge whatever they are keeping secret now in order to get the most bang closer towards release).

I still think that the main reason which bugs have not been fixed in these newer builds (though I have not seen them, so I really don't know) is that Apple simply doesn't want to merge their branches too often. I think that merging development and production branches caused problems for them when iTunes had resources hinting at the iPhone.
Based on previous seeds (Tiger, Panther, etc), they've normally been very aggressive. With Leopard for 9A283 and 9A321, engineering resolved a large number of issues I reported but so far, none for the ones in 9A344. They normally are quick to respond if it is already a known engineering issue, ask for additional debugging information, ask us to try a specific set of steps, or if a problem has been addressed, to check and respond if it has been resolved but so far, nothing. This just leads me to believe they are busy working on prioritizing and addressing them which is one possible reason why the relatively small number of builds to date and seamingly large list of known issues.

But you do also have a point regarding not merging branches too often because especially with Leopard, they probably don't want to accidentally introduce elements of the stuff they don't want us to see just yet and are therefore managing the entire build process a bit more carefully.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.