Jean-Francois Charles

 is an argument for [jit.buffer~], but I can't find how to change the buffer_name after initialization (without scripting).

- Why is the buffer_name not an attribute? Would this be a reasonable feature request?

- Other feature request: to implement the 

 attribute for jit.buffer~ - I can't change it either.

Let me know if I overlooked something, thanks.

buffer_name is an argument for [jit.buffer~], but I can't find how to change the buffer_name after initialization (without scripting).
- Why is the buffer_name not an attribute? Would this be a reasonable feature request?
- Other feature request: to implement the out_name attribute for jit.buffer~ - I can't change it either.
Let me know if I overlooked something, thanks.


jit-buffer-needs-buffer_name-and-out_name-attributes

If it seems complicated to change the buffer_name (should that also change the name of the underlying buffer~ object, what should happen if a buffer~ object has the same name: should it be renamed, or should another buffer~ be created?...), then another option could be to add a 

 message, to link a jit.buffer~ to an existing buffer~.

If it seems complicated to change the buffer_name (should that also change the name of the underlying buffer~ object, what should happen if a buffer~ object has the same name: should it be renamed, or should another buffer~ be created?...), then another option could be to add a refer message, to link a jit.buffer~ to an existing buffer~.


Something else while I'm at it: the attributes 

 work, but cannot be used as attributes: upon creation, [jit.buffer~ cool-sound 3000 @outputfirst 0] returns the following error to the Max window: 

buffer~: "outputfirst" is not a valid attribute argument"

Something else while I'm at it: the attributes outputfirst, outputlast, outputstart, outputlength work, but cannot be used as attributes: upon creation, [jit.buffer~ cool-sound 3000 @outputfirst 0] returns the following error to the Max window: buffer~: "outputfirst" is not a valid attribute argument"
(Max 6 & Max 7, Mac OSX).


Why would you not use the replace message to jit.buffer~ to change the underlying audio data. I have done this extensively and it works fine.

Regarding the "not a valid attribute argument" messages - you can ignore these. As I understand it, the error messages are known bugs and not likely to be fixed. The attributes are set for jit.buffer~ properly, despite appearances -- it's just that the attributes don't exist in the underlying buffer~ object, so it throws errors.

Why would you not use the replace message to jit.buffer~ to change the underlying audio data.  I have done this extensively and it works fine.

Regarding the "not a valid attribute argument" messages -   you can ignore these.  As I understand it, the error messages are known bugs and not likely to be fixed.  The attributes are set for jit.buffer~ properly, despite appearances --  it's just that the attributes don't exist in the underlying buffer~ object, so it throws errors.


Thanks Jesse. Actually, my bad about the 

 message: we can rename a jit.buffer~ the same way we rename a buffer~, with the name message, since [jit.buffer~] does support all of the messages supported by [buffer~].

We still need an out_name attribute, though.

Thanks Jesse. Actually, my bad about the name message: we can rename a jit.buffer~ the same way we rename a buffer~, with the name message, since [jit.buffer~] does support all of the messages supported by [buffer~].
We still need an out_name attribute, though.


jit.buffer~ needs buffer_name and out_name attributes