Skip to main content
Participating Frequently
November 6, 2012
Question

NetStream receiveVideoFPS

  • November 6, 2012
  • 1 reply
  • 705 views

I'm trying to set receiveVideoFPS for a NetStream connection on a live stream and I can not get it to update correctly.

The only time the FPS actually updates is if the publishing stream is changed to publish with a keyframe interval of 1. Meaning that every frame is a keyframe. This would obviously not be ideal as it would require a rediculous amount of bandwidth.

According to the documentation, the receiveVideoFPS can be called before or after play() is called, however neither update correctly.

With keyframes seeming to be the culprit, I've attempted to set the keyframeInterval and FPS rate at a combo that should evenly divide to make it easier on the server. For example:

myCam.setMode(512, 384, 12, false);

myCam.setQuality(0, 90);

myCam.setKeyFrameInterval(6);

Should mean that either a target of 2 FPS or 1 FPS would be possible right ??

Because every 6th frame is a key frame, meaning 2 per second

but both fail...

ANY help would be greatly appreciated - I can't seem to find any responses online to people who have same problem.

Thanks so much!

.daniel

This topic has been closed for replies.

1 reply

Participant
November 7, 2012

I'm trying to accomplish the same thing? Anyone out there have any luck/info to provide?

Participating Frequently
November 27, 2012

Okay so I accidently noticed that this function IS actually TRYING to work.

I had the video application up on two separate computers and was viewing the streams for some testing. A colleague of mine just happened to stroll by in front of the camera and I noticed that his walking across the room was VEEERY choppy ... almost 1 FPS.

I dug in a little deeper and though i was publishing at 6 FPS, I had left the code in to receive at 1 FPS. The result was that though it was not receiving at 1 FPS, it was definitely lower: 2-3 FPS. So it was indeed TRYING to drop it to 1 FPS, but just not doing a very good job.

I suppose for my use, where I want tablets and mobile devices to receive at a lower rate, this will at least help, it just won't be perfect.

I'd still love to hear from Adobe on the subject. What are the best practices?? How reliable is it?....