(03-21-2022, 09:25 PM)Jens Noritzsch Wrote: There are two threads on MatLab in this forum: https://phyphox.org/forums/showthread.php?tid=716 and https://phyphox.org/forums/showthread.php?tid=796 – and a search text field at the top…

You could also find some examples on the net, for instance, at https://uk.mathworks.com/matlabcentral/fileexchange?q=phyphox

(11-06-2021, 08:40 PM)Romaxx Wrote:

(11-05-2021, 01:59 AM)Sebastian Staacks Wrote: I have tracked the problem down to an unexpected (if not buggy) behavior of requests: It form-encodes the pipe "|" no matter how you pass it to get(). The docs (https://docs.python-requests.org/en/master/user/quickstart/#more-complicated-post-requests) specifically say that it should not encode it if you pass the url or the parameters as a string, but it still does so and phyphox at the other end does not decode the form encoding (why should it - it's not an endpoint for a HTML form and it still is a valid HTTP request).

So, after searching for ways to circumvent this problem, I ended up using urllib3 instead and this seems to work:

Code:

#MIDI configuration
M_OUTPUT = "Midi Through:Midi Through Port-0 14:0"
M_CHANNEL = 0
M_CONTROLS = [1, 2, 3, 4] #You can send on different CC channels
# M_CONTROLS = [70]

#phyphox configuration
PP_ADDRESS = "http://192.168.2.194:8080"
PP_CHANNELS = ["accX", "accY", "accZ", "acc_time"] #If using different CC channels, define multiple phyphox buffers
# PP_CHANNELS = ["accY"]

from urllib.request import urlopen
import json
import time
import numpy

value_temp = 0

time_update = 0
count = 0
while True:
    if count == 0:
        PP_CHANNELS_def = ["acc_time=full","accX=full","accY=full","accZ=full"]
    else:
        PP_CHANNELS_def = ["acc_time=" + str(time_update), "accX=" + str(time_update) + "|acc_time","accY=" + str(time_update) + "|acc_time","accZ=" + str(time_update) + "|acc_time"] #If using different CC channels, define multiple phyphox buffers

    url = PP_ADDRESS + "/get?" + "&".join(PP_CHANNELS_def)

    response = urlopen(url).read()
    data = json.loads(response)

    time.sleep(0.04)
    count = count + 1
    time_update = count * 0.04;

    # Uncomment to send pitch bend
    time_value = numpy.array(data["buffer"]["acc_time"]["buffer"])
    value_x = numpy.array(data["buffer"]["accX"]["buffer"])
    value_y = numpy.array(data["buffer"]["accY"]["buffer"])
    value_z = numpy.array(data["buffer"]["accZ"]["buffer"])

However, there is one other thing you probably want to change: You should not use "time_update" in your request, but the latest value you received in data["buffer"]["acc_time"]["buffer"] in your previous request (so, the last value in "time_value"). Otherwise, your time_update will eventually get out of sync with phyphox (well, it will probably start out of sync as you cannot start the script and the measurement at exactly the same time) and you will either get duplicates (imagine your time_update is 10 seconds behind and phyphox will send you everything from the last 10 seconds every time) or miss values (imagine it is a few milliseconds ahead and requests before a data point with that timestamp exists). The whole point of this function is to tell phyphox which is the last value you received, so it can send you anything after that.

Thanks for your answer.

I did not try it so far, but I will (probably tomorrow).

Edit: I now tested your code and it works as expected. Thanks for this!!!

But, can you tell me what you think about my first Question in my last post, the one with the link?

Thanks again!

(03-29-2022, 05:36 PM)Jens Noritzsch Wrote:

Code:

<audio>
  <output>recording</output>
  <output component="rate">rate</output>
</audio>

The audio data is in the buffer “recording”. In contrast to other sensors, audio data has no time stamp associated to it. That's why phyphox goes to some length in the analysis block to create some time buffer.

Code:

<graph label="Audio Data" labelX="Time" unitX="[[unit_short_milli_second]]" labelY="Amplitude" unitY="[[unit_short_arbitrary_unit]]" scaleMinY="extend" scaleMaxY="extend">
  <input axis="x">subtime0</input>
  <input axis="y">subdata</input>
</graph>

Hm… our remote access indeed plots “subdata” against “subtime0”.