• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Are crashes auto reported to developers?

J

John Vere

Active member
Pro Studio Crashed when I clicked on the Close button after saving my work.
A dialogue opened about reporting to the developers with a bunch of boxes all ticked so I said OK and it disappeared.
I took note of that it showed it was saved in a folder. I opened it and there was the typical Greek stuff.
Anyway is this automatically sent to the developer or am I supposed to do something?
 
You have to attach the dump file to a support request which details what you did to cause the crash/hang and send it to support by logging into https://my.fender.com/support/open.

Unlike many major SW manufacturers, there is no automatic user tracking data, AFAIK.
 
Oh well Not really a big deal. That sounds like way too much work to me.
What’s weird is reading the crash report it shows something about the audio engine and 44.1. I have absolutely nothing that uses 44.1. I checked the project that crashed and it was 48.

There’s also a bunch of stuff about Fenders plugins like Splice? Rumble etc. I have never used them. The project was only 4 midi instruments and only Effects were stock eq, compressor and reverb. Nothing 3rd party.
I simply Saved it . And then clicked Close. Poof!

I opened it again with no problem. And then I closed it again with no problems. Open another project and working for 2 hours. So just a Random stupid crash But I don’t think I have ever had Studio one ever crash.But then again it’s not Studio one now.
 
I've crashed it many times by pilot error... moving too fast for the application to finish previous command. Never had a crash where the dump reported a SR issue.
 
John Vere said:
...
What’s weird is reading the crash report it shows something about the audio engine and 44.1. I have absolutely nothing that uses 44.1. I checked the project that crashed and it was 48.
Click to expand...

Might be your OS grabbing hold of the audio device and deciding to run at 44.1kHz?
 
Gerran said:
Might be your OS grabbing hold of the audio device and deciding to run at 44.1kHz?
Click to expand...
Everything is set for 48. Even Windows.
I think it’s the software has this built in setting to default to 44.1.
I posted about it a while ago. If you open a Midi file it always defaults to 44.1. Very annoying because you might not notice it.

Later on the same project crashed when I tried to open it. It is the most simple project on the planet! I started as a New Project blank.
It’s 2 Wave files48/24 Guitar and Vocals. Drag and drop.
I added the stock EQ and Compressor added a reverb bus using the stock reverb.
Thats what crashed the first time after I saved it and closed it.
I reopened it right away with out a problem.
I then switched to another project and then closed down.
After dinner I opened Studio one by mistake. I closed it and opened Fender. When I clicked on the project on the start screen it crashed.
I got a screen asking if I wanted to start normally or disable stuff. There was some very weird things on that list that to me have nothing to do with what I’m doing. SI I unchecked them. I should have taken a screenshot. One of the items I unchecked was ARA because at this point I hadn’t used Melodyne.
Anyway project opened and I worked on it for a long time.
But I made a mistake on the very end of a bass part and I realized I haven’t learned how to do a punch in yet. Oh well I’ll fix it with Melodyne. Oh oh. No problem just totally shut down and crossed my fingers.
It loaded up no problem.
Not sure if it’s normal but Auto Scroll doesn’t work in Melodyne anymore. Definitely was checked. I’ve used Melodyne since version 3.
 
John Vere said:
Everything is set for 48. Even Windows.
Click to expand...

If you really want to ensure control over sample rate etc - your DAW (and Windows) should only ever know the existence of a single audio interface - the one you use with S1/SP.

Any other vectors - like the usual crappy built audio chip on your motherboard should be disabled in the BIOS so it's existence is permanently removed from Windows and so it can never interfere with a DAW install.

VP
 
Vocalpoint said:
you really want to ensure control over sample rate etc - your DAW (and Windows) should only ever know the existence of a single audio interface
Click to expand...
Been doing this since beginning of time.
That and HDMI.

I’ve never understood why people say they don’t do this because they use on board audio for other apps. I’ve never had any issues using any ASIO interface. Windows can access my interfaces using WASAPI.

One problem is Windows updates will reinstall the Realtek drivers. I just found 5 Realtek apps that I had uninstalled a year ago.
 
John Vere said:
One problem is Windows updates will reinstall the Realtek drivers. I just found 5 Realtek apps that I had uninstalled a year ago.
Click to expand...

Windows can never install drivers for hardware that does not exist.

All my ASUS boards here have Realteks on board - if you kill the sound chip in the BIOS at OS install - it can never exist for Windows at all

HDMI remains enabled here since I never use a third party graphics card in any of my DAWs.

VP
 
You must log in or register to reply here.
Back
Top