Presonus Studio One 7.1 - Released!

[trusampler]

I have absolutely no need for any sort of samples or tired vst instruments from any daw developer. They’re never gonna come close to dedicated sound design development and creative design. It’d be great if they’d add tagging to their browser. Instead of the Splice option. Focus more on adding audio/midi features like Cubases midi remote. We still can’t back up our midi mappings for our midi controllers ! That’d be a great way to continue to get my money.

[trusampler]

I think they should interact with their customers again, when Jonathan and Rick would speak to us lowly supporters of their platform! maybe bring back their forums, and count it as a feature. Definitely not interested in waiting months for Magregors videos on content we’re never going to use.
It seems like they’re going downhill ever since the fender takeover happened.

[THE INTRANCER]

I'm happy that there is a new instrument, it's not like Studio One has that many anyway and how many full point updates have included a new instrument to play with. I can't think of any.... and in any case, as this is considered a point update, we still don't know what lays in store for the next series of updates and revisions to fix certain things should there be any. Sometimes the smallest of things can be the most critical to you, like the crossfade feature they added to one of the older instruments like Impact and show and hide workflow features it has. Studio One still has the fastest workflow curve out of all the big DAWs out there so if you are thinking of jumping ship, you will probably feel you are dragging your feet through the mud for a very long period and using only a tiny fraction of what you really want. If the DAW s stable and works for your way of working, you really need to ask your self if the pain is worth it in the long run.

EDIT: I mentioned that it was Impact that had crossfade added, it's actually Sample One which has had it added.

[BONES]

I have a lot of my work invested in Studio One. Not only all of my source tracks, but also a very refined template and workflow. I don't see any of that being replaceable. But I also once felt the same way about Cubase, until I didn't. So never say never.

I'm the same but I haven't upgraded and I won't. V6 does everything I need (plus a million things I don't) and Presonus continue to work with me on issues I have with the product.

As for Apple, I haven't found myself disappointed with their direction so far.

So you were OK with them completely dropping support for 32 bit software? Because I can still open every project I have ever worked on, all the way back to last Century. Sure, I don't install al my old 32 bit plugins any more but I know I could and they would all still work. I do still keep installing the 32 bit version of Orion so I can access songs from our first three albums, though.

I know I haven't liked the direction of Windows starting after Windows 7.

Windows 7 was the worst version of Windows I've used. I f**king hated it. Windows 8 and beyond have been pretty f**king awesome. Win 11 maybe slightly less so but it is still streets ahead of anything else out there.

Not saying that anybody else cares about these things but, at the same time, I doubt I'm that unusual.

That's the problem, everybody wants different things. Nothig you listed is of even the slightest interest to me and the problem with things like changing the workflow is that what one user sees as an improvement, 10 other users will spit their dummy over. It's very hard for any established product to change things like that, which is why we end up with so much bloat - 20 different ways to do one thing so that nobody gets upset that their favourite feature got messed with.

As a recorder its quite basic,and needs a lot adding,but its foundation seems to be very good.

Which is the problem - a lot of work is needed to finish off a feature most Studio One users probably don't want and will never use, while things that most of us might appreciate don't get done.

Am I the only one who feels like they used to deliver more features in smaller updates?

Yeah but that's always been the way. e.g. I thought the 6.1 update was more useful than the update from 5.x to 6.

I have absolutely no need for any sort of samples or tired vst instruments from any daw developer. They’re never gonna come close to dedicated sound design development and creative design.

I dunno, if I hadn't spent $400-$500 on things from Heavyocity and Output, I reckon I'd be all over this thing.

[THE INTRANCER]

Windows 7 was the worst version of Windows I've used. I f**king hated it. Windows 8 and beyond have been pretty f**king awesome. Win 11 maybe slightly less so but it is still streets ahead of anything else out there.

I don't usually say profanities but imop and arguably by millions of others, but that's B***ocks.

"Released in 2009, Windows 7 was Microsoft's fastest-selling OS and was the most popular OS in the world until 2018."

"Windows 7 was more secure and user-friendly than previous versions, and it had better networking features and touch-screen functionality. "

If you wanted to be critical of it, it would be that the Home version was limited to 16 gigs of ram despite you possibly having more.

On topic though...

[jamcat]

As for Apple, I haven't found myself disappointed with their direction so far.

So you were OK with them completely dropping support for 32 bit software? Because I can still open every project I have ever worked on, all the way back to last Century. Sure, I don't install al my old 32 bit plugins any more but I know I could and they would all still work. I do still keep installing the 32 bit version of Orion so I can access songs from our first three albums, though.

Yes, I'm more than fine with it. It's the kind of thing I want to see happen. Progress is a good thing.

For a very long time I have made sure all of my audio software/plugins supported 3 things:

• 64-bit
• VST3
• Mac/Windows cross-platform

Then I updated the cross-platform requirement to be Apple Silicon Mac/Windows.

Any song that may have used an obsolete plugin got updated long ago.

