CD+G Karaoke On Macbook Pro

Discussion in 'Mac Apps and Mac App Store' started by dataset, Dec 29, 2007.

  1. dataset macrumors member

    Jun 27, 2007
    La Mirada, California, United States Of America
    Hello everyone!
    I've ran into a problem while trying to use CD+G karaoke cds on my macbook pro. They basically cant be used by anything on my MacBook!

    When I insert the CD+G iTunes starts up automatically and locks up so I have to force quit that. Next I Finder sees two Cds, the CD+G with the name and another empty cd named "Untitled". I am able to browse the first CD and see all the .aiff files. I've downloaded programs that said they could read the files such as kJams Lite and iStar but neither have worked.

    I know its not the CDs because a PC can read them fine. I want my Karaoke! :p Thanks anyone who can help!
  2. iynque macrumors newbie

    Nov 6, 2006
    You must have a CD+G capable drive. ...and the Macbook's drive is not.
  3. davecotter macrumors newbie

    Sep 13, 2007
    You should post your question to the kJams Forums.

    There is a "bug" in the MacOS such that if you insert a CD which mounts two volumes (and some karaoke discs do that) then it is impossible to dismount the disc and you must restart to get it out (hold the mouse button down after the "chome" sound, until it ejects).

    The only MacBook drives that support CD+G are the "HL-DT-ST" drives, but they are very rare. All others do NOT support CD+G. This is due to Apple's driver ONLY supporting "native" CD+G drives (most are not). On Windows, the karaoke vendors have written their OWN drivers that can extract and write CD+G info even on drives which DO NOT support CD+G "natively", that's why some say "it works on windows but not on mac".

    Sadly, you must buy a separate drive (they're cheap) specially for CD+G on the mac. see:
  4. karoke macrumors newbie

    Jul 28, 2010
    Oh I get it. Maybe that's the reason why I am not able to use my cd drive for karaoke too. It hangs up on me as well. I thought it has something to do with my macbook but it turns out that it's a compatibility issue. Thanks for the heads up because this is really helpful. nice one pal!

Share This Page