GEM-dev

gem-dev@lists.iem.at

2417 discussions

travis-ci integration
by IOhannes m zmölnig 04 Dec '14

04 Dec '14

thanks to antoine, Gem is now using travis-ci for automated test-builds whenever something is pushed to the (github) repository. https://travis-ci.org/umlaeute/Gem/ todo - enable OSX-builds (antoine, how did you do that?) - upload the built binaries to some webserver (e.g. github) - fix the build-matrix to avoid unnecessary builds caveats - currently only linux (and osx, see todo) are supported by travis-ci - "linux" is some rather outdated ubuntu (12.04, amd64 only) fnsdr IOhannes

2 3

video with alpha channel
by Cyrille Henry 04 Dec '14

04 Dec '14

hello, did anyone know a gem friendly video codec with alpha channel? i tried the video posted in a previous thread (24/05/2013) using pnga codec and pd crash. thanks and cheers Cyrille

3 3

[pd-gem:bugs] #239 PD/GEM crashes when natively supported Fire-I785C camera is plugged in
by Ticket 239 18 Nov '14

18 Nov '14

--- ** [bugs:#239] PD/GEM crashes when natively supported Fire-I785C camera is plugged in** **Status:** open **OS:** OSX **Release:** unknown **Created:** Tue Nov 18, 2014 05:30 AM UTC by Anonymous **Last Updated:** Tue Nov 18, 2014 05:30 AM UTC **Owner:** nobody PD/GEM crashes when [gemwin] is toggled to render when a natively supported Fire-I 785C camera by Mac OS X is plugged in to the firewire port. It doesn't crash if the camera is not plugged in and a similar device manufactured by the same company, the entry-level Fire-i camera, works with the current version of PD/GEM. Both devices have been tested in MAX/MSP with Jitter and work perfectly. MAC OS 10.9.4 PD 0.42.5 or 0.43.4 extended --- Sent from sourceforge.net because gem-dev(a)lists.iem.at is subscribed to http://sourceforge.net/p/pd-gem/bugs/ To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

PD/GEM crashes when natively supported Fire-I785C camera is plugged in
by Miles Warrington 17 Nov '14

17 Nov '14

PD/GEM crashes when [gemwin] is toggled to render when a natively supported Fire-I 785C camera by Mac OS X is plugged in to the firewire port. It doesn't crash if the camera is not plugged in and a similar device manufactured by the same company, the entry-level Fire-i camera, works with the current version of PD/GEM. Both devices have been tested in MAX/MSP with Jitter and work perfectly. MAC OS 10.9.4 PD 0.42.5 or 0.43.4 extended

2 1

Re: [GEM-dev] [PD-dev] [PD] gemglxwindow or gemwin
by IOhannes m zmölnig 06 Nov '14

06 Nov '14

moving this back to gem-dev. On 11/06/2014 12:48 AM, patrice colet wrote: > > [gemglxwindow] renders a black screen by sending a bang to it's inlet. > If gemwin is opened, rendering turns to black at the same moment. that's expected (and desired) behaviour. > > glxinfo is attached. thanks. so you are using nvidia proprietary drivers. which driver version, which card= > >> >>> there is also [gemglutwindow] it seem to do the same thing, but I've no >>> clue about how it works >>> >> what's "the same thing"? >> >> [gemglutwindow] gives you glut, so you can have ugly menus in the >> window... >> [gemglxwindow] gives you glx, which might give you context sharing... i forgot: [gemglutwindow] will work on all platforms (that support glut, which are all that i currently care for), whereas [gemglxwindow] will only work on X. all of these [gem*window] externals provide a common interface, but might have additional features. > > I'm trying right now to reproduce the crash, but it only happens with > [gemglutwindow], when [destroy( is sent > > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff61f9170 in gem::Context::push() () from > /usr/lib/pd/extra/Gem/Gem.pd_linux interesting. could you get a full backtrace? in any case, multiple-windows are still quite experimental (they are default in the dev-version, in order to get feedback like this) fgmdsr IOhannes

1 0

Re: [GEM-dev] [PD-dev] [PD] gemglxwindow or gemwin
by patrice colet 05 Nov '14

05 Nov '14

Hi, this is an interesting feature, where is it documented? I've tried it with last git version on archlinux 64bit, pd crashes when [destroy( message is sent to [gemwin] after a rendering window has been created with [gemglxwindow] there is also [gemglutwindow] it seem to do the same thing, but I've no clue about how it works Le 05/11/2014 14:32, Antoine Villeret a écrit : > hello, > > this have been already discussed on the Gem-dev list, but basically > with the new multicontext feature, IOhaness rewrote the windowing system. > [gemwin] is now an abstraction which everyone can customized to suit > its needs. > And it includes [gemdefaultwindow] abstraction by default, which might > include the external [gemglxwindow] which actually manage the OpenGL > context and rendering window. > > please also note that now (i mean with the latest Gem from git), you > can have multi windows and share texture between them. > > concerning the [reset( and [clear( message, if they don't work as you > expected, please report it to https://github.com/umlaeute/Gem/issues > afair, reset does reset the view and maybe more, but I don't what > [clear( shoulod do > > Cheers > > antoine > > > -- > do it yourself > http://antoine.villeret.free.fr > > 2014-11-05 14:01 GMT+01:00 mick mengucci <misturapura(a)gmail.com > <mailto:misturapura@gmail.com>>: > > Hi > I installed and compiled Pd vanilla and some externals including GEM. > I have problems with the [gemwin] object as it does not receive > |reset( nor |clear( messages which I used in older patches that I > use to run in Pd-extended. > Why is that? And what is the [gemglxwindow] object? what is the > difference between it and [gemwin]? > > I run Xubuntu > > Ubuntu 14.04.1 LTS > Release: 14.04 > Codename: trusty > > I hope I have been clear enough. Any feedback is appreciated. > Mick > > > -- > mickmengucci.bandcamp.com <http://mickmengucci.bandcamp.com> > facebook.com/Labio.pt <http://facebook.com/Labio.pt> > MISTURAPURA.NET <http://WWW.MISTURAPURA.NET> > pure mixture vibration since 1995 > > _______________________________________________ > Pd-list(a)lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > > > > > _______________________________________________ > Pd-dev mailing list > Pd-dev(a)lists.iem.at > http://lists.puredata.info/listinfo/pd-dev

3 2

sharing texture between process
by Antoine Villeret 04 Nov '14

04 Nov '14

hello, since texture sharing seems to work between context inside one Gem's instance, I'm now wondering how we can introduce texture sharing between process. According to [1], texture (and more generally display list) can be shared between process if direct rendering is disabled and process are using the same X server. If I understand correctly, the only thing to do is to share the display list structure over process. Could we use shared memory to do that ? I look into the [gemglxwindow] and [gemglutwindow] code and it looks a bit obscure to me, it uses advanced C++ idioms (PIMPL for the former and CALLBACK4WIN for the latter) that I don't understand well yet. So I want to know if this texture sharing between process is feasible before going deeper. Cheers Antoine [1] : https://www.opengl.org/sdk/docs/man2/xhtml/glXCreateContext.xml -- do it yourself http://antoine.villeret.free.fr

4 12

multiple window system
by Antoine Villeret 25 Oct '14

25 Oct '14

hello, I started some new examples on how to use multiple window system. here is a pull request : https://github.com/umlaeute/Gem/pull/85 there are only 2 for now, but maybe someone else can help to make more ? + a -- do it yourself http://antoine.villeret.free.fr

1 0

modelloader plugins
by IOhannes m zmölnig 22 Oct '14

22 Oct '14

hi all, thanks to antoine, we now have working modelloaders again (the default OBJ-loader, one based on the old assimp2 API and a shiny new one based on assimp3). cool! however, i'd like to make some more (minor, cosmetic) changes to the modelloader API, but wanted to discuss them beforehand: (this is mainly directed at antoine, but others should chime in). the current API (src/plugins/modelloader.h) looks like (simplified): float* getVector(std::string); VBOarray getVBOarray(); with VBOarray being a stripped down version of gem::VertexBuffer (Gem/VertexBuffer.h), just containing the float-array and type. it's a custom type defined in modelloader.h is there any specific reason not to directly use gem::VertexBuffer for returning the data from the modelloader? the VertexBuffer contains all the data that is needed (float-array, type) plus some more that should actually be returned (dimension, stride) plus some that is not needed by the modelloader-API (e.g. vbo-ID) this might simplify the API slightly to: VertexBuffer getVector(int type); vector<VertexBuffer> getVectors(); mfg.hj.iuo IOhannes

2 2

[pd-gem:bugs] #237 Texture coordinate pb on some geo's
by Ticket 237 08 Oct '14

08 Oct '14

--- ** [bugs:#237] Texture coordinate pb on some geo's** **Status:** open **OS:** any **Release:** 0.93.3 **Created:** Wed Oct 08, 2014 02:39 PM UTC by Anonymous **Last Updated:** Wed Oct 08, 2014 02:39 PM UTC **Owner:** nobody Modify lower left and upper left corners with pix_coordinate doesn't work with some geo's (circle, curve3d or surface3d). --- Sent from sourceforge.net because gem-dev(a)lists.iem.at is subscribed to http://sourceforge.net/p/pd-gem/bugs/ To unsubscribe from further messages, a project admin can change settings at http://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
242
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev