Muse2ps - Revision history

Craig: /* Feature requests and bug reports */

2025-04-13T05:58:05Z

Feature requests and bug reports

← Older revision		Revision as of 05:58, 13 April 2025
Line 573:		Line 573:

	See the page: [[Muse2ps feature requests and bug reports]].		See the page: [[Muse2ps feature requests and bug reports]].

			== Link ==

			Shortcut to this page: https://muse2ps.ccarh.org

Craig: /* Overview */

2024-10-11T00:27:04Z

Overview

← Older revision		Revision as of 00:27, 11 October 2024
Line 2:		Line 2:

	== Overview ==		== Overview ==


	The <b>muse2ps</b> program is a command-line version of the [[autoset]], [[mskpage]] and [[pspage]] programs which are usually run within the [[dmuse]] editor using the built-in [[zbex language]] interpreter. The ''muse2ps'' program reads MuseData [[stage2]] data or [[page file]] data from standard input and converts them into PostScript data representing graphical musical notation which is sent to standard output. The following diagram illustrates the flow of data through ''muse2ps'':		The <b>muse2ps</b> program is a command-line version of the [[autoset]], [[mskpage]] and [[pspage]] programs which are usually run within the [[dmuse]] editor using the built-in [[zbex language]] interpreter. The ''muse2ps'' program reads MuseData [[stage2]] data or [[page file]] data from standard input and converts them into PostScript data representing graphical musical notation which is sent to standard output. The following diagram illustrates the flow of data through ''muse2ps'':

Craig at 00:26, 11 October 2024

2024-10-11T00:26:54Z

← Older revision		Revision as of 00:26, 11 October 2024
Line 2:		Line 2:

	== Overview ==		== Overview ==


	The <b>muse2ps</b> program is a command-line version of the [[autoset]], [[mskpage]] and [[pspage]] programs which are usually run within the [[dmuse]] editor using the built-in [[zbex language]] interpreter. The ''muse2ps'' program reads MuseData [[stage2]] data or [[page file]] data from standard input and converts them into PostScript data representing graphical musical notation which is sent to standard output. The following diagram illustrates the flow of data through ''muse2ps'':		The <b>muse2ps</b> program is a command-line version of the [[autoset]], [[mskpage]] and [[pspage]] programs which are usually run within the [[dmuse]] editor using the built-in [[zbex language]] interpreter. The ''muse2ps'' program reads MuseData [[stage2]] data or [[page file]] data from standard input and converts them into PostScript data representing graphical musical notation which is sent to standard output. The following diagram illustrates the flow of data through ''muse2ps'':

Craig: /* Multiple Music Page files */

2024-04-26T07:47:13Z

Multiple Music Page files

← Older revision		Revision as of 07:47, 26 April 2024
Line 466:		Line 466:
	</source>		</source>

	N.B.: ~~Probably two~~ slashes also need to be added at the end of the last page; otherwise, it will not print:		N.B.: Two slashes also need to be added at the end of the last page; otherwise, it will not print:

	//		//

Craig: /* Multiple Music Page files */

2024-04-26T07:46:34Z

Multiple Music Page files

← Older revision		Revision as of 07:46, 26 April 2024
Line 456:		Line 456:
	=== Multiple Music Page files ===		=== Multiple Music Page files ===

	When concatenating multiple Music Page (~~MPG~~) files, separate each file's content with a line with the single capital letter "P" on it. Example of how to do this on the command line, creating a PDF file:		When concatenating multiple Music Page (PAG) files, separate each file's content with a line with the single capital letter "P" on it. Example of how to do this on the command line, creating a PDF file:

	<source lang="bash">		<source lang="bash">

Craig: /* Inputting MPG data (adding a title) */

2024-04-26T07:45:55Z

Inputting MPG data (adding a title)

← Older revision		Revision as of 07:45, 26 April 2024
Line 143:		Line 143:
	* <tt>=l3000</tt>: Set the vertical printable region to 10 inches.		* <tt>=l3000</tt>: Set the vertical printable region to 10 inches.

	=== Inputting ~~MPG~~ data (adding a title) ===		=== Inputting PAG data (adding a title) ===

	The extracted [[music page]] data from the previous section can be edited (such as to add a title) and then can be reprocessed by ''muse2ps'' to generate PostScript output:		The extracted [[music page]] data from the previous section can be edited (such as to add a title) and then can be reprocessed by ''muse2ps'' to generate PostScript output:

Craig at 07:45, 26 April 2024

2024-04-26T07:45:34Z

← Older revision		Revision as of 07:45, 26 April 2024
Line 126:		Line 126:
	</center>		</center>

	=== Extracting ~~MPG~~ intermediate data ===		=== Extracting PAG intermediate data ===

	When a MuseData [[stage2]] file is converted into graphical music notation as PostScript output from ''muse2ps'', it will pass through two data transformation steps. The first step is a conversion from [[stage2]] data into non-page-specific [[i-files]] which is accomplished with the [[autoset]] component. Then these "non-page-specific" [[i-files]] are converted into "page-specific" [[page files\|i-files]] (or Music Page (MPG) files) which describe the precise position of musical elements on each page of typeset music. This [[music page]] data can be extracted from the program surreptitiously by using the "=P" option. This will cause the [[MPG]] data to be embedded in comments within the PostScript output. Each page of MPG data will be stored in a sequence of comments starting with "<tt>%=BeginMPGData: 1</tt>", where <tt>1</tt> is the data for page one. And each page of MPG data is ended by the comment <tt>"%=EndMPGData: 1"</tt>.		When a MuseData [[stage2]] file is converted into graphical music notation as PostScript output from ''muse2ps'', it will pass through two data transformation steps. The first step is a conversion from [[stage2]] data into non-page-specific [[i-files]] which is accomplished with the [[autoset]] component. Then these "non-page-specific" [[i-files]] are converted into "page-specific" [[page files\|i-files]] (or Music Page (MPG) files) which describe the precise position of musical elements on each page of typeset music. This [[music page]] data can be extracted from the program surreptitiously by using the "=P" option. This will cause the [[MPG]] data to be embedded in comments within the PostScript output. Each page of MPG data will be stored in a sequence of comments starting with "<tt>%=BeginMPGData: 1</tt>", where <tt>1</tt> is the data for page one. And each page of MPG data is ended by the comment <tt>"%=EndMPGData: 1"</tt>.
Line 370:		Line 370:

	\|- valign="top"		\|- valign="top"
	\| {{anchor\|p_option}}<b>=p</b> \|\| The source is a concatenated set of page specific i-files (also called .~~mpg~~ files), not a set of MuseData files.		\| {{anchor\|p_option}}<b>=p</b> \|\| The source is a concatenated set of page specific i-files (also called .pag files), not a set of MuseData files.

	\|- valign="top"		\|- valign="top"

Edc: /* Zbex programs */

2021-03-30T18:57:56Z

Zbex programs

