Bug in waveform~ ruler values.
I am desperate. I am 99% sure there is a major bug in the waveform~ object ruler. Look at the attached pics and you can see they numbers make no sense at all. I have put a lot of work into this software and it is totally useless if the waveform~ ruler is incorrect.
Any suggestions? Has anybody else noticed this?
Can you isolate and send along a simple example patch that just displays the issue?
Hi Ben thanks for the speedy response.
Here is a simple patch and some screenshots of the bug using the same patch.
Hope it helps!
----------begin_max5_patcher---------- 746.3ocwV0rbaBCD9L9ofgyTORfkLzac5gdouAY5jQFjcTCHQEhjzlI8Yu5G CVxlF6jl1xAgzpcY28a2OgdbQTxFwCz9j32GeUbTziKhhrhLBh1uNJok7PUC o2pVRKsumrilj51SQePYkKocMjpI4hAUCUo9dG08wSRh+x9s1J3JNo0tQxGj LRynQcDU0ML9tqkzJkytbLXIHMFlYegbKJVBl9ZrZ62Qr4quKOwyC8reX8.L SahSLenkw0QkMQxNHzEqVoPivmVrvLjdgHBmdu16m.HaF1tkJ+Y7Vg32BJaa DDURpVYBe2eHB4vFbgYzfVygPvWBBAmEgxdEHz8j6naEx1eN596Hxo7abyON H6ExQMHJk75McsVWBVByxJJWseO4PCUZ1.bVb8Ylzv5suO.6cRZOkqHJlf6A vkVf0MhcfcF.5Av2oXU216GP8zFs4jltaHVwS.bPk8yCUrZR7mjDd8Dww01L oiW2SCYCsIvMVIa1UIZDRWrBVhxMOoyNyOn2Hj0TYfo3R.rDaL.WjkixCmcv TW1oAo.qAFkJPfxBqiBMYl9VDnXIxz2hbL6Ccwy04hSloH42ktS5zFNg0iMV mFkdCdIkpUTaA8bOprmwSpFvRPi3YXYHCBWiQFW.mJC.r9YcXYvVBOxQ91b5 LeqMMdsD4sdFag9CCGkhCblxOEC4132Bt8ywbY63BcGPiNr8qc+c4uE1Fr0q 73uli79uPeOpKAZHbvzYmcFxJ.hvEX+tY3kQQmq4eN5Iz8QA6+wa1I3lG6LC 8OjdBeMzyuMvnJeqCpDGQZNOAc8pRPV5LSNC67Bs7EwTsVooC7iuHmspZjGR e6ECxpQl196MEev20zdEiOU.uZ5lCd5bCqtlx8oLsr5NAiq5GKFydTxkFQ5S 6igmIhL8bdJc1PBCWsLC..PMVmCsmIrpz9JbUwZ6AEqzmgibqdCRFvkjLu.7 EAs2yKGf8yifUk1EHXo4urlEAogdwSK9ELqIG2B -----------end_max5_patcher-----------
I can’t reproduce what your images indicate.
On my machine, waveform is accurately representing the values of the attributes you have set. You have Timing Units set to BPM, and the Ruler BPM is set to something like 20.122894.
Can you put up an example audio file somewhere for me to download?
Are you running Max 5.0.3?
So i have replicated the bug on another computer. With an audio file you can download. It is not the only audio file that it happens with.
1. Open Max 5.0.3
2. replace buffer with 03.aif http://www.neongolden.net/media/03.aif
3. Zoom in to about bar 2.2
4. I get the same as the pic i attached earlier.
I really don’t have any idea why it is happening.
Let me know what you think.
Thanks for your persistence, i can see that there is something going on here. It seems like the math get a little funky when you use a bpm that has anything after the decimal seperator and you zoom in.
We will take a closer look.
just to clarify, it doesn’t seem to happen with all decimal numbers, just some, and it doesn’t seem to happen with shorter audio files.
Again, i’ll pass it along.