Hi,

I have a pd patch that's doing nearly everything I want but I have an .exe I want it to call (that just creates some files) at a certain point.

The problem is I'm running Windows and there doesn't seem to be a [shell] object for windows, is this true? Is there an alternative?

Thanks in advance.

Hi,

I want to be able to get webcam stream into PD using GEM but PD just crashes to desktop when I bang the [create( message to gemwin.

If I call [devices( on pix_video it finds 1 webcam (on my laptop) and the name is correct. I can set dimensions, change colorspace etc. but when I call [create( on gemwin it just quits to desktop.

I thought maybe I'd done something wrong so I just tried the example in the [pix_video] help patch but this crashes it too.

I only have 1 patch open at a time with [pix_video] so it's not that I'm calling it from 2 different sources.

I'm on Windows 8.1 64-bit if that makes any difference :-/

If anyone has any ideas what could be going on, it would be great to hear.

Thanks for your time.

Hi,

I have accelerometer data in a file and I want to be able to split it into 3 lists (one list containing all the X values, one for all the Ys, and one for all the Zs).

The file looks as follows:

0.34234
4.32423
0.3242
0.34322
4.232
0.3242

Where element 0 is X, element 1 is Y, element 2 is Z, element 3 is X and so on.

I'm trying to do it by banging the textfile object 3 times so it has 3 values in its list and then splitting these into 3 list objects using

twice (the left inlet of the first one going to X list, the other 2 values going into the next and then the left of that going into Y list and the middle going into Z list).

I then clear the textfile with [clear( and bang it again 3 times and so on.

This doesn't seem to be working quite correctly and I think it is quite a convoluted way to do quite a simple task (well a simple task if I was coding in C or something).

Does anyone have any ideas of an easier way to do this?

Thanks in advance.

Hi,

I have a device sending comma-delimited float lists which come into pd as a byte stream.

They look like this: 123,332.43,-34.4,39,111

I am converting the bytes to text using [bytes2any] which seems to work fine but when I then try and unpack, I get errors.

I tried using [unpack f s f s f s f] (for 4 floats, each with commas in between them) and just not linking up the outlets for the commas, this works but my console gets filled with "unpack: type mismatch", but my number boxes are getting the floats correctly.

This is okay but I'd rather not have those unpack errors.

So I looked at this forum thread and tried using [symbol2list] but got the "no method for 'float'" error mentioned in that thread. So I tried putting my message through [symbol] first which gets rid of the error but I have a really weird output. Instead of printing the list it prints:

"print: list l i s t"

for the list contents which seems very strange.

Could it be that putting my message through [symbol] is clearing the message (because it doesn't know what to do) and then when I try and put it through s2l I just get a list made out of the letters "list"?

Here is a kinda pseudo version of my code:

[comport 4 9600]
|
|
[bytes2any]
|
|
[symbol]
|
|
| _ _[ , (
| |
[s2l]
|
|
[print]

(Using the comma there for the message box).

Does anyone have any ideas?

Thanks in advance

Hi,

Thanks for reply - if I print straight from the stream it is in bytes but if I print after feeding the stream through [bytes2any] I get a line like:

610 , -244 , 48 , -4100 , 4 , 1 , 28 , -1224 , -27771 , 2145

If I just connect straight to the device (through tera term) the line is like:

610,-244,48,-4100,4,1,28,-1224,-27771,2145

So it looks like PD is adding spaces between the commas and numbers, does this mean it has turned it into a list? If so, then I guess that's why [symbol2list] wouldn't work for it.

But how would I cut out the commas and just have a float list I could unpack?

Thanks.

*bump*

Hey everyone, sorry I'm bumping this because (although it works) the pd window being filled with "unpack: type mismatch" is very annoying for debugging other parts of my patch.