Sounds like they don't want ints and sending non decimal values as floats results in an int type tag in the OSC message. Try forcing all values to be floats with a [float] object.
On Aug 28, 2013, at 3:34 PM, pd-list-request@iem.at wrote:
From: Max abonnements@revolwear.com Subject: [PD] RME TotalMix controlled with OSC Date: August 28, 2013 2:33:32 PM EDT To: PD list pd-list@iem.at
Hi List, has anyone used OSC o control RME's TotalMix application? The OSC support in there seems rather flawed, for instance the float messages seem to require 1.0 format and 1 will be wrong. How can I sent floats in Pd which have a zero decimal?
m.
Dan Wilcox @danomatika danomatika.com robotcowboy.com
hm. since in Pd all numbers are floats printing a 1.0 will show 1 however I can use [makefilename %s.0] which seems to be a possible workaround.
Am 28.08.2013 um 21:58 schrieb Dan Wilcox danomatika@gmail.com:
Sounds like they don't want ints and sending non decimal values as floats results in an int type tag in the OSC message. Try forcing all values to be floats with a [float] object.
On Aug 28, 2013, at 3:34 PM, pd-list-request@iem.at wrote:
From: Max abonnements@revolwear.com Subject: [PD] RME TotalMix controlled with OSC Date: August 28, 2013 2:33:32 PM EDT To: PD list pd-list@iem.at
Hi List, has anyone used OSC o control RME's TotalMix application? The OSC support in there seems rather flawed, for instance the float messages seem to require 1.0 format and 1 will be wrong. How can I sent floats in Pd which have a zero decimal?
m.
Dan Wilcox @danomatika danomatika.com robotcowboy.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 28/08/13 21:10, Max wrote:
hm. since in Pd all numbers are floats printing a 1.0 will show 1 however I can use [makefilename %s.0] which seems to be a possible workaround.
[makefilename %f]
But then it might be sent as s string instead of a number (whether float or int).
What are you using to send OSC?
Claude
Yeah all numbers are floats ... but if I do this:
[3 < | [int] | [/osc/number $1 < | [packOSC] | [udpsend]
packOSC sets the argument type on the receiving end as an int. I've had that bite me in the past for osc apis that are only looking for ints instead of both ints & floats. I was thinking that [packOSC] might be interpreting a non-decimal float as an int, but I don't think so ...
On Aug 28, 2013, at 4:10 PM, Max abonnements@revolwear.com wrote:
hm. since in Pd all numbers are floats printing a 1.0 will show 1 however I can use [makefilename %s.0] which seems to be a possible workaround.
<forcedecimal.pd>
Am 28.08.2013 um 21:58 schrieb Dan Wilcox danomatika@gmail.com:
Sounds like they don't want ints and sending non decimal values as floats results in an int type tag in the OSC message. Try forcing all values to be floats with a [float] object.
On Aug 28, 2013, at 3:34 PM, pd-list-request@iem.at wrote:
From: Max abonnements@revolwear.com Subject: [PD] RME TotalMix controlled with OSC Date: August 28, 2013 2:33:32 PM EDT To: PD list pd-list@iem.at
Hi List, has anyone used OSC o control RME's TotalMix application? The OSC support in there seems rather flawed, for instance the float messages seem to require 1.0 format and 1 will be wrong. How can I sent floats in Pd which have a zero decimal?
m.
Dan Wilcox @danomatika danomatika.com robotcowboy.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Dan Wilcox @danomatika danomatika.com robotcowboy.com
Looking at the source, there seems to be a way to set explicit type tags. I haven't checked the help patch, maybe it is documented there.
On 28/08/13 21:26, Dan Wilcox wrote:
I was thinking that [packOSC] might be interpreting a non-decimal float as an int, but I don't think so ...
There is no other way it could be happening - because messages are arrays of atoms and there are no int atoms:
https://sourceforge.net/p/pure-data/svn/17199/tree/trunk/externals/mrpeach/o...
Claude
On 2013-08-28 16:44, Claude Heiland-Allen wrote:
Looking at the source, there seems to be a way to set explicit type tags. I haven't checked the help patch, maybe it is documented there.
On 28/08/13 21:26, Dan Wilcox wrote:
I was thinking that [packOSC] might be interpreting a non-decimal float as an int, but I don't think so ...
There is no other way it could be happening - because messages are arrays of atoms and there are no int atoms:
Yes, that's why. The default behaviour of [packOSC] checks if an incoming float is the same as its integer representation, if it is, send it as an integer. If Pd used the int atom it wouldn't need to do that.
Martin
-
Claude Heiland-Allen -
Dan Wilcox -
Martin Peach -
Max