Substantial reward for the total legend who can open this bastard reason file

Song.zip 436.32 kB · 23 downloads

been trying to open this reason file on a few versions but they all get this bloody 'media problem' message.

spent about 2 months on this song, one of the best ive ever made :'(

i will shower you with rewards and praise if you manage to open it!

I tried, no joy

i was able to open it, but i couldn't stand the song so i deleted it.

then i went back in time and told myself not to download it, so i didn't download it.

i'm at work so i just have to guess, but is and .rns just a zip compressed file with a sample folder and some kind of .xml document? renoise is like that, when i had a renoise track that corrupted on me i was able to extract and save some of it i think

that's fucked. i get the same error...

"Reason the operation could not be completed because of a media related problem"

I get the error too.

I looked it up on the reason forums and found these not very enlightening hints:

"Remove the FSB and Orkester Sound Banks and reinstall these from the CDs. You may also have to remove any third party refills and then re-install them one by one, to determine if any of these are damaged.

Best Regards,

Michael Lindqvist

(Reason Support)"

"When I switched over my computer I moved a bunch of files and I got media problems all over the place. Try reloading just the refills then reload Reason. For some reason, Reason doesn't like it when you move things around. But I've seen it before, when it's been unfixable... Scary stuff."

""Media" in this connection appears to mean the storage medium for your data. Could the drive on which your songs are stored be flaky? I haven't seen the error myself, so can't tell whether it might appear in response to things other than actual media/controller/driver errors."

I'm wondering - could it be something like one of your samples being loaded from a detachable drive (F:) or something and then when its not there Reason can't handle it?

If you're a registered user you could try sending the file to reason customer support.

  zazen said:

If you're a registered user you could try sending the file to reason customer support.

:teeth:

  zazen said:

If you're a registered user you could try sending the file to reason customer support.

:teeth:

heh, could someone perhaps try it for me?

also - what of this xml file? if i could only extract the midi notes that'de be just as good. it's about 3 cellos, 4 violins, a double bass, some beats and a good month or twos worth of melody - the funny thing is that if i don't get the file back, I WON'T BE ABLE TO HEAR THE VIOLINS. :'(

i tried to see if there was anything that could decompile an .rns but no luck with google.

zazen's post is probably the one you want to explore

possible the file is just corrupted though

I've been encountering this fun problem with Reason where it won't play anything. It's fucking rad. So yeah, I don't use Reason anymore. The only things I was using it for on occassion were bass sounds, "acid" type synths, the compressor/reverb automation... and click tracks for other recordings, just because.

Reason's a bit of a dick sometimes.

i have never once had a problem in the 4 years ive been using it. i dunno.

i forgot to mention - is was working on this when my HD crashed. i just refuse to believe that the data is just completely lost - ive opened the file in a program called hex workshop and its not actually that much code which goes into the file - if only there was some way of just retrieving the portions that are the midi notes and so on...

I too caught this problem a year or two ago, on one of my best songs nonetheless. Never could fix it, and that song is still on my hard drive. completely unusable/

i also have the problem. can't open about two of my songs. if anyone has any luck with zazen's post let us know

Wow, this sounds like a really terrifying bug. I guess I won't be using Reason then.

  Jonas said:

open up an other correct (=working) reason song of yours in a hex editor, + the corrupt file in another instance of a hex editor, and compare the two, maybe there is just an error in the header, and you can copy the header out of the working version over the corrupt bytes.

 

I've done this in the past with a few madtracker tracks & renoise files (before the xml structure change) and could save some fuxord files.

innit, thats exactly what i did after i read somewhere that you could do this with renoise files (both reason and renoise files are .rns - google). the headers slightly differ so im guessing its the filename. did alot of chop and changing to no avail.