RTMP to websocket on IOS video lost but got sound

[kelvin]

hi, I am facing problem from RTMP to websocket on IOS the video is lost but is still can get the video sound.
and have message : Not enough bandwidth

may know why will lost the video but can get sound?

thanks.

 

[Max]

NOT_ENOUGH_BANDWIDTH event is raised to inform subscriber that there is loss on the download channel. By default, the event is fired when loss reaches 5% in 1 second.
"Packet loss on session" INFO messages in the client log (in WCS_HOME/logs/client_logs) can be monitored to see the loss rate. Video can freeze if the rate is high.

 

[kelvin]

I check the lot , it look all is same message and I get message from the log file. it not show the video rate ?
how I can enable push_log at client side ?


2017.09.06.14.09.49 Report login: vucuoe2ajb56vvij7jde7l8488 authName: null port: -1 OS: null browser: null
Folder with logs: client_logs/2017-09-06/vucuoe2ajb56vvij7jde7l8488-14-09-49
Report Text: Report by disconnect

[-- BEGIN CLIENT LOG --]
CONF: ClientConfig{rtspMedia=false, wsTunnel=false, login='vucuoe2ajb56vvij7jde7l8488', authenticationName='null', password='null', domain='null', outboundProxy='null', localPort=-1, port=0, visibleName='null', regRequired=false, applicationName='null', swfUrl='null', useProxy=true, qValue='null', pAssociatedUri='null', contactParams='null', authDate=Wed Sep 06 14:09:49 MYT 2017, authToken='kelvin-HLS', logsFolderName='null', clientVersion='null', clientOSVersion='null', clientBrowserVersion='null', wsTunnelPacketization2='false', custom='{}'}
IMPL: com.flashphoner.server.B.A@7c9cdb15
LOGS:
Client didn't pushed logs to server, try to enable push_log at client side.
[-- END CLIENT LOG ----]

 

[kelvin]

another question :
if I using Wowza streaming out RTMP , the video lost but can get the sound
if I using wirecast to stream out RTMP , i can get the video and sound

is that wowza no support or any setting should need setting?

thanks.

 

[Max]

how I can enable push_log at client side ?

You have to add logger parameter:

logger:{push:true, severity: "DEBUG"}

Example:

Flashphoner.init({logger:{push:true, severity: "DEBUG"},...});

https://github.com/flashphoner/flas.../examples/demo/streaming/player/player.js#L16

is that wowza no support or any setting should need setting?

WCS supports H.264 + AAC/Speex/G.711 streams over RTMP.
Make sure your stream fits this format.
If you provide a step-by-step guide how to re-publish stream using Wowza, we will check this on our Wowza installation.

As an option, you can try to pull stream from Wowza over RTSP.
For example,
If you publish stream to Wowza as rtmp://wowza-host/live/stream1
You can play stream rtsp://wowza-host/live/stream1 in WCS server.

 

[kelvin]

for my wowza setting;
Debug Log false
Debug Log Children false
SecureToken Shared Secret
Adaptive Streaming false
Send FCPublish true
Send Release Stream true
Send Stream Close Commands true
Remove Default Application Instance true
Send Original Timecodes true
Original Timecode Threshold 0x100000
Connection Flash Version
Query String
Local Bind Address
Debug Packets false

using Stream Targets

 

[Max]

We have fresh Wowza installation.
Please describe step-by-step, with screenshots what we would need to do to configure and reproduce your test.

 

[kelvin]

can get the listing for the resolution ?
maximum is can get ?

 

[kelvin]

just basic for the setting

Playback Types
Adobe RTMP and RTSP/RTP

Options
Low-latency stream (ideal for chat applications)
Cross-origin resource sharing (CORS) (for HTTP-based streams)

others is default

 

[Max]

if I using Wowza streaming out RTMP , the video lost but can get the sound

We just need an instruction how to make the same test. Please describe step-by-step with screenshots.

just basic for the setting

Well. It has basic settings. Please tell us how to test this to reproduce reported issue. We need screenshots or video capture to repeat this.

 

[Max]

can get the listing for the resolution ?
maximum is can get ?

We tested 1920x1080 maximum resolution.

If you play in iOS Safari over WSPlayer, then too high resolution is incorrect because iOS Safari WSPlayer has limitation 640x480 and your Full HD stream will be transcoded to 640x480 to be played on iOS Safari.

If you play in WebRTC browser, like Chrome, resolution will be passed without changes. If you stream Full HD, it will play Full HD.

 

[kelvin]

thanks for the information