Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why does apple kill everything. :D I mean 99% of the things they release owns everything mobile me and atv were the only fails

Mobileme is anything but a fail. If you are a very Mac-based person (owning several computers and iDevices), once you have it, you can't go back.
 
Mobileme is anything but a fail. If you are a very Mac-based person (owning several computers and iDevices), once you have it, you can't go back.

Too true. With MobileMe, I get push email and calendar to my iPhone for my personal stuff, in addition to the Exchange Server push for my work email.

Keeping my calendar and contacts automatically synced between my iPhone, iPad, desktop and laptop is invaluable, and the cloud storage has saved me on a few occasions.

All in all, it's well worth $99 a year.
 
You're joking, right? (Whatever "routed" means, both of the things the poster explicitly mentioned significantly predate USB, and most of things he didn't probably do, too.)


I'm not joking. Are you getting defensive? It's an honest question.

USB 2.0 > RCA cables exist, so there's no need for a dongle or dock connector.

"Routed" means Dock connector pins all lead to a USB plug on the other end anyway. Pretty simple stuff. Are there any "dock connector to line out" cables? Because it seems any line out scenario includes a dongle or dock regardless of the dock connector's presence.

So, in summary, there's no need for the dock connector, but I really don't even care. I just questioned the validity of the statement.
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
I really don't get apple in the video space... sure i can see video content but as far as face time goes why didn't they work with Cisco (Who owns ios and iphone trademarks) to get iphone to support the open Telepresence video standards and fantastic Codec's they have in their arsenal of IP.

This would help blur the lines of business & consumer further and open up interop for other platforms such as Cisco's CIUS Android based Video Conferencing tablet.

see http://www.eweek.com/c/a/VOIP-and-T...d-TelePresence-with-Protocol-New-Apps-540055/
 
I really don't get apple in the video space... sure i can see video content but as far as face time goes why didn't they work with Cisco (Who owns ios and iphone trademarks) to get iphone to support the open Telepresence video standards and fantastic Codec's they have in their arsenal of IP.

This would help blur the lines of business & consumer further and open up interop for other platforms such as Cisco's CIUS Android based Video Conferencing tablet.

see http://www.eweek.com/c/a/VOIP-and-T...d-TelePresence-with-Protocol-New-Apps-540055/

They've been there a long time, and have their own IP deeply entrenched in the space, including the fact that the QuickTime file format was used as the basis for the MPEG-4 spec. More here.

They are using that experience, plus their iChat experience, in FaceTime. I see FaceTime as Apple trying to do what it often does, and likes to do: take technology that exists and put it together in a form that is easy for people to use. (Using a name that had to buy, rent, or...ahem...borrow, from someone else :D ) Whether or not FaceTime will be adopted by others is yet to be seen. We'll see, but I don't find it odd at all.
 
You did actually read the product description that mentions this is a line in, not an audio/video line out, right?

I'm not joking. Are you getting defensive? It's an honest question.

USB 2.0 > RCA cables exist, so there's no need for a dongle or dock connector.

"Routed" means Dock connector pins all lead to a USB plug on the other end anyway. Pretty simple stuff. Are there any "dock connector to line out" cables? Because it seems any line out scenario includes a dongle or dock regardless of the dock connector's presence.

So, in summary, there's no need for the dock connector, but I really don't even care. I just questioned the validity of the statement.
 
As an Amazon Associate, MacRumors earns a commission from qualifying purchases made through links in this post.
H.264/SVC is not based on wavelet compression. The proposals based on wavelet compression were ruled out during the early standardization period. H.264/SVC is a regular block-based (layered) video codec.
Ok, my bad. Haven't followed codec development closely enough in recent years. I guess that it's about time to include wavelet to h.264, so it might not take long before they introduce new version.
 
Bottleneck/Weakest ink

All of which could have been handled by standard USB...

Well, for one thing it IS USB on the other side. So no matter how many more pins the 30 pin connector has, the other end of the cable is still a standard USB port. It has to be converted to standard USB at some point along the cable!

EDIT: title should say "Weakest Link"
 
If this happen, I'll be really happy cause it shows that Apple still want to be in the high-end market. Kinda worried with what happening now (not that its bad or anything), I am wondering when we will see a new 27"/30" Apple Cinema Display.

