-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write support #7
Comments
Apologies for the late reply, I have been rather ill. It would be possible to add write support but I personally will not have the time for quite a while yet. I can try look into it and at least plan it out but I can't promise anything on it being done, sorry about that. |
Okay fair enough. Thanks for the response @43081j. I have created a repo for benchmarking id3 libs and your was one of the three I found that worked really well. I have written a blog post about the performance results in case you are interested. If you do end up adding write support I will add it to my blog post. |
I would also be interested in write support. I could probably help implement it, with some guidance. |
@43081j I'd love to add write support. Would you mind updating this thread with a high-level overview of how you'd go about it? |
I'm sorry I haven't been involved in this repo for quite a long time, I haven't had the time for various reasons. There's a few problems with the repo in addition to the need for write support, such as:
As for write support, you'd want to implement it as per the 2.3 spec most likely here: So off the top of my head:
|
@oddityoverseer13 did you have a crack at implementing write support based on the info from @43081j ? |
I have not. I've been pretty busy since I asked about that, but I should be coming into some free time soon. I'll keep this in mind. |
Thanks for the great project. Are there any plans for write support?
The text was updated successfully, but these errors were encountered: