This is not the right venue to discuss implementation issues.
Please open tickets in implementors bug trackers:
- Firefox:
https://bugzilla.mozilla.org/enter_bug.cgi?product=Core&component=Web%20Audio
- Chrome: https://code.google.com/p/chromium/issues/list
- WebKit: https://bugs.webkit.org/
Also, you can continue this discussion on public-audio-dev:
https://lists.w3.org/Archives/Public/public-audio-dev/.
Thanks,
Paul.
On Tue, Aug 18, 2015 at 12:04 PM, Jason Miller <jason@developit.ca> wrote:
> How are you decoding the MP3 streams?
>
> - Jason
> On Aug 18, 2015 5:19 AM, "Georg Turecka" <georg@sound-sets.com> wrote:
>
>> Hi, dear mailinglist.
>>
>> i'm a noob here, and i am working on an audio player with server side
>> schedule and simple file encryption in chrome.
>> while chrome-webaudio is still most stable browser implementation from
>> what i can tell,
>> it will crash on mp3's bigger than ~20mb
>> it will crash on some mp3 encodings
>> it will crash after around decoding the 155 10mb mp3's.
>>
>> is this acceptable?
>> it seems that audio software always suffers from such problems...
>>
>> ps: <audio> works better in firefox than chrome, and does not suffer from
>> these problems, while it doesn't load all files completely
>>
>> any resources on webaudio and stability? is the nightly build more stable
>> ?
>>
>> thanx#
>> greetz
>> Georg Turecka
>>
>> --
>>
>
