Bug Report OBS Studio crashes right at the start.

Status
Not open for further replies.

Cryonic

Member
Thats it. Cant give you any information besides hardware and software versions and logs (where you can also see what hardware and software i use).
No idea what causes the crash, but it should be fixed asap since thats the newest windows build and will go public in a pretty short time^^
 

Attachments

  • Crash 2016-04-08 21-35-54.txt
    50.5 KB · Views: 109
  • Crash 2016-04-08 21-31-37.txt
    50.5 KB · Views: 40
  • Crash 2016-04-08 19-32-50.txt
    50.5 KB · Views: 27
  • Crash 2016-04-08 19-32-39.txt
    50.5 KB · Views: 31

Cryonic

Member
Well thats for you guys, you have a chance to optimize on that build before it goes public. And i need that for streaming. Your software is the only one that refuses to work
 

Sapiens

Forum Moderator
Don't run insider builds on your production system if having your software work reliably is a priority. This type of issue will be addressed if it still happens when the updates go live for everyone. It's unlikely that much, if any, effort is going to be spent on making OBS run on insider builds.
 

Cryonic

Member
The insider preview build is pretty much 90% of what goes into a regular big update a couple of weeks later.

That issue has to be fixed anyway. Or at least give me a workaround.
 

Suslik V

Active Member
Who knows, maybe in few updates win10 wouldn't use this file at all. Studio has its own road map. I think, best answer should be: when its done...
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
We've had similar things happen before with insider builds and last time it was fixed before it went public. It's clearly not crashing in our code, but in Microsoft code. It's happening on a video device capture source which went inside Microsoft API (meaning inside Microsoft code).

There is one thing you can do in the mean time if you wish, you can reset your scene data to remove the device from the scene (What I really need to do is implement a safe mode for this).

1.) Press Windows Key + R and paste this in and press OK: %appdata%\obs-studio\basic\scenes
2.) Delete or move, or manually edit the .json file associated with your main scene collection (usually Untitled by default)
3.) Start obs up and it should reset your scene data. You may have to avoid adding a capture device or webcam until Microsoft solves the problem.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
I'd just like to emphasize what sapiens said, that if you have a critical stream or recording setup that you rely on, you really should not use Microsoft insider builds of windows. This sort of thing has happened before and it'll probably happen again in future insider builds.

That being said, I really do appreciate that people are testing the insider builds with OBS so we can get these possible bugs in their builds solved before they go public. So thank you very much for testing that out and discovering this.

If Microsoft has a means of reporting insider build problems, please make sure to make a report to them about the problem (though I'm sure that it reports back to Microsoft when any program on the system crashes in insider builds anyway).
 

Cryonic

Member
I send all the crash dumps/logs to MS with a description. And i dont mind rolling back once in a while to a previous build. But i want my software to recieve day1 patches to keep it functional. Specially for alpha&beta status games, preview builds and generally everything that is not officially released. A lot of streamers depend on that stuff so it is priority Nr.1 over everything else - having a 100% stable software no matter what changes where.
Generally the old OBS works good - i managed to have a 4h stream right now with it, before i had some freezes while using the restream chat capture via webserver with some custom CLR browser settings. But OBS MP is working 25% of the time and with selected games only. Game capture on The Culling stopped working at all... Just a fat facepalm, when the old software without updates works better :D

And yes. When i remove the scene settings, it works. When i try to add a video capture device (the usual C920) and just open the popup selection window for the video capture - crash. I can test a few things like an older Creative webcam, opening it without a cam attached, lets see.
 

Osiris

Active Member
If you absolutely want stable software, you should NOT use insider builds. Higher chance of the software being not as stable.
 
Last edited:

Cryonic

Member
I try to help making Win10 better. This is why i use it, i could just use a regular Win10 or an older Win8.1 installation.
This is also a reason why i stream and work with it, to make sure my software that i use on daily basis IS stable under Win10.

Like i said, the old OBS works 100% stable, with all Insider Preview builds for like 6 months already. There was a minor issue with the capture, that dropped my performance, increased the CPU usage and dropped FPS - but that was like 5 months ago and was solved pretty fast.
The problem is OBS studio, it is really unstable so far and has way more capture problems with games.

Dont tell people to stop helping the software developers and fall back to the safest working version that is still avaliable out there. I could use Win7 and dont even try, it would work, but the whole point of improving software that i enjoy goes away with that.
Instead of working with the people who report errors and bugs you tell them to fall back to a safe version? Worst thing possible if you want your software to be stable with the latest release. I expect that stuff to be fixed withhin 1-2 working days after a build rolls out the first time on the fast ring. Specially because MS releases information about the build before it actually goes out. Remember, that build goes through us (fast ring), in a couple of weeks it will be in the slow ring and in a month it will be a full release for every Win10 user.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
1.) Studio and classic have a few minor differences in their device code, and it would be easy to assume that based upon the fact that you have it happen in one but not the other, but they also use different device defaults and it's set up slightly differently, so it's not yet safe to assume that it's a bug in studio code when you factor in the next two items.
2.) It crashes in a microsoft code, not in OBS code. The crash log quite clearly shows that. Microsoft code does not typically crash like this.
3.) I have a C920 myself, and the latest non-insider build of windows, the program does not crash with it with any setting I throw at it. This is the most-used webcam on the market, if there were a bug with the code I would receive a lot more crash reports than just windows insider users. There's clearly a difference between the insider and non-insider builds here, and it's very very unlikely something that "exposes some dormant unseen bug in obs studio".

