Hi Testers, thank you for participating in a beta test of our new Studio!
What’s the plan?
We will open this group for at least a month for all testers to post bug reports and general feedback. Your insights will provide invaluable assistance in the fine-tuning of our studio before its official release in the coming months.
What’s new in the Studio?
We’ve made major changes from an architecture point of view so our new Studio has gained a major performance boost. More specifically, the new Studio is based on WebAssembly and is using components that are completely new in a browser. This helps us build a more powerful and stable Studio which in turn lets you create more demanding projects. While there are no new features added to the new Studio, this will facilitate any further improvements and added features in the future!
What should I do?
Make as many tracks as possible using our beta Studio: https://beta-studio.soundation.com (Important: Use this link only) on Chrome version 70. If you find any bugs in the process, please comment in this group with the information: What I did, what went wrong, what I expected + Operating system + Studio and Engine version
Is there anything I should be aware of?
Yes. Please find below more info on buffer size/latency and some known issues:
1. Buffer size vs. latency
• Increasing buffer size makes the Studio work more fluently, with less risk of glitches but with cost in latency (recommended for projects with long effect filter chains and/or many SendTo effect instances).
• Decreasing buffer size makes the Studio work with smaller latency but with cost in risk of glitches and fluency (recommended for simpler projects with shorten effect filter chains). Recommended buffer size is 512 or 1024.
• In case of complex projects and need of short latency, try to mute as many those channels which has the longest effect filter chains and then decrease buffer size to 256, 512.
2. Known bugs raised by testers (work in progress):
• Some presets of WubMachine (using Retrigger) differs in the beta studio
• The studio stops responding when used for a long time
3. Current Studio version 2.0.1 Engine version 1.7.1
4. Improvements added
• Import of flac
• Import of mp4 (including import of the AAC coded audio track from video mp4 file)
• Option to enable Turbo Mode to maximize CPU usage
What will I get?
In return for your help in scrutinizing our new Studio, you will get one item from our sound shop for free at the end of the testing period.
We really appreciate your time and feedback. If you have any questions feel free to post here. Now, have fun with our new Studio!
Team Soundation
👉 Access the beta Studio here: https://beta-studio.soundation.com
Comments
Lakota
When I try to play the virtual keyboard with the wub machine on any preset I cannot play more than one note. I also can't glide to another note as it won't produce any sound until I let go of the first key. Operating system: Chrome OS | Google Chrome Version 70
MX RpKO
I leave the program idle for about an hour or two. I expect it to work as usual. What happens is it doesn't work, refreshing it gives an error, but refreshing again seems to fix is, as it does with most issues // Windows 10 // Google Chrome Version 70
BASS BUNNY aka DJ VAVI BEAT
(vox // you really think electronica 140)..floats with me back and forth, won't stay put
rysiekg
@SHTAB - Thank you fir kind words and trying our new studio. There was quite big effort spent on it but since technology in some extent is brand new (not WebAssembly as such but some its elements) we did not mention that work is in progress due to risks caused by dependencies. We know that gain of performance is key thing to go forward and introduce those elements which you (users) consider as needed.
Futilitarian / shtab
I've been trying out the new studio for a few days, and I can say it's definitely an improvement over the old one
rysiekg
@Dutch "The mono glide.." yes, I confirm that bug it is in our queue
DUTCH
The mono glide doesn't work in studio. When you overlap notes so the mono will have a glide effect only the first note will work.
rysiekg
@rysiekg :) "Some presets of WubMachine differs in beta-wasm - looking for a reason and fix" -> seems Retrigger button from LFO Section of WM does not react
rysiekg
@Trystar @Shards "and the wub machine won't change notes.." has the same root cause - lastly pushed and (when kept pushed VK key) overrides MIDI sound from the track, when on our (https://chrome.soundation.com) pushing a key on VK overrides only one note from the midi (those which was played when key was pushed) no matter how long key is being kept pushed
rysiekg
@Shards I confirm "and the wub machine won't change notes at all if something else is playing in the same midi or in virtual keyboard" bug created in bugtracking