Help - Search - Members - Calendar
Full Version: Something really annoying while encoding MPC!
Hydrogenaudio Forums > Lossy Audio Compression > MPC
Raymond
When I encode some WAV files into MPC, sometimes my computer will crash. I guess the MPC encoder uses CPU very heavily to make it too hot. Maybe I should buy a new fan for my CPU.
The problem is, after I restart my computer, all my pre-encoded MPC files are lost! Sometimes even include the original WAV files! They become something like FILE0000.CHK in a new FOUND.000 folder.
Why does this happen? Do I have any way to avoid this?

My system is win2kpro.
wynlyndd
sounds like the scandisk or other disktool you are using is gathering up some lost clusters into a file on the off chance you can do something with it (my guess: no)

before trying to make anymore mpc files...defrag your machine after doing a diskcheck...

really, mpc encoding isn't that bad to the processor
lucpes
So far no one reported problems like the one you mentioned, so it seems like the culprit lies on your side rather that having anything to do with the encoder itself.

BTW: if you're still using Windows 98 or Me I strongly suggest upgrading to XP. Even on a lesser machine.

Also, make sure that the HDD drive is set at the end of the Ultra ATA cable. If it is there, change the ATA cable for another (my own experience, got all sorts of errors until I changed the HDD cable - could just be a bad one in your case.)

Should the CPU be problem - need more details: Motherboard/chipset, CPU, CPU's temperature... or you can just open the side panel of your case (leave it open) and see if that makes a difference.

Hope this helps :)
NumLOCK
In addition to lucpes's advices:

Raymond: Never ever waste your time on defrag when your machine is not rock-stable. You'll only lose more data.

Try to open the side of your case to see what's going on. Maybe your cpu fan died or something.
budgie
QUOTE(lucpes @ Apr 17 2003 - 12:04 AM)
...if you're still using Windows 98 or Me I strongly suggest upgrading to XP. Even on a lesser machine.

I see really no reason why doing so... Still using Win98SE and NT4(SP7 - I know it wasn't an official release) and not so fast machines, they are from 1999... I am very satisfied, everything runs smoothly and I must admit I use a lot of music software. rolleyes.gif
DonP
Since replies are speculating you may be on win98 and your post says win2k I'm guessing that was your edit?
In general, a single application like an mpc encoder wouldn't crash the whole system in win2000 like it might in win98.

Also relevent is your file system. THe files you ask about sound like those you get in a FAT file system
when the computer crashes or loses power. (FAT being the system for older windows, but you may also
have it on a win2000 machine). As someone suggested, they are the contents of the dustpan after
broken files are swept up.

Look on this board for the poll: "What file system do you prefer: FAT32 or
NTFS?"

This could mean your hard drive is going bad.
Lev
Raymond,

Your computer never crashes whilst doing anything else processor intensive? Or isnt prone to crashing just because of being utterly bogged down with software conflicting with itself?

Edit: Because I cant believe its MPC
floyd
yeah, any audio encoder will use 100% of your cpu if you have spare cycles. hard to believe mpc is at fault. I'd guess either your install of win2k is screwed (very rare), or you have a hardware failure (probably motherboard or cpu, possibly cpu fan)
WaldoMonster
QUOTE(budgie @ Apr 17 2003 - 09:32 AM)
QUOTE(lucpes @ Apr 17 2003 - 12:04 AM)
...if you're still using Windows 98 or Me I strongly suggest upgrading to XP. Even on a lesser machine.

I see really no reason why doing so... Still using Win98SE and NT4(SP7 - I know it wasn't an official release) and not so fast machines, they are from 1999... I am very satisfied, everything runs smoothly and I must admit I use a lot of music software. rolleyes.gif

Why still using NT4?

I also had a not so fast Celeron 300Mhz.
And I thought that NT4 was faster than Windows 2000.
But after testing Windows 2000 was faster than NT4.
Memory is more important, for Windows 2000 you need minimal 256Mb.
budgie
QUOTE(WaldoMonster @ Apr 17 2003 - 03:22 AM)
Why still using NT4?

Because I need my big comp for ripping & burning audio, encoding music, sometimes for composing and sometimes for various editing and some internet activities... I play no games. And I use it yet for viewing movies, some excel spreadsheets... For this all is NT4 more than enough... I have 512 MB RAM, that's no problem. But the raw installation has 150 MB! Compare it with W2K... And I really don't need all the shit and crap that's inside W2K, leave alone XP...
Raymond
Thanks a lot for all ur answer!

My computer: AMD 1.2G/256MRAM, file system is FAT32 with WIN2KPRO (yeah, I edited my first post )

I don't mean MPC encoder is the only reason of crash. I think my CPU fan is not strong enough for my CPU when it's in heavily use. When I encoded once a WAV file instead of batch encoding things will be better.

What confused me is: for example, after encoded A and B file, then A.MPC and B.MPC is there on the HD. Then I begin to encode C file. Then crash happened. After restart, ALL MPC files (include A.MPC, B.MPC) are lost!
They become FILE000.CHK, FILE001.CHK!

Why things happen like this? I experienced other kind of crash occasionally. The existed files will never lost after crash.
flloyd
Raymond, a great way to test the stability of your computer is with Prime95. Download the program, read all of the instructions, and then run a torture test. It will tell you everytime that it finds an error, thus telling you whether your computer is stable or not.

I recently bumped the FSB of my Duron 600 from 100 to 133 to give me a Duron 800. All of my programs worked fine for a day with no problems but I decided to try Prime95 to make sure. I ran Prime95 a bunch of times and it would always come up with an error after about 30 minutes or so. I then decided to put my Duron back to 600 and try running it again and I haven't had a single error after a week straight. So it is definitely a good stress tester. This will at least allow you to narrow down your search. Good luck.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.