The device has just never been a device that's caused trouble, nor is it a device that does anything unusual. It's not even a device that uses custom drivers from the OEM, it works through microsoft's own device code. So although I can understand your doubts due to it working in one but not the other, the most likely situation still points towards a bug in microsoft code. I am not even trying to brush off the issue here, if I had a suspicion that it was caused by our code I wouldn't be afraid to admit it, I will always admit it when it even hints to a bug with obs code, but as it is, all evidence points towards it being a microsoft issue. Can I say for 100% certain? No -- for all I know I could end up eating my words, but again it's extremely unlikely based upon the information so far.

As for the part where you appear to be pushing back at me for saying "don't use insider builds", when I said "don't user insider builds", I specifically stated "if your stream/recording setup is critical". What does "critical" mean? It means "if it is your source of income or for a major production". I will always tell people who have critical stream/recording setups not to use the microsoft windows insider builds, and will continue to do so. However if you want to test, as you stated, that's perfectly fine. In fact, I would encourage anyone who does not have a critical streaming/recording setup to test insider builds it if they don't mind dealing with that potential instability that can happen with them. So clearly that was a misunderstanding that somehow got blown out of proportion.

Lastly, if you're having problem capturing certain games with studio, could you be a bit more descriptive about your problem? Or if you've reported it in another thread, could you link me to that other thread? "25% of the time with selected games only" isn't helpful to me. State your problem more descriptively: what games you're having trouble with, and what is or is not happening properly, with logs. The game capture code is a bit different between the two, and unlike with the C920 insider build issue you're having now, it's quite possible there could be a bug with the newer version of game capture, but I can't know without more information.

For example, "I'm getting a black screen with [x], [y], and [z], and here are the logs from those sessions where I tried to capture those games, doesn't happen with classic". That's literally all you'd have to say, as short as that, and it would make me happy. (This is assuming of course that it's the game capture source, if it's not you'll have to state how you're capturing them)
 
I don't believe I have a Windows 10 Insider build, just the regular commercial one, and this started occuring to me today. I streamed last night with no problems, but just a little while ago when I went to start a stream up OBS studio reported a crash.

I have attached logs and the mini dump. Please let me know if there is anything I can do to help.
 

Attachments

  • 2016-04-08 22-58-39.txt
    9 KB · Views: 29
  • Crash 2016-04-08 22-58-41.txt
    31.3 KB · Views: 29
Also, the suggested work around with the .json file worked like a charm, so perhaps MS pushed some kind of update to all versions of Win10 that messed with one of the sources?
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
That's not the same crash that the OP is referring to (doesn't have anything to do with devices or windows), though thank you for reporting it, I'll take a look at it. It's very likely a bug in that case.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
portuguesecaptain - I noticed that crash is happening on a crop filter. What source do you have a crop filter on? (Actually, could you private message me with more info so we don't derail the original poster's thread?)
 

Cryonic

