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
Trystar
when holding down chords on the wub machine it only plays the last note pressed and not the full chord
rysiekg
@COLE JACKSON - I pushed Engine v.1.6.19-1-g4660170 with modified GM-2, made tests and seems that now it is ok. Since this was data race error (and I would like to introduce this fix to all instruments) could you, please, reproduce this issue once more and let me know? If you will confirm that it is fine I will populate change to other instruments at the morning (CET time) and merge it before weekend.
rysiekg
@COLE JACKSON - Thank you a lot for narrowing scenario down! I confirm - I managed to reproduce this issue.
kiLL spyro
Testing a bit more, it only happens with yamaha grand piano on gm-2.
kiLL spyro
When editing a note clip, if you press down the keys on the side and swipe up whilst holding your mouse click down, it will crash the studio
rysiekg
@ChromeClouds - If below steps did not help anyhow, please - send me exported sng (ryszard@soundation.com)
rysiekg
@ChromeClouds - Firstly try different buffer sizes (bigger ones) as mentioned in this group header, bigger buffer -> smoothness in exchange for increased latency (Settings->Edit Settings->Buffer Size). Than if still there is a problem (Settings->Edit Settings->Turbo Mode) it will lower probability of glitching caused by other CPU demanding applications run in background (it was done for Hack Attack use case with screen recorder, here cost is power consumption and due to that also quicker rotating coolers..
rysiekg
@ChromeClouds I am worrying about result of your stress test, since I have 4 core machine (with 8 cpu threads) with base clock 2,6GHz and just checked 50 SimpleSynth, reverb on each and in every had MIDI 80_RnB_Love_Keys_02_C.mid glitch less (no cracklink)
rysiekg
@ChromeClouds Thank you for the response. 8 core CPU would mean that audio processing is done in 6 threads and you should have performance gain (in comparison to our official version - based on PNaCL). However comparing online DAW with other non-online DAW is comparing software executed in sandbox with one executed directly on CPU and playing with audio drivers directly.. Please if you would like to judge and compare with DAWs, please compare us with other online ones. ok, now will write about turbo mode.
rysiekg
@ChromeClouds AFAIR all mentioned features/improvements you already submitted (they are queued) or something is new in comparison to "Ideas and Feedback" group, just do not want to miss something?