Audio nodes - Revision history

Karellen: Moved page to Music_nodes

2018-02-13T20:25:01Z

Moved page to Music_nodes

← Older revision		Revision as of 20:25, 13 February 2018
Line 1:		Line 1:
	~~{{mininav\|~~[[~~Music library]]\|[[:Category:Music_library\|Category:Music Library]] }}~~		#REDIRECT [[Music_nodes]]
	~~{{DISPLAYTITLE:Music Nodes}}~~

	<section begin="intro" />Music nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.

	To get full functionality from custom nodes, you need to use a skin that allows you to deploy them as you would like (e.g. latest builds of Aeon Nox). Confluence will show your nodes, but doesn't allow you to decide exactly where.<section end="intro" />

	~~== Audio node editor add-on ==~~
	~~{{main\|Add-on:Library Node Editor}}~~
	~~Users can now create and edit audio nodes from within {{kodi}} thanks to the add-on [[Add-on:Library Node Editor\|Library Node Editor]].~~

	~~== Technical documentation ==~~

	~~=== Default audio nodes ===~~
	~~[[File:defaultaudionodes.jpg\|right\|500px\|frame\|The standard audio nodes]]~~
	~~You can find a copy of the default nodes in one of two ways. One is to download all or some of the nodes you want form https://github.com/xbmc/xbmc/tree/master/system/library .~~

	~~The other way is to copy the Kodi system default nodes that come with Kodi, shown in the table below:~~


	~~{\| border="1" cellpadding="4" class="prettytable"~~
	~~! '''Operative system'''~~
	~~! '''default nodes paths'''~~
	\|-
	~~\|'''Android''' \|\| ?~~
	\|-
	~~\|'''iOS''' - Varied \|\| /Applications/XBMC.frappliance/XBMCData/XBMCHome/system/library/ <br /> /Applications/XBMC.app/XBMCData/XBMCHome/system/library/~~
	\|-
	~~\|'''Linux''' \|\| /usr/share/xbmc/system/library/~~
	\|-
	~~\|'''Mac OS X''' \|\| /Applications/XBMC.app/Contents/Resources/XBMC/system/library/~~
	\|-
	~~\|'''Windows (32bit)''' \|\| C:\Program Files\XBMC\system\library\~~
	\|-
	~~\|'''Windows (64bit)''' \|\| C:\Program Files (x86)\XBMC\system\library\~~
	\|}


	~~To understand nodes a little better, lets take a look at one of the defaults. As an example take a quick look at the ''system/library/music/genres.xml'' node in its simplest form:~~

	~~<syntaxhighlight lang="XML" enclose="div">~~
	~~<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>~~
	~~<node order="1" type="filter" visible="Library.HasContent(Music)">~~
	~~<label>135</label>~~
	~~<icon>DefaultMusicGenres.png</icon>~~
	~~<content>artists</content>~~
	~~<group>genres</group>~~
	~~</node>~~
	~~</syntaxhighlight>~~

	~~As you can see we are using standard XML format here so nothing too complicated.~~

	~~=== XML node components ===~~
	~~'''Order''' = This is the order that you want to show the nodes. Starts at 1 for the top and goes sequentially so 2 will be the next node down.~~

	'''Label''' = This is the text that will show for the node. In this case it is pointing to an ID in the strings.xml file (for translation purposes) It can also just be any String you want, just type some text instead of the id number.

	'''Path''' = This can be any valid Kodi path, such as a file path. This includes internal Kodi DB paths, such as <code>musicdb://recentlyaddedalbums</code>. For more on internal paths, see '''[[Opening Windows and Dialogs]]'''.

	~~'''Icon''' = Pretty self explanatory really, this is the icon that will show when the node is navigated over.~~

	~~== Manually creating or editing a custom node ==~~
	So now we understand how the default nodes work, lets have a look at making a custom node. Custom nodes live inside your [[Userdata]] folder. To create custom nodes, the first step is to copy the whole of the default node file structure from the default library folder to a new folder called ''library'' inside your [[Userdata]] folder.

	~~So, in the case of Windows, copy the 'music' folder from ''C:\Program Files (x86)\XBMC\system\library'' to ''%appdata%\XBMC\userdata\library''.~~

	~~Having copied the node structure, we can now create a new xml file under the relevant directory.~~

	~~In a vanilla install with the confluence skin, custom nodes in ''/music'' will appear in the sub-list of the Music main menu item.~~

	~~For now, we're going to place our node under~~

	~~/userdata/library/music/~~

	~~Let's call it Custom_Genre_Country.xml~~

	~~<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>~~
	~~<node order="10" type="filter">~~
	~~<label>(Custom) Genre Country</label>~~
	~~<content>artists</content>~~
	~~<match>all</match>~~
	~~<rule field="genre" operator="is">~~
	~~<value>Country</value>~~
	~~</rule>~~
	~~</node>~~

	~~As you can see as well as changing the order, we have a few more xml tags this time:~~

	~~'''Type''' = Can be folder or filter, folder requires path to be set.~~

	~~'''Match''' = Specifies how many rules should match. In this case we are matching all rules.~~

	~~'''Rule''' = Any rule created with the smart playlist editor. (See [[Smart Playlists]])~~

	~~'''Limit''' = Limit the number of results returned (can be excluded altogether for unlimited)~~


	~~[[File:Custommusicnodecountry.png\|500px\|Custom node in action]]~~

	~~So there you have it, a simple genre filter for country music.~~

	There are many other rules you can apply, a simple way to find them is to have a go with the smart playlist editor and copy the rule from the resulting xml playlist. There are many possibilities, you could create a rule for any of the database fields such as genre or year, use paths or combine rules together.

	~~A more advanced idea would be a node structure so you could browse your albums by the first letter like this:~~

	~~[[File:Atoznodes.jpg\|500px\|A more advanced custom node]]~~

	~~== See also ==~~
	* [[Custom home items]]
	* [[Smart playlists]]
	* [[Video nodes]]

	~~== Notes ==~~

	~~{{Top}}~~

	~~{{Isengard updated}}~~
	~~[[Category:Music library\|Nodes]]~~
	~~[[Category:Manual~~]]

Davu at 15:21, 13 February 2018

2018-02-13T15:21:15Z

← Older revision		Revision as of 15:21, 13 February 2018
Line 2:		Line 2:
	{{DISPLAYTITLE:Music Nodes}}		{{DISPLAYTITLE:Music Nodes}}

	<section begin="intro" />~~Audio~~ nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.		<section begin="intro" />Music nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.

	To get full functionality from custom nodes, you need to use a skin that allows you to deploy them as you would like (e.g. latest builds of Aeon Nox). Confluence will show your nodes, but doesn't allow you to decide exactly where.<section end="intro" />		To get full functionality from custom nodes, you need to use a skin that allows you to deploy them as you would like (e.g. latest builds of Aeon Nox). Confluence will show your nodes, but doesn't allow you to decide exactly where.<section end="intro" />

Karellen: Update Mininav and Category

2018-02-13T09:03:55Z

Update Mininav and Category

← Older revision		Revision as of 09:03, 13 February 2018
Line 1:		Line 1:
	{{mininav\|[[Music library]]\|[[Music ~~navigation\|Navigation~~]] }}		{{mininav\|[[Music library]]\|[[:Category:Music_library\|Category:Music Library]] }}
			{{DISPLAYTITLE:Music Nodes}}

	<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.		<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.
Line 111:		Line 112:

	== Notes ==		== Notes ==

			{{Top}}

	{{Isengard updated}}		{{Isengard updated}}
			[[Category:Music library\|Nodes]]
	[[Category:Music library]]
	[[Category:Manual]]		[[Category:Manual]]

Ned Scott at 01:16, 24 July 2015

2015-07-24T01:16:21Z

