Recommended Posts

Waiting for you to turn off the system before it downloads and installs the update is to make sure the user doesn't try to do something that could mess with it.  The only downside is that it doesn't restart on it's own after but waits for you to.  That could be to make sure someone is actually home and not away.  What if you don't have it set to go into standby on it's own after a set period of time being idle?  Then it would stay on till you got home, don't think anyone want's that.  Of course I'm sure they'll update the update process itself so we'll see how it is later on.

I turned my Xbox One off (using "Instant On" mode) a few minutes ago. I can hear the hard drive working. So I'm guessing it's downloading the update? :huh:

 

When I first tried instant On, it took whole minutes for the Xbox to stop making any noise, disk/fan etc.

I completely understand why the system needs to be reboot but they could have made it better.

If some Joe user didn't know about this update and was using instant on, won't he be left clueless why his Xbox doesn't respond to Xbox On anymore?

They could have

- Download the update in the background and go back to "sleep" (instant on) state.

- When user wakes it up the next time, prompt for update, install it, reboot and done!

The only logical way I can see this being possible.

 

MS don goof.

Now if they can just get the "Xbox On" command to work properly, like the rest of the commands... it's like a 25% success rate, and like the mic is too low to pick up the command, unless you get really close to the Kinect, I have verified the issue with the console using 2 different Kinects.

Now if they can just get the "Xbox On" command to work properly, like the rest of the commands... it's like a 25% success rate, and like the mic is too low to pick up the command, unless you get really close to the Kinect, I have verified the issue with the console using 2 different Kinects.

I see this mentioned, but it might not be that the command doesn't work, there could be other reasons:

1. Mic needs to be calibrated again with a louder volume set to your speakers for the calibration

2. Maybe there is a placement issue.

So I would highly suggest anyone that is having the problem you mentioned to try recalibrating and crank that sound. You don't need to blow up your speakers, but I can verify that having that volume too low during calibration results in the mic not picking up commands nearly as well and requiring you to be fairly close.

If it fails to improve at all after that, then maybe its a defective Kinect.

I see this mentioned, but it might not be that the command doesn't work, there could be other reasons:

1. Mic needs to be calibrated again with a louder volume set to your speakers for the calibration

2. Maybe there is a placement issue.

So I would highly suggest anyone that is having the problem you mentioned to try recalibrating and crank that sound. You don't need to blow up your speakers, but I can verify that having that volume too low during calibration results in the mic not picking up commands nearly as well and requiring you to be fairly close.

If it fails to improve at all after that, then maybe its a defective Kinect.

 

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

It can't be a problem with the system in low power because not everyone is having your problem. I am not having your problem. That's why I suggested that something might be faulty.

As far as it not mattering since the room is quiet, I don't think that is true. I think the calibration actually adjusts how sensitive the mic is, in order to say work farther away or while there are other sounds in the room.

So if you have calibrated and it didn't fix anything, complain to MS and see what they say. Anyone having this problem should tell them about it because it shouldn't be happening.

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

 

 

 

 

 

I know exactly what you're talking about.

 

Same issues.. Saying "xbox on" after it's been off all night doesn't get recognized easy enough.

 

I've repeatedly had to say it 3 or 4 times at some points for it to actually hear me. Usually after getting right in front of it for it to hear me.

 

Seems to me it isn't hearing the command effeciently enough after being in the standby Instant On mode overnight as it does when you are actively using it. If you actively use the voice commnads, and even turn it off and back on a minute later, it seems to repsond well enough there. But overnight, it doesn't want to hear you in a dead silent room in the morning.  Like it's in too deep a sleep mode.

I maybe imagining it but Forza 5 doesn't play as smoothly since the update, anyone else notice this, am in the UK?

 

EDIT

 

I fixed this by getting the X1 to redetect the TV and set it to HDMI rather than HDMI(Auto) then changing the resolution from 640 to 1080P.

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

Have you tried "Yo... Xbox On". Or something like that? Sort of waking it up, ready to listen.

 

