Drew Bach

So, this has been driving me a bit nuts, and I'm going to go out on a limb and hope that it is pilot error. I started out with Max mainly with RNBO, and so most of what I've been able to figure out is trying to adapt Max knowledge into RNBO. 

So, most of my patches have been using Ableton Link for Tempo Sync and it is solid, but I've been trying to add a MIDI clock out to my FX patches as well from the Ableton Link transport clock. It works, but wowzers, the jitter is crazy. It isn't minor either, I'm getting massive jumps of 3-5bpm at times within a second or two. I've seen all sorts of references to using phasor, doing rounding, etc, but there have not been any example patches to learn from. 

The clock is made to always be sending, and have no notion of start/stop. This is intentional, as a lot of drum machines/synths take a few extra MS to catch the BPM before start, so by always sending I can prep the machines in advance. 

If someone could tell me what I am doing wrong I would be eternally grateful. 

(Note, if dropping into Max, remember that this is RNBO. So the Param object should be replaced.

Hi all,
So, this has been driving me a bit nuts, and I'm going to go out on a limb and hope that it is pilot error. 

rnbo-link-to-midi-clock-patch-jitter-help

Welp, I guess that I messed up the copy/paste patch....sorry!! I feel like such a dork. Since  it seems like I have not figured out copy/paste for patches, here is a pic of the patch as well:

{
	"boxes" : [ 		{
			"box" : 			{
				"maxclass" : "newobj",
				"text" : "t 248",
				"outlettype" : [ "" ],
				"patching_rect" : [ 254.0, 360.0, 37.0, 23.0 ],
				"numinlets" : 1,
				"id" : "obj-2",
				"numoutlets" : 1,
				"rnboinfo" : 				{
					"needsInstanceInfo" : 1,
					"argnames" : 					{
						"out1" : 						{
							"attrOrProp" : 1,
							"digest" : "Output order 1 (number).",
							"defaultarg" : 1,
							"isalias" : 0,
							"aliases" : [  ],
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"outlet" : 1,
							"type" : "number"
						}
,
						"triggers" : 						{
							"attrOrProp" : 2,
							"digest" : "The number of arguments determines the number of outlets. \t\t\t\t\t\tEach outlet sends out either a whole number, float, bang or list, \t\t\t\t\t\tas identified by symbol arguments (i, f, b, l). \t\t\t\t\t\tIf there are no arguments, there are two outlets, both of which send a float.",
							"defaultarg" : 1,
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "list"
						}

}
,
					"inputs" : [ 						{
							"name" : "input",
							"type" : [ "bang", "number", "list" ],
							"digest" : "input to distribute",
							"hot" : 1,
							"docked" : 0
						}
 ],
					"outputs" : [ 						{
							"name" : "out1",
							"type" : "number",
							"digest" : "Output order 1 (number).",
							"defaultarg" : 1,
							"docked" : 0
						}
 ],
					"helpname" : "trigger",
					"aliasOf" : "trigger",
					"classname" : "t",
					"operator" : 0,
					"versionId" : -1133428571,
					"changesPatcherIO" : 0
				}
,
				"rnbo_extra_attributes" : 				{
					"triggers" : ""
				}
,
				"rnbo_uniqueid" : "t_obj-2",
				"rnbo_serial" : 3,
				"rnbo_classname" : "t"
			}

}
, 		{
			"box" : 			{
				"maxclass" : "comment",
				"text" : "MIDI Clock out",
				"patching_rect" : [ 242.5, 396.0, 102.5, 21.0 ],
				"numinlets" : 1,
				"id" : "obj-23",
				"numoutlets" : 0
			}

}
, 		{
			"box" : 			{
				"maxclass" : "comment",
				"text" : "Start/Stop clock",
				"patching_rect" : [ 155.0, 138.0, 128.0, 21.0 ],
				"numinlets" : 1,
				"id" : "obj-20",
				"numoutlets" : 0
			}

}
, 		{
			"box" : 			{
				"maxclass" : "newobj",
				"text" : "/ 20",
				"outlettype" : [ "" ],
				"patching_rect" : [ 246.0, 283.0, 31.0, 23.0 ],
				"numinlets" : 2,
				"id" : "obj-8",
				"numoutlets" : 1,
				"rnbo_extra_attributes" : 				{
					"hot" : 0
				}
,
				"rnbo_uniqueid" : "/_obj-8",
				"rnbo_serial" : 2,
				"rnbo_classname" : "/"
			}

}
, 		{
			"box" : 			{
				"maxclass" : "newobj",
				"text" : "metro @interval 1 ticks @active 1",
				"outlettype" : [ "" ],
				"patching_rect" : [ 172.5, 174.0, 190.0, 23.0 ],
				"numinlets" : 2,
				"id" : "obj-4",
				"numoutlets" : 1,
				"rnbo_extra_attributes" : 				{
					"lock" : 0.0
				}
,
				"rnbo_uniqueid" : "metro_obj-4",
				"rnbo_serial" : 2,
				"rnbo_classname" : "metro"
			}

}
, 		{
			"box" : 			{
				"maxclass" : "newobj",
				"text" : "transport",
				"outlettype" : [ "", "", "", "", "", "", "", "" ],
				"patching_rect" : [ 172.5, 237.0, 103.0, 23.0 ],
				"numinlets" : 2,
				"id" : "obj-1",
				"numoutlets" : 8,
				"rnbo_uniqueid" : "transport_obj-1",
				"rnbo_serial" : 1,
				"rnbo_classname" : "transport"
			}

}
, 		{
			"box" : 			{
				"maxclass" : "newobj",
				"varname" : "clockstart",
				"text" : "param clockstart @value 20 @enum stop start",
				"outlettype" : [ "", "" ],
				"patching_rect" : [ 45.0, 48.5, 250.0, 23.0 ],
				"numinlets" : 2,
				"id" : "obj-28",
				"numoutlets" : 2,
				"rnboinfo" : 				{
					"needsInstanceInfo" : 1,
					"argnames" : 					{
						"value" : 						{
							"attrOrProp" : 2,
							"digest" : "Set initial value",
							"defaultarg" : 2,
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "0",
							"label" : "Initial Value",
							"displayorder" : 3
						}
,
						"normalizedvalue" : 						{
							"attrOrProp" : 1,
							"digest" : "Set value normalized. ",
							"isalias" : 0,
							"aliases" : [  ],
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"inlet" : 1,
							"type" : "number"
						}
,
						"reset" : 						{
							"attrOrProp" : 1,
							"digest" : "Reset param to initial value",
							"isalias" : 0,
							"aliases" : [  ],
							"attachable" : 1,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "bang"
						}
,
						"normalized" : 						{
							"attrOrProp" : 1,
							"digest" : "Normalized parameter value.",
							"isalias" : 0,
							"aliases" : [  ],
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"outlet" : 1,
							"type" : "number"
						}
,
						"name" : 						{
							"attrOrProp" : 2,
							"digest" : "Name of the parameter",
							"defaultarg" : 1,
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"label" : "Parameter Name",
							"mandatory" : 1
						}
,
						"enum" : 						{
							"attrOrProp" : 2,
							"digest" : "Use an enumerated output",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "list",
							"label" : "Enum Values",
							"displayorder" : 6
						}
,
						"minimum" : 						{
							"attrOrProp" : 2,
							"digest" : "Minimum value",
							"isalias" : 0,
							"aliases" : [ "min" ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "0",
							"label" : "Minimum",
							"displayorder" : 1
						}
,
						"min" : 						{
							"attrOrProp" : 2,
							"digest" : "Minimum value",
							"isalias" : 1,
							"aliasOf" : "minimum",
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "0",
							"label" : "Minimum",
							"displayorder" : 1
						}
,
						"maximum" : 						{
							"attrOrProp" : 2,
							"digest" : "Maximum value",
							"isalias" : 0,
							"aliases" : [ "max" ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "1",
							"label" : "Maximum",
							"displayorder" : 2
						}
,
						"max" : 						{
							"attrOrProp" : 2,
							"digest" : "Maximum value",
							"isalias" : 1,
							"aliasOf" : "maximum",
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "1",
							"label" : "Maximum",
							"displayorder" : 2
						}
,
						"exponent" : 						{
							"attrOrProp" : 2,
							"digest" : "Scale values exponentially",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "1",
							"label" : "Exponent",
							"displayorder" : 7
						}
,
						"steps" : 						{
							"attrOrProp" : 2,
							"digest" : "Divide the output into a number of discrete steps",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"defaultValue" : "0",
							"label" : "Steps",
							"displayorder" : 8
						}
,
						"displayName" : 						{
							"attrOrProp" : 2,
							"digest" : "DEPRECATED: Use the lower case 'displayname' instead",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 1,
							"type" : "symbol",
							"label" : "Display Name"
						}
,
						"displayname" : 						{
							"attrOrProp" : 2,
							"digest" : "A more readable name for the parameter in an external RNBO target",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"defaultValue" : "",
							"label" : "Display Name",
							"displayorder" : 14
						}
,
						"unit" : 						{
							"attrOrProp" : 2,
							"digest" : "A symbol to describe the unit of the parameter in an external RNBO target",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"defaultValue" : "",
							"label" : "Unit",
							"displayorder" : 15
						}
,
						"tonormalized" : 						{
							"attrOrProp" : 2,
							"digest" : "Converts a real parameter value to its normalized form.",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"label" : "To Normalized Expression",
							"displayorder" : 10
						}
,
						"fromnormalized" : 						{
							"attrOrProp" : 2,
							"digest" : "Converts a normalized parameter into its actual parameter value.",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"label" : "From Normalized Expression",
							"displayorder" : 9
						}
,
						"order" : 						{
							"attrOrProp" : 2,
							"digest" : "Order in which initial parameter values will be sent out on patcher load. The order can be numeric or symbolic ('first' and 'last')",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"defaultValue" : "0",
							"label" : "Restore Order",
							"displayorder" : 12
						}
,
						"displayorder" : 						{
							"attrOrProp" : 2,
							"digest" : "Order in which parameters will show up in a list of all parameters. The order can be numeric or symbolic ('first' and 'last')",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"defaultValue" : "-",
							"label" : "Display Order",
							"displayorder" : 13
						}
,
						"sendinit" : 						{
							"attrOrProp" : 2,
							"digest" : "Send initial value",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "bool",
							"defaultValue" : "true",
							"label" : "Send Init",
							"displayorder" : 4
						}
,
						"ctlin" : 						{
							"attrOrProp" : 2,
							"digest" : "MIDI controller number to control this parameter.",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "number",
							"label" : "MIDI Controller Number.",
							"displayorder" : 16
						}
,
						"meta" : 						{
							"attrOrProp" : 2,
							"digest" : "A JSON formatted string containing metadata for use by the exported code",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "symbol",
							"defaultValue" : "",
							"label" : "Metadata",
							"displayorder" : 17
						}
,
						"nopreset" : 						{
							"attrOrProp" : 2,
							"digest" : "Do not add this value to the preset [DEPRECATED - USE @preset 0 instead].",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 1,
							"type" : "bool",
							"defaultValue" : "false"
						}
,
						"preset" : 						{
							"attrOrProp" : 2,
							"digest" : "Add this value to the preset.",
							"isalias" : 0,
							"aliases" : [  ],
							"settable" : 1,
							"attachable" : 0,
							"isparam" : 0,
							"deprecated" : 0,
							"type" : "bool",
							"defaultValue" : "true",
							"label" : "Include In Preset",
							"displayorder" : 11
						}

}
,
					"inputs" : [ 						{
							"name" : "value",
							"type" : "number",
							"digest" : "Parameter value",
							"hot" : 1,
							"docked" : 0
						}
, 						{
							"name" : "normalizedvalue",
							"type" : "number",
							"digest" : "Set value normalized. ",
							"docked" : 0
						}
 ],
					"outputs" : [ 						{
							"name" : "value",
							"type" : "number",
							"digest" : "Parameter value",
							"hot" : 1,
							"docked" : 0
						}
, 						{
							"name" : "normalized",
							"type" : "number",
							"digest" : "Normalized parameter value.",
							"docked" : 0
						}
 ],
					"helpname" : "param",
					"aliasOf" : "param",
					"classname" : "param",
					"operator" : 0,
					"versionId" : -1696900560,
					"changesPatcherIO" : 0
				}
,
				"rnbo_extra_attributes" : 				{
					"exponent" : 1.0,
					"ctlin" : 0.0,
					"tonormalized" : "",
					"displayname" : "",
					"minimum" : 0.0,
					"maximum" : 1.0,
					"sendinit" : 1,
					"fromnormalized" : "",
					"steps" : 0.0,
					"preset" : 1,
					"unit" : "",
					"meta" : "",
					"displayorder" : "-",
					"order" : "0"
				}
,
				"rnbo_uniqueid" : "clockstart",
				"rnbo_serial" : 2,
				"rnbo_classname" : "param"
			}

}
, 		{
			"box" : 			{
				"maxclass" : "toggle",
				"outlettype" : [ "int" ],
				"patching_rect" : [ 45.0, 95.5, 46.0, 46.0 ],
				"numinlets" : 1,
				"id" : "obj-85",
				"parameter_enable" : 0,
				"numoutlets" : 1,
				"rnbo_extra_attributes" : 				{
					"preset" : 0,
					"order" : ""
				}
,
				"rnbo_uniqueid" : "toggle_obj-85",
				"rnbo_serial" : 1,
				"rnbo_classname" : "toggle"
			}

}
 ],
	"lines" : [ 		{
			"patchline" : 			{
				"source" : [ "obj-28", 0 ],
				"destination" : [ "obj-85", 0 ]
			}

}
, 		{
			"patchline" : 			{
				"source" : [ "obj-85", 0 ],
				"destination" : [ "obj-1", 0 ]
			}

}
, 		{
			"patchline" : 			{
				"source" : [ "obj-8", 0 ],
				"destination" : [ "obj-2", 0 ]
			}

}
, 		{
			"patchline" : 			{
				"source" : [ "obj-4", 0 ],
				"destination" : [ "obj-1", 0 ]
			}

}
, 		{
			"patchline" : 			{
				"source" : [ "obj-1", 7 ],
				"destination" : [ "obj-8", 0 ]
			}

}
 ],
	"appversion" : 	{
		"major" : 8,
		"minor" : 5,
		"revision" : 6,
		"architecture" : "x64",
		"modernui" : 1
	}
,
	"classnamespace" : "rnbo"
}

Sorry about the paste above. It isn't actually a working one anyway, it works in max but not in RNBO. Here is the simplest clock patch. The results are identical using transport or a raw Metro feed, but ideally I would like to go this route as I am not using the transport in any of the patch. 

why do you need transport at all ?
is metro set to beatclock ticks interval and lock 1 
not supposed to follow host sync ?
I don't know if rnbo can sync well  that way, but using only needed objects
helps sometimes in max.

I don't use ableton and can't say if it makes sense to sync to live link and
generate another clock out of synced plugins.




RNBO Link to MIDI Clock Patch Jitter-Help?

UnUnUnium

Given that both param and param~ are controlled by a non signal rate  outside the rnbo~ object, would param and sig~ together be equivalent to param~?

I am asking because I have noticed that param~ only works in the top level patcher, whereas param seems to work anywhere.

Given that both param and param~ are controlled by a non signal rate  outside the rnbo~ object, would param and sig~ together be equivalent ... 

param-vs-param

param~ can be additionally controlled by an audio buffer but, AFAIK, only the web target supports it.
We're having discussions around param~ internally as the range and clamping details are a little odd, so we might have some updates in a future release.

If you wanted to roll your own, it would more likely be a combination of inlet~ and param.

Thank you Alex, that clears it up. 

So the approach might be to use inlet~, then use *~ to multiply the signal using the output of the param?

I will also experiment with sig~ and param, as the sample accurate objects (sig~, line~ etc) seem to be getting me the precision I need.

technically, param~ is effectively a [+~] of a [param] value and in [inlet~], but if your param -> sig~ and sample accurate objects are giving you the results that you like, sounds like you should just do that

Got it, that makes sense , thank you - I'll stick with the param/sig~ approach for now . Curious to see the next implementation of param~!

param~ vs param 

jmmmp

Hi all,
I receive lists with symbols from Pd, which have some backslashes because of spaces, such as 
4716.631348 90. 1. 2. gong\ 2 10. 0. 2. 0. 0. 0. 0. 166. 43. 60.
(in bold is the symbol)

Is there a way to edit this symbol with sprintf to keep the space, but remove the backslash? That is, change if from "gong\ 2" to "gong 2".
THanks,
jmmmp


Hi all,
I receive lists with symbols from Pd, which have some backslashes because of spaces, such as 
4716.631348 90. 1. 2. gong\ 2 10. 0. 

remove-backslash-from-symbollist

not with sprintf.
but it makes me wonder how do you receive that message from pd,
OSC ?
something like gong\ 2  can not be part of a max message.
try to type it into message object ...
if you have it in text an output, it wil get auto transformed into "gong 2"


Remove backslash from symbol/list

benjamin vyger

Hello,
I would like values of 4*4 matrix with marker < and > in order to have those datas
< 113, 220,...,..., 110 >
In. a jit.matrix  we have 4 datas/cell. That means we have 4*4 datas between  < and >
I made this small patch and I think we have to use object that I can't use.
Thank you for your help

In my example I receive only the raw 0 but value are strange

receivedmess: cell 0 0 val 123 40 53 248
receivedmess: cell 0 3 val 141 132 163 180
receivedmess: cell 0 2 val 234 97 200 213
receivedmess: cell 0 1 val 226 205 19 176
receivedmess: cell 0 0 val 123 40 53 248
receivedmess: cell 0 3 val 141 132 163 180
receivedmess: cell 0 2 val 234 97 200 213
receivedmess: cell 0 1 val 226 205 19 176


GetmaxtrixData.maxhelp

Capture d’écran 2023-09-26 à 16.24.17.png

Hello,
I would like values of 4*4 matrix with marker < and > in order to have those datas
< 113, 220,...,..., 110 >
In. 

get-values-of-jitmatrix

The screenshot seem broken, I can't see it.
Also, for future patch sharing: select objects you want to share, then hit Edit -> "Copy compressed", then paste the code here.
What you want is unclear. Values from your pasted log doesn't look weird to me. Loking at youyr patch, your source matrix is a 4 planes char jit.noise of dim 4x4, which means that you have 4x4=16 cells, each with 4 values between 0 and 255. You're only sending getcell for the first row (row 0), which means you only gete the values of the 4 cells of that first row. This is exactly what you receives in your log.

Maybe have a look at [jit.iter] or [jit.spill]. Also, if you really need to format your messages with '<' and '>', why not adding those with [pack]? Or maybe [combine] or [sprintf]?

Also, seems that you're french, I can help you in french if you struggle with english if you want.


Dois je utiliser [jit.iter] or [jit.spill] après jit.print ou jit.matrix ?

En fait, j'aimerais que les données soient bien formées dans le monitor dans  receive

Pas seulement dans jit.print

I hope you understood me ?

I would like to have for cell 0 0 in receive < 234, 49, 59, 130 >

The aim is to transfer datas of each pixel to an Arduino to control a matrix of led

cell 0 0 ne correspond pas à la premiere donnée de jit.matrix

Apparemment vos images ne fonctionnent toujours pas :


Dois je utiliser [jit.iter] or [jit.spill] après jit.print ou jit.matrix ?

C'est pareil, l'outlet gauche de  [jit.print] renvoie la matrice à l'identique.


Malheureusement, il semblerait qu'il n'y ait pas moyen d'obtenir l'output console de [jit.print] en tant que message. Mais c'est possible de recréer un message identique :


Pour rajouter les '<' et '>', il suffit de les rajouter dans le [sprintf] aux endroits voulus.


merci c'est presque bon.
Mais je n'arrive qu'à voir 32 données em meme temps, pas 64.


Cela semble être dû à une limitation de [sprintf], qui n'accepterait pas plus de 32 entrées. De plus, la virgule est un caractère spécial dans Max, donc je ne vois pas comment simplement outrepasser cette limitation (autrement qu'en utilisant javascript). Le plus simple serait de gérer autrement le traitement du message directement dans arduino, et par exemple d'envoyer les valeurs en une simple liste de 64 entier (sans les virgules et les '<' et '>'). Le programme arduino devra ensuite séparer les entiers 4 par 4 pour chaque pixel, puis tous les 4 pixels pour chaque ligne.
Ou alors l'update de la matrice de LED se fait tous les 4 messages (un par ligne ou colonne).


get values of jit.matrix

Ryan Ozols

Trying to create a square that continuously gets smaller and will loop, but upon resetting a vertical and horizontal line along the middle appear


 
Trying to create a square that continuously gets smaller and will loop, but upon resetting a vertical and horizontal line along the ... 

unwanted-lines-in-jitlcd

no idea why this happens, but i would get rid of that unnecessary dual-metro, dual-counter design, then you have better control over when "clear" is performed.

and it could also be a good idea to use float values for the size. the interpolation looks slightly different between mac os and windows but if this is an mask or alpha channel you will probably work with it as char anyway (and not 2-bit)

Use pack i i i i instead of pak, and it should work as expected :-)

(with pak, framerect is drawn 4 times for each bang...)

Unwanted lines in jit.lcd

Noah Mitchell

I'm trying to figure out how to sample only select pixels within jit.gl.pix

Say I want to use an snorm scaled up to have a repeat effect, but I only want the to happen with a certain part of the image not to take the whole part of the image.

Can I repeat only a select part of the image using a sample parameter...or is there another simpler way to do this?

Hello,
I'm trying to figure out how to sample only select pixels within jit.gl.pix
Say I want to use an snorm scaled up to have a repeat eff

repeat-only-selected-region-of-an-image-jit-gl-pix

that's a cool patch...not exactly what I'm looking for though.

Here's an easier way to explain. Say I'm using a mask on an image and only want the masked part of the image repeated. In your patch the entire image is still getting repeated

Matteo's example does exactly what you are describing, you just need to adjust the rsliders to define the masked part of the image.

Hi there. These patches have been a real help. I'm keen to enact a mirror repeat on the cropped & zoomed area but I'm struggling with how the right inlet of 'sample' works. Any tips greatly appreciated.

the right inlet of [sample] takes a 2-component vector representing the normalized position (aka between 0 and 1) at which the image coming into the first inlet is sampled.
The attribute @boundmode affects the sampling coordinates ONLY when they exceed the range [0, 1]. 
Some examples:
given input sampling coordinates x = -0.1 and y = 1.3
@boundmode wrap (default) -> x = 0.9; y = 0.3
@boundmode clamp -> x = 0; y = 1
@boundmode mirror -> x = 0.1; y = 0.7

Since your patch samples a subregion of the original video, the sampling coordinates never exceed the range [0, 1]. 
If you want to have mirrored sampling, you must implement it manually. This could be a way to go:

Repeat only selected region of an image jit.gl.pix

Michael Beil

jit.movie sometimes (like 1 out of 10) freezes playback after loading a movie. There's no error message and I can see the first frame. I tried with load and start message. I tried with load and autostart. And here's the weird part: when I extract only the qt part of this huge patch to an extra patch I cannot reproduce the issue.
With viddll it doesn't happen, yet. But I am a bit worried to go into the next gig without really knowing what's going on. I attach the extracted patch. The big one is to complex I think. Maybe you can see a problem. Quick help appreciated.

qttesterseparate.maxpat

jit.movie sometimes (like 1 out of 10) freezes playback after loading a movie. There's no error message and I can see the first frame. 

jitmovie-freezes-after-first-frame-macavf

jit.movie freezes after first frame (mac/avf)

Hey,
Just wanted to share that small project I was working on, which is a Max implementation of the cubehelix algorithm, made to create readable color palettes with gradients of linearly changing lightness.
It consists of a few files:

cubehelix.genjit which is the "low-level" code for cubehlix calculation in the jit world

jit.cubehelix.maxpat, an abstraction wrapping cubehelix.genjit as a patcher with some added features for convenience: initialization with attributes, accepts inputs for both ranges (like the D3 implementation) and legacy parameters (start, rotation), converts output matrix...

jit.cubehelix.maxhelp, the help file for the [jit.cubehelix] abstraction, with examples and explanations

jit.cubehelix.ui.maxpat, which is basically a wrapper for [jit.cubehelix] with an user interface (can be used as a [bpatcher]), randomization capabilities and preset handling (using the pattr system). Small video demo here. 

knob-range.js, a custom [jsui] knob made for [jit.cubehelix.ui] but which can be repurposed for other things. It allows to set a custom output range, randomize the value in an inner range that can be modified with ctrl+drag (change offset) and option/alt+drag (change width). Holding shift allows fine tuning. Still a work in progress, many improvements to do.

cubehelixui-default.json, some default presets for [jit.cubehelix.ui]


You can find the repo here or direct .zip download there.

jit.cubehelix.ui.png

jit.cubehelix.maxhelp.1.png


 
Hey,
Just wanted to share that small project I was working on, which is a Max implementation of the cubehelix algorithm, made to create ... 

sharing-creating-color-palettes-using-cubehelix

[Sharing] Creating color palettes using cubehelix

Gary Leyrn

I am trying to make work a patch that before used to work properly, now I get this errors when trying to assign textures to videoplanes , each time , this 3 errors :

jit.gl.texture: update_texparameter_state: GL Error: Invalid operation
jit.gl.texture: bind: GL Error: Invalid operation
jit.gl.texture: blit: GL Error: Invalid operation

The video plane looks black.
What is going on and how can I fix this ? 

Hello, 
I am trying to make work a patch that before used to work properly, now I get this errors when trying to assign textures to ... 

jitgltexture-gl-error

we'll need a patch to provide any insight 

jit.gl.texture GL Error

Julien Bayle

Hi there,
Still in the middle of a big project for which I need to capture 3 webcam simultaneously (swap the one I record (only one at a time).

I found the Decklink Quad HDMI Recorder : https://www.blackmagicdesign.com/products/decklink/techspecs/W-DLK-36 

It can drive 4 cam. We'd use 3 Panasonic GH 5 & 4.

We'd need a very tight sync etc.
The PC would be a very big one (i9, 128Gb RAM, BIG RTX for the texture process + replay)

Would this setup the best from the acquisition point of view ?
I read Blackmagic drivers behave well in this kind of setup, with max.


Hi there,
Still in the middle of a big project for which I need to capture 3 webcam simultaneously (swap the one I record (only one at a ... 

multiple-cams-simultaneous-real-time-acquisition

Thanks for sharing with us, best regards for the personal .

Hello there, I still didn't have any chance to get some answers :-)

We are on it.
jit.dx.grab seems a way to follow VS jit.grab

The issue here is the latency.
- cams => Decklink Quad HDMI Recorder => OBS ====> VERY FAST display (not recording this)
- cams => Decklink Quad HDMI Recorder => Max 8 =====> feeling latency

I can't understand.
We are using a basic patch just grabbing frames with jit .grab, or jit.dx.grab as mentioned.
1080p 25fps (from nice panasonic cams)

By latency, I mean: there is a delay (I guess about 250ms, 300ms) 

Hey, 
I capture cameras all the time.
Just to get this straight..
You are capturing into the Decklink to record, is this then going live to screen?
Trying to figure out where the latency is noticed?
There will always be latency, no matter what you do.
Can you not record with OBS?  If you run the cams at 50 fps, you'll halve the latency.
If running to a live screen, I run everything at 50 fps, capture with Resolume (surprisingly fast) and send via spout to max for processing?
Let me know if I can help further.
B

Hi there.
I'm talking about the delay between a movement in real life and the frames showing the movement on the computer.

Frame reading seems smooth.
Frame rate at reading seems ok too.

But that delay...

I'm not sure adding resolume + syphon in the chain could help (but I obviously don't know as I didn't test myself) VS jit.grab or even jit.dx.grab

And I don't talk about recording. Just... Displaying frame.

I tested with a basic patch. Same.


Decklink here are just the hub. It collects 2 flows. And potentially 4.
I was thinking about creating a switching system for not grabbing all flow at the same time (as only one would be recorded at a time... But I was afraid of small overload when switching a jit.grab on and off on the fly)... But even with one 1080p25i/s, it is the same delay. 

The computer is very powerful, I talk about a i9, 128Gb RAM, one BIG NVIDIA RTX. 

We trying with resolume (and obs) as frameservers through spout in the equation.

Current research is about recording a BIG file, constantly, and to trying to find a way to play some part of it (during the recording) in order to grab the correct moment in time and to "offset/remove" the delay.


Hello Julien,
I did a quick test here concerning frame latency.
I sent timecode @25fps from my laptop into my PC using a Blackmagic Decklink Duo 2.
I wasn't able to acquire an image with jit.dx.grab with max? I tried evrything. 
Might help..?
B

possibly helpful discussion - https://forum.openframeworks.cc/t/how-to-reduce-latency-when-projection-mapping-onto-moving-objects/42464 

Multiple Cams simultaneous real-time acquisition ?

Ben Bracken

We are happy to announce the release of Max 8.5.6 and RNBO 1.2.1. 

On the Max side, we have a number of bug fixes, with improvements to fullscreen jit.window / thispatcher behavior, among other things. 

On the RNBO side, this release features many new improvements and bug fixes, with a focus on the Raspberry Pi target (can upload and manage the active patch), new ease objects, messages to the rnbo~ object for managing manual target exports, new integer utilities for codebox, among many other things.

As always, you can download the update here: 
https://cycling74.com/downloads

For a list of all Max 8.5.6 and RNBO 1.2.0 improvements, check out the change logs below, or here:
Max:
https://cycling74.com/releases/max/8.5.6 

RNBO:
https://cycling74.com/releases/rnbo/1.2.1 

udpreceive: 'defer' attribute to set message output to the low-priority queue

curve~ / line~: pending ramps are appropriately cancelled if interrupted

jit.dx.grab: support for outputting at device max framerate

jit.gl.handle: autohandle works with jit.gl.mesh

jit.gl.pix: fixed dim variable breakage with codebox

jit.gl.sketch: fixed usage of vertex colors

jit.gl.text: fixed draw errors on visiblity change

jit.window/jit.pwindow: fixed visibility in Max for Live

jit.world: fixed crash when enabling/disabling fullscreen or floating

live.menu: svg files are included as dependencies in Projects

Max for Live Editor: fixed issues when multiple Max instances are running

Max for Live: fixed crash when setting 'is_mpe' attribute

MIDI: improved support for multiple devices of the same type (Windows)

scala: fixed default scale "B" from 1200 to 1100 cents

thispatcher / jit.window: improved manual fullscreen behavior / fixed regressions

accum: added gen~ style features (resetmode, min, max)

C++ source code export: option to disable export of RNBO Engine

codebox: imod/iadd/imult integer operators

ease: new objects a la Max Package (ease, ease.list, ease.listinterp, ease~, ease.xfade~)

Max External Target: set default buffername for buffer attributes

number~: displaymode option (first / average)

oscquery runner: report if/when a preset was loaded

Raspberry Pi Target: add a device to the sidebar by address

Raspberry Pi Target: support for cloud compiling

Raspberry Pi Target: upload and manage multiple patches (hot swap)

Raspberry Pi Target: upload patcher without loading it

rnbo.remote: 'launchwebinterface' message to launch web interface from rnbo.remote

rnbo.remote: @patchername attribute to change current patch on device

rnbo~: dumptargetconfig message for getting the configuration dictionary for an export target (defaults c++)

rnbo~: export message for triggering a target export (defaults to c++)

codebox: allow const values in param declarations

codebox: fixed Int cast of bitwise operators

codebox: fixed parameter visibility in user defined functions

codebox: improved let/var declaration parsing

codebox: simplified Fixed Array initialization

counter/counter~: fixed crash when adding or removing ~ in object box

env2~: fixed an issue with release in hold mode

Export Sidebar: improved device add and delete UI

Export Sidebar: improved error message when Max is unauthed / authed via Live

Gen in RNBO: parameter with the name "t60" works

lockedphase~: removed (can still be used in codebox)

Max External Target: data can use Max buffers

Max External Target: overwrite warning references ‘external’

Max External Target: refpages in search path are not overwritten by new version of object

message: left inlet input always triggers output

param~: fixed issues when used in polyphonic top-level patchers

RNBO Object Inspector: shows enum attrs in a dropdown menu

RNBO patcher title bar: right-click title bar shows patcher filepath

samplerate: updates in the context of Max for Live

silencedetector~: fixed issues with cut off notes

silencedetector~: threshold and length options have some constraints

Themes: improved RNBO patcher legibility in non-default themes

VST Target: parameter automation improvements

We are happy to announce the release of Max 8.5.6 and RNBO 1.2.1. 

Cycling '74 Forums

We are happy to announce the release of Max 8.5.6 and RNBO 1.2.1.

why do you need transport at all ? is metro set to beatclock ticks interval and lock 1 not supposed to follow host sync ? I don't know if ...

Got it, that makes sense , thank you - I'll stick with the param/sig~ approach for now . Curious to see the next implementation of param~!

not with sprintf. but it makes me wonder how do you receive that message from pd, OSC ? something like gong\ 2 can not be part of a max ...

Cela semble être dû à une limitation de [sprintf], qui n'accepterait pas plus de 32 entrées.

Use pack i i i i instead of pak, and it should work as expected :-) (with pak, framerect is drawn 4 times for each bang...)

Hi Dunk, the right inlet of [sample] takes a 2-component vector representing the normalized position (aka between 0 and 1) at which the ...

jit.movie sometimes (like 1 out of 10) freezes playback after loading a movie. There's no error message and I can see the first frame.

very cool!

we'll need a patch to provide any insight

possibly helpful discussion - https://forum.openframeworks.cc/t/how-to-reduce-latency-when-projection-mapping-onto-moving-objects/42464