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
@ChromeClouds "CPU has issues.." Please submit here anything you found with beta-wasm it give us a chance to queue, prioritize and fix those bugs. Just note at the side - from CPU point of view code is different, many things has changed - it was necessary to fit into WebAssembly and AudioWorklet requirements.
rysiekg
@ChromeClouds "More than 5 midi tracks playing at once= lag". Any particular five midi, any particular instrument, with or without filter effects? What is your CPU? What buffer size do you use is there any other program running which is CPU demanding and finally did you try Turbo Mode?
rysiekg
@KristleTribble - Reverb should be ok, Engine v.1.6.19
KaI
@Trystar Some work on plugins integration has already been started and we're working through some limitation of WebAssembly atm. This might take some time but we're working on that!
rysiekg
@KristleTribble - Thank you, definitely it is a bug, I need to test effect by effect, knob by knob once again since I missed it previously. I will keep you informed.
Trystar
You should consider adding in more electronic instruments especially : sub bass, and risers and also a big one would be ability to add plugins.
KristleTribble
I had loaded a .sng file from the non-Beta side of Soundation. Both of the channels on the file have a reverb fx, size 85% and the rest of the dials set to max. Soundation played both channels with no reverb fx. I attempted to correct this with both turning bypass on and off, and then resetting the entire fx setting. Both methods had no effect. I wonder if reverb has yet to be added to the Beta version, or if this is an actual bug. System: Windows x64 Studio: Beta v. 1.4.0-13-gfba8 Engine: v. 1.6.15
rysiekg
@Dutch Yes, thank you for a good idea!
DUTCH
Regarding the turbo modus I think it's nice if there would be some kinda pop up that would explain what it does so people wouldn't accidentally turn it on with no idea what it does
Lovecraftia
Hmm. I've noticed that whenever i run between different audio pitches that the audio will sometimes stop altogether, and won't return. When i attempted to return to the studio, everything was frozen, like it was trying to load but was unable to. Is this an issue with my internet or CPU power? I believe its my internet, but i can't be sure. anyway thank you for allowing me to be part of the Beta test, i'll use every time i make a "song" (I'm still learning to use the effects and editing the synths and all that) and i'll point out anything i notice seems.. off or not anticipated.