A1：Check if the switch or router supports DHCP

The encoder relies on the switch or router supporting DHCP to obtain an IP address. If DHCP is not supported, the encoder cannot get an address. If a DHCP environment is unavailable, it is recommended to manually configure a static IP address.

A2：Check the network cable, switch port, or device network port.

Try replacing the network cable or the switch port. If the device’s network port is damaged, it cannot obtain an address correctly. If the problem persists, contact [email protected] assistance.

A1：Network connectivity issues.

Use the pingcommand in the computer’s command prompt to check if the encoder’s IP address is reachable. If it cannot be pinged, the network connection has failed.

A2：IP address conflict.

Check if there are two devices with the same IP address on the local network, as this can also cause login issues.

A3：Device nginx service issue.

It is recommended to contact [email protected] assistance and remote troubleshooting.

A4：Browser cache issue.

Browser cache can also cause this problem. Try clearing the browser cache or using a different browser to log in.

A5：Incorrect subnet mask.

If the device’s IP address has a subnet mask of 255.255.255.255, it will cause connectivity problems. Ensure the IP address is configured correctly according to the local network settings.

A1：Restore to factory settings.

Use the encoder’s reset button to restore the device to factory defaults. The default username and password are both admin.

A2：Contact technical support to recover the password.

If the encoder has important configurations and restoring factory settings is not convenient, contact [email protected] assistance in recovering the password.

A1：Check for non-standard resolution.

Some encoders do not support non-standard resolutions. Please contact [email protected] assistance.

A2：Check cables or interfaces.

Some cables may not support 4K, leading to recognition failure or abnormalities when used for 4K signals. Damaged or faulty cables can also affect interface recognition.

A3：Cable length is too long.

If HDMI or SDI cables are too long, there may be no signal or an unstable signal. Standard transmission distances: HDMI: 15-20 meters; SDI: 100-150 meters.

A4：SDI 1080P50/P60 Level A/Level B.

For SDI 1080P50/P60, some cameras have Level A/Level B differences. Currently, some encoders do not support Level B. If the source camera outputs SDI Level B, please change its setting to Level A before connecting to the encoder.

A1：Audio input source selection.

The encoder defaults to HDMI audio or SDI audio. If using an embedded 3.5mm audio input, you must change the audio source in the encoder’s web interface to Line In.

A2：Multi-channel audio issues.

For multi-channel audio sources, check if some channels lack audio or if the desired audio is outside the range captured by the encoder. Adjust the source audio settings to match.

A3：Difference between Line In and Mic In.

If using an embedded 3.5mm audio input, some encoders do not support Mic In. It is recommended to use Line In.

A1：Network issues.

If the local area network is unstable, stream playback may stutter. It is recommended to use the pingcommand for a simple packet loss test.

A2：High device load.

If multiple devices are pulling the stream from the encoder simultaneously, it can cause high device load, leading to stuttering. Try reducing the number of devices pulling the stream.

A3：Encoder parameter setting abnormality.

The GOP size should generally be set equal to the video source frame rate, and the maximum should not exceed twice the frame rate. Excessively large GOP values can easily cause stuttering

A1：Check if the video source is interlaced.

If the input is interlaced, it is recommended to use an encoder that supports native interlaced processing (e.g., N50, N60 modes, “i in i out”). Contact [email protected] assistance.

A2：Software compatibility issues.

Some software has poor compatibility with interlaced streams. It is recommended to use a professional decoder for playback.

A3：Monitor compatibility issues.

Some monitors do not handle interlaced signals well. Try using a monitor with better interlaced signal compatibility.

A1：Incorrect push URL.

If there are spaces in the URL, the push will fail. If a stream key is required, the format is typically rtmp://address/app/stream_key.

A2：Encoder DNS configuration error.

RTMP addresses usually contain domain names. For a successful push, the domain name must be resolved first, which relies on DNS. Check the DNS configuration in the encoder’s network settings.

A3：RTMP vs RTMPS.

If the push URL uses RTMPS (secure RTMP), please contact [email protected] assistance. Confirm if the specific encoder model supports RTMPS, otherwise the push will fail.

A1：Gateway not set.

The encoder must be set on the same subnet as the streaming device, with the same gateway configured.

A2：Crossing switches.

The multicast function must be enabled and configured on the switch. If the connection crosses switches, the corresponding ports on the switches need to be configured appropriately (e.g., IGMP Snooping).

A3：Incorrect multicast address.

The valid range for multicast addresses is 224.x.x.xto 239.x.x.x. It is recommended not to exceed this range.

A1：Port issues.

For SRT transmission over the public internet, it is recommended to use ports 10000 and above to avoid conflicts. Also, confirm that the port is not already in use.

A2：Incorrect transport protocol setting.

SRT transmission relies on the UDP protocol. If TCP mode is incorrectly selected, push stream failure will occur.

A3：StreamID and passphrase.

If a StreamID and/or passphrase are required, they must be filled in correctly in the respective fields. Ensure the correct encryption mode is selected.

Problem Background

When the customer starts the SRT streaming of E3, an error is displayed

problem causes

After location analysis, we found that the following problem occurred in the customer’s on-site environment: when the E3 and the switch were powered off and restarted together, the E3 would start before the switch. In this case, when the E3 started, the switch had not yet started completely, causing the E3 to be unable to connect to the network normally. Therefore, when the E3 could not connect to the network, performing the SRT streaming operation would result in an error.

solution

You can try the following steps to resolve the issue :

1. Wait for the switch to fully boot up:

After the E3 and the switch are powered off and restarted together, wait for a while to ensure that the switch is fully started and stably connected to the network before starting the E3. This can avoid the problem that the E3 cannot connect to the network when starting SRT streaming .

2. Manually restart E3

If you have already powered on the E3 but are experiencing network connectivity issues that cause SRT streaming errors, you can try manually restarting the E3. After the switch is fully powered on, restart the E3 to ensure it can connect to the network properly.

Problem Background

An encoder is a device or software that converts a video source signal into a compressed format video file or stream.

In the process of video encoding, the video signal undergoes multiple stages, including frame capture, processing, compression, and output to the target storage or network.

The core purpose of this process is to ensure the highest possible image quality while minimizing file size to accommodate the capabilities of network transmission, storage, and playback devices.

Common standards for video encoding include H.264 (AVC), H.265 (HEVC), etc.

The encoder will select different compression ratios, rate control methods, and other parameters during encoding based on the different encoding algorithms and application requirements.

Blurred image quality is usually caused by compression of video signals during the encoding process or packet loss during network transmission.

In order to ensure the final output image quality, various parameters need to be finely controlled during encoding.

Common Troubleshooting Approaches

The problem of blurry image quality usually occurs in the following aspects: bitrate, frame rate, resolution, network conditions, etc.

1. Bit rate issue

Bitrate refers to the amount of video data transmitted per unit of time, typically measured in Kbps (kilobits per second) or Mbps (megabits per second).

In video encoding, the bit rate has a significant impact on the image quality, and lower bit rates can lead to excessive compression of the image quality, resulting in blurring.

1. Troubleshooting approach:

Confirm the bitrate set during encoding: Check if the bitrate of the current video is set reasonably.

A low bitrate can significantly reduce image quality, resulting in loss of details and blurring.

For 1080p videos, it is recommended to have a bitrate of at least 3-6 Mbps.

For 4K videos, it is recommended to have a bitrate of at least 15-25 Mbps.

Using appropriate rate control methods: There are two main rate control methods:

Constant Bitrate (CBR): The video’s bitrate is fixed and suitable for real-time videos that require smooth playback.

Variable Bitrate (VBR): dynamically adjusts the bitrate according to the complexity of the image, which can improve the image quality while maintaining a low file size, and is suitable for file storage.

Attempt to increase the bitrate: If possible, increase the bitrate during encoding and check if the image quality has improved.

2. Frame rate issue

Frame rate refers to the number of frames displayed per second, usually measured in frames per second (fps).

Insufficient frame rate can lead to disjointed motion and stuttering, thereby affecting the clarity and smoothness of the video.

Troubleshooting approach:

Confirm the frame rate used: Check the frame rate used during video encoding.

If the frame rate is too low (such as below 15fps), the video will appear unsmooth and may produce blurry effects.

The standard video frame rate is usually 30fps, while high-speed action or gaming videos can use 60fps.

Increase frame rate: Try using a higher frame rate for encoding, especially in high dynamic scenes where 60fps is a suitable choice.

Frame rate and content matching: If there are few dynamic changes in the video content, the frame rate can be appropriately reduced to save bandwidth and storage.

3. Network issues

The impact of network bandwidth and stability on real-time video encoding is crucial, especially in the process of video streaming transmission.

Unstable or insufficient network bandwidth can lead to packet loss, delay, or decreased image quality during video transmission.

Troubleshooting approach:

Check network bandwidth: Check if the upstream bandwidth of the network is sufficient to support the streaming media transmission of the current video.

Network speed measurement tools can be used to detect the actual bandwidth.

The bitrate of video streams should usually not exceed 80% -90% of the available network bandwidth to avoid buffering or image quality degradation caused by bandwidth fluctuations.

Use adaptive bit rate: To cope with network fluctuations, adaptive bit rate (ABR) encoding or streaming protocols (such as HLS) can be used, which can dynamically adjust the video bitrate according to network conditions.

Using low latency transmission protocols: For real-time video transmission, it is recommended to use low latency transmission protocols such as RTMP to reduce the impact of latency and packet loss.

4. Resolution issue

Resolution refers to the clarity of a video image, typically expressed as width x height (e.g. 1920 x 1080).

Low resolution can cause loss of video details and blurriness.

Troubleshooting approach:

Check resolution settings: Ensure that the resolution set during encoding meets the requirements of the video content.

The higher the video resolution, the clearer the image, but it also increases the file size.

For example, for 1080p videos, the resolution should be 1920 × 1080, while for 4K videos it should be 3840 × 2160.

Avoid excessive compression: If the video resolution is reduced to a too low value, although the file becomes smaller, many details will be lost, resulting in blurry image quality.

Resolution matching with target device: Ensure that the video resolution matches the display capability of the target playback device.

Excessively high resolution will waste bandwidth, while excessively low resolution will affect the viewing experience.

5. Encoding settings

The settings of the encoder affect the compression effect and image quality of the video, especially the selection of parameters such as encoding method and quality control.

Troubleshooting approach:

Encoding method: Using a more efficient encoder can achieve better compression and image quality.

For example, H.265/HEVC can provide better image quality at the same bitrate compared to H.264.

GOP setting: GOP length refers to the number of P-frames and B-frames in a group of frames, excluding I-frames (keyframes).

I-frames are keyframes that can be decoded independently, while P-frames and B-frames depend on the preceding and succeeding frames.

Generally speaking, to achieve the best picture quality, the GOP setting value should be 1-2 times the frame rate of the video source.

A longer GOP can be used in the static part of the video, while a shorter GOP can be used in the dynamic part (such as fast-moving or changing scenes) to ensure the quality and smoothness of the video.

When using adaptive bitrate control, the target bitrate and maximum bitrate can be adjusted to balance video quality and file size.

1. Check the firmware file format and naming

Is there a prompt saying ‘non bin file uploaded’ during upgrade?

Please upgrade using Google Chrome on a Windows computer to avoid browser compatibility issues.

→ Ensure that the firmware file name has not been modified (such as no spaces, special characters, or suffixes (1), etc.).

If using an Apple computer, it is recommended to upgrade to a Windows system.

2 . Verify that the firmware version matches the device model

Prompt ‘firmware version model error’?

It may be caused by a mismatch between the firmware version and the device model.

Firstly, confirm the purchased product model and find the corresponding firmware to download and upgrade.

For example, E1 and E1-NDI (supporting NDI protocol) products require downloading the corresponding firmware that supports NDI.

For example, products with NDI markings in the following image are considered to support NDI.

• Login to the official website to confirm the device model (if E1/NDI version requires downloading the corresponding firmware with NDI identification).
• Download Path: KiloView Official Website – Data Download

3. Clear browser cache and force refresh

Prompt ‘network error’ or unresponsive upgrade?

This situation is mainly caused by browser caching, which aims to speed up webpage loading by storing previously accessed resources and reducing requests to the server.

However, if the data in the cache is outdated, damaged, or does not match the current webpage, it may cause display issues.

As a result, the device cannot be upgraded normally.

The following methods can be used to repair it

Press Ctrl+F5 (Windows) or CMD+Shift+R (Mac) to force the page to refresh.

→ Clear browser cache (Settings → Privacy → Clear cached data).

4 . Check if the upgrade path requires an intermediate version

Display ‘Upgrade successful’ but version number not updated?

This situation mostly occurs when the changes in the old and new versions are significant and cannot be directly upgraded. It is necessary to first upgrade to the intermediate intermediate version before upgrading to the latest version.

Partial cross version upgrades (such as D350 from 1.00.0002 to 1.01.0027) require upgrading to an intermediate version (such as 1.01.0018) first.

Problem Background

