search for: libshin

...//droidtools.sourceforge.net/content/libogglibvorbis-and-libshout-libraries-android I just finished compiling an android version of our reshaped shine encoder [1] there: http://rastageeks.org/~toots/shine-android.tar.gz In order to use it, you'll need to make /system read-write and copy lib/libshine.so.1.0.0 to /system/lib/libshine.so.1 and bin/shineenc to /system/bin. On my low-end HTC, however, encoding is not real-time, which is a bit disappointing: $ shineenc bla.wav bla.mp3 shineenc (Liquidsoap version) WAV PCM DATA, stereo 44100Hz 16bit, Length: 0: 0:18 MPEG-I layer III, stereo Psych...

Hi everybody. Any development on this? Andrea Thomas.Rucker wrote: > > He's asking for a SOURCE client, not a _listener_ client. > > I don't think such a thing exists at the moment. > > > TBR > > -- View this message in context: http://old.nabble.com/Any-android-source-client-for-icecast---tp30375352p33700728.html Sent from the Icecast - General

...ent/libogglibvorbis-and-libshout-libraries-android > > I just finished compiling an android version of our reshaped shine > encoder [1] there: > http://rastageeks.org/~toots/shine-android.tar.gz > > In order to use it, you'll need to make /system read-write and copy > lib/libshine.so.1.0.0 to /system/lib/libshine.so.1 and bin/shineenc to > /system/bin. > > On my low-end HTC, however, encoding is not real-time, which is a bit > disappointing: > $ shineenc bla.wav bla.mp3 > shineenc (Liquidsoap version) > WAV PCM DATA, stereo 44100Hz 16bit, Length: 0: 0:...

...braries-android > > > > I just finished compiling an android version of our reshaped shine > > encoder [1] there: > > http://rastageeks.org/~toots/shine-android.tar.gz > > > > In order to use it, you'll need to make /system read-write and copy > > lib/libshine.so.1.0.0 to /system/lib/libshine.so.1 and bin/shineenc to > > /system/bin. > > > > On my low-end HTC, however, encoding is not real-time, which is a bit > > disappointing: > > $ shineenc bla.wav bla.mp3 > > shineenc (Liquidsoap version) > > WAV PCM DATA, s...

I'm following up on a thread started by Stephen a couple months ago about building a JavaScript source client using webrtc. The first step suggested was to figure out how to mux the audio and video. After I posted a feature request on the webrtc experiment js library, we seem to have a solution: https://github.com/muaz-khan/WebRTC-Experiment/issues/28#issuecomment-20791759 Based on the last

On Fri, May 16, 2014 at 06:24:48PM -0400, Tristan Matthews wrote: > Hi, > > On Fri, May 16, 2014 at 1:58 PM, batguano999 <batguano999 at zoho.com> wrote: > > > > > Hi > > With 32-bit Xubuntu-14.04. > > When I compile FFmpeg from git using speex-1.2rc1 it builds OK. > > When I compile FFmpeg from git using speex-git it fails to build. > >

...refox and the encoding speed. > > Because there is no native encoding API for browser-side javascript, > we have (temporarily?) resorted to using javascript-compiled libraries > for mp3 encoding. However, only firefox seems to show suitable > performances for mp3 encoding, using the libshine build and thanks to > its asm.js support. > https://github.com/savonet/shine/tree/master/js I'm curious why encoding speed on the browser is an issue. If you are sending the data to a nodejs app on a server, why not have the nodejs app doing any additional encoding necessary? jamie...

...rtially implemented in firefox and the encoding speed. Because there is no native encoding API for browser-side javascript, we have (temporarily?) resorted to using javascript-compiled libraries for mp3 encoding. However, only firefox seems to show suitable performances for mp3 encoding, using the libshine build and thanks to its asm.js support. https://github.com/savonet/shine/tree/master/js On the other hand, only chrome implements the adequate Web Audio API, but is too slow to encode :-o All in all, if we keep forging, it is very likely that once mozilla finishes implementing the web audio AP...

...ncoding speed. > > Because there is no native encoding API for browser-side javascript, > we have (temporarily?) resorted to using javascript-compiled libraries > for mp3 encoding. However, only firefox seems to show suitable > performances for mp3 encoding, using the libshine build and thanks to > its asm.js support. > https://github.com/savonet/shine/tree/master/js > > On the other hand, only chrome implements the adequate Web Audio API, > but is too slow to encode :-o > > All in all, if we keep forging, it is very likely tha...

...irefox and the encoding speed. > > Because there is no native encoding API for browser-side javascript, > we have (temporarily?) resorted to using javascript-compiled libraries > for mp3 encoding. However, only firefox seems to show suitable > performances for mp3 encoding, using the libshine build and thanks to > its asm.js support. > https://github.com/savonet/shine/tree/master/js > > On the other hand, only chrome implements the adequate Web Audio API, > but is too slow to encode :-o > > All in all, if we keep forging, it is very likely that once mozilla >...