X/Twitter compatibility? YT bug?

[0xDeadEye]

Thank you for all your hard work! Love the plug in but have some bugs.

I have a stream URL and stream Key to be able to go live on X/Twitter. I can go live via OBS, via streamlabs but for some reason can not use the plug in. (I want to go live via twitch so that I can utilize the twitch vod track, and than use your plug in to go live to X/Twitter and YT so I can set them to the came vod track channel.

YT will work sometimes and others times it will not. Not sure why this is happening. When I see that it will not go live, the vod ends up showing up later. So it seems to not trigger the LIVE feature.

Thanks again! Hope this helps

[0xDeadEye]

@sorayuki any help would be greatly appreciated. Reached out to the X/Twitter team and got no response

[CosmacGrandpa]

I too am experiencing the X/Twitter issue. Using the plugin OBS will not connect to X, logging the following continuously:

20:48:13.844: [rtmp stream: 'multi-output'] Connecting to RTMP URL rtmp://va.pscp.tv:80/x...
20:48:13.845: [rtmp stream: 'multi-output'] Interface: Killer E2600 Gigabit Ethernet Controller (ethernet, 1000 mbps)
20:48:14.086: [rtmp stream: 'multi-output'] Connection to rtmp://va.pscp.tv:80/x successful
20:48:17.834: WriteN, RTMP send error 10053 (16 bytes)
20:48:17.834: WriteN, RTMP send error 10053 (47 bytes)
20:48:17.834: WriteN, RTMP send error 10038 (42 bytes)
20:48:17.834: [rtmp stream: 'multi-output'] Disconnected from rtmp://va.pscp.tv:80/x
20:48:17.834: Output 'multi-output': stopping
20:48:17.834: Output 'multi-output': Total frames output: 48
20:48:17.834: Output 'multi-output': Total drawn frames: 120
20:48:17.835: Output 'multi-output': Reconnecting in 2 seconds..

Making Twitter/X the main OBS destination and using the plugin to stream to other the other service instead works fine. It's only when trying to use the plugin with X that gives any problems. The symptoms were the same regardless of whether the plugin was slaved to the OBS encoder settings or set to encode separately.

[sorayuki]

disconnected after 3 seconds. Check bitrate and video resolution exceed the platform (X) limit

…

________________________________ From: CosmacGrandpa ***@***.***> Sent: Wednesday, April 10, 2024 9:00:26 AM To: sorayuki/obs-multi-rtmp ***@***.***> Cc: 雷Q ***@***.***>; Mention ***@***.***> Subject: Re: [sorayuki/obs-multi-rtmp] X/Twitter compatibility? YT bug? (Issue #410) I too am experiencing the X/Twitter issue. Using the plugin OBS will not connect to X, logging the following continuously: 20:48:13.844: [rtmp stream: 'multi-output'] Connecting to RTMP URL rtmp://va.pscp.tv:80/x... 20:48:13.845: [rtmp stream: 'multi-output'] Interface: Killer E2600 Gigabit Ethernet Controller (ethernet, 1000 mbps) 20:48:14.086: [rtmp stream: 'multi-output'] Connection to rtmp://va.pscp.tv:80/x successful 20:48:17.834: WriteN, RTMP send error 10053 (16 bytes) 20:48:17.834: WriteN, RTMP send error 10053 (47 bytes) 20:48:17.834: WriteN, RTMP send error 10038 (42 bytes) 20:48:17.834: [rtmp stream: 'multi-output'] Disconnected from rtmp://va.pscp.tv:80/x 20:48:17.834: Output 'multi-output': stopping 20:48:17.834: Output 'multi-output': Total frames output: 48 20:48:17.834: Output 'multi-output': Total drawn frames: 120 20:48:17.835: Output 'multi-output': Reconnecting in 2 seconds.. Making Twitter/X the main OBS destination and using the plugin to stream to other the other service instead works fine. It's only when trying to use the plugin with X that gives any problems. The symptoms were the same regardless of whether the plugin was slaved to the OBS encoder settings or set to encode separately. ― Reply to this email directly, view it on GitHub<#410 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEAUME4W4RLRVT4DGSL76RDY4SFKVAVCNFSM6AAAAABEN3AGYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBWGI3TAOJSGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[CosmacGrandpa]

Thank you for responding, and for your fine work on this plugin! The workaround of swapping destinations is working for me, so this feedback is purely for future improvement purposes. I tested the plugin using “get from OBS” for the encoder settings, using the same OBS encoder settings that broadcast directly to X without error, so the settings should be correct. But just to be certain I tested the plugin using separate encoder settings dialed way below X’s max (30FPS 1280x720 2500bps) and still received the same 3 second disconnect issue. I am streaming to 5 destinations in total and X is the only one that the plugin has any issues with. Making X OBS’s primary destination and using the plugin to stream to the other 4 works fine.