Jump to content

marcnet

VIP's
  • Posts

    267
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by marcnet

  1. The batch mode crash has been fixed in 1.00 beta 3
  2. I have just uploaded beta 3. This has the following fixes: 17/02/2008 - Fixed crash in "add files" in batch mode (again) 17/02/2008 - Fixed corrupt and/or repeated audio at the end of some file 17/02/2008 - Fixed crash in bug reporter 17/02/2008 - Fixed album titles in ID3 tags becoming truncated See first post for download link
  3. Okay, I managed to borrow of a vista laptop from my mate (jeez, he trusts me ) and I downloaded the release version of HIMDRenderer from my own web site, unzipped it and ran it. It ran with no crashes. I didn't do any conversion with it, since I dont a ) Have a sonicstage installer handy b ) Don't want to install Sonicstage on my mates laptop But... the WMA / OGG / LAME and FLAC dlls loaded with no problems. The unicode stuff must be working fine. I have no idea why your version of beta 2 crashes upon load. My mate does have a lot of the security stuff of vista disabled, since it pisses him off somewhat.... I don't know if vista security causes it to crash or not...it's not my laptop and I don't want to annoy him by messing with the laptops settings... One thing to try: Can you just try to extract beta 2 to a completly new, empty and seperate folder and run it from there... just to see if it still crashes. The only thing I can think of is that the configuration data of 0.54 is somehow corrupt in such a way that breaks 1.00 beta 2
  4. Unfortunatly, I don't have vista installed, nor do I have a copy of it. And for what it's worth, I really don't want to have to install it (bloatware anyone?) .I shall try and find a vista machine at work, or borrow my mates laptop or something, and find out why it crashes. Meanwhile, would it be possible to collect the crash report from windows (I don't know if it has a "save" option) and upload it here (zip/rar it if its quite big) Azureal: I shall investigate this when I have time. I take it you have submitted a bug report using the built-in bug report feature - this will help me track the problem down,
  5. I have just released beta 2. This fixes a few bugs that crashed beta 1. Please see my first post for details and download link
  6. Sorry, the Mac version isn't possible as my program uses some of the DLL's that Sonicstage installs. It also uses DirectShow (part of Direct X) in order use these DLL's - and of course, Direct X is a Windows only thing I also don't actually own a Mac
  7. Version 1.00 beta 1 of HIMDRenderer will now also write track numbers to the ID3 tag information on WMA,mp3, ogg and flac.
  8. Please try this new version: http://forums.minidisc.org/index.php?showtopic=20395 Thanks
  9. Helo. Yes. I've released a new version of HIMDRenderer. Please use & test and report any problems. Thanks. Changes and additions...IMPORTANT: THIS VERSION PROBABLY WON'T WORK WITH WIN98, WIN95 or WIN ME (see first change). Sorry, but these operating systems have limited support for unicode. * Unicode and codepage support allowing displaying of track names containing non-english characters. This change requires the "Arial Unicode MS" font to work properlly. HIMDRenderer will still work if you don't have this font, but non english characters may not be displayed correctly. Search google if you don't have it! * "MD Listing" can export track listings in UTF-8 or Unicode format (Output Encoding). It can also export in plain ASCII format, but this format cannot contain support for foerign characters (yet) * Support for opening .HMA files from harddisk. This has the same limited support / restrictions as if using the "Scan HIMD" function. * Support for non-wav/non-riff based AT3 files. Only LP2 and LP4 AT3 files of this type are currently supported. * Added support for decoding mp3 data. This includes mp3 files, OMA files containing mp3 data (previously these cause static/noise to be generated), as well as decoding MP3 tracks direct from a HI-MD device (experimental) * Added an option that if enabled, and the input data is mp3 (see above), then HIMDRenderer will not re-encode the mp3, but just pass it through into an mp3 file. * Added support for encoding to WMA. Capabilities are limited to whatever WMA codec is installed on your machine. * Updated FLAC encoding dll routines to match newer FLAC dll interface * Added Lame MP3 presets (I hope these are correct, I just based this on what LAME actually does internally....). * Added a filter/search system in the file list. Simply select how you wish to find/filter tracks (currently only by filename) and type the search text in the filter text box. To turn this off just remove the filter text, or select "no filter" from the filter drop-down list. *Added an "other" folder selection button to allow selection and scanning of a custom folder that may contain OMA,OMG or MP3 files * Added "filename options" with a default save folder, allowing you to define how HIMDRenderer constructs the output filename of each file it generates. The way to configure this is simular to how "MD Listing" works * Added option to allow "MD Recorder" to use selected "filename options" as above, or to use the old filename format. * Improved timings in "MD Recorder".. Tracks should no longer be truncated wrongly. * Atrac SP tracks are no longer displayed as "Unknown ATRAC" * Detection of when OMA/OMG decoders refuse to work, and report an appropriate error to the user. Sorry, this is as best I can make it - I can't seem to get around the darned error in certain cases :/ * Minor GUI fixes and memory leaks. Beta 2: 21/01/2008 - Fixed crash in "add files" in batch mode 21/01/2008 - Fixed random crash in "MD Listing" Beta 3: 17/02/2008 - Fixed crash in "add files" in batch mode (again) 17/02/2008 - Fixed corrupt and/or repeated audio at the end of some files 17/02/2008 - Fixed crash in bug reporter 17/02/2008 - Fixed album titles in ID3 tags becoming truncated Beta 4: 26/02/2008 - Fixed file creation error when creating output files for tracks that have a question mark (?) in their tag data ALSO NOTE: THIS IS BETA. THERE ARE MANY CHANGES. BUGS MAY OF CREPT IN WITHOUT MY KNOWING. PLEASE REPORT ANY PROBLEMS VIA THE BUILT-IN BUG REPORT SYSTEM, OR VIA THIS FORUM. Download: http://www.marcnetsystem.co.uk/HIMDRenderer-1.00-beta4.zip
  10. Thanks for that. My program currently only handles (and assumes) ASCII track names. All the lists and controls of HIMDRenderer are also ASCII based. In order to handle the korean / chinese / jap character sets I need to convert HIMDRenderer to use unicode based strings.
  11. Ive not been able to get Sonicstage, or any of the Directshow components that Sonicstage (and HIMDRenderer uses) to decode/decrypt tracks that have been recorded directly off a minidisc. Neither have I been able to get it to decode tracks that Sonicstage refuses the play. The tracks are encrypted heavily (unless you have the copy protection option turned off - which SonicStage 3.0 dosn't have) and are tied to both the installation of Sonictsage that imported them as well as the installation of Windows that was used. If either of these change or are lost then the OMA files are useless.
  12. Would it be possible for you to email me the following: 1) The contents of the HMDHIFI folder from the HIMD minidisc, not including the very big ATData file. 2) A screen shot of Sonicstage showing the tracks from the same HIMD disc correctly - as they should be displayed 3) A screen shot of what HIMDRenderer actually shows for the same HIMD disc.
  13. HIMDLister is an obsolete product of mine. Mainly because the functionality has been merged into HIMDRenderer. Try HIMDRenderer 0.54 and see if its any improvement. It should work with both NetMD and HIMD devices -just use the "lister" button
  14. I use my development skills at a well paid job, so I don't need to depend on a home project as my major income. Therefore I don't see the point in making people pay for something that other people find useful. If, however, those people want to pay then they can via donation. It's entirly the users choice whether to pay for it or not, not mine. I think more "shareware" style software should be like this - not limited functionality because you can't afford to / are not able to / do not want to, and letting the user decide whether to pay for a fully featured program, or not. Im not having a go at anyone in particular here - it's just my 2p
  15. It seems to be with OMA files that contain mp3 data... Although im not 100% sure...I only know from the bug report / log files that the Sony OMA decoder outputs mp3 data instead of PCM which I "intercept" and assume its PCM (and because its not PCM , its heard as static) .. so my guess of what causes this is OMA files that contain mp3 data. Most probably with non minidisc mp3 devices ps: Many thanks for the continued support :)
  16. The bug I described above isn't really what you descirbed. Some people are complaining that the entire output mp3 or wav file is static, and is only a minute or 2 long. The first improvement you suggested will be possible if the ID3 library I use for tagging mp3's supports it (it probably does). Although is it required, as I can only get Artist, Track title, Genre, track number and album from OMA file..... This needs investigation As for the second improvement you suggested: Ive added the ability to configure how the output filename is generated using the Title, album, artist, original filename, track number, etc, as well as a custom output folder.
  17. Hi, Im working on fixing one of the major bugs in HIMDRenderer. The one where it is given an OMA file as input, does not error, but produces an output file full of static. These OMA files are probably from Sony MP3 players/recorders that take OMA files. This bug happens because the decoded OMA produces mp3 data, and not PCM data which HIMDRenderer is expecting (assuming). I cannot re-create such files myself, since I only have a (well, two) HIMD recoders, so if you have encounterd this bug then please say so on this thread If you can give me (via link or email or possibly PM attachment) a relativly small OMA file (less than 6mb) that causes this bug to happen, then please do so. Thanks. PS: And thanks to all your bug reports. They have helped in fixing several bugs so far, as well as helping me get to the bottom of this 'static' problem :)
  18. You like in the UK, right? There is one way... if a bit crap: 1) Get a mobile phone 2) Hook up your MD player to your HIFI or computer or something with loud speakers 3) Start playing the music at reaonable volume 4) Dial 2580 on the phone and hold it up to the speaker for around 45 seconds. Yes, its the shazzam music recognition service :D 5) Hang up 6) You will get a text message detailing the artist and song ========================== But as far as I know, if the disc has not been labelled, then there isnt a way of getting the details. Each track on the MD has info about the artist, track name, etc , but they are filled in when the tracks are put onto the disc by SonisStage. If any details are missing when this is done, then there is no way I know of of automatically filling these details back in.
  19. The information from those posts was only useful for re-creating an OMA file from the data on a HI-MD disk. And then, only those tracks that have been downloaded from PC could be recreated. Recorded tracks have no MAC/Key in the HMA file, so no valid OMA file could be created from them.
  20. HIMDRenderer will convert these files to .wav, mp3, ogg or flac http://forums.minidisc.org/index.php?showforum=102
  21. The LAME library I use does not use standard command line parameters... its a bit more complex that that via the LAME library SDK. The LAME options presented to the user via HIMDRenderer are simply copied more or less directly into the LAME library SDK. I will investigate further into this issue when I get a chance.
  22. There are two VBR algorithms in LAME - Old and new. Perhaps this option is the cause of the inconsistancy between encoding apps and HIMDRenderer. I am not sure which algorithm HIMDRenderer uses, and what the default on Lame.exe is. I shall investigate further.
  23. Read my description several posts up in this thread And no, it does not work with a mac (unless Windows is running on it, of course)
  24. Sorry, but a debug version would not help. HIMDRenderer uses the DLL's that Sonicstage installs/uses itself to do all the OMA decoding. This is why you get the same result with my program as with Sonicstage. So if the OMA file is damaged, then neither HIMDRenderer or Sonicstage can repair it. You could try again with HIMDRenderer, let it fail as it did before and then use the "bug report" feature of HIMDRenderer to send me the log file (this is done automatically when you press "Send report") Apart from that, there is nothing more I can do. Sorry.
  25. Dixons / Currys.digital in Reading had some. They were not on the shelves, but when I asked if they had some the guy came back with a box of 5. The whole box cost me £6.99
×
×
  • Create New...