Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting USE_AUDIO_INPUT to true causes NS1 Nanosynth to hang after 10s #32

Open
dturner opened this issue Aug 24, 2017 · 7 comments
Open

Comments

@dturner
Copy link

dturner commented Aug 24, 2017

Steps to reproduce:

Expected result:

  • Sawtooth wave is played out of PIN 9 whilst the nanosynth has power

Actual result:

  • Sawtooth wave stops playing after around 10 seconds, and the device becomes unresponsive to MIDI input (no LED flashes when notes are sent)

Note: After problem has occurred to reflash the nanosynth you need to hold down the reset button, and release it only when the new sketch is shown as "uploading" in the Arduino IDE.

@sensorium
Copy link
Owner

sensorium commented Aug 25, 2017 via email

@dturner
Copy link
Author

dturner commented Aug 28, 2017

Rather than optimising the NS1 sketch I just tried the Mozzi Audio_Input example. I did this because it has a minimal amount of code in the updateAudio method:

int updateAudio(){
      int asig = getAudioInput(); // range 0-1023
      asig = asig - 512; // now range is -512 to 511
      return asig;
} 

I tested on 3 boards: NS1 nanosynth, normal Leonardo board and an UNO r3.

On all 3 I was unable to hear any output from PIN 9.

@sensorium
Copy link
Owner

sensorium commented Aug 29, 2017 via email

@dturner
Copy link
Author

dturner commented Aug 29, 2017

My audio source is the nanosynth which generates a 5V square wave. The nanosynth also provides a 5V supply to the arduino.

@dturner
Copy link
Author

dturner commented Aug 29, 2017

@sensorium
Copy link
Owner

sensorium commented Sep 5, 2017 via email

@thomasfredericks
Copy link

There are known issues with Mozzi on Leonardo using Arduino IDE after 1.0.5.

@sensorium is there an issue or a fix for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants