GEM-dev April 2011

gem-dev@lists.iem.at

9 participants
62 discussions

question regarding closing a DC1394 device
by cyrille henry 04 Apr '11

04 Apr '11

hello, after removing a pix_video object that is connected to a dc1394 device (or closing pd), the device is still sending information. (so you have to reboot it if you want to connect it again) i don't really understand the code of videoDC1394.cpp. line 59 : what is this close() function? i think closeDevice need to be add line 60. It help to stop transfer function when removing the object, but strangely it did not help when closing pd. So i did not really know if it's the way to go. could you help me trying to fix this problem? thanks Cyrille

2 2

[separator] compatibility question
by IOhannes zmölnig 04 Apr '11

04 Apr '11

hi all, since about a year, [separator] not only saves/restores the modelview matrices, but also the projection, texture and color matrices. today i noticed that pushing/popping the projection matrix can have weird side effects (the problem occurs on current nvidia drivers where the projection matrix stack has a rather limited size of 4 - with mesa on i845 i get a projection matrix stack size of 32). since the feature is relatively new, i'd like to remove it again. actually, i would only like to change the _default_ behaviour of [separator], in order to only push the modelview matrix. (you can still force [separator] to push any/all of the 4 matrices) however, i just thought i'd ask whether anybody has patches relying on [separator] pushing/pooping the projection matrix. if not, i'm going to change the default. fgamsdr IOhannes

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

GEM-dev April 2011