The 264/H.265 encoder is widely used in video streaming media transmission.However, after prolonged operation, there may be issues such as performance degradation, lagging, and encoding anomalies.These issues may be caused by various factors such as memory leaks, excessive resource usage, high temperatures, or software errors.In order to ensure the long-term stable operation of the encoder, this FAQ provides some common solutions and temporary solutions, especially the timed restart function, to help solve problems that occur after long-term operation.

Common Troubleshooting Approaches

1. Analysis of common problems

A. Memory leak

Problem: The encoder software may have a memory leak issue, causing the system memory to gradually deplete, affecting encoding performance, and ultimately leading to encoder crashes or exceptions.

Symptom: Excessive system resource utilization, resulting in video lag, frame loss, or asynchronous audio and video.

B. CPU load too high

Problem: Long term operation may lead to excessive CPU load, resulting in decreased encoding performance and stuttering of video output streams.

Symptom: The CPU usage of the encoder or related system processes remains consistently high and is not released in a timely manner.

C. The temperature is too high

Problem: If the encoder works for too long, it may cause the hardware temperature to be too high, resulting in a decrease in system performance or even stopping working.

Symptoms: Abnormal restart, stuttering, or inability to output video streams from the encoder.

D. Software/firmware error

Problem: There may be bugs or configuration issues with the encoder software or firmware, which can cause abnormalities after prolonged operation.

Symptom: The encoder fails to function properly after prolonged operation, resulting in crashes, crashes, or inability to continue encoding.

2. Scheduled restart plan

Timed restart is a simple and effective temporary solution, especially suitable for encoders that may experience anomalies after prolonged operation.

By regularly restarting the system, resources can be released to avoid exceptions caused by issues such as memory leaks and excessive CPU usage.

A. The advantages of setting a timed restart:

Resource release: Scheduled restarts help clean up system memory, free up occupied CPU resources, and avoid performance issues caused by prolonged operation.

Improving system stability: Regular restarts can reduce the accumulation of software or firmware errors and enhance the stability of the encoder.

Simple and easy to implement: Setting up scheduled restarts does not require complex configuration and is suitable for temporary problem-solving.

B. Method for setting scheduled restarts:

In general, when entering the encoder-, you can see that the device maintenance module has a timed restart switch button.

C. Precautions for timed restart:

Ensure that the encoder and its related services can automatically start after restart to avoid service interruption caused by restart.

The restart time should be selected during low peak periods as much as possible to minimize the impact on normal business.

For long running tasks, the restart frequency should not be set too high to avoid unnecessary interruptions to the system operation.

3. Long term solutions

Although scheduled restarts are an effective temporary solution, they are not a long-term solution.

If the encoder frequently encounters abnormal problems after long-term operation, it is recommended to describe the scenario where the problem occurred clearly, collect log files, provide necessary encoding parameter detailed settings, technical support, and conduct in-depth investigation and optimization.

Problem Background

When the customer starts the SRT streaming of E3, an error is displayed

Common Troubleshooting Approaches

problem causes

After location analysis, we found that the following problem occurred in the customer’s on-site environment: when the E3 and the switch were powered off and restarted together, the E3 would start before the switch. In this case, when the E3 started, the switch had not yet started completely, causing the E3 to be unable to connect to the network normally. Therefore, when the E3 could not connect to the network, performing the SRT streaming operation would result in an error.

solution

You can try the following steps to resolve the issue :

**1. ** Wait for the switch to fully boot up:

After the E3 and the switch are powered off and restarted together, wait for a while to ensure that the switch is fully started and stably connected to the network before starting the E3. This can avoid the problem that the E3 cannot connect to the network when starting SRT streaming .

**2. ** Manually restart E3:

If you have already powered on the E3 but are experiencing network connectivity issues that cause SRT streaming errors, you can try manually restarting the E3. After the switch is fully powered on, restart the E3 to ensure it can connect to the network properly.

Problem Background

Network Attached Storage (NAS) is a device used for centralized storage and management of data, which can be accessed through a network.

However, after configuring the NAS, users may encounter situations where the device cannot connect to the NAS.

This type of problem may stem from multiple aspects, including firewall configuration, sharing settings, network configuration, etc.

This article will provide a detailed explanation on how to troubleshoot issues such as firewall configuration, sharing configuration, and network settings to solve NAS connectivity problems.

Common Troubleshooting Approaches

1. Analysis of common problems

A. Firewall or router configuration issues

Problem: The configuration of the firewall or router may be preventing communication between the device and NAS.

Symptom: Error messages such as “connection timeout” and “unable to access” appear when attempting to access the NAS.

B. NAS sharing settings are incorrect

Problem: The shared folder permissions on the NAS are not properly set, resulting in inability to connect.

Or improper NAS storage configuration in the device may result in connection failure.

Symptom: The user is denied access or experiences permission errors when configuring to connect to NAS on the device UI interface.

C. Network configuration issues

Problem: NAS and client devices may be on different subnets or have incorrect IP configurations, resulting in the inability to establish a connection.

Symptoms: Connection failure, device unable to discover NAS.

D. DNS configuration issue

Problem: DNS configuration errors between NAS and client devices may result in inability to access NAS by name.

Symptom: Unable to access NAS through device name, can only connect through IP address.

E. SMB protocol or network protocol configuration issues

Problem: The file sharing protocol of NAS (such as SMB, NFS, etc.) is not configured correctly, resulting in connection issues.

Symptom: Unable to access NAS through commonly used sharing protocols.

2. Troubleshooting steps

The following are detailed troubleshooting steps for NAS configuration failure.

A. Check firewall configuration

1. Ensure that the firewall allows file sharing ports

Step: Open the firewall settings of the NAS device and confirm that the following ports are open:

SMB protocol: Port 445

NFS protocol: Port 2049

FTP Protocol: Port 21

Operation:

Check if the above ports are allowed in Windows Firewall or other security software.

Ensure that the relevant ports of the NAS are open to the outside world in the router firewall.

2. Turn off firewall testing

Step: Temporarily shut down the firewall and test the connection to confirm if the firewall is the root cause of the problem.

If the connection can be made after turning off the firewall, the problem may lie in the firewall configuration.

Suggestion: Based on the test results, adjust the firewall settings appropriately or add the relevant ports to the exception list.

2. Check the router firewall

Step: If the NAS is connected to a router, ensure that the router’s firewall does not restrict access between devices within the local area network.

Operation: Log in to the router management interface, check the firewall configuration, and ensure that devices within the local area network can access each other.

B. Check sharing settings

1. Verify shared folder permissions

Step: Log in to the NAS management interface and check if the shared folder and access permissions are configured correctly.

Ensure that the folder is shared.

Set appropriate access permissions to ensure that the device has read and write permissions.

Suggestion: Check user permissions one by one to ensure that the account used has access permissions.

Refer to the detailed explanation and examples of parameters in the user manual to fill in the parameter configuration.

2. Verify the network sharing protocol

Step: Confirm that the NAS has enabled the appropriate network sharing protocol (such as SMB, NFS, AFP, CIFS, etc.).

In Windows, the SMB protocol is used by default for file sharing.

In Linux/MacOS, NFS or AFP protocols may be used.

In our encoder, we support the connection of NFS/CIFS protocols.

Operation:

Check the sharing settings on the NAS and confirm that the correct sharing protocol is enabled.

Ensure that the NAS and devices support the same protocol version.

C. Check network configuration

1. Ensure that NAS and client devices are on the same network segment

Step: Check the IP addresses of the NAS and client devices to ensure they are in the same subnet.

Operation:

a. Check the IP address settings of the NAS and confirm that it is in the correct IP range.

b. Ensure that the client device and NAS are on the same LAN or configured with the correct routing.

2. Confirm the stability of the network connection

Step: Use the ping command to test the connection between the client device and the NAS.

For example, on Windows, open a command prompt and type pingto check if a reply can be received successfully.

Suggestion: If the ping test fails, it may be due to network faults or unstable connections between NAS and client devices.

2. Check DHCP or static IP configuration

Step: Ensure that the IP addresses of the NAS and devices are configured correctly.

Operation:

If using DHCP, please ensure that the router has assigned the correct IP address to the NAS.

If using a static IP, ensure that the IP address does not conflict and matches the subnet configured by the router.

D. Check DNS configuration

1. Connect using an IP address

Step: Enter the IP address of the NAS directly in the browser or file manager and check if it can connect properly.

Suggestion: If you can connect using an IP address but cannot connect using a device name, it may be a DNS configuration issue.

2. Check the DNS server configuration

Step: Ensure that the DNS configuration of the NAS and client devices is correct.

Operation:

a. If using local DNS, ensure that the DNS server can correctly resolve the host name of the NAS.

b. If using public DNS, confirm that it can correctly resolve device names in the network.

E. Check file sharing protocol settings

1. Confirm the activation of SMB protocol

Step: If using the SMB protocol for sharing, ensure that both the NAS and client devices have enabled the SMB protocol.

