David Stanford

[train~] seems to be ignoring its arguments, has an unexpected 

default pulse width, and outputs a value of 0 for 2000 ms after dsp 

[train~] generates a pulse wave with a period of 1000 ms, a pulse 

[train~ 5000 0.5] generates a pulse wave with a period of 5000 ms and 

Opening the patch using different methods should yield the same 

results. Behavior should be consistent after closing and reopening 

[train~] and [train~ 5000 0.5] both generate a pulse wave with a 

period of 1000 ms, a pulse width of 0.99, and an initial period of 

Opening the patch using different methods yields different results:

Copy text -> New Patcher -> Paste will yield the results listed above.

Copy text -> New from clipboard results in all [train~]s generating a 

pulse wave with a period of around 15ms, with the exception of 

[train~ 50], which will generate a pulse wave with a period of 1000 ms.

After the patch has been saved, closing the patch and reopening, 

without quitting MaxMSP, yields another set of results: After 

reopening the patch, all [train~]s generate a pulse wave with a 

Mac OS 10.4.7, PB G4 1.5, MaxMSP 4.6.1/Jitter 1.6.1

I have tried un/reinstalling MaxMSP. No change in behavior.

So - can anyone else confirm this, or is it my problem?

[train~] seems to be ignoring its arguments, has an unexpected  
default pulse width, and outputs a value of 0 for 2000 ms after dsp  
is started.

[train~] generates a pulse wave with a period of 1000 ms, a pulse  
width of 0.5.
[train~ 5000 0.5] generates a pulse wave with a period of 5000 ms and  
a pulse width of 0.5.

Opening the patch using  different methods should yield the same  
results. Behavior should be consistent after closing and reopening  
the patch.

[train~] and [train~ 5000 0.5] both generate a pulse wave with a  
period of 1000 ms, a pulse width of 0.99, and an initial period of  
2000 ms at a value of 0.

Opening the patch using  different methods yields different results:

Copy text -> New Patcher -> Paste will yield  the results listed above.

Copy text -> New from clipboard results in all [train~]s generating a  
pulse wave with a period of around 15ms, with the exception of  
[train~ 50], which will generate a pulse wave with a period of 1000 ms.

After the patch has been saved, closing the patch and reopening,  
without quitting MaxMSP, yields another set of results: After  
reopening the patch, all [train~]s generate a pulse wave with a  
period of around 50ms.

bug-train-in-4-6-1

Quote: David Stanford wrote on Tue, 29 August 2006 09:23

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

> [train~] seems to be ignoring its arguments, has an unexpected 

> default pulse width, and outputs a value of 0 for 2000 ms after dsp 

I am not having this problem. I tried a few different ways of making this patch, and they all work the way I would expect from the help file.

Quote: David Stanford wrote on Tue, 29 August 2006 09:23
----------------------------------------------------
> Summary:
>
> [train~] seems to be ignoring its arguments, has an unexpected  
> default pulse width, and outputs a value of 0 for 2000 ms after dsp  
> is started.
>

I am not having this problem.  I tried a few different ways of making this patch, and they all work the way I would expect from the help file.

Thanks for the report, we're looking at it.

bug: [train~] in 4.6.1?