From ccfae7e28769084aca0b6cd1f268165af5f82b30 Mon Sep 17 00:00:00 2001 From: jp9000 Date: Wed, 7 Jan 2015 03:16:02 -0800 Subject: [PATCH] rtmp-services: Fix setting of custom x264 profile Profile was being set as a bool rather than a string, resulting in an embarrassing situation where the profile was being set to 'true' rather than the actual profile name. ..There really needs to be a compiler warning for using non-bools as bools. This is one of the reason I started using !! to change non-bools to bools. --- plugins/rtmp-services/rtmp-common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/rtmp-services/rtmp-common.c b/plugins/rtmp-services/rtmp-common.c index 4dc1ed9b8..8ee91f471 100644 --- a/plugins/rtmp-services/rtmp-common.c +++ b/plugins/rtmp-services/rtmp-common.c @@ -245,7 +245,7 @@ static void apply_video_encoder_settings(obs_encoder_t *encoder, item = json_object_get(recommended, "profile"); if (item && json_is_string(item)) { const char *profile = json_string_value(item); - obs_data_set_bool(settings, "profile", profile); + obs_data_set_string(settings, "profile", profile); } item = json_object_get(recommended, "max video bitrate");