One day back and around 30 crashes so far....

[redgazza]

It's not going well for me using Studio Pro 8 so far. I was a keen Studio One user up until version 6, then got into Reaper for the last couple of years. The difference in stability is really unbelievable.. Reaper just doesn't crash. Then I paid for the upgrade to FSP8 to keep up with developments..

What has happened to this program???!

Time has obviously been spent on making the corners of the parts rounded, and other Logic lookalike stuff, and integrating things we done need - Moises? What?

Whatever, but in terms of workflow, it's falling apart. The last 24 hours has been pathetic. I can't freeze a track and get back to the midi unless I keep the instrument active now? Complete lockup if I do that. I'm saving before loading any plugin now because it feels like Russian roulette otherwise. Crash after crash. The 8.2.1 update helped with the whole routing fiasco I was having initially (FX tracks just disappearing in the arrange page, but still there in the mixer, and no way to delete tracks etc...). I mean, come on! Who releases software which has such fundamental flaws. New problems, which were never there before. Who is testing this software????

Is it just me? I'm not a novice (mac user and producer for 35 years) - I'm regularly using Cubase, Logic and Reaper, which are all solid on my system. Not just to tinker, but full productions. Time is ticking before I forget Studio Pro for good. It's not worth the grief if this is going to be a constant battle.

Any help or advice appreciated - just don't tell me to restart my computer or check I'm not running in Rosetta etc..

Cheers

 

[madFloyd]

It's too bad there isn't some easy way for Fender to get crash reports. I'm sure that would help.

 

[Vocalpoint]

It's too bad there isn't some easy way for Fender to get crash reports. I'm sure that would help.

The app creates these on the fly and stores them.

Not exactly sure where that is on a Mac - but the OP needs to collect as many diagnostic reports as can be found and get a ticket started.

If there is really 30 crashes in a day - there are major issues over there.

VP

 

[madFloyd]

The app creates these on the fly and stores them.

VP

But then they just sit there.... I have a huge collection lol; it should be more of an automated process to get these to the devs.

 

[Vocalpoint]

But then they just sit there.... I have a huge collection lol; it should be more of an automated process to get these to the devs.

Agreed. But that's above my paygrade.

And if you have a huge collection - might be time for a ticket for you as well

VP

 

[redgazza]

Thanks for the replies and info. I went round the houses with testing all manner of things, and noticed more stability dragging plugins from the browser, rather then choosing from a dropdown menu for starters, and in the end started a new project and imported all the session data to fresh tracks, but excluding busses and send effects. Seemed to be a glitch built in to the original project after a weird missing track situation (an 8.2.0 bug), so maybe track ID getting messed up for adding a plugin unless the mouse physically drops it on...? Or routing gone weird..? I also found out in my back-and-forth with diagnostic reports and Gemini that Slate VMR actually loads all the modules in to RAM, regardless of how many used... which is probably why they have separated them out into individuals now. Thats a bit of a shocker. Also Vocalign 5 and Spectralayers aren't the best idea in terms of screwing with ARA, apparently. Automation is a total mess. "Read" buttons in the arrange page flickering or just not lit when they should be, etc... And audio playback performance still crummy in comparison to at least one much cheaper competitor in my opinion. I'm gonna persist for a while, because when it works, the workflow is sweet.

 

[redgazza]

Yes, Fender support is lacking. They won't accept .ips files, for a start...

 

[Sebastian Holtzer]

Thanks for the replies and info. I went round the houses with testing all manner of things, and noticed more stability dragging plugins from the browser, rather then choosing from a dropdown menu for starters, and in the end started a new project and imported all the session data to fresh tracks, but excluding busses and send effects. Seemed to be a glitch built in to the original project after a weird missing track situation (an 8.2.0 bug), so maybe track ID getting messed up for adding a plugin unless the mouse physically drops it on...? Or routing gone weird..? I also found out in my back-and-forth with diagnostic reports and Gemini that Slate VMR actually loads all the modules in to RAM, regardless of how many used... which is probably why they have separated them out into individuals now. Thats a bit of a shocker. Also Vocalign 5 and Spectralayers aren't the best idea in terms of screwing with ARA, apparently. Automation is a total mess. "Read" buttons in the arrange page flickering or just not lit when they should be, etc... And audio playback performance still crummy in comparison to at least one much cheaper competitor in my opinion. I'm gonna persist for a while, because when it works, the workflow is sweet.

Yes, I have the green "Read" Automations going black, once i hover over with the mouse too, since v8.2.1. Whole Playback Performance since v8.0 with larger Project is a Nightmare compared to 7.2.3 and my system is a fresh install. 8.2.1 broke some things and i would bet on that it changed some of my automations on some tracks. I would bet on cause they were set right and yesterday they were not on some tracks. I could'nt believe that but i was. These have been old Automations and i know that for sure cause i am currently rebuilding and old broken track. On my Bassline i had old automation back on my Reverb and the on my FX they were slightly off the grid.