AppleScruff1
Apr 22, 08:53 PM
Wouldn't it be funny if they put Steve in jail?
LethalWolfe
Apr 12, 10:17 PM
You really are worried that Final Cut Pro will not be more complicated than iMovie??!
No, I'm worried that FCP could be dumbed down too much to properly do the job at hand.
Lethal
No, I'm worried that FCP could be dumbed down too much to properly do the job at hand.
Lethal
vnle
Feb 19, 10:08 PM
Not much I can do with my dorm.
Do you go to UMD by any chance? :confused: Because that looks almost exactly like my dorm down to the tiny desk they give you.
Do you go to UMD by any chance? :confused: Because that looks almost exactly like my dorm down to the tiny desk they give you.
Lord Blackadder
Mar 4, 02:58 PM
If you buy a truck or SUV because you want to tow or haul, drive offroad or use it for work, fine. If you bought it because you're being "protective", then, yes, that is a selfish motivation.
Larger SUV's and trucks often do suffer fewer driver fatalities, so in some ways they are safer (in the US), but that is because they force smaller vehicles to absorb most of the impact during a crash. Also, the rollover risk remains high, so that the "protection" you are buying is pretty conditional and may come at the expense of other people's lives.
In addition, I should point out that minivans are safer than SUVs, so if you want your family safe, buy a minivan. Finally, it's a proven fact that pickups are less safe than cars, period.
If you want to debate it further I suggest we start another thread though, so we can keep this one on-topic.
Larger SUV's and trucks often do suffer fewer driver fatalities, so in some ways they are safer (in the US), but that is because they force smaller vehicles to absorb most of the impact during a crash. Also, the rollover risk remains high, so that the "protection" you are buying is pretty conditional and may come at the expense of other people's lives.
In addition, I should point out that minivans are safer than SUVs, so if you want your family safe, buy a minivan. Finally, it's a proven fact that pickups are less safe than cars, period.
If you want to debate it further I suggest we start another thread though, so we can keep this one on-topic.
theBB
Jul 19, 04:17 PM
There are more details here - http://biz.yahoo.com/prnews/060719/sfw089.html?.v=60
Desktop sales are down 14% on last quarter, and 23% on a year ago, but laptop sales are up a whopping 60% on last quarter and 61% on a year ago.
23% drop in desktop sales is surprising to me. Is it just due to people waiting for PowerMacs with Intels? It is not a good sign that higher iMac sales are not making up for it.
Of course, maybe Apple sold so many Mac Minis last year, that a drop was inevitable.
Desktop sales are down 14% on last quarter, and 23% on a year ago, but laptop sales are up a whopping 60% on last quarter and 61% on a year ago.
23% drop in desktop sales is surprising to me. Is it just due to people waiting for PowerMacs with Intels? It is not a good sign that higher iMac sales are not making up for it.
Of course, maybe Apple sold so many Mac Minis last year, that a drop was inevitable.
homsar
Apr 19, 11:04 AM
A relatively predictable spec bump? Performance bumped to exceed the new MBPs (edit: i.e. Sandy Bridge), Thunderbolt replaces the Mini DisplayPort (could conceivably have two, but I doubt it), FaceTime HD. A RAM upgrade seems unlikely but possible. SSD option may or may not move to the MBA one, probably will (to consolidate stock). A new form factor seems unlikely given current precedent; new screen sizes also seem unlikely due to lack of rumours. They could conceivably bring back the 24" (common panel size would mean fewer rumours), but I doubt they will. Thinner profile (especially on the 27") is also conceivable. Maybe they'll make the Magic Trackpad standard? Free upgrade to Lion when it releases?
Edit: As others have mentioned, a bumped GPU is obviously also on the cards.
Edit: As others have mentioned, a bumped GPU is obviously also on the cards.
Hooka
Jan 13, 05:07 PM
Come on, people!!
In my opinion, their quote, "There's something in the air," is nothing other than an allusion to the fact that they're going to introduce a 3G iPhone. We have all known that this was coming eventually; Jobs even said that the only thing stopping them from introducing it was low battery life.
I would be very surprised if they do any updating to iPhone except for software. The holidays were just around the corner, I doubt Apple will want to give back another $100 bucks to everyone who just bought an iPhone in November or December.
It's going to be a piece of hardware I can guarantee that.
In my opinion, their quote, "There's something in the air," is nothing other than an allusion to the fact that they're going to introduce a 3G iPhone. We have all known that this was coming eventually; Jobs even said that the only thing stopping them from introducing it was low battery life.
I would be very surprised if they do any updating to iPhone except for software. The holidays were just around the corner, I doubt Apple will want to give back another $100 bucks to everyone who just bought an iPhone in November or December.
It's going to be a piece of hardware I can guarantee that.
mrapplegate
Apr 3, 06:11 PM
I dont know the significance of the big gray bar on top of the page where it blocks a portion of the page when the menu bar is coming out of auto hide -they could of made it semi transparent Hopefully they change that in the final release
I see how some might not like how it is handled. I guess my point was it was by design and is not a bug.
I see how some might not like how it is handled. I guess my point was it was by design and is not a bug.
TMay
Apr 12, 08:50 PM
Pretty sure FCE doesn't support 24fps, which is kinda a problem for film editing, and an increasingly bigger problem for other work as 24fps gets used more. IIRC, it doesn't have stuff like the color scopes or audio mixer either. The main difference is the suite though.
Just read something today to the effect that Peter Jackson is following James Cameron's lead and shooting 48fps on the "Hobbit"; gambling that enough digital theaters will upgrade to 48fps by the time the "film" arrives in a couple of years time. Guess that is the beginning of the end of the "film" look for at least action movies.
Just read something today to the effect that Peter Jackson is following James Cameron's lead and shooting 48fps on the "Hobbit"; gambling that enough digital theaters will upgrade to 48fps by the time the "film" arrives in a couple of years time. Guess that is the beginning of the end of the "film" look for at least action movies.
tny
Aug 7, 08:11 AM
Let me steer this off topic real quick. I have read before that Apple has two OS teams so "in theory" Leopard would, in fact, be Panther 2.0 and 10.7 would be Tiger 2.0. Again, in theory� Can someone clear that up?
Nope. Here's how it works, usually (not saying this is what Apple does, but nearly everyone else does this, so ...). You've got one master codebase, called the "trunk." Everyone works with that. When it's time to start working toward a release candidate, you copy off the code base and create what's called a "branch."
Changes to the trunk are rarely back-ported to the branch (it usually depends upon whether they are bug fixes or new features; bug fixes, often are back-ported if they aren't risky; new features almost never); any changes to the branch which are relevent to the trunk *are* ported to the trunk (since most of them are bug fixes, and the rest are probably new features whose loss might be noticed in the next release).
The branch keeps being used by one team that is working on, let's say, Tiger, right up through the release and during maintenance (10.4.1, 10.4.2, 10.4.3, etc. are all from the branch, not from the trunk), while another team keeps working on the trunk until the time they branch (10.5 Alpha) the next release (let's say Leopard). When the newer branch hits release, one of two things happen: either the team that did the development on the new branch continues doing maintenance (10.5.1, 10.5.2, 10.5.3), or the group that was doing maintenance on the earlier release does maintenance on the new branch and the folks who designed the new branch go back to work on the trunk until it's time to branch again (10.6, let's call it Lion). Both methods have their advantages and disadvantages.
I'm guess this it what is meant by "Apple has two teams working on OS X." Two teams, but only one code base trunk. And thus 10.4 is derived from 10.3, not 10.2.
Nope. Here's how it works, usually (not saying this is what Apple does, but nearly everyone else does this, so ...). You've got one master codebase, called the "trunk." Everyone works with that. When it's time to start working toward a release candidate, you copy off the code base and create what's called a "branch."
Changes to the trunk are rarely back-ported to the branch (it usually depends upon whether they are bug fixes or new features; bug fixes, often are back-ported if they aren't risky; new features almost never); any changes to the branch which are relevent to the trunk *are* ported to the trunk (since most of them are bug fixes, and the rest are probably new features whose loss might be noticed in the next release).
The branch keeps being used by one team that is working on, let's say, Tiger, right up through the release and during maintenance (10.4.1, 10.4.2, 10.4.3, etc. are all from the branch, not from the trunk), while another team keeps working on the trunk until the time they branch (10.5 Alpha) the next release (let's say Leopard). When the newer branch hits release, one of two things happen: either the team that did the development on the new branch continues doing maintenance (10.5.1, 10.5.2, 10.5.3), or the group that was doing maintenance on the earlier release does maintenance on the new branch and the folks who designed the new branch go back to work on the trunk until it's time to branch again (10.6, let's call it Lion). Both methods have their advantages and disadvantages.
I'm guess this it what is meant by "Apple has two teams working on OS X." Two teams, but only one code base trunk. And thus 10.4 is derived from 10.3, not 10.2.
Warbrain
Jun 22, 05:42 PM
I'm confident that you will not see any computers running both Mac OS and iOS. Apple has made it pretty clear that they are two different lines (you may think the iPad blurs that line but it is still explicitly iOS and doesn't eat into the Mac usage as much as you'd think).
Could you see the two operating systems merge one day? Possibly, but also doubtful.
Could you see the two operating systems merge one day? Possibly, but also doubtful.
iMeowbot
Nov 29, 03:11 PM
According to Bob Cringley:
"�The USB port is clearly intended for an Apple iSight camera, a webcam to go with your HDTV."
Cringely comes up with some interesting thoughts, I'll say that :) There are much more mundane possibilities, like a keyboard to facilitate content purchases or iPod connectivity.
"�The USB port is clearly intended for an Apple iSight camera, a webcam to go with your HDTV."
Cringely comes up with some interesting thoughts, I'll say that :) There are much more mundane possibilities, like a keyboard to facilitate content purchases or iPod connectivity.
Dunepilot
Sep 6, 10:16 AM
The Superdrive option in the base model has gone.
Earth to Apple: a Combo drive in 2002 was state of the art. A Combo drive in 2004 was a reasonably priced alternative to a DVD burner. A Combo drive in 2005 was an acceptable means of marketing differentiation. A Combo drive in 2006 (particularly with no option to buy a DVD burner) is an embarrassment...
There's some truth in this. Apple's approach to optical drives has been haphazard for some time now.
Earth to Apple: a Combo drive in 2002 was state of the art. A Combo drive in 2004 was a reasonably priced alternative to a DVD burner. A Combo drive in 2005 was an acceptable means of marketing differentiation. A Combo drive in 2006 (particularly with no option to buy a DVD burner) is an embarrassment...
There's some truth in this. Apple's approach to optical drives has been haphazard for some time now.
dernhelm
Nov 29, 07:53 PM
I'm glad that he confirmed this. Otherwise Macworld in January would be memorable for all the wrong reasons.
Mr. Jobs finished his keynote with the startling admission that there is nothing left: "That's all folks! We've got nothing else in development. See you in 2010."
:D
I'm tellin' ya! I'm in the wrong business. Forget all this deadline - get product out carp. Get in to journalism where all you need to do is restate the obvious with a few well-placed typos, and Bob's your uncle.
Ahhh! I'm blind!
:rolleyes:
Mr. Jobs finished his keynote with the startling admission that there is nothing left: "That's all folks! We've got nothing else in development. See you in 2010."
:D
I'm tellin' ya! I'm in the wrong business. Forget all this deadline - get product out carp. Get in to journalism where all you need to do is restate the obvious with a few well-placed typos, and Bob's your uncle.
Ahhh! I'm blind!
:rolleyes:
shawnce
Jul 20, 12:09 AM
So will there be any surprises at WWDC?
They weren't very clear...
If they told you it wouldn't be a surprise now would it? :D
They weren't very clear...
If they told you it wouldn't be a surprise now would it? :D
SciFrog
Mar 23, 12:50 PM
Got confused, makes sense :rolleyes:
odyssey924
Apr 13, 12:16 AM
Here's the deal...(and I just realized that the way this is written might make it look like I have earlier posts in this thread. I don't. I'm jumping in right here.)
The reason that I think pros fear "dumbed down" isn't so much because they want something that is difficult to use, but rather because sometimes making difficult things easy makes things that were previously easy difficult, or impossible.
So just this week I had to help somebody with an iMovie problem. There was a part where they had 3 overlapping audio tracks. Movie audio, voiceover, and music. Try as they might, and try as I might, we could not get the movie audio to actually go away -- even though we had set it's volume level to "0%."
Oh...and did I mention that they're on a white iBook? Fine machine, but a little slow. So I copy their iMovie stuff onto an external drive so we can look at it on my Core i7 iMac instead.
Except iMovie on my iMac won't recognize the project on an external drive. I know that supposedly iMovie is supposed to...but it won't work. So I have to copy the files onto my iMac, and then iMovie magically sees them...because they're in the spot that iMovie wants files to be in.
Well the only way to get the clips to work right that I could come up with, was to actually run all their clips through Quicktime 7 and just delete the audio track off them. Voila! No audio track for iMovie to play, when it's not supposed to.
My point is that I spent 30 minutes dinking around with the "Easy" iMovie to do what would have taken me 10 seconds to do in Final Cut. (Select audio. Delete.)
And that's pretty much my experience every time I get lulled into trying to run a quick project through iMovie. Everything seems to be going well, I'm even sort of enjoying myself (Don't tell anyone), then I hit a snag or a wall...bump up into some limitation of iMovie that there isn't a very good work-around to...and wish that I'd just used Final Cut to begin with.
So while I agree that there are those who want pro tools to be difficult simply for the sake of having a high barrier of entry...
...I also think there are a ton of us that are just afraid that the cost of these new and handy features will be that some of the things we rely on doing, especially things that are a little "hackish," will become difficult/impossible. In the name of simplicity.
It's like my iPhone. I love it to pieces, and I don't plan to have any other type of phone any time soon, but sometimes I wish for a few more advanced features...features that are available (Usually through third-party tools) on Android. Instead I'm stuck hoping and wishing and praying that Apple will implement them.
+1 here. Every time I've tried to use iMovie for a "quick" edit it always ends in disasters like this. In my case, I was trying to move some music around and time my edits with the music. It was really infuriating trying to do this in iMovie compared to how fast I could have done it in FCP. I guess we'll have wait till Apple posts more info or we get it in our hands to really tell if it can be run like the current FCP.
The reason that I think pros fear "dumbed down" isn't so much because they want something that is difficult to use, but rather because sometimes making difficult things easy makes things that were previously easy difficult, or impossible.
So just this week I had to help somebody with an iMovie problem. There was a part where they had 3 overlapping audio tracks. Movie audio, voiceover, and music. Try as they might, and try as I might, we could not get the movie audio to actually go away -- even though we had set it's volume level to "0%."
Oh...and did I mention that they're on a white iBook? Fine machine, but a little slow. So I copy their iMovie stuff onto an external drive so we can look at it on my Core i7 iMac instead.
Except iMovie on my iMac won't recognize the project on an external drive. I know that supposedly iMovie is supposed to...but it won't work. So I have to copy the files onto my iMac, and then iMovie magically sees them...because they're in the spot that iMovie wants files to be in.
Well the only way to get the clips to work right that I could come up with, was to actually run all their clips through Quicktime 7 and just delete the audio track off them. Voila! No audio track for iMovie to play, when it's not supposed to.
My point is that I spent 30 minutes dinking around with the "Easy" iMovie to do what would have taken me 10 seconds to do in Final Cut. (Select audio. Delete.)
And that's pretty much my experience every time I get lulled into trying to run a quick project through iMovie. Everything seems to be going well, I'm even sort of enjoying myself (Don't tell anyone), then I hit a snag or a wall...bump up into some limitation of iMovie that there isn't a very good work-around to...and wish that I'd just used Final Cut to begin with.
So while I agree that there are those who want pro tools to be difficult simply for the sake of having a high barrier of entry...
...I also think there are a ton of us that are just afraid that the cost of these new and handy features will be that some of the things we rely on doing, especially things that are a little "hackish," will become difficult/impossible. In the name of simplicity.
It's like my iPhone. I love it to pieces, and I don't plan to have any other type of phone any time soon, but sometimes I wish for a few more advanced features...features that are available (Usually through third-party tools) on Android. Instead I'm stuck hoping and wishing and praying that Apple will implement them.
+1 here. Every time I've tried to use iMovie for a "quick" edit it always ends in disasters like this. In my case, I was trying to move some music around and time my edits with the music. It was really infuriating trying to do this in iMovie compared to how fast I could have done it in FCP. I guess we'll have wait till Apple posts more info or we get it in our hands to really tell if it can be run like the current FCP.
Eolian
Mar 28, 04:50 PM
I know this is venturing into iOS territory, but the single feature that would drive Classic well into the future for me is AirPlay. No other touchscreen BS; keep it rugged, keep it click wheel, just 160+GB of your fixed and lovingly maintained library, in your hand, poised to beam to the big stereo.
Yeah.
Yeah.
alfagta
Apr 1, 04:50 PM
Basically. Now they just need to polish what they gave us. It's honestly a lot though. I wouldn't feel ripped off for them charging money for it.
Almost all of the Applications have been enhanced, autosave, Launchpad, Mission Control, Versions, resume, Multitouch gestures, full screen apps and the Mac App Store.
You feel like it�s a new experience? So much better?
Almost all of the Applications have been enhanced, autosave, Launchpad, Mission Control, Versions, resume, Multitouch gestures, full screen apps and the Mac App Store.
You feel like it�s a new experience? So much better?
carmenodie
Apr 3, 12:04 AM
Marketing geniuses :)
You got that right.
People also forget that Apple is, at its core, an engineering company.
I can't wait to get my ipad 2 64 gig only . I'll get the wifi because I ain't paying no body for tethering and I'm too chicken to jailbreak my iphone 4.
You got that right.
People also forget that Apple is, at its core, an engineering company.
I can't wait to get my ipad 2 64 gig only . I'll get the wifi because I ain't paying no body for tethering and I'm too chicken to jailbreak my iphone 4.
BaldiMac
Sep 15, 08:51 AM
As far as the car comparisons go, I actually had an issue that is on point (as opposed to comparing a safety recall to a reception issue.)
I had a 2006 Acura TSX which got poor stereo reception because of an internal antenna. The official response was that it was "working as designed." They offered one year of satellite radio to anyone who complained about it.
Sounds a lot like Apple's response!
I had a 2006 Acura TSX which got poor stereo reception because of an internal antenna. The official response was that it was "working as designed." They offered one year of satellite radio to anyone who complained about it.
Sounds a lot like Apple's response!
alfagta
Apr 1, 04:16 PM
Faster? Not so sure. More stable? Definitely. All of my main bugs have been fixed aside from the full screen apps on dual screens.
So I guess we won�t see any new features� Apple is busy polishing what we�ve got now�:/
So I guess we won�t see any new features� Apple is busy polishing what we�ve got now�:/
RawBert
Apr 2, 07:29 PM
Very classy with the black theme and piano music. Loved it.
bmustaf
Sep 14, 09:29 AM
I love my iPhone 4, I tend to really love the way Apple does business, but I am not naive, either. I am glad CR is sticking to their principles & original statement and in doing so, holding Apple's feet to the fire however they can.
Let's be very clear - Apple can and will do whatever is most expedient for it. Not necessarily a bad thing because in a perfect market economy consumer preference will find what is good for the consumer to be good for Apple - but I think it's pretty clear that "academic" view of it doesn't always translate into reality.
So, just like the people who threw fits when Apple dropped the price of the iPhone original based on volume sustained by high-price-paying early adopters and got Steve to at least offer some small concession of $100 gift cards to his own store, people/organizations need to keep Apple accountable.
If everyone/every organization falls in line to what Apple tells us we must think/accept, the tail is wagging the dog and the theory of the free market falls apart - let alone the practice.
Written on my MBP, syncing my iPhone 4, my iPad, my iPhone 3GS, and my Magic Mouse right before I got in to my car with a neat little Apple sticker on the back. Just like I love my government, I also fear it. I love my Apple, Inc, but I also know they'll screw me as soon as it becomes convenient for them.
Let's be very clear - Apple can and will do whatever is most expedient for it. Not necessarily a bad thing because in a perfect market economy consumer preference will find what is good for the consumer to be good for Apple - but I think it's pretty clear that "academic" view of it doesn't always translate into reality.
So, just like the people who threw fits when Apple dropped the price of the iPhone original based on volume sustained by high-price-paying early adopters and got Steve to at least offer some small concession of $100 gift cards to his own store, people/organizations need to keep Apple accountable.
If everyone/every organization falls in line to what Apple tells us we must think/accept, the tail is wagging the dog and the theory of the free market falls apart - let alone the practice.
Written on my MBP, syncing my iPhone 4, my iPad, my iPhone 3GS, and my Magic Mouse right before I got in to my car with a neat little Apple sticker on the back. Just like I love my government, I also fear it. I love my Apple, Inc, but I also know they'll screw me as soon as it becomes convenient for them.
