by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ion Reguera
    @ibiltari
    yes! i looked at that example! we were already thinking of using websockets so libossia is making itself a very good candidate for a building block
    Jean-Michaël Celerier
    @jcelerier
    super :) that's what it's made for so please tell us if you encounter any issues
    we'll do our best to see what we can do =p
    Ion Reguera
    @ibiltari
    Nice :)
    i'm seeing some strange behavior now with the parameter callbacks in python, i will test more and tell with i find
    Ion Reguera
    @ibiltari
    I found the problem, updating a parameter from inside its own callback hang-ups the callback. Is this completely wrong or not intended? or just a bug?
    Ion Reguera
    @ibiltari
    im having a hard time now figuring out how list_node_pattern() and NodeVector work, anny advice?
    Jean-Michaël Celerier
    @jcelerier
    hello ! hm looking

    I found the problem, updating a parameter from inside its own callback hang-ups the callback. Is this completely wrong or not intended? or just a bug?

    arf that sounds like a bug

    but callbacks are not recommended - i think they should move out from the API and that you should use the message queue API instead
    which is much safer
    Ion Reguera
    @ibiltari
    ok, so i am good now because i moved to message queue, but now i'm struggling with pattern matching
    by the way , should i open a issue about callbacks? i won't be using them i think and if they are going out perhaps is not worth it..
    Marcelo Kuroi
    @basskuroi_twitter
    hi y'all
    ah, I'm running the appimage and I don't know what to do with that =P
    I can make video and sound interact, for what I saw
    Thibaud Keller
    @thibaudk
    @basskuroi_twitter hi ! the appimage for Score ?
    you need to enable it to be excuted with
    chmod +x Score-v2.5.2-linux-amd64.AppImage
    P Baltazar
    @bltzr
    @sl1200mk2 salut - @jcelerier faisait un peu de spéléo dans les vieux fichiers, et on a des fichiers de namespace de D-light… tu avais le projet de le passer en OSC query, non ? Est-ce que tu as fait quelque chose de ce genre ?
    Nicolas Bats
    @sl1200mk2
    @bltzr hello, non... ça m'a saoulé que ça fonctionne avec des websoskets...
    mais un jour ça devrait venir :)
    P Baltazar
    @bltzr
    haha !
    sinon, tu as vu qu’il y a un serveur OSC query qu’a fabriqué vidvox : en principe c’est censé fonctionner en parallèle des autres apps (et sans modification de celles-ci), mais je suppose que c’est assez limité
    Nicolas Bats
    @sl1200mk2
    oui j'ai vu...
    Thibaud Keller
    @thibaudk

    petite question OSCQuery, peut être @avilleret peut répondre. Pour la connection osc bidirectionel, le serveur OSCQuery attend de recevoir du client la comand

    {"COMMAND":"START_OSC_STREAMING","DATA":{"LOCAL_SERVER_PORT":10203,"LOCAL_SENDER_PORT":43340}}

    ducoup j'attend de recevoir cette comand pour assigner le port osc 10203. Mias je me rend compte que c'est toujours le même port 10203. est ce que ce numéro de port est toujours constant ? specific à OSCQuery ou spécific à score ?

    onar3d
    @onar3d
    Hi!
    I want to use libossia on windows, and may be a bit dumb, but I haven't managed to make much headway. My goal is to use the OSC Query functionality.
    Following the build instructions with VS 2019, building fails with this message "1>...\libossia\src\ossia\network\wiimote\wiimote_protocol.hpp(27,3): error C7626: unnamed class used in typedef name cannot declare members other than non-static data members, member enumerations, or member classes
    "
    And then many others.
    Since the windows build status is "Failed" also on your github page I thought I'd check here.
    Also, I don't see how I can straightforwardly use the dll / lib win builds for getting to the OSC Query functionality, instead of building myself, can you point me in the right direction?
    Thanks!
    onar3d
    @onar3d
    Also from the visual studio 2017 terminal cmake creates a .sln which uses the v142 build tools, of VS 2019. Should I be telling cmake to use older platform tools for the build to succeed?
    Jean-Michaël Celerier
    @jcelerier
    hello !
    oh
    hm
    lemme check, I have a VS2019 handy
    we should be making a new release somewhat soon I guess which will be built with 2019
    Jean-Michaël Celerier
    @jcelerier
    note to self: make an help page that explains all the build options
    maybe the build should be minimal by default, what do you think @avilleret ? most people don't need the wiimote or whatever by default I guess
    onar3d
    @onar3d
    Good morning :)
    Meanwhile, the wiimote was an easy fix, now boost is acting up
    ...I just moved wiimote_parameters up as such: typedef struct wiimote_parameters
    Jean-Michaël Celerier
    @jcelerier
    hm, I'm seeing the boost issue indeed
    checking if that's not something that would just be solved by updating the boost version maybe
    kinda strange as this works fine on linux & mac... yay Visual Studio -_-
    Jean-Michaël Celerier
    @jcelerier
    (good morning indeed!)
    onar3d
    @onar3d
    As a relevant aside: If I were to just use your pre-built lib, how would I go about it? It doesn't seem like the .h file included in the "ossia-cpp-win" exposes everything needed. Adding "#include <ossia/ossia.hpp>" in one of my code files, after I've added the paths to the include and lib directories of visual studio, doesn't work. (it doesn't see the ossia.hpp file). So I'm assuming I should be using the ossia source tree anyway?
    Jean-Michaël Celerier
    @jcelerier
    hm, so there are multiple APIs depending on the need - the ossia-cpp is actually a "simplified C++" version which only needs one header (ossia-cpp/ossia-cpp.h iirc?)
    which only exposes the core functionality