helio.fm No paid content found

Helio is an open-source music sequencer for desktop and mobile platforms, built for MIDI composition and arrangement. It suits producers and composers who want a minimal, distraction-free interface and who are interested in experimentation with exotic scales and microtonal temperaments. You can get it on Windows, macOS, Linux, iOS, and Android.

What Helio Is Designed For

Helio describes itself as "an attempt to rethink a music sequencer." Its stated priorities are:

• A minimalistic, distraction-free UI
• Clarity over cleverness
• Encouragement of experimentation in underexplored areas of music, such as exotic scales and microtonal temperaments

That makes it a reasonable fit if you want a lightweight sequencing environment rather than a large, feature-dense digital audio workstation. If your work depends on microtonal or non-standard scales, Helio treats that as a core interest rather than an afterthought.

Platforms and Builds

Helio ships in two channels: stable builds and development builds. Available packages per the project site:

Portable Windows builds are useful if you want to run Helio without a full install, for example on a machine where you can't or don't want to change system setup.

Getting Started

The project points new users to its documentation, which covers hotkeys, refactoring options, arpeggiators, and more. A practical path:

1. Pick the build matching your platform and install or unpack it.
2. Open the documentation and skim the hotkeys section first — a minimal UI usually leans on keyboard shortcuts, so learning them early saves time.
3. Create a short test project to try the arpeggiator and refactoring options before committing to a larger composition.
4. If you work with microtonal or exotic scales, set up a small piece in one of those temperaments to see how the workflow fits you.

The site also links a YouTube channel, a bug tracker, and translation resources, so you can follow development or contribute if you want to go beyond using the software.

What to Check Before Choosing It

• Sequencing vs. full production: Helio is a sequencer. If you need a complete production suite with extensive built-in instruments and mixing, compare it against your current DAW rather than assuming it replaces one.
• Mobile workflow: iOS is distributed through the App Store and Android through F-Droid and a package, so mobile use is a first-class option, not a port afterthought.
• Stability vs. new features: development builds exist for most platforms. If you need reliability for finished work, start with stable builds and treat development builds as something to test separately.

Pricing and licensing terms are not stated in the material available here beyond the project's license agreement link, so check that page directly if cost or license terms matter for your use.

MIDI is a data protocol that carries performance instructions—which note, how hard, when—rather than sound itself. A sequencer or DAW records those instructions, then routes them to a virtual instrument or hardware synth that actually generates audio. This matters because it separates the performance from the sound: you can edit a wrong note, change tempo, or swap instruments after recording, which you cannot do with a recorded audio waveform.

What MIDI actually transmits

MIDI messages are small packets of numbers. The ones you'll meet most often:

Velocity is not volume in the audio sense—it's an instruction the receiving instrument interprets, so the same MIDI part can sound aggressive on one synth and soft on another.

How the pieces connect

MIDI travels over physical DIN ports, USB, or virtual MIDI (software-to-software, no cable). A typical setup:

1. A controller (keyboard, pad grid) sends MIDI out.
2. A sequencer or DAW receives it and records the messages.
3. The sequencer plays the messages back into a virtual instrument or hardware synth.
4. That instrument outputs audio, which you then mix.

Virtual MIDI lets a sequencer drive a soft synth on the same machine without any hardware in between.

Recording and editing in a sequencer

When you record MIDI, you're capturing events on a timeline, not a waveform. That gives you editing moves audio can't match: quantize timing, transpose, adjust individual velocities, loop a section, or reassign the whole part to a different instrument. Helio, an open-source sequencer for desktop and mobile, is built around this kind of workflow—its documentation covers hotkeys, refactoring options, and arpeggiators, and the project explicitly aims at experimentation in areas like exotic scales and microtonal temperaments. Those are exactly the cases where MIDI's note-by-note data model pays off, since you're defining pitches numerically rather than playing fixed audio.

Common misconceptions

• MIDI is not audio. It contains no sound. You need a synth or sampler to hear anything.
• General MIDI is a convention, not the protocol. It maps program numbers to standard instrument names so a file plays roughly the same everywhere—useful for compatibility, limiting for expression.
• A MIDI file is just stored messages. It plays back differently depending on what instrument receives it.

If your goal is to compose, edit, and re-voice parts flexibly, MIDI is the layer you work in. If you need a finished recording, MIDI is only the first half—the audio comes from whatever instrument you route it into.

Microtonal music is music that uses pitches outside the twelve equal semitones of standard Western tuning — for example quarter tones, just intonation, or historical and experimental temperaments. You compose with it by choosing a tuning system, mapping it to your instruments, and editing note pitches at a finer resolution than a piano roll normally allows. Helio, an open-source sequencer for desktop and mobile, is explicitly built to encourage experimentation in "exotic scales and microtonal temperaments," so it works as a concrete example of how this looks in practice.

What makes music "microtonal"

Standard Western tuning divides the octave into 12 equal steps (12-tone equal temperament, or 12-TET). Each step is 100 cents, and an octave is 1200 cents. Microtonal music uses intervals that don't land on those 100-cent grid points.

That covers a wide range of systems:

• Quarter tones — 24 equal steps per octave, 50 cents each. Common in modern classical and some Middle Eastern traditions.
• Just intonation — intervals built from simple frequency ratios (3:2 for a perfect fifth, 5:4 for a major third) rather than equal steps. Chords sound beatless in one key but drift in others.
• Other equal divisions — 19-TET, 31-TET, 53-TET, and so on, each trading off how well different intervals approximate just ratios.
• Historical and regional temperaments — meantone, Pythagorean, and various maqam and raga systems that predate or sit outside 12-TET.

The practical difference: in 12-TET a major third is 400 cents. In just intonation it's about 386 cents. That 14-cent gap is small but audible as a change in how "locked in" a chord sounds.

Why composers use it

Three recurring motivations:

1. Harmonic accuracy. Just intervals have no beating, so sustained chords can sound cleaner than their equal-tempered equivalents.
2. Expressive color. Quarter tones and other inflections add melodic tension that 12-TET can't produce.
3. Cultural and historical fidelity. Music written for non-Western or pre-20th-century tuning systems is often approximated poorly by 12-TET.

How a sequencer handles microtonal scales

A conventional piano roll assumes 12 notes per octave. A microtonal-capable sequencer has to do more than that. Helio's stated design goal is to "encourage experimentation in underexplored areas in music, like exotic scales and microtonal temperaments," which means the scale and tuning layer is part of the composition workflow rather than an afterthought.

In practice, the pieces you need to control are:

• The scale or temperament — which pitches exist and how they're spaced.
• The note grid — how finely you can place and edit pitches.
• The instrument's tuning — whether the sound source actually plays the pitch you specified.

The third point is where most microtonal work breaks, so it's worth treating separately.

Practical steps for composing microtonally

The exact menus differ by tool, but the sequence is consistent:

1. Pick a tuning system. Decide on a specific equal division, a just-intonation set, or a custom scale file. Vague intentions ("I want it to sound exotic") don't translate into editable pitches.
2. Set the scale in the sequencer. Load or define the temperament so the note grid reflects your chosen pitches rather than 12-TET.
3. Choose instruments that accept pitch data. This is the critical step — see the pitfalls below.
4. Edit notes at the required resolution. If your scale has 24 or 31 steps per octave, you need note placement and pitch-bend resolution to match. Coarse grids will quantize away the intervals you're trying to use.
5. Verify by ear and by measurement. Play a sustained interval and listen for beating. If a just fifth beats, something in the chain is retuning it.

Expected result: notes land on the intended cents values, and sustained intervals sound as the chosen system predicts.

Common pitfalls

Instruments that ignore your tuning

Most sample-based and many synth VSTs are hardwired to 12-TET. They receive a MIDI note number and play a fixed pitch. If your sequencer sends a microtonal pitch as a note number, the instrument snaps it to the nearest semitone.

Workarounds:

• Use synths that support MIDI tuning standards or Scala (.scl) / tuning-table files.
• Send pitch as pitch-bend data per note, which most synths do respond to — but check the bend range, since a default of ±2 semitones may not cover your intervals.
• Use MTS-ESP-style dynamic tuning, if your host and plugins support it.

Pitch-bend range mismatches

If the sequencer assumes a ±2 semitone bend range and the synth is set to ±12, every microtonal note plays at the wrong offset. Match the ranges explicitly.

Quantization erasing your intervals

A grid set to 1/16 notes is fine for rhythm but says nothing about pitch. Make sure pitch editing isn't snapping to 100-cent steps.

Chords that only work in one key

Just intonation is key-dependent. A chord that's beatless in C may sound rough after a modulation. Decide whether you want a fixed just tuning, a adaptive one, or an equal division that compromises across keys.

Choosing a tool

If you want to explore microtonality, the deciding factors are:

• Does the sequencer expose scale/temperament settings directly? Helio lists exotic scales and microtonal temperaments as a design focus, which puts it in the "built for this" category rather than "possible with workarounds."
• Does it run where you work? Helio ships stable builds for macOS, Windows (installer and portable 32/64-bit), Linux (AppImage, deb, tarball), iOS, and Android, plus development builds for the same platforms.
• Can your instruments follow? No sequencer can fix a plugin that ignores tuning data. Budget time for testing your sound sources.

