By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Adinnieken on 18 June 2012
Edit Thread
fillet said:
Adinnieken said:

As I tried to reexplain elsewhere, the issue is in the architecture of the console itself, not in the actual available bandwidth of USB2.

Saying the bandwidth is an issue is an easy explanation.  It requires a lot less time in explaining.  The real issue is in that an Xbox 360 may have multiple peripherals or thumb drives connected to the console, because these may require a high degree of bandwidth themselves does not have the bandwidth available for full resolution RGB video.  So in order to compensate, and assure that the available bandwidth would be there regardless of the circumstances, they reduced the RGB resolution. 


Except that isn't the case, the USB port on the rear which Kinect must be connected to is not part of a hub, it has the full bandwidth USB2.0 has to offer. The front 2 ports share.

I don't really disagree with most of what you say, you obviously know a thing or two and a fair bit more than me but I believe the real issue is just the amount of processing going on, from capturing image data -> processing -> showing results and this isn't really acceptable for a peripheral that should have been designed to accomodate the obvious long latencies in the chain.

 

I appreciate your comments though genuinely, and my apologies for being heated and a little rude.

Nevermind...  

Very old data is very old.

Originally the IR camera was at 320x240, but that resolution got increased, not decreased.  Nor was the RGB video ever decreased.

I recalled the original article, from EuroGamer, and the refuting of it, but I don't believe I read a more thorough follow-up on it until today.

http://www.statepress.com/2011/01/25/microsoft-rumored-kinect-update-already-happened/