Am Mittwoch, den 11.07.2012, 19:12 -0700 schrieb Roberto Lionello: > I recorded a track on my MZ-RH910 in atrac3plus. I then uploaded it on > my machine with QHIMD. Since I know there isn't a codec for that > format yet, I went to a Windows machine with Sonicstage 4.3 and tried > to upload the file and convert it to wav format. It gives me an error > that it cannot save the file in wav format. This sounds like you used a really old version of QHiMDTransfer that did not clear the DRM tracking ID (called "Content ID") while uploading the file from HiMD to you hard disk. The .oma files created by QHiMDTransfer have always been completely unencrypted, but the Sony DRM system refuses some actions even on unencrypted files, if they contain a DRM tracking ID, but the DRM database does not contain any record for that ID. For the upload of a track recorded with the MZ-RH910, it sounds like you needed to use the unofficial "intoxicated" version of QHiMDTransfer floating around in the internet. I am surprised to hear that there is an intoxicated version based on a version that does not clear the DRM tracking ID. So maybe there is another problem. If you have a hex editor, search in the .oma file for "EA3" (with capital EA!), which should be followed by "01 00 60 FF FF". The 20 (0x14) bytes starting 12 (0x0C) bytes after the beginning of the "EA3" mark are the DRM tracking ID. Patch them to be all zero if they are not. > I tried also with HiMD Renderer and still can't do it. I put the file > uploaded with QHIMD and it cannot be converted. As far as I know, HiMD Renederer uses the Sony .ocx components to play back or convert files, so if the Sony DRM modules denies some operations, HiMD Renderer can't do that, too. > Does QHIMD taint the file and make the conversion impossible or is > there some other problem? Apart from the problem with old versions that didn't clear the DRM tracking ID, I don't know of any problems. If the ID already is zero, please send the headers of the offending .oma files to the list. The headers end 96 (0x60) bytes after the start of the "EA3" magic. Regards, Michael Karcher
Attachment:
signature.asc
Description: This is a digitally signed message part