Jo2003
commented
7 months ago Hi jounii!
I think all netmd implementations have their source in the linux_netmd project. This is the base of the type script implementation and the go lang implementation as well. There are many forks, but almost nothing new finds its way back into the linux_netmd project. I based my work on the original linux_netmd project, the changed netmd sources of the Platinum MD-, and the webmd project. Since I'm more a C++ programmer than a plain C programmer I started the C++ library. I added the MD header handling and the gapless transfer (UTOC split) to this library. This library is used in NetMD Wizard. The handling is rather easy.
To get some more important information from the log, set the log level to "debug" in the program settings. After that you'll find the raw packet transfer information in the log, which might really help.
Furthermore: These devices are old and use the USB 1.1 standard. You might have issues due to compatibility issues of your Mac Book with the NetMD device. You can try to use a cheap USB2 hub between the Mac Book and the 980 flagship. This helped me more than once.
Best regards, Jörg
jounii
I have Sony MDS-JB980 (European model) and connected to MacBook Pro 2019 (macOS Monterey). The NetMD seems to work only partially. With the different apps available now the NetMD device is detected correctly and type shown correctly. The basic functions seem to work, you can play/stop, edit the disc title. Even erase the disc properly.
However as soon you try to send audio (SP mode, 16-bit/44kHz wav) the device shows "CONNECT" and then goes back to "Net MD" in it's display. The different apps we have behave slightly different on the error handing. Sorry for logs from NetMD Wizard, but by looks of it, it is using the netmd++. I have tried with platinum-md and webmd.pro implementations as well and well debug the code more with those what is going on. The golang implementation I have yet to try.
Trying to get to bottom of this, as it seems it almost works.
Anything to understand a bit on the NetMD protocol? I understand the implementations have a bit differences, but they all seem to fail with this particular case, so there is something going on now.
The webmd.pro especially is a bit problem on error handling as it hangs the deck in the "CONNECT" state (doesn't even allow to turn-off the device without pulling power plug). You can get it recovered, but seems it doesn't return gracefully. platinum-md has some re-try system and it re-tries and finally returns gracefully. But I suppose this is just the UI apps failure in using the underlaying netmd libs.
The NetMD Wizard gives follow log which I traced back to somewhere in https://github.com/Jo2003/netmd_plusplus/blob/b2f1d15cf32d17d197d74ababefe10a3506236bb/src/CNetMdSecure.cpp#L1010 :
I'm professional programmer, so no problem discussing in low level details. Already thinking about making own MD tool for my own purposes, but trying to figure out what is the issue with these libs now. As fallback solution I probably would make app that just realtime records audio as gapless and modifies the TOC afterwards as TOC editing seems to work. I'm figuring out app for easier mass-MD duplication.
Thanks already. I'll continue with my investigation later.