Andrew D.Laptev

@cubecleveland Hi! Maybe :smile: But right now I have no time to do this. But I wrote a small example how you can do it by yourself. https://github.com/agsh/onvif/issues/250#issuecomment-1273208097 And don't...

@RicardoEmm, hi! As I can see, the problem can be in the code and `this` scope. Just try this: ```js const cam = new Cam({...yourConnectionOptions}, (err) => { cam.absoluteMove({ zoom:...

Hello! Can you send me full demo example? And what did you mean when you said about 'on' event of the stream object?

Do you mean that when you change sources to your ip-cams nothing works?

Oh, now I understand. Are you sure that this is wright rstp stream? Try to check it with vlc and ffmpeg with corresponding params

Are you're sure that rtsp://192.168.1.48:554/profile1 is pure rtsp stream that can be processed with ffmpeg?

And what is the result of `ffmpeg -i rtsp://192.168.1.48 -f image2 -updatefirst 1`?

Seems that it is failure with your rtsp stream. Just try to fix them with different ffmpeg arguments that you can later pass to the consturtuctor of rtsr.FFMpeg as an...

Oh, this is simple, just look at https://github.com/agsh/rtsp-ffmpeg/blob/master/lib/rtsp-ffmpeg.js#L74 add all missing arguments in array in style of `spawn` node.js method https://nodejs.org/api/child_process.html#child_process_child_process_spawn_command_args_options

Ok, I'll fix it in the next few days