We’re looking to add a third full-time person to the Soundslice team: a product designer.
After working for five years with part-time design help, we want a full-time person to join our team. Could that be you? Here’s what we’re looking for:
You’ll be in charge of Soundslice’s design and UX — everything from high-level direction to low-level implementation. You’ll be expected to do everything from initial user research to mockups to coding in HTML/CSS.
Specific projects will be all over the map: from incremental improvements to our music player, to marketing/branding materials for our presence at the NAMM Show, to significant new product initiatives.
To state the obvious: as the third person in the company, you’ll have massive impact on Soundslice.
Skills in the entire design process — understanding problems, creating mockups, implementing in HTML/CSS.
Significant experience designing and building websites for desktop and mobile devices.
A great eye for design.
Knowledge of (and passion for) music. You play an instrument. Being a musician isn’t necessarily your whole life, but it’s important to you.
Excellent verbal and written communication skills in English.
Attention to details.
Ability to work well on a small, remote team in a rapidly changing environment, with a lot of autonomy.
Ability to balance many simultaneous projects and responsibilities with ease.
Soundslice is the web’s best way of learning and practicing music. Our state-of-the-art music player, which syncs music notation/tablature with real audio/video, is used and loved by hundreds of thousands of musicians.
Our Store features one-of-a-kind music instruction — and helps artists make a living by giving them a majority of the proceeds. Our technology is embedded in about 70 music-education websites (and growing), including big names such as TrueFire. Many passionate musicians follow our “lick” videos on Instagram.
Much of Soundslice’s value comes from pure UX: the beauty and simplicity of the Soundslice player. Design is front-and-center in our product. As such, your role will be critical for the company.
From a technical perspective, Soundslice is in the upper echelon of modern web applications. With features like offline mode, it pushes the limits of what’s possible in a web page. Working here, you’ll get direct access to this and will be encouraged to continue pushing the envelope.
From a business perspective, Soundslice is healthy and refreshingly independent. We’re proudly bootstrapped, so we’re not playing the venture capital game. While that means we don’t provide free cafeteria food or plush office space, it means we’re not beholden to investors or fundraising cycles. We make decisions with customers and long-term business interests in mind. We’re a sustainable business that’s growing steadily.
From a personal growth perspective: you’d work with me (one of the people who created Django, plus some other stuff). I’m an experienced developer and can teach you a lot, if you’re open to it.
From a workplace perspective: we’re small and geographically distributed. I’m in Amsterdam, and my colleague Corey is in Chicago. We are accustomed to working remotely, so this remote job will not be “bolted on” to an otherwise non-remote team.
Overall, it’s incredibly fun and gratifying to work on Soundslice. This is easily a dream job for a combination musician/designer. If you’re interested, please email me at firstname.lastname@example.org with a resume and links to websites you’ve built.
We’ve been rolling out a bunch of new features lately, as always. If you create scores in Soundslice, you may have already seen some of these.
We now support Wistia, for people who use Wistia video hosting.
When you add a recording, just select the Wistia option. You’ll first need to link your Wistia account with your Soundslice account. From then on, you’ll be able to access your Wistia videos within Soundslice.
You can now disable a score’s notation.
Click “Hide notation” when creating or editing the score, and the score will behave in notationless view (i.e., showing only a full-screen video).
Why would you use this? Perhaps you embed Soundslice in your website and want to give people access to your lesson video as soon as possible, before you’ve synced it with notation. In that case, create the score with “Hide notation” checked, then add the video as a recording. Your users will immediately see the video, and you can take your time with notation and syncpoints. When notation and syncpoints are ready, just uncheck “Hide notation.”
Simplified printing toggle
Previously, when creating a score, you had to choose among three printing options — “Printing is disabled,” “Printing is disabled only for embed” and “Printing is allowed.”
This was unnecessarily complicated, given how people were using it, so we’ve simplified it to an “Allow printing” checkbox.
If you check this, then your score will have a “Print” button in its Settings menu.
Switching recordings in the syncpoint editor
You can now switch among a score’s recordings while editing syncpoints.
Previously, you had to click back-and-forth between the syncpoint editor and the score manager. Now, just toggle recordings at the bottom of the player, and you’ll be able to edit syncpoints for multiple recordings.
You can also switch to the the Synthetic player, which wasn’t previously possible in the syncpoint editor. This can be useful if your recording is hard to hear and you need to hear how the notation sounds when played “perfectly” by a computer.
Embed over non-white backgrounds
Previously our embeddable player assumed your website had a white background — causing a flash of white during loading. It no longer does this, meaning it works elegantly with, e.g., black page backgrounds.
New player API methods
If you embed Soundslice in your site, you’re welcome to use these new hooks for customization:
The setViz API method lets you dynamically activate (or deactivate) a visualization in the player — the piano keyboard, fretboard, violin fingerboard, waveform or mixer.
The viz=0 URL parameter lets you turn off all visualizations.
The getFullscreenSupport API method tells you whether the user’s browser supports web pages going full screen.
The setFullscreen API method lets you make the Soundslice player full-screen.
The narrow_video_height URL parameter now accepts percentages — so you can, for example, specify that the video should use 40% of the available height. This lets you make the player more responsive.
The settings=0 URL parameter lets you disable the Settings menu.
The vfs=0 URL parameter lets you hide the icon that lets users toggle notationless (full-screen video) view.
The setNotationVisibility and getNotationVisibility let you programatically control whether notation is visible.
The ssAudioEnd API event is triggered when playback reaches the end of the recording.
The ssToggleSettings API event tells you when the Settings menu is toggled.
The show_notation=0 URL parameter lets you activate notationless view on a per-embed basis.
We have lots of new Soundslice improvements to share with you today. The biggest news: we’ve launched a new speed-changing interface and a way to share scores across your organization.
New speed interface
Changing playback speed has always been an integral part of Soundslice. But due to the variety of audio/video sources Soundslice supports, we’ve had a variety of slowdown interfaces:
The YouTube player traditionally has allowed only 50% and 100% speeds — so we customized our interface to reflect that. For non-YouTube videos, we support any arbitrary speed down to 50%. For audio files, if you’re using a modern browser, we support any speed down to 25%.
These differences have been tricky to maintain, and they’ve caused some confusion with some of our customers. What’s more, our “slider” interface required a bit too much precision on smaller screens and touch devices. And some of you have (rightfully so) been asking for slower minimum speeds and faster maximum speeds — something we were hesitant to do because it would complicate the interface even more!
All those problems are solved today, with our new interface:
Use the up and down arrows to quickly change speed. For fine-grained precision, click (or tap) the number in the middle and enter whatever speed you want. That’s it.
As part of this, we’ve increased the maximum supported speed for our synth player from 125% to 300% — and decreased the minimum speed from 25% to 10%.
YouTube 75% speed!
In related news, YouTube now supports 75% speed in its embedded player! That means any YouTube video in Soundslice now supports 75% speed. Enjoy your new, moderately faster slowdown powers.
And if you want to practice faster, you’ll appreciate that we now support 125%, 150% and 200% speeds for YouTube videos.
Do you use Soundslice with other people in your company/school/group, sharing a single Soundslice login across multiple people? We’re here to help.
Instead of sharing passwords, you can use our new organizations feature. With it, you can share scores across Soundslice accounts, and easily switch between them:
For more, see our new documentation. Note that this is only available for our licensing customers at the moment. If you’re interested in using it, please get in touch!
Our rendering engine now supports multi-bar rests:
We’ve updated our MusicXML and PowerTab importers to handle multi-bar rests properly.
As always, we make daily improvements to all aspects of our product. Some highlights:
Fixed a bug in iOS where you had to tap the Play button twice for videos to start. Take that, Apple!
Fixed a bug in Safari where the keyboard/fretboard/mixer would sometimes overlap the bottom of the notation.
The visual fretboard now has more padding on top and bottom, which means notes on the outer-most strings no longer get awkwardly cropped.
Score owners can now activate the virtual violin even on tracks that have tablature. Previously this wasn’t allowed.
When in notationless view, our player now always resizes video to fit the full width of the screen. Previously, it did different things depending on screen size.
When in notationless view on a small screen, our player didn’t have a way to toggle notation back on. Now, the arrow icon is available in the upper right of the video.
In the waveform, if you use your mouse wheel while dragging the boundaries of a loop, we now keep the loop properly anchored.
Made the mouse wheel more sensitive in Firefox, when you scroll through notation. It now matches the “feel” of other browsers.
Notationless scores now include a Settings menu. Previously it was hidden.
Notationless scores no longer have a Synthetic player. That was rather useless!
Improved chord-diagram rendering to compress the names of really long chords, so they don’t bump into neighboring chord names.
Improved the vertical positioning of several tablature symbols: let ring, P.M. (palm mute), tap, pop, slap and artificial harmonics. They use space much more efficiently now, though there’s more work to do.
Fixed commentary-bar rendering so that tempo and triplet feel markings are rendered above (if applicable).
Fixed beamed grace notes to have an even beam width. Previously it was slightly oblong.
Fixed trill rendering to avoid doubling up the trill squiggly line in case of subsequent trilled notes.
Made some nice performance improvements, especially in the music-glyph rendering.
Fixed barre (aka Roman numeral position) rendering on retina screens.
Fixed our renderer never to display accidentals for slash noteheads. That bug was just silly.
Began implementing specific error messages for our MusicXML importer, if your uploaded file contains a known problem. Much better than a generic “Invalid file” error message.
Fixed a bug with funny characters in MusicXML chord names.
Fixed a bug where multi-line lyrics in MusicXML would sometimes import in the wrong order.
Fixed some bugs with our MusicXML importer’s handling of cross-staff beaming in piano music.
In the syncpoint editor, inner-bar syncpoints no longer display the fraction (which was confusing and unnecessary), and their circles are smaller.
In the syncpoint editor, the notation’s playhead now properly autoscrolls during syncpoint tapping.
In the syncpoint editor, if you double-click a syncpoint to edit its bar number, you can now use the Escape key to cancel your pending change.
In the syncpoint editor, syncpoint deletion is much more intuitive. Previously, when deleting a syncpoint, we used weird logic in determining whether to alter the subsequent syncpoints.
Overall site design
Redesigned the “Account settings” page to be better on small screens, nicer looking and simpler to use.
Changed all file-upload pages to use the same design. And all file-upload pages now support drag-and-dropping files onto the page.
For people embedding Soundslice
The new flippable=0URL parameter lets you hide the “Flip video” button in Settings. Useful for instruments like piano in which flipped video is meaningless.
The new waveform URL parameter lets you control whether the waveform is visible at page load time.
If you use top_controls and have a video above your notation, our tooltips (e.g., for audio sources) will now go upward, not downward. This feels more natural.
The “Powered by Soundslice” logo looks better at super-small player widths.
Thanks for using our site, and please get in touch with feedback, as always!
Today we’ve launched a great new feature that several of you have requested: a “horizontal view” for notation/tab.
When you activate horizontal view, the Soundslice player will continuously scroll notation horizontally — rather than spreading it over multiple lines (staves) as in paper sheet music.
Whether you prefer this is a matter of taste, of course. The advantage is a more compact interface, and the disadvantage is that you see less music at one time.
To activate horizontal view, use the advanced settings menu — which is also new today! Click the Settings button at the bottom right of any Soundslice score, then click “Advanced.” You’ll see a few options:
Use “infinite horizontal view” — toggles the aforementioned horizontal view.
Keep playhead at top of screen (or Keep playhead at left of screen, if you have horizontal view active) — controls playhead scrolling behavior. More on this below.
At the moment, your preferences are not saved between page loads — you’ll have to set them each time you want to change a score to horizontal view — but we plan to make these preferences saveable.
When horizontal view is active, you can scroll notation by dragging the scrollbar at the bottom of the player, or using a mouse scroll wheel, or using a two-finger drag on a touchpad.
You have two options for playhead scrolling with horizontal view
If you check Keep playhead at left of screen, the playhead will stay in one place while the notation moves underneath. This can make the music hard to read if you’re trying to learn it, but it’s useful for some purposes.
If you leave Keep playhead at left of screenunchecked, then the playhead will scroll through one “page” of music at a time.
Astute Soundslice users will notice there’s also a new option for scrolling in the normal (non-horizontal) view: Keep playhead at top of screen. Here’s what that does:
Default scrolling behavior, without that checked, is to ensure the currently playing bar and the next bar are both visible on the screen at all times; in practice, this results in the playhead being near the bottom of the screen.
If you check Keep playhead at top of screen, the currently playing bar/stave will always be at the top of the screen. You may prefer this second approach if you’re used to reading from paper sheet music.
Finally, for those of you embedding Soundslice, you can tell your embedded player to default to horizontal view by using the new horiz=1URL parameter.
As always, Soundslice has gotten lots of tasty new features and fixes lately. Here’s what’s new:
2017 NAMM Show
We’ll have a booth at this week’s NAMM Show in California. (Hall E, booth 1670.) If you’re coming to the convention, please drop by and see us — we love to meet our customers in person.
Auto-hiding of empty staves
Our player now automatically hides empty staves. If your Soundslice score has multiple tracks, and one of the tracks has no music in a given stave (row) of music, we’ll automatically hide that stave.
This makes for a much more efficient use of vertical space. You no longer have to scroll through meaningless empty staves for instruments that don’t contain any information.
If you embed Soundslice in your own site, you can disable this behavior with the new collapse_empty=0 URL parameter, documented here.
With music that contains many notes in a single bar — say, lots of 16th and 32nd notes — you may have noticed that the Soundslice player would automatically reduce the size of the notation, to make sure all the notes fit in the screen. Otherwise, the notes would overflow the width of your browser window.
This behavior was unintuitive, though. Several customers had emailed us, assuming it was a bug because they weren’t able to make the notation bigger.
Now, we have a better solution. If notation doesn’t fit in the current browser window, first we’ll try to “smoosh” the horizontal spacing in that bar, to put the notes closer to each other. If that works, then great — no need to auto-change the zoom level. But if the “smooshed” notes are too hard to read, then we’ll resort to the old way, zooming out.
We’ve made many changes to many pages on our site to make things work and look better on mobile devices.
Of note, the score manager is much easier to use on smartphones, with more than a dozen usability improvements for touch devices and small screens.
Our player keeps getting better:
Subtitles (if available) are now displayed on our player’s narrow view (i.e., when the video is above notation). Previously they were only displayed if the video was on the left of notation.
If you spend a long time in the Soundslice player without reloading, you might have run into a problem where the video stops working due to the URL expiring. This is now fixed — you can stay in the player as long as you’d like.
For touchscreen devices, we fixed a usability issue when using a two-finger swipe to zoom in/out. Sometimes this would inadvertently create a loop, depending on your exact finger movement.
We fixed a mobile usability issue in the Settings menu, where clicking on an audio source caused a shift in the UI.
The waveform display is now crisper on high-definition screens such as Apple Retina.
Our “Print” feature now uses a bigger font size. The printed music is much easier to read.
You can now disable the visual piano keyboard for any score that you own. Open track controls for the given instrument and uncheck the “Virtual keyboard” checkbox, then click Save.
We fixed a bug in our calculation of directions (Da Capo, Da Segno, etc.) that happened in some obscure cases.
We polish our rendering engine on a nearly daily basis, so printing a whole list of recent changes would break the Internet. But here are the highlights:
Fingering now uses a more readable font. We also added several bits of magic to the automatic positioning algorithms to make the numbers more readable within staff lines.
Right-hand fingering (i.e., for guitar music) is now consistent with left-hand fingering.
Tempo markings now put the text before the metronome marking.
Ties now have better spacing for chords that contain the interval of a second.
Same goes for ties that continue on a new stave into a chord that contains the interval of a second.
We greatly improved the positioning of rests in multi-voice music.
Alternate endings now have a more unified look, using the same numeric typeface as time signatures.
Directions such as Da Capo now use a larger typeface.
Palm mute and “let ring” are now larger and have a nicer dashed line.
For slides into notes, the slide symbol no longer crashes into notes in chords that contain the interval of a second.
This was a “long time” coming: we now support breve notes (double-whole notes).
Score manager / course manager
You can now move folders! Nest them under another folder, move them to the top-level, etc.
Many pages in the score manager now feature “breadcrumbs” at the top of the page, for easier navigation.
After you make changes in the score manager, we used to redirect you to the main score manager index. Now, we redirect you to the folder/page you were previously on. Much nicer.
The score manager now has a “Clear notation” feature for each score. This will erase all notation in the score, in case you want to make it notationless.
The score manager now has a “Download audio” link for each audio recording. This lets you quickly download the MP3.
For courses, you can now add “Intro text for students” — optional text that’s displayed above the list of lessons.
For courses, we removed the ability to set a date for a lesson. Nobody was using that feature, and you can simply use the lesson notes or score title to insert a date.
We fixed a MusicXML importer bug with accidentals in non-standard tablature tunings.
We fixed a MusicXML importer bug with cross-staff beams containing chords.
We fixed our MusicXML importer to detect segnos and codas that we weren’t already detecting (MusicXML has several ways of coding them.)
We fixed our MusicXML importer to handle bad chord names as generated by Notion.
We improved our MusicXML importer to detect bad ties in tablature — where the first note in the tie has a different string than the second note in the tie.
Our MusicXML importer now detects a few other common ways that people specify metronome markings.
For percussion music, we improved our importer to use proper sounds in the cases where we weren’t already using proper sounds.
You can use our new enable_print=0 URL parameter to disable printing for a score. Yes, you can already disable printing for a score in the score manager, but this gives you more flexibility. For example, one of our partners is using this to limit the number of times a score is printed by a given customer.