Page 1 of 1
Getting good, but apparently not THAT good !
Posted: 24 Aug 2013 22:59
by Glennzone
Oh, this is seeming so stupid, but the attached jzml, as simple as it is, shows a simple pads object and a monitor object. When you press the button, the monitor cycles through values of 1, 2, 3, 4, and then starts over.
I just want to be able to send this value over OSC, and I can't figure it out !
help !?
jzml attached
Thanks in advance. I know youz guyz will come up with something.
Re: Getting good, but apparently not THAT good !
Posted: 25 Aug 2013 10:07
by Softcore
????? You are having a blonde moment I guess! lol
Just map the bank custom expression inside pbank pad object and you are done.
Re: Getting good, but apparently not THAT good !
Posted: 25 Aug 2013 10:19
by Softcore
Also....you can reduce the scripts to this:
Re: Getting good, but apparently not THAT good !
Posted: 27 Aug 2013 21:14
by Glennzone
Thanks for your assistance Softcore (as always), but it's still not sending the bank number out of the Lemur to my Max app. I can send data to and from for other items, but this one is not working for whatever reason.
Re: Getting good, but apparently not THAT good !
Posted: 28 Aug 2013 11:30
by Softcore
Did you actually "map" the bank custom expression and still doesnt work? -> set its lemur target and desired OSC settings?
Re: Getting good, but apparently not THAT good !
Posted: 28 Aug 2013 21:07
by Glennzone
As I understand it, the attached screenshot shows what I believe it should be, but when I look at the data coming into my udpreceive object . . . nuffin'.
Again, I can touch other controls in Lemur, and I see the different data coming in. Just not from pBank/bank, the Monitor or Text objects. The pads object communicates the x value, but not the pBank's bank value, even if I set the x value mapping to none.
Re: Getting good, but apparently not THAT good !
Posted: 29 Aug 2013 19:32
by Glennzone
Before going any further, I just wanted to share with the forum the solution I arrived at. It may not be the only one, but it's for the catalog nonetheless.
I'll think you'll see by the attached graphic. When the CustomButton is pressed, it cycles through 1, 2, 3, 4, 1, etc., which updates the Monitor object. It is the Monitor object's BankNum variable which accepts the bank number, and sends it out OSC.
It's working like a charm now. Again, thanks to all who post their answers, as well as those who guide us to the solutions.
Thanks,
Glennzone
Re: Getting good, but apparently not THAT good !
Posted: 04 Sep 2013 13:50
by Softcore
So weird...it should work as you have it set in your first image - example! I really dont have a clue what's wrong!