Upon further investigation I found that in Ardour's Jack latency menu, the "frames/period" DO in fact match up with the number in qjackctl. What showed a confusing half-value was Ardour's "output latency" display (always half the milliseconds shown in Jack). The XRUNS I saw were probably just due to Ardour requiring twice the latency of other jack programs. So, to me, this behavior is actually not a bug. Nothing to fix.
However, there was another Ardour latency-related bug in 9.11 that was fixed in Ardour 2.8.8 (http://ardour.org/node/3384). So, as long as Gazpacho uses at least 2.8.8, should be good. ** Changed in: puredyne-live Status: In Progress => Invalid -- You received this bug notification because you are a member of puredyne team, which is the registrant for Puredyne Live. https://bugs.launchpad.net/bugs/793798 Title: Ardour defaults to half the frames/period of Jack (9.11) Status in Puredyne liveCD/DVD/USB/HD: Invalid Bug description: NOTE: APPLIES TO Puredyne 9.11 Even with Jack operating perfectly, opening a project in Ardour results in Ardour defaulting to half the "Latency" (frames/period) value that Jack is set at. This always produces XRUNS for me. An easy work-around is changing Ardour's latency value (Jack-->Latency-->[value]) to match Jack's frame/period or greater. This ALWAYS prevents XRUNS from Ardour (aside from some Ardour/LADSPA- specific bugs). As a side note, that this problem does not exist on Ubuntu Studio 9.10 which also has Ardour 2.8.2, so this is why I consider it a Puredyne- specific bug. To manage notifications about this bug go to: https://bugs.launchpad.net/puredyne-live/+bug/793798/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~puredyne-team Post to : [email protected] Unsubscribe : https://launchpad.net/~puredyne-team More help : https://help.launchpad.net/ListHelp
