vade

The shell external includes source, which ive attempted to re-compile 

as an mxo. due to my xcode and c inexperience, ive been unsuccessful. 

Id love to have it working in 4.6 properly.

The shell external includes source, which ive attempted to re-compile  
as an mxo. due to my xcode and c inexperience, ive been unsuccessful.  
Anyone care to give it a shot?

universal-binary-version-of-shell

> The shell external includes source, which ive attempted to re-compile as an

> mxo. due to my xcode and c inexperience, ive been unsuccessful. Anyone care

> Id love to have it working in 4.6 properly.

On 8/14/06, vade  wrote:
>
> Hello.
>
> The shell external includes source, which ive attempted to re-compile as an
> mxo. due to my xcode and c inexperience, ive been unsuccessful. Anyone care
> to give it a shot?
>
> Id love to have it working in 4.6 properly.
>
> Thanks,
>
>
>
> v a d e //
>
> www.vade.info
> abstrakt.vade.info
>
>
>
>


I've posted a version that appears to be working on my /share page:

https://cycling74.com/twiki/bin/view/Share/JeremyBernstein

Only tested on PPC, though. Let me know if it fails on Intel.

on a macbook pro 2ghz max4.6/ jitter1.6 the object seems to kinda work.

after being loaded for about 15 seconds it will start to send status

and do stuff, like create a new directory, so it's obviously doing

something, but it takes a little bit to warm up.

it keeps reporting "bang" in the max window, even though i should (if

i remember correctly) see things like, what's in the directory, etc.

so, sorta working, but not exactly as expected.

curious as to your changes, because i tried to compile it unaltered on

intel hardware and got the same errors as anton :

/Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:15:

error: redefinition of 'struct _opaque_pthread_mutex_t'

/Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:16:

error: redefinition of 'struct _opaque_pthread_cond_t'

> I've posted a version that appears to be working on my /share page:

> Only tested on PPC, though. Let me know if it fails on Intel.

after being loaded for about 15 seconds it will start to send status
and do stuff, like create a new directory, so it's obviously doing
something, but it takes a little bit to warm up.

it keeps reporting "bang" in the max window, even though i should (if
i remember correctly) see things like, what's in the directory, etc.

curious as to your changes, because i tried to compile it unaltered on
intel hardware and got the same errors as anton :

/Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:15:
error: redefinition of 'struct _opaque_pthread_mutex_t'

/Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:16:
error: redefinition of 'struct _opaque_pthread_cond_t'

On 8/15/06, Jeremy Bernstein  wrote:
> I've posted a version that appears to be working on my /share page:
>
> https://cycling74.com/twiki/bin/view/Share/JeremyBernstein
>
> Only tested on PPC, though. Let me know if it fails on Intel.
>
> jb
>


So, I got to my intel machine today, and tried this object (as found 

on my share site) out and... it worked fine. Can anyone else confirm 

Am 16.08.2006 um 01:57 schrieb Scott Fitzgerald:

> on a macbook pro 2ghz max4.6/ jitter1.6 the object seems to kinda 

> after being loaded for about 15 seconds it will start to send status

> and do stuff, like create a new directory, so it's obviously doing

> something, but it takes a little bit to warm up.

> it keeps reporting "bang" in the max window, even though i should (if

> i remember correctly) see things like, what's in the directory, etc.

> so, sorta working, but not exactly as expected.

> curious as to your changes, because i tried to compile it unaltered on

> intel hardware and got the same errors as anton :

> /Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:15:

> error: redefinition of 'struct _opaque_pthread_mutex_t'

> /Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:16:

> error: redefinition of 'struct _opaque_pthread_cond_t'

>> I've posted a version that appears to be working on my /share page:

>> Only tested on PPC, though. Let me know if it fails on Intel.

So, I got to my intel machine today, and tried this object (as found  
on my share site) out and... it worked fine. Can anyone else confirm  
or deny Scott's experiences on Intel?

> on a macbook pro 2ghz max4.6/ jitter1.6 the object seems to kinda  
> work.
>
> after being loaded for about 15 seconds it will start to send status
> and do stuff, like create a new directory, so it's obviously doing
> something, but it takes a little bit to warm up.
>
> it keeps reporting "bang" in the max window, even though i should (if
> i remember correctly) see things like, what's in the directory, etc.
>
> so, sorta working, but not exactly as expected.
>
> curious as to your changes, because i tried to compile it unaltered on
> intel hardware and got the same errors as anton :
>
> /Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:15:
> error: redefinition of 'struct _opaque_pthread_mutex_t'
>
> /Applications/MaxMSP 4.6/MaxMSP UB SDK/my-externs/shell/shell.c:16:
> error: redefinition of 'struct _opaque_pthread_cond_t'
>
> and a bunch of warnings
>
>
>
> On 8/15/06, Jeremy Bernstein  wrote:
>> I've posted a version that appears to be working on my /share page:
>>
>> https://cycling74.com/twiki/bin/view/Share/JeremyBernstein
>>
>> Only tested on PPC, though. Let me know if it fails on Intel.
>>
>> jb
>>


Yes, my experience seems to be pretty much the same as Scott's.

hm, ok. tomorrow, i'll release a new version, built on the Intel 

Am 23.08.2006 um 00:37 schrieb jbmaxwell:

> Yes, my experience seems to be pretty much the same as Scott's.

hm, ok. tomorrow, i'll release a new version, built on the Intel  
machine, and let's see how that works.

> Yes, my experience seems to be pretty much the same as Scott's.


This shell object don't work for me (on imac 2Ghz core duo)

There's only a bang coming on the right outlet for some function.

Nothing out of the left outlet nor direct to the max window.

it created a new folder in my user directory though.

the pkill button most of the time freeze max 4.6.2

I tried to recompile but the issues persist.

There's only a bang coming on the right outlet for some function.
Nothing out of the left outlet nor direct to the max window.

I tried to recompile but the issues persist.
Maybe that's due to a kind of CFM glue ?

This appears to be an Apple issue - we've observed the problem only 

on some machines (machines I don't have to test with - my MacMini Duo 

doesn't exhibit the behavior). The output of the object is being 

redirected to the Console. At this time, there's no workaround.

> This shell object don't work for me (on imac 2Ghz core duo)

> There's only a bang coming on the right outlet for some function.

> Nothing out of the left outlet nor direct to the max window.

> it created a new folder in my user directory though.

> the pkill button most of the time freeze max 4.6.2

> I tried to recompile but the issues persist.

> Maybe that's due to a kind of CFM glue ?

This appears to be an Apple issue - we've observed the problem only  
on some machines (machines I don't have to test with - my MacMini Duo  
doesn't exhibit the behavior). The output of the object is being  
redirected to the Console. At this time, there's no workaround.

>
> Hello,
>
> This shell object don't work for me (on imac 2Ghz core duo)
>
> There's only a bang coming on the right outlet for some function.
> Nothing out of the left outlet nor direct to the max window.
>
> it created a new folder in my user directory though.
>
> the pkill button most of the time freeze max 4.6.2
>
> I tried to recompile but the issues persist.
> Maybe that's due to a kind of CFM glue ?
>
> Salvator


> This appears to be an Apple issue - we've observed the problem only

> on some machines (machines I don't have to test with - my MacMini Duo

> doesn't exhibit the behavior). The output of the object is being

> redirected to the Console. At this time, there's no workaround.

If absolutely need feedback from the object, make an mxj that calls

shell commands. This is pretty straightforward.

On 9/30/06, Jeremy Bernstein  wrote:
> This appears to be an Apple issue - we've observed the problem only
> on some machines (machines I don't have to test with - my MacMini Duo
> doesn't exhibit the behavior). The output of the object is being
> redirected to the Console. At this time, there's no workaround.

If absolutely need feedback from the object, make an mxj that calls
shell commands.  This is pretty straightforward.

Hi list - this topic seems to be on several threads - just adding my 2 penneth to this one.

I get no output from calling the shell in any way - via java or externals, calling a script or direct. I'm trying to pipe my stuff to a file and it works fine on the terminal but zero's the file from Max.

MacBook Pro 2.16 GHz 2 GB OSX 10.4.8 Max 4.6.2

Universal Binary version of Shell?