I think ProRes has stated their in the high-end market for the future. Arri, one of the, if not the most used film camera company in Hollywood, is now recording straight to ProRes in their new Alexi digital film cameras. ProRes has been rated better than Avid's DNXHD format, which I haven't heard anything about in a while.

I would like to have more news about Final Cut Studio, especially in relation to mega-high-end workflows like RED 4.5Ks and would like more speed and native editing instead of NEEDing to go to ProRes, even though it is a really nice codec.

-Brian
 
4096 x 2304 resolution !!! Looks pretty awsome !!!

it will be requested by many many peoples to see it in public releases.:D

and it will also agree with Yvan256 that "A free, open CODEC offering better video quality at lower bitrates would be welcomed by all. If Apple could also push JPEG2000 at the same time, it would be a bonus."
I agree with this too that lower bitrates would be welcomed by most of the users if they found it in free or at a reasonable price.
 
I don't get it.

Apple is heavily invested in H.264, both as a prosumer and a leading proponent in the H.264 standards body. Why would it try to develop something to compete with H.264?

Technically, I understand that H.264 is not where it is supposed to be by now. But, if anything I would assume Apple would be helping and putting more resources into making it better.

Its like saying my right hand is not strong enough, let me try it with my left hand instead. You dont do that, you use your left hand to help with the right hand. .. ok, bad example, but you guys see the point?
 
Before we start making insane hypotheses here, l;et's recall some basic issues.

(a) Apple ALREADY has a video codec based on wavelets. It's called pixlet. It's been around for years. It was designed for video professionals who are editing and manipulating video --- ie the goal is to allow for rapid decode and random access, NOT to provide best quality viewing in the smallest file size.

If I had to guess, I would guess that hardmac (like everyone commenting on this thread) have got their wires crossed, that what Apple has in mind is some improvements to pixlet which will, no doubt, be of interest to the professional movie/TV world, and of zero relevance to the rest of us.

(b) Does it make any sense for Apple to devise a new proprietary video codec? Doing so is making a bet that Apple (with its team of maybe ten codec engineers) is smarter than the combined smarts of a hundred companies and a thousand universities spread across the world. This seems unlikely, and I am sure Apple know it. Even once they have designed such a codec, they then have to get chip implementations created (otherwise how does it run at low power on mobile devices) and doing so is not easy and not cheap. And at the end of the day, why? Is there a large market out there of people saying "You know, I really want to buy an iPhone, but I am disturbed by the fact that they don't use a proprietary video codec?".

h.264 is not ideal --- like most codecs, it was not designed with multiple CPUs in mind, and incorporates parts of the algorithm that are very hostile to multi-threading (every subsequent step depends on what went before). I think there is room in the world for one more round of the video codec improvement wheel, with the improvements most aggressively targeting ways to segment the work done into independent units that can be decoded on independent CPUs. But this sort of thing seems better done in universities than at Apple.

