Magma: “Could not open ‘c:.’ for read.”

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #396802
    FUGGNUTZ
    Participant

      I’m trying to make a PS3 version of Into You, and Magma keeps throwing this error:


      Magma: C3 Roks Edition v3.3.2
      =============================
      Build started at 11:42 PM

      Starting Nemo's MIDI Validator...
      Everything looks good, continuing...
      MIDI file contains 2X Bass Pedal track.
      Two files will be created, one with each drum track enabled.
      Compiling 1X Bass Pedal MIDI...

      Nemo's MIDI AutoGen process started.
      Found PART DRUMS and you have enabled the 'Add to MIDI' option
      However, the current suggested drum mix event is unsupported
      Nothing is being changed in the drums track.
      Added drum mix events successfully.
      Nemo's MIDI AutoGen process completed.

      Loading MagmaCompilerC3.exe...
      Reading the archive
      Project Compiler: Reading project 'C:UserslmoorDocumentsRB3 Custom ProjectsAriana Grande - Into Youfugg_intoYou.rbproj'...
      Project Compiler: Entering Phase 1 of 5...
      ERROR: Audio Compiler: Could not open 'c:.' for read.
      ERROR: Project Compiler: Unable to calculate song length due to Audio Compiler errors.
      Compiling 2X Bass Pedal MIDI...

      Nemo's MIDI AutoGen process started.
      Found PART DRUMS and you have enabled the 'Add to MIDI' option
      However, the current suggested drum mix event is unsupported
      Nothing is being changed in the drums track.
      Added drum mix events successfully.
      Nemo's MIDI AutoGen process completed.

      Loading MagmaCompilerC3.exe...
      Reading the archive
      Project Compiler: Reading project 'C:UserslmoorDocumentsRB3 Custom ProjectsAriana Grande - Into Youfugg_intoYou.rbproj'...
      Project Compiler: Entering Phase 1 of 5...
      ERROR: Audio Compiler: Could not open 'c:.' for read.

      I’ve tried renavigating to every item in my project (the album art, the individual audio tracks, and the MIDI), restarting Magma, running Magma as Administrator, and restarting my computer. I’ve also checked my drum mix events, moved everything past 1.2, and made sure to use drums0 because I only have one drum stem and my drum mix is set as Kit in Magma. Can anyone help me out here?

       

      EDIT: Making a new Magma project worked, but I still want to find out what’s wrong with the old one.

      #503702

      I know the fix and why it happens. It’s a bug with Magma. If you’ve added audio to more than 1 drum parts, and save and reopen, and then proceed to reduce the number of drum parts, Magma won’t disable the extra parts. This confuses Magma because it sees that those parts are enabled so it should add those audio files into the mix. But because they don’t have a location, magma will try to use the working drive label, in this case C, and finds that C is not a file.

      Here’s the fix. Open the rbproj file in a text editor other than Notepad. Find this section.


      'tracks'
      ('drum_layout' 'drum_layout_kit')
      (
      'drum_kit'
      ('enabled' 1)
      ('channels' 2)
      ('pan' -1.00 1.00)
      ('vol' 0.00 0.00)
      (
      'file'
      ""
      )
      )
      (
      'drum_kick'
      ('enabled' 0)
      ('channels' 0)
      ('pan' 0.00)
      ('vol' 0.00)
      (
      'file'
      ""
      )
      )
      (
      'drum_snare'
      ('enabled' 0)
      ('channels' 0)
      ('pan' 0.00)
      ('vol' 0.00)
      (
      'file'
      ""
      )
      )

      You’ll see that there is an ‘enabled’ spot on each ‘drum_…” section. It will most likely be 1 in your file. Set the ones not in use to 0, save, and re-open the file. It should now build correctly.

      This is a must have fix for those who make PS3 versions specifically because the 360 version has multiple drum stems.

      #503881

      Answered his (DIFFICULT) question inside 5 hours of his post – admirable and nicely done. <img decoding=” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” />

       

      Two weeks later, OP hasn’t returned to thank you – poor manners at best. :argh:

      #503887
      FUGGNUTZ
      Participant

        We ended up solving this on Discord first. Brendan’s post was made after the fact.

      Viewing 4 posts - 1 through 4 (of 4 total)
      • You must be logged in to reply to this topic.
      Back to top button