From 63f013dd2492f6c01792198aceb6874ccf227086 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Fri, 15 Nov 2024 18:45:41 -0500 Subject: Remove transport position dumping from Jack process callback This is handy at times, but prints in the process callback which is obviously not realtime safe. The communication dumping is, though, and both are controlled by the same option, so there wasn't a way to enable that without introducing a pretty severe performance issue in the audio thread. So, simply remove it for now. If transport dumping is really needed, it can be implemented by sending the information to the main thread for printing there, which will be easier after the upcoming work to improve the communication facilities. --- src/jack.c | 2 -- 1 file changed, 2 deletions(-) (limited to 'src/jack.c') diff --git a/src/jack.c b/src/jack.c index 7971987..3a92ff4 100644 --- a/src/jack.c +++ b/src/jack.c @@ -121,8 +121,6 @@ jack_process_cb(jack_nframes_t nframes, void* data) lv2_atom_forge_key(forge, jalv->urids.time_beatsPerMinute); lv2_atom_forge_float(forge, pos.beats_per_minute); } - - jalv_dump_atom(jalv, stdout, "Position", lv2_pos, 32); } // Update transport state to expected values for next cycle -- cgit v1.2.1