Refer to the system requirements or the ReadMe file file included in the product.
If the encoding computer does not meet the minimum system requirements, the resulting audio/video stream might be compromised. Always make sure that CPU usage does not exceed 75% while encoding, or the quality of the encoded file could be affected.
Check the graphics card on the encoding computer; it should be overlay enabled or should support Video Mixing Renderer (VMR).
Check the graphics card on the encoding computer; it should be overlay enabled or should support VMR.
This may happen for IEEE 1394 devices because they populate the value field based on the video standard. The value is 29.97fps for NTSC and 25fps for PAL.
This option is disabled when either the device is not capable of providing the timecode or the device timecode DLL is missing from the Timecode folder in the application installation directory. However, you may use the System Timecode option to embed the system time as a timecode in the video stream or file.
Deinterlace works only for video sizes that have a height greater than or equal to 480 pixels and a width greater than or equal to 576 pixels.
All DirectShow supported devices that give data in raw format can be used with Flash Media Live Encoder. See the list of capture devices certified for Flash Media Live Encoder.
Verify that the device is listed in the Device Manager and the device drivers are properly installed. Also, make sure that the device supports DirectShow.
First, make sure no other application is using the device. Then, try the following:
In general, Flash Media Live Encoder does not tamper with the audio or video timestamps. But when the device gives video frames with a backward timestamp, those frames are dropped. With audio, if the samples have a backward timestamp, then the timestamp value is adjusted.
Flash Media Live Encoder supports only raw data from video and audio devices. The supported raw video formats include I420, YV12, YUY2, UYVY, RGB24, and RGB32.
The device may not support the combination of frame rate and video size that you selected. Change either the frame rate or the video size.
This error occurs when the audio device filter does not expose the interface required to set the audio intensity. The volume level will be the default level sent by the device.
This error occurs when the device starts behaving unexpectedly (sending packets with wrong or backward timestamps) after a long encoding session. The application will restart itself after encountering this error. This error will not affect the video quality.
There could be two reasons for this error:
Flash Media Live Encoder uses RTMP and RTMPT to connect to the server.
Verify that the encoding computer is connected to the network. Also, verify that the connection URL to Adobe Media Server is correct and that the Adobe Media Server application to which you're connecting exists. Make sure that the port on the server is enabled and the firewall is not blocking the connection. Also make sure that the Allow tag in vhost.xml in Adobe Media Server contains the correct parameters. Refer to the vhost.xml for the correct parameters.
Yes. Flash Media Live Encoder tries to reconnect every five seconds (by default) until a connection is established. However, you can change that default setting and determine how often and for how long Flash Media Live Encoder tries to reconnect by editing the profile file. Refer to Flash Media Live Encoder Help for more details.
Verify that the stream name is not already used by that application. Also, make sure the stream name follows stream-naming conventions for Adobe Media Server.
Flash Media Live Encoder version information is passed as a user agent ID to the server.
Hostname resolution occurs at every reconnection attempt. Flash Media Live Encoder does not cache the IP address of the server.
Download the Authentication add-in and install it on Adobe Media Server.
Credentials are saved only for each connect-disconnect session and not for a complete encoding session.
No. Default authentication is implemented at the server level, not at the application level. If desired, you can implement a custom server-side access module for application-level authentication.
The selected bitrate represents the average value at which the application should encode; the actual bit rate depends primarily on the content. Complex video sequences require more bits compared to still video. Also, if there is a drop in frame rate, either due to the device or high CPU usage, the actual bitrate will differ.
The selected frame rate represents the average value at which the application should encode; the actual frame rate depends on the frame rate the application is getting from the device. Some devices do not give the video at the desired frame rate. It may be lower or higher. Also, in the Encoding Statistics panel on the Encoding Log tab, check for frame drops. If there are frame drops, make sure CPU usage of the system is not more than 75%.
Make sure the CPU usage of the encoding computer does not exceed 75%. If it does, try increasing the video bitrate or decreasing the video size or frame rate.
Verify the buffer value from the Flash Media Live Encoder publishing statistics. If this value is high, then network conditions are unfavorable, and Flash Media Live Encoder is unable to stream the data to the server. If the buffer value keeps increasing, then Flash Media Live Encoder may crash. Use Auto Adjust to overcome this issue.
By default, you can stream up to 20Mbps of data to the server.
The deinterlace filter is based on a simple vertical blur algorithm and is not very effective at higher video sizes. Adobe suggests that you deinterlace at the hardware level for better quality and performance.
Select a bitrate according to the video content. For large and dynamic video input, you need a higher bitrate. An extremely low bitrate might result in low-quality video and pixilation. For small and relatively still video input, you can use a lower bitrate.
The Base profile uses less CPU power than the Main profile but compromises video quality. If you want high-quality video and you have a good hardware configuration system, use the Main profile; otherwise the encoder might reduce the output fps during the encoding process.
H.264 levels define the limit on the combination of video size, frame rate, and bitrate that the encoder can encode. Changing the H.264 level does not have any impact on video quality and CPU usage. For details, see the Flash Media Live Encoder Help and Wikipedia article on H.264.
Adobe recommends you use the highest available sample rate to get the best quality. The bit rates listed below are only suggestions; actual bit rates vary from case to case.
For music, movies, and mixed content, try the following bit rates:
|Less than 48kbps||HE-AAC||Parametric stereo|
|Above 224kbps||MP3 or AAC||Stereo (for MP3) or LC stereo (for AAC)|
For speech, dialogue, and meeting content, use the same ranges listed above, but use Mono for the channel setting.
Pixelation occurs when the video bitrate is not sufficient to encode the video. Increasing the video bitrate will usually resolve the issue. Also, if you are using the H.264 base profile, try switching to the Main profile.
Auto Adjust is used to adjust video settings dynamically in case of adverse network conditions between Flash Media Live Encoder and Adobe Media Server. With Auto Adjust, you can select either the Drop Frames or the Degrade Quality option. Drop Frames will drop video frames at the RTMP end, and Degrade Quality will reduce the bitrate of the encoded stream. The Degrade Quality option affects both the primary and backup stream as well as the file that is being saved. The Drop Frames option adjusts each stream individually. The saved file will not be affected.
This problem occurs because of adverse network conditions. Try reducing the bitrate to work better with the network bandwidth, or try the Auto Adjust feature.
Jittery video occurs if the subscriber buffer empties. Change the buffer size of the subscriber to a non-zero value.
The size of the buffer depends on two factors:
These two factors are conflicting: Ideally the stream should both start quickly and be stable. One way to deal with this situation is to have two different buffer settings, one for when the stream starts and one for when the playback is in progress. This strategy significantly reduces the conflict. It allows a small buffer to be set for fast start, and a longer one to be used to ensure stream stability when playback begins. Because network issues can still affect the initial buffer size, the initial buffer size cannot be arbitrarily small. Adobe recommends always setting the buffer to a non-zero value.
Live applications that use the Live Aggregate Messages feature on Adobe Media Server to improve performance need to use a buffer that is at least as long as the delay introduced by the live aggregation. The delay is 500ms (0.5s) by default but can be configured on a per-application basis. If the buffer isn't long enough, the stream will not play back smoothly.
For dynamic bitrate switching, Adobe recommends using a buffer length value that is equal to the keyframe frequency of the encoded video.
Per the MP4 standard, Flash Media Live Encoder creates fragmented F4V files that are optimized for streaming from Flash Media Server. F4V or MP4 playback applications that do not fully conform to the MP4 specification may fail to play.
If the Flash Media Live Encoder process is terminated during encoding, the saved file will be closed improperly and will not be playable.