Operation:

a. Confirm that the SMB sharing feature is enabled in the NAS management interface.

b. In the Windows system, open Control Panel>Programs>Enable or Disable Windows Features and confirm that the SMB 1.0/CIFS file sharing support option is enabled.

Problem Background

The customer wants to use an external hard drive to record and save videos, but tried using different hard drives and USB drives for recording, but E3 cannot recognize them.

Common Troubleshooting Approaches

Troubleshooting steps:

The inability of E3 devices to recognize USB hard drives may be related to hardware compatibility, USB port failures, incompatible hard drive formats, software versions, power requirements, and other factors.

In terms of USB versions, E3 supports USB 3.2 and below (including 2.0) USB and SSD devices.

In terms of format, E3 supports mainstream USB hard drive and storage device formats, including FAT32, exFAT, and NTFS.

To ensure optimal compatibility and performance, it is recommended to use NTFS or FAT32 formats, which were also the most commonly used formats during our testing process.

In terms of capacity, E3 devices have no specific limitations on the capacity of USB hard drives and can support different capacities ranging from tens of GB to several TB.

However, the minimum capacity cannot be less than 1GB.

For hard drives that require additional power supply, if there is a matching power supply, they can be recognized after inserting E3.

However, E3 hardware does not have the function of supplying power to the hard drive, so if the hard drive is not powered on, E3 cannot power on and recognize it.

Based on the above information, we can follow the following steps to investigate:
Step 1: Guide the user to upgrade the firmware to the latest version first

Download link for EN firmware: Download Center – Kiloview

Step 2: Check the USB port and the connected USB cable

Check the USB port on the E3 encoder to ensure it is functioning properly, and use different cables to troubleshoot any cable related issues.

Step 3: Check the format of the hard drive and USB drive

Verify if the format of the hard drive and USB drive is correct, and if they are indeed in the format we support. If necessary, format the hard drive and USB before inserting E3.

Step 4: Verify the effectiveness of HDD and USB

Verify whether the computer can recognize hard drives and USB drives.

If it cannot be recognized, the problem may lie in the storage device itself.

Step 5: Confirm whether the port connected to E3 is Type C or Type A

Determine whether to use the front Type C port or the rear Type A port for connection.

If it is a front-end Type-C interface, it may not be recognized due to hardware compatibility issues, such as Samsung T7 SSD.

After uniformly modifying the hardware, this SSD can be recognized.

Step 6: Conduct comparative testing

Connect this hard drive or USB to another E3 device to confirm if it is a hardware issue with a single device.

Connect different models and brands of hard drives or USB on this E3 to confirm if there are compatibility issues.

Step 7: Collect accessory models

Collect the models of hard drives and USB drives used by users, test and verify if they are compatible.

Problem Background

The customer set the CBR to 8M, but the actual encoding rate did not reach 8M. Why?

How to reach 8M?

Common Troubleshooting Approaches

The reasons why the actual encoding rate may not always reach 8Mbps are:

1. Changes in video content: Different scenes in the video have varying levels of complexity, which may lead to fluctuations in bitrate.

If the complexity of the video source is low, according to the dynamic bitrate algorithm, the actual encoding bitrate will not be too high.

2. Network conditions: The available network bandwidth may affect the encoder’s ability to maintain a constant bit rate.

3. Quality of Service (QoS) settings: If QoS settings are in place, they may prioritize other traffic over video streams, affecting bit rates.

4. Encoding parameters: Encoding settings such as resolution, frame rate, and GOP size may affect the overall bitrate.

You can try the following steps to solve the problem:

1. Network configuration: Ensure stable network connection and sufficient bandwidth to support the required CBR.

To ensure the stability of data flow, it is recommended to manually configure the IP address instead of using DHCP to obtain the IP.

2. Adjust encoding parametersIf possible, adjust encoding parameters to find a balance between video quality and bit rate consistency.

For example, adjust the bit rate to 10M or higher.

Adjust GOP value.

The smaller the GOP value, the closer the keyframes are, and the greater the bandwidth consumption.

3. Inserting empty packets : Some satellite TV live streaming scenarios may require a consistently stable bitrate.

** ** To ensure the stability of the bitrate and avoid image quality issues caused by bitrate fluctuations, it is possible to set the insertion of null packets at E3.

When the bitrate is insufficient, a null value will be inserted to increase the bitrate.

Note that this setting is only supported for versions 0034 and above, and only TS-UDP protocol and SRT protocol support inserting empty packets.