[Whizzer]

thanks i was just curious how the ids were treated packaged. all of my songs should have id’s but packaged you get n/a for the pack file

 

Indeed the pack itself doesn’t have a song_id since it’s not a song, but that doesn’t cause any problems. All songs inside the pack with a proper numerical song_id will work as they did before.

[genaro227]

So using MAGMA to re-do song IDs would keep the songs scores wipe proof, but I’d need to edit the ‘smallname’ in the DTA if songs arent showing up?

[Whizzer]

So using MAGMA to re-do song IDs would keep the songs scores wipe proof, but I’d need to edit the ‘smallname’ in the DTA if songs arent showing up?

 

Deleting your song cache should do it, at the risk of losing some of your scores one last time, if you replace all non-wipe proof song ID’s with proper numerical wipe-proof song ID’d at once.

 

Changing the smallname also requires repacking the song, such that the internal folder structure matches the new smallname. It’s quite a lot of work and I would not recommend it. Magma can bulk replace song ID’s. Delete your song cache afterwards and all should work.

[FujiSkunk]

To be clear, we’re talking about using C3 CON Tools to change ID’s, not Magma, correct?

[Whizzer]

For bulk replacing, Magma would be the way to go.

[hardcoredrummer]

hey is there anyway to reference a new single that you downloaded against songs in a pack? i think i have a conflict again but how can i look at the id numbers or file names of singles that may be conflicting with songs in a pack?

[FujiSkunk]

You can use C3 CON Tools to look at the data (DTA) files of both packs and singles. A pack will have a single DTA which contains all of the ID’s for the song within the pack.

 

I’m not aware of any tool that takes a collection of singles and/or packs and shows if there are any conflicts, so eyeballing the DTA’s may be your best bet.

[hardcoredrummer]

thanks

[Author]

Posts