Member
@Jim:
My setup is not critical, but still, having a software crash is always meh. I just expect that to be fixed withhin like 24-48h after that goes out, specially small stuff like a single new driver producing an error.
I know that MS fk`d up here this time, but they will not hotfix it, so it will most likely take 2-4 weeks to get a new build that has a fix inside. Or they will keep it as it is right now, because it is actually stable.
I reported that to MS, no answer so far. I think that is planned. And will not be the first time where MS decided to mess around with the video capture in many ways.
The problem is definetly on the software side, since removing the camera or replacing it with a different webcam did nothing.

Btw i use only the old OBS if i can, because the new one is just years away from being userfriendly and stable (compared to the old). Testing and reporting bugs would help maybe, but i still hope that a) all needed settings and options will be moved to the main screen b) midi hotkey mapping (and in general mapping for all elements) will be released sooner than later and the software will lean more towards a professional tool, not a toy where you have to search for settings pretty deep. Modular interface design (so i can bring my crop filter or sound filters on top of the main screen by dragging it around) is an absolute must for a decent worklflow, so i dont have to touch the software at all.
But all that is my personal preference and not a priority at all, stability is.
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
I can't tell if I'm being baited. Years away from being user friendly? You have got to be baiting me, I can't tell. I seriously can't tell right now. And yet I'm going to fall for it -- here we go! I am seriously experiencing physical pain right now by engaging in this conversation.

Studio is vastly more user friendly than the original. User friendliness is one of the things I emphasized upon the most in studio. Please, feel free to tell me why every single specific reason why it's "years away" from being user friendly. Explain to me in detail how OBS classic is "years ahead" more user friendly than studio.

I couldn't even understand someone saying it more mildly, such as "a little bit less user friendly than OBS classic". I actually couldn't even fathom it.

I see you mentioned "all needed settings and options (should) be moved to the main screen", and "not a toy where you have to search for settings pretty deep". Oh boy. Are you seriously talking about the advanced output mode? I hope you're not talking about advanced output mode. Are you? Are you talking about advanced output mode? Please tell me you're not. Please, please tell me you're not actually suggesting that advanced output mode is the problem you have with it. Please, for the love of god, for the love all existence, please, please don't say that advanced output mode is your criticism that makes the program "years away from being user friendly". If that's seriously, actually what you're saying, I think I'll actually just build a rocket and fly myself directly in to the sun. The idea that we should move all those advanced setting so all the users have to use them instead of having a simple output mode is complete insanity. I can't actually believe what I'm reading right now. I am seeing my life flash before my eyes.

99% of users only need simple output mode, and that's where the actual user friendliness is meant to be. Why do you think advanced mode and simple mode are separated like that? It's to make it more user friendly. The simple output mode automatically configures all the encoding settings to the optimal settings for you, it's ideal for 99% of users. Even I use simple output mode because it automatically configures all the optimal settings. There's almost no reason to even use advanced output mode for general recording/streaming. Multi-track audio maybe? Perhaps I should add that as a recording option in simple output mode. But people very rarely ever even need multi-track audio.

And please, before you include the crop filter, the crop filter was a temporary thing I wrote to give people some way to crop until I had time for alt-cropping, which I finally just recently finished for 0.14.0 -- it's already finished on the master branch for the next release.

Stability on the other hand is another story, there's some argument there, classic is a bit more stable -- a bit. Not "years" more, but "a little bit". Studio is a little less stable just because of active development, where as classic has been almost entirely just the occasional bug fixes for the past year. That filter crash the other guy had is evidence of it. If you prefer the maximum possible stability then that's fine, though there are fundamental inherent design flaws and issues in classic that won't be going anywhere because of how deep those design flaws went, design flaws in both audio and video, and design flaws that prevented us from being able to add new features. "Years behind" is such an overblown exaggeration though. It's like you just want to overly exaggerate everything, and I just can't take it seriously anymore.

I must have been baited. I just can't even take this conversation seriously at this point. Let's just forget this conversation ever happened.
 

Cryonic

Member
Not baiting you. Take a look at professional software, i will link you some pictures.
Userfriendly for me is: everything is customizeable and is oriented for professionals who have a) more than just an idea what they do and b) love everything right there.

Here we go:
Resolume VJ - https://hearandknow.files.wordpress...rst-video-the-internal-recording-function.jpg
Arkaos VJ - http://vj-dj.arkaos.net/sites/default/files/images/arkaos-gvj2-mxr-001.jpg
All that software does almost the same task, but it is designed towards mixing videofiles together and output it locally, not record or stream it.
Ableton live - http://www.heise.de/imgs/18/1/7/4/2/5/2/0/Ableton_Live_2-81530673b4104831.png

For the "normal" people that software looks like a complete mess, every time i open it in front of my friends etc. - i earn that "WTF is this shit?!" look.
But for an expirienced user this layout is amazing, everything is right there, you see everything what you want, you can also remove or add some parts of the interface, depends on how you love it.
Right now to open a filter for one of my sources, i have to go through a dropdown menu, click on it, a freakin popup opens and there i can click my way to the filter and the right settings.
For me thats just pure jungle, optimized for noobs so they will never touch it and go deep in that jungle >.<
Thats not a console where you slap your stream key in and press stream: done, there is not much else you can do...

And i hope that OBS will be more tailored towards professionals with years of expirience in the video/DJ/radio area, audio editing and just general knowledge that is needed to stream on a high level that can be compared to a TV show in terms of production quality. Right now it is possible, but requires a lot of workarounds and twists, instead of being simple and offer everything right there where your cursor is...
 

Lain

Forum Admin
Lain
Forum Moderator
Developer
Did.. did you just seriously just complain about "user friendliness" and then show me a pic of ableton live and DJ programs with bazillions of knobs, sliders, and settings on the main window?

"Userfriendly for me is" [...] "WTF is this shit?!" [..] "Optimized for noobs so they will never touch it".
"Userfriendly for me is" [...] "WTF is this shit?!" [..] "Optimized for noobs so they will never touch it".

Do you see the massive contradiction here? You keep saying "user friendly", but the phrase has lost all of its meaning. It's become a perversion of the phrase, its meaning hollow, and butchered into oblivion. If you say "user friendly" again I will jump out of my window through the glass right now, and then after writhing in pain on the ground, I will roll in the shards of glass until I black out. So just.. stop. Stop, please, just stop right there. I'm not even criticizing what you want. I'm criticizing how you're communicating it to me.

*Breathes deeply* ..Okay, listen. I understand that's what you want. It's perfectly reasonable to *want* something like that. We all can dream of having a program tailored to our personal needs and wants. But the way you've gone about doing it is not the right way. The way you criticize the program in such an overly exaggerated and unintentionally deceptive way; it's just not the right way to do it.

Let's stop here for a moment and examine the situation. Right now, again, I'm not criticizing what you want, I don't mind that. While it's unrealistic to expect one or two men to make the next ableton live ("ableton live, but for streaming!"), I've heard people ask for far more. I don't mind that you want this.

What I'm ultimately upset about right now is your inability to properly communicate it in a sensible way.

Firstly, your criticism is not constructive, it's clearly exaggerated ("years away"), uses unintentionally deceptive wording ("not userfriendly"), and I have to be honest here, although you may not mean it, it feels completely provocative. I don't mind negative criticism, people occasionally come around and express anger or will give harsh criticism if I messed something up, and I could name you a few. I always listen to it regardless, and try to do something about it. But the way you communicated your wishes here is probably about as unhelpful and the worst way to go about doing it as humanly possible.

Secondly, using the phrase "user friendly" was the wrong thing for you to say from the start. You're using the wrong phrases to describe what you want, "user friendly" is not the word you'd want to use here to describe how the program is "lacking" in your eyes. You'd want to use "customization", or some word similar to that.

I'll give you an example of you how you could have simply and concisely communicated this entire situation without having caused this cluster%&#* of a mess.

"I personally would prefer it if OBS had a lot more features, and all the features were on the main window, something like ableton live but for streaming. It just doesn't meet my needs at the moment. OBS caters too much to casual users, I'd prefer software that's catered to professional users. It's also somewhat unstable at the moment, so I've been using the classic version instead of studio." (although that last part is hypocritical because this entire thread was about a crash you're getting caused by a microsoft windows insider build)

That's how you could have phrased the entire thing from the very beginning. Do you see the difference? It uses proper wording, it's not provocative, it doesn't exaggerate; I summed up pretty much everything you wanted to communicate in one small, concise paragraph. I'm not asking you to praise me, and I don't even mind negative criticism at all. But what I do mind is when I see overblown, exaggerated, poorly worded, poorly thought-out negative criticism.

So next time, just think a lot more about how to communicate your wishes or problems.

Anyway, if you want something like that that has as many features as ableton live but for streaming, you'll be disappointed because that's not really what I'm trying to make. I have my own personal "vision" for how the program should be, and having millions of options on the main window isn't something I want for this interface. You'll simply have to live with that fact.

Now, let us cease this conversation, gracefully, while we both still have the chance. Let's let it go now. Before trying to communicate further, find and read the book "how to win friends and influence people".
 
Status
Not open for further replies.
Top