Fender Studio Pro 8 Released

[BONES]

I thought this might be interesting but it's a complete waste of time. He doesn't give us any information on specs and he's using a 10 year old version of Windows that's no longer supported by Microsoft and wonders why he gets f**ked around. And he calls 30% higher CPU usage on macOS "slightly more". I'd hate to see what it takes for him to see it as significantly more.

It might not suit your workflow but it works perfect for me so i have no regrets with my decision to move away from Windows

I can only assume you don't use your computer for anything but I rely on mine to earn a living. For that it needs to be able to run industry-standard software applications, pretty much none of which run on Linux. Even with Studio Pro, you are massively limited in which plugins you can use, so you end up allowing your operating system, whose main job is to allow you to run the software applications you want/need to use, to determine your choice of applications. That's really f**king stupid if you ask me.

I can't think of a more different DAW to Studio Pro than Bitwig, so it's not even a reasonable replacement for your preferred DAW. It's a classic example of the tail wagging the dog.

[BONES]

We did our first live show with Studio Pro last night and it performed flawlessly. It definitely feels more robust, more reliable, although over the past two weeks I've noticed something weird - If I load up the whole set, run through it straight away and then close all the songs, it's fine. However, if I leave it for any length of time, either before I start the run-through or after I've finished, it will crash when it starts closing the songs. It's a bit weird but of no consequence. In fact, last night it sped up the changeover after our set because it takes a couple of minutes to close the songs one-by-one, as it asks if you want to save each song or not. The crash was quicker.

Oh, in case your interested, the gig went really well. lots of audience engagement, particularly with our new AI generated songs, lots of dancing and thrashing around.

[audiojunkie]

I thought this might be interesting but it's a complete waste of time. He doesn't give us any information on specs and he's using a 10 year old version of Windows that's no longer supported by Microsoft and wonders why he gets f**ked around. And he calls 30% higher CPU usage on macOS "slightly more". I'd hate to see what it takes for him to see it as significantly more.

It might not suit your workflow but it works perfect for me so i have no regrets with my decision to move away from Windows

I can only assume you don't use your computer for anything but I rely on mine to earn a living. For that it needs to be able to run industry-standard software applications, pretty much none of which run on Linux. Even with Studio Pro, you are massively limited in which plugins you can use, so you end up allowing your operating system, whose main job is to allow you to run the software applications you want/need to use, to determine your choice of applications. That's really f**king stupid if you ask me.

I can't think of a more different DAW to Studio Pro than Bitwig, so it's not even a reasonable replacement for your preferred DAW. It's a classic example of the tail wagging the dog.

Just want to chime in and let you know that Linux, through WINE, can now run all Adobe software. There was a major patch announced last week.

[audiojunkie]

We did our first live show with Studio Pro last night and it performed flawlessly. It definitely feels more robust, more reliable, although over the past two weeks I've noticed something weird - If I load up the whole set, run through it straight away and then close all the songs, it's fine. However, if I leave it for any length of time, either before I start the run-through or after I've finished, it will crash when it starts closing the songs. It's a bit weird but of no consequence. In fact, last night it sped up the changeover after our set because it takes a couple of minutes to close the songs one-by-one, as it asks if you want to save each song or not. The crash was quicker.

Oh, in case your interested, the gig went really well. lots of audience engagement, particularly with our new AI generated songs, lots of dancing and thrashing around.

It’s cool that your gig went well! One of these days, you’ll need to post a live show. I doubt I’ll ever get enough money saved to go see a live show.

Go into your task manager when you first start everything up. Check it periodically as time progresses. How does your RAM look. The symptoms you describe sound a lot like a memory leak. If your RAM usage continues to go up and up, something may not be releasing all of the RAM back to the system.

[thievedletter]

...it will crash when it starts closing the songs. It's a bit weird but of no consequence.

I've had this type of thing happening even in version 7. I close the project and it just hangs. Similarly, by then I've already saved, so I kinda just shrug it off, but it seems to not want to fully close my session for some reason.

[BONES]

I'll give that a go, it sounds like a reasonable assumption. Thanks for the tip!

Just want to chime in and let you know that Linux, through WINE, can now run all Adobe software. There was a major patch announced last week.

On top of an abstraction layer! Adobe's shit is unreliable enough running native, I shudder to think how f**ked it would be on top of WINE. Blackmagic tried running Digital Fusion that way and it was an unmitigated disaster that trashed the reputation of the application.

[jamcat]

...it will crash when it starts closing the songs. It's a bit weird but of no consequence.

I concur with audiojunkie. It sounds like a memory leak or something not letting go of its resources gracefully. It’s probably one of your regularly used plugins, not Studio One/Pro itself.

Send a crash log to ChatGPT. It will be able to analyze it and tell you what’s causing the crash. Then proceed by contacting the relevant tech support.

[BONES]

Oh, I know exactly which plugins cause it. It's been a regular issue for years, across at least half-a-dozen different computers, that neither PreSonus nor Ujam were interested in fixing. They've seen all the crash reports but they weren't interested in installing any of the problem VSTi to see if they could replicate the issue.

[jamcat]

It’s probably something really basic like Ujam not calling a destructor for a C++ class that dynamically allocates memory.

[Grizzellda]

Hey BONES, you are talking about evolution, and stuff changing.

Were you not a kid once? Hey KVR, pause to reflect on what kinda kid wuz BONES???

Did ya change overnight BONES? Were you suddenly a grown up, and you weren't the day before?

Evolution is gradual, it is how the Creator rolls. Also, I feel that "Fender Studio Pro", and other Daws are continually evolving. Of course I will mention MuLab, because...well just because, I always mention MuLab.

So there!

[BONES]

That's not evolving, that's just growing up, becoming the thing you were always going to be. I'd call it "maturing", which is what I am far more interested in when it comes to Studio Pro. I don't want it to change into something else, like Fruityloops or Reason did, I want it to get better at what it already is.

[Touch The Universe]

Evolution is gradual, it is how the Creator rolls.

df7c5e03-75a4-4aef-b7e4-73e1a9fe4b0b (1).png

[Grizzellda]

That's not evolving, that's just growing up, becoming the thing you were always going to be. I'd call it "maturing", which is what I am far more interested in when it comes to Studio Pro. I don't want it to change into something else, like Fruityloops or Reason did, I want it to get better at what it already is.

Solid post, I get your angle...

Perhaps what we each think "evolution" means, is different.

Like, FSP will likely continue to advance and get new cool features, but will never change into MuLab, and vice versa.

By the way, what do you feel that Reason and Fruity changed into? And did that affect your usage of these apps?

[BONES]

I don't need new features, I'd prefer that existing features were refined and improved. We get a good amount of that in Studio Pro but stuff like a Session View and a new reverb are, to me, a waste of resources that could be put to better use. Unfortunately they need to keep growing the user base and existing users seem to want to get new things for their upgrade money, so I understand that compromises are necessary. But it does annoy the shit outta me.

[jens]

[...]

Trolling or serious?