Tools & Scripts - Revision history

Mcassera: /* Music Tools and Scripts */

2026-01-30T07:14:52Z

Music Tools and Scripts

← Older revision		Revision as of 03:14, 30 January 2026
Line 94:		Line 94:
	\|-		\|-
	\|GoatTracker		\|GoatTracker
	\|Guide to use [[GoatTracker]] for the F256.		\|[[GoatTracker\|Guide to use GoatTracker for the F256.]]
	\|A SID tracker for DOS/MAC/LINUX that can create packed binary files for playback on the F256 computers.		\|A SID tracker for DOS/MAC/LINUX that can create packed binary files for playback on the F256 computers.
	\|}		\|}

	*		*

Mcassera: Added a link to the GoatTracker guide for the F256

2026-01-30T04:50:31Z

Added a link to the GoatTracker guide for the F256

← Older revision		Revision as of 00:50, 30 January 2026
Line 92:		Line 92:
	\|https://openmidiproject.opal.ne.jp/Sekaiju_en.html		\|https://openmidiproject.opal.ne.jp/Sekaiju_en.html
	\|Easily compose and sequence MIDI music. Supports score notation, piano roll and MIDI in if you have a MIDI interface.		\|Easily compose and sequence MIDI music. Supports score notation, piano roll and MIDI in if you have a MIDI interface.
			\|-
			\|GoatTracker
			\|Guide to use [[GoatTracker]] for the F256.
			\|A SID tracker for DOS/MAC/LINUX that can create packed binary files for playback on the F256 computers.
	\|}		\|}

	*		*

1BitFeverDreams: /* Music Tools and Scripts */ sekaiju added in music tools

2025-10-14T14:49:32Z

Music Tools and Scripts: sekaiju added in music tools

← Older revision		Revision as of 10:49, 14 October 2025
Line 88:		Line 88:

	convert.py : python script to read a VGM or VGZ, decompress it if needed, and strip off the VGM header and GD3 tag		convert.py : python script to read a VGM or VGZ, decompress it if needed, and strip off the VGM header and GD3 tag
			\|-
			\|Sekaiju
			\|https://openmidiproject.opal.ne.jp/Sekaiju_en.html
			\|Easily compose and sequence MIDI music. Supports score notation, piano roll and MIDI in if you have a MIDI interface.
	\|}		\|}

	*		*

1BitFeverDreams: /* Music Tools and Scripts */ added convert.py

2025-01-18T03:39:22Z

Music Tools and Scripts: added convert.py

← Older revision		Revision as of 23:39, 17 January 2025
Line 1:		Line 1:
	== ~~F256~~ Machines Game Development Tools ==		== 000F256 Machines Game Development Tools ==

	=== Sprite Creation Tools & Scripts ===		=== Sprite Creation Tools & Scripts ===
Line 82:		Line 82:

	midi2vgm_opl3 <- Executable		midi2vgm_opl3 <- Executable
			\|-
			\|convert.py
			\|https://github.com/natebarney/playvgm-f256k/tree/master/util
			\|from NateBarney

			convert.py : python script to read a VGM or VGZ, decompress it if needed, and strip off the VGM header and GD3 tag
	\|}		\|}

	*		*

1BitFeverDreams: /* Sprite Creation Tools & Scripts */ new link to png2raw and merged the Aseprite scripts to the table at the top

2025-01-18T03:18:02Z

Sprite Creation Tools & Scripts: new link to png2raw and merged the Aseprite scripts to the table at the top

@@ Line 9: / Line 9: @@
 | style="white-space:nowrap;"| https://www.aseprite.org/
 | style="white-space:nowrap;" |Aseprite can be used to create sprites animation or Tiles Sets.
 |-
 |f256_sprite_cutter
@@ Line 27: / Line 34: @@
 |https://github.com/econtrerasd/F256-GraphicToolkit
 |The Sprite Editor module in the Graphics Toolkit can help you draw sprites of different sizes in the F256 platform and save them as Spr files. The file format is documented in the manual
 |}
@@ Line 74: / Line 85: @@
 |}
+*

SprySloth at 05:21, 13 June 2024

2024-06-13T05:21:01Z

← Older revision		Revision as of 01:21, 13 June 2024
Line 63:		Line 63:
	Link to WSL install:		Link to WSL install:
	https://learn.microsoft.com/en-us/windows/wsl/install		https://learn.microsoft.com/en-us/windows/wsl/install

			'''Link to binaries'''

			https://github.com/cmassat/midi2vgm/releases/tag/V1.0.0

			libADLMIDI.a <- Required Library

			midi2vgm_opl3 <- Executable

	\|}		\|}

SprySloth at 05:13, 13 June 2024

2024-06-13T05:13:04Z

← Older revision		Revision as of 01:13, 13 June 2024
Line 57:		Line 57:

	10) run playvgm.pgx		10) run playvgm.pgx
			\|-
			\|Convert MIDI files into VGM files.
			\| https://github.com/SudoMaker/midi2vgm
			\| This is a Linux app, but does compile using Linux on windows under WSL.
			Link to WSL install:
			https://learn.microsoft.com/en-us/windows/wsl/install
	\|}		\|}

1BitFeverDreams: /* Music Tools and Scripts */

2024-05-11T13:31:03Z

Music Tools and Scripts

← Older revision		Revision as of 09:31, 11 May 2024
Line 44:		Line 44:
	3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.		3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.

	4) this gives you a .DRO that you can analyze with ~~<nowiki>~~https://www.jestarjokin.net/apps/drotrimmer/~~</nowiki>~~ . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.		4) this gives you a .DRO that you can analyze with https://www.jestarjokin.net/apps/drotrimmer/ . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.

	5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.		5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.

	6) use dro2vgm command line tool: ~~<nowiki>~~https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM~~</nowiki>~~		6) use dro2vgm command line tool: https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM

	7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)		7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)

1BitFeverDreams: /* Music Tools and Scripts */ formatting of music tool

2024-05-11T13:25:00Z

Music Tools and Scripts: formatting of music tool

← Older revision		Revision as of 09:25, 11 May 2024
Line 41:		Line 41:

	2) before you get to the point where the music you want to extract plays, hit CTRL-ALT-F7 and you should see in the dosbox 'log' window that a music capture has started. I think it dumps your captures in /username/appdata/local/dosbox/capture but it will say where in the log window		2) before you get to the point where the music you want to extract plays, hit CTRL-ALT-F7 and you should see in the dosbox 'log' window that a music capture has started. I think it dumps your captures in /username/appdata/local/dosbox/capture but it will say where in the log window

	3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.		3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.

	4) this gives you a .DRO that you can analyze with <nowiki>https://www.jestarjokin.net/apps/drotrimmer/</nowiki> . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.		4) this gives you a .DRO that you can analyze with <nowiki>https://www.jestarjokin.net/apps/drotrimmer/</nowiki> . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.

	5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.		5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.

	6) use dro2vgm command line tool: <nowiki>https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM</nowiki>		6) use dro2vgm command line tool: <nowiki>https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM</nowiki>

	7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)		7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)

	8) transfer to your F256K (jr has no opl support!)		8) transfer to your F256K (jr has no opl support!)

	9) bload "yourtrimmed.vgm",$010000		9) bload "yourtrimmed.vgm",$010000

	10) run playvgm.pgx		10) run playvgm.pgx
	\|}		\|}

1BitFeverDreams: /* F256 Machines Game Development Tools */ added an entry for VGM extraction

2024-05-11T13:24:26Z

F256 Machines Game Development Tools: added an entry for VGM extraction

← Older revision		Revision as of 09:24, 11 May 2024
Line 29:		Line 29:
	\|}		\|}

	~~==== Scripts ====~~

			=== Music Tools and Scripts ===

			{\| class="wikitable"
			! Tool !! Link !! Notes
			\|-
			\|DOSBox VGM music extraction mini-guide
			\|[[Software#Music]] for playvgm.pgx
			\|DOSBox uses a YM3812 chip that outputs OPL2, this is a great, immense source of music that can leverage the OPL functionality of the F256K
			1) run dosbox 0.74+, from the command line and mount your game as <code>dosbox -c "MOUNT C C:\YOURGAMEISHERE"</code> avoid spaces in folder names

			2) before you get to the point where the music you want to extract plays, hit CTRL-ALT-F7 and you should see in the dosbox 'log' window that a music capture has started. I think it dumps your captures in /username/appdata/local/dosbox/capture but it will say where in the log window
			3) reach the point where it plays and let it loop or run its course, hit CTRL-ALT-F7 to stop the capture.
			4) this gives you a .DRO that you can analyze with <nowiki>https://www.jestarjokin.net/apps/drotrimmer/</nowiki> . the analysis tool is supposed to find loops, but it didn't work well with the first tune I tried.
			5) try to find the location of your first tune's note in the main window of drotrimmer and try to start the playback from there. delete superfluous notes that might surround your tune.
			6) use dro2vgm command line tool: <nowiki>https://www.vgmpf.com/Wiki/index.php/DRO_to_VGM</nowiki>
			7) open in a hex editor and chop off the bytes from 0x00 to 0xFF (it's the header)
			8) transfer to your F256K (jr has no opl support!)
			9) bload "yourtrimmed.vgm",$010000
			10) run playvgm.pgx
			\|}