A few thoughts . . . 
Starting in 2010, I was using NOTION and Digital Performer (MOTU) in ReWire sessions where Digital Performer was the ReWire controller and NOTION was the ReWire device; but then the Propellerheads (now Reason Studios) dropped ReWire; so no more NOTION providing real-time music notation.
Then starting with Studio One 5, the core of NOTION was embedded; and so I switched to Studio One. It got better in Studio One 6 and after using NOTION since 2010 when it was Notion Music, the music notation was the best ever for folks like me who use music notation to play VSTi virtual instruments. Yet, the folks who primarily need to create sheet music never have been very happy; but there are other products that apparently are designed for sheet music focused folks, which is fine with me.
I used Studio One 5, 6, and more recently 7; and everything was working very nicely. The music notation got better with each version of Studo One, and now it's focused and made as easy and efficient as I think it possibly can be.
Fender bought PreSonus a while back, which works for me; and earlier this week I saw a topic in this forum about Fender Studio Pro 8 and initially had a panic attack because I saw nothing about music notation; but a few folks assured me the music notation stuff was there, hence no panic attack required.
Rollback the clock a few years, and I posted to the NOTION forum (Notion Music and then PreSonus) every day and made a diligent effort to help folks, which also helps me because I learn by writing and doing research, which makes it like having a daily Pop Quiz.
After doing that daily since 2010 when initially I did not know what a virtual instrument was, and over the past year I have written a volume every six weeks in my ongoing series of books on "The Art of Digital Music Production", which is available currently as Kindle eBooks and if all goes according to play will are available as Apple eBooks, where the key bit of information is that the Kindle book application creates Kindle and ePub (Apple Books) versions.
For reference, the "official" strategy is to write a book in Word for Windows or Pages (Apple) and then to import it to the Kindle Create application for formatting; but there is no easy or practical way to attach titles to diagrams, which for me was a big problem.
The solution is to do everything in Kindle Create and to add captions or titles to diagrams using a combination of than Krita and Graphic drawing applications, so that each diagram or image has its own caption title, hence no need to mess with associating captions and titles with images and diagrams, because they are self-contained.
I suppose this is not the "standard" way of creating eBooks; but then I use a similar strategy for digital music production, where for example instead of having 120 notes, I have 12 notes and 10 octaves, so that for example I only need to remember there is a note named "C" that can be low-pitch, medium-pitch, or high-pitch depending on its octave, which is enhanced by doing everything on soprano treble staves and using transposition to cause the actual notes to be played as the octave notated or one or two octaves lower or higher than notated, which is easy to do when configuring a staff, all because I only learned soprano treble staff when I was in a liturgical boys choir.
it might be stupid; but it works and it lets me focus on the music, where I also do everything in the keys of C Major or A minor, 4/4 time, and specify sharps per measure as needed, which is a tiny bit more work but avoids needing to remember that when using other key signatures, the music notation does
not look like what it really is, where for example when C is sharped in a key signature, you only see C without the added sharp, which one might suppose saved paper centuries ago but today is confusing for no logical reason. If it's C#, then I want to see the sharp (sorry for the pun).
Fender Studio Pro 8 appeared, and after exploring it for a few days, I like it!
As an additional bit of background, I have a Computer Science degree and started doing mainframe programming in the late-1970's on the NASA Space Shuttle Mission Simulation System, which at the time had the largest Univac computers in the world; and among other things gave me a bit of free computer time when all the nightly work was done, which I used to write a computer program to print every possible chord on an electric guitar and was what now is called a "Grimmorie" and was hundreds of printed pages. This was OK with NASA, because it improved my programming skills, and along the way I devised a way to automate a lot of the work in preparing simulation code for astronaut training, which was used in the first two Shuttle missions during which I was a primary contact, meaning my work required me to be within 10 feet of the astronauts in the weeks before launch. It also mapped to having some "stick time" on the fixed-base simulator, which basically ruined me on playing computer games, since how can a computer game be better than the actual NASA shuttle simulator, where for reference there was a motion-based simulator but it required being a licensed pilot and wearing helmets, shoulder and seat harnesses, and all that stuff, because the hydraulic systems were sufficiently powerful to propel the simulator module through the top of the building if folks did stupid stuff.
Then Windows appeared, and I started doing Windows programming, which soon was called "software engineering"; and I became a Microsoft Solution Provider and wrote two books on Visual Basic programming, with this leading to being a Judge in the the last three Windows World Open Contests, where among other things I got to meet Alan Cooper who also was a Judge and created "Ruby", which was the foundation for Visual Basic.
A while later, Microsoft was accused of being a monopoly and one might guess this annoyed Bill Gates so much that he moved most of the Windows programming to India, which soon mapped to the appearance of ".NET", which ruined Visual Basic and annoyed me greatly,
Around the same time, Apple introduced the original iPod, which I got along with an Apple computer which was required to configure and charge the iPod. This was when I discovered "Aqua", the Graphic User Interface (GUI) for macOS and fell in love it, along with the overall simplicity of the way things are done on Apple computers where the strategy is based on James Martin's perspective that computers should help people rather than make people their puppets, or simply put "people are more important than computers".
Fast forward to this week; and I am a bit puzzled by some of the reactions to Fender Studio Pro 8, many of which make absolutely no sense, especially when they suggest Fender Studio Pro 8 somehow is vastly different from PreSonus Studio One 7.2.3, which it isn't.
I like to be a happy and gracious fellow whenever possible; but how can anyone with a working brain look at Fender Studio Pro 8 and then look at PreSonus Studio One 7.2.3 and suggest they are vastly different?
Fender Studio Pro 8 is a very nice and quite elegant improvement to PreSonus Studio One 7.2.3; and as best as I can determine it was developed and software engineered by the same folks, if only because there is no way those folks can be replaced.
Why?
Fender Studio Pro 8 is doing so much advanced work that it's like macOS in the sense that the folks doing the work are so advanced and skilled that they are the only ones who can do the developing and software engineering.
Thanks to some very helpful clues and suggestions by other folks in this topic, I have discovered some very nice improvements in the GUI and behaviors of Fender Studio Pro 8, including the new Channel Overview GUI design and its behaviors, which is going to make my work creating songs a lot easier and more focused. It also was motivation to devise a new way to diagram GUI steps using curved dotted lines with arrows and new graphic symbols for "double-click" and "right-click" actions.
On top of all this, I get to do updates to Volumes 1 through 10 of "The Art of Digital Music Production" to use Fender Studio Pro 8 images, which I was going to do regardless to create eBooks for Apple Books, hence is not so much additional work. I already started doing screen captures with Reason 13 (Reason Studios) and most of the other digital music production software, which like clockwork changes frequently, if only because software engineers become bored and then without adult supervision are compelled to devise new stuff.
If there is a summary, then it's the fact that Fender Studio Pro 8 is a consistent and logical improvement and makes everything better.
It also makes it clear that "Fender" is a more ubiquitous name then "PreSonus"; and "Studio" is more focused than "Studio One".
I love Fender guitars; and over 15 years ago custom-modded a 1999 Fender American Deluxe Stratocaster, which I call the "Fabulous Fifty Million Dollar Trinaural Stratocaste®r", since it has two separate and independent output signals or channels but is not a stereo guitar. Among other things, it has what I call the "Really Big Knob" that operates a Varitone control.
I also learned that Elvis Presley could do natural vibrato spanning three half-steps, which is as mind-boggling as doing uvular trills on the "H" in "Hound Dog" when he was 21 years-old; and Scotty Moore had a custom amplifier that had built-in slapback echo.
FACT: Everything is better this week, and I am vey happy!
My S1 Licence has expired, BTW, which is probably why I didn't see the options that you described...