Does it work if you say it loud enough?

Have you tried "Yo... Xbox On". Or something like that? Sort of waking it up, ready to listen.

 

Does it work if you say it loud enough?

 

 

Doesn't really matter how loud you say it, it only seems to work for me if I get like real close to the sensor 2-4 feet away, then I can say it normal or loud. If I say it normal or loud from 8 feet, it doesn't wake.

Well there has to be some variable that is different for those having the problem and those that are not.

Maybe its the range. My couch is 6 feet away and I can get the X1 to turn on with a normal voice whether that is from sitting overnight or after its been on during the day.

I'll try it from say 8 feet away and see if it is unable to pick me up like xendrome has run into.

Booting from cold start now definitely feels faster for me. I don't have the Instant On feature active as my One is plugged into a plugboard with other stuff that gets switched off at night, I don't turn the console off anyway unless I want it fully off, if I'm in the middle of something I leave it on :)

I completely understand why the system needs to be reboot but they could have made it better.

If some Joe user didn't know about this update and was using instant on, won't he be left clueless why his Xbox doesn't respond to Xbox On anymore?

They could have

- Download the update in the background and go back to "sleep" (instant on) state.

- When user wakes it up the next time, prompt for update, install it, reboot and done!

 

Dude, I knew about the update and I still forgot why my Kinect wasn't responding. Then it clicked afterwards, but whatever, hopefully they smooth out these things.

Booting from cold start now definitely feels faster for me. I don't have the Instant On feature active as my One is plugged into a plugboard with other stuff that gets switched off at night, I don't turn the console off anyway unless I want it fully off, if I'm in the middle of something I leave it on :)

I can second your observation.

I did a quick test and my cold boot times went from 30 seconds to 21 seconds. So they did something to cut those times.

That's good news, I bet they'll make it even faster with a few more updates as they optimize it more and more.  I really want to see what benefits come to the games.

Just had the Kinect replaced today, the original one died, (Kinect DIsconnected error, another issue many people are having) Microsoft FedEx'ed me a new one, it works, but same issue with "Xbox On" Command.

 

1: Calibrated 10+ times on old Kinect and 3-4 times on new Kinect

 

2:Placement has been in front of the TV just below it, and on-top of it, with a Kinect Mount for the XBox one, and it is direclty in front of user 6-7 feet away. Doesn't matter if you are 6-7 feet or 10+ feet away when you say the command, only seems to work if you are standing right in front of it, 2-3 feet away.

 

I've re-calibrated it with sound Loud, and REALLY loud, shaking the room, 5.1 surround, and no difference. Plus, room is TOTALLY quiet when I say "Xbox On" so it shouldn't matter. And can't be a defective Kinect, since this is a brand new one. I think it's a problem with their system in low-power mode not powering the Kinect Mic enough to pick up the command while it is in this state. Since all commands when the system is on work fine, even over really LOUD TV.

Off topic- but which mount did you pick up?  there is only 1 on amazon and the only review says it wont work with the new kinect

 

http://www.amazon.com/LETECK-Xbox-One-Kinect-Camera-mount/dp/B00GU0H5X4/ref=sr_1_1?s=videogames&ie=UTF8&qid=1386874002&sr=1-1&keywords=kinect+tv+mount

This topic is now closed to further replies.
  • Posts

    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
    • Normally, I admit when a title is clickbait (unfortunately, it's become somewhat necessary to compete against AI-dominated news sections today), but in this case, all supported versions is implied and doesn't need to be spelled out in the title. Of course, I'm covering a Patch Tuesday update bug that is only available to supported Windows SKUs. All our coverage relates to supported Windows software and SKUs only unless we expressly state that it's "unsupported", "unofficial", or "third-party". I'm sorry, but supported/official SKUs don't need to be spelled out as such in every Neowin headline.
    • ALL versions or ALL SUPPORTED versions? Neowin does it again.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      595
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!