Log In  

Ignore StinkerB06, call me "The Beesh-Spweesh!"

[ :: Read More :: ]

Cart #eas_test-0 | 2022-01-22 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

If you don't know: The Emergency Alert System (EAS) is a warning system in the United States that interrupts TV and radio programming in order to provide important information on events that pose danger to your life. This cartridge replicates the intimidating tones from the system using the secret PCM channel in PICO-8.

Note that the National Periodic Test here is completely fake. There's no voice announcement included for now, due to concerns about hitting the limited storage capacity of PICO-8 carts.

WARNING: Never broadcast the EAS header bursts on TV or radio! The FCC will have the right to fine anyone for such misuse of EAS/SAME tones.

P#105517 2022-01-22 17:57

[ :: Read More :: ]

Cart #nes_triangle_wave-0 | 2021-12-30 | Code ▽ | Embed ▽ | No License

What is this cartridge?

This is an example of how the bitcrush/distortion flags (found at poke location 0x5F42) can be utilized. The triangle waveform in PICO-8 can be made to sound more like the NES's triangle wave channel, but not exactly the same as it.

Technical bits

Generally, all digital sound data is not accurate. They are limited by some factors. One of those factors is "amplitude".

The primary way to store audio digitally is with Pulse-Code Modulation (PCM), where an analog audio signal is repeatedly sampled at a certain time interval, and each analog sample is quantized to a limited range of digital values.

Let's take one common PCM audio storage medium: the music CD. These encode each digital sample with 16 bits, so the amplitude of an analog sample needs to be rounded towards one of around 65,000 linearly-spaced amplitudes to be stored in the format. (65,000 is quite high, and there are some other formats that have a higher range of amplitudes.)

So how is this info relevant to PICO-8 and the NES?

My definition of "bitcrush" is to further limit the range of digital amplitudes an already-digital sample can use. PICO-8 provides a bitcrush effect built-in that can be applied individually to any of the four PSG channels. It's presumably a novelty effect remindful of game corruption - it was first discovered on accident by literally corrupting the RAM while playing something!

As the NES triangle wave is, in-fact, composed of very few amplitude levels, the PICO-8 PSG can achieve a similar type of triangle wave just by a single poke!

P#103812 2021-12-30 11:37 ( Edited 2021-12-30 11:47)

[ :: Read More :: ]

Cart #sw_and_hw_rng-1 | 2021-12-12 | Code ▽ | Embed ▽ | No License

This is a re-implementation of PICO-8's own pseudo-random number generator state algorithm.

Press any button to tick the software RNG, and the hardware RNG as well. The text will turn red if the software RNG state doesn't match the 64-bit RNG state within the base RAM layout.

P#102467 2021-12-12 15:26 ( Edited 2021-12-12 15:56)

[ :: Read More :: ]

Did anybody ask to be annoyed by some beeps and boops in their PICO-8? If you did, here you go!

Cart #ice_cream_truck-0 | 2021-11-24 | Code ▽ | Embed ▽ | No License

The animation is inspired by old "learning computer" toys that sound like ice cream trucks.

P#100760 2021-11-24 14:52

[ :: Read More :: ]

Officially, the 0x5F00 to 0x5F3F area is referred to as "Draw State" RAM, and 0x5F40 to 0x5F7F is referred to as "Hardware State" RAM.

However, I think this is quite misleading, considering Draw State RAM offers some non-related functionality like controlling Devkit Mode, muting audio, and suppressing the pause menu. Furthermore, there are some graphics-related addresses in Hardware State RAM, notably for: the default print() attributes, the bitplane read/write masks, the undocumented high-color stuff, and the "Palette 2" shared between the recent fill pattern functionality and high-color modes.

I'd suggest both 64-byte areas be merged into a single 128-byte "Hardware Variables" area.

P#93993 2021-06-24 22:00

[ :: Read More :: ]

EDIT: This has been resolved by Zep.

As the title says, the "code snippet within a line" markdown on the BBS doesn't properly respond to the end marker, and instead runs down to the end of the whole line.

Assume the following raw text:

This is a `code snippet` within a line!

This should be expected (italics used to represent the text within the backticks):
This is a code snippet within a line!

But the observed result is:
This is a code snippet within a line!

P#81030 2020-08-22 00:38 ( Edited 2022-02-12 08:22)

[ :: Read More :: ]

Hey @zep!

Can you please add a feature to PICO-8's WAV export function, so that each of the four channels have one WAV file each? I've been wanting to do oscilloscope views of PICO-8 chiptune music, but the "oscilloscope view" format requires one WAV file for each channel (so that each channel is seen as a separate waveform).