Sure, if the current attempt to define an h264 successor were to bog down in the sort of stupidity and bickering that made MPEG4 such a crappy standard, Apple might decide to go it alone; to base something off the framework proposal leaving out the most stupid thing people are trying to add. (What happened at MPEG4 was that every company that had ever thought of some hare-brained video compression idea insisted that their crap be stuck in the proposal or they wouldn't vote for the proposal as a whole, and so we got a huge mountain of crap built on top of an adequate framework.) But it seems way too early to start assuming things will turn out the MPEG4 way --- the fact that MPEG4 was abandoned as soon as the vastly superior h264 proposal was available (put together by vastly fewer people and companies) may have taught everyone involved a lesson.
 
4096 x 2304 resolution !!! Looks pretty awsome !!!

If Apple could also push JPEG2000 at the same time, it would be a bonus."

Uhh, Apple has had JPEG2000 since, god, ten years ago or more. It shipped as part of QuickTime ever since than. I ought to know ---I wrote the code (though I imagine it's been modified a bit since I left Apple some years ago).
It's free, is part of 10.6.4. I just downloaded a monster 117MB JPEG2 image that's 10,000 x50,000 pixels (!!!) and QT opened it and displayed (after a few seconds) just fine.

If JPEG2000 has not taken off, you can't blame Apple for that.
The first question I'd ask is: was it built into XP? Vista? Win 7?
How about the Linux distros (a minor factor to be sure) and the various mobile platforms (a big factor)?
I'm not sure what iPhone/iPad's JPEG2000 status is.

The next question is why the camera manufacturers avoid it.
I honestly have no answer to either of these questions.
 
Sure, if the current attempt to define an h264 successor were to bog down in the sort of stupidity and bickering that made MPEG4 such a crappy standard, Apple might decide to go it alone; to base something off the framework proposal leaving out the most stupid thing people are trying to add. (What happened at MPEG4 was that every company that had ever thought of some hare-brained video compression idea insisted that their crap be stuck in the proposal or they wouldn't vote for the proposal as a whole, and so we got a huge mountain of crap built on top of an adequate framework.) But it seems way too early to start assuming things will turn out the MPEG4 way --- the fact that MPEG4 was abandoned as soon as the vastly superior h264 proposal was available (put together by vastly fewer people and companies) may have taught everyone involved a lesson.

What are you talking about?

H.264 is part of the MPEG4 standard (part 10 to be exact)

the other MPEG4 4 video standard is part 2 which has many different profiles,one that's well known is ASP which is created by encorers like divx and xvid.
Other profiles of that standard have been used to create the hd-cam sr recording format,a high end recording format.

So your statement is confusing me a little
 
What are you talking about?

H.264 is part of the MPEG4 standard (part 10 to be exact)

the other MPEG4 4 video standard is part 2 which has many different profiles,one that's well known is ASP which is created by encorers like divx and xvid.
Other profiles of that standard have been used to create the hd-cam sr recording format,a high end recording format.

So your statement is confusing me a little

Oh god, do we have to go through this every time the discussion of h264 comes up?

H264 is a product of the ITU VCEG. MPEG is a product of the ISO/IEC MPEG--- different standards groups with different personnel, different ways of working, different mandates. You are aware, as a starting point, that there are, in fact, multiple different organizations in the world that call themselves standards bodies?

Why do you think it's called h264 (ie following h263 and h261) rather than MPEG5? You are aware, are you not, that it's technically rather different from MPEG4 (well the part of MPEG4 that refers to standard video, since MPEG4 contains about ten thousand different pieces) --- more different from MPEG4 than MPEG4 is from is from, say, MPEG2?

Let's not mince words here. The essence of what happened is that, two years after the godawful mess that is MPEG4 was finalized, it became clear that the ITU had produced a vastly superior codec. Face-saving was obviously necessary --- the large companies that had thrown so much manpower and so much stupidity at MPEG4 could hardly admit that the much smaller, much more interested in results rather than patent battles ITU group had produced something far superior --- and so we get h264 hustled into an appendix to the MPEG4 spec, creating the fiction that it's somehow an organic outgrowth of MPEG4 and the product of the dysfunctional ISO organization, whereas in fact it has nothing to do with them.

(And no, I did not work on either of these bodies. I'm just reporting the objective facts about what each achieved and the quality of the specs they created. Find a single engineer knowledgeable about this issue who disagrees with my assessment of the relative quality of these specs.)
 
Oh god, do we have to go through this every time the discussion of h264 comes up?

H264 is a product of the ITU VCEG. MPEG is a product of the ISO/IEC MPEG--- different standards groups with different personnel, different ways of working, different mandates. You are aware, as a starting point, that there are, in fact, multiple different organizations in the world that call themselves standards bodies?

Why do you think it's called h264 (ie following h263 and h261) rather than MPEG5? You are aware, are you not, that it's technically rather different from MPEG4 (well the part of MPEG4 that refers to standard video, since MPEG4 contains about ten thousand different pieces) --- more different from MPEG4 than MPEG4 is from is from, say, MPEG2?

Let's not mince words here. The essence of what happened is that, two years after the godawful mess that is MPEG4 was finalized, it became clear that the ITU had produced a vastly superior codec. Face-saving was obviously necessary --- the large companies that had thrown so much manpower and so much stupidity at MPEG4 could hardly admit that the much smaller, much more interested in results rather than patent battles ITU group had produced something far superior --- and so we get h264 hustled into an appendix to the MPEG4 spec, creating the fiction that it's somehow an organic outgrowth of MPEG4 and the product of the dysfunctional ISO organization, whereas in fact it has nothing to do with them.

(And no, I did not work on either of these bodies. I'm just reporting the objective facts about what each achieved and the quality of the specs they created. Find a single engineer knowledgeable about this issue who disagrees with my assessment of the relative quality of these specs.)



Actually, thats not entirely true. H.264 is the first project that both the standards bodies ITU and ISO have worked together on. It is the first time they have collaborated and therefore H.264 is formally referred to as H.264/AVC, the H.xxx part from ITU and the AVC for MPEG-4 Part 10 Advanced Video codec.
 
Actually, thats not entirely true. H.264 is the first project that both the standards bodies ITU and ISO have worked together on. It is the first time they have collaborated and therefore H.264 is formally referred to as H.264/AVC, the H.xxx part from ITU and the AVC for MPEG-4 Part 10 Advanced Video codec.

Sure sure. Look at the timeline of when the real work was done compared to when the two groups started "collaborating".
 
This good news. Let's be realistic the real uses for this codec. I can fit more porn, in better quality, on my hard drives. Thanks Apple.
 
Why do you think it's called h264 (ie following h263 and h261) rather than MPEG5? You are aware, are you not, that it's technically rather different from MPEG4 (well the part of MPEG4 that refers to standard video, since MPEG4 contains about ten thousand different pieces) --- more different from MPEG4 than MPEG4 is from is from, say, MPEG2?


You conveniently skipped H.262 which is the video standard of MPEG2 and what everyone refers to when they say "mpeg 2 video",so an ITU format in an mpeg standard is not a new thing.

So I would think H.264 is an evolution of what you call MPEG 2 video.


But I get what you're saying,it's just that ,when it comes to naming conventions,I don't care who developed what,if it's part of the MPEG4 standard,it's part of the standard.
 
Uhh, Apple has had JPEG2000 since, god, ten years ago or more. It shipped as part of QuickTime ever since than. I ought to know ---I wrote the code (though I imagine it's been modified a bit since I left Apple some years ago).
It's free, is part of 10.6.4. I just downloaded a monster 117MB JPEG2 image that's 10,000 x50,000 pixels (!!!) and QT opened it and displayed (after a few seconds) just fine.

If JPEG2000 has not taken off, you can't blame Apple for that.
The first question I'd ask is: was it built into XP? Vista? Win 7?
How about the Linux distros (a minor factor to be sure) and the various mobile platforms (a big factor)?
I'm not sure what iPhone/iPad's JPEG2000 status is.

The next question is why the camera manufacturers avoid it.
I honestly have no answer to either of these questions.
There is JasPer and other stuff for Linux. You're also referring to "free of charge" than "free to access the source code". Proprietary stuff doesn't spread fast, Apple understood that. Have a look at WebKit for example. (Yeah, KHTML fork, but anyways).
PNG however is free of licenses AND better then JPEG, that's why it's so widespread.
 
I would like to have more news about Final Cut Studio, especially in relation to mega-high-end workflows like RED 4.5Ks

As wonderful as RED 4.5k is, that is their "low end" resolution system. They have a 21 megapixel camera that can record at full resolution at 60 fps. While it is unlikely a consumer company will support much above 4K in the consumer world, which is about 4x HD, a pro editing solution should be able to deal with whatever resolution is economically achievable on the injest side and be able to process output to at least 4K if not higher for a "pro fee".

It is at the point where it is technically feasible for iPhone 5 owners to become 4K news reporters to capture content that can be transferred non-real-time to redistribution points for blogs, feeds, news services, and broadcasts. There needs to be a 4x bus speed increase at least for that "burst feature" and given local storage limits, it will reduce the probability of overheating. At least till iPhone 6.

Rocketman
 
Well, for one thing it IS USB on the other side. So no matter how many more pins the 30 pin connector has, the other end of the cable is still a standard USB port. It has to be converted to standard USB at some point along the cable!

EDIT: title should say "Weakest Link"

30pin connector pinout

It's nice to have apples dock connector, maybe inconvenient on the surface but it opens a lot of doors for accessory designers.

Plus with the popularity of iDevices everything is "compatible with iPod" "works with iphone" and so on. With electronics manufactures building ipod docks into just about everything...It's free advertising.

Call it greed if you want. I call it smart.
 
I guess that all video compression methods are and will be patented. Otherwise it would make no sense to invest in them.

That's not correct at all. It would be correct from the point of view of someone who wants to create and sell video codecs. But from the point of view of content providers, they would be happiest with _one_ top quality codec that can be freely implemented by everyone. They don't care about what money can be made with video codecs, there's much more money to be made selling or renting videos.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.