← Older revision		Revision as of 01:16, 24 July 2015
Line 1:		Line 1:
	{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}		{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}
	~~{{isengard}}~~

	<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.		<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.

Ronie: /* Audio node editor add-on */

2015-05-14T22:40:35Z

Audio node editor add-on

← Older revision		Revision as of 22:40, 14 May 2015
Line 7:		Line 7:

	== Audio node editor add-on ==		== Audio node editor add-on ==
	~~Unfortunately there is no way~~ to ~~edit Audio Nodes inside of Kodi yet via an~~ Add-on.		{{main\|Add-on:Library Node Editor}}
			Users can now create and edit audio nodes from within {{kodi}} thanks to the add-on [[Add-on:Library Node Editor\|Library Node Editor]].

	== Technical documentation ==		== Technical documentation ==

Ned Scott: Template will populate the category

2015-05-06T00:16:50Z

Template will populate the category

← Older revision		Revision as of 00:16, 6 May 2015
Line 1:		Line 1:
	{{~~isengard~~\|~~nocat=~~}}		{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}
	{{~~notice\|Kodi v15 (Isengard) final has not been released yet. As such, these changes is for the current Kodi mainline which is a work in progress and are still subject to change.~~}}		{{isengard}}

	~~{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}~~
	<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.		<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.

Line 117:		Line 116:
	[[Category:Music library]]		[[Category:Music library]]
	[[Category:Manual]]		[[Category:Manual]]
	~~[[Category:Isengard feature]]~~

Gamester17 at 14:25, 16 April 2015

2015-04-16T14:25:05Z

← Older revision		Revision as of 14:25, 16 April 2015
Line 117:		Line 117:
	[[Category:Music library]]		[[Category:Music library]]
	[[Category:Manual]]		[[Category:Manual]]
			[[Category:Isengard feature]]

Gamester17 at 14:15, 16 April 2015

2015-04-16T14:15:13Z

← Older revision		Revision as of 14:15, 16 April 2015
Line 1:		Line 1:
	{{~~Isengard~~}}		{{isengard\|nocat=}}
	{{notice\|Kodi v15 (Isengard) final has not been released yet. As such, these changes is for the current Kodi mainline which is a work in progress and are still subject to change.}}		{{notice\|Kodi v15 (Isengard) final has not been released yet. As such, these changes is for the current Kodi mainline which is a work in progress and are still subject to change.}}

Gamester17 at 14:11, 16 April 2015

2015-04-16T14:11:59Z

← Older revision		Revision as of 14:11, 16 April 2015
Line 1:		Line 1:
			{{Isengard}}
			{{notice\|Kodi v15 (Isengard) final has not been released yet. As such, these changes is for the current Kodi mainline which is a work in progress and are still subject to change.}}

	{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}		{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}
	<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.		<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.

Mkortstiege at 20:09, 1 April 2015

2015-04-01T20:09:04Z

← Older revision		Revision as of 20:09, 1 April 2015
Line 1:		Line 1:
	{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}		{{mininav\|[[Music library]]\|[[Music navigation\|Navigation]] }}
	<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of ~~v14~~ Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.		<section begin="intro" />Audio nodes are defined views that are used to organize your media from the music menu. In the past Kodi has had a number of standard nodes such as Artist, Album, Tracks that were hard coded. As of v15 Isengard, Kodi introduces the ability to customize these nodes using an XML file. Using XML files really gives great flexibility in how you display your media and lets you browse large collections quickly. Don't want your country music in your main album node... exclude it. Want a genre in a separate node, create it. Don't like how Top 100 Played is presented, change it.

	To get full functionality from custom nodes, you need to use a skin that allows you to deploy them as you would like (e.g. latest builds of Aeon Nox). Confluence will show your nodes, but doesn't allow you to decide exactly where.<section end="intro" />		To get full functionality from custom nodes, you need to use a skin that allows you to deploy them as you would like (e.g. latest builds of Aeon Nox). Confluence will show your nodes, but doesn't allow you to decide exactly where.<section end="intro" />