[DAW v DAW - Part 2: Automation Speed]
(http://www.admiralbumblebee.com/music/2 ... io-one-450) “Yes, it gets worse. Unsurprisingly it’s the reigning champion of sucking at automation: Studio One. The normal 1600 sample (800 on both sides of transition) window was *way* too small. I had to render the entire file in a single image with a 57,600 window. In the large image, each block is 1,920 samples on the X-axis. That’s a 15,360 sample fade. 48 samples is 1ms. 320ms fade when then visual feedback, and what I entered, is a sharp transition.”
MacMini M2 Pro
Memory: 16 GB OS X latest version Apollo X6 Thunderbolt Studio One Pro latest version https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ |
I just finished reading the other thread where automation noise issues with fade in/out was discovered by the same guy who wrote the above article. Towards the end of that thread, I was happy to hear that the automation noise problems were fixed in Studio One v.4.5. But now the same guy discovers another issue, now regarding automation timing.
Nooo! |
If the guy wants to contact Support about the issue then fine. Why post his thread here on the forum if you have not tested this for yourselves?
Do you find an issue with this on your system? |
I ran the test in 4.5. This is broken in 4.5. The OP is correct it is nearly a 300 ms fade either side.
In 4.1.4 it was instantaneous for me going from max level to silence level. And only 1 mS coming back back up from silence to max level. It is around 1mS either side for Ableton Live 10 as well. I am sure this is easily fixed similar to the automation noise.
Specs i5-2500K 3.5 Ghz-8 Gb RAM-Win 7 64 bit - ATI Radeon HD6900 Series - RME HDSP9632 - Midex 8 Midi interface - Faderport 2/8 - Atom Pad/Atom SQ - HP Laptop Win 10 - Studio 24c interface -iMac 2.5Ghz Core i5 - High Sierra 10.13.6 - Focusrite Clarett 2 Pre & Scarlett 18i20. Studio One V5.5 (Mac and V6.5 Win 10 laptop), Notion 6.8, Ableton Live 11 Suite, LaunchPad Pro
|
Bbd wroteIf the guy wants to contact Support about the issue then fine. Why post his thread here on the forum if you have not tested this for yourselves? Good day! I'm "the guy". I stopped contacting Presonus support after repeated instances of the support personnel not understanding what I was reporting. Being given basic troubleshooting instructions in response to a mildly complex (and detailed) bug report is absurdly frustrating, Having it happen multiple times is a sign. Presonus released the software in this state, so here we are. If they wish to have me test their software, then I would be more than happy to do so in a detailed and professional manner as I have when contacted by numerous other developers. I LOVE software testing and documentation. Until then... I'll just have fun investigating software. I always update content when I see bugs fixed as well. I also make an effort to note versions tested, provide reproduction instructions and urge people to not trust me (and do the work themselves). Hopefully these actions show that I'm trying to be fair as possible. |
Jose7822 wroteI just finished reading the other thread where automation noise issues with fade in/out was discovered by the same guy who wrote the above article. Towards the end of that thread, I was happy to hear that the automation noise problems were fixed in Studio One v.4.5. But now the same guy discovers another issue, now regarding automation timing. The next article coming on the topic isn't particularly flattering to S1 either... I don't plan it this way, and personally I have a bias towards S1 since it's what I do all of my drum editing in no matter what other DAW I'm using. It would be wonderful if I could just switch to it and not constantly be annoyed by these sonic deficiencies (or the lack of notation). I'm in the cheer camp. The sooner S1 is super awesome, the sooner my life becomes simpler. I have a similar bias for Tracktion Waveform for similar reasons. I'm an unabashed fan of it, and it's also "failing" these tests. If this particular issue fixed in a timely manner, I promise to make an update video specifically covering it. As always, I'll edit previous articles with updates as well. If anyone feels that I can improve this content, Im always open to ideas and criticism. Fairness and accuracy are my #1 concerns. |
robertgray3 wroteThanks for doing these tests admiralbumblebee. Pretty illuminating. Hope it gets addressed. Indeed!
MacMini M2 Pro
Memory: 16 GB OS X latest version Apollo X6 Thunderbolt Studio One Pro latest version https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ |
Admiralbumblebee,
I think you’re already doing a great job. Please keep doing what you’re doing! To be honest, I’m finding this version of Studio One to be a bit buggy. So far I’ve only experienced one crash, which is not a big deal. Studio One almost never crashes on me. However, I’m now experiencing issues recording an audio part where there’s a tempo change right before the measure I start recording. The audio plays back at twice the speed (similar to what a Sample Rate mismatch sounds like). Also, my console faders keep shrinking for no reason, so I have to keep adjusting their size vertically. Lastly, I was having a weird behavior where Studio One would sort of lock up graphically when using the MIDI editor in Superior Drummer 3 while the project was playing back. It’s almost like I lose focus away from SD3, so I have to stop the project in order to regain it. IOW, I wouldn’t be surprised to read a not so flattering post about Studio One 4.5. BTW, I know that this is not the place to report these bugs. I’ll report them directly to support when I get a chance to find out how to reproduce these reliably. But this, in MY experience, is the buggiest version of Studio One so far. That said, I’m sure Presonus will be able to get Studio One back to being its usual awesome self in no time. They always do . |
Jose7822 wroteBTW, I know that this is not the place to report these bugs. I’ll report them directly to support when I get a chance to find out how to reproduce these reliably. But this, in MY experience, is the buggiest version of Studio One so far. That said, I’m sure Presonus will be able to get Studio One back to being its usual awesome self in no time. They always do . I think it is important to report bugs in the forum, it can confirm and / or avoid them. cordially |
Confirmed also. This is really bad the amount of data missing in the fade down and extra data added in the fade up makes automation usless. It's not even close to what you want it to do.
I hope they fix this one asap. back to 4.1.4 till they sort this mess out. |
admiralbumblebee wroteBbd wroteIf the guy wants to contact Support about the issue then fine. Why post his thread here on the forum if you have not tested this for yourselves? Thank you for all your time and hardwork doing the testing. I have had issue with Persons support in the past and not listening and testing what I have discovered, very sad tbh. Keep up the great work, and lets hope Presonus starts reading some of these forum posts! Best Scott
Studio One Professional v6, Apple iMac Pro 14 core, 128gb memory, 4TB SSD. macOS Ventura, Main audio interface is RME Babyface Pro. Presonus 192, DP88 (not currently used), RC500, ADL600, Focusrite ISA430, TC4000 reverb, SPL Phonitor, Monitoring: Event Opal, IK Multimedia MTM Studio Monitors x 5, DMAX audio Super Cubes. HD800s mastering reference headphones. Sequential Prophet 12, Prophet 12 modules x4, E-MU 4XT Ultra, Roland Fantom 8, Korg Pa3x, Roland Fp7-F, MOTU midi express 128, Xkey air 37, Studiolive CS18, Atari STE with Notator plus loads of microphones and plugins etc
|
Does this apply only to rendered stems, or (also) to the normal playback?
Maybe it has absolutly nothing to do with this problem in this thread, but i remember having a volume automation on a heavy kickdrum from mute to instant "in", on the begin of the kickdrum, and i could hear clear that the kickdrum audible to late. Just like i would have a bad cutted sample. Like if the automation was to late.
Last edited by lfo2k on Mon May 27, 2019 12:29 pm, edited 1 time in total.
|
Thanks to @admiralbumblebee for this info -- gotta say, this is very frustrating. I'm going to confirm this stuff today for myself if possible. If I confirm this, I can't trust the timing, I need frame-accurate time since I work with picture. Not happy about these automation issues (and the fade issue from the other thread). Good grief.
|
lfo2k wroteDoes this apply only to rendered stems, or (also) to the normal playback? It happens on on renders and playback. This is a 4.5 only issue as far as I know. 4.1.x does not exhibit this behaviour. I've tried to find a workaround, and I have been unable to find one. Even mute automation is affected (it triggers late). |
Thanks, Bumblebee.
You have found bugs in the software and in "the system" for reporting them. Let's stop killing the messengers and start fixing this software and its official support service. Not much use in having tech support if they're not technically qualified to help you—or perhaps it's just a lack of motivation in some who don't like their job anymore... I won't be updating to 4.5 on my PC. I think this is the 4th time I've avoided an update until it was fixed by a subsequent update.
Last edited by roland1 on Mon May 27, 2019 12:26 pm, edited 2 times in total.
Studio One Pro (v5) on i7 7700 win10 PC w16GB RAM and a Mac Pro Tower (w/RME & Focusrite interfaces.)
I use S1 as an author/musician/multi-media artist. My work includes the newly released: Clearing a Path to Joy (And finding contentment along the way) [AuroraSkyPublishing.com] and my upcoming music video, Too Big To Fail, which introduces Citizen Based Social Planning — "the next step in the evolution of democracy." You know...typical everyday stuff. |
admiralbumblebee wroteBbd wroteI stopped contacting Presonus support after repeated instances of the support personnel not understanding what I was reporting. Being given basic troubleshooting instructions in response to a mildly complex (and detailed) bug report is absurdly frustrating, Having it happen multiple times is a sign. I think support is not for that kind of very indeep problems. They can help for simple problems most people experience, but not for very techy stuff. |
So who is supposed to do the real techie stuff, us here on the forum?
lfo2k wroteadmiralbumblebee wroteBbd wroteI stopped contacting Presonus support after repeated instances of the support personnel not understanding what I was reporting. Being given basic troubleshooting instructions in response to a mildly complex (and detailed) bug report is absurdly frustrating, Having it happen multiple times is a sign.
Studio One Pro (v5) on i7 7700 win10 PC w16GB RAM and a Mac Pro Tower (w/RME & Focusrite interfaces.)
I use S1 as an author/musician/multi-media artist. My work includes the newly released: Clearing a Path to Joy (And finding contentment along the way) [AuroraSkyPublishing.com] and my upcoming music video, Too Big To Fail, which introduces Citizen Based Social Planning — "the next step in the evolution of democracy." You know...typical everyday stuff. |
roland1 wroteSo who is supposed to do the real techie stuff, us here on the forum? You can see why Ableton adopted the model they did where basically any user who really cares can sign up to chime in on the software. I don't know how well it actually works for them but it makes sense. If you volunteer to give feedback, it feels a lot better when you're having to report issues than if you never signed up to in the first place. |
Users browsing this forum: No registered users and 42 guests