wtsnz
New Member
Hey La_Verte,Worked once, tried your trouble shooting it does not work anymore on :
iphone 6s
iphone 8
I understand that Dev need money and resources that's why i purchased this app but are you still supporting it ?
I'm continuing to work on the app yes :) I've noticed that since v2.5.0 was release there is an issue that is causing a crash for a small number of users, and I'm looking into it. The crash reports haven't been great so I've been having a fun time over the last few days trying to replicate & fix the issue. I hope to have a fix out by the end of the weekend.
Hi Will (or anyone else who can help!),
Any suggestions...
I have a Win10 HP Elitebook with i5 processor & 8Gb RAM. At no point do I go over about 30% CPU utilisation. I want to LIVE stream to facebook and youtube (but not at the same time!).
I've been using OBS with OBScamera for about a month now. I've had excellent success with iPhone 6&7 (720 resolution with 10Mb/s, but if I use 1080 I have to drop to 4Mb/s).
I've had limited success with iphone 5 (until I updated to 2.4.0 I could get it to work at 720 and 1Mb/s, but now with 2.4.0 I'm struggling to get anything). I either get nothing, a static image or occasionally a live feed when setting up the source, but once I save the settings it stops updating.
I've had no success with iphone 4S - just lines on the top half of the display and a really distorted image in the bottom half.
I've tried a fresh install, loads of different resolutions / frame rate / bitrate combinations but am struggling.
I really don't want to rely on the iphone 7 (as its my phone and I want to leave 2 phones permanently setup in the venue).
I get these errors in the OBS log when it starts (but I don't *think* any of them relate to the iOS camera:
That goes on for nearly 2Mb...
I love the concept, and have had great successes - would just love to understand what I need to do for a little more robustness...
PLEASEEEEEEE help!
Thank you guys!
Trev
I made some changes in v2.5.0 that should fix this issue - set the keyframe interval to "Every Frame", and turn the resolution down until the error messages stop happening (this depends on the device), and turn the bitrate to the highest (higher bitrate, less CPU strain, but higher bandwidth). It seems that older devices have a hard time encoding video that was considered very high quality 6 years ago (720p/1080p).
Thanks for the feedback about making this more clear - I'll see what I can do to add some more information regarding best setups on a device by device basis :)