Repo/project organization?

[eliasdaler]

Hello.
I was thinking about the current repo structure and organization and what if it was made a bit simpler?
For example, it looks like "goaudiofile" and "gomixing" can live in this repo, but be a separate packages so that you could do something like this if you need to use goaudiofile specifically:

import "github.com/gotracker/playback/goaudiofile"

This will make it easier to update the code (only bump 1 version instead of fixing things in goaudiofile and then updating "playback" repo) and the decoupling is still there.

This is something like what Ebiten does.
It has many subpackages like "audio", "text", "vector" which live in the same repo and make things easier to use/update.

[eliasdaler]

Actually, never mind...
Ebiten has several other "subrepos" it depends on so I guess it's just how things work when you split the project into multiple repos.

The only remaining question is if "gomixing" should remain a separate repo or just be a part of "playback", because it kinda makes sense ("goaudiofile" looks a bit more decoupled)

[heucuva]

Sorry for the late response! I have considered a number of times to go this way - the longer I think about it, the more I like the idea of pulling in the mixing code.

I'll put together a proof of concept and see what makes sense.

[heucuva]

The gomixing package is now part of the playback package!

Doing this allowed for fixing a few bugs in the stereo mixing, elimination of some silly/stupid code, and gave room to implement stereo separation. All things considered, it was a pretty good idea.

Fixed by #14