Chat

Author Topic: Corrupted NES project!! Pleeeaaase heeelp!!  (Read 1946 times)

Offline th4d34d

  • Newbie
  • Posts: 2
  • Delek FTW
Corrupted NES project!! Pleeeaaase heeelp!!
« on: December 30, 2016, 05:12:12 am »
Ohhh man, so I was working on this file for hours... really happy with the progress, and so I bounced it as a Rom.  Noticed the rom wasn't working, so I bounced another project to compare which worked, then went back to open my original project and it said it was corrupted, and now it just opens completely blank.  I reaaallly hope this can be fixed. :(
Thank you!! -th4 d34d

The file: https://dl.dropboxusercontent.com/u/101990255/D34D%20-%20Epic%20NES%20-%20broken.dmf

Offline marcb0t

  • Member
  • Posts: 125
Corrupted NES project!! Pleeeaaase heeelp!!
« Reply #1 on: December 31, 2016, 06:09:04 pm »
Ohhh man, so I was working on this file for hours... really happy with the progress, and so I bounced it as a Rom.  Noticed the rom wasn't working, so I bounced another project to compare which worked, then went back to open my original project and it said it was corrupted, and now it just opens completely blank.  I reaaallly hope this can be fixed. :(
Thank you!! -th4 d34d

The file: https://dl.dropboxusercontent.com/u/101990255/D34D%20-%20Epic%20NES%20-%20broken.dmf

Howdy!

If you get this message in time, do NOT start any more Deflemask modules.

Your best option is to go into your Deflemask "Home" directory and look for the file called "backup.dmf".

Make a copy of that file and call it something like "OLDbackup1.dmf" or something like that.

Now, open up Deflemask and open up that file, and see if this is a backup version of your pre-corrupted file.

There is a possibility that it will be there.

Offline th4d34d

  • Newbie
  • Posts: 2
  • Delek FTW
Corrupted NES project!! Pleeeaaase heeelp!!
« Reply #2 on: December 31, 2016, 08:56:53 pm »
Marcus!   Many thanks for your reply.  Unfortunately, the back up was something I was aware of and had already checked.  To my dismay, the auto-save had already corrupted the backup (the backup was the same file size as my corrupted file).

So I went back into Defle, and luckily I had saved most of the instrument patches (and of course my prefab's in Ableton were safe), so I began reconstructing my track (we've all been there done that, right? Hahahaha).  Anyway, I was lucky enough to be able to recreate everything as it was still pretty fresh in my head.  And, as this sort of thing usually goes, I think the redone version came out even better than before! lel...

Here is what I learned:  When working with the 2a03 on Defle, you CAN NOT overload the sample bank with large file sizes or IT WILL CORRUPT THE FILE.  So, if you have too many files or a file size that is simply too large, it will immediately corrupt when you save.  To remedy this, I went through and re-saved all of my samples as 22050, and then dropping them to mono.  OK, so I got it working and it wasn't corrupt when adding the smaller files.... buuuut, when I bounced the project as a ROM, the ROM was corrupt and wouldn't play in any NSF player or emulator.  So I went back to the file, and in Defle I set most of the files to 11025, resaved and voila, it worked!  So, I was lucky enough to get it working both on Defle, and the ROM bounce.  Soooo happy I was able to figure it out after hours of trials and tribulations, lol.

So for anyone reading this working on 2a03, remember, always save your PCM samples at 22050 or less and in mono, or work on your project at your own risk but don't say I didn't warn! XD

Thank you maaaarc!  You are teh best, as always.