Helio is open-source and its documentation covers hotkeys, refactoring options, and arpeggiators — useful once the tuning layer is set up, since microtonal parts often need more editing passes than 12-TET ones.

Where to start

Pick one system — quarter tones are the gentlest entry point — set it up in your sequencer, and write a short piece using only that scale. The goal of the first attempt isn't a finished track; it's confirming that the pitches you specify are the pitches you hear. Once that chain is verified, the compositional questions (which intervals, which chords, which keys) become the interesting part.

iHeart is a free streaming platform that combines live radio stations, customizable artist stations, playlists, and podcasts in one place. You can start listening without paying by opening iheart.com in a browser or using the iHeart app, then searching for a station, artist, song, or podcast. A subscription is only relevant for certain premium features; the core listening experience described on iHeart's site is available for free.

What you can listen to on iHeart

iHeart organizes its content into a few main types, and knowing the difference helps you find what you want faster.

The key distinction is live versus on-demand. Live radio plays whatever is broadcasting right now, so you can't skip tracks. Artist stations and playlists behave more like on-demand listening, where you control the starting point.

How to start listening for free

You can begin on either the web or the app. The steps are similar.

1. Open the platform. Go to iheart.com in a browser, or install the iHeart app on your phone or tablet.
2. Search or browse. Use the search function to enter a station name, artist, song, or podcast. Alternatively, browse categories to see what's available.
3. Select what you want to hear. Choosing a live station starts playback immediately. Choosing an artist creates or opens a station built around that artist.
4. Press play and adjust. Use the player controls to pause, change volume, or move between stations. On live radio, expect no track skipping; on artist stations, you have more control over what plays next.
5. Save what you like. Favoriting a station or artist makes it easier to return to later without searching again.

Expected result: audio begins playing shortly after you select content, and your favorites appear in your account for quick access next time.

Creating your own stations and playlists

• Artist stations: Start from an artist you like, and the station plays music in that style. This is the fastest way to get continuous music without building a list yourself.
• Playlists: Add individual songs to a playlist when you want a specific set of tracks rather than a continuous stream. This suits workouts, commutes, or a fixed party set.
• Tip: Use artist stations for discovery and playlists for control. If a station drifts away from what you want, switch to a playlist instead of fighting the stream.

What's free versus what needs a subscription

iHeart's own description states that its music, podcasts, and radio stations are available for free, and that you can listen to thousands of live stations or create your own artist stations and playlists. The site also references a subscription, which indicates that some features sit behind a paid tier.

Because the exact free-versus-paid split isn't fully detailed in the available information, treat it this way:

• Assume free: live radio stations, artist stations, playlists, podcasts, and general music/news browsing, based on iHeart's stated offering.
• Check before assuming: any feature labeled as premium, ad-free, or subscription-only. If a paywall appears, that specific feature requires payment.
• Don't assume: that a subscription is required to listen at all, or that everything is free. Verify at the point where you're asked to sign up or pay.

Common snags and how to handle them

• A station won't play. Live stations can be unavailable due to regional restrictions or temporary outages. Try another station to confirm whether the issue is the station or your connection.
• You can't skip a track. That's expected on live radio. Switch to an artist station or playlist if you want control.
• Search returns too many results. Add the type of content to your search, such as the artist name plus "station," or search podcasts separately from music.
• You lose your favorites. Sign in to an account so saved stations and playlists persist across sessions and devices.

Quick decision guide

• Want background music with no effort? Open an artist station.
• Want a specific set of songs? Build a playlist.
• Want a live show or local broadcast? Pick a live radio station.
• Want talk or storytelling? Go to podcasts.
• Want to avoid paying? Stick to the free listening options above and check any prompt before entering payment details.

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

• Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
• UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
• Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

• Keyboard focus is visible and the element is reachable by Tab.
• Color contrast meets WCAG AA (4.5:1 for normal text).
• Interactive elements use semantic HTML (<button>, not a clickable <div>).
• Form inputs have associated labels.
• Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

• Prototypes and demos: you need something clickable today, not a design system.
• Landing pages and marketing sites: a handful of distinctive elements, each custom.
• Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
• Learning: reading well-made CSS is one of the fastest ways to improve.
• Small projects: a personal site doesn't need a theming architecture.

Where they fall short

• Consistency at scale: ten elements from ten contributors rarely look like one product.
• Maintenance: you own every copy. When your design changes, you edit each one.
• Accessibility debt: you inherit whatever the contributor did or didn't do.
• No upstream fixes: a bug fixed in the original won't reach your copy.
• Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.