Show Posts
Pages: [1] 2 3 ... 9
1  Forum 2005-2010 (read only) / Forum / Re: out of Pins..! on: May 27, 2010, 01:50:11 pm
the forum is clearly running out of pins
2  Forum 2005-2010 (read only) / Troubleshooting / Re: Bitcrusher problems on: May 31, 2010, 10:34:44 pm
hey FJ, so the code is over my head as i have never done anything near that complex. But after giving it a quick look, it looks like on the "interface.h" tab there are the pins defined. i don't know what bitcrush, bitshift and such do, are they maybe inputs? you can change the numbers of them to the pins you want them to be (as long as they aren't already in use).
also there is the "dsp.h" tab that is left and right defined, swapping those might give you the change in output you are wanting.

again, i don't claim to know what i'm talking about, but that's what i would try messing with.

good luck!!
3  Forum 2005-2010 (read only) / Troubleshooting / Re: how to send once then stop sending? on: March 10, 2010, 03:33:04 am
because i want it to send the message one time per trigger.

when the value is triggered as it is it sends out the message constantly slamming my midi device with non-stop messages, rather than just the one message to turn the function on.

basically i want it to operate as if it were a button sending an on then off message.
not like: on on on on on on on on on on on on on on on on off off off off off off off off off off off off off off off off off off off off off off....
4  Forum 2005-2010 (read only) / Troubleshooting / Re: how to send once then stop sending? on: March 10, 2010, 03:27:14 am
i actually need it to happen over and over (each time the "touchX" value triggers it)

i tried the setup method and that didnt work out.

5  Forum 2005-2010 (read only) / Troubleshooting / how to send once then stop sending? on: March 10, 2010, 02:58:02 am
I can not figure out how to get this CC message to just send one time.
The message is continuously being sent out as either a 0 or 127.

This is the code i am working with.
Code:
if(touchX > 127)
{MIDI.sendControlChange(22,0,1);   //needs to be sent only once
}
else
{
MIDI.sendControlChange(22,127,1);   //needs to be sent only once
}

isn't there some way to say "just send once" or something to that effect?
6  Forum 2005-2010 (read only) / Troubleshooting / MIDI "Panic Button" - with MIDI Library? on: March 06, 2010, 04:04:27 pm
is there a panic button function in the MIDI Library?
i haven't been able to find one.

or is there another way to send an "all note and CC messages off" with the press of a switch?
7  Forum 2005-2010 (read only) / Syntax & Programs / Re: Laser Harp source code help on: April 11, 2010, 03:03:17 am
yeah man that is a sweet laser harp and inspired me to build one someday.
ive read that 150mW lasers can burn your hand but i wouldn't want to use a laser that was too weak to easily see.
8  Forum 2005-2010 (read only) / Syntax & Programs / please help me understand button functions on: April 21, 2010, 07:48:06 pm
okay, i always end up running in to this problem and i do not fully understand what/why i do the things i do.

i pretty much always end up dealing with midi projects with the arduino.

here is an example of what the problem is:
Code:
if (note1.uniquePress()) {
Serial.println("Sending note");  
  }
  else {
Serial.println("Turn off note");
  }
the problem is, the else command to "turn note off" slams my midi device (or in this case the serial monitor) with constant messages.
using AlphaBeta's button library with the "uniquepress" function makes it so the send note message is sent only once, so that part is good.

when i have 10 or so buttons all shooting out constant note off messages it causes my midi devices to freak out and hang up.

it would be awesome if i could fully understand how to press a momentary button and have it send just one message, then then i release the button have it send out just one different message.


9  Forum 2005-2010 (read only) / Syntax & Programs / Re: strange button problem... on: April 10, 2010, 11:05:27 pm
wow, thanks guys not that makes sense!
great to know why i should do something rather than just knowing what to do.
10  Forum 2005-2010 (read only) / Syntax & Programs / Re: strange button problem... on: April 09, 2010, 11:27:44 pm

actually...i guess i don't really understand why it makes a difference.
i just know that i will be using the -- or ++ int he front now.

would you mind explaining whats going on? it would be cool to truly know what was going on.

thanks cr0sh!
11  Forum 2005-2010 (read only) / Syntax & Programs / Re: strange button problem... on: April 09, 2010, 07:07:18 pm
that was exactly the problem!

thanks so much, i could not figure out what was going wrong, and it was so simple!
12  Forum 2005-2010 (read only) / Syntax & Programs / strange button problem... on: April 09, 2010, 05:50:38 pm
hey guys, so i have 2 buttons, one does program changes up and the other is program changes down, one interval at a time.

the problem is this:
lets say i am on program 10
i press program down, it goes to 9, press again it goes to 8.
now i want to go back up to program 9
i press program up and it will go down to 7, press again 8, press again 9.
then if i press program down it will go up one before going down and so on.
hopefully that makes sense.

i am using AlphaBeta's button library for the unique press function.

this is the section of code in question.
Code:
Button progUp = Button(11,PULLUP); //program up pin 11
Button progDn = Button(12,PULLUP); //program up pin 12
int prog = 114;



    if(progUp.uniquePress()){
    MIDI.send(PC,prog++,0,1);
}
   if(progDn.uniquePress()){
    MIDI.send(PC,prog--,0,1);
}

*note that is not the entire sketch, just the button assignment and loop section.
13  Forum 2005-2010 (read only) / Syntax & Programs / Re: problem with else command on: April 06, 2010, 02:44:26 pm
thanks Paul, that is exactly what i am after.
i have sent you a PM
14  Forum 2005-2010 (read only) / Syntax & Programs / Re: problem with else command on: April 06, 2010, 01:01:04 pm
hey Paul,
the screen is mapped to give out readings from 0 up to 126 and will send out a stable reading of such if the finger is held still.
when you release the screen the value goes up to 127 (or more) and sends the midi command with the 0 velocity to turn the command off. that part works good enough since the value doesn't change while the screen isn't being touched.

it is just that every +1 or -1 of the screen value re-triggers the midi cc command of 127 resulting in a choppy sweep between the range.
15  Forum 2005-2010 (read only) / Syntax & Programs / problem with else command on: April 06, 2010, 05:46:33 am
hi guys,
so i have been trying to get this last problem sorted out the last few days with no luck.
i am trying to get this else command to just send the midi message one time regardless of the changes in "touchX".

here is the section of the sketch i am stuck on:
Code:
if(touchX > 127 && touchX != touchXOld)
{
  touchXOld = touchX;
  MIDI.sendControlChange(92,0,1);
} else
[glow]  if(touchX < 127  && touchX != touchXOld)
{
  touchXOld = touchX;
  MIDI.sendControlChange(92,127,1);[/glow]
}
it reads the values of a resistive touch screen, that is where the value of the "touchX" comes from.
basically i need the above highlighted part to just send the midi message one time but it is being resent every time there is a change in "touchX".
i have tried everything i can think of.
Pages: [1] 2 3 ... 9