Reason Bad Format

If anyone can open this without getting "Bad Format" error and PM it to me I'd be eternally gratefull

It's in Reason 4.0.1

Thanks

Jam325.rns.zip 274.63 kB · 4 downloads

shit man, wouldn't open for me either :(

thanks for tryin

no prob bob.

I can't open it either, sorry.

dude ive had similar problems with reason. Ive had one of my most amazing old tracks completely destroyed because of this. Its completely random, extremely rare, and very incurable.

are you following the extremely necessary rule of saving a new version of a sequencer project file each time you save?

all programs i've used can corrupt a project file, even Cubase and Nuendo do it. Which is why i never save over my original project i always save a new version.

i have learned the hard way, many times over

If you're copy of Reason is a proper, registered one, i believe you can send the file to Propellerheads support and they will try and untangle it for you

  On 7/30/2009 at 10:33 PM, Awepittance said:

are you following the extremely necessary rule of saving a new version of a sequencer project file each time you save?

 

 

all programs i've used can corrupt a project file, even Cubase and Nuendo do it. Which is why i never save over my original project i always save a new version.

i have learned the hard way, many times over

hmmm I save every 30 seconds whatever program I'm in. Force of habit I guess

To be fair, reason hardly every crashes, I've only had this once before.

  On 7/30/2009 at 10:41 PM, zazen said:

If you're copy of Reason is a proper, registered one, i believe you can send the file to Propellerheads support and they will try and untangle it for you

doh

  On 7/30/2009 at 11:46 PM, G. I. Raffe said:

  On 7/30/2009 at 10:33 PM, Awepittance said:

are you following the extremely necessary rule of saving a new version of a sequencer project file each time you save?

 

 

all programs i've used can corrupt a project file, even Cubase and Nuendo do it. Which is why i never save over my original project i always save a new version.

i have learned the hard way, many times over

hmmm I save every 30 seconds whatever program I'm in. Force of habit I guess

 

To be fair, reason hardly every crashes, I've only had this once before.

 

  On 7/30/2009 at 10:41 PM, zazen said:

If you're copy of Reason is a proper, registered one, i believe you can send the file to Propellerheads support and they will try and untangle it for you

doh

if you 'save' and not 'save as' that is your problem right there. The more times you save over a complicated sequencer project file the more liklihood it has of becoming a corrupt unusable file. trust me on this, you want to get in the habbit of doing a 'save as' every time.

just do it like by putting a # at the end of every version ie: songdemo1, sondemo 2, songdemo 3

In my experience any hefty program like Final Cut pro, Logic Audio, Cubase, Reason, even Photoshop or Illustrator saves very complex files that even if they get the slightest bit corrupted they will be totally unopenable in their respective programs. I have lost probably about 4-5 very important projects in my life that took hundreds of hours of work just because i did the common fuckup and just saved straight over my original file.

i cannot stress to you enough just how crucially important a 'save as' habit is. sure you may have gone all this time with Reason not fucking up and thats a great track record. I have had 4 hard drive failures in a 2 year period, while a friend of mine has never had a hard drive fail in his history with computers. Some people have great luck some people like me have shit luck, but just in case one day your luck changes you will at least have a defense already set up :)

edit: i will finish by saying that this technique to me has proven just as valuable as doing regular data backups of my stuff.If you have ever used photoshop before , imagine what it would be like to use photoshop with only 1 undo with zero history. By using this technique you are basically creating a manual history of your song, sometimes corruptions still happen but at least when they do you can go to the directly previous version that is not corrupted

  On 7/31/2009 at 12:44 AM, Awepittance said:

  On 7/30/2009 at 11:46 PM, G. I. Raffe said:

  On 7/30/2009 at 10:33 PM, Awepittance said:

are you following the extremely necessary rule of saving a new version of a sequencer project file each time you save?

 

 

all programs i've used can corrupt a project file, even Cubase and Nuendo do it. Which is why i never save over my original project i always save a new version.

i have learned the hard way, many times over

hmmm I save every 30 seconds whatever program I'm in. Force of habit I guess

 

To be fair, reason hardly every crashes, I've only had this once before.

 

  On 7/30/2009 at 10:41 PM, zazen said:

If you're copy of Reason is a proper, registered one, i believe you can send the file to Propellerheads support and they will try and untangle it for you

doh

 

if you 'save' and not 'save as' that is your problem right there. The more times you save over a complicated sequencer project file the more liklihood it has of becoming a corrupt unusable file. trust me on this, you want to get in the habbit of doing a 'save as' every time.

just do it like by putting a # at the end of every version ie: songdemo1, sondemo 2, songdemo 3

In my experience any hefty program like Final Cut pro, Logic Audio, Cubase, Reason, even Photoshop or Illustrator saves very complex files that even if they get the slightest bit corrupted they will be totally unopenable in their respective programs. I have lost probably about 4-5 very important projects in my life that took hundreds of hours of work just because i did the common fuckup and just saved straight over my original file.

i cannot stress to you enough just how crucially important a 'save as' habit is. sure you may have gone all this time with Reason not fucking up and thats a great track record. I have had 4 hard drive failures in a 2 year period, while a friend of mine has never had a hard drive fail in his history with computers. Some people have great luck some people like me have shit luck, but just in case one day your luck changes you will at least have a defense already set up :)

 

edit: i will finish by saying that this technique to me has proven just as valuable as doing regular data backups of my stuff.If you have ever used photoshop before , imagine what it would be like to use photoshop with only 1 undo with zero history. By using this technique you are basically creating a manual history of your song, sometimes corruptions still happen but at least when they do you can go to the directly previous version that is not corrupted

Great tips.

What I do is very similiar, I have a folder called "Backup" on my external harddrive, then every time I do backups, I just create a new folder (like if I backed things up today it'd be called "2009-07-30") and then copy all my music files in there. It's good too if you listen to an old mix and realize that you almost like it more than a newer mix, because then you can go back and just replace the new mastering tweaks with the ones used in the earlier mixes.

Actually I work with bigger files than that. Every day I use Flash, Strata 3D, After Effects, Final Cut, Illustrator, Photoshop as part of my job and and I only do a 'save as' when there's a fairly moderate change I've made, about 2, 3 times a day on average. I don't think doing a save as every 30 seconds would be ideal as I'd have Thousands of versions. I do apple+s every 30 secs now without thinking.

It's very rare a mac crashes but when it does I'm usually safe because of regular saving in this way

My Mac froze froze whilst in the middle of my save on that above file, I suspect the same could've happened with a 'save as' - just bad luck

  On 7/31/2009 at 10:00 AM, G. I. Raffe said:

Actually I work with bigger files than that. Every day I use Flash, Strata 3D, After Effects, Final Cut, Illustrator, Photoshop as part of my job and and I only do a 'save as' when there's a fairly moderate change I've made, about 2, 3 times a day on average. I don't think doing a save as every 30 seconds would be ideal as I'd have Thousands of versions. I do apple+s every 30 secs now without thinking.

if you have time to hit apple + S every 30 secs you should be able to do a save as that often as well, i mean in the end it's going to you that will suffer if you save over your original file.

and you say that it froze 'while saving' and no the same thing wouldn't have happened with Save as because you would be able to go back to a version you saved 30 seconds earlier that is not corrupted. Do you follow the logic? if you save over your file you have no previous versions.

Macs crash. You are a lucky mac user