well..

how about.. [tabright~ ] ?

:)

alabala

2009/8/3 Miller Puckette mpuckett@imusic1.ucsd.edu

Yep, it's a damn pity I used the tabwrite~ name for the wrong object! We're all stuck with it now.

I've been planning to put an object like this into Pd for many years, but can't think of a "correct" name... anyone have a better idea than "tabwriteat~"

?

cheers Miller

On Mon, Aug 03, 2009 at 02:51:07PM +0200, Frank Barknecht wrote:

...

Hi,

attached is code for an external [tabwriteat~] that I would wish would be part of Pd vanilla. It is the audio equivalent to [tabwrite] for messages and writes the signal coming in through the first audio inlet at positions coming in to the second audio inlet. So it's name should actually be [tabwrite~] but as you know this is already taken by something that acts more like having the name [tabrecord~]. :)

[tabwriteat~] is not well tested and I probably won't be able to maintain it.

Ciao

Frank Barknecht Do You RjDj.me? _

______footils.org__

...

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->

http://lists.puredata.info/listinfo/pd-list

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Hallo, Miller Puckette hat gesagt: // Miller Puckette wrote:

Yep, it's a damn pity I used the tabwrite~ name for the wrong object! We're all stuck with it now.

I've been planning to put an object like this into Pd for many years, but can't think of a "correct" name... anyone have a better idea than "tabwriteat~"

Here are a bunch of random ideas:

tabfill~, tabgraph~, tabset~, tabput~, arraywrite~, tabindex~, tabpush~, tabjam~, tabfeed~

Ciao

Frank

tabplot~ ?

On Mon, Aug 3, 2009 at 3:44 PM, ypatios ypatios@gmail.com wrote:

And some more:

tabstream~, vtabwrite~, tabrec~, writetab~, tabfloat~ ...

albl

2009/8/4 Frank Barknecht fbar@footils.org

Hallo,

...

Miller Puckette hat gesagt: // Miller Puckette wrote:

...

Yep, it's a damn pity I used the tabwrite~ name for the wrong object!

We're

...

all stuck with it now.

I've been planning to put an object like this into Pd for many years,

but

...

can't think of a "correct" name... anyone have a better idea than

"tabwriteat~"

Here are a bunch of random ideas:

tabfill~, tabgraph~, tabset~, tabput~, arraywrite~, tabindex~, tabpush~, tabjam~, tabfeed~

Ciao

Frank

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

-- ypatios

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

On Mon, Aug 3, 2009 at 7:01 PM, Chris McCormickchris@mccormick.cx wrote:

On Mon, Aug 03, 2009 at 12:30:29PM -0700, Miller Puckette wrote:

...

Yep, it's a damn pity I used the tabwrite~ name for the wrong object!  We're all stuck with it now.

I've been planning to put an object like this into Pd for many years, but can't think of a "correct" name... anyone have a better idea than "tabwriteat~"

Maybe you could pass [tabwrite~] an argument to specify whether it should have an extra 'index' inlet?

Chris.

Doesn't tabwrite~ have a second inlet to set the name of the array (It's been awhile)? If so, then what harm could there be in re-writing the object with 3 inlets? Would it break something?

Chuck

...or how about 'tabpoke~ ? That would suggest putting in one value at a time instead of shoveling them in en masse.

cheers M

On Tue, Aug 04, 2009 at 03:21:55PM +0200, Frank Barknecht wrote:

Hallo, Charles Henry hat gesagt: // Charles Henry wrote:

...

Doesn't tabwrite~ have a second inlet to set the name of the array (It's been awhile)? If so, then what harm could there be in re-writing the object with 3 inlets? Would it break something?

It just has one inlet, you change the table to set with "set NAME" messages into the first inlet.

So, yes, adding a second inlet should not change anything there. But it gets a bit tricky later on: How should you deal with a [bang( message that goes into the first inlet when there's something connected to the new audio-index inlet? There is a conflict of interest, which IMO is better solved with a new object.

Actually I like the name [tabfeed~], as it somehow describes, that with audio index inlets you kind of constantly feed data into the table.

Ciao

Frank

---

Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

Hmm, tabindex~ diesn't make it clear that stuff is actually going into the table.

vtabwrite~ sounds OK, as do tabpoke~ or tabput~ or tabwriteto~ ... ?

cheers M

On Thu, Aug 06, 2009 at 07:16:43PM +0900, hard off wrote:

[tabindex~] is the best one so far in my opinion.

not sure if it'd be technically correct, but what about: [vtabwrite~]

???

On Thu, Aug 6, 2009 at 12:06 PM, Frank Barknechtfbar@footils.org wrote:

I think, vtabwrite~ maybe could be used to make a "v"-version of tabwrite~, by which I mean something, that acts correctly with clock-delayed messages as vsnapshot~, vline~ etc. do.

That's a very good point--with the new tabwrite~ object, you're already going to have to change its [bang( behavior anyway. So why not add it to your desired feature set also?

There ought to be some way to start a recording with sub-block accuracy from clock-delayed messages, which is brilliant.

But I also think it exposes a sort of problem, like what things would go wrong when only part of the table has been written in a single block. Good patching solves this case-by-case, but there's a potential for things to go wrong somewhere.

Also, does that mean you'd be wanting at some point to add vtabplay~? or other vtabxxxxx~ rewrites?

So, at the risk of sounding lazy, do you really want to have that sort of growing project for an object you've already written? or just name it tabwriteto~?

Chuck

Miller Puckette wrote:

Hmm, tabindex~ diesn't make it clear that stuff is actually going into the table.

vtabwrite~ sounds OK, as do tabpoke~ or tabput~ or tabwriteto~ ... ?

cheers M

[tabpoke~] might also make more sense to converted Max/MSP users, as MSP uses [poke~] to access buffers. If that matters ;-).

.mmb