woj

i doubt it. from what i've read up on in the past day, ss's drm encryption key for an oma file is not version-specific; it's installation-specific. so, installing an old version of ss will not allow you (or me) to read oma files that were created with another installation of ss -- even if it's the same version number on the same computer. sucks, but that seems to be the case. and i suspect that the old wave conversion tool, like himdrenderer, would not able to access oma files, even if 2.1 was installed, since the drm would prevent it from reading them. woj

already tried that. while sonicstage will load the old files and even read the metadata, it chokes when playing or converting them. so, as you would expect, himdrenderer can't do anything with them either -- but i did try hoping that it might! i also tried sony's wav conversion tool but it errored out saying i had to install sonicstage 2.1 or better. of course, sonicstage 3.3 is installed so there must be some catch about the the new version not being recognized by the conversion tool (probably not programmed in since the newer versions of songicstage have the wav conversion capability built-in). in any case, i'd guess that the standalone converter would not be able to do anything with the old oma files anyway for the same reason himdrenderer can't.

i'd be interested if anyone has any suggestions for this problem as well since i ended up in a similar situation, though via different means. i transferred a live recording i made using ss 3.2 but did not convert to wav due to (at the time) limited hard disk space. while transferring another recording yesterday, i managed to muck up ss so i upgraded to 3.3 but i did not backup the oma files i had first. instead, i just dragged them to the desktop expecting that i could simply open them in 3.3 afterwards. well, 3.3 recognizes the oma files but does not realize that it was made from an analog recording. so, 3.3 refuses to do anything with it. grrrrrr. any suggestions would be appreciated!