Miller

According to the Max reference, the waveform~ object supports a "line" command, which is supposed to display a vertical line at a position specified in ms. But I can't seem to get it to work. Has anyone successfully used this command?

Basically, I would like to be able to see on the waveform~ display where I am reading in an audio file.

waveform-line-command

On 20 avr. 08, at 19:10, Miller Peterson wrote:

> According to the Max reference, the waveform~ object supports a 

> "line" command, which is supposed to display a vertical line at a 

> position specified in ms. But I can't seem to get it to work. Has 

> Basically, I would like to be able to see on the waveform~ display 

Simply send the line message with the time (in ms) as argument.

> According to the Max reference, the waveform~ object supports a  
> "line" command, which is supposed to display a vertical line at a  
> position specified in ms. But I can't seem to get it to work. Has  
> anyone successfully used this command?
>
> Basically, I would like to be able to see on the waveform~ display  
> where I am reading in an audio file.

Yeah, I tried that but the line doesn't show up. Here is a sample patch:

Ah, great. If I send a float it shows up.

why isnt stuff like this in the help file!!! This is very useful and Ive wanted something like this before and why is it that 99% of the features are shown in the help files and then very useful ones like this arent there... ?!?!

Quote: Axiom-Crux wrote on Mon, 21 April 2008 12:24

----------------------------------------------------

> why isnt stuff like this in the help file!!! This is very useful and Ive wanted something like this before and why is it that 99% of the features are shown in the help files and then very useful ones like this arent there... ?!?!

Ah, another time it would be nice if my brain held the full contents of the reference manual....oh well, I guess I'm just stuck feeling silly for using the start and/or end points to track position.

Quote: Axiom-Crux wrote on Mon, 21 April 2008 12:24
----------------------------------------------------
> why isnt stuff like this in the help file!!! This is very useful and Ive wanted something like this before and why is it that 99% of the features are shown in the help files and then very useful ones like this arent there... ?!?!
----------------------------------------------------

Ah, another time it would be nice if my brain held the full contents of the reference manual....oh well, I guess I'm just stuck feeling silly for using the start and/or end points to track position.


If you wait a day or two, you will find that this information will be 

far more easy to gain access to. Your future is bright...

> -=ili!ili=- www.Axiom-Crux.net -=ili!ili=-

If you wait a day or two, you will find that this information will be 
far more easy to gain access to.  Your future is bright...

Nicholas C. Raftis III wrote:
> why isnt stuff like this in the help file!!! This is very useful and Ive wanted something like this before and why is it that 99% of the features are shown in the help files and then very useful ones like this arent there... ?!?!
> --
> -=ili!ili=-  www.Axiom-Crux.net  -=ili!ili=-
>


On 21 avr. 08, at 19:30, Chris Muir wrote:

> Well the requirement to send a float may be a bug, for one thing.

It's fixed for Max 5, and the doc will be just under the mouse ;-)

Any more fixing done on Waveform~ in M5? It's a very handy object, 

but it's unfortunately plagued by weird behaviour in its current (Max 

Op 21-apr-2008, om 22:42 heeft Emmanuel Jourdan het volgende geschreven:

> On 21 avr. 08, at 19:30, Chris Muir wrote:

>> Well the requirement to send a float may be a bug, for one thing.

> It's fixed for Max 5, and the doc will be just under the mouse ;-)

Any more fixing done on Waveform~ in M5? It's a very handy object,  
but it's unfortunately plagued by weird behaviour in its current (Max  
4) version.

> On 21 avr. 08, at 19:30, Chris Muir wrote:
>
>> Well the requirement to send a float may be a bug, for one thing.
>
>
> It's fixed for Max 5, and the doc will be just under the mouse ;-)
>
> ej
>


All UI objects have required re-writes for Max 5.

On 2008 Apr 21, at 4:18 PM, Zip Boterbloem wrote:

> Any more fixing done on Waveform~ in M5? It's a very handy object, 

> but it's unfortunately plagued by weird behaviour in its current 

> Op 21-apr-2008, om 22:42 heeft Emmanuel Jourdan het volgende 

>> On 21 avr. 08, at 19:30, Chris Muir wrote:

>>> Well the requirement to send a float may be a bug, for one thing.

>> It's fixed for Max 5, and the doc will be just under the mouse ;-)

All UI objects have required re-writes for Max 5.
best,
   Tim

On 2008 Apr 21, at 4:18 PM, Zip Boterbloem wrote:
> Any more fixing done on Waveform~ in M5? It's a very handy object,  
> but it's unfortunately plagued by weird behaviour in its current  
> (Max 4) version.
>
> Best,
>
> Zip
>
> Op 21-apr-2008, om 22:42 heeft Emmanuel Jourdan het volgende  
> geschreven:
>
>> On 21 avr. 08, at 19:30, Chris Muir wrote:
>>
>>> Well the requirement to send a float may be a bug, for one thing.
>>
>>
>> It's fixed for Max 5, and the doc will be just under the mouse ;-)
>>
>> ej
>>


> Any more fixing done on Waveform~ in M5? It's a very handy object, but 

> it's unfortunately plagued by weird behaviour in its current (Max 4) 

Zip Boterbloem wrote:
> Any more fixing done on Waveform~ in M5? It's a very handy object, but 
> it's unfortunately plagued by weird behaviour in its current (Max 4) 
> version.
>
> Best,
>
> Zip


Op 21-apr-2008, om 23:57 heeft Andrew Benson het volgende geschreven:

>> Any more fixing done on Waveform~ in M5? It's a very handy object, 

>> but it's unfortunately plagued by weird behaviour in its current 

> Just you wait...
>
> AB
>
> Zip Boterbloem wrote:
>> Any more fixing done on Waveform~ in M5? It's a very handy object,  
>> but it's unfortunately plagued by weird behaviour in its current  
>> (Max 4) version.
>>
>> Best,
>>
>> Zip
>


waveform~ line command