Jump to content

marcnet

VIP's
  • Posts

    267
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by marcnet

  1. You could use HIMDRenderer to convert the omg to a WAV file (lossless conversion) and then use whatever to convert the WAV into WMA
  2. Isn't more that trying to help people is the whole point of this forum / subforum?
  3. You can now with version 0.5. Ive added functionality to control the playing of the NetMD device and record tracks via the soundcard of your PC. Could you repeat the process and then use the bug reporter to send me a log file. All you need to do is fill in the email and comment fields. The log file is sent automatically.
  4. I have released version 0.5 of HIMDRenderer. It was going to be 1.00, but I decided that because of the large amount of additional features, I'll keep it an alpha/beta version. Okay... change log: ===== HIMDRenderer Changes====== * Fixed memory leaks. * Fixed bug in silence detection. * Fixed crashing after first file in batch mode * Fixed bug in bug reported that caused reports to become corrupted occasionally * Improved error messages (now have codes too!) * All logging is written to a single set of log files within the program folder. These logs are sent automatically when reporting a bug. * Improved desciptions on FLAC compression options * Now renders files silently. There is an advanced option to go back to "noisy" conversion ===== HIMDRenderer Additions====== * Added output directory to batch mode * Added silence trimming (cuy start & end silence) - NOT FULLY TESTED - USE WITH CAUTION! * Added ID3 tagging on mp3,flac and ogg files * Added new output file type - OMA. This is mostly useful for AT3 files. OMA/OMG files are simply copied when used with OMA/OMG files from the PC * Support for getting audio data direct from HIMD. *THIS ONLY WORKS FOR AUDIO THAT ORIGINATED FROM THE PC* also * THIS HAS NOT BEEN FULLY TESTED - USE WITH CAUTION* * Added ability to convert .at3 files into the supported file types - including OMA * Added HIMDLister. Just press the "MD Listing" button to access it. This also supports NetMD discs and NetMD devices * Added a NetMD recorder. Access this via "MD Recorder" button. Simply select the tracks to record, select the sound-card input, choose an output directory and hit "record" -- *THIS WILL NOT SHOW TRACKS FROM HI-MD DISCS* ===================== Download: http://www.marcnetsystem.co.uk/himdrenderer050.zip This zip includes ALL dlls required - including libmmd.dll ======================= Please note: Most of the new features have been tested by myself - but there may (probably) be something I missed. Please report any bugs using the bug reporter, or by posting here. Ill investiage ASAP Oh, and I can no longer test OMG files as I have none. The PC that had my OMG collection died, so I can only support OMA files from now on. The functionality to convert OMG files is stilll there- just dont expect me to fix any processing bugs when dealing with these type of files As for a guide to using all this new stuff.... well... You could either 1) Write one (I prefer this option ) 2) Wait for me to start & finish one.
  5. If the omg's are still on your PC then my HIMDRenderer might be able to convert them to mp3 or .wav. Wav is better because you avoid re-encoding. http://www.marcnetsystem.co.uk/himd/
  6. WAV files have a limit of 4GB (or is it 2GB). The file can be bigger, but most programs will get the size of the WAV data by reading the header of the WAV file. The length within this header is stored in 32 bits. The max value that 32 bits can store is 4GB You could use himdrenderer to convert to flac. I think FLAC files support > 4GB
  7. Id thought that you might like to add the following information to your info (some of which you already have, but I have repeated to make the rest of this make sense): First of the initial values/calculations: Track start pos = [Block List value at offsets 8 & 9] Track End pos = [Block List value at offsets 0xa & 0xb] End Info value = [Block List value at offsets 0xc & 0xd] [/code] NB: Dont multiply the start and end pos values by 0x4000 yet.... Okay, now this part is codec specific. I reference the codecs by the lowest 16 bits (eg: 0x2807 for LPCM). The block waste and factor values are in decimal [code] For 0x2030: Block Waste = 256 Factor = 192 For 0x282e: Block waste = 216 Factor = 376 for 0x28b9 Block waste = 1504 Factor = 1488 for 0x2822 Block waste = 144 Factor = 280 For 0x2026 BLock waste = 272 Factor = 304 for 0x2018 Block waste = 256 Factor = 192 for 0x2807: BLock waste = 64 Factor = 64 Okay, pick your values from the above and stick them into this. Ive split the calculations up into seperate operations so it looks nicer in your web browser Length = [Track end pos] - [Track start pos] Length *= 16384 - [Block waste] Length += ( 1 + [End info value] ) * [Factor] [/code] And thats it. You now have a track length in bytes. At least, I hope you do - this part of my HIMDRenderer program is quite messy and needs tidying up. Ive basically taken my code and (hopefully accuratly) optimized it down to these calculations. Oh, and for you non-C programmers: += means take current left hand value and add it to the value at right hand side *= means take current left hand value and multiply it to the value at right hand side
  8. Use the 16 or so selection boxes to select what you want each track of the listing to contain. If you select a track in the actual track list then an example of what the track list will look like will be displayed at the bottom of the window. Remeber to select 'CRLF' for the last option you choose, otherwise all tracks will be on one line!
  9. Sure, stick a copy on your webiste. Ive no problem with that. Just make sure you still provide a link to my site.. I may be updating HIMDRenderer very soon....
  10. Its not 100% bit perfect, no. But its very close. The dlls used for the conversion dont allow more than 1 minute to be converted at a time. I get around this by converting in blocks of 1 minute. This, unfortunatly, creates small repeated sections in the resultant audio file. I use various algorithms to seek and remove the repeated bits. This last part may make the output file slightly different to the original There is no re-encoding / resamping / etc done in my software. Give it a go, its free! If the result dosnt work out then there's no loss.
  11. no. The data is decoded to PCM, yes, but my program supplies the mp3/ogg/flac/whatever DLL with the PCM data as it gets it. There is no saving of wav file first. Whatever the OMA decoder returns get input directly into the mp3/ogg/flac/whatever DLL
  12. 1) DRM does stand for D(igital)R(ights)M(anagement) 2) If a file/song won't work in SonicStage (not recognized as stemming from that PC) then HiMDRenderer won't be able to convert it. 3) HiMDRenderer was (and still is) intended for converting imported recordings to wav. Especially uploaded digital recordings that cannot be converted by the Sony stuff. 4) The "cannot directly connect..." error means that the sony decoding DirectShow DLL is refusing to talk to any other DirectShow DLL's. It usually does this when it cannot or will not decode the input file. 5) There is no current way to restore OMA/OMG files if the DRM no longer exists or has never existed on your PC. 6) An upcoming version of my program will have HIMD and NetMD listing cabability, as well as the ability to play & record NetMD tracks via your PC soundcard (a bit like what that WinMD program can do). It will also have better error mesasages .
  13. No harm in giving himdrenderer a try.It works with both omg and oma. It wont wreck the oringal .omg/oma files (it dosnt even change them), its free, and if it outputs complete rubbish then you delete the .wav/.flac/.ogg/.mp3/.whatever and find another solutions There is a slight bug ive found with .omg files in that you have to restart himdrender after converting a .omg file, but thats about it.... (/me hints at a juicy 0.40 update coming soon.... and then runs awa.....
  14. I got the US Dualdisc imported via ebay Here is the offical NIN site description: http://www.nin.com/halo/19/index_DVD-A.html
  15. Yes. I have: Nine Inch Nails -- With Teeth Nine Inch Nails -- The downward Spiral Judas Priest -- Angel of retribution All of these are Dualdisc and all of them play ok and all of them rip ok via SonicStage and Cdex I have a Liteon DVD+-RW writer and a LG DVD+-RW /DVD-RAM writer. Both these drives have no problem using the NIN discs, but my LiteOn struggled ripping the Judas Priest Album. The LG had no problem ripping any of these discs. I also have a Yamaha CDC-675 CD Player and that plays these dualdiscs okay. My KiSS DP-500 player has no problem reading the DVD side of these discs (The Judas Priest is just a making of while the NIN ones are a 5.1 mix of the music)
  16. If you still have the uploaded OMA files on your PC then you can try SonicStage again. Failing that, try my program HIMDRenderer. Informatiom about it is here: http://forums.minidisc.org/index.php?showtopic=6087 If none of those work then your only option is to record from the HIMD to the PC realtime. There's a whole load of info about HIMD uploading via USB, and realtime recording here: http://forums.minidisc.org/index.php?showtopic=6330
  17. All the encryption is done on the PC so a program that would transfer WAV/OGG/Mp3/FLAC whatever would need to have access to the functionality that encrypts and converts those files into OMA. As far as I can see all of this handling is done via unknown COM objects.
  18. Hmmm. I dont know much about the Sony HD players (I dont even have one), so I couldnt tell you if audio upload (from device to PC) is supported by the hardware or not. It could have the same restrictions as NetMD. The first thing I would do is to create a dummy version of the DLL that logs all calls to all functions before passing the call to the real (renamed) DLL. Also, I would actually need one of these devices in order to start investigation & development.
  19. It turns out that all the track data is in the trkidx02 file ... not the trkidx01 file. For some reason HIMDLister is not using the 02 file. I think it has something to do with the timestamps on both the 01 and 02 files being the same. But if I force himdlister to open the 02 file, all tracks are listed as usual
  20. Interesting..... Could you zip up all your hma files from the offending disc (except the really big one) and either put them on a http server for me to download or PM them to me via this forum. It might also be useful to include a small text file detailing what the tracks are (name, length, format, etc) I am currently working on a new version of HIMDRenderer which incorporates the functionality of HIMDLister, so any information on this "new" format of hma file would be most useful. Thanks.
  21. How about adding the following test to the listening tests & frequency response graphs: Take the 256kbps MP3 and convert it to a .wav using winamp, foobar, LAME etc. Then convert the .wav to a HI-SP 256kbps ATRAC and a 132kbps ATRAC.
  22. FLAC support came into HIMDRenderer like this (and this also describes my entire FLAC usage): I had never heard of FLAC before. Someone wanted this file format supported. I used google and got the SDK. I implemented FLAC support using the SDK. I tested a few output files with winamp. It worked. The end. I also have no idea what the FLAC options in HIMDRenderer mean. I just copied their description from the related SDK function. Basically The FLAC options in HIMDRenderer directly set the related FLAC option in the SDK. I have no idea how to translate user-friendly options to the options the SDK gives me. Any suggestions?
  23. To add to my comment. It will be very difficult to recover the audio data from a .HMA file if the tracks were recorded (ie: not downloaded via SonicStage). This is because the encryption keys that are on your PC are different to the ones the HIMD device used. So even if you did stick the .HMA data into a OMA file, it wont play or convert because the sony directshow drivers wont recognize the DRM keys from the .HMA file.
  24. Strange that flac bug thing... Ill take a look as soon as I get the bits for my new PC and have set it up (Current PC died)
  25. Just a side note: When uploading recorded tracks to the PC SonicStage does the following: 1) Decrypts the data on the HI-MD disc 2) Creates a brand new set of encryption keys 3) Re-encrypts the decrypted track data using the new keys 4) Stores the new re-encrypted track data in the OMA and sticks these new keys in its DRM database So when uploading a recorded track, the data on the HIMD disc will be completly different to the resultant OMA file that SonicStage creates. This is due to the re-encryption described above.
×
×
  • Create New...