History

remove a too-tight checking of bit rate

Sijia Chen committed 11 years ago

Commit 7cea82b1 parent e7debe71 file · +4 −7Browse files

Showing the changes to codec/encoder/core/src/encoder_ext.cpp (1 of 1 file). Show all

Unified · Split

codec/encoder/core/src/encoder_ext.cpp+4−7
@@ -90,16 +90,13 @@ int32_t WelsBitRateVerification (SLogContext* pLogCtx, SSpatialLayerConfig* pLay · 89 unmodified lines
90 if (pLayerParam->iMaxSpatialBitrate > iLevelMaxBitrate) {90 if (pLayerParam->iMaxSpatialBitrate > iLevelMaxBitrate) {
91 ELevelIdc iCurLevel = pLayerParam->uiLevelIdc;91 ELevelIdc iCurLevel = pLayerParam->uiLevelIdc;
92 if (WelsAdjustLevel (pLayerParam)) {92 if (WelsAdjustLevel (pLayerParam)) {
93 WelsLog (pLogCtx, WELS_LOG_ERROR,
94 "MaxSpatialBitrate (%d) is larger that the limitation LEVEL_5_2, considering it as error setting",
95 pLayerParam->iMaxSpatialBitrate);
96 return ENC_RETURN_UNSUPPORTED_PARA;
97 } else {
98 WelsLog (pLogCtx, WELS_LOG_WARNING,93 WelsLog (pLogCtx, WELS_LOG_WARNING,
94 "MaxSpatialBitrate (%d) is larger that the limitation LEVEL_5_2, the setting will be invalid",
95 pLayerParam->iMaxSpatialBitrate);
96 }
97 WelsLog (pLogCtx, WELS_LOG_INFO,
99 "Level is changed from (%d) to (%d) according to the maxbitrate",98 "Level is changed from (%d) to (%d) according to the maxbitrate",
100 iCurLevel, pLayerParam->uiLevelIdc);99 iCurLevel, pLayerParam->uiLevelIdc);
101 }
102
103 }100 }
104 if (pLayerParam->iMaxSpatialBitrate < pLayerParam->iSpatialBitrate) {101 if (pLayerParam->iMaxSpatialBitrate < pLayerParam->iSpatialBitrate) {
105 WelsLog (pLogCtx, WELS_LOG_ERROR,102 WelsLog (pLogCtx, WELS_LOG_ERROR,

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t