-
Notifications
You must be signed in to change notification settings - Fork 67
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
Is this project abandoned? #68
Comments
No reply in over a year, strongly suggests it. |
It is blocked, not abandoned. There's basically no resource for maintaining it. You're welcome to take part in maintenance. |
Thank you for the update.
…________________________________
From: Dmitry Yv. <notifications@github.com>
Sent: Monday, September 30, 2019 7:15:16 PM
To: audiojs/web-audio-api <web-audio-api@noreply.github.com>
Cc: Scott Martin <scott@scottmartin.systems>; Comment <comment@noreply.github.com>
Subject: Re: [audiojs/web-audio-api] Is this project abandoned? (#68)
It is frozen, not abandoned. There's basically no resource for maintaining it.
There's a couple of blockers need resolving first - audio-speaker implementation for node audiojs/audio-speaker#44<audiojs/audio-speaker#44> and https://github.com/audiojs/audio-mpg123.
You're welcome to take part in maintenance.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#68?email_source=notifications&email_token=AHW4CBJ46RUAGUQZDKJ7Z2LQMI63JA5CNFSM4FPJEH3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76STTY#issuecomment-536685007>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHW4CBPBGZI42UCGVLZJAQDQMI63JANCNFSM4FPJEH3A>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I see the code hasn't changed for over a year now, and the feature set is incomplete.
Is this project dead? I can't see any other WebAudio implementation for Node anywhere but there's nothing in the readme here saying what the plan is.
Thanks.
The text was updated successfully, but these errors were encountered: