Fluid.waveform~ not updating markers

Bug Reports and Issues
1

Using FluCoMa 1.0.0-TB2 beta4 in Max 8.2.1

It would seem that the markers don’t update when e.g. changing the threshold of a slicer and resending the markers message. They just get stacked on top. Refresh message does nothing either, it requires a fresh new waveform object. Minor thing but it would be nice to have snappy updating for fine tuning.

2

Dear Jesse

I’m pretty sure it is sorted in the current nightly version. If you are comfortable with all its new features you can read about it and download here and confirm it is still happening for you.

If you prefer you can wait for the official beta5 release which we hope should happen in the next few weeks.

1 Like
3

Yep, sure enough, that fixed it. You guys rock.

2 Likes
4

fluid.waveform~.maxhelp suggests that markers can be edited edited within UI :
user can add / move / remove markers
BUT : corresponding buffer~ containing markers is not updated accordingly.
Am I missing something ?
If it’s expected behavior, so what’s the point of editing markers in the UI, but not updating associated buffer ?..

BTW : correct shortcut to remove markers on windows is Ctrl + Maj + click


----------begin_max5_patcher----------
1367.3oc6XsziaaCD97Ff7efPmZQcE3aQVDTr.4bA5sdHHXgrLsWsqjngj75
MMn42dGRJYK60u1D4zVfdX0rjVZd7oYlug5yu8M2DM09roIB8KnOft4lOC6b
ieO2N2zuwMQkoOmUj13uwnLaYoopMZR2O1Zdt0+Cuust.8SneK8A356KxydD
0ZQ0lR6SFTYZ8il5FzO7G4Uyrqa9w3MJXYsoATXZats5th7JSlcUkWkzM2RZ
a184UKtq1j0FbWJFGimfDAAmQbBpHFi9X+SUspLupvz58axP+MyVXqC5AGqR
vBkhxDTMmPTSfsvDgTIoIbAVqv7CtEYnolaqZmmlY1wRf8sqZ6c.b+14y7vk
c5C+LkEMTCM4+YPCxXre6+5suwIAwjK98yzUss1pnS.cBpG4ndjix6udNfa2
vgr0.0oklVS8clpzoEliFqzM9TPMseZoI3PQSSqVDg93WcLWYVCl3kojsnom
GH3JgSvTdff8UCDChUh75EqklllzElWFr3XThTAWIBlDDzDIWEiXDJiBBAi5
VozDXEWJzfPvST7XjjxkfHAS3NQhBRGPJIFxCQZlTCBBlvR7RMV3jDNwulHS
XxsEy6T+xNK1K6RB0gh4iC9zWA3yNN3eMRxlWrJeV7zUyoE4MsnaarqpyLn6
MEKiWOOF52kmAMYOeAYR.KnmKQ7UfEmHOz4reKvwQ4AlUmtF0duA0T3BbTZy
lt+1JfRXIxN2+6qSexL2VWhVm2de+c+tN7Bvy4l5eE8tZCHMUYltcNbp1IoJ
zc.q1Wmi8nMjz95oJHdJBntJPYL4h2RP2wVmgVHIZ7eqTl9H7FwV1+Z4T4i.
KnChHBnwnTh4bZBVqozDMrY.EuDl1oql1wGbbDEOYvExd57LvDOZ7ah1kEtW
w6l0M0YmB3zzPoqHV.QCz2bzJjEWmdZmeXgPHcvTguaiNvtdroGsd42SyqZ8
soB8c9hqqU5pY4VzZn0UdQApwrXmm8PURgVOcETTo7eK0N5qQwylF5WX4hH3
4gY.HcivOJkK5qS4xCMqxO74V1FTRFOVjvXZolRHhDEKw0KPDS4LUhP4NHAi
JYgytHzRtDm.BlNANUAiKi4JhatLAUBChoEaQiiN5.U4gPIVFKjfZUDLSwSD
9yon.DUln0XJrlITBw0tb8zn+lS7jW.5ozLXHp9DnuD+PyAwYu+L5Sv0Wg+J
FYSxCIsZn6GQInDXTZFAPbWi+u1iRPOzzrm.LmWXSg1OWuyOsYzVaUC3iNtw
u7hAbghbzs6ST1u9VHgoNOCoQ21dO7h7dawLngE6BnbNDzJ3zwCZo3SjmN4a
qSgCB2ibEhx.pdpXGJ3C7sIPk797sgwXwCi8ooYOtnFlBd1K3JrOYp2guvOI
Z+kc3K7Jv3UgzYjdrZQkEbM2mxYen8..dgYQZ1m1gk53bWLNzOZxA9mW6mUg
8hjV5N4w1pA1kzwTt8xvlqmn61zE6qEbbh+iF49uvf96ouUPEy9uENDUEibl
rP3OelyPMOcwf3Z6PCK1IZA1Eu6s8p2A+tmSyEpA77+eV7EkES9uUVrl8OaV
bPu9uIv9eOaeFo6G1K2NPi04i8egRzfXelooMuZybGeXymTAcxpnK1dD4kXu
duZDLnavryaPx3EgWT.59dcHxnXuKJ91GEJymszB4lc4MBs+v6vfFfPR1rXT
bPwH3fDr2ofSGr0C8KFmbjKJmDOZoH8p5zFTbP60UzmtbIzdpo6IBlBXtdHz
AQMIrNuJrVDVWadJu+QBCGFkVCLWs.s0p5vgRdVxi5dZ6LScEb3utye3BVmo
8jitCwzrrqAumD8suAtg+FDyq5PA
-----------end_max5_patcher-----------
5

Hello,

It’s always been the intention to enable this, just haven’t got round to implementing it yet.

IIRC, from when I looked at it the first time, there’s no real way of resizing a buffer~ from JS, so the best we might be able to do is dumping a list of markers to be fed back to a buffer~ via fluid.list2buf.

6

thanks for your reply

that would certainly do the trick :slight_smile:

maybe adding some messages when markers are added / updated / removed could be useful as well.

7

Hello,

Does fluid.waveform~ now update the buffer~ containing each of the markers? This feature would be useful for a patch in development.

Thanks

8

Not yet, but there are workarounds you can probably code in JS. It is not on my immediate radar to add that feature sadly.

1 Like