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
rysiekg
@Shards Thank you, let's start from crackling - this should not happen (or should be significantly reduced in comparison to our base version). In other words (https://beta-studio.soundation.com) should be better than (https://chrome.soundation.com) when using the same audio project on both. Could you confirm or deny?
Shards
just updated chrome from version 70.0.3538.77 to 70.0.3538.102 and those glitches still happen
Shards
and there's also a lot of crackling
Shards
and the wub machine won't change notes at all if something else is playing in the same midi or in virtual keyboard
Shards
also happens in normal studio
Shards
when u do fullscreen mode u can't right click
(as in, pressing view then fullscreen)
Shards
yea, its mono so it cant do chords
Key Lime Canid
@Trystar doesn't the wubmachine normally not produce chords? Kinda like the mono synth, the wubmachine plays one tone, but you are able to glide the tone to overlapping notes (Much like the mono synth as well).
rysiekg
@Kage Termia - I will contact you on PM
Kage Termia
If it helps I can post a video on my issue for you to watch?