First Timer, Having Problems from the Start

[Flon Klar]

I just started a trial with S1, after 32 years on Cubase. From day 1, I 've been having crash issues, mostly centering around activity with Kontakt (8). Just wondering if this something that happens regularly, if it's a known issue, or it's just me. Thanks.

 

[Vocalpoint]

You would need to provide a bit more detail on exactly what you are doing and how the "crash" issues are appearing related to Kontakt 8.

Also some version information would help too. OS - (your exact version of Windows), which version of Kontakt etc...

VP

 

[Flon Klar]

You would need to provide a bit more detail on exactly what you are doing and how the "crash" issues are appearing related to Kontakt 8.

Also some version information would help too. OS - (your exact version of Windows), which version of Kontakt etc...

VP

Sure. I've added to my signature; I can add more if you need it.
Kontakt version is 8.7.2.
As far as I can remember, the crashes have occurred while I was adding instances of Kontakt to my S1 project and while adding multis to Kontakt. I wasn't really paying attention to specific details, but if it happens again, I will be sure to note it. My original question was just to inquire if this TYPE of thing happens often, like maybe the demo version is unstable, as I DO notice some other anomalies, such as the MIDI channel selectors in the track list (some are called Eveut, some are Event, some are Ch- and it just occurred to me that Eveut is EVEnt inpUT). Thanks for the response.

 

[Vocalpoint]

The labels become "normal" when you expand the width of the Tracks panel.

When in it's default width - some of these labels "look" misspelt. You need to grab the divider between the track panel and Arrange window and drag it right. All the controls will then reveal the correct spelllings

As far as your crash goes - been using Kontakt 8 here since release and have never had a crash. Not saying it's not possible. Need to know what you are loading into Kontakt and how...

VP

 

[TimC340]

Studio One v7 has been incredibly stable for most of us, but some people have had hardware or conflicting software issues - as is the case for almost anything.

I use full Kontakt 8 and Komplete Kontrol 15 Ultimate with several other addons that exploit Kontakt, and have never had a crash of any kind. It's probably worth knowing what instruments you're using in Kontakt when you get the crashes, and whether any FX are active at the time.

 

[Flon Klar]

"It's probably worth knowing what instruments you're using in Kontakt"

Most of it was Spitfire Woodwinds, Kirk Hunter Diamond Strings and Brass, some Cinesamples stuff, and some vocal things Voices of Rapture. There wouldn't have been any active fx at the time of loading the sounds. I'm not saying that it definitely was Kontakt that brought on the crashes, I was just asking if that would be a known issue. If it's not, then it was probably something else.

Oh, this is lucky. S1 crashed JUST NOW. I clicked on my piano part to select it, then hit shift and clicked on the vocal part below it. The vocal part wouldn't select; the screen was frozen. And there's more. As I was typing this, the selection focus suddenly switched from one to the other. Still frozen. And now, after a minute or so, both tracks deselected and my headphones started a rhythmic clicking, then S1 went into play mode, but played the piano part as a staccato figure (which it is not). It is now unfrozen, after about 5 minutes of anomalies. It still involves Kontakt, I think, but it sounds possibly like a memory issue. I'll report back if I find anything else.

 

[TimC340]

Woah! Weird! I'm sure someone here will have a clue, Fion, but I'm afraid I don't!

 

[Vocalpoint]

"It's probably worth knowing what instruments you're using in Kontakt"

Most of it was Spitfire Woodwinds, Kirk Hunter Diamond Strings and Brass, some Cinesamples stuff, and some vocal things Voices of Rapture. There wouldn't have been any active fx at the time of loading the sounds. I'm not saying that it definitely was Kontakt that brought on the crashes, I was just asking if that would be a known issue. If it's not, then it was probably something else.

Oh, this is lucky. S1 crashed JUST NOW. I clicked on my piano part to select it, then hit shift and clicked on the vocal part below it. The vocal part wouldn't select; the screen was frozen. And there's more. As I was typing this, the selection focus suddenly switched from one to the other. Still frozen. And now, after a minute or so, both tracks deselected and my headphones started a rhythmic clicking, then S1 went into play mode, but played the piano part as a staccato figure (which it is not). It is now unfrozen, after about 5 minutes of anomalies. It still involves Kontakt, I think, but it sounds possibly like a memory issue. I'll report back if I find anything else.

If it is getting this bad - it's either hardware or something that only support can deal with.

Not really familiar with all of these libraries - but by your description - this sounds like things are so sensitive (for reasons unknown) that even the slightest tweak of this or that is causing everything to fall apart - which is most definitely not what I see when I use Kontakt. I pound the crap out my instances every which way and never have had a issue.

Not sure what you options are for actual support - if you are on a trial - but you might consider entering a ticket on your MyPresonus account portal and see what they say.

You can also launch Studio One in diagnostic mode by holding SHIFT and then double clicking the icon. This mode will allow you to general logs, skip plugins and other things to try to troubleshoot a bit on your own. But I would recommend support first.

VP

 

[Flon Klar]

Thanks for your attention, guys, but I've decided Studio One isn't going to work for me.

 

[TimC340]

I'm sorry it's not working out for you, Fion, but it's a big move after so long with Cubase - and if that DAW is working for you, why change? I do wonder if your PC may be a bit underpowered for what you've been trying to do with S1, and if it's still handling Cubase well then stick with what you know! As it happens, I've just (for fun) started a demo period with Cubase 15 having been a Cubase boy many years ago - all the way back to Pro 24 - and the learning curve is just as steep in the other direction!

 

[Vocalpoint]

Thanks for your attention, guys, but I've decided Studio One isn't going to work for me.

Sorry things did not work for you but IMHO - Studio One is considered one of the most mature and stable apps out there - if it is given a proper environment to run in.

Without a detailed view of your hardware, configuration of Windows , possible conflicts etc and what you believe should work vs what actually does work makes troubleshooting this difficult.

Thanks for popping by - continued success with whatever you choose.

VP

 

[John Vere]

Question about this? Are you saying that unless S1 is in Diagnostic mode that there isn’t any crash dumps created?

 

[Vocalpoint]

Question about this? Are you saying that unless S1 is in Diagnostic mode that there isn’t any crash dumps created?

I have only had 3 crashes since 2011 - so I cannot confirm (or deny) the creation of crash dumps.

I will assume they are created as encountered - and Diagnostic mode would have nothing to do with this as many users are completely unaware as to how to place S1 in this mode in the first place.

I use this mode very rarely - but for troubleshooting only - never for crash analysis.

VP

 

[John Vere]

Thank you @Vocalpoint for the clarification. I don’t think I have crashed S1 yet but I must have crashed Sonar at least once a week. I always submit the report. That is always the best way to make the development team aware of any issues.