Announcement

Collapse
No announcement yet.

[Plugin] OSC for UE4

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts



    Unfortunately, Github has no "feature request" list... and I don't want to manage a 3rd party tool.

    This is really my "TODO list" for the project.

    Comment


      I still do not understand this plugin, can someone please put up a tutorial?

      Comment


        Hi M.Gustav,

        Just been testing the new build and it works as advertised! This is really great for me - trying to explain to someone how to find an IP address and entering it into a field in a widget was a bit painful. Now the player only has to press any button on my TouchOSC interface and the whole thing gets sorted out!

        Also - and I don't know if you or anyone uses TouchOSC (Which is a great app), I had another huge breakthrough tonight! It's the same thing with IP addresses - i'd have to find the IP address of my PC in order to type this into TouchOSC so it knows where to send commands to - not anymore! Previously I couldn't get TouchOSC to use the HostName - which would obviously save a lot of time and effort - i've worked it out though - my PC is called WIN10BOX and I've found that typing WIN10BOX.local into touch OSC means my PC is locate-able on my home network - great news for me! Everything can now autoconfigure with no pesky IP addresses in sight!

        Massive thanks again, M.Gustav. I'll get you a clip of what i'm doing as you asked.

        Lumli - i'd like to contribute to this plugin so when I get a chance I'll put a tutorial together.

        Dan

        Comment


          Originally posted by Dannington View Post

          Lumli - i'd like to contribute to this plugin so when I get a chance I'll put a tutorial together.

          Dan

          I would be very grateful if you could!

          Comment


            Hello,

            I've been trying to get this plugin to work in 4.11 but so far I haven't been able to identify the problem (see https://github.com/monsieurgustav/UE4-OSC/issues/21 ).

            Does anyone have managed to get it working? Is there an alternative to this plugin to get OSC messages in UE4? I really need to use this version due to the new VR features. 4.11 is also near to become stable.

            Thanks!

            Hector

            Comment


              Originally posted by Dannington View Post


              Lumli - i'd like to contribute to this plugin so when I get a chance I'll put a tutorial together.

              Dan
              By no means at all to bother, but any progress so far?

              PS: Thank you for considering it as this will do wonders for my live audio visual performance and am beyond excited to start as soon as I can

              Comment


                Originally posted by hcenteno View Post
                Hello,

                I've been trying to get this plugin to work in 4.11 but so far I haven't been able to identify the problem (see https://github.com/monsieurgustav/UE4-OSC/issues/21 ).

                Does anyone have managed to get it working? Is there an alternative to this plugin to get OSC messages in UE4? I really need to use this version due to the new VR features. 4.11 is also near to become stable.

                Thanks!

                Hector
                This has been fixed. Now working in 4.11.
                Last edited by virtualHC; 04-01-2016, 11:01 AM.

                Comment


                  Could this plugin also be updated to support midi ?

                  Comment


                    I've made a tutorial for this - I should be able to upload it tonight.

                    Comment


                      Hello!
                      How to configure the receiving port on the client to exactly the same as when sending data?

                      What I mean:
                      I pointed out to the reception port 8000
                      I send data to 127.0.0.1:9000

                      On the server side raised node.js and node-osс.
                      I can see that the client has 127.0.0.1 ip and port 64027 (each time a different client port is opened), so here I am on the side of the server can send back data on 127.0.0.1:64027 but the client is configured on port 8000 and the data can not be considered to the customer.
                      So the question arises, how to automatically substitute the client port on the wiretap data? in my case it has to be 64027 (same as the port and is set automatically when sending data)

                      Comment


                        Originally posted by Mbit View Post
                        Hello!
                        How to configure the receiving port on the client to exactly the same as when sending data?

                        What I mean:
                        I pointed out to the reception port 8000
                        I send data to 127.0.0.1:9000

                        On the server side raised node.js and node-osс.
                        I can see that the client has 127.0.0.1 ip and port 64027 (each time a different client port is opened), so here I am on the side of the server can send back data on 127.0.0.1:64027 but the client is configured on port 8000 and the data can not be considered to the customer.
                        So the question arises, how to automatically substitute the client port on the wiretap data? in my case it has to be 64027 (same as the port and is set automatically when sending data)
                        To change the listening port, go to Project Settings/Plugins/OSC and change the value under Receive From.

                        Comment


                          The sending port is chosen arbitrarily by the OS, you can make no assumption about it.

                          You can either hard-code the listening port to be 8000 everywhere, or include the "callback" port in the OSC message.

                          Comment


                            Originally posted by Dannington View Post
                            I've made a tutorial for this - I should be able to upload it tonight.
                            Do you know where could we find this tutorial ?

                            Comment


                              Originally posted by monsieurgustav View Post
                              The sending port is chosen arbitrarily by the OS, you can make no assumption about it.

                              You can either hard-code the listening port to be 8000 everywhere, or include the "callback" port in the OSC message.
                              you couldn't give an example of "callback" port? how to learn what port the operating system has opened for sending the message that I could set up him in OSC the message?

                              Comment


                                You misunderstand: the sending port (here 64027) has nothing to do with the listened port (8000, 9000, ?).
                                (you may find useful to read about how networking works)
                                Anyway: you don't care the sending port, only the listened port on the destination machine.

                                The easiest way is to listen the same port (8000) on all machines, that's generally what I do.
                                If you cannot do that, and you want a system that runs without configuration, every machine should add its listened port ("callback port") to the message it sends.

                                Comment

                                Working...
                                X