PDA

View Full Version : Only sending one message



seamus
01-15-2010, 12:36 AM
So I'm running FingerPlay on my droid and connecting to OSCulator - no problems there. I receive messages for all the controls, etc. The problem is, when i assign a message a "Midi Note" and choose the actual note, it will only send one message to Garage band. I.E. I assign "A4" to a pad in FingerPlay, hit the pad and it plays A4 once. Every time I hit the pad after that, nothing. The indicator still flashes in OSCulator, but no sound. If I change the note, it works one time again. I'm running OSX 10.5.5 and GB 08.

camille
01-15-2010, 09:50 AM
Hello Seamus,


Thanks for reporting back this problem to me.

I don't have an Android for testing, so I will need a bit of help from you to solve this issue.


The first thing I need to know is the version of OSCulator you are running. If this is not the latest version (2.9-rc3), please update the software by downloading this version on the website (since it is a release candidate, there is no automatic update path from 2.8.8).


Now, I would need you to open the Console application found in the /Applications/Utilities folder. In OSCulator, select the message the is received from FingerPlay, and set the Event Type column to "Console Log", and in the Value column, choose Simple Log.

On FingerPlay, hit a few times the button. What do you see in the Console log?


My guess is that FingerPlay doesn't send correct OSC and that OSCulator only receives values above 0.5, which causes the note to be triggered but never released. When you change the note, you actually reset this trigger, thus allowing a note to be played again.


Best,

Camille

seamus
01-15-2010, 10:13 AM
Well, I've tried running both versions, hoping that one or the other would work. No go. Here's what console log says:


1/15/10 3:17:11 AM OSCulator[3569] /fingerplay/control/32: 25

1/15/10 3:17:11 AM OSCulator[3569] /fingerplay/control/32: 25

1/15/10 3:17:12 AM OSCulator[3569] /fingerplay/control/32: 24

1/15/10 3:17:12 AM OSCulator[3569] /fingerplay/control/32: 24

1/15/10 3:17:12 AM OSCulator[3569] /fingerplay/control/32: 27

1/15/10 3:17:12 AM OSCulator[3569] /fingerplay/control/32: 27


It doesn't seem like it's a problem with the fingerplay/osculator connection because the indicators in osculator show everything being pressed just fine. It's particularly strange that it sends one message successfully. I just got this computer so as soon as I can install ableton on it, I'll let you know if it works better with that.

seamus
01-15-2010, 10:23 AM
Ah, wait... I see what you're saying. Is there a way I can adjust that on the osculator side? I don't think fingerplay allows me to change the messages.

camille
01-15-2010, 01:39 PM
if you know the min and max of what FingerPlay is sending, you can put those values in the Input Min and Input Max columns of the Scalings Page. The Scalings Page is accessible from the View menu.

seamus
01-15-2010, 05:38 PM
Well, nothing so far. I'm not quite clear on how to fix the problem though. Should I cap the signals? Any recommended values? I've tried playing with some various settings, but nothing seems to work.


Dang!

camille
01-15-2010, 08:01 PM
It would be useful to know what is the extent of the values your control is sending. Then report those minimum and maximum values into the Input Min and Input Max fields.


When you have done this, you should open a Quick Look window on the message of your control, and see what values are displayed. If the new extent ranges from 0 to 1, then you are good, knowing that a MIDI Note (and everything that can be triggered in OSCulator), needs the values to cross 0.5 from down to up for a Note to be triggered, and up to down for the Note to stop.


Please let me know of your findings, hopefully we'll manage to get this work!

zosoaudo007
03-23-2010, 05:06 AM
Hey. I had a similar issue here. Finger play was actually sending values between 0 and 127. Once I changed the scaling of the input for the XY controller to 0 to 127 everything worked absolutely perfectly. Unfortunate hiccup, but after about an hour of troubleshooting everything is good!

zosoaudo007
03-23-2010, 05:11 AM
Update: I still can't seem to get this to work with the pad buttons. As he said it only plays one note.


Upon touching it (with Input min at 0 and max at 1), you get values between 10 and 50 in the console. These are rough values. I'm not really sure how to scale this, and there doesn't seem to be any consistency in the values. Each press of the button will generate a different number. Obviously the best thing would be to have OSCulator be able to tell when the button is depressed and released, but it isn't consistent with that either.

camille
03-23-2010, 09:51 AM
The input min and max scaling is the right idea, tho.

Note triggers happen when the values crosses from down to up the half of the input range.


You need to know what Finger Play sends to OSCulator in order to use it, or it won't be useful.

Is it a note number? If yes, then use "Edit->Demux" to separate the values from the argument and you will have triggers for each individual notes.

Please be more descriptive.


Cheers,

Cam

zosoaudo007
03-23-2010, 02:19 PM
Hey camille. I am being as descriptive as I can. I have to be honest...I'm not certain what information Fingerplay is sending to OSCulator. I can see a range of values in the console log, but I have no idea what the min and max of those values are. As I said, whenever I depress the pad it seems to send out somewhat random numerical values.


If it is any use, here is the FingerPlay link (http://thesundancekid.net/blog/fingerplay-midi/).


I believe that it is not sending out a note number. When the control parameter is selected the Demux is greyed out. I am almost positive it is sending out OSC information, but nowhere on the site does it say that. Is there a test I can do which will tell me what kind of information it is sending out?


Edit: I overlooked it earlier. The link I supplied states that FingerPlay sends either OSC information or it's "own FingerPlay format". When setting up FingerPlay last night (it was late, I forgot) I set the server type to OSC server. So I assume that means FingerPlay is sending OSC information to OSCulator

camille
03-23-2010, 03:22 PM
Fair enough, Zo!

Well, you may know that already but I think it would be easier to monitor the values with a Quick Look window rather than the console log, unless you have started the application on the command line.


By quickly looking at FP's source code it looks like it is really some kind of MIDI data written on OSC message.

For example, I believe /fingerplay/control/27 with argument 35, means control change 27 with value 35.


Sorry to say that, but I think you should directly ask flat20, the author of FP, on its blog, he seems to be using FingerPlay with oscltr.


Best,

Cam

zosoaudo007
03-23-2010, 04:04 PM
I emailed him shortly after my last post. I will post my findings back here to see if we can shed some light onto this issue.

camille
03-23-2010, 04:40 PM
Thanks!

Hopefully we'll know what those values are about :-)