Search results

by the way there are still endless flow of errors in the logs when sharing screen (from chrome latest version at least):

hello i have a small issue when re publishing to wowza: if i use this url: rtmp://mywowzaserver.com:1935/wcs/1/streamName, the rest call return a striped url name if i use this instead (no instance name): rtmp://mywowzaserver.com:1935/wcs/streamName its working as expected. but i absolutely...

ok thanks, i will wait 5.1 then. by the way, if i can make a feature request: i talked about this point few months ago i think, to have the equivalent of sharedObjects so we can maintain values on the server that can be shared accross participants in a same room. currently im doing this using a...

ha, but if i use stripcodec i have the following error:

okay, swithching to vp8 server side solved the pb. many thanks !

Hello is it possible to stop recording using the rest api ? the thing is if we want to transfert the recording from wcs server to another server (for conversion or whatsoever) while the stream is publishing, the file wont close properly and will be corrupted...and its not very convenient to stop...

thanks for reply, that was an error in the js. if it can help others, here is the working js for facebook live (where "_myStreamID" is the stream name):

Hello since a recent update (sorry i cant tell you which), the screensharing (which was working perfectly with the recent extension update) is now of very bad quality. My first though was it was related to my bandwidth, but if using FF the quality is perfect like before. did somebody noticed the...

thank you, i figured this out meanwhile. still no luck: its working when using rest advanced client in chrome (though have following error in logs: and i get a error 500 when using this js:

hello there might be something wrong in my js function calling the rest api as from chrome rest extension its working fine can you tell me if you see something wrong in this: thank you

hello for a conferencing app, i'm currently retrieving current publisher usiing rest /find_all problem i see with this is that if there are a lot of connected users (lets say hundreds, playing and publishing), the return value will be very very big. is there a lighter way to get only published...

hello yes ssl is installed and perfectly working. and no i cant make http rest request as i'm making the request from a https url

got it working, was a typo in my js apparently (had to change simple quotes bu double quotes...strange) so now the rest call is working, but still no publishng: new error message from rest: ERR_SSL_PROTOCOL_ERROR

Hello im trying to push to facebook and get the following error as result of the rest query: here is the jquery code im using (where streamID is the streamName): using latest wcs5 build, ubuntu 14.04 any clue ? beside this, new error coming from time to time:

Hello im trying to push to facebook and get the following error as result of the rest query: here is the jquery code im using (where streamID is the streamName): using latest wcs5 build, ubuntu 14.04 any clue ? beside this, new error coming from time to time:

hello i've updated to latest version and there are still errors with the conference model: when pulishing, if publishing rtmp to wowza: also, if a stream is being published from webcam/micro, if disconnect while publishing:

thanks, its working. since last update (today), new errors showing up in the logs when sharing desktop from chrome or FF (latest builds), windows 7 (but the sharing is working as expected): also, rtmp republishing still not working. will give a try from another windows version

hello just updated to latest wcs version, and rtmp republishing to wowza stopped working publishing from windows 7, chrome 65 to wowza 4 on ubuntu server wcs error log:

Hello, i'm experiencing a lot of unstability when playing live streams on ios (ipad 2, ios 11.4) video tends to turn grey after few minutes of playing, then browser crashes. anyone else experiencing the same problems ? using the conference example. android doesnt have this problem and is very...

the new ff extension is working fine, thanks. however it seems that only "window" can be shared, and not "screen". probably an api limitation...thank you