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
Key Lime Canid
Alright I think I'm onto a bug. When the playback is paused and you then click a key on the virtual keyboard or the edit note clip keyboard (as far as I can tell it doesn't matter the instrument), it desyncs with the playback when it is played again. It is as if that clicking a key causes some sort of ghost playback to progress forward without playing anything until unpaused, making the visible playback out of sync and can even appear to skip over the loop.
rysiekg
Engine v.1.6.33 has been released. Problem with automation of volume and pan in Master Channel is fixed
rysiekg
@Dear all - Thanks to @Psycodelicnight - there is problem with parameter automation of Pan and Volume in Master Channel
KaI
@All, Guys! Make sure to check your email today. We've sent you a small update. Let me know if you don't get the email 🙂
KaI
@Kage Termia Feel free to post your track in any of the Share Your Sounds groups!
rysiekg
@Dear all - urgent question could users with Win7 as OS let me know if beta is working for you fine or not via email (ryszard@soundation.com) or PM
rysiekg
Beta is up and running
rysiekg
Beta is down, working on it
Kage Termia
@puddles For a temp fix just play a note early but make the volume on that note be 0
rysiekg
Dear all, @Triskelight - Engine v.1.6.29 has been released with fix of "jumpin at position freeze/stalls" - please let me know if you will be able to reproduce an issue when jumping at position.