leosutherland wroteMaybe not the place for it, but in everyone's opinion (OMG, THAT's opening a can of worms ) is the general state (bugs, features, improvements, etc) of v5 now conducive to my upgrading from V4? It's early days with this patch, nobody has identified any serious issues yet.
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 wroteleosutherland wroteMaybe not the place for it, but in everyone's opinion (OMG, THAT's opening a can of worms ) is the general state (bugs, features, improvements, etc) of v5 now conducive to my upgrading from V4? I am working on a project currently, in V4, so obviously I'll keep on V4 for that. I was meaning if it worth upgrading to V5 for new stuff, or stick with V4, that's all
...said Halo
Studio One Pro v4.6.2 / v5.5.2 / v6.6 Serum, Diva, Synthmaster, MTron Pro, Kontakt 6/7, Cherry Audio synths, Battery 4 etc ad nauseam 3XS SQ170 Music Studio PC Windows 10 x64 (22H2) i7 8700 Hexcore 3.2GHz, 16GB, 2TB 970 EVO+ M.2 NVMe SSD + 1TB SATA HD Scarlett 2i4 (G2), Korg Taktile 25, Faderport 2018, Maschine 3 Beyerdynamic DT990 Pros, JBL 305P II speakers |
leosutherland wroteI am working on a project currently, in V4, so obviously I'll keep on V4 for that. I was meaning if it worth upgrading to V5 for new stuff, or stick with V4, that's all please note that for V4 you need Melodyne v4, for V5 you need Melodyne v5, any other combination is not supported, i.e. at your own risk and nobody will help you. and yes, you cannot have Melodyne both v4 and v5, when you upgrade to Melodyne v5, your v4 becomes invalid. V5 seems pretty stable for me, but if you're finishing the project and would like to keep V4 for it, keep using V4 for now and that's it. |
vasilykorytov wroteleosutherland wroteI am working on a project currently, in V4, so obviously I'll keep on V4 for that. I was meaning if it worth upgrading to V5 for new stuff, or stick with V4, that's all So how come Melodyne V5 works in both S1 V4 and V5 for me? I havn't used Melodyne V4 sinse we got a free update to V5 in both Studio One V4 and V5. Maby it's the Melodyne product type i don't know but the included essential works no problem. |
Notes still get stuck using the qwerty keyboard as the midi input source with vst's. They don't get stuck when using the stock instruments however. I've been producing on a laptop ever since I bought it some months ago and needing the ability to use the qwerty keyboard to play the instruments has been the determining factor on deciding which daw I'll be using or whether I'll be making beats or not. I would love to see this fixed possibly in the next update.
|
garyanderson5 wroteSo how come Melodyne V5 works in both S1 V4 and V5 for me? that's great to hear! to be frank, in my workflow having the perfect working Melodyne Studio is a must, that's why I didn't try this combination and updated both to v5 at once. I recall reading somewhere at Celemony that they test and support v5 with S1 v5, not with the older ones. in fact, I made a long journey with Melodyne and remember the 2-3-4 upgrades as well and there were some problems in the past. to sort all them out, I use Melodyne and Studio One versions that are claimed to be compatible, so that if anything goes wrong, I can contact the support and get this sorted out. |
why does it crash so much ? i turned of auto save , my computer does nothing but studio one . plugins are up to date which took ages . windows i7 16gb ram no heavy processes just small projects but really random freezes . love this software so much but its the most buggy i have ever experienced . seems with every update it gets worse . frustration
|
snb1 wroteNotes still get stuck using the qwerty keyboard as the midi input source with vst's. They don't get stuck when using the stock instruments however. I've been producing on a laptop ever since I bought it some months ago and needing the ability to use the qwerty keyboard to play the instruments has been the determining factor on deciding which daw I'll be using or whether I'll be making beats or not. I would love to see this fixed possibly in the next update. Do they get stuck if you use a real keyboard or other controller? Can you give an example plugin where this occurs?
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 wroteDo they get stuck if you use a real keyboard or other controller? Can you give an example plugin where this occurs? Everything works fine using a midi keyboard controller or any other midi controller. An example plugin would be Initial Audio Heatup 3. |
weswild wrotewhy does it crash so much ? i turned of auto save , my computer does nothing but studio one . plugins are up to date which took ages . windows i7 16gb ram no heavy processes just small projects but really random freezes . love this software so much but its the most buggy i have ever experienced . seems with every update it gets worse . frustration No issue here, I suggest starting a new thread to try and troubleshoot it with your full specs and details in your signature. If the whole computer is freezing that points towards a hardware or driver issue. Check the windows event viewer, show us any error message etc... On the new thread.
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. |
snb1 wrotePreAl wroteDo they get stuck if you use a real keyboard or other controller? Can you give an example plugin where this occurs? Create a ticket with support I suggest.
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 wroteCreate a ticket with support I suggest. I did. They said that they were aware of the problem and for me to look for a fix in an upcoming update which I thought was going to be this one lol. Maybe the next one. |
vasilykorytov wrotegaryanderson5 wroteSo how come Melodyne V5 works in both S1 V4 and V5 for me? --- Is there documentation somewhere that says Melodyne 4 isn't supported in S1v5? Because I had Melodyne 4 Assistant back when S1v5 came out, and didn't want to "downgrade" to Melodyne 5 essential, and was specifically told by Presonus Support that I could stay on Melodyne 4 Assistant with no problems....so I did...until Celmony ran a sale on the Melodyne 5 upgrade. It was almost a year. I had no problems whatsoever.
Win11, 12th Gen Intel Core i7-12700K (3.60 GHz), 32GB Ram. Focusrite Scarlett 8i6 3rd Gen. Native Instruments Komplete Kontrol S88 Mark 2, Native Instruments Komplete Kontrol S61 Mark 1, Presonus FaderPort 8.
https://www.midiboy.com https://gregghart.bandcamp.com |
I have v4 Assistant and it works in 5.5+ (I didn't feel like upgrading)
gregghart wrote---
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. |
When seeing this fix on the list:
● Stuck "packaging" status window when (auto-) saving I was really hoping the "freeze" (5-10 seconds) that happens when saving/autosaving songs was fixed, but it is not. This is a real workflow killer. After some quick research, I was surprised to see that this has been discussed since 2019 in the Questions and Answers section...... N.B.: The only way I've been able to "avoid" this S1 behavior is by disabling my network adapter. If others can replicate this, please let me know. Not sure if the program attempts a communication of some sort, causing it to become momentarily unresponsive while saving files. Hopefully, this can be fixed for good in the next update. Rock on |
This depends on the exact issue you're to referring to. Do you mean the modal dialog that appears while saving (which can't be avoided) or is there an additional freeze after this dialog closes?
slylarock wroteHopefully, this can be fixed for good in the next update. If this is an issue and not by design: Did you report this to tech support? As long as this cannot be reproduced and confirmed internally, there will be no fix.
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 |
[quote="jazzundso"]If this is an issue and not by design: Did you report this to tech support? As long as this cannot be reproduced and confirmed internally, there will be no fix..
Same behavior as many have reported: Clicking File/Save, or CTRL-S, dialog box briefly shows but not persistent. but it randomly freezes S1 for 5-10 seconds, where keyboard and mouse are not responding (I don't use auto-save). Safe to assume a support ticket has been opened since 2019. If, unfortunately, this is by design, then I guess I'll just have to live with it. |
Safe to assume a support ticket has been opened since 2019. Maybe. All I say is: No ticket, no repro -> no fix. Does this happen as well without any 3rd party plug-ins in your song?
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 |
jazzundso wroteSafe to assume a support ticket has been opened since 2019. Actually, this happens even on a new project, single track, no plugins. Record an event, make slight changes, like clip gain & save after each change. Does not freeze on every save, but happens often, still. Disabling the ethernet adapter seems stop the behavior. If you don't mind to check if you can repro, that would be appreciated. Thanks! |