![]() If you like AudioMass, and like the way it is built and it performs, perhaps you might enjoy working together with me. If anyone is interested on how it is built, and how the interface complexities are managed, even though it is just plain old school JS that has the reputation of being notoriously difficult to maintain, I would be happy to make a write-up shortly, or perhaps give a talk on it. Share your work! Do not be afraid to put it out there! ![]() Perhaps the javascript people would make fun of me for just using Vanilla JS.īut if this is impressive in 2020, imagine how impressive it would have been back in 2018! So I guess my point is. I guess I was afraid of sharing it to the world, perhaps the audio people would get mad at me for making mistakes with the audio api (like the fade in/fade out being linear). as I said I wrote this in June 2018, and just. The point is, I thought I was aware of all bugs, and all areas of improvement, and I am humbled to have my mind opened and see how valuable outside perspectives are! It's so easy get tunnel vision and think you know best I guess. I have been dog fooding it by using it to quickly edit foley audio from a tascam hand-microphone device, in order to make some cheap sound effects for a game project I am working on. First of all, I am amazed at the suggestions and love this is getting. macOS also sacrifices some low-latency when comparing the same hardware on it versus Linux (with raw ALSA or JACK) and Windows with ASIO.Īuthor again here! Now that this is finally sunsetting, I feel a bit more comfortable writing some things I 've learnt today! With my band we had tons of issues with a M-Audio card on windows fixating itself on the wrong sampling rate as soon as a desktop music playing was launched (this includes web browsers), entirely preventing playback on Ableton Live for instance. things crash or get stuck routinely, and I sometimes get random loud buzzes or no sound until I reboot. I mean, I have currently 5 soundcards on my desktop computer, 1 pro over PCIe, 2 pro over USB, 1 standard HD Audio and 1 output in my screen's HDMI, and I can assure you that even on windows it's definitely not a smooth ride between WASAPI, ASIO, MME, WDMKS. But instead of improving one or two audio APIs, on Linux it is time for a new audio server that will, but doesn't, solve all of the problems of every predecessor. > Easily, reliably, and quickly playing audio is table stakes for Windows and Mac OS. I wrote this in 2018, and just kept it on my hard disk until recently, so certain features might be slightly different than back then :) ![]() but I need to figure out the licenses of some libs I am using first (eg wavesurfer, lzma-wasm) and do proper attribution! To answer a few questions, I plan to have a very open license this is just a fun side project for me. play a bit more with the concept of having different windows that can be in different screens (check out the frequency analyzer under "view") ![]() Easier recording mode (like the ability to open a new empty audio project) Add some tutorials! Some things might not be straightforward like using Shift + for shortcuts etc. polish a bit some audio plugins (like the paragraphic EQ) since some parts feel a bit off (the limiter, paragraphic eq for example). redo drawing library to further improve performance! I am the author! Wow, I can't believe the attention this is getting! Hopefully this proves to be useful as a tool, and not just as a JS demo! :) ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |