Split Sound Effects and Quickchat's

HSharp · Post by **HSharp** » Tue Apr 19, 2011 6:13 pm

It would be nice to be able to get new sounds (for new factions or effects etc...) and not break existing chatpacks so is there a possibilty of spliting sounddef.mdl into two files, one sounddef for sound effects and another sounddef for quick chats (sounddefqc.mdl?) that way no matter how many new sound effects are in place a persons existing quickchats can remain the same. This will make it easier for chat packs to stay around without needing someone who knows how to edit them to constantly update them after sounddef updates.

Also maybe change the default setting to mute unknown voice chats?

Andon · Post by **Andon** » Tue Apr 19, 2011 6:47 pm

I believe this can be done, if you used a separate file for the chatpack stuff. You'd have to make a "blank" file for the regular sounddef.mdl file to reference, but that's just technicalities.

TurkeyXIII · Post by **TurkeyXIII** » Wed Apr 20, 2011 1:35 am

On a related note, what about different sound effect files for each core? It's annoying having to modify sounddef when two different people are working on two different cores that share the same sounddef.mdl file.

Andon · Post by **Andon** » Wed Apr 20, 2011 1:39 am

More or less the same thing. Without looking at the file and playing with it myself, it'd be hard to say, but it should be possible.

HSharp · Post by **HSharp** » Sat Apr 23, 2011 5:11 pm

Not really the same Andon, yes in principle but in practice it's going to require a rewrite of each individual core as it would change the way core files would work having to show which coresounddef file they are using. Of course it might just be a simple thing to do to change on every core and all the current cores can use the same sounddef file (minus the quickchats) as now anyway so wouldn't need to make a whole bunch of new sounddef files but I dunno if that would be breaking ICE or text2core etc...

Quickchat I believe though has nothing to do with the core files so that should be able to work without touching the cores themselves, would just be changing where quickchats get the sounds defined.

Andon · Post by **Andon** » Sat Apr 23, 2011 9:28 pm

You'd have to change the .igc format to have each core pull the coresounddef files.

You can, however, have sounddef.mdl use other files - So you add a line for adding xc_sound.mdl and have all the xc definitions in there. You'd still have to maintain the individual numbers over all the different files, but that's no different than now.

HSharp · Post by **HSharp** » Sat Apr 23, 2011 10:31 pm

yeah I know, im just saying you have to edit all the existing cores, I dunno if it would affect ICE, it would probably require an update to add the functionality to add coresounddef file.

Not saying it's hard(er) to do, just different, you can definitely split sounddef and create a quickchat sounddef now without breaking anything apart from custom chatpacks but it would be a piece of cake to add em.

Andon · Post by **Andon** » Sat Apr 23, 2011 11:55 pm

HSharp wrote:QUOTE (HSharp @ Apr 23 2011, 06:31 PM) yeah I know, im just saying you have to edit all the existing cores, I dunno if it would affect ICE, it would probably require an update to add the functionality to add coresounddef file.

Not saying it's hard(er) to do, just different, you can definitely split sounddef and create a quickchat sounddef now without breaking anything apart from custom chatpacks but it would be a piece of cake to add em.

You DON'T have to edit the cores for a separate file for core sound files. You WOULD have to edit the cores to do it how you're saying.

At the moment, Alleg references sound number X for the gat firing sound. Primary location it checks is sounddef.mdl - But if you decided to take all of the BSG sounds and put them in bsg_sounddef.mdl and then use sounddef.mdl to reference bsg_sounddef.mdl, it'd still find the file.

In theory, it should work, but I know that some things like this don't work (Tried to do something similar with HUDs)

HSharp · Post by **HSharp** » Sun Apr 24, 2011 12:14 am

Andon wrote:QUOTE (Andon @ Apr 24 2011, 12:55 AM) At the moment, Alleg references sound number X for the gat firing sound. Primary location it checks is sounddef.mdl - But if you decided to take all of the BSG sounds and put them in bsg_sounddef.mdl and then use sounddef.mdl to reference bsg_sounddef.mdl, it'd still find the file.

Yes but the whole point of having a bsg_sounddef.mdl is so you don't need to keep changing sounddef.mdl for every new core

TurkeyXIII · Post by **TurkeyXIII** » Sun Apr 24, 2011 9:58 am

As long as the change to sounddef.mdl is only one line per core it would be easier to maintain than the current convention. But if it does work (big if, I know), how would it resolve conflicts? For example, if I defined 999 to play a sound that I wanted in dc_sounds.mdl, while you defined 999 to play a different sound you wanted in bsg_sounds.mdl, and we included both in sounddef.mdl - how would it know which one to play?