-
Hi and welcome to the Studio One & Studio Pro User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!
8.2 Crashes when Instrument Track is created
- Thread starter getatnard03
- Start date
Sebastian Holtzer
Active member
I have been having the same experience on 8.2. When I create a new song, create a new instrument track and select the atom sq, as soon as i click OK, it crashes. Support said it was a conflict with moises and to uninstall and reinstall but that didn't help. everything works fine if i create the track, then go back and select the Atom SQ. It worked fine before upgrading. Wondering how easy it is to downgrade back to 8.1
Vocalpoint
Well-known member
No "moises" here - and will never be.
And v8.2.0 is still crashing on me with a new instrument track.
VP
Whether the connection between this site and Fender is official or unofficial, your first impression strikes me as true. The "developers" things amiss found here get reported to work for Fender, not some unnamed company. Continuing to pretend no one who works for Fender ever finds themselves viewing these pages might not stand up to scrutiny if their online activity was available. Why keep refuting there's even a minimal connection? Alternatively, superusers and moderators on this site could just state it's an unofficial forum without a Fender moderator and leave it at that. That much is indisputable.
getatnard03
New member
Ive been working with support yesterday and today. We tried a bunch of things but none of them work. They logged it with the dev team and they told me to check a for a fix in a future update. For now Im good with either dragging external instruments in my arranger or waiting to add instrument afters its been created.
Yeah looks like a neat Add Track feature,
As @Lukas is escalating this upstairs. I suppose it's sit back and wait for a result.
Kindest regards folks.
Vocalpoint
Well-known member
The only "connection" (to the DEV team) that I am aware of is Lukas - and his ability to take things up to the proper channels.
As far as Fender DEV goes - which is really the only official group I am only ever concerned about - my take - is it is very unlikely that any actual Fender dev employee (listed on the About Studio Pro screen) - spends any time here - whatsoever. Either for fun or for actual dev concerns.
And even if we did have the slightest evidence of an actual DEV team member checking in - that does not mean he/she is suddenly entering tickets into their systems based on our chatter in here.
If you want something to get in front of the DEV team - it is always better to simply ask Lukas if he can escalate for us and carry on.
VP
Last edited:
Fender developers wouldn't be very good at their jobs if they didn't take user reactions into account. You can choose to believe that feature requests sent directly to them are the only source of feedback that affects future developments; I choose not to, just like I choose to believe they read reviews in what's left of magazines as well. I don't believe they exist in some sensory deprivation chamber where their stern taskmakers force them to avoid reading this forum at all costs. You can. All that said, it doesn't really matter if they do or they don't. And I understand the necessity for Lucas and the mods to point out this isn't a forum where developers interact and field requests to newbies. Except Ari, who posts here regularly enough, is a developer, is he not? So my small ask would be to temper the continual statements that Fender has nothing to do with this forum to the level I already stated.
Vocalpoint
Well-known member
I do not believe Ari is a developer. And we haven't heard from him in a long while either.
VP
Crossinger
Active member
Iirc Ari is “head of quality assurance”, a software tester. And this role might be connected to software development skills.
Developers usually don't receive user feedback directly at all (there are exceptions, of course). They work based on tickets. Browsing forums isn't typically part of their job. That's up to product managers or product specialists like me.
You can find us all on the 'About Studio Pro' screen
First off, I'm not on the warpath about any of this.Developers usually don't receive user feedback directly at all (there are exceptions, of course). They work based on tickets. Browsing forums isn't typically part of their job. That's up to product managers or product specialists like me.
View attachment 4174
You can find us all on the 'About Studio Pro' screen
It's not going to make a bit of difference to my or anyone else's tracks. But "developer" or "quality assurer," sorry, both of those are Fender positions. Personally, I'd prefer a supportable position—that for the most part, this is an independent user forum—rather than on insisting there's no connection whatsoever to Fender which is unsupportable. We already know you're a direct conduit to Fender, with a good working relationship, which is perfectly fine. As long as Fender likes you enough to let you have at least limited access to their code, enough to make sure your add-ons work properly, that's dependent. Not independent. Which still doesn't really matter in the overall scheme of things.
Vocalpoint
Well-known member
We get that you are not on the warpath - but there are those in here - usually new users (but oddly not always) that simply assume that because this forum dives deep into Fender Studio Pro - and there we are chatting up testing scenarios and bug discoveries - that these discussions are automatically being viewed (in real time) by the internal development team at Fender for this product.
This assumption is flawed.
Now I am not saying with 100% certainty that since this forum was created on 11-09-24 - that nary a single actual real life developer of Studio Pro - has not viewed a page here and there - but without any actual evidence indicating they ever have - my take is that they have not.
It is important (once in a long while) to gently remind folks that we are totally on our own out here and that there are established processes that must be used to actually get an issue out of here - and into the actual developer ticket system - for future analysis.
VP
This is the important point. Even if every Fender developer & QA person spent oodles of time here, the reports still need to be filed. Who visits here when and how often doesn't change this.
That's why I already said, "I understand the necessity for Lucas and the mods to point out this isn't a forum where developers interact and field requests to newbies."
I'm just pointing out that when one of those flawed assumptions pops up, a better script might be, "While an occasional Fender employee might chime in here, none of them do it on a regular basis, nor is it part of their job description, so your best bet is to contact them through regular Fender feedback channels rather than expecting responses here." As opposed to "this site has no connection to Fender whatsoever" which makes some people roll their eyes.
Enough bandwidth spent on this. No need to keep debating (at least for me).
Last edited:
Vocalpoint
Well-known member
An even better script is - "File a support ticket via your MyFender account - and tech support will take it from there".
VP
Um, while that's more concise, it doesn't get the point across that this site and Fender are mostly independent. So that newbie could still be confused over whether this site is Fender Support, or just the wrong part of Fender Support. If you can stay concise and still get that point across, we'd have a winner.
Vocalpoint
Well-known member
Well - when it comes to getting some actual "Fender" eyes on your issue, bug or whatever - it says exactly what it needs to say - without saying anything extraneous.
And there is no other "consumer" conduit into Fender Support/DEV - outside of this. (Unless of course you are on PM terms with Lukas or Ari
) or the mods on the board here are kind enough to enter a ticket for you.Just not sure we really need to toot the ole "independence" horn with every post reply.
VP
TimC340
Well-known member
This is a lot of words for a very simple concept - the forum is not Fender's, and doesn't obviate or bypass the need to report issues via the Fender system. What it does do is allow is to share intel between ourselves, and potentially solve problems that aren't actually a bug in Studio Pro - or if they are, we can perhaps create a workaround that allows us to get what we need done while we await an official fix.