Help get this topic noticed by sharing it on Twitter, Facebook, or email.

MPC v1.4 Ren/Studio crashing when loading saved projects

This is a continuation from a closed thread.
http://community.akaipro.com/akai_pro...

I did some further troubleshooting by installing MPC v1.4 on three separate PC's with Ren and Studio as controllers. It seems that most saved projects with multiple samples (chopped from a original WAV) will crash during load. It will start and then crash around 10%. Each PC had a fresh install with no 3rd party VST's. A few times I would get a "Microsoft Visual C++ Runtime Library" error during a crash. All are operating with Windows 7. Here are some screen shots.

Both Ren and Studio
HP Desktops and HP laptop
Windows7 (64bit)
i7 processors
12GB Memory (Desktops)
6GB Memory (Laptop)

2 people have
this problem
+1
This topic is no longer open for comments or replies.


  • The only work around I have is to start a new project and load programs. Then save the changes by overwriting the original project. Not very happy about that.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Akai needs to sort out the crashing issues.

    I have had random crashes on all versions on mac.

    I even tried several brand new Macs.

    Its off-putting to use the software.

    I notices there was an auto save feature, great, but needs to work in the background because it can freeze the sound when it saves.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • Okay, I think I figured it out the "MS C++ Visual Library" crash issue. I'm 80% sure I got it. After checking my Soundforge, I realized I have been saving WAV files with metadata included. Fine, I will not do that from now on. BUT after checking my MPC WAV files from my project folders using SoundForge - I noticed that the MPC software, itself, uses metadata to give information to the individual sounds (such as loops, sustain in/outs, ect). That's why when you removed the metadata and re-saved the files I sent you, J, all the sounds came up blank (start/end points are butting together). It had no meta information to tell what the in/out points were. You would have to do the in/outs all over again to get each sound back to hear them.

    Which exposes a potential problem. All my projects were sample edited in non-destruct mode. Meaning, I never truncated(discarded) my samples - just in case I needed to trim/add more or less later. I have enough HD space...so why not? Apparently, if I do truncate(discard) my samples I can reload the projects with no problems. So now I have to make a New project and load my existing programs from another project. Truncate them and overwrite the original project for it to load properly next time. It's my work around for now, but Akai has to figure out the issue with "Non-Destructive" sample editing. I base my work-flow with importing an entire sample. Then copying and chopping it into pieces to create my projects. I don't want to be forced to truncate(discard) anything. Although, it doesn't crash when I reload projects that have samples that play from start to finish. Meaning no discard-able parts to chop off.

    So if you guys use SoundForge or anything like it...check your project sounds and you will see the metadata in the wave readout, highlighted with your in/out points as (sustain, loop) regions. AKAI uses that info for the MPC software to read. Hopefully, this helps whoever is going through this same issue.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited