ryanheise
ryanheise
> @ryanheise if you think this is resource-intensive what do you think about adding a max number of concurrent jobs so that people could limit the number of files being...
I would consider it a misuse of the plugin to simultaneously write to the same path, so the path should be unique among the simultaneous requests.
This problem is not a a real problem since it can be documented and an exception can be thrown if the same output file is being used in two simultaneous...
I'll add to the above that using a UUID does not actually solve the problem of using the same output file in simultaneous requests - an exception would be needed.
For now, you can download the URL to a file and then use the file with just_waveform.
Yes it is.
Note you can also check the changelog to see if there have been updates.
Just to update everyone, the current way is still do download the file first and then pass the file into the API. There is no urgency to do it another...
I do not see how that use case won't work, and how extracting audio via a URL will help your use case at all. Decoding directly from a URL doesn't...
@zzterrozz > would it be possible to extract the waveform as String of Json in order to store it and then use it to display the waveform instead of downloading...