Bug Report Unspecified Error

Katie Donovan

New Member
THIS IS NOT A "proper" BUG REPORT. FYI ONLY:

There is obviously a major bug in the latest build.
Many users across multiple diverse platforms are encountering the "unspecified error" issue.
This error circumvents the error logging.
That tends to suggest malicious intent behind the error.
I use OBS on the following platforms:
Windows 7 x86
Windows 7 x64
Ubuntu 14.04
MacOSX El Cap

All of them present this error.
Ergo, it is not any of my systems, or platforms, or ancillary plugins/whatnot.
Your latest build is buggy, and the bug appears to be malicious.

I'm switching back to OBS Studio until the patch is out.....
 
Last edited:

Katie Donovan

New Member
Do a forum search for, "Unspecified Error."
You know, what the DEVS ought to be doing....lol
Notice the dates.
SOMETHING is wrong with the build.
I just rolled back to OBS Studio and disabled nags and whatddaya know? It works like a charm......
 

Boildown

Active Member
What were you using before OBS Studio? I wouldn't characterize moving away from OBS Classic back to OBS Studio "rolling back", for example.

Which build is the "latest" that is working poorly? Which is not-the-latest that is working properly?

Where's your log files?
 

Harold

Active Member
So in short, you're complaining about people putting in terrible settings and otherwise using unsupported hardware and blaming the devs for user misunderstanding?
 

Katie Donovan

New Member
I am not accustomed to repeating myself, nor engaging in a fruitless debate over the pitiful direction "open source" software seems to be taking, as exemplified by this issue.
Suffice it to say the open source movement seems to now be moving itself over a cliff following a dollar bill, not unlike the proverbial donkey and carrot gag.
Since when does "open source" mean, "do our stuff for us" when it breaks?
As I said, there is an issue in this build;
I'm too busy scrambling to meet a production deadline to spare time to figure out what a log even is, let alone where to find it or what to do with it when I do.
I click button, machine do things. That's what I know.
Only now, I had to figure out how to install what I've been using for years without issue because someone said Studio was deprecated so I had to upgrade....
Then my studio halts all activity while the f'n software gets re-tooled....again....
 

Osiris

Active Member
Studio deprecated? What are you talking about? OBS Classic is the one that's deprecated and has been for quite a while.
You have given basically no info about your problem, haven't provided a logfile, no system specs.
 
Last edited:

mrasmus

Forum Moderator
If you're seeing a novel issue on newer builds of OBS and not on older, than it'd be great to be able to sort out what's going on. As for the idea of "'do our stuff for us' when it breaks", there's literally nothing that devs can do if you provide no relevant details of your setup, what version(s) you're seeing the issue on, and what settings you're using.

I want to clarify something really quick: Open source efforts have always, from the beginning, relied on their users, as a community, to sort out issues; OBS doesn't have big corporate dollars to go and spend on undreds of computers and QA staff like a paid product would. The devs make every effort to release a stable program, but with an infinite number of potential hardware configurations it could get run on, sometimes pre-release testing misses things.

Luckily, if rolling back to a previous version of Studio got you back to a stable state, that's the best possible case for both you and the project, if you're willing to help: It means that you have a workable version (all of the installers should still be on the github) so you're not blocked from streaming, but you also have the opportunity to provide diagnostic information such that the devs can sort out the issue that's hitting you. If you can say "when I launch version 18.0.2 and get this specific error after I do X every time, but when I launch version 18.0.1 with the same settings and do X it works", then we're on a great track, but that's just the start. Uploading and sharing logfiles from both versions, in which you do the same things and different outcomes occur, is exactly the type of diagnostic information that lets devs be able to investigate an issue; if you can do that, it might be feasible to address whatever's plaguing your setup. The process for uploading logs and error logs is well-documented here, if you're unfamiliar.

If the devs just get "it broke, fix it" (which you say here, and many people across many versions have said similar things) there is literally nothing actionable, so you shouldn't expect anything to come of your complaint.

You paid nothing for OBS, and came in here to act hostile towards the 100% volunteer support staff + the volunteer devs, but literally didn't give any of the necessary info to even start diagnosing your issue. I urge you to see how frustrating that could be to be on the other side of. Let's take a second to breathe, reset, and see if we can't move forward to both improve your own situation, and the project itself.
 

Boildown

Active Member
because someone said Studio was deprecated so I had to upgrade....

OBS Classic is depreciated, OBS Studio is the current version. Whoever said that misled you. Or you're just confused.

Which build is the "latest" that is working poorly?
Which is not-the-latest that is working properly?
Post your log files.

Until you do/answer those you'll get nothing here except possibly muted by the only people on this planet able and willing to help you.
 
Last edited:
Top