WebHelp:Basic Concepts/4.0 - Revision history

Lowlander at 18:17, 23 January 2012

2012-01-23T18:17:50Z

← Older revision		Revision as of 18:17, 23 January 2012
Line 305:		Line 305:

	'''Notes'''		'''Notes'''
	* ~~Alac~~ isn't supported by MediaMonkey yet		* ALAC isn't supported by MediaMonkey yet

Lowlander at 18:17, 23 January 2012

2012-01-23T18:17:32Z

← Older revision		Revision as of 18:17, 23 January 2012
Line 121:		Line 121:
	\| width="14%" \| -		\| width="14%" \| -
	\|-		\|-
	\| width="14%" \| ALAC		\| width="14%" \| ALAC *
	\| width="14%" \| lossless		\| width="14%" \| lossless
	\| width="14%" \| ~58%		\| width="14%" \| ~58%
Line 303:		Line 303:
	Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able to play content from a Media Server. MediaMonkey is both a DLNA server (it can serve files to DLNA clients), and a DLNA client (it can browse other DLNA servers).		Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able to play content from a Media Server. MediaMonkey is both a DLNA server (it can serve files to DLNA clients), and a DLNA client (it can browse other DLNA servers).

	~~<br>~~
			'''Notes'''
			* Alac isn't supported by MediaMonkey yet


	'''Related Information:'''		'''Related Information:'''

Rusty: /* Media Streaming (UPnP / DLNA) */

2011-06-12T03:28:22Z

Media Streaming (UPnP / DLNA)

← Older revision		Revision as of 03:28, 12 June 2011
Line 299:		Line 299:
	== Media Streaming (UPnP / DLNA) ==		== Media Streaming (UPnP / DLNA) ==

	If a ~~huge~~ library of media files are stored on one machine, it ~~would be great if~~ that library ~~could~~ be ~~accessed and played~~ from other devices without having to sync the files ~~between the two devices~~. That's what UPnP / DLNA is designed to do. A DLNA ~~client is able to browse files that exist on~~ a DLNA ~~server and~~ '~~stream~~' ~~them~~ on demand. ~~Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able~~ to ~~play~~ content ~~from a Media Server.~~		If a library of media files are stored on one machine, it's usually desirable for that library to be accessible / playable from other devices without having to sync the files. That's what UPnP / DLNA is designed to do: A DLNA 'Server' shares the contents of a library with DLNA 'clients' that play the files on demand. Streaming refers to the fact that content begins playing on the client without first having downloaded the entire file.

	~~MediaMonkey is both a DLNA~~ client ~~(it can browse other DLNA servers) and a DLNA server (it can serve files to DLNA clients)~~.

			Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able to play content from a Media Server. MediaMonkey is both a DLNA server (it can serve files to DLNA clients), and a DLNA client (it can browse other DLNA servers).

	<br>		<br>

Rusty: /* Digital Rights Management */

2011-06-12T03:20:35Z

Digital Rights Management

← Older revision		Revision as of 03:20, 12 June 2011
Line 214:		Line 214:

	MediaMonkey supports WMA DRM up to version 9, and allows playback of DRMed M4P tracks if Quicktime is installed.		MediaMonkey supports WMA DRM up to version 9, and allows playback of DRMed M4P tracks if Quicktime is installed.

			<br>

	'''Related Information:'''		'''Related Information:'''

	[http://www.eff.org/IP/DRM/ Electronic Frontier Foundation DRM Page]		[http://www.eff.org/IP/DRM/ Electronic Frontier Foundation DRM Page]

	== Tags ==		== Tags ==

Rusty: /* Ripping & Digital Audio Compression Formats */

2011-06-12T03:20:05Z

Ripping & Digital Audio Compression Formats

← Older revision		Revision as of 03:20, 12 June 2011
Line 200:		Line 200:
	As for video, AVI (MPEG4) and MP4 (H264) are most commonly used formats, though WMV is very common as well.<br>		As for video, AVI (MPEG4) and MP4 (H264) are most commonly used formats, though WMV is very common as well.<br>

	~~<br>~~

	~~<br>~~

	'''Related Information:'''		'''Related Information:'''

Rusty at 17:32, 7 June 2011

2011-06-07T17:32:01Z

← Older revision		Revision as of 17:32, 7 June 2011
Line 304:		Line 304:
	MediaMonkey is both a DLNA client (it can browse other DLNA servers) and a DLNA server (it can serve files to DLNA clients).		MediaMonkey is both a DLNA client (it can browse other DLNA servers) and a DLNA server (it can serve files to DLNA clients).

			<br>

	'''Related Information:'''		'''Related Information:'''

	[[WebHelp:~~Setting_UPnP~~/~~DLNA_Media_Servers~~/4.0\|~~Configuring UPnP / DLNA~~]][[{{WebHelp:Links\|About Track Properties}}\|<br>]]		[[WebHelp:Setting UPnP/DLNA Media Servers/4.0\|Streaming your Library to other Devices]][[{{WebHelp:Links\|About Track Properties}}\|<br>]]

	{{WebHelpFooter}}		{{WebHelpFooter}}

Rusty: /* Media Streaming (UPnP / DLNA) */

2011-06-07T17:31:25Z

Media Streaming (UPnP / DLNA)

← Older revision		Revision as of 17:31, 7 June 2011
Line 300:		Line 300:
	== Media Streaming (UPnP / DLNA) ==		== Media Streaming (UPnP / DLNA) ==

	If a huge library of media files are stored on one machine, it would be great if that library could be accessed and played from other devices without having to sync the files between the two devices. That's what UPnP / DLNA is designed to do. A DLNA client is able to browse files that exist on a DLNA server and 'stream' them on demand. Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able to play content from a Media Server.		If a huge library of media files are stored on one machine, it would be great if that library could be accessed and played from other devices without having to sync the files between the two devices. That's what UPnP / DLNA is designed to do. A DLNA client is able to browse files that exist on a DLNA server and 'stream' them on demand. Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able to play content from a Media Server.

	MediaMonkey is both a DLNA client (it can browse other DLNA servers) and a DLNA server (it can serve files to DLNA clients).		MediaMonkey is both a DLNA client (it can browse other DLNA servers) and a DLNA server (it can serve files to DLNA clients).



			'''Related Information:'''

			[[WebHelp:Setting_UPnP/DLNA_Media_Servers/4.0\|Configuring UPnP / DLNA]][[{{WebHelp:Links\|About Track Properties}}\|<br>]]

	{{WebHelpFooter}}		{{WebHelpFooter}}

Rusty at 17:29, 7 June 2011

2011-06-07T17:29:53Z

← Older revision		Revision as of 17:29, 7 June 2011
Line 295:		Line 295:
	[[{{WebHelp:Links\|Volume Leveling}}\|Volume Leveling]]		[[{{WebHelp:Links\|Volume Leveling}}\|Volume Leveling]]

	[http://replaygain.hydrogenaudio.org/outline.html Replay Gain Standard] (by David Robinson).		[http://replaygain.hydrogenaudio.org/outline.html Replay Gain Standard] (by David Robinson).


			== Media Streaming (UPnP / DLNA) ==

			If a huge library of media files are stored on one machine, it would be great if that library could be accessed and played from other devices without having to sync the files between the two devices. That's what UPnP / DLNA is designed to do. A DLNA client is able to browse files that exist on a DLNA server and 'stream' them on demand. Many televisions, game consoles, and Blue Ray players are DLNA clients, and are able to play content from a Media Server.

			MediaMonkey is both a DLNA client (it can browse other DLNA servers) and a DLNA server (it can serve files to DLNA clients).

	{{WebHelpFooter}}		{{WebHelpFooter}}

Rusty at 17:22, 7 June 2011

2011-06-07T17:22:39Z

← Older revision		Revision as of 17:22, 7 June 2011
Line 228:		Line 228:
	MediaMonkey allows you to store all sorts of information about a Track within the Library, and to automatically update tags when changes are made to this information. The rationale for storing the information to both the MediaMonkey Library and to the track tags as well is that:		MediaMonkey allows you to store all sorts of information about a Track within the Library, and to automatically update tags when changes are made to this information. The rationale for storing the information to both the MediaMonkey Library and to the track tags as well is that:

	1) If the Track is shared with an external device such as an MP3 Player or DVD, the tag allows that information to be available via the device (~~assuming~~ the device ~~supports tags~~).		1) If the Track is shared with an external device such as an MP3 Player or DVD, the tag allows that information to be available via the device (Note: some devices (e.g. iPods) ignore most tags and instead rely on direct synchronization of metadata to the device database).

	2) If you wish to use another player or music manager, the tags embedded within your songs can often be read by those applications.		2) If you wish to use another player or music manager, the tags embedded within your songs can often be read by those applications.

