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
.
Great way to utilize the community to benefit the platform. 10/10, will do testing.
ChordsBoy
I am super excited to test this out! Thanks so much for being so interactive with the community :)
DUTCH
My operating system is Windows 10 Pro yes
By Studio version it says its ca55
KaI
@Keylime Pie Pls make sure your Chrome is version 70 otherwise you won't be able to access the studio (you'll get stuck at a loading page) 🙂
KaI
Thanks @Dutch (so fast!), can you let us know the studio version as well? You can find it on the top right corner. As for your operating system, I understand it's Windows 10 pro, is that correct?
DUTCH
Alright I found out the problem with moving the player: I had the buffer size on 1024 but when i put it on 2048 it suddenly didn't freeze any more. Even so in small project the player still freezes when the buffer is on 1024. Its only on 2048 that the player doesn't get any problems any more
DUTCH
Another finding! I opened up a track made out of a lot of premium loops, and when they fully loaded the names of the loops failed to appear. The loops were just blank. When opening up the track I was expecting it to open up as usual, which it did but it just didn't open the names of the loops.
DUTCH
-My operating system is Windows 10 Pro.
Studio version: ca55
Engine: v.1.5.3-7-ga8c6
DUTCH
-The last point is that the studio fails to load imported files when opening the track. I've tried multiple tracks already and in all of them the imported audio files (Very small ones, mainly kicks and snares) failed to load.
DUTCH
- Next thing I found is that the tracks do take an insane amount of time to load. For my most recent track, which isn't the most peformance heavy track, it took a whole 3 minutes to just load at the "open track" screen. For the track with over 60 channels it took over 5 minutes. And even when those tracks were loaded in they still wouldn't play untill after another 2 minutes.