← Older revision		Revision as of 18:57, 30 March 2021
Line 564:		Line 564:
	== Zbex programs ==		== Zbex programs ==

	In the muse2ps source code directory, the sub-directory <tt>zprogs</tt> contains the [[zbex]] programs used to generate the file zfun32.c. Most necessary files needed to create [http://www.ccarh.org/software/muse2ps/muse2ps/zfun32.c zfun32.c] are in that directory, but perhaps not all of them. These programs are not used directly by muse2ps, but are compiled into zbex executable code within zfun32.c. The muse2ps is essentially a non-interactive version of [[dmuse]] (see http://dmuse.ccarh.org). The [[dmuse]] program is a text editor which also has a built-in [[zbex]] language interpreter and graphical music display capabilities. The interpreter portion of [[dmuse]] has been extracted for non-interactive use in muse2ps.		In the muse2ps source code directory, the sub-directory <tt>zprogs</tt> contains the [[zbex]] programs used to generate the file zfun32.c. Most necessary files needed to create [http://www.ccarh.org/software/muse2ps/muse2ps/zfun32.c zfun32.c] are in that directory, but perhaps not all of them. These programs are not used directly by muse2ps, but are compiled into zbex executable code within zfun32.c. The muse2ps program is essentially a non-interactive version of [[dmuse]] (see http://dmuse.ccarh.org). The [[dmuse]] program is a text editor which also has a built-in [[zbex]] language interpreter and graphical music display capabilities. The interpreter portion of [[dmuse]] has been extracted for non-interactive use in muse2ps.

	== Examples ==		== Examples ==

Edc: /* Humdrum interface */

2021-03-30T18:49:36Z

Humdrum interface

← Older revision		Revision as of 18:49, 30 March 2021
Line 557:		Line 557:
	</table>		</table>

	Images can be generated from Humdrum data online by pasting/typing data into the [http://kern.humdrum.org/cgi-bin/kern/kseditor Humdrum online editor]. For example, copy and paste the above Humdrum data into the left black box on the Humdrum online editor page, ~~and the~~ click on the red "Generate" button to produce an image of the graphical music using the default settings.		Images can be generated from Humdrum data online by pasting/typing data into the [http://kern.humdrum.org/cgi-bin/kern/kseditor Humdrum online editor]. For example, copy and paste the above Humdrum data into the left black box on the Humdrum online editor page, then click on the red "Generate" button to produce an image of the graphical music using the default settings.

	Here is the intermediate MuseData which is passed between [http://extra.humdrum.org/man/hum2muse hum2muse] and muse2ps: [[Media:beethoven-kern.md2 \| beethoven.md2]]. Try copying / pasting		Here is the intermediate MuseData which is passed between [http://extra.humdrum.org/man/hum2muse hum2muse] and muse2ps: [[Media:beethoven-kern.md2 \| beethoven.md2]]. Try copying / pasting

Edc: /* Creating images */

2021-03-30T18:31:11Z

Creating images

← Older revision		Revision as of 18:31, 30 March 2021
Line 505:		Line 505:
	== Creating images ==		== Creating images ==

	Graphical images can be created in various ways. A good method is to convert PostScript output from muse2ps to a bitmap image with the unix command-line program pstopnm. For smaller examples and converting to other ~~images formtas~~, Imagemagick's convert is another command-line which is useful. Both pstopnm and convert are often pre-installed on linux computers, and both are available for free on the internet. They should also work with OS X, and can be used in MS Windows using [http://www.cygwin.com cygwin].		Graphical images can be created in various ways. A good method is to convert PostScript output from muse2ps to a bitmap image with the unix command-line program pstopnm. For smaller examples and converting to other image formats, Imagemagick's convert is another command-line program which is useful. Both pstopnm and convert are often pre-installed on linux computers, and both are available for free on the internet. They should also work with OS X, and can be used in MS Windows using [http://www.cygwin.com cygwin].

	To create an image pipe the output from muse2ps into pstopnm, and convert to a bitmapped image at 300 dots per inch. Next pipe the resulting image to convert for further processing. In the following example, the image is first trimmed from a full page to just the area which contains the printed music, then the image is resized to 33% of the original size for use on the web, and saved into a PNG file.		To create an image, pipe the output from muse2ps into pstopnm, and convert to a bitmapped image at 300 dots per inch. Next pipe the resulting image to convert for further processing. In the following example, the image is first trimmed from a full page to just the area which contains the printed music, then the image is resized to 33% of the original size for use on the web, and saved into a PNG file.

	cat [[Media:scale.md2\|scale.md2]] \| muse2ps \| pstopnm -dpi=300 \| \		cat [[Media:scale.md2\|scale.md2]] \| muse2ps \| pstopnm -dpi=300 \| \
Line 533:		Line 533:
	=== Images for printed publications ===		=== Images for printed publications ===

	To insert musical examples in a Microsoft or similar word processing program, do not resize the image, but leave it at the 300 dots per inch size of the original. Then you can rescale the image in the word processor as necessary. This will optimize the quality of the image in the final printout from the word processor.		To insert musical examples in a Microsoft or similar word-processing program, do not resize the image, but leave it at the 300 dots per inch size of the original. Then you can rescale the image in the word processor as necessary. This will optimize the quality of the image in the final printout from the word processor.

	cat [[Media:scale.md2\|scale.md2]] \| muse2ps \| pstopnm -dpi=300 \| \		cat [[Media:scale.md2\|scale.md2]] \| muse2ps \| pstopnm -dpi=300 \| \