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
MX RpKO
I pressed the keys while messing with the equalizer. I expected to continue to be able to press keys. Upon releasing the key, I was unable to press anymore keys until I let go of the knob on the equalizer. // Windows 10 // Soundation Chrome - Chrome Version 70.0.3538.77
MX RpKO
I pressed the play button on the bottom bar. I expected my song to start. I got nothing, but doing it a second time got it to work. - I pressed the keys on the virtual keyboard. I expected the sound. I got the sound, but with a noticeable delay that I did not hear when using the normal version // Windows 10 // Soundation Chrome - Chrome Version 70.0.3538.77
Ｐｕｄｄｌｅｓ
The misplaced virtual keyboard key started with the original studio not the new one
rysiekg
Engine v.1.6.13 has been released - WubMachine and SuperSaw should not crash with virtual keyboard.
rysiekg
I confirm freeze/crash when using keyboard with WubMachine and SuperSaw (I was not able to reproduce problem with other instruments)
Key Lime Canid
So I decided to try what WordOfTheDayIsYay did, and I got the same results. The very first time the studio froze, so I went back to this tab and closed the studio tab (It could not be closed in the frozen studio) and opened up a new studio tab and it did not freeze this time trying the same thing.
rysiekg
There was Engine v.1.6.9 pushed yesterday (CET) it should get rid of freezes whilst changing buffer size and significantly reduce probability of freeze whilst jumping at position. Please let us know if your observation of v1.6.9 confirms our tests.
rysiekg
@Unique - thank you, yes this bug is already queued
WordOfTheDayIsYay
So, I found a bit of a bug. I opened the studio, opened a new project, created an instrument channel as usual, ran my cursor down the keyboard on the side of the note clip (I like to do that, idk why) and then it froze. I opened my task manager and closed chrome and everything went back to normal. I haven't been able to replicate this bug though, so I'm not sure what could have caused it. (I'm using Windows 10 Home by the way)
rysiekg
Regarding to freezes whilst jumping at position. Until it will be fixed proposed workaround is it to jump once again to different position and jump back to desired position.