Legacy CFM: Jitter 1.5.3 rc1
For those of you still working with MaxMSP 4.5 on OS X, or using CFM
jitter objects under MaxMSP 4.6 on OS X, there is a release candidate
version of Jitter 1.5.3 CFM available for download at the following
Please let us know if you experience any problems with this release,
with examples and steps to reproduce where necessary.
While this version seems to be stable, as always with pre-release
software, it is not recommended for installation/performance work,
and recommended that you back up your work before installing and more
often while working with the software.
WAS: jit.gl.slab v1.6 bug with multiple displays[message #74345]
it?s still the same behaviour in 1.6 and 1.53rc1. When having two or more monitors connected to more than one graphic card (NV 6600 )jit.gl.slab does not work (see below).
My setup consists of a G5 DualCore2,3GHz, QT7.11,OSX4.6,
Starting up with only one monitor, jit.gl.slab works well.
As soon as having a second monitor connected at the SECOND video card (which is in the 8-lane slot), the error occurs.
Just try the jit.gl.slab help file.
1) Start qmetro
2) Start metro
As soon as you start the metro the following message is sent for each bang to the MAX window,
error: jit.gl.texture: error binding readback mechanism for capture!
error: jit.gl.pbuffer: error binding invalid pbuffer!
On Sep 21, 2006, at 5:54 AM, Bernd wrote:
> WAS: jit.gl.slab v1.6 bug with multiple displays[message #74345]
Yes, Bernd. This wasn’t fixed (as reflected by no mention o it in the
release notes), and might not be fixed until 1.6.3. I’ve only gotten
my hand on a machine to reproduce this issue yesterday, and will try
to have it solved soon. Thanks for your patience.
In the meantime ;jitter glreadback fbo seems to solve some problems
and introduce others. YMMV.