You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From line 48 of adapterWebAudio.js
this.audio.addEventListener( 'progress', function ( e ) {
if ( e.currentTarget.duration ) {
_this.progress = e.currentTarget.seekable.end( 0 ) / e.currentTarget.duration;
}
});
Causes an Uncaught IndexSizeError: Failed to execute 'end' on 'TimeRanges': The index provided (0) is not less than the object's length (0).
This occurs when I use sources like shoutcast and icecast.
This is fixable if you nest this condition if(e.currentTarget.seekable.length>0) inside the function.
This doesn't appear to be a problem in Chrome, it just runs through the error anyway. However, I'm guessing/hoping that a similar type of error for the mozilla adapter is preventing firefox from using live mp3 streams (it appears firefox can play and visualize local mp3's just fine).
Awesome project though I'm hooked on the demo.
The text was updated successfully, but these errors were encountered:
same issue on my stream. (and i used the same solution.. :) )
when adding a >0 condition Chrome runs just fine,
IE doesnt show anything, but at least the stream audio plays (maybe due to combo with audio-elements? ) and the same goes for mobile devices.
firefox is a different problem tho.
adding dancer actually disables the stream playing which makes it not usuable for now.
From line 48 of adapterWebAudio.js
this.audio.addEventListener( 'progress', function ( e ) {
if ( e.currentTarget.duration ) {
_this.progress = e.currentTarget.seekable.end( 0 ) / e.currentTarget.duration;
}
});
Causes an Uncaught IndexSizeError: Failed to execute 'end' on 'TimeRanges': The index provided (0) is not less than the object's length (0).
This occurs when I use sources like shoutcast and icecast.
This is fixable if you nest this condition if(e.currentTarget.seekable.length>0) inside the function.
This doesn't appear to be a problem in Chrome, it just runs through the error anyway. However, I'm guessing/hoping that a similar type of error for the mozilla adapter is preventing firefox from using live mp3 streams (it appears firefox can play and visualize local mp3's just fine).
Awesome project though I'm hooked on the demo.
The text was updated successfully, but these errors were encountered: