Hi,
since the 4.1 update I am experiencing a breaking issue, where using the split tool, on a region that is only partly in view (because it exceeds the screen area at the given zoom level), or moving a region TO THE RIGHT (not to the left!) makes the whole view jump. I can't really find reason or a pattern, sometimes it jumps to some place in the newly formed even, sometimes it jumps right back to the start. This happens with a completely vanilla S1 4.1 installation, on two different workstations, with no setting touched/changed from the default. I can work around most anything but this makes editing absolutely unbearable, and Studio One 4.1 de facto unusable to me. To be perfectly clear: What I am looking for is for the screen to not move at all, ever, when I make a cut, anywhere, at any zoom level, on anything. *Any* help towards that end would be very much appreciated. Thank you so much in advance, Jochen |
This probably won't help but for fun I suggest you update to latest display driver via third party sites
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Sadly, all drivers (on both workstations) are up to date. Can you (or anyone else) even replicate the issue? I am absolutely stunned that this issue seems to be flying under the radar.
|
jstummbillig wroteSadly, all drivers (on both workstations) are up to date. Just checking. You aren't assuming this just because you ran Windows update? Thx. And please give us your system and OS specs
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
No, that is not why I am assuming that :)
Windows 7 pro (2014) i7 something 16gigs ram ndivia gpu Windows 10 pro (2018) i7 something 32gigs ram intel gpu I don't have the exact components at hand and I am not in the studio to check right now but basically the two computers have nothing in common, apart from running a version of windows and an up to date studio one 4.1 with up to date system drivers. I also just tried it at home on my windows 10 laptop -- again, same issue. If anyone could just fire up studio one and try to replicate this, please? |
Guys have a look here at the german forum please. Someone found out what`s causing the Issue in your v4 and he has posted a video about how to reproduce this bug. It`s related to tempo automation:
https://forums.presonus.com/viewtopic.php?p=183637#p183637 |
Starting to feel I should have stuck with V3 till at least mid 2019. I think the bugs vs feature balance has definitely shifted. My fault I guess, I should not have upgraded so early.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Thanks a lot!
|
Yes, select Time Linear, this is a new bug with Beat Linear timebase in 4.1. Pretty frustrating when editing until you figure out how to avoid it
As usual resist the temptation/urging to reinstall all your drivers |
robertgray3 wroteAs usual resist the temptation/urging to reinstall all your drivers Because updating drivers is illegal, twelve rabbits get shot every day because of it. Updating drivers always breaks systems because we are still living in 1997. Right? Because trying something to see what happens should never be allowed when others have retrospective behind their belts. This is 2018, everbody should be keeping everything up to date in an online world. Of course if you are completely offline and not installing anything else whatsoever then who cares. Like I said do it for fun. Nothing to lose other than snarky know it all comments.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
PreAl wroteStarting to feel I should have stuck with V3 till at least mid 2019. I think the bugs vs feature balance has definitely shifted. My fault I guess, I should not have upgraded so early. I feel ya. Still haven't upgraded over here. Could consider buying an upgrade to version 4 if the price is amazing during a Black Friday sale or something, but without installing it until all bugs are sorted out. Version 3 does most of the job adequately as it is, really, and all in all it suits me better than any other DAW out there, so I'm good. |
BobF wroteTry right-clicking the timeline and select timebase = time-linear if it isn't already selected. Thank you!
OS: Win10 x64 || Software: Studio One Pro [latest version]
Hardware: AMD Ryzen 9 3950X || Asus Prime X570-PRO || 64GB DDR4 RAM || Asus Dual-RTX2070S-A8G-EVO || UAD2 Octo & Duo PCIe Peripherals: RME Fireface UFX II (+2x ADA8200) || Faderport Legacy || Atom || NI Komplete Kontrol A25 Audio Settings: 44,1/48kHz, 256 Samples, DP Off, 64 Bit |
briandeeley wroteThank you so much!!!! Yeah I’m glad there’s a workaround, between this and the bug with drag and drop duplicating tracks with layers 4.1 is actually a bit annoying for my vocal work. Which is tough because it’s more stable for my other work |
robertgray3 wroteNot illegal, just a colossal waste of the op’s time Thankyou SO much for your retrospective judgements. Really helpful for these forums I'm sure. Keep up the good work. "As usual resist the temptation/urging to reinstall all your drivers" - meh.
Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb. Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental). Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths. |
Thanks guys for pointing out the 'timebase' solution. I just searched the forum for answers on this weird problem and luckily found this thread. Let's hope it will be fixed on the next update.
Asus X99-A, i7 5820K 6-Core (4.2Ghz With Multiplier), Corsair 32Gb DDR4 RAM (2133 C15), 1 Samsung 840 PRO 512GB SSD, 2 Samsung 840 PRO 1TB SSD, 2 Samsung 850 EVO 2TB SSD, 2 Western Digital Caviar Black 4 TB HDD, AMD Firepro 2460, Win 7 64 Bit, USB 2.0 + 3.0 Ports, UAD-2 Octo Core PCIe, TC Powercore Express PCIe, Studio One Pro [Latest Update] 64 Bit
|
Users browsing this forum: No registered users and 50 guests