Martin Beck

Hello, I would like to use jit.catch~ with jit.graph as an oscilloscope that can be triggered.

In the reference description of @mode it is mentioned that the buffer size is 100ms.

Is it possible to increase this buffer size?

The attached patch shows the behaviour if the @framesize is set to a number that causes frames that are bigger than 100ms - triggering doesn't work .

message

comment

flonum

loadbang

dspstate~

loadmess

toggle

route

jit.matrixinfo

number

jit.unpack

saw~

jit.fpsgui

jit.gl.pix

jit.gl.gridshape

attrui

jit.gl.camera

jit.gl.handle

jit.world

ezdac~

rect~

qmetro

jit.graph

jit.catch~

Hello, I would like to use jit.catch~ with jit.graph as an oscilloscope  that can be triggered.
In the reference description of @mode it is mentioned that the buffer size is 100ms.
Is it possible to increase this buffer size?
The attached patch shows the behaviour if the @framesize is set to a number that causes frames that are bigger than 100ms - triggering doesn't work .

Hello, I would like to use jit.catch~ with jit.graph as an oscilloscope  that can be triggered.
In the reference description of @mode it is 

oscilloscope-in-max-jit-catch~-mode-3-with-buffersize-bigger-100ms

Anyone?
Do I have to use jit.poke~ for this?

I think that the documentation is correct: it is not possible to increase this internal buffer size. When you specify "too large" a framesize, the object behaves like in mode 2.

Oscilloscope in Max: jit.catch~ @mode 3 with buffersize bigger 100ms?