87 postsPage 1 of 5
1, 2, 3, 4, 5
Dear Studio One Users,

a new S1 update is online! Click check for updates within Studio One or download from your user account. Have fun and happy discussion!

Announcement thread.
viewtopic.php?f=151&t=42503

best
Ari

Ari Ahrendt - Quality Assurance Specialist
PreSonus Software Ltd. - Hamburg
http://www.presonus.com/products/studio-one

Modern electronic Synth Pop........../..........Musicproduction, Support & coaching
http://www.denoisary.de/................./...........http://www.arimusik.de/

Windows 10 64-Bit, i7 6700k 4.0 GHz, 16GB RAM, 4TB SSD, Studio One 5 Professional
User avatar
by gregghart on Tue Nov 17, 2020 10:06 am
Thanks for fixing the score editor issues. That was a tricky one! Glad I contacted support on that one. I can confirm that the font I had the caused the crash no longer causes the crash. Thank you!

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
User avatar
by snb1 on Tue Nov 17, 2020 10:51 am
Unfortunately the graphic hardware acceleration still doesn't work for me. My plugins still comes up with no gui. The up and down arrows still doesn't work inside the Reason Rack Plugin.
Last edited by snb1 on Tue Nov 17, 2020 10:59 am, edited 1 time in total.

Studio One Pro 6.5.1 64 bit, macOS Monterey 12.6, 14" MacBook Pro M1 (2021),16gb ram, 512 SSD, 8-core CPU

SkipNo Beet
User avatar
by pawelhebda on Tue Nov 17, 2020 10:55 am
Thank you!!! :)
User avatar
by PreAl on Tue Nov 17, 2020 2:36 pm
Excellent
I hope attention will now be turned on atom firmware bug fixes and minor enhancements.

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.
User avatar
by UntilTheBones on Tue Nov 17, 2020 3:48 pm
Audio Device Controls for the Quantum are showing up again in the console. TY! :thumbup:

_______________________________________
Studio One 5.1.1
Pro Tools 2020.5
2017 iMac Pro 3.0GHz 10-Core Xeon 64GB
macOS Catalina 10.15.7
Quantum (Desktop Workstation)
Studio 26c (Mobile Workstation)
FaderPort 2
User avatar
by briandeeley on Wed Nov 18, 2020 12:18 pm
Thank you! :D
User avatar
by jonwright on Thu Nov 19, 2020 9:27 am
I've just finished setting up a reasonably large disabled track template, and I am running into some issues with hanging on project load, seemingly related to Kontakt.

A fresh disabled template loads without any issues, as does a project without any Kontakt instances enabled.

When I load a project with just one track that uses Kontakt, it will hang on 'Loading:Workspace', for about two minutes.

It does eventually load. Is this happening to anyone else?

----------

Studio One 5.1.1 - Mac OS X 10.15.7. iMac 3.5 GHz Intel Core i7 - 32GB RAM.
https://www.jonathanwrightmusic.com
User avatar
by robertgray3 on Thu Nov 19, 2020 10:41 am
jonwright wroteI've just finished setting up a reasonably large disabled track template, and I am running into some issues with hanging on project load, seemingly related to Kontakt.

A fresh disabled template loads without any issues, as does a project without any Kontakt instances enabled.

When I load a project with just one track that uses Kontakt, it will hang on 'Loading:Workspace', for about two minutes.

It does eventually load. Is this happening to anyone else?


I've noticed some inserts load slower than I recall happening before. Kontakt is one of them. Some Waves plugins are the others.

Mac OS X Catalina 10.15.7
Mac Pro 6.1
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by aqvtgkoi on Thu Nov 19, 2020 10:46 am
I can no longer launch Studio One after installing the 5.1.1 update on my mac -- it just hangs at startup while displaying a checking for updates dialog... clicking cancel doesn't help either.
User avatar
by PreAl on Thu Nov 19, 2020 11:00 am
For those who need their issues troubleshooted, can you please create your own thread - please. If a bug is validated by somebody else, you can always come back here.

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.
User avatar
by Blades on Thu Nov 19, 2020 7:27 pm
Glad to see an aggressive update schedule (it seems). Bummer that this round didn't fix the issue with a controller getting set to a starting value in a MIDI track as reported and reproduced during this development cycle. Maybe next time!

Drummer and Singer mostly with some limited Guitar/Bass/Keys and a love for tech.
My personal website, with some useful videos and other music related things: https://blades.technology

Using:
Self-built i7 8700k/16gb/all SSD, S1 4 Pro, +Sonar Platinum/Cakewalk by Bandlab, PreSonus Studio 18|24 USB, Faderport 8, Tranzport, Edirol PCR-800, Pearl Mimic Pro and Roland V-Drums kit & Console 1 with SSL4000e + British Class A..
User avatar
by PreAl on Thu Nov 19, 2020 8:02 pm
Blades wroteGlad to see an aggressive update schedule (it seems). Bummer that this round didn't fix the issue with a controller getting set to a starting value in a MIDI track as reported and reproduced during this development cycle. Maybe next time!


Here is your issue reported Nov 1st, two weeks before release is just not enough time. When you says "reported" you have created a ticket and has this confirmed?


viewtopic.php?f=151&t=42279&p=248507#p248507

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.
User avatar
by jonwright on Fri Nov 20, 2020 4:06 am
robertgray3 wrote
jonwright wroteI've just finished setting up a reasonably large disabled track template, and I am running into some issues with hanging on project load, seemingly related to Kontakt.

A fresh disabled template loads without any issues, as does a project without any Kontakt instances enabled.

When I load a project with just one track that uses Kontakt, it will hang on 'Loading:Workspace', for about two minutes.

It does eventually load. Is this happening to anyone else?


I've noticed some inserts load slower than I recall happening before. Kontakt is one of them. Some Waves plugins are the others.


Update to this, I found the cause. Cubase 11!

Removing the Spectral Layers VST from my plugins folder solved the issue, and Studio One loads as normal again.

----------

Studio One 5.1.1 - Mac OS X 10.15.7. iMac 3.5 GHz Intel Core i7 - 32GB RAM.
https://www.jonathanwrightmusic.com
User avatar
by PreAl on Fri Nov 20, 2020 4:11 am
^ Next time please post in the cubase forums ;) (joking).

Seriously though - please create your own thread next time for troubleshooting.

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.
User avatar
by gregghart on Fri Nov 20, 2020 5:18 am
PreAl, just a question....what is this thread for then? It's a discussion thread, which is pretty general. I think it's perfectly fine to discuss things you like, or dislike, things that were fixed, or broken, etc. I agree that if it becomes a topic, then yes, you should create a thread, but mentions should be fine, shouldn't they?

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
User avatar
by PreAl on Fri Nov 20, 2020 6:56 am
gregghart wrotePreAl, just a question....what is this thread for then? It's a discussion thread, which is pretty general. I think it's perfectly fine to discuss things you like, or dislike, things that were fixed, or broken, etc. I agree that if it becomes a topic, then yes, you should create a thread, but mentions should be fine, shouldn't they?


Groundhog day again:
viewtopic.php?p=245050&sid=161acd281d3a3b95d1dfef081cdbe2db#p245050

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.
User avatar
by roland1 on Fri Nov 20, 2020 7:04 am
Attention all Earthlings: POST WHAT YOU WANT HERE!

PreAI, please shut up. You act as though you are an official spokesman for Presonus but come off more like an annoying middle manager type who wants to be in charge of others.

This thread, as has always been the case, is for throwing out the first bits of good and bad news about the new release. It has always kept first impressions in one place where people can decide immediately whether it looks worth updating or not. That's what makes it useful.

A good idea would be to mention issues here and then link to a thread that lets others discuss it in greater detail.

I'm not here to make friends but to speak my mind without concern for whose ego I have to spank. PreAI, your thread policing is annoying at times and you are NOT the voice of the people. I suggest you get into politics for that instead. ;)

PreAl wroteFor those who need their issues troubleshooted, can you please create your own thread - please. If a bug is validated by somebody else, you can always come back here.


