K Henriksson

Could you clarify when you'd like these modifications to occur? I'm not sure also what you mean by stripping out bpm fields, since that tag information isn't preserved by the...

Alright. I'll leave this up here, but I don't anticipate being able to implement this in the near future.

Unfortunately, ID3 2.3 and 2.4 support is provided in two separate libraries, so supporting both would involve significant work to switch tagging functions and interfaces between the two. It's extremely...

Skipping the ID3v1 tags and only doing ID3v2.4 is easier to manage. I can look into this.

It's going to be awkward to add OGG support without restructuring the code. I'm in the process of doing this, but it's not done yet. Once it is done, then...

This was intentionally vague, as I want to leave open the possibility for both. Source file Ogg support is certainly reasonable. Source file support for Ogg will likely come before...

Since there seems to be a lot of interest, I just though I'd post an update on where things stand. The code has now been rewritten to make it more...

Closing since there's no response.

That does sound like a compiler issue, and I'm glad you were able to get it resolved. Closing this issue.

In cases where the pad name and signal name are the same (like say both are 1..20), it would be really nice to have a button that would just auto-associate...