jazzundso wroteSteve Carter wrote But this is about Studio One not the Sphere package and if 24 hours is not such a long time then why differentiate?
Windows 10 Pro/i7 6800k @3.4Ghz/16Gb ram. Studio One 6 Pro, Melodyne Editor, Vocalign Project 5, Superior Drummer 3, Izotope Music Production Suite 6, Komplete 13 and various other plugins. Focusrite Saffire Pro 40, Faderport, Focal Alpha 50's, Korg Pa3x, Korg Pad Kontrol, numerous guitars, basses & other antiquated outboard gear.
Maybe one day I'll actually finish a project! |
Nothing much to add I haven't been recording lately, I've forgotten what I'm missing but people here have already covered lot.whixh I agree with.
Only thing I can think of... Like Sonar, have separate drop in and drop out markers as well as loop markers. Stability, performance and bug fixing should always be priority. I'd also like to see the Dev team systematically go through features requests that have more than one hundred votes, make that list more of a priority. I think there are also a lot of duplicate feature requests that may need processing.
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 wroteI'd also like to see the Dev team systematically go through features requests that have more than one hundred votes, make that list more of a priority. I think there are also a lot of duplicate feature requests that may need processing. So true, I agree sooo much with this. Feature Requests are literally what users want, but some requests (with hundreds of votes) are still waiting, and waiting.. It's a bit disappointing when you notice they were originally posted years ago. In future updates, I would like more of those requested features implemented (possibly not just one at a time) and simultaneously work on bug fixes and stability. I don't know why but so far I've always got this weird feeling that they were fixing some bugs.. only to see some new ones pop out of nowhere, like a whack-a-mole game, am I the only one? I hope I'm the only one. However, I'm sure these new updates to the project page will make some people happy.
Presonus Featured Artist (Italy)
My Latest Feature Requests https://answers.presonus.com/73692/s1-essential-feature-plugin-racks https://answers.presonus.com/72506/zoom-to-selection-improvement-vote-if-you-agree Studio One Pro 6 Win10 - AMD Ryzen 9 5900X - 32gb ram DDR4 Gigabyte RTX 3060 Interface: Focusrite 18i20 3rd gen Prophet XL + KeyStep Pro Atom SQ Revelator |
kisnou wroteI don't know why but so far I've always got this weird feeling that they were fixing some bugs.. only to see some new ones pop out of nowhere, like a whack-a-mole game, am I the only one? I hope I'm the only one. That's the whole basis of agile software development. If you value stability you should always try to avoid major point releases with major new features, e.g. avoid 5.5.0 but install 5.5.1 which generally contains most of the fixes for the new features.
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. |
Bub wroteLokeyfly wroteI'm finishing an album and a video so a new release with Project page updates will get some love. You are confusing a few things. PreSonus actually invented ARA (in cooperation with Celemony) so Studio One is ready for it You'll have to check with Izotope and ask for an ARA version of Ozone.
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 |
PreAl wrotekisnou wroteI don't know why but so far I've always got this weird feeling that they were fixing some bugs.. only to see some new ones pop out of nowhere, like a whack-a-mole game, am I the only one? I hope I'm the only one. True, I'll keep that in mind. However, I was mainly referring to slightly older bugs which were being reported in the past, such as the 666 bug, the playback line disappearing with custom scaling options or the sustain pedal bugs (which I have been reporting since months now). I'm sure that 2022 is the right year to see these bugs finally fixed
Presonus Featured Artist (Italy)
My Latest Feature Requests https://answers.presonus.com/73692/s1-essential-feature-plugin-racks https://answers.presonus.com/72506/zoom-to-selection-improvement-vote-if-you-agree Studio One Pro 6 Win10 - AMD Ryzen 9 5900X - 32gb ram DDR4 Gigabyte RTX 3060 Interface: Focusrite 18i20 3rd gen Prophet XL + KeyStep Pro Atom SQ Revelator |
I can only suspect that Presonus is having great difficulty fixing satanic bugs, integration with third party code (plugins) can be tricky. The bug could be with a plugin or plugins of course, it could also be something to do with software libraries not being kept up to date (eg not running Windows update) but if that's the case they could catch it more gracefully, finding the criteria to do this could be very tricky indeed from a dev standpoint.
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. |
I tell you what I'd like to see, an online question and answer session in whatever format for all to see. We could ask them what exactly is the 666 issue for instance.
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. |
We could ask them what exactly is the 666 issue for instance. The 666 issue is not a bug in Studio One. "666" is displayed when invalid samples are detected (for example because a plug-in outputs invalid audio data) which can result in audio bursts.
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 wroteWe could ask them what exactly is the 666 issue for instance. In which case you are stating that this is 100% a plugin issue? Which would make sense... Although if this were the case I guess studio one should immediately mute the audio and stop if detected. Perhaps a more verbose error message will be nice, with goats.
Last edited by PreAl on Tue Jan 11, 2022 6:50 am, edited 1 time in total.
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. |
shanabit wrotejazzundso wrote[They pay and they get something in return. You paid for the software - and you get the software. As easy as that. I've explained to you how our Sphere subscription works. Feel free to contact me with any questions that adhere to the netiquette.
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 |
What???
Somebody saw a video 24 hours before I did? That's it I'm starting a petition
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 wrotejazzundso wroteWe could ask them what exactly is the 666 issue for instance. Yes, I totally agree. That's why we've changed this in version 5.5
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 wroteWe could ask them what exactly is the 666 issue for instance. That could very well be the case, but virtually every other DAW I have ever used deals with this differently and in a safe manner. This has been happening in Studio One since day 1 and it's the only DAW I've ever used in the last 20 + years that causes the loud audio problem it does. Of course I've seen VST's cause lockups and audio drop-outs, but I can honestly say I have never had one throw an internal error code like that and create equipment and ear damaging levels of noise. Many people have reported the problem over many years. It's not an isolated thing. Some of the largest threads on this forum are about the problem. It's not a plug-in problem. It's a problem with how Studio One deals with plug-in's that virtually every other developer has learned to handle in a way that doesn't cause equipment and hearing damage. Anyway, this is another dead horse that's been beaten, pulverized, cremated, and it's ashes spread around the desert. LOL. It's falling on def ears. Those at Presonus and those of us who have suffered hearing loss from the problem. All that said, it still happens, but significantly less frequently. So they must be slowly working it out. Anyhoo ... I'm looking forward to see what they have done in the Project page and anything else. And I'm looking forward to version 6. I know I'll upgrade (not rent 😜) no matter what. Here's to good things coming. 👍🏻 |
Steve Carter wrotejazzundso wroteSteve Carter wrote You're right! Some people say it's just one day. For every point there is a counter point. Studio One is a product. Sphere is a bi-product. Dollars to doughnuts, core users paid more into the core product (given the lifespan of Sphere up to now. Why are they not in the release news at the same time? Because someone paid? Lol. I could see if there is a sale specific to Sphere in and of itself. Not a product wide new release. There's a news feed to the right of the start page. Presonus! Maybe you should start universally using it, and showing some common courtesy. One day? You know interestingly, my friend and band member from our band in the 80's is releasing his album the end of this week. I told him, I'll hold off with my release for three weeks after (We have a lot of the ssme friends and loyal followers). He said, "if you want, go ahead and release this week", one week ahead of him. I could have crammed the Master this past weekend. I'm glad I didn't. Its a bit off putting that while I would be finalizing a Master, some newcomer who barely knows what to right click, and just tossed his first few $15 a month cookies in the kitty is getting Project Page news before me. More importantly. News before us. These same people who assist users of Studio One in this forum. It's not right. I used to be that guy (as folks can attest) who would say, "it's one day, no big deal". I truly get it. Still, what I also get is that I should re evaluate my time I use to assist others. Particiularly the ones waiting at the $15 a month Kool-Aid stand. I also hesitantly, but loyally tried to help those feeling a bit put off by the Sphere come first signals and the newsfeeds leading to dead ends with [Sorry, Sphere only users may pass], though I'm seeing more and more, the core users point. It's quite apparent. Going forward, I'll assist and share with the core users in the forum. If I see Sphere user in someones sig, I'm just going to take the position of "maybe they need to ask the question to the Sphere elite one day ahead circle of trust". Presonus started the US and Them position. I didn't. So a reassessment of how I contribute is in order.
Last edited by Lokeyfly on Tue Jan 11, 2022 9:10 am, edited 1 time in total.
S1-6.2.1, HP Omen 17" i7 10th Gen, 32 GB,512 GB TLC M.2 (SSD),1 TB SSD. Win10 Pro, Audient iD14 MkII, Roland JV90, NI S49 MkII, Atom SQ, FP 8, Roland GR-50 & Octapad. MOTU MIDI Express XT. HR824, Yamaha HS-7, NS-1000M, Yamaha Promix 01, Rane HC-6, etc.
New song "Our Time" https://youtu.be/BqOZ4-0iY1w?si=_uwmgRBv3N4VwJlq Visit my You Tube Channel https://youtube.com/@jamesconraadtucker ... PA5dM01GF7 Latest song releases on Bandcamp - Latest albums on iTunes All works registered copyright ©️ |
"The Sphere elite".
Where and when do we organised our protest against these evil elitists? I suggest 6.66pm outside Walmart tomorrow, bring a goat.
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. |
Man - you guys need to get a new hobby if Sphere is truly frosting your corn.
The choice is simple - either get off the wallet and purchase a subscription and "be ahead of the crowd" or wait until 11:00am CST today and see what's new. "Core" users or not - how is this really a thing? I am thinking it's not. VP
DAW: Studio One Pro 6.6.0.99237 | 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.249) | 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
|
Lokeyfly wroteIf I see Sphere user in someones sig, I'm just going to take the position of "maybe they need to ask the question to the Sphere elite one day ahead circle of trust". Presonus started the US and Them position. I didn't. So a reassessment of how I contribute is in order. I just noticed I still have it in my sig. I tried it for a while and didn't care for it. I never use samples and the only thing I did use were the extra's for the Fat Channel, and in the end, I only used what I already had without Sphere. It is a great value though if you are in to that kind of thing. That said, I got busy working on my house doing a major remodel and forgot that I was subscribed to Sphere. That's why I made the suggestion that it makes you confirm every month if you are on the monthly plan before it continues. If you are on the yearly plan, have it confirm once a year. You get the picture. You've always been a great help on this forum. I've always appreciated your assistance. It would be a great loss if the forum lost you but I completely understand. Thanks! (Changing my sig now.). |
Users browsing this forum: patricemazmanian and 57 guests