Question / Help OBS-FTL - "starting the output failed"

[zaro]

So I recently downloaded and built the OBS-FTL developed for streaming at BEAM on my macbook pro.
I adjusted the settings, created the scene and everything, but when pushing the 'start streaming' (and streaming ONLY) it gives me a STARTING THE OUTPUT FAILED - "note; if you are using the NVENC or AMD encoders, make sure your video drivers are up to date."

when hitting 'start Recording', it works just fine... Any ideas on how to fix this?!

LOG attached;

 

[keybounce]

I want to know also; I thought the FTL was (currently) windows only.

 

[zaro]

I want to know also; I thought the FTL was (currently) windows only.

following these instructions - https://www.reddit.com/r/beam/comments/5zwk30/mac_osx_build_of_obsftl_18/ I've managed to make it work for recording only... really anxious on getting that FTL-almost-no-delay going on my mac here...
someone, helpz?

 

[Narcogen]

Have you tried the official build? It is only of an older version, but the FTL it includes is still supported by Beam, and it may work without problems that might be caused by either your own computer's compilation environment or changes I made on my system to make my build work.

https://github.com/WatchBeam/obs-st...nload/ftl.30/OBS_Studio-FTL.17.0.2.ftl.30.dmg

FTL .30 is still being supported by beam, so this version should work.

Make sure that under Settings / Streaming / Stream Type you select "Beam FTL Service".

 

[zaro]

Have you tried the official build? It is only of an older version, but the FTL it includes is still supported by Beam, and it may work without problems that might be caused by either your own computer's compilation environment or changes I made on my system to make my build work.

https://github.com/WatchBeam/obs-st...nload/ftl.30/OBS_Studio-FTL.17.0.2.ftl.30.dmg

FTL .30 is still being supported by beam, so this version should work.

Make sure that under Settings / Streaming / Stream Type you select "Beam FTL Service".

NARCOGEN! you're everywhere!!! O_O thank you so much for ya help, bruv.

This 'old' dmg worked perfect!

now, if I may change the subject a bit; my stream was lagging and delaying like crazy on beam (with the old twitch settings);
any tips on settings for a macbookpro (2.3ghz i7 - 16gb 1600mhz ddr3, NVidia geforce GT 650 512mb + Intel HD graphics 4000 1536mb and a 500gb samsung SSD) run?

 

[keybounce]

WOOT! YES!

 

[Narcogen]

Beam needs its own settings.

https://watchbeam.zendesk.com/hc/en-us/articles/115000638643-Streaming-With-OBS-FTL

Hard to tell what might be causing your problem without your settings and what game you're trying to stream and how you're capturing.

In short, do not use anything but the x264 encoder, and do not use window capture. All are nonperformant on OSX.

 

[keybounce]

aaugh.

Apr 21 15:50:50 keybounceMBP ReportCrash[19980]: Attempting to read data: Called memoryAtAddress: 0x10a456270, which is in an unmappable portion of [0x0 -> 0xffffffffffffffff] in PID# 19917.
Apr 21 15:50:51 keybounceMBP com.apple.launchd.peruser.502[223] ([0x0-0x128128].com.obsproject.obs-studio[19917]): Job appears to have crashed: Trace/BPT trap: 5
Apr 21 15:50:51 keybounceMBP ReportCrash[19980]: Saved crash report for obs[19917] version ??? to /Users/michael/Library/Logs/DiagnosticReports/obs_2017-04-21-155051_keybounceMBP.crash

Doesn't work for me :-)

... what the actual ???



Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage
Referenced from: /Volumes/VOLUME/OBS-FTL.app/Contents/Resources/bin//libavfilter.6.dylib
Reason: image not found

Core image framework not found?!?

 

[Narcogen]

You using the older official app, or the one I compiled?

I know for some people, mine did not work for people who had certain libraries installed in different places.

 

[keybounce]

Pretty sure that run was using the older official binary you provided.