Jack Transport - Revision history

Achenar at 13:56, 27 May 2020

2020-05-27T13:56:33Z

← Older revision		Revision as of 13:56, 27 May 2020
Line 29:		Line 29:
	== PDC and Jack Transport ==		== PDC and Jack Transport ==

	Jack doesn't provide a way to explicitly handle latencies, which, when combined with PDC (~~automatic~~ plugin delay compensation) in Renoise, can result in small 'misfires'. For example, if another application attempts to jump Renoise to a specific "position", Renoise will attempt to compensate by jumping to "position + overall PDC latency". If this is causing issues, you should temporarily disable the PDC in Renoise.		Jack doesn't provide a way to explicitly handle latencies, which, when combined with [[Preferences#Automatic_PDC\|Automatic PDC]] (plugin delay compensation) in Renoise, can result in small 'misfires'. For example, if another application attempts to jump Renoise to a specific "position", Renoise will attempt to compensate by jumping to "position + overall PDC latency". If this is causing issues, you should temporarily disable the PDC in Renoise.



	[[Image:3.0_jack.png]]		[[Image:3.0_jack.png]]

Achenar: /* Jack Transport */

2019-10-04T14:04:17Z

Jack Transport

← Older revision		Revision as of 14:04, 4 October 2019
Line 1:		Line 1:
	= Jack Transport =		= Jack Transport =

	Jack Transport ~~(Linux only) adds~~ the ability to sync Renoise with multiple Jack clients on Linux. ~~This allows audio programs to be in sync with each other, all connected via Jack Transport. You~~ can start, stop and relocate the play position from any of the Jack enabled applications. ~~All~~ software ''"jacked into"'' the session will react and synchronise accordingly.		Jack Transport provides the ability to sync Renoise with multiple Jack clients on Linux. With it you can start, stop and relocate the play position from any of the Jack enabled applications. Any software that is ''"jacked into"'' the session will react and synchronise accordingly. Jack Transport is enabled in the [[Preferences#Audio\|Audio Preferences]] panel, though note that it's disabled by default, even when it has been selected as the audio device.

	[[Image:3.0_jack.~~png~~]]
			[[Image:3.0_jack-sync.gif]]


Line 9:		Line 10:

	'''Level 1:''' Each Jack client has the power to start, stop and relocate (change the playback position of) the transport. This is represented in either seconds or sample time.<br>		'''Level 1:''' Each Jack client has the power to start, stop and relocate (change the playback position of) the transport. This is represented in either seconds or sample time.<br>
	'''Level 2:''' Only one Jack client can control the Time Base, which is the tempo, time signature and beat position.		'''Level 2:''' Only one Jack client can control the Time Base, which is a combination of the tempo, time signature and beat position.

	Most applications support the first level of Jack Transport control~~. The second level is~~, at the time of writing, rarely supported. If ~~there is~~ more than one application running which supports the Time Base, Jack will select one automatically.		Most applications support the first level of Jack Transport control, though, at the time of writing, the second level is rarely supported. If more than one application is running which supports the Time Base, Jack will select one automatically.


Line 23:		Line 24:
	== Dealing with Loops ==		== Dealing with Loops ==

	~~There~~ is ~~no loop information in~~ the Time Base~~. Every~~ client will try to apply its own loops, fighting with the other Jack programs to reposition. To avoid this conflict, enable loops in the application that is currently active and disable them in the others.		Loop information is not transmitted via the Time Base, meaning that each client will try to apply its own loops, fighting with the other Jack programs to reposition. To avoid this conflict, enable loops in the application that is currently active and disable them in the others.


	== PDC and Jack Transport ==		== PDC and Jack Transport ==

	Jack doesn't provide a way to explicitly handle latencies~~. When~~ PDC (automatic plugin delay compensation) ~~is enabled~~ in Renoise ~~and~~, ~~for~~ example, ~~you want~~ to ~~use Ardour to tell~~ Renoise to ~~jump to pos 0~~, Renoise will attempt to compensate by jumping to "~~Pos 0~~ + overall PDC ~~Latency~~"~~. This offset may result in a small misfire~~. If this ~~becomes a problem~~ you should temporarily disable PDC in Renoise.		Jack doesn't provide a way to explicitly handle latencies, which, when combined with PDC (automatic plugin delay compensation) in Renoise, can result in small 'misfires'. For example, if another application attempts to jump Renoise to a specific "position", Renoise will attempt to compensate by jumping to "position + overall PDC latency". If this is causing issues, you should temporarily disable the PDC in Renoise.


	~~== Configuring Jack Transport ==~~

	~~The option to turn on Jack is in the [[Preferences#Audio\|Audio Preferences]] panel. Jack Transport is disabled by default, even when Jack is selected as the audio device in Renoise.~~		[[Image:3.0_jack.png]]

	[[Image:3.0_jack~~-sync~~.~~gif~~]]

imported>Taktik at 16:04, 13 May 2014

2014-05-13T16:04:10Z

← Older revision		Revision as of 16:04, 13 May 2014
Line 1:		Line 1:
	= Jack Transport ~~(Linux only)~~ =		= Jack Transport =

	Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.		Jack Transport (Linux only) adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.

	[[Image:3.0_jack.png]]		[[Image:3.0_jack.png]]

imported>Achenar at 10:43, 28 April 2014

2014-04-28T10:43:16Z

← Older revision		Revision as of 10:43, 28 April 2014
Line 35:		Line 35:
	The option to turn on Jack is in the [[Preferences#Audio\|Audio Preferences]] panel. Jack Transport is disabled by default, even when Jack is selected as the audio device in Renoise.		The option to turn on Jack is in the [[Preferences#Audio\|Audio Preferences]] panel. Jack Transport is disabled by default, even when Jack is selected as the audio device in Renoise.

	[[Image:~~Sato_stepup-jack~~-~~switch~~.~~png~~]]		[[Image:3.0_jack-sync.gif]]

imported>Achenar at 12:38, 26 April 2014

2014-04-26T12:38:21Z

← Older revision		Revision as of 12:38, 26 April 2014
Line 3:		Line 3:
	Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.		Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.

	[[Image:~~Sato_stepup-jack-transport~~.png]]		[[Image:3.0_jack.png]]

imported>Taktik at 16:18, 2 March 2010

2010-03-02T16:18:22Z

← Older revision		Revision as of 16:18, 2 March 2010
Line 1:		Line 1:
	= Jack Transport =		= Jack Transport (Linux only) =

	Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.		Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.

imported>Taktik at 18:54, 1 March 2010

2010-03-01T18:54:23Z

← Older revision		Revision as of 18:54, 1 March 2010
Line 19:		Line 19:

	In the case where all Jack Transport applications are Time Base aware, you still have to make sure that all clients are using the same tempo and automation. This is because playback relocation will be done in sample time instead of "beat time". All clients need to have the same base tempo in order to jump to the same positions.		In the case where all Jack Transport applications are Time Base aware, you still have to make sure that all clients are using the same tempo and automation. This is because playback relocation will be done in sample time instead of "beat time". All clients need to have the same base tempo in order to jump to the same positions.

	~~More succinctly:~~

imported>Achenar at 19:27, 26 February 2010

2010-02-26T19:27:40Z

imported>Achenar at 19:19, 26 February 2010

2010-02-26T19:19:02Z

← Older revision		Revision as of 19:19, 26 February 2010
Line 1:		Line 1:
	= Jack Transport =		= Jack Transport =

	Jack ~~transport~~ adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack transport. You can start, stop, and relocate the play position from any of the Jack enabled applications. All software "jacked into" the session will react and ~~synchronize~~ accordingly.		Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack transport. You can start, stop, and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.

	[[Image:Sato_stepup-jack-transport.png]]		[[Image:Sato_stepup-jack-transport.png]]

	~~== Levels of Jack Transport Control ==~~

	* '''Level 1:''' Each Jack client has the power to start, stop and relocate the transport. Relocation implies playback position change.		== Levels of Jack Transport Control ==
	~~This is represented in either seconds or sample time.~~
	* '''Level 2:''' One, and only one, Jack client can control the "time base". The time base is the tempo, time signature, and beat position.

	~~Most applications support the first level of Jack transport control. The second level is, at the time~~ of ~~writing, rarely supported. If there is more than one app running which supports "time base",~~ Jack ~~will select one automatically.~~

	== Dealing with Tempo ~~(-automation)~~ ==		* '''Level 1:''' Each Jack client has the power to start, stop and relocate the transport. Relocation implies playback position change. This is represented in either seconds or sample time.
			* '''Level 2:''' Only one Jack client can control the Time Base. The Time Base is the tempo, time signature, and beat position.

			Most applications support the first level of Jack transport control. The second level is, at the time of writing, rarely supported. If there is more than one application running which supports the Time Base, Jack will select one automatically.


			== Dealing with Tempo ==

			Tempo information is exchanged only when the synchronized application supports Time Base. As stated above, most applications do not support this and so you will have to set the tempo manually.

			In the case where all Jack transport applications are Time Base aware, you still have to make sure that all clients are using the same tempo and automation. This is because playback relocation will be done in sample time instead of "beat time". All clients have to have the same base tempo in order to jump to the same positions.

	Tempo information is exchanged only when the synchronized application support time base. As stated above, most apps do not support this. Because of this caveat, you will have to set the tempo manually.

	In the case where all Jack transport applications are time base aware, you still have to make sure that all clients are using the same tempo and automation. This is because playback relocation will be done in sample time instead of "beat time". All clients have to have the same base tempo in order to jump to the same positions.

	More succinctly:		More succinctly:


	== Dealing with Loops ==		== Dealing with Loops ==

	There is no loop information in ~~time bases~~. Every client will try to apply its own loops, fighting with the other Jack programs to reposition. To avoid this ~~unwanted~~ conflict, enable loops in the application that is currently active, disable them in the others.		There is no loop information in the Time Base. Every client will try to apply its own loops, fighting with the other Jack programs to reposition. To avoid this conflict, enable loops in the application that is currently active and disable them in the others.


			== PDC and Jack Transport ==

	== PDC and ~~Jack Transport ==~~		Jack doesn't provide a way to explicitly handle latencies. When PDC (automatic plugin delay compensation) is enabled in Renoise and you want to use Ardour to tell Renoise to jump to pos 0, Renoise will attempt to compensate by jumping to "Pos 0 + overall PDC Latency". This offset may result in a small misfire. If becomes a problem you should temporarily disable PDC in Renoise.

	Jack doesn't provide a way to explicitly handle latencies. When PDC (automatic plugin delay compenstaion) is enabled in Renoise, and you want to tell Renoise from Ardour to jump to pos 0, Renoise will attempt to compensate by jumping to "Pos 0 + overall PDC Latency". This offset may result in a small misfire. If this gets on your nerves, you should temporarily disable PDC in Renoise.

	== Configuring Jack Transport ==		== Configuring Jack Transport ==

	~~Configuration wise there~~ is ~~just one switch. It's~~ in the [[Preferences#Audio\|Audio Preferences]] ~~pane~~. Jack ~~transport~~ is disabled by default, even when Jack ~~was~~ selected as the Audio device in Renoise.		The option to turn on Jack is in the [[Preferences#Audio\|Audio Preferences]] panel. Jack Transport is disabled by default, even when Jack is selected as the Audio device in Renoise.

	[[Image:Sato_stepup-jack-switch.png]]		[[Image:Sato_stepup-jack-switch.png]]

imported>Taktik: /* Configuring Jack Transport */

2010-02-09T20:12:41Z

Configuring Jack Transport

← Older revision		Revision as of 20:12, 9 February 2010
Line 31:		Line 31:
	== Configuring Jack Transport ==		== Configuring Jack Transport ==

	Configuration wise there is just one switch. It's in the Audio ~~Prefs~~ pane. Jack transport is disabled by default, even when Jack was selected as the Audio device in Renoise.		Configuration wise there is just one switch. It's in the [[Preferences#Audio\|Audio Preferences]] pane. Jack transport is disabled by default, even when Jack was selected as the Audio device in Renoise.

	[[Image:Sato_stepup-jack-switch.png]]		[[Image:Sato_stepup-jack-switch.png]]

← Older revision		Revision as of 19:27, 26 February 2010
Line 1:		Line 1:
	= Jack Transport =		= Jack Transport =

	Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack ~~transport~~. You can start, stop, and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.		Jack Transport adds the ability to sync Renoise with multiple Jack clients on Linux. This allows audio programs to be in sync with each other, all connected via Jack Transport. You can start, stop and relocate the play position from any of the Jack enabled applications. All software ''"jacked into"'' the session will react and synchronise accordingly.

	[[Image:Sato_stepup-jack-transport.png]]		[[Image:Sato_stepup-jack-transport.png]]
Line 8:		Line 8:
	== Levels of Jack Transport Control ==		== Levels of Jack Transport Control ==

	* '''Level 1:''' Each Jack client has the power to start, stop and relocate the ~~transport. Relocation implies~~ playback position ~~change~~. This is represented in either seconds or sample time.		'''Level 1:''' Each Jack client has the power to start, stop and relocate (change the playback position of) the transport. This is represented in either seconds or sample time.<br>
	* '''Level 2:''' Only one Jack client can control the Time Base~~. The Time Base~~ is the tempo, time signature, and beat position.		'''Level 2:''' Only one Jack client can control the Time Base, which is the tempo, time signature and beat position.

	Most applications support the first level of Jack ~~transport~~ control. The second level is, at the time of writing, rarely supported. If there is more than one application running which supports the Time Base, Jack will select one automatically.		Most applications support the first level of Jack Transport control. The second level is, at the time of writing, rarely supported. If there is more than one application running which supports the Time Base, Jack will select one automatically.


Line 18:		Line 18:
	Tempo information is exchanged only when the synchronized application supports Time Base. As stated above, most applications do not support this and so you will have to set the tempo manually.		Tempo information is exchanged only when the synchronized application supports Time Base. As stated above, most applications do not support this and so you will have to set the tempo manually.

	In the case where all Jack ~~transport~~ applications are Time Base aware, you still have to make sure that all clients are using the same tempo and automation. This is because playback relocation will be done in sample time instead of "beat time". All clients ~~have~~ to have the same base tempo in order to jump to the same positions.		In the case where all Jack Transport applications are Time Base aware, you still have to make sure that all clients are using the same tempo and automation. This is because playback relocation will be done in sample time instead of "beat time". All clients need to have the same base tempo in order to jump to the same positions.

	More succinctly:		More succinctly:
Line 30:		Line 30:
	== PDC and Jack Transport ==		== PDC and Jack Transport ==

	Jack doesn't provide a way to explicitly handle latencies. When PDC (automatic plugin delay compensation) is enabled in Renoise and you want to use Ardour to tell Renoise to jump to pos 0, Renoise will attempt to compensate by jumping to "Pos 0 + overall PDC Latency". This offset may result in a small misfire. If becomes a problem you should temporarily disable PDC in Renoise.		Jack doesn't provide a way to explicitly handle latencies. When PDC (automatic plugin delay compensation) is enabled in Renoise and, for example, you want to use Ardour to tell Renoise to jump to pos 0, Renoise will attempt to compensate by jumping to "Pos 0 + overall PDC Latency". This offset may result in a small misfire. If this becomes a problem you should temporarily disable PDC in Renoise.


	== Configuring Jack Transport ==		== Configuring Jack Transport ==

	The option to turn on Jack is in the [[Preferences#Audio\|Audio Preferences]] panel. Jack Transport is disabled by default, even when Jack is selected as the ~~Audio~~ device in Renoise.		The option to turn on Jack is in the [[Preferences#Audio\|Audio Preferences]] panel. Jack Transport is disabled by default, even when Jack is selected as the audio device in Renoise.

	[[Image:Sato_stepup-jack-switch.png]]		[[Image:Sato_stepup-jack-switch.png]]