@Shabroy Not sure, but in the [expr] object $f1 is the left inlet... lat
and $f2 is the right inlet....... lon

So reading the values from left to right in [expr] in my example "maybe.pd"
1.12 is the minimum GPS value for latitude to trigger playback
5.12 is the maximum GPS value for latitude to trigger playback
7 is the minimum GPS value for longitude to trigger playback
14.8 is the maximum GPS value for longitude to trigger playback

Have a look at where you are and the values that [r #loc] is sending.

Both latitude and longitude have to be in range for playback to be triggered and you need to change the values to encompass (good pun) the place where you will be when it should trigger.

Hoping that helps as I have no way to test your patch even if you upload it.
Maybe someone else could help with that if you cannot get it working.

Also maybe you need a path set to your sound file on the iPhone.
That is mentioned somewhere in the Doc for PdParty.
David.

@Shabroy In PdParty_composerpack\PdParty_composerpack\lib\pd you have playback.pd which needs to be triggered for playback when your parameters from loc are in range...... and only once or playback will be triggered repeatedly by incoming data and restart the file.
So you need to send to [r #transport] the message
[playback filename.extension(
|
[s #transport]

You need to control that with a patch something like..... maybe.pd
[expr if ()] is the geofence for lat and lon... outputs 1 for inside, 0 for outside.... (logical true/false)....
David.

@Shabroy I was mistaken about the "underline".
It is used in patch names to differentiate them from sends and receives.
[r_#name] for the patch but [r #name for a receive.
You found that patch as [main] in PdParty_composerpack\PdParty_composerpack\tests\pdparty\Loc in.......> http://danomatika.com/code/pdparty/PdParty_composerpack.zip

It is probably the "Detailed Instructions" in https://danomatika.com/code/pdparty/guide that need to be followed...
As I understand it when the patches are uploaded to ios the patches and GUI's cannot be directly connected by cords.... all connections have to be made using sends and receives.
David.

@Shabroy I don't have an ios device so I am flailing around in the dark.
But you should try [r_#loc-help] which has a spigot to open for data to flow (It seems that the format is definitely [r_#x] with no spaces).
And although these rj patches are useful for debugging it seems that the [rj_loc] object is required and is only created on an I-device.... presumably the same as the ios window screenshot (Loc ... see below) from the PdParty/Guide PDF.

I might read this..... https://danomatika.com/code/pdparty/guide ... when I get time.
It seems to explain such things...
And I imagine that this.....

... exists somewhere in the PdParty download......... https://danomatika.com/code/pdparty
David.

@impression You are running this on an RPI so have a look at this thread... https://scsynth.org/t/limit-to-maximum-number-of-osc-messages-that-can-be-received-in-short-time/8641/6
The sysctl command will probably help.
David.

@c_c I think you will always have artefacts as the delay read point changes.
Even if you have 2 delays and swap (flip-flop) between them you will hear the change.
But if you crossfade between the 2 delays maybe your ears/brain will be deceived.
You will need to find a sweet spot for the length of the crossfade dependant on the range of the timing changes.
David.

@Shabroy It seems that you have to enable GPS in PdParty........
Chapter 3.2.5 here........ https://danomatika.com/publications/pdparty_pdcon_16.pdf
.... and then receive the data through an [r #loc] object...... then [unpack f f f] for lon, lat, accuracy.

You will find a lot of help on Github..... especially here...... https://github.com/rjdj/rjlib/blob/master/rj/r_%23loc-help.pd
It is old but should still be good.... and there are patches for generation too.
You should grab the whole rjlib here..... https://github.com/rjdj
David.

@raynovich Sorry to be late replying.... I have been away..
I suppose that not so many people share their projects, and often those that do just list the necessary libraries (if we are lucky).
But it is good practice to use a folder structure to group your own abstractions.... which of course the other person will need to run the main patch.
Here is an example that is about as complex (but complete) of an old shared library for GEM.
It can be found here..... https://github.com/extendedview/extended_view_toolkit
This is the structure.....

And this is how the paths were declared........

You can see how . and .. are used for paths in the help file for [declare]
But if you put all your abstractions in a folder "abs" then you only need a [declare -path abs] so that they are found in that sub-folder.
And you can of course add the libraries to your bundle and declare them as was done in the [init] sub-folder in extended-view.
They then used an abstraction..... [ev-main/ev_declare] in their patches (inside [pd init] ) to set the paths for all the examples in their project.
David.

@raynovich You had the same problem 5 years ago....
https://forum.pdpatchrepo.info/topic/13399/paths-and-organizing-pd-files-for-use/1
Using the [declare] object for libraries and externals in your patches solves the problem both on your computer and for when you share a patch.
It sets up a search using the standard paths.... so adapts to the Pd paths for each computer and OS.
Also it shows the other person which libraries they are missing.
It is a little more work, but future proof....
David.

@spluta No. [clone] is I think the only way.
You could use dynamic patching but for this purpose [clone] makes that redundant.
David.

@donnerbono You might also like this...... https://www.katjaas.nl/slicejockey/slicejockey.html
It needs extra libraries for Vanilla..
HCS
Zexy
nilwind

@jameslo I would use [coords( rather than [donecanvasdialog( as it is less "dirty". [pdcontrol] I have never tried.
I can't remember whether you need to exit from edit mode after the [coords( message.
David.

@jameslo Yes, I think so too......
It seems to have a tilt to archaeology... digging up blasts from the past.
I will have to put my "bad cop" hat on again.
David.

@nicnut Yes, as the [phasor~] output jumps it could output samples that jump from near 0 to near 1 or vice versa and that will produce clicks.
You could window each grain, or as I did here soft duck the output during the jump.
The effect is the same I think.
Microsound-granular.pd
See [s smooth] and [r smooth] for the duck.
David.

@crttrkix P.S. As well as passing arguments from [cue] to the name of the abstraction it contains, you can also pass arguments to it.
i.e. [cue 1 22 33 44]
contains
[whatever$1 $2 $3 $4]
where $2 $3 $4 inside [whatever1] resolve to 22 33 44 upon creation.
David.

@crttrkix "This demonstrates a bit of an inconsistency in their behavior (I don't know why this is) that is good to know.

It is just that [whatever] is an abstraction... that is another patch..... whatever.pd.... inserted into your patch.
[pd whatever] is a window within the patch that contains it..... useful for keeping a patch tidy but also to fix an order of operations and to set a different block size for resampling, and for processing audio at a different block size (right down to single sample processing).

And what @jameslo said..
David.

@crttrkix You can pass arguments, but not as part of the name.
$0 is not so useful, as when you want to send messages from outside the abstraction you can get it to declare its $0 value but that becomes complicated.
So it is easier to give each instance known arguments.
Arguments are passed down to sub-patches within the abstraction.
So probably.....

I have used the first argument directly in [expr]
Since some version of Pd the $1 would be automatically escaped within the formula of [expr] and made literal, so I have escaped it again to make it a variable as required in this case.

You can have as many arguments as you wish..... intteger and string....
Inside the abstraction use [symbol $1] to loadbang a string.
I tried to make a tutorial here.... https://forum.pdpatchrepo.info/topic/9774/pure-data-noob/4

For the sub-patch it is not actually useful as the sub-patch is just a window within [cue].... so all you have done is change the name of the sub-patch.
If you want a completely different sub-patch in each instance of [cue] then use another abstraction (a patch) instead.
[cue 1 34]

inside [cue] $1 becomes 1 (in an object) and [patch$2] becomes [patch34] which you have created as patch34.pd

But if the sub-patches are identical then pass arguments from the creation of [cue]..... as many as you need...
[cue 1 34 woof lala 12 rev delay]
Inside object names they will be resolved...... and not escaped.
David.

Should be here..... https://puredata.info/docs/developer/PdFileFormat ...... but the whole site is unreachable right now.
It used to be included in Pd extended source code..... another loss....
Here it is....... pdfileformat.zip
David.

@pepika32 [gemwin] should be an object..... not a [gemwin( message.
Hopefully it will then work as you expect.
David.

@Moothart The easy way will be to use [print] and you will see the value in the console even though a number box might not have time to show it.
Or you could use [sel 2 5 6 7 10] with bangs on the first 5 outlets and see the effect in the patch.
David.