Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Blank screen in OS X El Capitan, errors in Processing

Open
#42 12 comments 0 reactions 1 assignee View on GitHub

@codingjoe is already working on this.

Since Oct 30, 2016.

Assessment

This issue has not been assessed yet.

Description

bug

Hi,

I'm trying to test MusicBeam on MacBook Air/OSX El Capitan with projector set as second monitor, and it's not working.

It's giving a blank/black main screen with no UI or anything at all.

I've tried opening the MusicBeam.pde in Processing, and installing the libraries as described in the readme file, and it gives errors when running in Processing which make me think one or more library is not loading correctly - eg. line 26 "Stage stage = null;" give the error "The class "Stage" does not exist", and likewise for many classes thereafter.

Any help appreciated.

Thanks,

Andy

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/38783790-blank-screen-in-os-x-el-capitan-errors-in-processing?utm_campaign=plugin&utm_content=tracker%2F444396&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F444396&utm_medium=issues&utm_source=github).
Dominant language
Processing
Stars
294
Forks
53
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codingjoe/MusicBeam

All issues in codingjoe/MusicBeam

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.