normen

Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • in reply to: Syphon QTKit and IP Cam Inputs #6098
    normen
    Participant

    Alright, thanks for clearing that up 🙂
    Edit: Made the changes and also uploaded new binaries for all binary leecherz 😉

    in reply to: Syphon QTKit and IP Cam Inputs #6096
    normen
    Participant

    Looking over the changes now and just so I understand all changes made here some statements for correction if needed:

    a) I don’t need a framebuffer to be able to draw at all (which I thought) having a context is enough to create and modify a texture in OpenGL.
    b) I don’t need to update the context as I am not technically changing anything that needs to be updated (e.g. painting meshes etc.) but only set this one texture buffer.
    c) I don’t need to make the context current as I am the only one managing it..? This is the thing I was wondering most about.. Its clear that for one capture session I’ll get served from one thread but couldn’t it be that another capture device arrives on another thread? Is having a reference to the context and being sure you are the only one using it enough to be able to use it? Is makeCurrentContext just for “thread locking” the context?
    d) The use of GLMacro is just more efficient when not using all the apple-related GL stuff I suppose? The “switching GL context” is caused due to the class I used being apple-specific GL use?

    Again thanks very much for the help, its much appreciated, this is what I love OSS for 😉

    in reply to: Syphon QTKit and IP Cam Inputs #6094
    normen
    Participant

    Cool, thanks, thats exactly the kind of looking over the code I was hoping for 🙂 I’ll do that to the NetCam application as well when I got time. I know from jMonkeyEngine3 that going down the “support all image formats” road can get hairy quick so I don’t think I’ll do that for now 😉

    • This reply was modified 8 years, 9 months ago by normen.
    in reply to: Syphon QTKit and IP Cam Inputs #6086
    normen
    Participant

    15 downloads of the binaries already, cool 🙂 If anyone here tried the applications, I’d be happy to hear if you had any issues or if it worked as intended for you.

    in reply to: Syphon QTKit and IP Cam Inputs #6071
    normen
    Participant

    Alright, made a repo at http://code.google.com/p/syphon-camera/ and gave it a more general name, maybe similar applications can be hosted there together..? I added you guys as admins as well.

    in reply to: Syphon QTKit and IP Cam Inputs #6069
    normen
    Participant

    haha, fair enough 🙂 I’ll check in the code in a GC repo at some point and pingback here.

    in reply to: Syphon QTKit and IP Cam Inputs #6067
    normen
    Participant

    Hm sounds a bit problematic to me actually.. Like for example the threading part etc.? Making the system adapt to multiple ways of doing it (lock the context, create new contexts etc.) sounds like it might bloat the system pretty quick to me.. But maybe thats because I think of plugins basically in a “single-threaded” callback way similar to VST’s / AudioUnits..?
    Syphon itself already feels pretty plugin-ish to me given its cross-application abilities and the ability to pipe it around as you wish. What I would have liked when I started doing this would have been a base class to reuse like [syphonTool startServerAndGlContext]; [syphonTool publishImageData:nsData];. Still maybe I am just oblivious of better and simpler ways to implement such a plugin system 🙂

    in reply to: Syphon QTKit and IP Cam Inputs #6058
    normen
    Participant

    Yeah, I could set up another gc repo for this but personally I enjoyed being able to download so much example code for syphon from one place.. The actual code I implemented for this now is pretty slick and might help others who just want to push some kind of image into the gpu/syphon (even without a gl context in the first place). I just need some hints if I should re-apply some gl states or if its not necessary or if it could be done even simpler. Oh and ofc I found one bug in the netcam thing, forgot to replace a call to a wrong thread where I even explicitly comment about it in another place 🙂 I just wouldn’t want to be responsible for any complaints to you about bad syphon example code..

    in reply to: Syphon QTKit and IP Cam Inputs #6051
    normen
    Participant

    Sure, maybe you wanna take a look at the code first though? Theres one thing where I don’t exactly know why its working (painting the texture)… but it does work 🙂 My googlemail is normen667 and I have the full googlemail.com (not gmail.com) ending.

    in reply to: Syphon QTKit and IP Cam Inputs #6049
    normen
    Participant

    Nice, thanks or the feedback 🙂 I guess I finished work on the IP-Cam plugin so I uploaded it to google docs for now: https://docs.google.com/open?id=0B84M35anjNjANEtUQWxHemJjMmM
    It contains the binary and sources for possibly adding them to the projects repo. Maybe the “on demand” enabling of cameras could be made optional still to have faster switching for some applications (its pretty fast with my ip cameras though)..

    I also uploaded the QTKit thingy, just didn’t have a chance to improve the “hot camera” handling yet. Its working globally and you should set it before you enable any camera. Maybe I’ll improve this still so if you want to you could wait with adding this. https://docs.google.com/open?id=0B84M35anjNjAbnB1NkZpOG9md2s

    I marked some parts of the code as “TODO”, maybe someone can have a look at these parts as with some stuff I am not 100% sure if its supposed to work like this.

    Thanks again to everybody!

    Cheers,
    Normen

    in reply to: Syphon QTKit and IP Cam Inputs #6029
    normen
    Participant

    Sure I could OSS them, would also alleviate the problem of hosting them for me. They are really not much code, was more the research for me. I guess some additional eyes and ideas can improve them still, they were not really intended to become OSS, eherm ;). Blackmagic driver support would be nice indeed 🙂 Should I contact you directly somehow when I got “per-cam-hotness” working? Everything else seems to work fine so far, some threading could be more elegant but its safe so this would probably be the last thing I’d do for myself.

    Cheers,
    Normen

Viewing 11 posts - 1 through 11 (of 11 total)