This is actually for the same reason that I upgraded to Studio One 7. I am always looking to be in the most future-proof position I can be in, and not get locked into something that won't allow me to upgrade or switch. And history only moves in one direction. We are not going back to 32-bit. We are not going back to VST2. We are not going back to Intel. And we are not going back to Studio One 6. Insisting on these minimum requirements means that I never have to worry about older songs not loading, or not being able to open a song on a Windows or Mac system. I avoid AU plugins for this reason as well, even though Studio One supports them.

[dellboy]

As a recorder its quite basic,and needs a lot adding,but its foundation seems to be very good.

Which is the problem - a lot of work is needed to finish off a feature most Studio One users probably don't want and will never use, while things that most of us might appreciate don't get done.

Who are "most Studio One users" nowadays? We all know who they used to be - but Presonus have gone off in a new direction recently with the Splice addition, presumably looking for a new audience. I guess they hope to pick up a whole new group of people who like the new features. But as far as using the Clip launcher as a recording tool, I seem to be the only one who uses it that way,so I guess you are right with regard to that mode. At least,no one else has ever posted that they use it as a pattern based real time recorder that I recall.

[concealed identity]

As a recorder its quite basic,and needs a lot adding,but its foundation seems to be very good.

Which is the problem - a lot of work is needed to finish off a feature most Studio One users probably don't want and will never use, while things that most of us might appreciate don't get done.

But as far as using the Clip launcher as a recording tool, I seem to be the only one who uses it that way,so I guess you are right with regard to that mode. At least,no one else has ever posted that they use it as a pattern based real time recorder that I recall.

As someone that's never tried it, what ways are people using it? I always assumed it (and Ableton's Session View) were almost exclusively used in this way, at least as far as studio use goes.

[dellboy]

As a recorder its quite basic,and needs a lot adding,but its foundation seems to be very good.

Which is the problem - a lot of work is needed to finish off a feature most Studio One users probably don't want and will never use, while things that most of us might appreciate don't get done.

But as far as using the Clip launcher as a recording tool, I seem to be the only one who uses it that way,so I guess you are right with regard to that mode. At least,no one else has ever posted that they use it as a pattern based real time recorder that I recall.

As someone that's never tried it, what ways are people using it? I always assumed it (and Ableton's Session View) were almost exclusively used in this way, at least as far as studio use goes.

I choose either an external audio input or a VST input and arm a cell,and hit the keyboard return key, and record in real time for as many bars that I choose. Hit the spacebar to stop - and hope it loops OK. Sometimes a small adjustment is need to start and end lengths of the clip. When you have all the tracks\clips that you need,drag them into the linear view to edit and arrange into a song. Lots of people just drag third party loops into a cell and build a song that way. In Ableton a lot of people use Push to input with. In Studio One, many people seem to input notes with the mouse,so I guess they see no need for a clip launcher\recorder.

[SeeingInMidi]

I want to assume that a ".1" release is not considered as one of the bigger releases they had advertised. I don't think I'm being too charitable since we are still in Q1.

[HGX]

Think I read something about new functions for clip launcher in latest version.. Anyone tried it?

[BONES]

"Released in 2009, Windows 7 was Microsoft's fastest-selling OS and was the most popular OS in the world until 2018."

All that shows is how absolutely f**king stupid people are. Seriously, they put a coat of paint over Vista, without fixing any of the things people didn't like about it, and in the process they broke shit that used to work, like Windows Media Player. Vista SP1 and Windows 7 were functionally identical but they changed the way it looked and every fucktard on the planet fell for it.

Yes, I'm more than fine with it. It's the kind of thing I want to see happen. Progress is a good thing.

And next time, when everything you have been working on up until that point suddenly won't work any more? You'll still be happy?

This is actually for the same reason that I upgraded to Studio One 7. I am always looking to be in the most future-proof position I can be in

Future-proof but clearly not idiot-proof. You are the perfect patsy for corporate shite like this.

We are not going back to 32-bit.

Hardly the point. We made our first three albums on 32 bit software and played our first 40 or 50 shows. We probably have 50 or 60 songs that were made using 32 bit software. At the time we transitioned to 64 bit, we moved 20 or so songs across, which was fine because we knew that we'd always be able to go back and bring some more things over whenever we needed to. And it's worked a treat - last year we performed a song from our first album we hadn't played live in 20 years and there's another we've been rehearsing that we haven't played in 17 or 18 years. If we were on Mac, all those songs would be dead and we'd have to re-do them from scratch.

Insisting on these minimum requirements means that I never have to worry about older songs not loading, or not being able to open a song on a Windows or Mac system.

So how do you open things you made with 32 bit software? Or are you such a Johnny-come-lately that you weren't making music 15 years ago? If you are, then you have no idea of the world of hurt you're in for next time Apple decides it doesn't want to do something any more.

I guess they hope to pick up a whole new group of people who like the new features.

My point exactly - all their effort is going into chasing new users at the expense of their loyal, existing customers.

[jamcat]

Yes, I'm more than fine with it. It's the kind of thing I want to see happen. Progress is a good thing.

And next time, when everything you have been working on up until that point suddenly won't work any more? You'll still be happy?

That's exactly the point of why I've been so adamant about what I use supporting VST3 on Apple Silicon. I won't be around by the time anyone has to worry about either no longer being supported (and I'm younger than you!)

So I'm set. That is the entire point of "future-proof."

Insisting on these minimum requirements means that I never have to worry about older songs not loading, or not being able to open a song on a Windows or Mac system.

So how do you open things you made with 32 bit software? Or are you such a Johnny-come-lately that you weren't making music 15 years ago? If you are, then you have no idea of the world of hurt you're in for next time Apple decides it doesn't want to do something any more.

So I started out on Opcode Studio Vision Pro in the early/mid-90s. I believe it was the first MIDI sequencer ever to offer digital audio. It had 4 tracks of 16-bit 44.1kHz audio.

When I got on Windows 95, I messed around with Cakewalk, SAW+ and Cubase Audio XT 3.0. I settled on Cubase VST 3.5 when it came out. This introduced VST 1.0 and it was a revolution. I moved over to Nuendo when it came out, and then back to Cubase when it became Cubase SX (which was really Nuendo reskinned.) Nuendo/Cubase SX was made by the same guys who would go on to develop Studio One.

I then switched to Studio One Pro 1.0 in early 2010, about 6 months after it came out.

The primary reason was actually precisely because Cubase still didn't support 64-bit (it wouldn't until version 6 an entire year later), but Studio One did.

I recreated all of my songs in Studio One over the next year or so. That was 15 years ago.

So I don't ever need to open anything on 32-bit ever again, and I haven't for a very very long time. Again, this was done as a conscious effort to future-proof. That's how long I've been on about this for.

[BONES]

That's exactly the point of why I've been so adamant about what I use supporting VST3 on Apple Silicon. I won't be around by the time anyone has to worry about either no longer being supported (and I'm younger than you!) So I'm set. That is the entire point of "future-proof."

Why? Why put it all on yourself? I don't have to worry about any of that because I'm on Windows and I know that everything I have ever bought and anything I will ever buy, will always keep working, long after I'm done with it. Windows is all the future-proofing anyone needs.

Insisting on these minimum requirements means that I never have to worry about older songs not loading, or not being able to open a song on a Windows or Mac system.

So how do you open things you made with 32 bit software? Or are you such a Johnny-come-lately that you weren't making music 15 years ago? If you are, then you have no idea of the world of hurt you're in for next time Apple decides it doesn't want to do something any more.

The primary reason was actually precisely because Cubase still didn't support 64-bit (it wouldn't until version 6 an entire year later), but Studio One did.

Why did that matter? I'm 100% certain that all it's internal calculations were being done in float, or at least 64 bit, the 32 bit limitation only ever applied to output so you never got any change in sound quality by moving to 64 bit. It was mostly a way to make you buy bigger hard-drives and lots of extra RAM. I would have happily stayed on 32 bit forever if Korg hadn't made the ARP Odyssey 64 bit only.

I recreated all of my songs in Studio One over the next year or so. That was 15 years ago...
Again, this was done as a conscious effort to future-proof. That's how long I've been on about this for.

Whereas I didn't really have to do anything at all because I can still run 32 bit Orion on my 6 months old 64 bit Windows 11 computer, so all my old songs are still available to me whenever I need them. THAT, right there, is future-proofing. All you did was make lots of extra work for yourself by jumping onto every new bandwagon at the first opportunity.

[jamcat]

Windows is all the future-proofing anyone needs.

Until Windows inevitably goes ARM64 like everyone else...

Why did that matter? I'm 100% certain that all it's internal calculations were being done in float, or at least 64 bit, the 32 bit limitation only ever applied to output so you never got any change in sound quality by moving to 64 bit. It was mostly a way to make you buy bigger hard-drives and lots of extra RAM.

Because at the time I used lots of very large sample libraries—primarily drums, orchestral, and choir. 4gb simply was not enough. Now it's actually moot since my drums and orchestra are physically modeled and take mere kilobytes instead of gigabytes. But I still use Eastwest Symphonic Choirs and Hollywood Choirs.

Whereas I didn't really have to do anything at all because I can still run 32 bit Orion on my 6 months old 64 bit Windows 11 computer, so all my old songs are still available to me whenever I need them. THAT, right there, is future-proofing.

No, that's not future-proofing. What you've done is "grandfathering", which is the opposite of future-proofing. You've locked yourself in to dependence on x86 Windows with a 32-bit layer. Whereas I can take my songs back and forth between Windows and Mac, Intel or Apple Silicon. I can work with partners on any system. You can't.

All you did was make lots of extra work for yourself by jumping onto every new bandwagon at the first opportunity.

Actually it just gave me an opportunity to improve upon old work. I've also continually updated plugins to either the latest versions or replaced them with better plugins. This also means finding replacements for obsolete plugins that have failed to stay up to date with my basic cross-platform requirements.