HTML preprocessors can make writing HTML more powerful or convenient. For instance, Markdown is designed to be easier to write and read for text documents and you could write a loop in Pug.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. So you don't have access to higher-up elements like the <html>
tag. If you want to add classes there that can affect the whole document, this is the place to do it.
In CodePen, whatever you write in the HTML editor is what goes within the <body>
tags in a basic HTML5 template. If you need things in the <head>
of the document, put that code here.
The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https.
CSS preprocessors help make authoring CSS easier. All of them offer things like variables and mixins to provide convenient abstractions.
It's a common practice to apply CSS to a page that styles elements such that they are consistent across all browsers. We offer two of the most popular choices: normalize.css and a reset. Or, choose Neither and nothing will be applied.
To get the best cross-browser support, it is a common practice to apply vendor prefixes to CSS properties and values that require them to work. For instance -webkit-
or -moz-
.
We offer two popular choices: Autoprefixer (which processes your CSS server-side) and -prefix-free (which applies prefixes via a script, client-side).
Any URLs added here will be added as <link>
s in order, and before the CSS in the editor. You can use the CSS from another Pen by using its URL and the proper URL extension.
You can apply CSS to your Pen from any stylesheet on the web. Just put a URL to it here and we'll apply it, in the order you have them, before the CSS in the Pen itself.
You can also link to another Pen here (use the .css
URL Extension) and we'll pull the CSS from that Pen and include it. If it's using a matching preprocessor, use the appropriate URL Extension and we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
JavaScript preprocessors can help make authoring JavaScript easier and more convenient.
Babel includes JSX processing.
Any URL's added here will be added as <script>
s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.
You can apply a script from anywhere on the web to your Pen. Just put a URL to it here and we'll add it, in the order you have them, before the JavaScript in the Pen itself.
If the script you link to has the file extension of a preprocessor, we'll attempt to process it before applying.
You can also link to another Pen here, and we'll pull the JavaScript from that Pen and include it. If it's using a matching preprocessor, we'll combine the code before preprocessing, so you can use the linked Pen as a true dependency.
Search for and use JavaScript packages from npm here. By selecting a package, an import
statement will be added to the top of the JavaScript editor for this package.
Using packages here is powered by esm.sh, which makes packages from npm not only available on a CDN, but prepares them for native JavaScript ESM usage.
All packages are different, so refer to their docs for how they work.
If you're using React / ReactDOM, make sure to turn on Babel for the JSX processing.
If active, Pens will autosave every 30 seconds after being saved once.
If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.
If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.
Visit your global Editor Settings.
#main
html, body
height: 100%
body
margin: 0
#main,
#app,
#visualizer
height: 100%
#app
display: flex
justify-content: center
align-items: center
background: url("https://i.imgur.com/Zk6TR5k.jpg") center center / cover no-repeat
button
cursor: pointer
height: 30px
width: 97px
border: none
background: url("https://coddec.github.io/Classic-Shell/www.classicshell.net/forum/download/filefc1a.png?id=1542")
background-position: 0 -12px
&:hover
background-position: 0 -66px
&:active
background-position: 0 -120px
#visualizer
display: flex
flex-direction: column
width: 100%
padding: 4px
box-sizing: border-box
background: radial-gradient(white 30%, blue)
#controls
flex: 1
display: flex
justify-content: center
align-items: center
background: linear-gradient(dimgray, ghostwhite)
#bars
flex: 4
display: flex
justify-content: center
align-items: flex-end
gap: 1px
background: black
padding-top: 4vh
padding-bottom: 4vh
.bar
width: 4px
background: chartreuse
// Given 128 bars, hide the >= 84th bars, because there's no info for those frequencies
// (May change depending on song)
&:nth-child(n + 84)
display: none
// Shoutout to Sarah Drasner for heavily commenting her visualizer setup!
// https://codepen.io/sdras/pen/PVjPKa
const AMPLITUDE_MAX = 255;
// In case the Sandstorm audio source ever fails, uncomment this royalty-free audio source
// https://pixabay.com/music/synthwave-synthwave-80s-110045/
// const audioSource = 'https://cdn.pixabay.com/audio/2022/04/25/audio_5d61b5204f.mp3';
const audioSource = 'https://ia902201.us.archive.org/16/items/darude-sandstorm_202201/Darude%20-%20Sandstorm.mp3';
function App() {
const [userClicked, setUserClicked] = React.useState(false);
// Chrome requires a user click/gesture before AudioContext can be created
// https://goo.gl/7K7WLu
return (
<div id="app">
{userClicked ? (
<Visualizer frequencyCount={128} audioSource={audioSource} />
) : (
<button onClick={() => setUserClicked(true)} aria-label="start" />
)}
</div>
)
}
class Visualizer extends React.Component {
constructor(props) {
super(props);
this.state = {
frequencyAmplitudes: Array.from(props.frequencyCount)
};
}
// Ensure this.audio has been set by ref callback
componentDidMount() {
// Wire up our audio
this.audioContext = new (window.AudioContext || window.webkitAudioContext)();
this.source = this.audioContext.createMediaElementSource(this.audioRef);
this.volumeControl = this.audioContext.createGain();
this.source.connect(this.audioContext.destination);
this.source.connect(this.volumeControl);
// Create our analyZer πΊπΈ
this.analyzer = this.audioContext.createAnalyser();
this.analyzer.fftSize = this.props.frequencyCount * 2;
this.volumeControl.connect(this.analyzer);
this.analyzer.connect(this.audioContext.destination);
// Analyzer will know user's set volume
this.volumeControl.gain.value = this.audioRef.volume;
// Kick off our animation
this.animate();
}
// Constantly get frequency data from audio so that amplitude can be updated
animate() {
let frequencyData = new Uint8Array(this.props.frequencyCount);
this.analyzer.getByteFrequencyData(frequencyData);
// Without the "bind(this)" silliness, we'll lose the component's context
requestAnimationFrame(this.animate.bind(this)); // lol
// Trigger React render with updated frequencyData
this.setState({
frequencyAmplitudes: Array.from(frequencyData).map(amplitude => amplitude * 100 / AMPLITUDE_MAX)
});
}
render() {
const bars = this.state.frequencyAmplitudes.map(val => {
return <Bar amplitude={val} />
});
return (
<div id="visualizer">
<div id="bars">
{bars}
</div>
<div id="controls">
<audio ref={element => this.audioRef = element} src={this.props.audioSource} controls autoplay="true" crossorigin="anonymous"></audio>
</div>
</div>
)
}
}
function Bar({ amplitude }) {
return <div className="bar" style={{ height: amplitude + '%' }}></div>
}
ReactDOM.render(<App />, document.getElementById('main'));
Also see: Tab Triggers