Hi list,I'm done implementing the Windows menu in the GUI port. Now-- does anyone ever use the Array List View? Can't this just be a GOP abstraction? Especially since it doesn't allow keyboard-only entry... On the other hand, if you widen the window you get this fat motif scrollbar, which is fun...
-Jonathan
Array list view is useful for debugging. I rarely open it via properties menu, but mostly via message 'arrayviewlistnew' (not even sure if this is documented).
On Thu, Nov 12, 2015 at 3:45 AM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Hi list, I'm done implementing the Windows menu in the GUI port.
Now-- does anyone ever use the Array List View?
Can't this just be a GOP abstraction? Especially since it doesn't allow keyboard-only entry...
On the other hand, if you widen the window you get this fat motif scrollbar, which is fun...
-Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Somehow I didn't know about this, but now I intend to use it all the time. Thanks for the "arrayviewlistnew" hint, too.
On Thu, Nov 12, 2015 at 2:32 AM, katja katjavetter@gmail.com wrote:
Array list view is useful for debugging. I rarely open it via properties menu, but mostly via message 'arrayviewlistnew' (not even sure if this is documented).
On Thu, Nov 12, 2015 at 3:45 AM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Hi list, I'm done implementing the Windows menu in the GUI port.
Now-- does anyone ever use the Array List View?
Can't this just be a GOP abstraction? Especially since it doesn't allow keyboard-only entry...
On the other hand, if you widen the window you get this fat motif scrollbar, which is fun...
-Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Would you mind if this opened a Pd patch instead of a tk dialog? -Jonathan
On Thursday, November 12, 2015 11:53 AM, Matt Barber <brbrofsvl@gmail.com> wrote:
Somehow I didn't know about this, but now I intend to use it all the time. Thanks for the "arrayviewlistnew" hint, too. On Thu, Nov 12, 2015 at 2:32 AM, katja katjavetter@gmail.com wrote:
Array list view is useful for debugging. I rarely open it via properties menu, but mostly via message 'arrayviewlistnew' (not even sure if this is documented).
On Thu, Nov 12, 2015 at 3:45 AM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
Hi list,I'm done implementing the Windows menu in the GUI port. Now-- does anyone ever use the Array List View? Can't this just be a GOP abstraction? Especially since it doesn't allow keyboard-only entry... On the other hand, if you widen the window you get this fat motif scrollbar, which is fun...
-Jonathan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
I don't know. Something like this with the guts hidden? I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype. So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly. And then I can get rid of all the arraylistview C/GUI code that's scattered about. -Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com> wrote:
A Pd patch with what in it? On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's scattered about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber brbrofsvl@gmail.com wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
I use it often to check if the array has received new values, sometimes it is used to change array values.
hi katja,I don't understand that last paragraph. Why would you need to close the array list view for an audio-length array? From what I can tell it's not "live"-- that is, it doesn't automatically update its values to stay in sync with the array. -Jonathan
On Friday, November 13, 2015 4:00 AM, katja <katjavetter@gmail.com> wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden? I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype. So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly. And then I can get rid of all the arraylistview C/GUI code that's scattered about. -Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com> wrote:
A Pd patch with what in it? On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
On Fri, Nov 13, 2015 at 5:02 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
hi katja, I don't understand that last paragraph. Why would you need to close the array list view for an audio-length array? From what I can tell it's not "live"-- that is, it doesn't automatically update its values to stay in sync with the array.
Normally the list view isn't updated but I've seen cases where Pd hangs when an object writes into an array with open list view. I don't remember the exact conditions. It helped to automatically close the list view before writing again. I could dig into my test patches to find details, but it is a useful option anyhow.
-Jonathan
On Friday, November 13, 2015 4:00 AM, katja katjavetter@gmail.com wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's scattered about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber brbrofsvl@gmail.com wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Thanks. That sounds like all the more reason to have this as a Pd patch instead. Even if I add a little mechanism to poll the area for changes, it's going to be discoverable inside a subpatch. That means if there is trouble, any user can open it and inspect the innards. -Jonathan
On Friday, November 13, 2015 3:27 PM, katja <katjavetter@gmail.com> wrote:
On Fri, Nov 13, 2015 at 5:02 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
hi katja,I don't understand that last paragraph. Why would you need to close the array list view for an audio-length array? From what I can tell it's not "live"-- that is, it doesn't automatically update its values to stay in sync with the array.
Normally the list view isn't updated but I've seen cases where Pd hangs when an object writes into an array with open list view. I don't remember the exact conditions. It helped to automatically close the list view before writing again. I could dig into my test patches to find details, but it is a useful option anyhow.
-Jonathan
On Friday, November 13, 2015 4:00 AM, katja <katjavetter@gmail.com> wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden? I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype. So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly. And then I can get rid of all the arraylistview C/GUI code that's scattered about. -Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com> wrote:
A Pd patch with what in it? On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
That's just a matter of creating a single number box and connecting its output to [s $0-offset]. Well, there's bounds checking, too-- the point is it's all just a Pd patch so you're unlikely to crash Pd by revising the functionality. Plus the barrier to entry is much lower than the small number of people who can untangle garray-related spaghetti code. -Jonathan
On Friday, November 13, 2015 4:00 AM, katja <katjavetter@gmail.com> wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden? I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype. So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly. And then I can get rid of all the arraylistview C/GUI code that's scattered about. -Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com> wrote:
A Pd patch with what in it? On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
I did some revisions on an abstraction replacement for the listview button in the array dialog.
Rather than hook into a button buried in a dialog, I'm going to just throw theabstraction in "extra" somewhere. That's about as discoverable as it currently is, plus one could use it as a control in a patch if they wish. But the best part is that it requires zero code in the core/GUI, opening up revisions and bugfixes to anyone who can write a Pd patch.
Improvements welcome, as well as shorter abstraction name (as long as it's obscure enough not to clash with anything else). -Jonathan
On Thursday, November 19, 2015 12:20 PM, Jonathan Wilkes via Pd-list <pd-list@lists.iem.at> wrote:
That's just a matter of creating a single number box and connecting its output to [s $0-offset]. Well, there's bounds checking, too-- the point is it's all just a Pd patch so you're unlikely to crash Pd by revising the functionality. Plus the barrier to entry is much lower than the small number of people who can untangle garray-related spaghetti code. -Jonathan
On Friday, November 13, 2015 4:00 AM, katja <katjavetter@gmail.com> wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden? I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype. So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly. And then I can get rid of all the arraylistview C/GUI code that's scattered about. -Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com> wrote:
A Pd patch with what in it? On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi Jonathan,
Your concept is a great improvement over built-in array list view. It is now a very useful debug tool since you can jump to any desired index no matter how long the array is. Thank you for this new year's present.
I figured out some refinements. Attached version has:
- buttons: offset inc / dec by 1 or 10, set to min / max offset, refresh
- inlet for offset, refresh, and array name message
- outlets for index / value pairs and offset
- toggle to activate console printout
It is temporarily called 'arraylistview2' for evaluation, and a patch with tests is included in the tarball. An issue with the name anyhow is confusion between 'arraylistview' and 'arrayviewlist'. Pd's built-in method goes with message 'arrayviewlistnew'. Maybe it could be a completely different name, like 'tabviewer'.
Jonathan, your approach makes me realize once more how powerful Pd is as a framework / language for dsp prototyping. Imagine a whole collection of debug instruments along the same line, like zoom viewer, spectrum viewer etc. Each tool would do a small job and they could be chained together by array name and index offset. Yummy.
cheers, Katja
On Wed, Dec 30, 2015 at 4:15 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I did some revisions on an abstraction replacement for the listview button in the array dialog.
Rather than hook into a button buried in a dialog, I'm going to just throw the abstraction in "extra" somewhere. That's about as discoverable as it currently is, plus one could use it as a control in a patch if they wish. But the best part is that it requires zero code in the core/GUI, opening up revisions and bugfixes to anyone who can write a Pd patch.
Improvements welcome, as well as shorter abstraction name (as long as it's obscure enough not to clash with anything else).
-Jonathan
On Thursday, November 19, 2015 12:20 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
That's just a matter of creating a single number box and connecting its output to [s $0-offset].
Well, there's bounds checking, too-- the point is it's all just a Pd patch so you're unlikely to crash Pd by revising the functionality. Plus the barrier to entry is much lower than the small number of people who can untangle garray-related spaghetti code.
-Jonathan
On Friday, November 13, 2015 4:00 AM, katja katjavetter@gmail.com wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's scattered about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber brbrofsvl@gmail.com wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Fri, Jan 1, 2016 at 8:24 PM, katja katjavetter@gmail.com wrote:
Hi Jonathan,
Your concept is a great improvement over built-in array list view. It is now a very useful debug tool since you can jump to any desired index no matter how long the array is.
...
Before someone else points out the incorrectness of this statement I'll do it myself: not all indexes above 2^24 can be accessed, because of imprecision. This is everything above ~ 6 min 20 seconds at SR 44100.
Katja
Hi katja,Thanks! I'll have a look at your revisions. "tabview" sounds like a decent name, as long as it isn't used anywhere else in Pd-land. Just an fyi-- I gutted all the arrayviewlist functionality for the GUI port of Pd-l2ork. Best,Jonathan
On Friday, January 1, 2016 2:24 PM, katja <katjavetter@gmail.com> wrote:
Hi Jonathan,
Your concept is a great improvement over built-in array list view. It is now a very useful debug tool since you can jump to any desired index no matter how long the array is. Thank you for this new year's present.
I figured out some refinements. Attached version has:
- buttons: offset inc / dec by 1 or 10, set to min / max offset, refresh
- inlet for offset, refresh, and array name message
- outlets for index / value pairs and offset
- toggle to activate console printout
It is temporarily called 'arraylistview2' for evaluation, and a patch with tests is included in the tarball. An issue with the name anyhow is confusion between 'arraylistview' and 'arrayviewlist'. Pd's built-in method goes with message 'arrayviewlistnew'. Maybe it could be a completely different name, like 'tabviewer'.
Jonathan, your approach makes me realize once more how powerful Pd is as a framework / language for dsp prototyping. Imagine a whole collection of debug instruments along the same line, like zoom viewer, spectrum viewer etc. Each tool would do a small job and they could be chained together by array name and index offset. Yummy.
cheers, Katja
On Wed, Dec 30, 2015 at 4:15 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I did some revisions on an abstraction replacement for the listview button in the array dialog.
Rather than hook into a button buried in a dialog, I'm going to just throw the abstraction in "extra" somewhere. That's about as discoverable as it currently is, plus one could use it as a control in a patch if they wish. But the best part is that it requires zero code in the core/GUI, opening up revisions and bugfixes to anyone who can write a Pd patch.
Improvements welcome, as well as shorter abstraction name (as long as it's obscure enough not to clash with anything else).
-Jonathan
On Thursday, November 19, 2015 12:20 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
That's just a matter of creating a single number box and connecting its output to [s $0-offset].
Well, there's bounds checking, too-- the point is it's all just a Pd patch so you're unlikely to crash Pd by revising the functionality. Plus the barrier to entry is much lower than the small number of people who can untangle garray-related spaghetti code.
-Jonathan
On Friday, November 13, 2015 4:00 AM, katja katjavetter@gmail.com wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's scattered about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber brbrofsvl@gmail.com wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
This is excellent, thanks. If Pd-l2ork includes the new [array] object suite, it may be worth it to use that instead of [expr] to get the array size, just for the sake of best practices.
I like the idea of a spectrum viewer. I'm including at least an [array-rfft], and probably the complex and inverse transforms with my array-abs. If I remember correctly the residual error vis-a-vis [rfft~] is in the ballpark of N/(10^9) and N/(10^12). It takes about 3 mins to calculate the rfft of a 2^24-point window, though. :)
I'm way behind on a composition and busy with baby twins at the moment, but I can make it available in the next couple of days if it would be useful at all. I feel bad that I haven't been able to contribute as much as I would like to Pd and Pd-l2ork the last few years.
On Fri, Jan 1, 2016 at 6:07 PM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
Hi katja, Thanks! I'll have a look at your revisions.
"tabview" sounds like a decent name, as long as it isn't used anywhere else in Pd-land. Just an fyi-- I gutted all the arrayviewlist functionality for the GUI port of Pd-l2ork.
Best, Jonathan
On Friday, January 1, 2016 2:24 PM, katja katjavetter@gmail.com wrote:
Hi Jonathan,
Your concept is a great improvement over built-in array list view. It is now a very useful debug tool since you can jump to any desired index no matter how long the array is. Thank you for this new year's present.
I figured out some refinements. Attached version has:
- buttons: offset inc / dec by 1 or 10, set to min / max offset, refresh
- inlet for offset, refresh, and array name message
- outlets for index / value pairs and offset
- toggle to activate console printout
It is temporarily called 'arraylistview2' for evaluation, and a patch with tests is included in the tarball. An issue with the name anyhow is confusion between 'arraylistview' and 'arrayviewlist'. Pd's built-in method goes with message 'arrayviewlistnew'. Maybe it could be a completely different name, like 'tabviewer'.
Jonathan, your approach makes me realize once more how powerful Pd is as a framework / language for dsp prototyping. Imagine a whole collection of debug instruments along the same line, like zoom viewer, spectrum viewer etc. Each tool would do a small job and they could be chained together by array name and index offset. Yummy.
cheers, Katja
On Wed, Dec 30, 2015 at 4:15 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I did some revisions on an abstraction replacement for the listview
button
in the array dialog.
Rather than hook into a button buried in a dialog, I'm going to just
throw
the abstraction in "extra" somewhere. That's about as discoverable as it currently is, plus one could use it as a control in a patch if they wish. But the best part is that it requires zero code in the core/GUI, opening up revisions and bugfixes to anyone who can write a Pd patch.
Improvements welcome, as well as shorter abstraction name (as long as
it's
obscure enough not to clash with anything else).
-Jonathan
On Thursday, November 19, 2015 12:20 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
That's just a matter of creating a single number box and connecting its output to [s $0-offset].
Well, there's bounds checking, too-- the point is it's all just a Pd
patch
so you're unlikely to crash Pd by revising the functionality. Plus the barrier to entry is much lower than the small number of people who can untangle garray-related spaghetti code.
-Jonathan
On Friday, November 13, 2015 4:00 AM, katja katjavetter@gmail.com
wrote:
That looks good Jonathan. In current array list view the entries are
grouped
per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a
specific
range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio
array
list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com
wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and
immediately
send a message to the relevant $0- receiver, and the patch will populate
the
value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's
scattered
about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber <brbrofsvl@gmail.com
wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com
wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Yeah, I just haven't ported the [array] and [text] stuff yet. -Jonathan
On Friday, January 1, 2016 6:32 PM, Matt Barber <brbrofsvl@gmail.com> wrote:
This is excellent, thanks. If Pd-l2ork includes the new [array] object suite, it may be worth it to use that instead of [expr] to get the array size, just for the sake of best practices. I like the idea of a spectrum viewer. I'm including at least an [array-rfft], and probably the complex and inverse transforms with my array-abs. If I remember correctly the residual error vis-a-vis [rfft~] is in the ballpark of N/(10^9) and N/(10^12). It takes about 3 mins to calculate the rfft of a 2^24-point window, though. :) I'm way behind on a composition and busy with baby twins at the moment, but I can make it available in the next couple of days if it would be useful at all. I feel bad that I haven't been able to contribute as much as I would like to Pd and Pd-l2ork the last few years. On Fri, Jan 1, 2016 at 6:07 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
Hi katja,Thanks! I'll have a look at your revisions. "tabview" sounds like a decent name, as long as it isn't used anywhere else in Pd-land. Just an fyi-- I gutted all the arrayviewlist functionality for the GUI port of Pd-l2ork. Best,Jonathan
On Friday, January 1, 2016 2:24 PM, katja <katjavetter@gmail.com> wrote:
Hi Jonathan,
Your concept is a great improvement over built-in array list view. It is now a very useful debug tool since you can jump to any desired index no matter how long the array is. Thank you for this new year's present.
I figured out some refinements. Attached version has:
- buttons: offset inc / dec by 1 or 10, set to min / max offset, refresh
- inlet for offset, refresh, and array name message
- outlets for index / value pairs and offset
- toggle to activate console printout
It is temporarily called 'arraylistview2' for evaluation, and a patch with tests is included in the tarball. An issue with the name anyhow is confusion between 'arraylistview' and 'arrayviewlist'. Pd's built-in method goes with message 'arrayviewlistnew'. Maybe it could be a completely different name, like 'tabviewer'.
Jonathan, your approach makes me realize once more how powerful Pd is as a framework / language for dsp prototyping. Imagine a whole collection of debug instruments along the same line, like zoom viewer, spectrum viewer etc. Each tool would do a small job and they could be chained together by array name and index offset. Yummy.
cheers, Katja
On Wed, Dec 30, 2015 at 4:15 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I did some revisions on an abstraction replacement for the listview button in the array dialog.
Rather than hook into a button buried in a dialog, I'm going to just throw the abstraction in "extra" somewhere. That's about as discoverable as it currently is, plus one could use it as a control in a patch if they wish. But the best part is that it requires zero code in the core/GUI, opening up revisions and bugfixes to anyone who can write a Pd patch.
Improvements welcome, as well as shorter abstraction name (as long as it's obscure enough not to clash with anything else).
-Jonathan
On Thursday, November 19, 2015 12:20 PM, Jonathan Wilkes via Pd-list pd-list@lists.iem.at wrote:
That's just a matter of creating a single number box and connecting its output to [s $0-offset].
Well, there's bounds checking, too-- the point is it's all just a Pd patch so you're unlikely to crash Pd by revising the functionality. Plus the barrier to entry is much lower than the small number of people who can untangle garray-related spaghetti code.
-Jonathan
On Friday, November 13, 2015 4:00 AM, katja katjavetter@gmail.com wrote:
That looks good Jonathan. In current array list view the entries are grouped per 1000 and arrows let you switch groups. For 'large' arrays (say one second of audio samples) this is inconvenient. Maybe your patch approach could even provide a better solution, like the option to select a specific range.
There's also method 'arrayviewclose' which I sometimes (ab)use to close a list view from within a patch. You don't want to try update an audio array list view in real time!
On Fri, Nov 13, 2015 at 1:32 AM, Jonathan Wilkes jancsika@yahoo.com wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's scattered about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber brbrofsvl@gmail.com wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
anyway nice idea, jonathan! thanks for this patch.
On Fri, Nov 13, 2015 at 9:32 AM, Jonathan Wilkes via Pd-list < pd-list@lists.iem.at> wrote:
I don't know. Something like this with the guts hidden?
I didn't do the hard stuff, like handling out-of-bounds elements if the array isn't a multiple of ten-- it's just a prototype.
So, in that method you and katja are abusing, I can forward the arrayname as well as the current $0 count. Then I can open the patch and immediately send a message to the relevant $0- receiver, and the patch will populate the value table accordingly.
And then I can get rid of all the arraylistview C/GUI code that's scattered about.
-Jonathan
On Thursday, November 12, 2015 4:55 PM, Matt Barber brbrofsvl@gmail.com wrote:
A Pd patch with what in it?
On Thu, Nov 12, 2015 at 4:21 PM, katja katjavetter@gmail.com wrote:
On Thu, Nov 12, 2015 at 8:36 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
Would you mind if this opened a Pd patch instead of a tk dialog?
Could be OK if the list is editable, like current array list view.
Katja
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Billy Stiltner -
Jonathan Wilkes -
Jonghyun Kim -
katja -
Matt Barber