BobF wroteLet's not forget that those 2 months included a major, annual holiday/vacation season. I'm surprised that there was a release big or small in mid January. It's actually been 2.5 months, that allows a couple of extra weeks for the holidays so I don't see this being a factor.
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 wrote It's actually been 2.5 months, that allows a couple of extra weeks for the holidays so I don't see this being a factor. Let's not forget that "the holidays" usually start on or about Dec 20 for most folks (regardless where you live) and end around the middle of the first week of January - so I am not buying any suggestions that the day after the last update (Nov 1) - Presonus decided to shut down, take a 10 week break and then suddenly decide it was time to shake the eggnog and pine needles off of themselves and release a 6.52 with just 5 items. There has to have been something more substantial going on over there than just this since Nov 2, 2023. VP
DAW: Studio One Pro 6.6.1.99821 | Host OS: Windows 10 Pro 22H2 | Motherboard: ASUS PRIME z790-A | CPU: Intel(R) Core(TM) i5-13600K | RAM: Corsair Vengeance LPX 64GB | Graphics: Intel UHD 770 (HDMI) | Audio Interface: RME UCX II (v1.250) | OS Drive : Samsung 990 PRO (1TB) | Media Drive: Samsung 970 EVO Plus (500GB) | Libraries: Samsung 970 EVO+ (2TB) | Samples : Seagate FireCuda (2TB) | Monitoring: Presonus Monitor Station v2 + Presonus Eris 5 | MIDI Control: Native Instruments Komplete S61 & Presonus ATOM
|
Vocalpoint wroteThe positive vibe that I am taking from this very sparse release is that if there are more 6.x releases in the pipeline - the next one (v6.6.x) should be worth waiting for I'm hoping they are well on to 7.0 right now. If we do get 6.6, I will be surprised (and delighted), but looking at past releases, I assume they are winding down the 6.X product cycle.... But who knows, maybe one more point release for a victory lap, so maybe 6.6 is coming in the Spring? I'm sure they are working on more than one thing of course, it's a question of how generous they want to be with the 6.X series and throw us another golden nugget before charging us some more money for 7.0. In any case, the 6.X lifecycle has been jam packed with good features and some nice surprises, plus two full-on cardiac SHOCKERS (immersive sound and Linux support, WOW!). The 6.X cycle has been a truly excellent value IMO. Another update like a potential 6.6 would be ultra generous in my book. TBH, looking at the last few years, I was skeptical of the Fender acquisition. But Presonus has continued to stay the course, and it seems like Fender has left the Hamburg team alone... my hope in humanity has increased slightly.  THANK YOU TO FENDER! PLEASE LET HAMBURG CONTINUE TO WORK THEIR MAGIC! And of course A HUGE THANK YOU TO PRESONUS for such an outstanding DAW. Just one tiny request if the Presonus devs read this... could you guys please PLEASE improve the ripple editing? Just a little? The current ripple editing is okay (and thank you for it), but it's still missing the fluidity and options of the Reaper ripple editing and even the WaveLab Audio Montage ripple editing. Just a little more magic would push your ripple editing up a notch and bring a little more peace and tranquility to the universe. Cheers! |
NoiseCoalition wroteDisappointing to see that the pan bug when exporting stems still exists. Stems still do not export with panning information when exporting in "track" mode. Support confirmed it as a bug in November. Are you sure you don't have the modes mixed up? I can export stems in Track mode that retain panning information, whether as Balance, Dual Pan, or Binaural. However, exporting stems in Channel mode doesn't retain panning information from any of these. If it's essential to retain panning while exporting in Channel mode, the workaround is to use the Dual Pan as an insert. Then, stems exported in Channel mode will retain the Dual Pan panning information. I'm pretty sure I got this right, but please feel free to confirm or point out why you might think I'm getting different results.
Digital storefront: craiganderton.com
Free educational site: craiganderton.org Music: youtube.com/thecraiganderton Studio One eBooks: shop.presonus.com |
|
Has there been any acknowledgement from Izotope or Presonus re non-functioning Audio Units in 6.5.2? Just had a client request revisions to a mastering project from about a year ago that I think is going to be full of them 🤦
Edit: just clocked the release notes. Fingers crossed! |
scissorkicks wroteHas there been any acknowledgement from Izotope or Presonus re non-functioning Audio Units in 6.5.2? Just had a client request revisions to a mastering project from about a year ago that I think is going to be full of them 🤦 They fixed it! First thing I checked on 6.5.2 yesterday. |
tremo wrotescissorkicks wroteHas there been any acknowledgement from Izotope or Presonus re non-functioning Audio Units in 6.5.2? Just had a client request revisions to a mastering project from about a year ago that I think is going to be full of them 🤦 Spoke too soon. Izotope AU plugins now work properly on channels, but NOT on busses! In fact, now even the VST3 versions don't process audio on busses. One step forward, two steps back... and back to 6.5.1 for me.  DISREGARD! Must have been a system glitch. Restarted Mac and both AU and VST plugins are working fine on busses. Sorry.... |
|
Not sure what you guys did, but my system (Windows 10) had been sailing along just fine with multiple projects.
After installing the latest update I have nothing but instability, loss of MIDI devices, crashes (usually hung up), and the system with my control surface is now freezing up. Can no longer work steadily on any of this. How convenient, just a week before my lease renewal. Please fix this mess I've really enjoyed using Studio One the past year. It's worked like a dream, but now it's turned into a nightmare. Disappointed !!! Dave |
davidg25nc wroteNot sure what you guys did, but my system (Windows 10) had been sailing along just fine with multiple projects. So didn't you install it in a new folder so you could do 1:1 comparisons to make sure it was really related to the new version (which I don't think it is)? However, this is not a problem, as you can still easily reinstall the previous version and then cross-check it. So no need to panic.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
So didn't you install it in a new folder so you could do 1:1 comparisons to make sure it was really related to the new version (which I don't think it is)? I've never had to "install to a new folder," as everything always worked. Thanks, I'll try to go back a version and hopefully that will be OK. Honestly, everything was rock solid before installing this update, so I'm not sure of your other implications. I've installed nothing else on this computer and it was FINE. Dave |
davidg25nc wroteSo didn't you install it in a new folder so you could do 1:1 comparisons to make sure it was really related to the new version (which I don't think it is)? Yes, but since you haven't double checked that a Windows update or other changes haven't taken place in the meantime, it's better to be safe than sorry. So it's better to install the new version in a new folder, especially for such cases.
Lukas Ruschitzka
Studio One Specialist Studio One Tutorials || Studio One Scripts & Add-ons || Studio One Tutorial Database || Studio One Toolbox [ s1toolbox.com ] Core i7 3.24 GHz, Windows 10, 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5 Clavia Nord Stage 3 - Moog Sub 37 - YAMAHA MoXF6 - M-Audio Axiom Pro 61 - Kawai ES-920 - Studio One 5 - Notion 6 - Orchestral Tools Junkie XL Horns, ProjectSAM Symphobia, Cinematic Studio Series, Strezov Sampling Afflatus, VSL Synchron Special Edition, KOMPLETE 9 Ultimate |
|
Thank you. I'll try rolling back the last Windows update. Just because I didn't install anything doesn't mean Windows didn't !
Appreciate the help! dave |
|
Anyone else still get CPU spikes when using ProEQ?
I get CPU spikes here with many things no matter how big the buffer is or 'dropout' protection etc. Using the File browser Adding Plugins Removing Plugins Disabling Plugins ...
Presonus StudioOne 6, Apple Logic
__ macOS, macMini M1 1TB SSD / 16 GB RAM, MOTU M2, Behringer X-Touch & 2*X-Touch Extender, https://ansolas.de |
davidg25nc wroteThank you. I'll try rolling back the last Windows update. Just because I didn't install anything doesn't mean Windows didn't ! Pay special attention to any changes in the sound and audio settings. Sometimes Windows "helpfully" re-installs drivers I specifically didn't want. Also check your preferences to make sure the correct interface is still chosen. Sometimes I've seen it flip to the FL Studio generic driver that's also installed on my computer, which wreaks havoc with Studio One compared to the PreSonus Studio USB drivers for my 1824c interface. FWIW the update has been rock solid here on Windows 10. It's definitely possible to attain stability once you discover the cause of the instability.
Digital storefront: craiganderton.com
Free educational site: craiganderton.org Music: youtube.com/thecraiganderton Studio One eBooks: shop.presonus.com |
|
Hi does anyone know why i may be having all these major delay compensation issues?
When I send he track to an FX channel with the analog delay the first issue is that when also have the same track going to a bus, the Bus is not compensating for the delay on the FX channel and so I am getting extra hits that are fluttering. In other words when there is a send to an FX channel but the output of the track also goes to a bus this is fluttering back an extra unwanted delay in addition to the analog delay's single delay. I cannot have this thing not compensating for all my stuff automatically. And even when i dont have the simultaneous bus, I am not getting any delay compensation at all even when having tghe send go to the FX bus while the output of the track go to the main output just like the FX output goes to the main output. And on top of this the issue is even worse when I have the metronome going at the same time. All of it is delayed after the metronome even the instrument track. This is unacceptable for any DAW to be doing this. Can anyone please tell me if there is a fix? because the manual says all delay compensation is automatic. Not even close on many levels here. I dont get any of these issues in pro tools. |
viccapota wrote... the Bus is not compensating for the delay... If you have time, please create a small project which reveals that issue and send it to presonus, so that they can easily reproduce it.
Presonus StudioOne 6, Apple Logic
__ macOS, macMini M1 1TB SSD / 16 GB RAM, MOTU M2, Behringer X-Touch & 2*X-Touch Extender, https://ansolas.de |
viccapota wroteWhen I send he track to an FX channel with the analog delay the first issue is that when also have the same track going to a bus, the Bus is not compensating for the delay on the FX channel and so I am getting extra hits that are fluttering. I think the following replicates what you're describing: Track send goes to FX Channel, track output goes to Bus. The FX Channel has an IK Multimedia Stealth loaded. This is a CPU-intensive mastering processor with 104 ms of latency. There is no difference in the timing between the Bus and the FX Channel. Could you please provide some more details if your track setup is different.
Digital storefront: craiganderton.com
Free educational site: craiganderton.org Music: youtube.com/thecraiganderton Studio One eBooks: shop.presonus.com |
Anderton wroteviccapota wroteWhen I send he track to an FX channel with the analog delay the first issue is that when also have the same track going to a bus, the Bus is not compensating for the delay on the FX channel and so I am getting extra hits that are fluttering. Hi Anderton. The PDC error doesn’t happen to me in such a small example. But in a medium sized session I’m working now, I’m trying to use the TrackSpacer plugin in my Stem Buses and when I used it stuff starts to really drift in time. It’s a terrible feeling not being able to trust the DAW for this stuff. I don’t think my template is over the top. I really expect my DAW to handle it when I’ve seen templates with hundreds and hundreds of tracks for film scoring for example. |
OneFingerSnap wroteWhen I send the track to an FX The PDC error doesn’t happen to me in such a small example. I think Viccapota was referring to a simple project where he had this problem. I was hoping that whatever caused the problem could be isolated within a simple, reproducible project, to see if there was a workaround. Beyond that, I can't be of much help. I do some pretty complex projects involving buses, sends, and plugins, but don't have issues.
Digital storefront: craiganderton.com
Free educational site: craiganderton.org Music: youtube.com/thecraiganderton Studio One eBooks: shop.presonus.com |
Anderton wroteOneFingerSnap wroteWhen I send the track to an FX The PDC error doesn’t happen to me in such a small example. Thanks Anderton, it would be great if a small, easily reproducible session caused the issue, it would be way easier to fix. The problem for me is my session is a real working project, that’s somewhat large in terms of audio files and it’s in this session that the problem arises towards the end of the mix when the session already has some “weight”. Do you know the best way for something like this, requiring downloading a large file, to reach someone that can actually investigate the problem? Thanks! |
Who is online
Users browsing this forum: No registered users and 8 guests