Lips: Number One Hits Previews - Xbox 360

Lips: Number One Hits
  • Publisher: Microsoft
  • Genre:Music
  • Developer: iNiS
  • Release Date:Oct 20, 2009
  • # of Players:4 players
  • ESRB:T - Teen (Lyrics, Mild Cartoon Violence, Sexual Themes, Use of Tobacco)
  • Platforms:
Game Description: The latest installment in Microsoft's karaoke-style rhythm game features a collection of songs that have reached the number one spot on major music charts from around the world. Some of the featured songs include Coldplay's "Viva La Vida," Rihanna's "Disturbia," MC Hammer's "U Can't Touch This," Timbaland's "Apologize" featuring OneRepublic and Culture Club's "Karma Chameleon."
G4TV Rating
2 / 5
  • Avg User Rating
    (1 Rating)
    1 / 5
  • Rate This Game

Lips: Number One Hits Previews

Displaying 1–1 of 1 previews

Sort by: Filter by:
All Categories
  • Video Preview

    Lips: Number One Hits Interview

    We talk to Keiichi Yano, chief creative officer at iNiS, about Lips: Number One Hits, motion control, Zune Marketplace, and more.

    Posted: Oct 12, 2009 | 2,828 Views | 11:05

  • Lips: Number One Hits Interview

    Posted: October 12, 2009

    2,828 Views | 11:05

  • Lips Number One Hits E3 Trailer

    Posted: June 1, 2009

    134 Views | 01:11


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>