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
mondaze.
orary shut down, it stood still and no buttons were usable. Then out of the blue it came back to life about a minute later
mondaze.
Just found i little bug with the virtual keyboard - I opened it up on a large sng file and found that the B key was chilling underneath the keyboard and the slot on the keyboard that it was from was shaded dark. Another thing that i observed is that after about 3 active channels (including an audio channel, all with about 6 or 7 effects), the studio began to lag quite a bit. In the song itself, about 8 - 9 tracks are active the majority of the time. After changing the buffer to every setting, it did not change. Might be my end. After enduring about 15 seconds of lag, the studio went into temp-
mondaze.
can verify @Dutch's observation, on SPC packs (purchased) the progress bar won't move, it just says infinity. However, the sounds play when you click the corresponding item. It just doesn't display the name of the sound, or waveform in the envelope. As far as I'm concerned, you can use those values in piano roll, so they are completely functional, they just aren't being displayed on the SPC dialog box.
mondaze.
Will be testing shortly, big props to the company for utilizing the community!
DUTCH
I managed to crash the studio as well @Chordsboy but my laptop wouldn't overreact. I just imputted a wub machine (Driven sub) and were using the keyboard of the note placement box when it suddenly all froze... I have no clue why this happened.
Also I had this time that when I pressed play I would hear nothing and had to pause and unpause first to get the sound playing again.
DUTCH
It won't let me load up the banging brostep spc kit. It just sais: "loading... infinity%"
ChordsBoy
Not sure if it's ever even this severe in the regular Chrome studio since I always keep the buffer size at the lowest there, but whenever I turn up the buffer size in this studio, the CPU really struggles, even with a quad core i7 (about 85% of my CPU gets used up by Chrome)
Key Lime Canid
@Kal that might have been it, I checked my home computer but forgot to check the lab computer.
ChordsBoy
Strangely I can't replicate the issue though, so it might have something to do with having both studios open
ChordsBoy
Alright, so while I was playing my song in the studio, I opened up the virtual keyboard, and then the studio froze, and my laptop fan started going crazy xD
I opened up task manager, and Google Chrome was using up 100% of my CPU. I exited out of the studio, but I had the normal studio open also, and that was freezing too. So I exited out of Chrome, and my laptop fan calmed down again. I have Windows 10 Home, the studio version was ca55, and the engine version was 1.5.3-7-ga8c6