update: apparently it’s a bug which is caused by the gray-scale-slider in the color settings of the mmp-objects. i reported it to daniel iglesia (mobmuplat.com) who’ll add a tracking bug for this issue on github.
cheers

/thread colsed

btw, here’s one of the mmp-files. maybe someone can open it, add some label-ojects, insert some random-text (with different sizes and font-styles) and then try to save it.
regards, p

game_labeltry_v.1.2.mmp

hi!
i have a big problem here and maybe someone knows how to fix it or can give me a tip:
i’m using the mobmuplat-editor and the app itself since a while now and up until yesterday everything worked quite well.
i’m designing an interface for a simple app on ipad. so, i’m using the mobmuplat-editor on my macbook in connection with pure data (works fine) and transfer the files to the
mobmuplat document folder on ipad to run them via the mobmuplat app (also works fine).

my problem: suddenly the mobmuplat-editor on my laptop does not save my .mmp files anymore. i can open a file but as soon as i add new elements (especially „label-objects“ for text) and try to save, the editor „freezes“ - it won’t save the changes i made and after 1-2 minutes i have to force-quit the program and the changes are lost.
it’s really strange because the patch itself is not very large or complicated, just some buttons/toggles in different colours, some sliders, some labels (the ones i already have are working fine).

i already tried to change the file directories, i tried to delete/reinstall the whole mobmuplat package, restarted the computer, even tried it on another macbook - but always the same problem.. as soon as i add label-objects and try to save afterwards, it loads and loads and then i have to force-quit the program. even if i make a complete new file and add some buttons or other objects.. when i add a label-object, i can’t save anymore..

does anyone know, what’s the problem? any suggestions what i can try? i’m really thankful for all
your help,
p

hi!
many thanks for your replies. it seems that the problem is more complicated than i thought. i will get back to the issue as soon as i have more time. meanwhile thank you for your tips!
best, p

hey folks!
i have a little problem here:
i’m trying to interpret and use data coming into pd from another program (namely mobmuplat). the object sending the data is a grid consisting of 3x4 buttons/toggles. the grid is named „/grid“.
when i hit one of the buttons in the grid mobmuplat sends data like „/grid 0 0 1“ - meaning that the first button (0) of the first row (0) was activated (1).
pd obviously receives the data like „ 0 0 1“ - because when connecting the receive-object of the grid with a print-object, the log-screen says: „print: 0 0 1“
for me this data seems to be a message that corresponds to (x-position $1, y-position $2, on/off $3).

now, how can i readout such a message to seperate the 3 values in order to know which button got hit? is there maybe an object to simply compare the incoming message with some self-generated messages to see if they match?

i’m thankful for all help and information!

Hey guys, thanks so much for your replies! This really helps me to make progress! You’ll probably hear from me again soon

Hi there!

I’m quite new to pd but getting more and more into it as I’m trying to build a simple game/app, where users must trigger sound-samples in a certain order and (most notably) at certain points in time. The samples are triggered with bangs and since I edited them by myself, I know the exact length of every sample.

Now let us assume we have 4 samples, each of them with a length of 1200ms and each sample has its own bang to trigger it. These bangs get their input from „buttons“ which the user can hit via a graphical user interface (I built this GUI with MOBMUPLAT, a GUI-editor which interacts with Pd patches). If the bangs are triggered with exact timing, the 4 samples will add up to a musical sequence.

The first bang starts sample1 - after 1200ms the second bang (= button on the interface) shall be hit to start sample2 and so on.. it’s obvious that the user will not hit the buttons on the interface with an accuracy of single milliseconds, so here are my questions for the pd patch:

1. How can I „read out“ certain points in time, after a bang got triggered? e.g. after the first bang was hit, how much time (in ms) has passed until the second bang got hit? And can I „store“ and „recall“ these values in any way?

2. Is it possible to define a kind of „time window“ in ms? e.g. after the first bang was hit, the second bang has to be hit within 1150-1250ms to trigger something, or else (if the second is triggered too soon/late) nothing will happen..

Hope this explanation of my problem is not too complicated. Any help would be much appreciated!