gregghart wrotePreAl, just a question....what is this thread for then? It's a discussion thread, which is pretty general. I think it's perfectly fine to discuss things you like, or dislike, things that were fixed, or broken, etc. I agree that if it becomes a topic, then yes, you should create a thread, but mentions should be fine, shouldn't they?

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. :)
User avatar
by PreAl on Fri Nov 20, 2020 7:17 am
roland1 wroteAttention all Earthlings: POST WHAT YOU WANT HERE!

PreAI, please shut up. You act as though you are an official spokesman for Presonus but come off more like an annoying middle manager type who wants to be in charge of others.

This thread, as has always been the case, is for throwing out the first bits of good and bad news about the new release. It has always kept first impressions in one place where people can decide immediately whether it looks worth updating or not. That's what makes it useful.

I'm not here to make friends but to speak my mind without concern for whose ego I have to spank. PreAI, your thread policing is annoying at times and you are NOT the voice of the people. I suggest you get into politics for that instead. ;)

PreAl wroteFor those who need their issues troubleshooted, can you please create your own thread - please. If a bug is validated by somebody else, you can always come back here.


gregghart wrotePreAl, just a question....what is this thread for then? It's a discussion thread, which is pretty general. I think it's perfectly fine to discuss things you like, or dislike, things that were fixed, or broken, etc. I agree that if it becomes a topic, then yes, you should create a thread, but mentions should be fine, shouldn't they?


Nope just stating facts which were endorsed by admins (did you actually read the link I gave you?). BTW I politely requested, I wrote "please" twice. If you consider that to be "policing" that's your problem not mine. So you get to police the police right?

BTW I don't make the rules and nor do you. Yet here you are making a personal attacks and trying to censor me by telling me to "shut up" and telling people post what they want here as though you are in charge. Well done you 👍.

I'm not going to hijack this thread further, the discussion about why people shouldn't troubleshoot here is covered by that link. I was asked a question and I gave an answer.

EDIT - I am responding to your original unedited post quoted above.

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.
User avatar
by gregghart on Fri Nov 20, 2020 11:42 am
Thanks PreAl, I didn't see that other thread. However, I still see nothing wrong with mentioning a problem and then mentioned it was fixed in this thread. Actual troubleshooting should be done in another thread, totally agree. There are so many threads created here that sometimes the problem threads get buried one or two pages below and they get missed. So putting it in the general thread, which is pinned, by the way, ensures more people will likely see it, and then hopefully will go find the actual thread to state they have similar issues, or a way to fix it. Maybe in the future., the person posting the question and "link" to the problem thread to help guide people there? It's an idea right? Why police everyone that may be having trouble? Instead, as a community, we can all help each other out. We're all friends here, right? My guess is that either the devs or a QA person DOES in fact look at the general thread pinned. After all, one creates it, it stands to reason they check it out as well. Read below for further proof of this theory.

I used to run a very large forum for a New York Best Selling author and we had similar rules (obviously, no real troubleshooting going on with an author forum, but we had general threads like this one as well as specific threads for questions / comments on certain books). Nothing wrong with a general thread that says, "Hey, Anyone seeing this? If anyone replies, then a new thread can be started in which troubleshooting can ensue. You even rightly pointed it out to start a new thread once someone confirmed they had a similar issue.

Just like I started a new thread when asking in the 5.1 forum about the score editing. As soon as I confirmed I wasn't alone, I started a thread. Nobody seemed to mind. A Mod didn't have to step in and say I was wrong. Even someone from Presonus (not sure if it was a QA guy or a dev) posted in my thread asking for information. What is really cool is someone from the QA team even reached out to me and had me test before they announced the fix, so that was very cool. I was a happy customer. I feel like that since asked the question in the general thread, more people saw the issue because even someone from Presonus was aware of the thread, actually posted in my thread and even reached out to me to give me a fix before the patch was released. I confirmed that it fixed it. it got resolved in the following patch, and I was able to continue on my staff editing way.

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

87 postsPage 1 of 5
1, 2, 3, 4, 5

Who is online

Users browsing this forum: No registered users and 36 guests