Always use revision number 1 when looking for status updates on the DACP remote contr...

diff --git a/dacp.c b/dacp.c
index 50cf0e170c42235477fe8cec2a4c69305158a1ef..c7adac58851fa906de5269f7b21846ad5cd00973 100644 (file)
--- a/dacp.c
+++ b/dacp.c
@@ -411,6 +411,7 @@ void set_dacp_server_information(rtsp_conn_info *conn) {
     debug(2, "set_dacp_server_information set IP to \"%s\" and DACP id to \"%s\".",
           dacp_server.ip_string, dacp_server.dacp_id);
 
+/*
     // If the client is forked-daapd, then we always use revision number 1
     // because otherwise the return read will hang in a "long poll" if there
     // are no changes.
@@ -424,6 +425,10 @@ void set_dacp_server_information(rtsp_conn_info *conn) {
         dacp_server.always_use_revision_number_1 = 1;
       }
     }
+*/
+
+    // always use revision number 1
+    dacp_server.always_use_revision_number_1 = 1;
 
     metadata_hub_modify_prolog();
     int ch = metadata_store.dacp_server_active != dacp_server.scan_enable;