OSC Receiver and Sender

[w_ellis]

I was thinking of Copperlan, the way a remote end can present a list of available parameters to choose from. But maybe I need to know the limitations of OSC better first.

Yeah, probably looking to walk before we can run I had a look into Copperlan a while back and from an implementation perspective it's a bit of a nightmare. Super complex and a lot of features that I imagine a tiny fraction of people would use.

[faxinadu]

Code: Select all

package c.oceanswift.scope1;

import android.support.v7.app.AppCompatActivity;
import android.os.Bundle;
import android.view.View;
import android.widget.Button;

import java.io.IOException;
import java.net.DatagramPacket;
import java.net.DatagramSocket;
import java.net.InetAddress;
import java.net.SocketException;
import java.net.UnknownHostException;

public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

       
        final Button button = findViewById(R.id.Randomizer);
        button.setOnClickListener(new View.OnClickListener() {
            public void onClick(View v) {
                    String udpMsg = "/0 12";
                    DatagramSocket ds = null;
                    try {
                        ds = new DatagramSocket();
                        InetAddress serverAddr = InetAddress.getByName("192.168.1.13");
                        DatagramPacket dp;
                        dp = new DatagramPacket(udpMsg.getBytes(), udpMsg.length(), serverAddr, 8000);
                        ds.send(dp);
                    } catch (SocketException e) {
                        e.printStackTrace();
                    }catch (UnknownHostException e) {
                        e.printStackTrace();
                    } catch (IOException e) {
                        e.printStackTrace();
                    } catch (Exception e) {
                        e.printStackTrace();
                    } finally {
                        if (ds != null) {
                            ds.close();
                        }
                    }
            }
        });
    }
    }

any hints why this isnt working? its a button on that is supposed to send on click

[w_ellis]

Sometimes there can be issues with firewalls, especially when sending across LAN. You might need to add an exception to a firewall on the listening PC.

I'm assuming you don't have any errors from the app? You could also use something like Wireshark to listen for the messages.

[faxinadu]

i don't have any compile errors but i have some debugger errors when clicking the button. its very much possible i have errors heh. yah im grabbing a sniffer, but imo my code is wrong

[faxinadu]

i think i got better java code now, but checking via the steps outlined in the link, it does not seem like anything is listening on port 8000 on my pc. i got the module open in sdk.

https://stackoverflow.com/questions/481 ... on-windows

[w_ellis]

The problem is that all those answers are talking about TCP. Listening on UDP is quite different. Mostly you just want to see if the messages are arriving on your machine now, which is where Wireshark comes in.

[faxinadu]

its showing udp answers too....

yeah im also with wireshark checking

[faxinadu]

aaaaa.png (180.33 KiB) Viewed 429828 times

so as far as i can see i am both transiting and receiving but nada on scope

[w_ellis]

Sorry, I only skimmed the page and saw all the stuff about TCP. It looks like you're doing the right thing with your app.

I'm actually just working on the OSC Sender, which I'll probably finish tomorrow. That will at least make it easy to check that stuff is working locally.

Btw. how are you checking that you're getting something on Scope? I generally just plug in one of Simon's Pipe modular modules and look at the values there. You have to be a bit careful with the readouts though, as the SDK often doesn't update them without explicitly refreshing.

[w_ellis]

Unfortunately have to go to bed now, as teething baby will be keeping us up all night, but hope to make more progress tomorrow!

[faxinadu]

yeah but once a value is sent, it is held in the array until a new one comes in yeah? its not momentary and reverts... so i should have seen my magic little 12 there by now ehhehe tried refreshing, clicking and declicking the module, going into the array with f2 and other wishful things... hmmm not sure what else to try, kinda stoked and shocked i even got the android part to work (lots of copy paste from online codes heeh).

[faxinadu]

ok i just verified your module works using some random android app called QuickOsc! so still something im doing isn't right

[faxinadu]

oscc.png (89.88 KiB) Viewed 429812 times

it seems the QuickOsc is working via OSC protocol while mine is over UDP... those are the differences i spotted

[faxinadu]

EDIT: fixed issue, i didn't notice the module inherits voices and it was getting 0 voices, sorry my bad, but yeah something to make sure when testing!

ok i have done some more testing and it seems the sdk module is not so reliable.

with the app that i confirmed works, and also seeing it transmit every button press over wireshark without problems, the sdk module seems to work only some of the time.

i have also forwarded the port via my router to the target pc as well as activated dmz host for good measure.

on same procedure ie open sdk, open the module and trasnmit to it sometimes it will connect and sometimes not.

[faxinadu]

eheh ok new issue - i can not get it to update anything real time.

osc module is connected to an array viewer that has selcount input and value output. a 0-1 normal scope button is connected to the value output.

quickosc is sending a 0 and a 1. the osc module is getting the info and it is passed to the splitter - but the information is not updating real time, only if and when i physically change the selcount to another sel and back, will it show the change.

i am not sure if its an issue from the osc module or the way to view arrays, but i anticipated this stuff i have been banging my head against the wall with some scope array issues lately, that is why i asked for 16 outputs instead of an array.

[faxinadu]

Scope arrays are a mess. Having 16 outputs instead of an array is (IMHO) the preferred way.

for sure!

and anyways......... why just 16? any chance for 64?

[faxinadu]

Message sent using actual OSC protocol (works):

udp1.png (35.44 KiB) Viewed 386710 times

message sent over UDP protocol (no bueno):

udp2.png (38.34 KiB) Viewed 386710 times

[faxinadu]

i am gonna try with javaOsc today but
a) i suck, its literally my second day with java hehe
b) its not public domain and has attributions

but lets see..

[faxinadu]

will are you SURE your module expects only /x yy ? i read more on the osc protocol and it seems sending just hat over udp is not enough. it expects more formating - at least this also seems to be the difference between what worked and what didn't here.

[w_ellis]

will are you SURE your module expects only /x yy ? i read more on the osc protocol and it seems sending just hat over udp is not enough. it expects more formating - at least this also seems to be the difference between what worked and what didn't here.

I'm using the Juce OSC library and don't know all the implementation details. All I know is that in Max For Live I just set up a updsend module and send /x yy and it works. There's a good chance that the Max For Live module is doing more than just pure UDP if that's the case.