Forgive the N00b question, but how do I fix customs using the same Song ID?

  • This topic is empty.
Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #398011
    cleverest
    Participant

      I have about 15 in my collection that are using the same SONG ID, as per File Indexer. Does this mean they won’t load or what DOES that actually cause to happen? (on Xbox 360)

      Is this fixable by me or must it be fixed by the author of the song itself? If by me, what is the process to do this properly with C3Contools? (I assume I’d use that)

      Thanks.

      #513156

      I believe that this would need to be fixed by the authors.

       

      Which songs have conflicting IDs?

      #513157
      cleverest
      Participant

        I believe that this would need to be fixed by the authors.

         

        Which songs have conflicting IDs?

        Here is a list of all my customs having conflicting song ID’s.

         

        https://drive.google.com/file/d/1pH3rfmUiG19dAs_8GecJ1BrnXo4ZpaeN/view?usp=sharing

         

        Does that means none of this stuff is loading in the collection normally or only 1 of them will? I haven’t checked yet…just been organizing stuff. (I’m a bit OCD with that…)

        #513158

        A few of the songs in your list are two versions of the same song (the 2x drums and the regular drums). I would expect those songs to conflict – is there a reason that you need both of them?

         

        When there is a conflict I believe that the ID that was cached first is the one that loads.

        #513159
        Shroud
        Participant

          Is this fixable by me or must it be fixed by the author of the song itself? If by me, what is the process to do this properly with C3Contools? (I assume I’d use that)

           

          You can change the ID manually by editing the DTA file, use C3 CON Tools -> Quick DTA Editor, then change the value of the ‘song_id’ field.

          #513161
          cleverest
          Participant

            A few of the songs in your list are two versions of the same song (the 2x drums and the regular drums). I would expect those songs to conflict – is there a reason that you need both of them?

             

            When there is a conflict I believe that the ID that was cached first is the one that loads.

            Thanks. Yeah, I want both and most 2x drums and single drum versions use different ID’s….the reason why is I alone in my group of friends and potential rock band-mates play Expert Pro Drums (with double bass on my Strike kit), but I want the single pedal version for anyone who may opt to play the same song and at least give them a fighting chance, HAHA

            #513162
            cleverest
            Participant

               

              You can change the ID manually by editing the DTA file, use C3 CON Tools -> Quick DTA Editor, then change the value of the ‘song_id’ field.

              Awesome! I didn’t even think of that!…I guess I can just make up something and check with File Indexer that it doesn’t clash with something else?

              #513164
              hardcoredrummer
              Participant

                if you change them to contain letters you could then run a batch id replace in magma and all of them would be given new id numbers in sequence…others wise like shroud you can use dta editor or just drag the cons into con tools and change it manual there and hit save

                #513168
                cleverest
                Participant

                  Thanks everyone!

                  #513172

                  A few of the songs in your list are two versions of the same song (the 2x drums and the regular drums). I would expect those songs to conflict – is there a reason that you need both of them?

                   

                  When there is a conflict I believe that the ID that was cached first is the one that loads.

                  2x versions should have a different ID than the non 2x version. Magma either increments the numerical ID, or adds 2x to the end of the alphanumeric ID

                  #513177

                  2x versions should have a different ID than the non 2x version. Magma either increments the numerical ID, or adds 2x to the end of the alphanumeric ID

                   

                  Good to know, thanks i0brendan0 <img decoding=” src=”/wp-content/uploads/invision_emoticons/default_SA_smile.gif” />

                  #513180
                  cleverest
                  Participant

                    Yes, good to know, I went ahead and did the same to the couple 2x’s I had that were identical to the non-2x’s, it’s all cleared up now! :-)
                    )

                    #513200
                    hardcoredrummer
                    Participant

                      sorry double post

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