I've already mentioned you on Twitter about this, but you never replied:

P#68824 2019-10-13 01:56

[ :: Read More :: ]

Cart #ls_and_bbs_stats-0 | 2019-06-05 | Code ▽ | Embed ▽ | No License

This thread is intended for the sake of researching particular (and most likely undocumented) parts of PICO-8's STAT(), that @zep didn't reference in the PICO-8 manual. The cartridge above also shows a new way for PICO-8 game devs to read the root-folder cartridge list with LS() (you must be on the desktop PICO-8 and your root directory must have at least 1 cartridge).

If you, Zep, know anything about the STAT() numbers not seen in the manual, can you tell me what they are for? People have figured out these for the BBS 101~104:

  • STAT(101) -> BBS ID (nil for local carts)
  • STAT(102) -> Site name (blank string in exported HTML's, nil in desktop PICO-8 builds and exported binaries)
    People have NOT figured out:
  • STAT(103) -> Hash string of unknown encryption method (was 0 in 0.1.11g)
  • STAT(104) -> False (when will this evaluate to true or some other value?)
P#65002 2019-06-05 10:19

[ :: Read More :: ]

Cart #sspr_tester-0 | 2019-05-19 | Code ▽ | Embed ▽ | No License

This cartridge is intended for PICO-8 newcomers to learn how SSPR() works.


Up and down arrows: Selects the parameter to change.
Left and right arrows: Modifies number-parameter values (the two sets of X, Y, W, and H values).
Z/C/N (or the right face-button on mobile touchscreens): Changes number-parameter values by 8 instead of 1. This also modifies the flip settings.


Src. X: The X-coordinate of the spritesheet to draw from, relative to the left. Pixels outside of the 0..127 range will be treated as black.
Src. Y: The Y-coordinate of the spritesheet to draw from, relative to the top. Pixels outside of the 0..127 range will be treated as black.
Src. W: The width of the sprite's image, in pixels. Negative values are treated as 0, of which results in no sprite drawn. The image is stretched to the 'Draw W' width.
Src. H: The height of the sprite's image, in pixels. Negative values are treated as 0, of which results in no sprite drawn. The image is stretched to the 'Draw H' height.
Draw X: The X-coordinate of the screen to draw to, relative to the left. Pixels outside of the 0..127 range are invisible, so that the sprite can be pushed into the left or right edge of the screen.
Draw Y: The Y-coordinate of the screen to draw to, relative to the top. Pixels outside of the 0..127 range are invisible, so that the sprite can be pushed into the top or bottom edge of the screen.
Draw W: The width of the sprite itself, in pixels. Negative values allow a horizontally-flipped image, with the 'Draw X' coordinate representing the right side of the sprite instead of the left.
Draw H: The height of the sprite itself, in pixels. Negative values allow a vertically-flipped image, with the 'Draw Y' coordinate representing the bottom of the sprite instead of the top.
H-Flip: If TRUE, the sprite's image is flipped horizontally. Combining this with a negative 'Draw W' value results in a cancel-out, drawing the image without flipping it.
V-Flip: If TRUE, the sprite's image is flipped vertically. Combining this with a negative 'Draw H' value results in a cancel-out, drawing the image without flipping it.

The spritesheet used here is the one from Zep's Jelpi Test!

P#64596 2019-05-20 00:16 ( Edited 2019-05-20 20:03)

[ :: Read More :: ]

Cart #video_mode_tester-0 | 2019-05-02 | Code ▽ | Embed ▽ | No License

This cartridge is intended for PICO-8 newcomers to learn how each mode works.

Use the arrows to change the video mode. Valid modes are 0~7.

It writes to the address 0x5F2C in Draw State RAM to set the video mode (display resolution or reflection).

The sprites used here are Jelpi sprites!

P#64141 2019-05-02 06:58

[ :: Read More :: ]

Cart #picovisualizer-9 | 2022-02-20 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

WARNING: Depending on what you watch and listen to with this visualizer, the bars can produce flickering effects on your screen, which may be a problem for those diagnosed with epilepsy. Better use with caution.


This is a heavily-modded variant of Music Visualizer Bars by iaoth. Thanks to him for his visualizer code base!

I can load() this cart. Is there anything special about doing that?

Yes! By a cart passing a load parameter string to PicoVisualizer, that cart can serve as a custom menu that allows users to view the visualization of any of its tracks, but has the cost of depending on an internet connection.

PicoVisualizer uses split() to extract the arguments inside the parameter string. The music and SFX data (that would be found at 0x3100...0x42FF) must be supplied at 0x8000...0x91FF by the cart.


  1. The song ID to start playing. If this is blank, PicoVisualizer will function normally.
  2. The initial "Sound Attributes" state. The bitfield structure is the same as peek4(0x5f40). This can be blank or omitted.
  3. The screensaver is disabled if this argument is 1. This can be blank or omitted.
  4. The "Sound Attributes" menu is disabled if this argument is 1. This can be omitted.

Sample usage:

load("#picovisualizer","exit visualizer",

What are these 10 tracks?

To test most of all of my new changes to that visualizer, I thought I'd use something that really got my attention around the time I first started making them. That is PICO-8 Tunes Vol. 2 released by @Gruber, a cartridge featuring 10 original songs you can use in your PICO-8 projects for free.

Update history

March 26th, 2019 (first version)

  • Corrected the octave numbers to match the PICO-8 SFX editor.
  • Fixed the waveform colors of the bars being wrong. The PICO-8 palette index it was referring to was 1 less than what the SFX editor references to.
  • Changed the beige text color to white. Prevents blending with bars with the PHASER waveform (SFX editor value 7).
  • Implemented displays for custom instruments (SFX 0~7) and effects (slide/vibrato/drop/fade/arp).
  • The colors of the bars and displays now change accordingly if the instrument is either a fixed waveform or a custom instrument.
  • Implemented the DROP and FADE IN effects (SFX editor values 3 and 4, respectively) to the volume bars' handling code. The code I added may not be 100% accurate, but if you have any changes to make to it, please let me know in the comments!
  • Added a function to disable all loop/stop control flags in the music RAM, found at 0x3100~0x31FF in the PICO-8 memory map. This can be disabled by commenting out lines 9~11 in code tab 0.

March 27th, 2019

  • Changed the DROP and FADEOUT effects' speed in their respective handler code. It should be more accurate now.
  • The position of the effect displays' texts are now pseudo-centered.
  • The dark-gray color of the displays for custom instruments is now changed to brown, if it blends with the black background of the visualization.

April 3rd, 2019

  • Fixed custom instrument displays from showing "SFX -1".
  • When the note volume is zero, the wave is set to -8 to make the bar black.
  • Custom instrument bars are now changed to a darker gray. The note/effect displays are changed to white, to be like the fixed waveforms.
  • Effect names now make use of PICO-8's own text string emojis.
  • If PICO-8 plays note indexes beyond 31, they're now treated as being a zero-volume note. Fixes the bars playing inaudible pattern data, especially noted with Marballs 2 while I was making this update.
  • Added displays at the top for showing which patterns and notes the channels are playing.
  • Added another display for identifying what frames repeat or stop the track, by reading the music control flags of each of those 64 frames on the cartridge.
  • Added a simple main menu to select a track the user wishes to play, rather than playing all tracks in one go.

April 5th, 2019

  • Made the loop and stop shapes brighter, as a result of preventing bars for displaying on the top 16 pixel rows.
  • Frames with all three flags disabled will now be displayed with a dark-gray dot/pixel.
  • Arp displays now show the exact note-cycle frequency division for the ~120Hz SFX clock.
  • Tracks in the TRACK.DATA table now have support for loading from an external cartridge. If this is unspecified, track data from the visualizer cartridge itself will be used instead.
  • Minor changes to the menu, including fixing a mistake where I didn't mention the left and right arrows would also select the track, which was already a thing in the previous update.
  • Added the ability to stop a track during playback. When stopping, a 333ms fade-out is applied. However, you can still pause the track by pausing the cartridge.
  • Removed the 3-line time code in the DRAW_VISUALIZER() routine that existed there and did nothing at all.

  • Fixed bars 2~4 from drawing in front of the top displays.
  • Fixed note nn indexes beyond 31 from showing on the "Rnn" displays.
  • SFX speed is now more accurate to the PICO-8 SFX engine.
  • Bars will no longer display beyond the limit (MUSIC_EVENTS.VOLUME[I]>7), improving max-volume FADE IN effects.
  • More minor changes to the interfaces.

April 14th, 2019

  • Added support for the undocumented "half-clock" audio flags in the RAM. Even when they're disabled (which they always were in all previous versions), the drop/fade speed is now fixed in regards to that TIME() change in PICO-8 0.1.12.
  • The 333ms fade-out is now more like an actual third-of-a-second fade.
  • Added a screen-saver! I don't know if it's any good, but please tell me your thoughts about it in the comments!
  • Removed more unnecessary parts of the code, including a blank MUSIC_EVENTS.LIST table that wasn't used.

April 15th, 2019

  • Fixed the FADE-IN movement from heaping over the top of the bar height position that represents the current note volume.
  • The screen-saver color-changer now refers to the lowest-indexed active channel, instead of only the first channel.
  • Changed the PEEK4() into the recently-added PEEK2(). Notes are 16 bits long, so NOTEDAT doesn't need to be 32-bit.
  • When a track stops, it now automatically goes back to the main menu.
  • Changed a few text label strings.
  • Removed one more unnecessary code line that I forgot to remove.

April 16th, 2019

  • Text labels and code editor comments now feature lowercase letters. Since PICO-8 0.1.12 doesn't convert to lowercase letters when 0.1.11g did, this change was made.
  • Fix to prevent the first frame of track playback from being drawn. This first frame had info from the previously-played track that shouldn't be drawn.
  • Minor change to the code that gets rid of one FOR loop.

June 3rd, 2019

  • Added the ability to load up any file (but only on the desktop versions of PICO-8). Just pause the cartridge and select "TOGGLE FILE MODE". Pick a file and the starting music frame (00~63), and play!
  • Changed PRINT() calls into the undocumented '?' syntax. Reduces token count if applied to the previous update of this visualizer.
  • More minor tweaks. Again.
  • Added an easter egg somewhere. Can you find it?

June 17th, 2019

  • Moved the flags display routine into a separate function, so that I could re-use it in the menu screen.
  • Made each of the 64 frame bars and each of the pattern/row displays change their gray shade. If dark gray, it's disabled (doesn't play any SFX/pattern during the current frame). Otherwise, if light gray, it's enabled.
  • Changed how the loops and red stop-flags look. This actually makes it better/possible to see some odd looping configurations. For example, "Morning Shower" starts on frame 00 and doesn't contain a loop-start marker. Thus, PICO-8 doesn't know what frame to jump to after playing the last frame, so it goes back to 00.

June 30th, 2019

  • Renamed this visualizer! This is the official thread, so why do I have to have the album's name?
  • Changed the screensaver color-changing code to use STAT(25) instead of STAT(24). Fixes the color not changing on 1-frame loops.
  • Added a new "Sound Attributes" menu that allows you to change undocumented audio features, such as the clock halvers, reverb filters, the distortion feature, and the lowpass filters while music is playing. Credit to @Synth_dfr for the icons!
    NOTE: Due to some constraints with the PICO-8 audio engine, the half-clock feature causes oddness with STAT(24) if not all four channels have it enabled. Channels with the same SPD value and different half-clock settings eventually get out of sync, not good ;-(

July 5th, 2019

  • Set the pink (0x40) flag of sprites 252~255. Fixes a display's error when song playback ended and the "Sound Attributes" window was open.
  • Rearranged sprites in the sprite editor.

May 9th, 2020

  • Code cleanup and optimizations for 0.2.0! Wow, PICO has indeed been in alpha for so many years, glad it's finally in beta then!
  • Changed the screensaver.
  • Changed the transparency in the "Sound Attributes" window. Basically, I have almost none of the spritesheet used up, so I copy the window's area to the spritesheet and change the draw palette.
  • Changed the music-frames display, so that any start/end/stop flag combination is visible, along with which frames are used and where the playhead is.
  • Moved the sprites into the code (written to spritesheet at runtime), so now only the code section needs to be transferred over to essentially copy the entire visualizer program (except the music/SFX).
    NOTE: iaoth's original visualizer started off with having more than one code tab (the main init/update/draw tab, the music events tab, and a debugging tab which I removed). As such, the code needs to be copied tab-by-tab (or not, since each tab is literally separated with a special marker visible in .p8 text carts).

January 4th, 2021

  • Changed up the visualizer look a little bit! The bars now use a fill pattern to reduce eye-strain. (It has that
    "pinball" aesthetic, doesn't it?) Let me know if you want me to revert some things back if you don't like them!
  • Fixed a bug where the specified external cartridge file for the 1st track in the playlist isn't immediately loaded when PicoVisualizer is runned.
  • I can't figure out why I wanted to have the sprites stored in the code... so I just put them back on the spritesheet for now.
  • Yet more minor code changes.

February 13th, 2021

  • Added a new display for effects added in 0.2.2. (not used by PICO-8 Tunes Vol. 2)
  • Updated the "Sound Attributes" window to support the effect toggles added in the upper nibbles of 0x5F40 to 0x5F43. I also gave a go at using some of the new P8SCII codes here.
  • Fixed a crash in the BBS player when "TOGGLE FILE MODE" is selected, as a result of LS() returning nil.
  • Yet yet more minor code changes.

July 1st, 2021

  • Fixed the left and right arrows from being able to select the menu items I customized for PicoVisualizer. It's just a side effect of the recent MENUITEM() callback functionality.
  • The visualizer now always closes even if the Sound Attributes window is open. I probably don't need the pink flags in sprites 252 to 255 to be set anymore, don't I?
  • Changed the fade-out speed to 1/2 a second.
  • Reworked the BUZZ and DETUNE sprites.
  • Once again, more minor code changes. I did some token optimizations, including the use of SPLIT() and UNPACK() when initializing an array of strings.

December 3rd, 2021

  • Added beep sound effects to the menu! (The undocumented PCM channel is the only way to play sound effects without clobbering an SFX slot!)
  • The transparency in the Sound Attributes menu now utilizes the ability to remap the spritesheet region to the screen region in PICO-8 0.2.4.
  • Most STAT() calls changed from the legacy versions to the superseding versions introduced in 0.2.4. STAT(24) calls remain as unchanged here, because STAT(54) doesn't seem to be returning -1 to indicate that no music is playing at the moment. Must be worthy to tell Zep about?
  • Moved the _INIT() method function into a separate tab.
  • Turned on CC4-BY-NC-SA licensing.
  • You can guess what else I have done...

December 6th, 2021

  • "Distortion" is now given a more-appropriate name in the source: "Bitcrush". The "Alt Distortion" is now just called "Distortion". Additionally, an associated sprite for Bitcrush is added to replace the original Distortion sprite, to maybe give a sense for the fuzzy timbres the effect creates.
  • Made the beep tones a bit louder.
  • Patterns with a SPD value of 0 are now properly treated like they're 1.
  • Changed most instances of STAT(24) to STAT(54), except for those where the value is being compared with -1 (to determine if music has stopped playing).
  • More code changes/optimizations?!?

February 7th, 2022

  • Changed comparisons of stat(24) with -1 to utilize the stat(57) flag that was added in PICO-8 0.2.4b.
  • The array in the music_events table storing the "SFX instrument" flags now uses booleans to make the code a little better.

February 18th, 2022

  • Added parameter string functionality!
  • Changed the design of the bottom blue bar. The bars now appear to come out of little slots, don't they?
  • Slightly increased the bars' maximum height.
  • More code changes. camera() is now used for simplicity in the visualizer draw code.

February 19th, 2022

  • Yeah, this is some more code editing.

If you keep seeing screenshots of the visualizer playing "Autumn Wind" throughout these updates and changes, that's because it's my favorite chilly song from that collection.

Plans for PicoVisualizer's future

  • Add a JavaScript GPIO pin interface. Users can upload cartridge files and it will be uploaded to the PICO-8 browser-player instance running PicoVisualizer.
  • Allow playlists to be configured for native exports (Windows, Linux, OSX, Raspberry Pi) from PICO-8. This could probably allow custom playlists of other cartridges to be created without having to buy the fantasy console. When there's a way to get this fully working, there's a will to release binaries to the public. For now until then, if you want to see other songs with my visualizer, post some suggestions in the comments, and I'll reply with a cartridge!
  • Fix 'CD [DIRNAME]' commands in the PICO-8 console from not working properly. When the cartridge is run, it gets all cartridge filenames from the directory, but trying to play them will attempt to load from the root directory instead. A workaround (as of the time of writing) is to put this cartridge in the folder directory of where you want to load your music from. Open the PICO-8 config.txt, and change root_path to the directory of where your music is. After that, run PICO-8, then load up this cartridge and run it. You may also just copy and paste PicoVisualizer into every folder PICO-8 can see if you don't want to edit the config, which is what I personally do.
P#63059 2019-03-27 09:09 ( Edited 2022-02-20 05:05)

[ :: Read More :: ]

Cart #stinkerb06rmg-1 | 2019-05-10 | Code ▽ | Embed ▽ | No License

The sound and music editor data that's generated is 100% randomized! Music starts at a random position from 0 to 63.

Update May 10th, 2019:

  • Improved corruption speed by using POKE4(). This pokes four memory locations simultaneously without having to use four sequential POKE()s.
  • Renamed the cartridge to prevent confusion.
P#62988 2019-03-24 05:29 ( Edited 2019-05-10 10:27)

[ :: Read More :: ]

Cart #55422 | 2018-08-20 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

Update August 20th, 2018: Slight change to show 15 color rectangles instead of only 7. This is not a song-related change.

Credit to Zep for the code base.

P#55388 2018-08-19 13:07 ( Edited 2018-08-22 21:50)