0.4.x changes

[sezero]

What do we plan to include change in 0.4.x? Created this one for possibly easier bookkeeping.

• return host-endian audio data, not little-endian: Done (issue Support for host Endian-ness #30, and the issues referenced therein)
• switch to using stdint.h types: Done (issue replace 'long' type usage by int or int32_t #43)
• remove console prints from the library (and possibly add an error reporting api?): issue prints to stdout and stderr from the library are plain annoying #41
• possibly change type of rate from 16 bit to 32 bit? (issue change type of rate from 16 bit to 32 bit #44)

[chrisisonwildcode]

Would be good to have an error reporting API for 0.4 since stderr reporting
has been removed

Sent from my iPhone

On 8 Mar 2014, at 8:04 pm, sezero [email protected] wrote:

What do we plan to include change in 0.4.x? Created this one for possibly
easier bookkeeping.

return host-endian audio data, not little-endian: Done (issue
#30#30,
and the issues referenced therein)

switch to using stdint.h types: Done (issue
#43#43
)

remove console prints from the library (and possibly add an error
reporting api?): issue #41#41

possibly change type of rate from 16 bit to 32 bit? (issue
#44#44
)

Reply to this email directly or view it on
GitHubhttps://github.com//issues/47
.

[psi29a]

That is also a good plan, but don't forget these:
https://github.com/Mindwerks/wildmidi/issues?milestone=2&state=open

^-- I assign a milestone (in this case 0.4) and all the issues under it. Those were all the original goals, everything we've been doing is also good but I see that more as enchantments/bug-fixes than features (aside from get_version).

Feel free to comment on those open issues.

[sezero]

On 3/8/14, chrisisonwildcode [email protected] wrote:

Would be good to have an error reporting API for 0.4 since stderr reporting
has been removed

stderr reports haven't been removed yet, but they do deserve to die,
and we'll then need adding an error api.

[psi29a]

One more thing we should add... I would like to reorganize our code a bit. We have our lib, player and devtest... we may have other tools later. Maybe it is time we organized our sources better.

[chrisisonwildcode]

One thing I was thinking of is having devtest imbedded in the player as a
verifying tool ... Saves having an extra binary and for us we can throw
test parsers in it for other formats.

Just a thought

Sent from my iPhone

On 9 Mar 2014, at 9:48 am, Bret Curtis [email protected] wrote:

One more thing we should add... I would like to reorganize our code a bit.
We have our lib, player and devtest... we may have other tools later. Maybe
it is time we organized our sources better.

Reply to this email directly or view it on
GitHubhttps://github.com//issues/47#issuecomment-37113770
.

[sezero]

XMI support is in now (issue #7). Multi-track xmi files require midi type-2 support, which needs implementing (issue #60).

[psi29a]

Is this wrapped up? I think we got everything in the opening post. The rest of the features and bugs are already being tracked for this milestone.

[sezero]

On 4/27/14, Bret Curtis [email protected] wrote:

Is this wrapped up? I think we got everything in the opening post. The rest
of the features and bugs are already being tracked for this milestone.

Pretty much. There are things to iron out though, wrt added formats
and midi-conversion thing.

[psi29a]

But those are covered by other issues in the tracker and not mentioned in the opening. Can this be closed?

[sezero]

On 4/27/14, Bret Curtis [email protected] wrote:

But those are covered by other issues in the tracker and not mentioned in
the opening. Can this be closed?

OK by me, then.