Libraries - Revision history

Achenar at 21:49, 1 December 2025

2025-12-01T21:49:37Z

← Older revision		Revision as of 21:49, 1 December 2025
Line 17:		Line 17:
	== Specific Preset Types ==		== Specific Preset Types ==

	[[Instruments]] are constructed from a variety of parts: [[Phrase Editor\|Phrases]], [[Keyzones]], [[Waveform]], [[Modulation]] and [[Effects]]. Specific preset types for each of these sections are available from a drop-down menu at the top right corner, where you can load, save, import and export. This allows an existing instrument to load the various presets into their specific sections without overwriting the whole instrument. A library can contain any of the file types associated with these sections:		[[Instruments]] are constructed from a variety of parts: [[Phrase Editor\|Phrases]], [[Keyzones]], [[Waveform]], [[Modulation]] and [[Effects]]. Specific preset types for each of these sections are available from a drop-down menu at the top-right corner, where you can load, save, import and export. This allows an existing instrument to load the various presets into their specific sections without overwriting the whole instrument. A library can contain any of the file types associated with these sections:

	[[Image:3.5_specificpresettypes.png]]		[[Image:3.5_specificpresettypes.png]]

Achenar at 20:35, 25 September 2025

2025-09-25T20:35:52Z

← Older revision		Revision as of 20:35, 25 September 2025
Line 1:		Line 1:
	= Libraries & Presets =		= Libraries & Presets =

	A library acts as a container for ~~other~~ presets, stored in the file format .xrnl, which is easily installed via drag and drop. Once installed, the ~~library’s~~ contents will be available to use through the preset ~~menu(s)~~. Since a library’s contents can be many different things, the installer will helpfully tell you what was installed - whether it was a bunch of new instruments, some multi-sample presets, or perhaps a collection of effect chains.		A library acts as a container for presets, stored in the file format .xrnl, which is easily installed via drag and drop. Once installed, the Library’s contents will be available to use through the preset menus, [[Effect_Chains#Storing/Recalling_Effect_Presets\|effect devices]] and [[Preferences#Theme\|Themes]]. Since a library’s contents can be many different things, the installer will helpfully tell you what was installed – whether it was a bunch of new instruments, some multi-sample presets, or perhaps a collection of effect chains.

	You may find it useful to watch [https://youtu.be/~~3V4f6oGcq8E a short~~ video on this subject.]		You may find it useful to watch [https://youtu.be/G4PQ8RLAHEc our video on this subject.]

	[[Image:dux1.4_presetbrowser.png]]		[[Image:dux1.4_presetbrowser.png]]


	If you save one of your own presets, ~~it is~~ stored in a special location - the User Library~~. This~~ is found in the same folder as any installed ~~libraries and~~ is shared for ~~use between~~ Renoise and Redux:		If you save one of your own presets, it’s stored in a special location – the User Library, which is found in the same folder as any installed Libraries. Since this is shared for Renoise and Redux, any preset from one can also be used in the other:

	* '''Windows:''' HOME/[My ]Documents/Renoise		* '''Windows:''' HOME/[My ]Documents/Renoise
Line 17:		Line 17:
	== Specific Preset Types ==		== Specific Preset Types ==

	[[Instruments]] are constructed from a variety of parts: [[Phrase Editor\|Phrases]], [[Keyzones]], [[Waveform~~\|Waveforms~~]], [[Modulation]] and [[Effects]]. Specific preset types for each of these sections are available from a drop-down menu at the top right corner, where you can load, save, import and export. This allows an existing instrument to load the various presets into their specific sections without overwriting the whole instrument. A library can contain any of the file types associated with these sections:		[[Instruments]] are constructed from a variety of parts: [[Phrase Editor\|Phrases]], [[Keyzones]], [[Waveform]], [[Modulation]] and [[Effects]]. Specific preset types for each of these sections are available from a drop-down menu at the top right corner, where you can load, save, import and export. This allows an existing instrument to load the various presets into their specific sections without overwriting the whole instrument. A library can contain any of the file types associated with these sections:

	[[Image:3.5_specificpresettypes.png]]		[[Image:3.5_specificpresettypes.png]]

	* '''Phrases''' - The Phrase Editor uses two different presets, depending on whether the selected phrase’s type is a [[Phrase Editor\|Pattern]] or a [[Phrase Editor#Phrase Scripting\| Script]]:		* '''Phrases''' - The Phrase Editor uses two different presets, depending on whether the selected phrase’s type is a [[Phrase Editor\|Pattern]] or a [[Phrase Editor#Phrase Scripting\| Script]]:
	** '''Phrase Pattern (.xrnz)''' - A phrase ~~preset~~ is an ~~XML~~ file describing the number of lines, columns and other settings (loop, tempo etc.) that make up a single phrase.		** '''Phrase Pattern (.xrnz)''' - A ‘Pattern’ phrase is an .xml file describing the number of lines, columns and other settings – such as loop, tempo etc. – that make up a single phrase.
	** '''Phrase Script (.lua)''' - A ~~script~~ preset is a ~~LUA~~ file ~~that simply contains~~ the script itself.		** '''Phrase Script (.lua)''' - A phrase 'Script' preset is simply a .lua file of the script itself.
	* '''Keyzones (.sfz)''' - ~~A multi~~-~~sample preset is~~ an .sfz ~~soundfont file~~, ~~an open standard~~ format for ~~describing musical instruments~~.		* '''Keyzones (.sfz)''' - This preset uses the open-source format of .sfz to store both the Keyzones data and all of an instrument’s samples. This provides access to a huge resource, since .sfz files created in external sources can be imported, and the popular Sound Font format .sf2 can be easily converted into .sfz – watch the [https://youtu.be/EnOXlgr6azc ‘Keyzones’ video] for more details.
	* '''Waveform (.flac)''' - Waveform presets are just samples stored as [https://xiph.org/flac/ .flac] files.		* '''Waveform (.flac)''' - Waveform presets are just individual samples stored as [https://xiph.org/flac/ .flac] files.
	* '''Modulation (.xrno)''' - A Modulation Set preset is ~~a collection~~ of modulation envelopes ~~that affect~~ various sample domains (volume, panning, etc~~.). The preset itself is a simple XML file~~.		* '''Modulation (.xrno)''' - A Modulation Set preset is an .xml file of the [[Sampler_Modulation\|modulation envelopes]] built within the various sample domains: volume, panning, etc.
	* '''Effects (.xrnt)''' - An Effect Chain preset ~~describes~~ the effect devices and parameter values that make up an effect-chain. ~~The~~ preset ~~itself~~ is ~~a simple XML file~~.		* '''Effects (.xrnt)''' - An [[Effect_Chains\|Effect Chain]] preset is an .xml file of the effect devices and parameter values that make up an effect chain. Note that although the preset menu is for [[Instruments]], the effect chains are compatible with [[Pattern_Editor#Track_Types\|track]] effects.

	A library can also contain two other file types:		A library can also contain two other file types:

	* '''Effect-Devices (.xrdp)''' - An Effect-Device preset defines the parameters of a single effect device. This can be any of the ~~regular~~ devices or a [[Doofer,_Splitter_%26_Notepad\|Doofer/Splitter]] ~~(a special combination of other devices)~~.		* '''Effect-Devices (.xrdp)''' - An [[Effect_Chains#Storing/Recalling_Effect_Presets\|Effect Device preset]] is an .xml file that defines the parameters of a single effect device. This can be any of the singular devices or particular combinations contained within a [[Doofer,_Splitter_%26_Notepad\|Doofer or Splitter]].
	* '''Themes (.xrnc)''' - Themes are alternative visual styles for the interface and are stored as simple ~~XML~~ files. New Themes can be created, or existing ones edited, in the [[Preferences#Theme\|Themes tab]] of the preferences menu.		* '''Themes (.xrnc)''' - Themes are alternative visual styles for the interface and are stored as simple .xml files. New Themes can be created, or existing ones edited, in the [[Preferences#Theme\|Themes tab]] of the preferences menu.

Achenar at 18:21, 8 July 2025

2025-07-08T18:21:20Z

← Older revision		Revision as of 18:21, 8 July 2025
Line 3:		Line 3:
	A library acts as a container for other presets, stored in the file format .xrnl, which is easily installed via drag and drop. Once installed, the library’s contents will be available to use through the preset menu(s). Since a library’s contents can be many different things, the installer will helpfully tell you what was installed - whether it was a bunch of new instruments, some multi-sample presets, or perhaps a collection of effect chains.		A library acts as a container for other presets, stored in the file format .xrnl, which is easily installed via drag and drop. Once installed, the library’s contents will be available to use through the preset menu(s). Since a library’s contents can be many different things, the installer will helpfully tell you what was installed - whether it was a bunch of new instruments, some multi-sample presets, or perhaps a collection of effect chains.

	You may find it useful to watch [https://youtu.be/3V4f6oGcq8E a short video on this subject].		You may find it useful to watch [https://youtu.be/3V4f6oGcq8E a short video on this subject.]

	[[Image:dux1.4_presetbrowser.png]]		[[Image:dux1.4_presetbrowser.png]]
Line 99:		Line 99:
	: ''It contains Instrument presets.''		: ''It contains Instrument presets.''

	If the installer encountered a problem you will be provided with a error message containing information that will be useful in tracking down the problem.		If the installer encountered a problem you will be provided with an error message containing information that will be useful in tracking down the problem.

Achenar at 12:25, 8 July 2025

2025-07-08T12:25:23Z

← Older revision		Revision as of 12:25, 8 July 2025
Line 31:		Line 31:
	A library can also contain two other file types:		A library can also contain two other file types:

	* '''Effect-Devices (.xrdp)''' - An Effect-Device preset defines the parameters of a single effect device. This can be any of the regular devices or a [[~~Doofers~~\|Doofer]] (a special combination of other devices).		* '''Effect-Devices (.xrdp)''' - An Effect-Device preset defines the parameters of a single effect device. This can be any of the regular devices or a [[Doofer,_Splitter_%26_Notepad\|Doofer/Splitter]] (a special combination of other devices).
	* '''Themes (.xrnc)''' - Themes are alternative visual styles for the interface and are stored as simple XML files. New Themes can be created, or existing ones edited, in the [[Preferences#Theme\|Themes tab]] of the preferences menu.		* '''Themes (.xrnc)''' - Themes are alternative visual styles for the interface and are stored as simple XML files. New Themes can be created, or existing ones edited, in the [[Preferences#Theme\|Themes tab]] of the preferences menu.

Achenar at 11:36, 8 July 2025

2025-07-08T11:36:33Z

← Older revision		Revision as of 11:36, 8 July 2025
Line 5:		Line 5:
	You may find it useful to watch [https://youtu.be/3V4f6oGcq8E a short video on this subject].		You may find it useful to watch [https://youtu.be/3V4f6oGcq8E a short video on this subject].

	[[Image:dux1.~~1_presetbrowser~~.png]]		[[Image:dux1.4_presetbrowser.png]]


Line 11:		Line 11:

	* '''Windows:''' HOME/[My ]Documents/Renoise		* '''Windows:''' HOME/[My ]Documents/Renoise
	* '''~~MacOS~~:''' HOME/Documents/Renoise		* '''macOS:''' HOME/Documents/Renoise
	* '''Linux:''' HOME/Renoise		* '''Linux:''' HOME/Renoise

Line 19:		Line 19:
	[[Instruments]] are constructed from a variety of parts: [[Phrase Editor\|Phrases]], [[Keyzones]], [[Waveform\|Waveforms]], [[Modulation]] and [[Effects]]. Specific preset types for each of these sections are available from a drop-down menu at the top right corner, where you can load, save, import and export. This allows an existing instrument to load the various presets into their specific sections without overwriting the whole instrument. A library can contain any of the file types associated with these sections:		[[Instruments]] are constructed from a variety of parts: [[Phrase Editor\|Phrases]], [[Keyzones]], [[Waveform\|Waveforms]], [[Modulation]] and [[Effects]]. Specific preset types for each of these sections are available from a drop-down menu at the top right corner, where you can load, save, import and export. This allows an existing instrument to load the various presets into their specific sections without overwriting the whole instrument. A library can contain any of the file types associated with these sections:

	[[Image: 3.~~1_specificpresettypes~~.png]]		[[Image:3.5_specificpresettypes.png]]

	* '''Phrases (.xrnz)''' - A phrase preset is an XML file describing the number of lines, columns and other settings (loop, tempo etc.) that make up a single phrase.		* '''Phrases''' - The Phrase Editor uses two different presets, depending on whether the selected phrase’s type is a [[Phrase Editor\|Pattern]] or a [[Phrase Editor#Phrase Scripting\| Script]]:
			** '''Phrase Pattern (.xrnz)''' - A phrase preset is an XML file describing the number of lines, columns and other settings (loop, tempo etc.) that make up a single phrase.
			** '''Phrase Script (.lua)''' - A script preset is a LUA file that simply contains the script itself.
	* '''Keyzones (.sfz)''' - A multi-sample preset is an .sfz soundfont file, an open standard format for describing musical instruments.		* '''Keyzones (.sfz)''' - A multi-sample preset is an .sfz soundfont file, an open standard format for describing musical instruments.
	* '''Waveform (.flac)''' - Waveform presets are just samples stored as [https://xiph.org/flac/ .flac] files.		* '''Waveform (.flac)''' - Waveform presets are just samples stored as [https://xiph.org/flac/ .flac] files.

Achenar at 17:05, 17 March 2022

2022-03-17T17:05:20Z

← Older revision		Revision as of 17:05, 17 March 2022
Line 11:		Line 11:

	* '''Windows:''' HOME/[My ]Documents/Renoise		* '''Windows:''' HOME/[My ]Documents/Renoise
	* '''~~OSX~~:''' HOME/Documents/Renoise		* '''MacOS:''' HOME/Documents/Renoise
	* '''Linux:''' HOME/Renoise		* '''Linux:''' HOME/Renoise

Achenar: /* XRNL Library Creation */

2019-10-07T13:18:50Z

XRNL Library Creation

← Older revision		Revision as of 13:18, 7 October 2019
Line 35:		Line 35:
	== XRNL Library Creation ==		== XRNL Library Creation ==

	The easiest way to build your own library is to save presets from inside Renoise~~, creating one based on an existing user library~~.		The easiest way to build your own library is to create a copy of an existing user library, save presets to it from inside Renoise and then do the file/folder organisation externally.

	=== Build The Collection ===		=== Build The Collection ===
Line 45:		Line 45:
	: + Instruments		: + Instruments

	Note that these folders are created automatically as you save a preset. ~~Inside these folders, you can organize~~ presets in folders ~~too. This is supported and shown in the Renoise/Redux interface~~, but ~~you can't reorganize or move files around from there - you need~~ to ~~do this~~ from within your OS explorer/finder window. Any changes performed ~~here should~~ automatically be reflected in the Renoise user interface.		Note that these folders are created automatically as you save a preset. It's possible to move presets around or reorganise them into sub-folders, but this needs to be done from within your OS explorer/finder window. Any changes performed there will automatically be reflected in the Renoise user interface.

	So, after a bit of customization your file structure might now look like this (with folders expanded):		So, after a bit of customization your file structure might now look like this (with folders expanded):
Line 75:		Line 75:
	The only thing that is important to get right is the name - it needs to follow a certain naming convention, in the form `abc.def.ghi`. For example `com.renoise.elements` for one of our Renoise-published libraries, but you can use whatever name you like as long as it has those three parts.		The only thing that is important to get right is the name - it needs to follow a certain naming convention, in the form `abc.def.ghi`. For example `com.renoise.elements` for one of our Renoise-published libraries, but you can use whatever name you like as long as it has those three parts.

	By now, the file structure might look like this:		By now the file structure might look like this:

	: + Samples		: + Samples
Line 82:		Line 82:
	: manifest.xml		: manifest.xml

	You can even add additional files if you wish to - perhaps a PDF document, or a 'readme'. These files will not be useful to Renoise, but will still be installed on the user's machine as part of the library.		You can even add additional files if you wish to - perhaps a PDF document or a 'readme'. These files will not be useful to Renoise, but will still be installed on the user's machine as part of the library.

	=== Creating The Library File ===		=== Creating The Library File ===
Line 90:		Line 90:
	=== Test Install ===		=== Test Install ===

	You can now install the library to check that everything has worked by simply dragging the file on top of the Renoise window. To install in Redux, drag the file on top of the plugin window, or click the load button [[Image:dux1.0_presetselector-load.png\|baseline]] of the [[Instruments#Preset Selector\|Preset Selector]].		You can now install the library to check that everything has worked by simply dragging the file on top of the Renoise window. To install in Redux either drag the file on top of the plugin window or click the load button [[Image:dux1.0_presetselector-load.png\|baseline]] of the [[Instruments#Preset Selector\|Preset Selector]].

	A successful install should result in a message:		A successful install should result in a message like this:

	: Library 'xxx' was successfully installed.		: ''Library 'xxx' was successfully installed.''
	: It contains Instrument presets.		: ''It contains Instrument presets.''

	If the installer encountered a problem you will be provided with a error message containing information that will be useful in tracking down the problem.		If the installer encountered a problem you will be provided with a error message containing information that will be useful in tracking down the problem.

Achenar: /* XRNL Library Creation */

2019-10-07T11:19:35Z

XRNL Library Creation

← Older revision		Revision as of 11:19, 7 October 2019
Line 35:		Line 35:
	== XRNL Library Creation ==		== XRNL Library Creation ==

	The easiest way to build ~~up a~~ library is to save presets from inside Renoise, creating ~~a library~~ based on an existing user library.		The easiest way to build your own library is to save presets from inside Renoise, creating one based on an existing user library.

	=== Build The Collection ===		=== Build The Collection ===
Line 41:		Line 41:
	Libraries are laid out in the same way as the user library. For example, it might have the following structure:		Libraries are laid out in the same way as the user library. For example, it might have the following structure:

	: - Samples		: + Samples
	: - Multi-Samples		: + Multi-Samples
	: - Instruments		: + Instruments

	Note that these folders are created automatically, as you save a preset. Inside these folders, you can organize presets in folders too. This is supported and shown in the Renoise/Redux interface, but you can't reorganize, move files around from there - you need to ~~open an~~ explorer/finder window ~~to organize your files~~. Any changes performed here should automatically be reflected in the Renoise user interface.		Note that these folders are created automatically as you save a preset. Inside these folders, you can organize presets in folders too. This is supported and shown in the Renoise/Redux interface, but you can't reorganize or move files around from there - you need to do this from within your OS explorer/finder window. Any changes performed here should automatically be reflected in the Renoise user interface.

	So, after a bit of customization your file structure might now look like this (with folders expanded):		So, after a bit of customization your file structure might now look like this (with folders expanded):

	: - Samples		: + Samples
	:: - Ambience		:: - Ambience
	:: - Channel		:: - Channel
Line 62:		Line 62:
	=== Add A Manifest ===		=== Add A Manifest ===

	Once you feel the content is ready to be exported, add a manifest to the root folder (use a basic text editor such as Notepad+ and copy the following text as a starting point).		Once you feel the content is ready to be exported, add a manifest to the root folder (use a basic text editor such as Notepad and copy the following text as a starting point).

	<pre><?xml version="1.0" encoding="UTF-8"?>		<pre><?xml version="1.0" encoding="UTF-8"?>
Line 73:		Line 73:
	</RenoiseContentLibrary></pre>		</RenoiseContentLibrary></pre>

	The only thing that is ~~really~~ important to get right is the name - it needs to follow a certain naming convention, in the form `abc.def.ghi`. For example `com.renoise.elements` for one of our Renoise-published libraries, but you can use whatever name you like as long as it has those three parts.		The only thing that is important to get right is the name - it needs to follow a certain naming convention, in the form `abc.def.ghi`. For example `com.renoise.elements` for one of our Renoise-published libraries, but you can use whatever name you like as long as it has those three parts.

	By now, the file structure might look like this:		By now, the file structure might look like this:
Line 82:		Line 82:
	: manifest.xml		: manifest.xml

	You can even add additional files if you wish to - perhaps ~~you have~~ a PDF document, or a 'readme' ~~of some kind?~~ These files will not be useful to Renoise, but will still be installed on the user ~~harddrive~~ as part of the library.		You can even add additional files if you wish to - perhaps a PDF document, or a 'readme'. These files will not be useful to Renoise, but will still be installed on the user's machine as part of the library.

	=== Creating The Library File ===		=== Creating The Library File ===

	Using a zip archive utility (on ~~windows~~, ~~7zip~~ is recommended), you first compress the ''inside'' of the root folder, and then assign it the name provided in the manifest plus the Renoise library file extension~~, `~~.xrnl`.		Using a zip archive utility (on Windows, [https://www.7-zip.org 7Zzip] is recommended), you first compress the ''inside'' of the root folder, and then assign it the name provided in the manifest plus the Renoise library file extension .xrnl. So, in the case of our example pack, the file name would become `org.username.examplepack.xrnl`

	So, in the case of our example pack, the file name would become `org.username.examplepack.xrnl`

	=== Test Install ===		=== Test Install ===

	~~If you want, you~~ can now install the library to check that everything has worked~~. To install in Renoise, drag~~ the file on top of the Renoise window. To install in Redux, drag the file on top of the plugin window, or click the load button.		You can now install the library to check that everything has worked by simply dragging the file on top of the Renoise window. To install in Redux, drag the file on top of the plugin window, or click the load button [[Image:dux1.0_presetselector-load.png\|baseline]] of the [[Instruments#Preset Selector\|Preset Selector]].

	A successful install should result in a message ~~such as~~:		A successful install should result in a message:

	: Library 'xxx' was successfully installed.		: Library 'xxx' was successfully installed.
	: It contains Instrument presets.		: It contains Instrument presets.

	If the installer encountered a problem~~, hopefully~~ you will ~~get~~ a ~~useful~~ error message that ~~can help to track~~ down the problem.		If the installer encountered a problem you will be provided with a error message containing information that will be useful in tracking down the problem.

Achenar: /* Libraries & Presets */

2019-08-27T15:59:22Z

Libraries & Presets

← Older revision		Revision as of 15:59, 27 August 2019
Line 5:		Line 5:
	You may find it useful to watch [https://youtu.be/3V4f6oGcq8E a short video on this subject].		You may find it useful to watch [https://youtu.be/3V4f6oGcq8E a short video on this subject].

	[[Image:dux1.~~0_presetbrowser~~.png]]		[[Image:dux1.1_presetbrowser.png]]

Achenar: /* Libraries & Presets */

2019-06-10T16:10:34Z

Libraries & Presets

← Older revision		Revision as of 16:10, 10 June 2019
Line 31:		Line 31:
	* '''Effect-Devices (.xrdp)''' - An Effect-Device preset defines the parameters of a single effect device. This can be any of the regular devices or a [[Doofers\|Doofer]] (a special combination of other devices).		* '''Effect-Devices (.xrdp)''' - An Effect-Device preset defines the parameters of a single effect device. This can be any of the regular devices or a [[Doofers\|Doofer]] (a special combination of other devices).
	* '''Themes (.xrnc)''' - Themes are alternative visual styles for the interface and are stored as simple XML files. New Themes can be created, or existing ones edited, in the [[Preferences#Theme\|Themes tab]] of the preferences menu.		* '''Themes (.xrnc)''' - Themes are alternative visual styles for the interface and are stored as simple XML files. New Themes can be created, or existing ones edited, in the [[Preferences#Theme\|Themes tab]] of the preferences menu.


	== XRNL Library Creation ==		== XRNL Library Creation ==