feat: Speaker Toy

[NotZer0Two]

Description

Describe the changes
Adding the SpeakerToy Apis

What is the current behavior? (You can also link to an open issue here)
None

What is the new behavior? (if this is a feature change)
None

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:
Requires help from anyone for the playing method

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentations

Submission checklist

• I have checked the project can be compiled
• I have tested my changes and it worked as expected

Patches (if there are any changes related to Harmony patches)

• I have checked no IL patching errors in the console

Other

• Still requires more testing

[BoltonDev]

There is already a pull request that adds the speaker toy, you should contribute on it (#235)

[NotZer0Two]

There is already a pull request that adds the speaker toy, you should contribute on it (#235)

talked already to nameless she doesn't update it or adds anything so that's why i did a separate one

[SticksDeveloper]

Final Credits for everything goes to

• Zer0Two
• 3m377
• Stick

Example of playing audio:

var speaker = Speaker.Create(5, new Vector3(0,0,0), true);
speaker.Play(Path.Combine(Paths.Plugins, "audio", "Audio.ogg"), 750f, 1, 500, true);

Proof of it working:
https://github.com/user-attachments/assets/a10eae7a-aa27-4053-8b94-2f6234c779d9

[obvEve]

talked already to nameless she doesn't update it or adds anything so that's why i did a separate one

Yeah I wasn't planning to add Play or anything, so this PR is fine

[NotZer0Two]

The only issue we encountered so far its not on our side but on NW Side where the audio glitches out if multiple speaker are nearby

[NotZer0Two]

Like can we push it and just end this here? because its like a month of this being open and getting fixes for stuff not needed

[SticksDeveloper]

Is there anything else that needs to get changed? Sorry if I'm sounding a bit impatient, I just want to use this exiled wrapper instead of my own variation and with that a lot of code to change to replace said variation.

[MS-crew]

I'm sorry, but what's the problem? When we are going to have this pr I don't want to use a separate audio api

[3m377]

I'm sorry, but what's the problem? When we are going to have this pr I don't want to use a separate audio api

The exiled higher ups are lazy and don't want to merge it because it would require adding a new dependency

[obvEve]

The exiled higher ups are lazy and don't want to merge it because it would require adding a new dependency

We just have other priorities, such as other projects, life and yk having a stable version, there are still bugs to fix rn.

Also as it currently stands, although minor, there is a breaking change which means this can't be merged into EXILED9 while it has that.

[VALERA771]

So as I noticed using nvorbis will require us to add 5 new dependencies (including nvorbis). Which is not good cuz we only use it in one method

[SticksDeveloper]

So as I noticed using nvorbis will require us to add 5 new dependencies (including nvorbis). Which is not good cuz we only use it in one method

Nvorbis is just one dll file though I think? The rest of it isn't required as we are just using the core.

[obvEve]

Nvorbis is just one dll file though I think? The rest of it isn't required as we are just using the core.

NVorbis might have other dependencies tho, which we must respect :)