-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sharp IM-DR80-B / charge stand #41
Comments
@StudioErrilhl Does it work with SonicStage? If so, could you please share its VID and PID? |
@StudioErrilhl - make sure you hold the ENTER/-USB button on the stand until the display reads - - - USB - - -. |
I have this issue with the same unit. I followed the above advise and it kinda worked. Held the "Enter/-USB" button on the stand till it displayed "- - - USB - - -". Then clicked "connect" and it showed NetMD, clicked on that and it successfully loaded the TOC showing what was on the disc. Then it always immediately restarts the TOC read on the player, knocking it off the USB mode. I'm so close to having it work. I've repeated this over and over with different disc, holding the connections, pressing down on the unit in the stand trying to get it to stay in USB mode. It always knocks it out and goes back to the Crome web app not "seeing" the player. This is my only NetMD devise :( ........NEED.......TO.........RESIST.......EBAY!! |
had the same issue, I tried it with Platinum MD , it wasnt making this anymore... no idea whats causing it. |
This NetMD player has the USB connector on the charge stand, and it doesn't get found by the Web MiniDisc at all - just get a "no supported devices found". The same installation works fine with the sam USB cable on the Sony MZ-N910 (although this one has the USB connector directly on the player itself).
Not sure if this is an issue with drivers, or the USB connector on the device/charge stand, an issue with Web MiniDisc, but if someone have this player, and have gotten it to work, I would love to hear your solution.
The text was updated successfully, but these errors were encountered: