jackd provides too verbose output

[jackaudio]

jackd provides too verbose output

[sletz]

Pleas they the following patch:

diff --git a/common/JackControlAPI.cpp b/common/JackControlAPI.cpp
index 3cc1141..41a9a7b 100644
--- a/common/JackControlAPI.cpp
+++ b/common/JackControlAPI.cpp
@@ -234,7 +234,7 @@ jackctl_add_driver_parameters(
break;
case JackDriverParamBool:
jackctl_type = JackParamBool;

•        jackctl_value.b = descriptor_ptr->value.i;
  

•        jackctl_value.b = (bool)descriptor_ptr->value.i;
       break;
   default:
       jack_error("Unknown driver parameter type %i", (int)descriptor_ptr->type);
  

[sletz]

Please try the following patch and report:

diff --git a/common/JackControlAPI.cpp b/common/JackControlAPI.cpp
index 3cc1141..41a9a7b 100644
--- a/common/JackControlAPI.cpp
+++ b/common/JackControlAPI.cpp
@@ -234,7 +234,7 @@ jackctl_add_driver_parameters(
break;
case JackDriverParamBool:
jackctl_type = JackParamBool;

•        jackctl_value.b = descriptor_ptr->value.i;
  

•       jackctl_value.b = (bool)descriptor_ptr->value.i;
       break;
   default:
       jack_error("Unknown driver parameter type %i", (int)descriptor_ptr->type);
  

Stéphane

Le 22 sept. 2012 à 20:44, Fryderyk Dziarmagowski a écrit :

jackd provides much too verbose by default (despite --verbose not used or --silent passed as comand line parameter), example:

% jackd -P70 -p128 -t5000 -s -dfirewire -dhw:0 -r48000 -p64 -n3 -I127 -O127
jackdmp 1.9.9.4
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 70
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: JackDriver::Open capture_driver_name =
Jack: JackDriver::Open playback_driver_name =
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 64
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
Jack: JackSocketServerChannel::Open
Jack: JackServerSocket::Bind : addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackSocketServerChannel::BuildPoolTable size = 1
Jack: JackEngine::Open
Jack: JackClientSocket::Connect : addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackEngine::ClientInternalOpen: name = freewheel
Jack: JackEngine::AllocateRefNum ref = 1
Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_freewheel val = 0
Jack: JackEngine::NotifyAddClient: name = freewheel
Jack: JackDriver::ClientNotify ref = 1 driver = system name = freewheel notify = 0

using jack2 1.9.9 7c6d111

I found this bug describing same problem.

—
Reply to this email directly or view it on GitHub.

[freddix]

With above patch the output is unchanged.

[freddix]

This is a gcc regression in 4.7.x / 4.8.
Closing, since this is not a jack2 bug.