Question / Help Is OBS Studio 32 or 64 bit?

[tonilyran]

Is OBS Studio taking advantage of 64bit windows OS's? I do see the 64bit Plugin directories and DLL's, however during the install and when the exe ran all of the files executed and logs seemed to indicate 32bit only.

If the base install is only 32bit is there a 64bit version available that I can download and install?

 

[Sapiens]

The installer includes both 32-bit and 64-bit versions. Look in your Start Menu or the .\bin folder of your installation directory.

 

[Wallaceman105]

What would be the difference, performance-wise, between the two?

 

[Sapiens]

Negligible as far as I know.

 

[the skinny nerd]

I was wondering this myself. I kept having the issue of missing runtime c++ during install and after installing the 64 bit version half a dozen times or more and still having issues I tried installing the 32bit runtime and BAM spice weasel....I mean the install continued without a hitch so I just thought it was a 32bit version of OBS.

 

[Se1pher]

Avermedia LGP still does't work with 64 version, wnen it'll be fixed?

 

[Osiris]

When Avermedia makes a 64-bit driver.

 

[Xorath]

Avermedia LGP still does't work with 64 version, wnen it'll be fixed?

Thanks for letting me...know I'll have to test it out on the 32-bit version of Studio.

Just a heads up with Avermedia LGP, it does work and there are 64-bit version Drivers with their install package, but from 'my experience' there are issues with LGP on the latest OBS Studio, at least on the 64-bit version...like the feed if it ever freezes, it will stop working for the rest of the Windows session and causes OBS to freeze & unable to close from the 'processes' in task manager...also messing with any properties while using the LGP, while it does save the settings for the session, it freezes the feed and the aforementioned issue happens again...and again...and again.

I'll test out the 32-bit version and see if it works without the aforementioned issues and update my post.

 

[Xorath]

I can confirm now that LGP runs exceedingly better on OBS Studio 32-bit! You can even tweak the settings without the whole program & LGP breaking on you!

Thanks for the heads up! OBS 64-bit currently breaks LGP support...it's very unstable.

Just want to reassure that LGP does have 64-bit drivers, the LGP setup doesn't even let you install the 32-bit standalone drivers from its driver folder if you're running a 64-bit system...just so you guys know.

I'll be sticking to the 32-bit version of OBS Studio, until LGP becomes more stable on the 64-bit version. :)

EDIT: Update #2: However 32-bit suffers from the same issue that if you ever close the program and re-open it, LGP breaks on you with a black screen which cause OBS to freeze when attempting to close & get stuck in your 'processes' for the rest of the Windows session.

One thing I can probably test out...is unplugging and plugging back the LGP before I proceed to open a new session of OBS to prevent the freeze from happening in the first place and to avoid the black screen on the 2nd boot of the program.

EDIT 2: Update #3: I can confirm that unplugging your LGP before quitting your session does not break your LGP for the next boot without restarting your computer, it's a way to circumvent the issue...if you get a black feed, just simply deactivate your feed from the source's properties & reactive it...you should be able to get it back right away.

LGP compatibility seems to be working in a pretty stable form on the 32-bit version of OBS Studio, aside from the above issues & the circumventing you have to do to avoid OBS freezing on you for the duration of the Windows session. :)

 

[Xorath]

I can also say that random freezes only happen when you have Browser Source Plugin enabled...and cause all of the aforementioned above to happen, which is to freeze the feed and freeze OBS for the duration of your Windows session when attempting to close by leaving a impossible to close 'process' under task manager.

I believe @Jim already mentioned in an earlier thread that he will be debugging the Browser Source Plugin as it wasn't made by the OBS Dev but by an outsider/user...according to Jim from what he saw in the logs...the Browser Source Plugin seems to be responsible for the random LGP freezes that remain for the duration of the 'Windows' session...which causes the program to freeze.

