Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by asivery

  1. 9 minutes ago, BearBoy said:

    One of the results of the different containers/file types is that WMD doesn't seem to recognise the SP .aea files so you can't rip them from one MiniDisc and then copy them back to another without do some sort of file conversion. Unless I'm missing something obvious?

    No, you aren't missing anything obvious. NetMD doesn't support putting raw ATRAC1 back on the discs. However, if you would like to test it, here's the unreleased version of WMD, which does support that on some devices: https://testing.minidisc.wiki/b0824780-3c0c-11ed-b994-2c56dc399093/


    10 minutes ago, BearBoy said:

    The other thing we noticed was that when you rip LP2 tracks from a MiniDisc and then try to copy them over to another one, they get added to the new MD in reverse order.

    That is a bug I am aware of, I'll fix it as soon as possible. It's still not fixed in the testing version I linked above.

    • Like 1
  2. @BearBoy - Yes - there's a difference. ATRAC3 data is stored in WAV, because the RIFF container (the specification that WAV files follow) allow that to happen. For ATRAC1 I couldn't go with WAV, since ATRAC1 isn't supported by the RIFF container. Instead WMD downloads these files as AEA (an old format that was created by MD Editor I think). Sir68k - another developer of netmd-exploits managed to add the ATRAC1 specification to the matroska file format, and we'll probably also try to do the same with ATRAC3, so that the container format will be unified. I'll soon publish a patch to FFMPEG which patch the matroska demuxer there. AEA files are terrible because it's hard to identify them - they don't have a "magic number", unlike WAVs, so the sooner we switch from them the better.

    • Thanks 1
  3. I'm not sure - I haven't looked at the Windows side of things personally, since I use Linux and the libusb driver gets loaded there automatically (no Zadig or any tool like that required), but I don't think I could get the Sony driver to work with Web Minidisc unfortunately, or even if it were possible, I just don't think it would justify the amount of work required to do so unfortunately. The solution that could solve all the problems would be to make a custom driver that just modifies the libusb inf file to include all the NetMD devices - then you wouldn't need to reinstall Zadig for every device. I might look into that at some point.

  4. 1 minute ago, BearBoy said:

    Feel a bit bad for requesting something I've ended up not making much use of 😳 Well, although I've never really used it, I am sure lots of people are very grateful for your efforts 😀


    Don't worry about it - I got myself a Sony LAM for testing and ended up falling in love with the whole LAM series of devices. I have 3 now, so I use that functionality regularly 😆

    • Haha 2
  5. 9 minutes ago, BearBoy said:

    I can't say I have ever encountered any bugs, not that I can recall anyway. Both of the things I originally flagged as being nice to have (ALAC support and compatibility with Sony NetMD decks) have both been implemented, although I've stuck to using portable devices tbh.

    Yeah the Sony NetMD decks were a painful mess to implement 😆.


    11 minutes ago, BearBoy said:

    One thing that is a (very minor) inconvenience is having to re-install the drivers if I connect a different model of NetMD Walkman (e.g. if I change from using an MZ-N910 to an MZ-N920). Note sure if there is anything that could be done about this but it is only a minor issue and I generally just stick to using the same device.

    That's the problem with using Zadig, Web Minidisc can't do anything about it, sorry...


    21 minutes ago, BearBoy said:

    I'm afraid I can't help you with your MZ-R3 problem but it might be worth starting a thread asking for assistance. There are others on here who are much more clued up on the technical side of things than I am. Good luck!

    Thanks, I'll try that later.

  6. Hi! Thanks for the kind words, if you have any suggestions or bugs to report, please let me know :).


    I got into MD for the first time in 2016 thanks to the first Techmoan MD video ("Minidisc: An appreciation" I think it was called), when I got myself an MZ-R3, that died a few years later with error 40. Now I own 5 MZ-R3s - 1 working and 4 dead. If you know any fixes for that dreaded error 40, please let me know - I'd love to fix it one day.

    • Thanks 1
  7. Hello @kgallen!

    I personally recommend any of the Sony Type-S portables. They're the most reliable when it comes to maintaining a connection to Web Minidisc Pro. Type-R portables like the MZ-N1 and alike still sometimes drop the connection mid-transfer.

    Sony Type-S portables should also work best with Platinum, but I haven't tested it - they're just the most lax when it comes to following the restrictions imposed by the NetMD protocol.

    When it comes to downloading data off of MDs via Web Minidisc Pro, that functionality only works on Sony non-HiMD portables - with Type-S you can achieve ~5x real time speed when ripping SP (~10x LP2, ~20x LP4), with Type-R ~0.5x for standard SP. It's impossible on the decks and non-Sony devices for now.


    I myself use an MZ-N520 for pretty much everything and it's been very reliable, but I expect other Type-S portables to be the same.
    Also, Web Minidisc Pro can use a remote Sony encoder hosted by the Wiki, which might produce better ATRAC3 than even SonicStage.

  • Create New...