Hello! This is my first post on the forum.

I am in the process of designing an RJDJ scene and need some help.
I have a small test patch that I am working which will output a different frequency sound whenever a different part of the iPhone screen is touched.

Basically I have a .JPG which is 320 pixels square. This is then divided up into 4 different coloured squares which are 160 pixles square.

Heres the logic:

If touch value on x-axis <160pix play 440hz (Bottom left square)
If touch value on x-axis >160pix play 880hz (Bottom right square)

if touch value on y-axis <160pix play 440hz (Bottom left square)
if touch value on y-axis >160pix play 1320hz (Top left square)

I can configure the patch to play these sounds using moses objects and they work fine

But here is my problem:

if touch value on x and y-axis is > 160pix play 1760hz (Top right square)
Only when both x and y values are more than 160pix is the patch aloud to output a sound. However I can not think of which objects/design to use in order to meet these conditions.

I have included the patch so you can see what I have been doing so far.

Thanks for your help

http://www.pdpatchrepo.info/hurleur/_mainforforum.pd

Hi,

There's actually an object in the rjlib that might help you a lot. [m_touch2grid] will divide a x,y pair of coordinates into a grid. Instantiating it as [m_touch2grid $0-grid 2 2] will output 0 (Top left), 1 (Top right), 2 (Bottom left), 3 (Bottom right).

A few things to remember:

I would suggest using [r_#touch] instead of the touch receiver to ensure compatibility for the future (currently it's just a wrapper).

(0,0) on the iPhone screen is in the top left hand corner. You might want to reverse your y-axis logic.

[rj_image] can be used to display images when touched (placement is done from the center of the image).

Hope that helps.

Just realised you had that in your patch. Does it not do what you want?

Btw, there's a bug in your code that means the y coordinates are always replaced by the x coordinates due to the order of the [unpack f f f]. This means the y axis is essentially doing nothing.

Jwif thanks for your help. I have to say tho that I am going to need some more help as I really am a beginner at this stuff and jumped in at the deep end!

Anyways the [unpack f f f] bug is there a way to fix this?

I am already using the [r_#touch] object in my patch so all is good where thats concerned?

I have fixed the y-axis logic by starting with the lowest frequency at the top left hand corner instead of bottom left.

I am just about to test the [m_touch2grid] it looks kind of complicated but hopefully i will manage!

Thanks again for your help. If you can give me anymore advice or useful websites it would be greatly appreciated!

LF

@louisf1819 said:

I have to say tho that I am going to need some more help as I really am a beginner at this stuff and jumped in at the deep end!

The best way

@louisf1819 said:

I am already using the [r_#touch] object in my patch so all is good where thats concerned?

Ahh, ok. It's just that (and I know it's subtle) I saw [r #touch] (with a space) instead of the underscore. Maybe this should be something different.

@louisf1819 said:

I have fixed the y-axis logic by starting with the lowest frequency at the top left hand corner instead of bottom left.

I am just about to test the [m_touch2grid] it looks kind of complicated but hopefully i will manage!

I think [m_touch2grid] would simplify the logic you already have there. Check out the help patch, it has an example of what you want to do. Use

to trim off the prepending '1' value, then unpack the x,y coords into [m_touch2grid]. The last outlet will give you the index of which square is currently being touched. Connect that to a [sel 0 1 2 3] to bang the different frequencies.

Jwif,

Massive thanks for your help, I have been able to get my test patch working! After some time and head scratching the penny finally dropped

All is working well for now and the design of the main scene is going to plan. I am documenting the build as I go as its for a Uni project. I hope to have it finished for the end of september, so I will let you now the final outcome.

Thanks again for the help

LF