Tried leaving OBS on over night for more than 8 hours w/o the Browser Plugin enabled/on and the feed never froze...so yes, the Browser Source Plugin is causing some of the random freeze issues.

Hope the Browser Source Plugin gets an official release with the next OBS Studio build release...bug free! :D

Don't want to rely on more windows being opened for TwitchAlerts & Window Capturing...kind of a hassle & a waste of CPU+RAM resources. :P

 

[Osiris]

It doesn't freeze for the duration of the windows session, I can close the process fine if it happens.
Also I didn't have it freeze on me when doing nothing, only when making some change to the browser source settings.

 

[Xorath]

It doesn't freeze for the duration of the windows session, I can close the process fine if it happens.
Also I didn't have it freeze on me when doing nothing, only when making some change to the browser source settings.

When LGP freezes, OBS freezes when attempting to close...when you try to force close it, the OBS window does close but remains open in processes under 'Task Manager' and when you attempt to end the process...it just remains and refuses to end until you restart your Windows.

Browser Source Plugin has an issue that it causes LGP to freeze after a short period of time, it happened several times so it's not like I'm coming to this conclusion out of one instance...without it I went for 8 hours strong without a freeze while I was away and it kept being fine.

@Jim said that the Browser Plugin seemed to be conflicting with LGP in an earlier thread and that he'll try debugging it to see if this can be fixed, since the Browser Source Plugin was not made by the OBS devs.

Not to mention LGP is very unstable on the 64-bit bin version of OBS...can't even dare to touch any of the 'properties' of the LGP source without getting a permanent freeze on the session with or without Browser Plugin...which causes OBS to freeze when attempting to close...and well...you know the rest.

 

[Osiris]

Jim didn't mean it was a conflict between LGP and browser plugin, the browser source can freeze regardless of other sources.

 

[Xorath]

Jim didn't mean it was a conflict between LGP and browser plugin, the browser source can freeze regardless of other sources.

Sorry, I just found the actual thread... https://obsproject.com/forum/threads/obs-studio-0-13-1-crash-on-exit.42853/#post-192716

Yes, he didn't say it was LGP but that it causes the random crashes that seemed to coincide with my OBS behavior, where it remains under processes...which only happens when my LGP feed freezes.

I forgot to mention that LGP has an issue that if you attempt to open another session of OBS after successfully closing a previous session while having the LGP still plugged from the last session...the LGP feed will start black screen regardless of what method you use or circumvention that I had stated before, so it is recommended from personal experience to only plug the LGP when OBS is already open, and refresh the feed under 'Properties' by deactivating & reactivating the feed.

This doesn't work under 64-bit, because the feed remains black screen when you touch any settings under LGP's properties.

But Browser Source Plugin seems to be a major culprit in the LGP feed randomly freezing during an active session which causes the odd behavior...doesn't happen when the plugin isn't installed.

I'll just upload some log files for my OBS as well as some Crash log files.

Actually, never mind, Crash logs are extremely outdated and whenever I suffered these crashes I guess it didn't log anything under crash reports.

 

[georgemacin]

Technically x86 simply refers to a family of processors and the instruction set they all use. It doesn't actually say anything specific about data sizes. The term x86 started out as a 16-bit instruction set for 16-bit processors (the 8086 and 8088 processors), then was extended to a 32-bit instruction set for 32-bit processors (80386 and 80486), and now has been extended to a 64-bit instruction set for 64-bit processors. It used to be written as 80x86 to reflect the changing value in the middle of the chip model numbers, but somewhere along the line the 80 in the front was dropped, leaving just x86.

Macin

 

[Marco Leon]

Hi ! I went to x86 > obs studio > bin > 64-bit > and I tryed to run obs64.exe (because my Windows is 64bits), but it doesnt works... there is a message saying "ERROR: could not find any D3DCompiler libraries" When I run obs32.exe the software works but when I try to use sharing screen my comps resets. How may I use obs64 ???