Rusty at 17:19, 7 June 2011

2011-06-07T17:19:11Z

← Older revision		Revision as of 17:19, 7 June 2011
Line 234:		Line 234:
	Tags are usually stored in a format that is designed specifically for the file type. e.g. MP3 files usually have ID3 tags wherease OGG files have vorbis tags. What follows is a brief discussion of the different tag formats supported in MediaMonkey:		Tags are usually stored in a format that is designed specifically for the file type. e.g. MP3 files usually have ID3 tags wherease OGG files have vorbis tags. What follows is a brief discussion of the different tag formats supported in MediaMonkey:

	ID3v1: ID3v1 is the lowest common denominator of MP3 tag formats. It stores only a very limited amount of information (e.g. Artist, Title, Album, etc.) however, it is supported almost universally by portable audio players and DVD players.		*ID3v1: ID3v1 is the lowest common denominator of MP3 tag formats. It stores only a very limited amount of information (e.g. Artist, Title, Album, etc.) however, it is supported almost universally by portable audio players and DVD players.
			*ID3V2: ID3v2 tags are also used for MP3 files. They support a much greater range of metadata (information about your music files) than ID3v1, however, some information encoded in ID3v2 tags may not be readable by another application or device that only supports ID3v1. For this reason, it's often a good idea to store music data in both ID3v1 and ID3v2 tags. There are 2 versions of ID3v2 in use today ID3v2.3 and ID3v2.4. MediaMonkey takes the approach of storing most information in a manner that allows it to be read by devices/applications that support either ID3v2.3 or ID3v2.4.
	ID3V2: ID3v2 tags are also used for MP3 files. They support a much greater range of metadata (information about your music files) than ID3v1, however, some information encoded in ID3v2 tags may not be readable by another application or device that only supports ID3v1. For this reason, it's often a good idea to store music data in both ID3v1 and ID3v2 tags. There are 2 versions of ID3v2 in use today ID3v2.3 and ID3v2.4. MediaMonkey takes the approach of storing most information in a manner that allows it to be read by devices/applications that support either ID3v2.3 or ID3v2.4.		*OGG and FLAC files have their own standard tag formats. There's no need for alternatives since the specification supports as much metadata as would be needed in a relatively unambiguos manner.
			*APE and MPC files use APE2 tags, which are designed to resolve some of the difficulties with ID3v2. Although they work very well, there is limited support for them in portable audio players and DVD players.
	files have their own standard tag formats. There's no need for alternatives since the specification supports as much metadata as would be needed in a relatively unambiguos manner.		*WAV/AVI use RIFF tags, an older format that is inconsistently implemented from device to device.  For this reason, AVI files often include a lot of metadata within the filename.
			*WMA/WMV follow a well designed and consistently implemented tagging format.
	APE and MPC files use APE2 tags, which are designed to resolve some of the difficulties with ID3v2. Although they work very well, there is limited support for them in portable audio players and DVD players.

	WAV/AVI use RIFF tags, an older format that is inconsistently implemented.  For this reason, AVI files often include a lot of metadata within the filename.

	WMA/WMV follow a ~~window media~~ format


			<br>

	'''Related Information:'''		'''Related Information:'''

	[[{{WebHelp:Links\|Editing Track Properties}}\|Editing ~~Track~~ Properties]]		[[{{WebHelp:Links\|Editing Track Properties}}\|Editing File Properties]]

	[[{{WebHelp:Links\|About Track Properties}}\|About ~~Track~~ Properties]]		[[{{WebHelp:Links\|About Track Properties}}\|About File Properties]]

	== Volume Leveling ==		== Volume Leveling ==