audiostream | Stream and transcode your music library over HTTP | Audio Utils library

I fixed it by increasing a function where I capture the audio from the microphone

Does Oboe stop rendering audio if it takes too much time to render audio like situation above?

Yes. If you block onAudioReady for longer than the time represented by numFrames you will get an audio glitch. I bet if you ran systrace.py --time=5 -o trace.html -a your.app.packagename audio sched freq you'd see that you're spending too much time inside that method.

Did I reach limit of rendering audio, meaning that only limiting number of queues is the solution? or are there any ways to reach better performance?

Looks like it. The problem is you're trying to do too much work inside the audio callback. Things I'd try immediately:

• Different compiler optimisation: try -O2, -O3 and -Ofast
• Profile the code inside the callback - identify where you're spending most time.
• It looks like you're making a lot of calls to sin and cos. There may be faster versions of these functions.

I spoke about some of these debugging/optimisation techniques in this talk

One other quick tip. Try to avoid raw pointers unless you really have no choice. For example AudioStream* stream; would be better as std::shared_ptr and std::vector* players; can be refactored to std::vector players;

In discord.js v12, VoiceConnection#createReciever() was removed in favor of VoiceConnection#reciever. I imagine this is because they wanted to limit you to one receiver instead of letting you create however many you want, but I'm not certain. I'm sure you can find a reason in the release notes.

Your example can play midi, wav files, maybe some others, but not mp3, because of patent issues, but If you can use JavaFX, then you can play mp3 like this:

I'm going to venture a guess that the issue about a line being unavailable is due to an attempt reuse a line. AFAIK, you can open as many Clips as you want (assuming you don't run out of memory).

How many can play at the same time is another question. I think it depends a great deal on the individual PC. I think the last time I tried this was several years ago on an older laptop and it could handle something like 30 Clips or half that many SourceDataLines playing at once.

If you are trying to play a sound file as a Clip concurrently (making many copies of the same audio resource), you might be interested in looking at AudioCue. This makes use of a plan where the source data is stored just once in memory, but multiple cursors (each a playing instance) are managed, and the outputs from the cursors are merged into a single SourceDataLine. Some very complex soundscapes can be built with this tool.

Figured this out: Different browsers use different transcoding. Insta only accepts MP4 transcoding. Hence, you need to use either a transcoder on the frontend(ffmpeg.js or wasm version of ffmpeg) or send your data to backend and handle there(which I ended up doing)

For MP3 the first 1105 samples are decoder delay, leaving 47 samples returned out of 1152. See How to compute the number of extra samples added by LAME or FFMPEG

Since Youtube URLs are not like other URLs for VLC, in the sense that you give a HTML URL to VLC, and that VLC needs to parse that HTML page and reconstruct the actual video URL (that's what the lua script does), you cannot give the HTML URL directly to the mediaplayer as a media.

Create a media from the HTML URL, as you have done.

Now is a ReadableStream object.