Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

csound~ 1.1.2 on Max 6.1.7 32 bit Windows does not load #345

Closed
alfonso73 opened this issue Jun 18, 2014 · 84 comments
Closed

csound~ 1.1.2 on Max 6.1.7 32 bit Windows does not load #345

alfonso73 opened this issue Jun 18, 2014 · 84 comments
Assignees
Milestone

Comments

@alfonso73
Copy link

Hi all,

  1. if i install csound~ in the Package directory of Max the external is not recognized
  2. if i install csound~ in the externals' directory of Max the external is recognized but does not load 'cause the system complains about a missing "pthreadGC2.dll" file.
  3. If i place a "pthreadGC2.dll" file in the Csound directory the warni9ng about the missing file disappear but the Max window says " Error 193 loading external csound~"

thanks and all the best

@kunstmusik
Copy link
Member

@alfonso73 : Besides csound~, what version of Csound do you have installed? Is it 6.03.2? Also, did you install csound using the standard location in "C:\Program Files(x86)"

I just installed Max 6.1.7 32-bit and was able to load a demo file. I'd just check if running "csound" on the command line work too to ensure it's on the PATH (which might affect csound~ finding the csound library).

@kunstmusik kunstmusik self-assigned this Jun 26, 2014
@kunstmusik
Copy link
Member

@alfonso73 : any word? I'll need further information to continue with this issue.

@alfonso73
Copy link
Author

Hi Steven,
sorry i missed this one!
now i'm touring for a few piano gigs. so no laptop with me.
as soon as i get back home on Jul 27 i'll do all the needed checks.
Many thanks and i'll be back to you very soon.
a,

Il mercoledì 23 luglio 2014, Steven Yi notifications@github.com ha
scritto:

@alfonso73 https://github.com/alfonso73 : any word? I'll need further
information to continue with this issue.


Reply to this email directly or view it on GitHub
#345 (comment).

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

@kunstmusik
Copy link
Member

Sounds good, good luck with your gigs and thanks for the update!

On Wed, Jul 23, 2014 at 10:44 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
sorry i missed this one!
now i'm touring for a few piano gigs. so no laptop with me.
as soon as i get back home on Jul 27 i'll do all the needed checks.
Many thanks and i'll be back to you very soon.
a,

Il mercoledì 23 luglio 2014, Steven Yi notifications@github.com ha
scritto:

@alfonso73 https://github.com/alfonso73 : any word? I'll need further
information to continue with this issue.


Reply to this email directly or view it on GitHub
#345 (comment).

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

Hi Steven,

yes i have Csound 6.03.2 installed in the standard location C:\Program
Files(x86)

but i have this error in max

"Error 193 loading external csound~"

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Jun 26, 2014 at 6:04 PM, Steven Yi notifications@github.com wrote:

@alfonso73 https://github.com/alfonso73 : Besides csound~, what version
of Csound do you have installed? Is it 6.03.2? Also, did you install csound
using the standard location in "C:\Program Files(x86)"

I just installed Max 6.1.7 32-bit and was able to load a demo file. I'd
just check if running "csound" on the command line work too to ensure it's
on the PATH (which might affect csound~ finding the csound library).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

hi Steven!
some news?
thanks and all the best!
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Jul 23, 2014 at 4:47 PM, Steven Yi notifications@github.com wrote:

Sounds good, good luck with your gigs and thanks for the update!

On Wed, Jul 23, 2014 at 10:44 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
sorry i missed this one!
now i'm touring for a few piano gigs. so no laptop with me.
as soon as i get back home on Jul 27 i'll do all the needed checks.
Many thanks and i'll be back to you very soon.
a,

Il mercoledì 23 luglio 2014, Steven Yi notifications@github.com ha
scritto:

@alfonso73 https://github.com/alfonso73 : any word? I'll need
further
information to continue with this issue.


Reply to this email directly or view it on GitHub
#345 (comment).

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

Hi Alfonso,

I'm not quite sure what is going on as it worked for me. I think the next
step is for me to remove my version of Csound and install the one from
Sourceforge and see if I can reproduce that way. I've got a busy weekend
but will try to find time to fit in researching this.

Thanks!
steven

On Fri, Aug 8, 2014 at 10:17 AM, alfonso73 notifications@github.com wrote:

hi Steven!
some news?
thanks and all the best!
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Jul 23, 2014 at 4:47 PM, Steven Yi notifications@github.com
wrote:

Sounds good, good luck with your gigs and thanks for the update!

On Wed, Jul 23, 2014 at 10:44 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
sorry i missed this one!
now i'm touring for a few piano gigs. so no laptop with me.
as soon as i get back home on Jul 27 i'll do all the needed checks.
Many thanks and i'll be back to you very soon.
a,

Il mercoledì 23 luglio 2014, Steven Yi notifications@github.com ha
scritto:

@alfonso73 https://github.com/alfonso73 : any word? I'll need
further
information to continue with this issue.


Reply to this email directly or view it on GitHub
#345 (comment).

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

hi Steven!
many thanks
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Fri, Aug 8, 2014 at 4:22 PM, Steven Yi notifications@github.com wrote:

Hi Alfonso,

I'm not quite sure what is going on as it worked for me. I think the next
step is for me to remove my version of Csound and install the one from
Sourceforge and see if I can reproduce that way. I've got a busy weekend
but will try to find time to fit in researching this.

Thanks!
steven

On Fri, Aug 8, 2014 at 10:17 AM, alfonso73 notifications@github.com
wrote:

hi Steven!
some news?
thanks and all the best!
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Jul 23, 2014 at 4:47 PM, Steven Yi notifications@github.com
wrote:

Sounds good, good luck with your gigs and thanks for the update!

On Wed, Jul 23, 2014 at 10:44 AM, alfonso73 notifications@github.com

wrote:

Hi Steven,
sorry i missed this one!
now i'm touring for a few piano gigs. so no laptop with me.
as soon as i get back home on Jul 27 i'll do all the needed checks.
Many thanks and i'll be back to you very soon.
a,

Il mercoledì 23 luglio 2014, Steven Yi notifications@github.com
ha
scritto:

@alfonso73 https://github.com/alfonso73 : any word? I'll need
further
information to continue with this issue.


Reply to this email directly or view it on GitHub
#345 (comment).

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an error where csound~ could not be found when using the Max Runtime. However, was using a patch that was not in the same location as the csound~.mxe file. I copied .pat and .csd files into the same folder as the mxe and they were able to run.

My guess is that the .mxe is not on the externals path. With the runtime, I don't know if there's a way to set that, but it should be settable in the main Max program.

Could you take a look and see if the info above gets things going there for you @alfonso73 ?

@alfonso73
Copy link
Author

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref file and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi notifications@github.com wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an error where
csound~ could not be found when using the Max Runtime. However, was using a
patch that was not in the same location as the csound~.mxe file. I copied
.pat and .csd files into the same folder as the mxe and they were able to
run.

My guess is that the .mxe is not on the externals path. With the runtime,
I don't know if there's a way to set that, but it should be settable in the
main Max program.

Could you take a look and see if the info above gets things going there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

@alfonso73 : This is very curious. Can you tell me if you have any other
versions of Csound (i.e. Csound5) or other version of csound~? Also, what
exact version of Max are you using? Maybe something subtle changed between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 notifications@github.com wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi notifications@github.com
wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an error
where
csound~ could not be found when using the Max Runtime. However, was
using a
patch that was not in the same location as the csound~.mxe file. I
copied
.pat and .csd files into the same folder as the mxe and they were able
to
run.

My guess is that the .mxe is not on the externals path. With the
runtime,
I don't know if there's a way to set that, but it should be settable in
the
main Max program.

Could you take a look and see if the info above gets things going there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my Win 7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~ 1.1.2 and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com wrote:

@alfonso73 : This is very curious. Can you tell me if you have any other
versions of Csound (i.e. Csound5) or other version of csound~? Also, what
exact version of Max are you using? Maybe something subtle changed between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi notifications@github.com
wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an error
where
csound~ could not be found when using the Max Runtime. However, was
using a
patch that was not in the same location as the csound~.mxe file. I
copied
.pat and .csd files into the same folder as the mxe and they were able
to
run.

My guess is that the .mxe is not on the externals path. With the
runtime,
I don't know if there's a way to set that, but it should be settable
in
the
main Max program.

Could you take a look and see if the info above gets things going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same folder as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my Win 7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~ 1.1.2 and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : This is very curious. Can you tell me if you have any other
versions of Csound (i.e. Csound5) or other version of csound~? Also, what
exact version of Max are you using? Maybe something subtle changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi notifications@github.com
wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an error
where
csound~ could not be found when using the Max Runtime. However, was
using a
patch that was not in the same location as the csound~.mxe file. I
copied
.pat and .csd files into the same folder as the mxe and they were
able
to
run.

My guess is that the .mxe is not on the externals path. With the
runtime,
I don't know if there's a way to set that, but it should be settable
in
the
main Max program.

Could you take a look and see if the info above gets things going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@gogins
Copy link
Contributor

gogins commented Aug 13, 2014

Can you use the dependency walker (http://www.dependencywalker.com/) to
find out what is wrong?

Regards,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com
wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same folder as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~ 1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : This is very curious. Can you tell me if you have any
other
versions of Csound (i.e. Csound5) or other version of csound~? Also,
what
exact version of Max are you using? Maybe something subtle changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi notifications@github.com

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an
error
where
csound~ could not be found when using the Max Runtime. However, was
using a
patch that was not in the same location as the csound~.mxe file. I
copied
.pat and .csd files into the same folder as the mxe and they were
able
to
run.

My guess is that the .mxe is not on the externals path. With the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

It may be an issue between some library existing on my system but not on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the .mxe
file. It should complain that it couldn't open some libraries which is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than those,
then that would hint that there's a library not existing on your system
that is on mine. I'm particularly curious to see if it is libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags to
statically link those which I can try to do if you can confirm those are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com
wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same folder as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~ 1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : This is very curious. Can you tell me if you have any
other
versions of Csound (i.e. Csound5) or other version of csound~? Also,
what
exact version of Max are you using? Maybe something subtle changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 notifications@github.com
wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi notifications@github.com

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an
error
where
csound~ could not be found when using the Max Runtime. However, was
using a
patch that was not in the same location as the csound~.mxe file. I
copied
.pat and .csd files into the same folder as the mxe and they were
able
to
run.

My guess is that the .mxe is not on the externals path. With the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com wrote:

It may be an issue between some library existing on my system but not on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the .mxe
file. It should complain that it couldn't open some libraries which is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than those,
then that would hint that there's a library not existing on your system
that is on mine. I'm particularly curious to see if it is libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags to
statically link those which I can try to do if you can confirm those are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com
wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~ 1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : This is very curious. Can you tell me if you have any
other
versions of Csound (i.e. Csound5) or other version of csound~? Also,
what
exact version of Max are you using? Maybe something subtle changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 notifications@github.com

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an
error
where
csound~ could not be found when using the Max Runtime. However,
was
using a
patch that was not in the same location as the csound~.mxe file.
I
copied
.pat and .csd files into the same folder as the mxe and they were
able
to
run.

My guess is that the .mxe is not on the externals path. With the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

" Error: Modules with different CPU types were found." is a bit
concerning. I guess one thing to try is to remove Max 64-bit and only have
Max 32-bit installed, then try csound~. I can try compiling csound~ here
with static libc++ and libgcc to see if that will further prevent issues.

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com
wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com
wrote:

It may be an issue between some library existing on my system but not on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the .mxe
file. It should complain that it couldn't open some libraries which is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than those,
then that would hint that there's a library not existing on your system
that is on mine. I'm particularly curious to see if it is libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags to
statically link those which I can try to do if you can confirm those are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com
wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com

wrote:

@alfonso73 : This is very curious. Can you tell me if you have any
other
versions of Csound (i.e. Csound5) or other version of csound~?
Also,
what
exact version of Max are you using? Maybe something subtle changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an
error
where
csound~ could not be found when using the Max Runtime. However,
was
using a
patch that was not in the same location as the csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and they
were
able
to
run.

My guess is that the .mxe is not on the externals path. With
the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@gogins
Copy link
Contributor

gogins commented Aug 13, 2014

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each compiled
for a different CPU architecture (64 bits and 32 bits). Only code compiled
for the same, consistent CPU architecture can normally run together. A 64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where that
refers, not to the CPU architecture, but to the audio sample word size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64 bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really wish we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and plugins
installed, but they must be installed and configured so that all plugins
found by a host are compiled for the host's CPU architecture. Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code that
is compiled for 32 bit CPU architecture as well (they have a whole separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com
wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com
wrote:

It may be an issue between some library existing on my system but not on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the .mxe
file. It should complain that it couldn't open some libraries which is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than those,
then that would hint that there's a library not existing on your system
that is on mine. I'm particularly curious to see if it is libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags to
statically link those which I can try to do if you can confirm those are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com
wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi notifications@github.com

wrote:

@alfonso73 : This is very curious. Can you tell me if you have any
other
versions of Csound (i.e. Csound5) or other version of csound~?
Also,
what
exact version of Max are you using? Maybe something subtle changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get an
error
where
csound~ could not be found when using the Max Runtime. However,
was
using a
patch that was not in the same location as the csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and they
were
able
to
run.

My guess is that the .mxe is not on the externals path. With
the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture external.
But for now i'm trying to load the csound~ ( i guess compiled for 32 bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a csound~ in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com wrote:

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each compiled
for a different CPU architecture (64 bits and 32 bits). Only code compiled
for the same, consistent CPU architecture can normally run together. A 64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where that
refers, not to the CPU architecture, but to the audio sample word size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64 bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really wish we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and plugins
installed, but they must be installed and configured so that all plugins
found by a host are compiled for the host's CPU architecture. Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com
wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com
wrote:

It may be an issue between some library existing on my system but not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the .mxe
file. It should complain that it couldn't open some libraries which is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than those,
then that would hint that there's a library not existing on your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags
to
statically link those which I can try to do if you can confirm those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com

wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you have
any
other
versions of Csound (i.e. Csound5) or other version of csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and they
were
able
to
run.

My guess is that the .mxe is not on the externals path. With
the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

i guess the csound-float / csound-double is better said than 32/64 to avoid
confusion.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:23 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture external.
But for now i'm trying to load the csound~ ( i guess compiled for 32 bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a csound~
in the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com wrote:

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each compiled
for a different CPU architecture (64 bits and 32 bits). Only code
compiled
for the same, consistent CPU architecture can normally run together. A 64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where that
refers, not to the CPU architecture, but to the audio sample word size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64 bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and plugins
installed, but they must be installed and configured so that all plugins
found by a host are compiled for the host's CPU architecture. Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code
that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com
wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com
wrote:

It may be an issue between some library existing on my system but not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the
.mxe
file. It should complain that it couldn't open some libraries which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than
those,
then that would hint that there's a library not existing on your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags
to
statically link those which I can try to do if you can confirm those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com

wrote:

and to be more precise csound works perfectly from CsoundQT and
from
Cabbage.
and Max is able to load all other externals located in the same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you have
any
other
versions of Csound (i.e. Csound5) or other version of csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and they
were
able
to
run.

My guess is that the .mxe is not on the externals path. With
the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

The reason I asked to uninstall Max 64-bit is that it may have libraries
with the same names that are conflicting in cpu architecture. Rather than
uninstall, could you temporarily move the folder to somewhere that is not
in Program Files or other Path (say, directly to c:), then try running Max
32-bit? You can then move it back to the original location and it should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 notifications@github.com
wrote:

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled for 32 bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com wrote:

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each compiled
for a different CPU architecture (64 bits and 32 bits). Only code
compiled
for the same, consistent CPU architecture can normally run together. A
64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where
that
refers, not to the CPU architecture, but to the audio sample word size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64 bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and
plugins
installed, but they must be installed and configured so that all plugins
found by a host are compiled for the host's CPU architecture. Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code
that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com
wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com
wrote:

It may be an issue between some library existing on my system but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the
.mxe
file. It should complain that it couldn't open some libraries which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than
those,
then that would hint that there's a library not existing on your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags
to
statically link those which I can try to do if you can confirm those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from CsoundQT and
from
Cabbage.
and Max is able to load all other externals located in the same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you have
any
other
versions of Csound (i.e. Csound5) or other version of csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and
they
were
able
to
run.

My guess is that the .mxe is not on the externals path.
With
the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

and btw my Max 6.1.8 32 bit is installed here ( its defalut location )

C:\Program Files (x86)\Cycling '74\Max 6.1

my Max 6.1.8 64 bit is installed here ( its default location )

C:\Program Files\Cycling '74\Max 6.1

maybe that csound~ ( 32 bit architecture should find stuff in C:\Program
Files (x86)\Cycling '74\Max 6.1 )

and a future 64 bit architectur csound~ will point to C:\Program
Files\Cycling '74\Max 6.1

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com wrote:

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each compiled
for a different CPU architecture (64 bits and 32 bits). Only code compiled
for the same, consistent CPU architecture can normally run together. A 64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where that
refers, not to the CPU architecture, but to the audio sample word size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64 bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really wish we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and plugins
installed, but they must be installed and configured so that all plugins
found by a host are compiled for the host's CPU architecture. Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com
wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com
wrote:

It may be an issue between some library existing on my system but not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the .mxe
file. It should complain that it couldn't open some libraries which is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than those,
then that would hint that there's a library not existing on your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some flags
to
statically link those which I can try to do if you can confirm those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 notifications@github.com

wrote:

and to be more precise csound works perfectly from CsoundQT and from
Cabbage.
and Max is able to load all other externals located in the same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you have
any
other
versions of Csound (i.e. Csound5) or other version of csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and they
were
able
to
run.

My guess is that the .mxe is not on the externals path. With
the
runtime,
I don't know if there's a way to set that, but it should be
settable
in
the
main Max program.

Could you take a look and see if the info above gets things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi notifications@github.com wrote:

The reason I asked to uninstall Max 64-bit is that it may have libraries
with the same names that are conflicting in cpu architecture. Rather than
uninstall, could you temporarily move the folder to somewhere that is not
in Program Files or other Path (say, directly to c:), then try running Max
32-bit? You can then move it back to the original location and it should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 notifications@github.com
wrote:

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled for 32 bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com
wrote:

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each
compiled
for a different CPU architecture (64 bits and 32 bits). Only code
compiled
for the same, consistent CPU architecture can normally run together. A
64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where
that
refers, not to the CPU architecture, but to the audio sample word size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64 bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and
plugins
installed, but they must be installed and configured so that all
plugins
found by a host are compiled for the host's CPU architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code
that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was
not
found.
Error: At least one module has an unresolved import due to a missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi notifications@github.com

wrote:

It may be an issue between some library existing on my system but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the
.mxe
file. It should complain that it couldn't open some libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than
those,
then that would hint that there's a library not existing on your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some
flags
to
statically link those which I can try to do if you can confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from CsoundQT and
from
Cabbage.
and Max is able to load all other externals located in the same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you
have
any
other
versions of Csound (i.e. Csound5) or other version of
csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did
get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and
they
were
able
to
run.

My guess is that the .mxe is not on the externals path.
With
the
runtime,
I don't know if there's a way to set that, but it should
be
settable
in
the
main Max program.

Could you take a look and see if the info above gets
things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

doesn't work anyway...

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi notifications@github.com
wrote:

The reason I asked to uninstall Max 64-bit is that it may have libraries
with the same names that are conflicting in cpu architecture. Rather than
uninstall, could you temporarily move the folder to somewhere that is not
in Program Files or other Path (say, directly to c:), then try running
Max
32-bit? You can then move it back to the original location and it should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 notifications@github.com
wrote:

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled for 32
bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a
csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com
wrote:

Just for your information, the use of the term "64 bits" can be very
misleading.

It sounds like your problem may be that Max and Csound are each
compiled
for a different CPU architecture (64 bits and 32 bits). Only code
compiled
for the same, consistent CPU architecture can normally run together.
A
64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound where
that
refers, not to the CPU architecture, but to the audio sample word
size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64
bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and
plugins
installed, but they must be installed and configured so that all
plugins
found by a host are compiled for the host's CPU architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run code
that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 notifications@github.com

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was
not
found.
Error: At least one module has an unresolved import due to a
missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi <
notifications@github.com>
wrote:

It may be an issue between some library existing on my system but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open the
.mxe
file. It should complain that it couldn't open some libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than
those,
then that would hint that there's a library not existing on your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some
flags
to
statically link those which I can try to do if you can confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from CsoundQT and
from
Cabbage.
and Max is able to load all other externals located in the same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both
installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you
have
any
other
versions of Csound (i.e. Csound5) or other version of
csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I did
get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe and
they
were
able
to
run.

My guess is that the .mxe is not on the externals path.
With
the
runtime,
I don't know if there's a way to set that, but it should
be
settable
in
the
main Max program.

Could you take a look and see if the info above gets
things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52057255>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

@alfonso73 : could you try this build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static libstdc++ and libgcc. Let's see if that
helps the situation.

On Wed, Aug 13, 2014 at 11:31 AM, alfonso73 notifications@github.com
wrote:

doesn't work anyway...

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi notifications@github.com
wrote:

The reason I asked to uninstall Max 64-bit is that it may have
libraries
with the same names that are conflicting in cpu architecture. Rather
than
uninstall, could you temporarily move the folder to somewhere that is
not
in Program Files or other Path (say, directly to c:), then try running
Max
32-bit? You can then move it back to the original location and it
should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 notifications@github.com
wrote:

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled for 32
bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a
csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com
wrote:

Just for your information, the use of the term "64 bits" can be
very
misleading.

It sounds like your problem may be that Max and Csound are each
compiled
for a different CPU architecture (64 bits and 32 bits). Only code
compiled
for the same, consistent CPU architecture can normally run
together.
A
64
bit host cannot load a 32 bit plugin, for example, and vice versa.

This is not to be confused with 64 bit Csound or 32 bit Csound
where
that
refers, not to the CPU architecture, but to the audio sample word
size
(float or 32 bits, double or 64 bits). You can get "32 bit" csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64
bit"
Csound compiled for both 32 bit and 64 CPU architectures. I really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and
plugins
installed, but they must be installed and configured so that all
plugins
found by a host are compiled for the host's CPU architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems are
themselves written for 64 bit CPU architecture, but they can run
code
that
is compiled for 32 bit CPU architecture as well (they have a whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 <
notifications@github.com>

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency was
not
found.
Error: At least one module has an unresolved import due to a
missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi <
notifications@github.com>
wrote:

It may be an issue between some library existing on my system
but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open
the
.mxe
file. It should complain that it couldn't open some libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else than
those,
then that would hint that there's a library not existing on
your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use some
flags
to
statically link those which I can try to do if you can confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from CsoundQT
and
from
Cabbage.
and Max is able to load all other externals located in the
same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both
installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if you
have
any
other
versions of Csound (i.e. Csound5) or other version of
csound~?
Also,
what
exact version of Max are you using? Maybe something subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted
the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I
did
get
an
error
where
csound~ could not be found when using the Max Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe
and
they
were
able
to
run.

My guess is that the .mxe is not on the externals
path.
With
the
runtime,
I don't know if there's a way to set that, but it
should
be
settable
in
the
main Max program.

Could you take a look and see if the info above gets
things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52057255>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52060610>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

same problem.

run another dependecy check with the 32 bit version of dependency checker

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive from a recent Cabbage version compiled for
64 bit architecture ( so i guess rory is using a 64 bit arch compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52 PM, Steven Yi notifications@github.com wrote:

@alfonso73 : could you try this build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static libstdc++ and libgcc. Let's see if that
helps the situation.

On Wed, Aug 13, 2014 at 11:31 AM, alfonso73 notifications@github.com
wrote:

doesn't work anyway...

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi notifications@github.com
wrote:

The reason I asked to uninstall Max 64-bit is that it may have
libraries
with the same names that are conflicting in cpu architecture. Rather
than
uninstall, could you temporarily move the folder to somewhere that is
not
in Program Files or other Path (say, directly to c:), then try
running
Max
32-bit? You can then move it back to the original location and it
should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 notifications@github.com

wrote:

I can't unistall Max for 64 bit architecture ( i use it for several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled for
32
bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a
csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com
wrote:

Just for your information, the use of the term "64 bits" can be
very
misleading.

It sounds like your problem may be that Max and Csound are each
compiled
for a different CPU architecture (64 bits and 32 bits). Only code
compiled
for the same, consistent CPU architecture can normally run
together.
A
64
bit host cannot load a 32 bit plugin, for example, and vice
versa.

This is not to be confused with 64 bit Csound or 32 bit Csound
where
that
refers, not to the CPU architecture, but to the audio sample word
size
(float or 32 bits, double or 64 bits). You can get "32 bit"
csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get "64
bit"
Csound compiled for both 32 bit and 64 CPU architectures. I
really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs and
plugins
installed, but they must be installed and configured so that all
plugins
found by a host are compiled for the host's CPU architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems
are
themselves written for 64 bit CPU architecture, but they can run
code
that
is compiled for 32 bit CPU architecture as well (they have a
whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 <
notifications@github.com>

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency
was
not
found.
Error: At least one module has an unresolved import due to a
missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not
found.
Warning: At least one module has an unresolved import due to a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi <
notifications@github.com>
wrote:

It may be an issue between some library existing on my system
but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then open
the
.mxe
file. It should complain that it couldn't open some libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else
than
those,
then that would hint that there's a library not existing on
your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use
some
flags
to
statically link those which I can try to do if you can
confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from CsoundQT
and
from
Cabbage.
and Max is able to load all other externals located in the
same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both
installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if
you
have
any
other
versions of Csound (i.e. Csound5) or other version of
csound~?
Also,
what
exact version of Max are you using? Maybe something
subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max
launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then deleted
the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are
correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2. I
did
get
an
error
where
csound~ could not be found when using the Max
Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the mxe
and
they
were
able
to
run.

My guess is that the .mxe is not on the externals
path.
With
the
runtime,
I don't know if there's a way to set that, but it
should
be
settable
in
the
main Max program.

Could you take a look and see if the info above gets
things
going
there
for you @alfonso73 https://github.com/alfonso73 ?


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52057255>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52060610>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52062613>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

Well having Rory's 64-bit csound version installed would most certainly
cause all these problems. It's likely the system's loader is trying to
load those before loading the 32-bit csound installed.

Two things you could try:

  1. Remove Rory's Csound
  2. Less intrusive, try copying all of the dll's into the same folder as
    csound~. They may then get picked up before Rory's (libcsound64.dll,
    libpthreadgc2.dll, etc.)

On Wed, Aug 13, 2014 at 11:58 AM, alfonso73 notifications@github.com
wrote:

same problem.

run another dependecy check with the 32 bit version of dependency checker

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive from a recent Cabbage version compiled for
64 bit architecture ( so i guess rory is using a 64 bit arch compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : could you try this build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static libstdc++ and libgcc. Let's see if that
helps the situation.

On Wed, Aug 13, 2014 at 11:31 AM, alfonso73 notifications@github.com
wrote:

doesn't work anyway...

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi notifications@github.com

wrote:

The reason I asked to uninstall Max 64-bit is that it may have
libraries
with the same names that are conflicting in cpu architecture.
Rather
than
uninstall, could you temporarily move the folder to somewhere that
is
not
in Program Files or other Path (say, directly to c:), then try
running
Max
32-bit? You can then move it back to the original location and it
should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 <
notifications@github.com>

wrote:

I can't unistall Max for 64 bit architecture ( i use it for
several
projects )
I will be happy to have csound~ compiled as a 64 bit architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled for
32
bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load a
csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins notifications@github.com

wrote:

Just for your information, the use of the term "64 bits" can be
very
misleading.

It sounds like your problem may be that Max and Csound are each
compiled
for a different CPU architecture (64 bits and 32 bits). Only
code
compiled
for the same, consistent CPU architecture can normally run
together.
A
64
bit host cannot load a 32 bit plugin, for example, and vice
versa.

This is not to be confused with 64 bit Csound or 32 bit Csound
where
that
refers, not to the CPU architecture, but to the audio sample
word
size
(float or 32 bits, double or 64 bits). You can get "32 bit"
csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get
"64
bit"
Csound compiled for both 32 bit and 64 CPU architectures. I
really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs
and
plugins
installed, but they must be installed and configured so that
all
plugins
found by a host are compiled for the host's CPU architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating systems
are
themselves written for 64 bit CPU architecture, but they can
run
code
that
is compiled for 32 bit CPU architecture as well (they have a
whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 <
notifications@github.com>

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded dependency
was
not
found.
Error: At least one module has an unresolved import due to a
missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not
found.
Warning: At least one module has an unresolved import due to
a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi <
notifications@github.com>
wrote:

It may be an issue between some library existing on my
system
but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then
open
the
.mxe
file. It should complain that it couldn't open some
libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something else
than
those,
then that would hint that there's a library not existing on
your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use
some
flags
to
statically link those which I can try to do if you can
confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from
CsoundQT
and
from
Cabbage.
and Max is able to load all other externals located in
the
same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both
installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3 and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me if
you
have
any
other
versions of Csound (i.e. Csound5) or other version of
csound~?
Also,
what
exact version of Max are you using? Maybe something
subtle
changed
between
versions and we're not testing with the same version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max
launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then
deleted
the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are
correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~ v.1.1.2.
I
did
get
an
error
where
csound~ could not be found when using the Max
Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the
mxe
and
they
were
able
to
run.

My guess is that the .mxe is not on the externals
path.
With
the
runtime,
I don't know if there's a way to set that, but it
should
be
settable
in
the
main Max program.

Could you take a look and see if the info above
gets
things
going
there
for you @alfonso73 https://github.com/alfonso73
?


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52057255>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52060610>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52062613>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52063655>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@alfonso73
Copy link
Author

uninstalled Cabbage64, copied csound64.dll, libsndfile-1.dll,
libwinpthread-1.dll, pthreadGC2.dll from Cabbage32 to the folder where
csound~.mxe is and....
no go..still 193 error while trying to create a csound~ object.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:06 PM, Steven Yi notifications@github.com wrote:

Well having Rory's 64-bit csound version installed would most certainly
cause all these problems. It's likely the system's loader is trying to
load those before loading the 32-bit csound installed.

Two things you could try:

  1. Remove Rory's Csound
  2. Less intrusive, try copying all of the dll's into the same folder as
    csound~. They may then get picked up before Rory's (libcsound64.dll,
    libpthreadgc2.dll, etc.)

On Wed, Aug 13, 2014 at 11:58 AM, alfonso73 notifications@github.com
wrote:

same problem.

run another dependecy check with the 32 bit version of dependency
checker

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive from a recent Cabbage version compiled
for
64 bit architecture ( so i guess rory is using a 64 bit arch compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : could you try this build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static libstdc++ and libgcc. Let's see if
that
helps the situation.

On Wed, Aug 13, 2014 at 11:31 AM, alfonso73 notifications@github.com

wrote:

doesn't work anyway...

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi <
notifications@github.com>

wrote:

The reason I asked to uninstall Max 64-bit is that it may have
libraries
with the same names that are conflicting in cpu architecture.
Rather
than
uninstall, could you temporarily move the folder to somewhere
that
is
not
in Program Files or other Path (say, directly to c:), then try
running
Max
32-bit? You can then move it back to the original location and it
should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 <
notifications@github.com>

wrote:

I can't unistall Max for 64 bit architecture ( i use it for
several
projects )
I will be happy to have csound~ compiled as a 64 bit
architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled
for
32
bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to load
a
csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins <
notifications@github.com>

wrote:

Just for your information, the use of the term "64 bits" can
be
very
misleading.

It sounds like your problem may be that Max and Csound are
each
compiled
for a different CPU architecture (64 bits and 32 bits). Only
code
compiled
for the same, consistent CPU architecture can normally run
together.
A
64
bit host cannot load a 32 bit plugin, for example, and vice
versa.

This is not to be confused with 64 bit Csound or 32 bit
Csound
where
that
refers, not to the CPU architecture, but to the audio sample
word
size
(float or 32 bits, double or 64 bits). You can get "32 bit"
csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can get
"64
bit"
Csound compiled for both 32 bit and 64 CPU architectures. I
really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture programs
and
plugins
installed, but they must be installed and configured so that
all
plugins
found by a host are compiled for the host's CPU architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating
systems
are
themselves written for 64 bit CPU architecture, but they can
run
code
that
is compiled for 32 bit CPU architecture as well (they have a
whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 <
notifications@github.com>

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded
dependency
was
not
found.
Error: At least one module has an unresolved import due to
a
missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not
found.
Warning: At least one module has an unresolved import due
to
a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi <
notifications@github.com>
wrote:

It may be an issue between some library existing on my
system
but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program, then
open
the
.mxe
file. It should complain that it couldn't open some
libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something
else
than
those,
then that would hint that there's a library not existing
on
your
system
that is on mine. I'm particularly curious to see if it is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe use
some
flags
to
statically link those which I can try to do if you can
confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from
CsoundQT
and
from
Cabbage.
and Max is able to load all other externals located in
the
same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit both
installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3
and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me
if
you
have
any
other
versions of Csound (i.e. Csound5) or other version
of
csound~?
Also,
what
exact version of Max are you using? Maybe something
subtle
changed
between
versions and we're not testing with the same
version.

Also, I saw that Max 6.1.3 had a release note here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max
launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then
deleted
the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are
correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~
v.1.1.2.
I
did
get
an
error
where
csound~ could not be found when using the Max
Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as the
mxe
and
they
were
able
to
run.

My guess is that the .mxe is not on the
externals
path.
With
the
runtime,
I don't know if there's a way to set that, but
it
should
be
settable
in
the
main Max program.

Could you take a look and see if the info above
gets
things
going
there
for you @alfonso73 https://github.com/alfonso73

?


Reply to this email directly or view it on
GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52057255>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52060610>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52062613>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52063655>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52064522>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

Oh, I was thinking to copy the dll's from Csound's install folder in
Program Files(x86). I hesitate to diagnose using Rory's csound version as
I have no idea how it was compiled.

On Wed, Aug 13, 2014 at 12:21 PM, alfonso73 notifications@github.com
wrote:

uninstalled Cabbage64, copied csound64.dll, libsndfile-1.dll,
libwinpthread-1.dll, pthreadGC2.dll from Cabbage32 to the folder where
csound~.mxe is and....
no go..still 193 error while trying to create a csound~ object.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:06 PM, Steven Yi notifications@github.com
wrote:

Well having Rory's 64-bit csound version installed would most certainly
cause all these problems. It's likely the system's loader is trying to
load those before loading the 32-bit csound installed.

Two things you could try:

  1. Remove Rory's Csound
  2. Less intrusive, try copying all of the dll's into the same folder as
    csound~. They may then get picked up before Rory's (libcsound64.dll,
    libpthreadgc2.dll, etc.)

On Wed, Aug 13, 2014 at 11:58 AM, alfonso73 notifications@github.com
wrote:

same problem.

run another dependecy check with the 32 bit version of dependency
checker

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive from a recent Cabbage version compiled
for
64 bit architecture ( so i guess rory is using a 64 bit arch compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52 PM, Steven Yi notifications@github.com
wrote:

@alfonso73 : could you try this build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static libstdc++ and libgcc. Let's see if
that
helps the situation.

On Wed, Aug 13, 2014 at 11:31 AM, alfonso73 <
notifications@github.com>

wrote:

doesn't work anyway...

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

i'll try now

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28 PM, Steven Yi <
notifications@github.com>

wrote:

The reason I asked to uninstall Max 64-bit is that it may have
libraries
with the same names that are conflicting in cpu architecture.
Rather
than
uninstall, could you temporarily move the folder to somewhere
that
is
not
in Program Files or other Path (say, directly to c:), then try
running
Max
32-bit? You can then move it back to the original location and
it
should
be fine.

On Wed, Aug 13, 2014 at 11:23 AM, alfonso73 <
notifications@github.com>

wrote:

I can't unistall Max for 64 bit architecture ( i use it for
several
projects )
I will be happy to have csound~ compiled as a 64 bit
architecture
external.
But for now i'm trying to load the csound~ ( i guess compiled
for
32
bit
architecture ) with Max for 32 bit architecture.
And even so i have the 193 external problem when i try to
load
a
csound~
in
the patcher of Max 6.1.8 32bit architecture.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:16 PM, gogins <
notifications@github.com>

wrote:

Just for your information, the use of the term "64 bits"
can
be
very
misleading.

It sounds like your problem may be that Max and Csound are
each
compiled
for a different CPU architecture (64 bits and 32 bits).
Only
code
compiled
for the same, consistent CPU architecture can normally run
together.
A
64
bit host cannot load a 32 bit plugin, for example, and vice
versa.

This is not to be confused with 64 bit Csound or 32 bit
Csound
where
that
refers, not to the CPU architecture, but to the audio
sample
word
size
(float or 32 bits, double or 64 bits). You can get "32 bit"
csound
compiled
for both 32 bit and 64 bit CPU architectures. And you can
get
"64
bit"
Csound compiled for both 32 bit and 64 CPU architectures. I
really
wish
we
would change this very misleading terminology.

You can have both 64 bit and 32 bit CPU architecture
programs
and
plugins
installed, but they must be installed and configured so
that
all
plugins
found by a host are compiled for the host's CPU
architecture.
Otherwise
there will be a load failure or a crash.

Another thing to keep in mind is that modern operating
systems
are
themselves written for 64 bit CPU architecture, but they
can
run
code
that
is compiled for 32 bit CPU architecture as well (they have
a
whole
separate
set of operating system and runtime libraries for this).

Hope this helps,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 11:02 AM, alfonso73 <
notifications@github.com>

wrote:

these are not found

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

these are marked in red as x64

CSOUND64.DLL
LIBGCC_S_SEH-1.DLL
LIBSNDFILE-1.DLL
LIBSTDC++-6.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

this is the message in the bottom part of the window

Error: At least one required implicit or forwarded
dependency
was
not
found.
Error: At least one module has an unresolved import due
to
a
missing
export
function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was
not
found.
Warning: At least one module has an unresolved import due
to
a
missing
export function in a delay-load dependent module.

what to do?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:40 PM, Steven Yi <
notifications@github.com>
wrote:

It may be an issue between some library existing on my
system
but
not
on
yours. Could you try downloading dependency walker from
http://www.dependencywalker.com. Open the program,
then
open
the
.mxe
file. It should complain that it couldn't open some
libraries
which
is
alright. For me, I get:

MAXAUDIO.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL

as ones it can not load. If it complains of something
else
than
those,
then that would hint that there's a library not
existing
on
your
system
that is on mine. I'm particularly curious to see if it
is
libstdc++6.dll
or libgcc_s_dw2-1.dll. I just read that I could maybe
use
some
flags
to
statically link those which I can try to do if you can
confirm
those
are
showing up as missing for you.

On Wed, Aug 13, 2014 at 10:26 AM, alfonso73 <
notifications@github.com>

wrote:

and to be more precise csound works perfectly from
CsoundQT
and
from
Cabbage.
and Max is able to load all other externals located
in
the
same
folder
as
csound~
i don't really understand what's wrong

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 4:11 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

Hi Steven
i'm now on Max 6.1.8 ( 'i have 64bit and 32 bit
both
installed
on
my
Win
7
partition )
i've just downloaded from sourceforge Csound 6.02.3
and
csound~
1.1.2
and
reinstalled, deleted again the max pref file.
Still 193 error :-( when loading csound~

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 3:59 PM, Steven Yi <
notifications@github.com>

wrote:

@alfonso73 : This is very curious. Can you tell me
if
you
have
any
other
versions of Csound (i.e. Csound5) or other version
of
csound~?
Also,
what
exact version of Max are you using? Maybe
something
subtle
changed
between
versions and we're not testing with the same
version.

Also, I saw that Max 6.1.3 had a release note
here:

http://cycling74.com/forums/topic/max-6-1-3-released/

regarding:

• windows: fixed error 193 loading external on max
launch

On Wed, Aug 13, 2014 at 5:07 AM, alfonso73 <
notifications@github.com>

wrote:

Hi Steven,
i've tried uninstall csound and csound~, then
deleted
the
max
pref
file
and
reinstalled everything.
always error 193 :-(
csound~ is installed in the
C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

the other externals in that "Packages" dir are
correctly
seen
by
Max.

mhhh...i don't know how to do.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 2:10 AM, Steven Yi <
notifications@github.com>

wrote:

Hi Alfonso,

I just installed both 6.03.2 and csound~
v.1.1.2.
I
did
get
an
error
where
csound~ could not be found when using the Max
Runtime.
However,
was
using a
patch that was not in the same location as the
csound~.mxe
file.
I
copied
.pat and .csd files into the same folder as
the
mxe
and
they
were
able
to
run.

My guess is that the .mxe is not on the
externals
path.
With
the
runtime,
I don't know if there's a way to set that, but
it
should
be
settable
in
the
main Max program.

Could you take a look and see if the info
above
gets
things
going
there
for you @alfonso73 <
https://github.com/alfonso73>

?


Reply to this email directly or view it on
GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-51994893>.


Reply to this email directly or view it on
GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52025345>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52051359>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52055294>.


Reply to this email directly or view it on GitHub
<

https://github.com/csound/csound/issues/345#issuecomment-52057255>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52060610>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52062613>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52063655>.


Reply to this email directly or view it on GitHub
<
https://github.com/csound/csound/issues/345#issuecomment-52064522>.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@gogins
Copy link
Contributor

gogins commented Aug 14, 2014

Nope, windows 8 here.

Regards,
Mike
On Aug 14, 2014 11:49 AM, "Steven Yi" notifications@github.com wrote:

I looked up error 193 and didn't find much on Cycling '74's forums. I
checked and the standard windows error for 193 says something about
not being a valid win32 application. I have no idea though if the
error code being presented by Max is the windows error code though.

One thing we haven't really checked is if the issue has to do with my
building/testing on Windows Server 2012 rc2, which is similar to
Window 8.

@gogins: Do you have a Windows 7 setup? If so, could you perhaps try
downloading the Max Runtime and latest csound~ I compiled
(http://www.kunstmusik.com/csound~_1.1.2.exe) to see about
reproducing?

On Thu, Aug 14, 2014 at 11:10 AM, alfonso73 notifications@github.com
wrote:

yeah. i did the same check. funny things is that dependency check give
the
same error about pthreadGC2.dll being 64 bit. but the old csound~ works
fine.
i try to reinstall csound 6 and csound~ 1.1.2.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:54 PM, Steven Yi notifications@github.com
wrote:

I checked and the dependencies for the older csound~ and the last one
I built are the same, except for the difference of depending on the
libcsound64 version for CS5 vs CS6. Hopefully the pthreadGC2.dll does
the trick.

On Thu, Aug 14, 2014 at 10:50 AM, Steven Yi stevenyi@gmail.com
wrote:

Well I'm pretty certain the issue has to do with dependent library
conflicts. csound~ 1.1.2 certainly is compiled for doubles and as I
said, it works perfectly fine here. The situation on your computer
points to there being a conflict in versions of libraries, which is
very difficult to sort out.

If you could try the pthreadGC2.dll, I'll run the older csound~ in
dependency walker to see if what I can find.

On Thu, Aug 14, 2014 at 10:47 AM, alfonso73 notifications@github.com

wrote:

Csound5 and csound~ 1.1.0 and Max 6.1.8 works perfectly.
Loaded some examples and they run perfectly.
so there's is definetly something wrong in csound~ 1.1.2 ( just out
of
curiosity is it compiled for csound double? )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:12 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

still error 193.

i can try unistall csound 6 and the new csound~ and then install
the
old
csound5 and old csound~ to see if it works?
what do you think about it?
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:06 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

did it.
i can just delete the Max pref files to check if something
change...
really hard thing ti spot!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:03 PM, Steven Yi <
notifications@github.com>

wrote:

Unless I'm misunderstanding, did you move the .mxe in there? And
did
you move the other folder out of the way to ensure we have a
clean
test?

On Thu, Aug 14, 2014 at 10:02 AM, Steven Yi stevenyi@gmail.com
wrote:

That wouldn't do anything as that only affects Max's locations
for
where to load. Having the .mxe in the same folder affects the
OS's
library loading order, which is why I suggested the previous
steps.

On Thu, Aug 14, 2014 at 10:01 AM, alfonso73 <
notifications@github.com>
wrote:

for point 2 i just added the Csound6 folder into the File
Preferences
window of Max.
everything done.
but...guess what...
error 193

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 3:49 PM, Steven Yi <
notifications@github.com>
wrote:

How about trying this:

  1. Move the csound~.mxe into the folder where Csound is
    installed
    (i.e. c:\Program Files(x86)\csound6\bin)
  2. Move the folder where csound~ was installed to your
    desktop,
    or
    other location where Max won't normally see it
  3. Run Max and set the externals path to load from the Csound
    bin
    folder
  4. Copy some .maxpat and .csd examples to the csound bin
    folder
    and
    try running it

On Wed, Aug 13, 2014 at 7:38 PM, alfonso73
notifications@github.com

wrote:

yeah.
193 error.

Il giovedì 14 agosto 2014, Steven Yi
notifications@github.com

ha

scritto:

Did you copy the patch files to the same location as the
.mxe
before
loading the patch?

On Wed, Aug 13, 2014 at 6:53 PM, alfonso73 <
notifications@github.com>
wrote:

btw the other dir are like yours.

i've just tried to run pluckedsynth.pat
from the Max runtime
and i have the
"Error 193 loading external csound~" message from Max
window

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:49 AM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

mhhh...i'm not logged as administrator....
your folder is C:\Users\Administrator
Documents\Max\Packages\csound~_v1.1.2-beta

mine is

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

so there's no -beta at the end

anyway as it is now Max does not see the external
so when i instantiate a csound~ object
i have this error in Max window

newobj csound~: No such object

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:35 AM, Steven Yi <
notifications@github.com>

wrote:

I have csound~ installed in:

C:\Users\Administrator\Documents\Max\Packages\csound~_v1.1.2-beta

and Csound 6.03.2 installed in:

c:\Program Files (x86)\Csound6

Max is installed in:

C:\Program Files (x86)\Cycling '74

I copy the examples from the csound~ examples into
one
folder
higher
where
the .mxe is. After that, I open Max Runtime and open
pluckedsynth.pat
and
it loads and runs alright.

The version of pthreadGC2.dll I have here is also
2.9.1.0.
(I
should
maybe
package libpthreadGC2.dll with csound~.mxe, as it
looks
like
Michael
is
using a different pthread lib in his compiles.)

As it is now, are you getting the same error message
or
no
error
message
at
all now (but also no csound~)?

On Wed, Aug 13, 2014 at 1:43 PM, alfonso73 <
notifications@github.com>

wrote:

and infact if i put the newer pthreadGC2 where
csound~
is
dependency
checker gives only

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

missing but no 64 architecture conflicts.

btw Max does not see csound~ from there.
this is very strange because on your system this is
not a
problem
and
on
my
system the other externals in that dir are
correctly
loaded by
Max.
very tricky situation!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:35 PM, alfonso santimone
<
alfonso.santimone@gmail.com> wrote:

and btw there's no pthreadGC2.dll freshly
installed
by
csound.

i have another pthreadGC2.dll ( GNU C
x86(mingw32)
2.9.1.0 )
in
the
SuperCollider folder wich is more recent and
marked
as
32 bit.

i run i dependency check for the freshly
installed
csound~ and
is
the
only
architecture conflict.
i guess because strangely enough both the version
of
pthreadGC2.dll
in
the
system32 and in the 64 bit system folders are(
POSIX
Thread 32
ver
2.8.0
)....but if its 32 bit why dep check see it as a
64
one?

...mhhh

should i copy the dll from SuperCollider?

but first we have to understand why i can't see
the
csound~.mxe
from
its
default dir.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:24 PM, alfonso
santimone <
alfonso.santimone@gmail.com> wrote:

Steve i followed your path but as it is now i
have
a
csound~: No such object

all other externals from the default dir where
csound~
installs
just
work
and max load those correctly.
Can you give me your paths?
where are csound~, csound and Max 6.1.8 32 bit?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:01 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

Hi Mike,
the other externals in the C:\Users\Live
Machine\Documents\Max
Packages\ dir are correctly loaded by max.
the only one that is not "seen" is csound~. i
don't
know
why.

Steven i go try your procedure....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:48 PM, gogins <
notifications@github.com>

wrote:

You need to look at your environment
variables,
not
just
for
Csound
but
perhaps also for Max. Also maybe the Windows
registry
for
Max.
These
are
things that might control where plugins and
libraries
are
loaded
from.

Regards,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 12:37 PM, alfonso73 <
notifications@github.com>

wrote:

i've moved the whole csound folder in the
main
Max
folder
have
copied
all
the .dll from csound dir to that dir
and the 193 error is back here again.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:33 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

ok. now the dependency checker does not
reveal
any
architecture
conflict.
actually turned out that i use to have
another
csound~.mxe
copy
in
the
Max
32 bit folder.
i removed.
so now i only have the one at

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

good news are that i have no more 193
error!!!

bad news are that now Max windows claims
for
"csound~:
No
such
object"

????

all other externals from that folder are
recognized....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:29 PM, Steven Yi
<
notifications@github.com>
wrote:

Actually, just in case, just copy all
.dll's
from
Csound's
install\bin
folder to the location of csound~.mxe.

On Wed, Aug 13, 2014 at 12:29 PM, Steven
Yi
<
stevenyi@gmail.com>

wrote:

Oh, I was thinking to copy the dll's
from
Csound's
install
folder in
Program Files(x86). I hesitate to
diagnose
using
Rory's
csound
version
as
I have no idea how it was compiled.

On Wed, Aug 13, 2014 at 12:21 PM,
alfonso73 <
notifications@github.com>

wrote:

uninstalled Cabbage64, copied
csound64.dll,
libsndfile-1.dll,
libwinpthread-1.dll, pthreadGC2.dll
from
Cabbage32
to
the
folder
where
csound~.mxe is and....
no go..still 193 error while trying to
create
a
csound~
object.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:06 PM,
Steven
Yi <
notifications@github.com>

wrote:

Well having Rory's 64-bit csound
version
installed
would
most
certainly
cause all these problems. It's
likely
the
system's
loader
is
trying
to
load those before loading the 32-bit
csound
installed.

Two things you could try:

  1. Remove Rory's Csound
  2. Less intrusive, try copying all
    of
    the
    dll's
    into
    the
    same
    folder
    as
    csound~. They may then get picked up
    before
    Rory's
    (libcsound64.dll,
    libpthreadgc2.dll, etc.)

On Wed, Aug 13, 2014 at 11:58 AM,
alfonso73
<
notifications@github.com>
wrote:

same problem.

run another dependecy check with
the
32
bit
version
of
dependency
checker

MAXAPI.DLL
MAXAUDIO.DLL

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL

API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive
from a
recent
Cabbage
version
compiled
for
64 bit architecture ( so i guess
rory
is
using
a
64
bit
arch
compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52 PM,
Steven
Yi <
notifications@github.com>

wrote:

@alfonso73 : could you try this
build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static
libstdc++
and
libgcc.
Let's
see
if
that
helps the situation.

On Wed, Aug 13, 2014 at 11:31
AM,
alfonso73 <
notifications@github.com>

wrote:

doesn't work anyway...

www.elgallorojorecords.com

soundcloud.com/alfonsosantimone

www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29
PM,
alfonso
santimone
<
alfonso.santimone@gmail.com>
wrote:

i'll try now

www.elgallorojorecords.com

soundcloud.com/alfonsosantimone

www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:28
PM,
Steven
Yi <
notifications@github.com>

wrote:


@kunstmusik
Copy link
Member

I'll write an email to the Csound list to request assistance then.

On Thu, Aug 14, 2014 at 11:57 AM, gogins notifications@github.com wrote:

Nope, windows 8 here.

Regards,
Mike
On Aug 14, 2014 11:49 AM, "Steven Yi" notifications@github.com wrote:

I looked up error 193 and didn't find much on Cycling '74's forums. I
checked and the standard windows error for 193 says something about
not being a valid win32 application. I have no idea though if the
error code being presented by Max is the windows error code though.

One thing we haven't really checked is if the issue has to do with my
building/testing on Windows Server 2012 rc2, which is similar to
Window 8.

@gogins: Do you have a Windows 7 setup? If so, could you perhaps try
downloading the Max Runtime and latest csound~ I compiled
(http://www.kunstmusik.com/csound~_1.1.2.exe) to see about
reproducing?

On Thu, Aug 14, 2014 at 11:10 AM, alfonso73 notifications@github.com
wrote:

yeah. i did the same check. funny things is that dependency check give
the
same error about pthreadGC2.dll being 64 bit. but the old csound~ works
fine.
i try to reinstall csound 6 and csound~ 1.1.2.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:54 PM, Steven Yi notifications@github.com
wrote:

I checked and the dependencies for the older csound~ and the last one
I built are the same, except for the difference of depending on the
libcsound64 version for CS5 vs CS6. Hopefully the pthreadGC2.dll does
the trick.

On Thu, Aug 14, 2014 at 10:50 AM, Steven Yi stevenyi@gmail.com
wrote:

Well I'm pretty certain the issue has to do with dependent library
conflicts. csound~ 1.1.2 certainly is compiled for doubles and as I
said, it works perfectly fine here. The situation on your computer
points to there being a conflict in versions of libraries, which is
very difficult to sort out.

If you could try the pthreadGC2.dll, I'll run the older csound~ in
dependency walker to see if what I can find.

On Thu, Aug 14, 2014 at 10:47 AM, alfonso73
notifications@github.com

wrote:

Csound5 and csound~ 1.1.0 and Max 6.1.8 works perfectly.
Loaded some examples and they run perfectly.
so there's is definetly something wrong in csound~ 1.1.2 ( just out
of
curiosity is it compiled for csound double? )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:12 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

still error 193.

i can try unistall csound 6 and the new csound~ and then install
the
old
csound5 and old csound~ to see if it works?
what do you think about it?
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:06 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

did it.
i can just delete the Max pref files to check if something
change...
really hard thing ti spot!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:03 PM, Steven Yi <
notifications@github.com>

wrote:

Unless I'm misunderstanding, did you move the .mxe in there? And
did
you move the other folder out of the way to ensure we have a
clean
test?

On Thu, Aug 14, 2014 at 10:02 AM, Steven Yi stevenyi@gmail.com
wrote:

That wouldn't do anything as that only affects Max's locations
for
where to load. Having the .mxe in the same folder affects the
OS's
library loading order, which is why I suggested the previous
steps.

On Thu, Aug 14, 2014 at 10:01 AM, alfonso73 <
notifications@github.com>
wrote:

for point 2 i just added the Csound6 folder into the File
Preferences
window of Max.
everything done.
but...guess what...
error 193

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 3:49 PM, Steven Yi <
notifications@github.com>
wrote:

How about trying this:

  1. Move the csound~.mxe into the folder where Csound is
    installed
    (i.e. c:\Program Files(x86)\csound6\bin)
  2. Move the folder where csound~ was installed to your
    desktop,
    or
    other location where Max won't normally see it
  3. Run Max and set the externals path to load from the Csound
    bin
    folder
  4. Copy some .maxpat and .csd examples to the csound bin
    folder
    and
    try running it

On Wed, Aug 13, 2014 at 7:38 PM, alfonso73
notifications@github.com

wrote:

yeah.
193 error.

Il giovedì 14 agosto 2014, Steven Yi
notifications@github.com

ha

scritto:

Did you copy the patch files to the same location as the
.mxe
before
loading the patch?

On Wed, Aug 13, 2014 at 6:53 PM, alfonso73 <
notifications@github.com>
wrote:

btw the other dir are like yours.

i've just tried to run pluckedsynth.pat
from the Max runtime
and i have the
"Error 193 loading external csound~" message from Max
window

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:49 AM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

mhhh...i'm not logged as administrator....
your folder is C:\Users\Administrator
Documents\Max\Packages\csound~_v1.1.2-beta

mine is

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

so there's no -beta at the end

anyway as it is now Max does not see the external
so when i instantiate a csound~ object
i have this error in Max window

newobj csound~: No such object

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:35 AM, Steven Yi <
notifications@github.com>

wrote:

I have csound~ installed in:

C:\Users\Administrator\Documents\Max\Packages\csound~_v1.1.2-beta

and Csound 6.03.2 installed in:

c:\Program Files (x86)\Csound6

Max is installed in:

C:\Program Files (x86)\Cycling '74

I copy the examples from the csound~ examples into
one
folder
higher
where
the .mxe is. After that, I open Max Runtime and open
pluckedsynth.pat
and
it loads and runs alright.

The version of pthreadGC2.dll I have here is also
2.9.1.0.
(I
should
maybe
package libpthreadGC2.dll with csound~.mxe, as it
looks
like
Michael
is
using a different pthread lib in his compiles.)

As it is now, are you getting the same error message
or
no
error
message
at
all now (but also no csound~)?

On Wed, Aug 13, 2014 at 1:43 PM, alfonso73 <
notifications@github.com>

wrote:

and infact if i put the newer pthreadGC2 where
csound~
is
dependency
checker gives only

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

missing but no 64 architecture conflicts.

btw Max does not see csound~ from there.
this is very strange because on your system this is
not a
problem
and
on
my
system the other externals in that dir are
correctly
loaded by
Max.
very tricky situation!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:35 PM, alfonso santimone
<
alfonso.santimone@gmail.com> wrote:

and btw there's no pthreadGC2.dll freshly
installed
by
csound.

i have another pthreadGC2.dll ( GNU C
x86(mingw32)
2.9.1.0 )
in
the
SuperCollider folder wich is more recent and
marked
as
32 bit.

i run i dependency check for the freshly
installed
csound~ and
is
the
only
architecture conflict.
i guess because strangely enough both the version
of
pthreadGC2.dll
in
the
system32 and in the 64 bit system folders are(
POSIX
Thread 32
ver
2.8.0
)....but if its 32 bit why dep check see it as a
64
one?

...mhhh

should i copy the dll from SuperCollider?

but first we have to understand why i can't see
the
csound~.mxe
from
its
default dir.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:24 PM, alfonso
santimone <
alfonso.santimone@gmail.com> wrote:

Steve i followed your path but as it is now i
have
a
csound~: No such object

all other externals from the default dir where
csound~
installs
just
work
and max load those correctly.
Can you give me your paths?
where are csound~, csound and Max 6.1.8 32 bit?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:01 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

Hi Mike,
the other externals in the C:\Users\Live
Machine\Documents\Max
Packages\ dir are correctly loaded by max.
the only one that is not "seen" is csound~. i
don't
know
why.

Steven i go try your procedure....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:48 PM, gogins <
notifications@github.com>

wrote:

You need to look at your environment
variables,
not
just
for
Csound
but
perhaps also for Max. Also maybe the Windows
registry
for
Max.
These
are
things that might control where plugins and
libraries
are
loaded
from.

Regards,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 12:37 PM, alfonso73 <
notifications@github.com>

wrote:

i've moved the whole csound folder in the
main
Max
folder
have
copied
all
the .dll from csound dir to that dir
and the 193 error is back here again.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:33 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

ok. now the dependency checker does not
reveal
any
architecture
conflict.
actually turned out that i use to have
another
csound~.mxe
copy
in
the
Max
32 bit folder.
i removed.
so now i only have the one at

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

good news are that i have no more 193
error!!!

bad news are that now Max windows claims
for
"csound~:
No
such
object"

????

all other externals from that folder are
recognized....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:29 PM, Steven Yi
<
notifications@github.com>
wrote:

Actually, just in case, just copy all
.dll's
from
Csound's
install\bin
folder to the location of csound~.mxe.

On Wed, Aug 13, 2014 at 12:29 PM, Steven
Yi
<
stevenyi@gmail.com>

wrote:

Oh, I was thinking to copy the dll's
from
Csound's
install
folder in
Program Files(x86). I hesitate to
diagnose
using
Rory's
csound
version
as
I have no idea how it was compiled.

On Wed, Aug 13, 2014 at 12:21 PM,
alfonso73 <
notifications@github.com>

wrote:

uninstalled Cabbage64, copied
csound64.dll,
libsndfile-1.dll,
libwinpthread-1.dll, pthreadGC2.dll
from
Cabbage32
to
the
folder
where
csound~.mxe is and....
no go..still 193 error while trying to
create
a
csound~
object.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:06 PM,
Steven
Yi <
notifications@github.com>

wrote:

Well having Rory's 64-bit csound
version
installed
would
most
certainly
cause all these problems. It's
likely
the
system's
loader
is
trying
to
load those before loading the 32-bit
csound
installed.

Two things you could try:

  1. Remove Rory's Csound
  2. Less intrusive, try copying all
    of
    the
    dll's
    into
    the
    same
    folder
    as
    csound~. They may then get picked up
    before
    Rory's
    (libcsound64.dll,
    libpthreadgc2.dll, etc.)

On Wed, Aug 13, 2014 at 11:58 AM,
alfonso73
<
notifications@github.com>
wrote:

same problem.

run another dependecy check with
the
32
bit
version
of
dependency
checker

MAXAPI.DLL
MAXAUDIO.DLL

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL

API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive
from a
recent
Cabbage
version
compiled
for
64 bit architecture ( so i guess
rory
is
using
a
64
bit
arch
compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52 PM,
Steven
Yi <
notifications@github.com>

wrote:

@alfonso73 : could you try this
build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use static
libstdc++
and
libgcc.
Let's
see
if
that
helps the situation.

On Wed, Aug 13, 2014 at 11:31
AM,
alfonso73 <
notifications@github.com>

wrote:

doesn't work anyway...

www.elgallorojorecords.com

soundcloud.com/alfonsosantimone

www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:29
PM,
alfonso
santimone
<
alfonso.santimone@gmail.com>
wrote:



Reply to this email directly or view it on GitHub.

@alfonso73
Copy link
Author

if you can give me some info on how to compile csound~
i can download VC express or whatever compile enviroment you use and try to
compile on Windows 7 here at my side.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 6:03 PM, Steven Yi notifications@github.com wrote:

I'll write an email to the Csound list to request assistance then.

On Thu, Aug 14, 2014 at 11:57 AM, gogins notifications@github.com
wrote:

Nope, windows 8 here.

Regards,
Mike
On Aug 14, 2014 11:49 AM, "Steven Yi" notifications@github.com wrote:

I looked up error 193 and didn't find much on Cycling '74's forums. I
checked and the standard windows error for 193 says something about
not being a valid win32 application. I have no idea though if the
error code being presented by Max is the windows error code though.

One thing we haven't really checked is if the issue has to do with my
building/testing on Windows Server 2012 rc2, which is similar to
Window 8.

@gogins: Do you have a Windows 7 setup? If so, could you perhaps try
downloading the Max Runtime and latest csound~ I compiled
(http://www.kunstmusik.com/csound~_1.1.2.exe) to see about
reproducing?

On Thu, Aug 14, 2014 at 11:10 AM, alfonso73 notifications@github.com
wrote:

yeah. i did the same check. funny things is that dependency check
give
the
same error about pthreadGC2.dll being 64 bit. but the old csound~
works
fine.
i try to reinstall csound 6 and csound~ 1.1.2.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:54 PM, Steven Yi notifications@github.com

wrote:

I checked and the dependencies for the older csound~ and the last
one
I built are the same, except for the difference of depending on the
libcsound64 version for CS5 vs CS6. Hopefully the pthreadGC2.dll
does
the trick.

On Thu, Aug 14, 2014 at 10:50 AM, Steven Yi stevenyi@gmail.com
wrote:

Well I'm pretty certain the issue has to do with dependent library
conflicts. csound~ 1.1.2 certainly is compiled for doubles and as
I
said, it works perfectly fine here. The situation on your computer
points to there being a conflict in versions of libraries, which
is
very difficult to sort out.

If you could try the pthreadGC2.dll, I'll run the older csound~ in
dependency walker to see if what I can find.

On Thu, Aug 14, 2014 at 10:47 AM, alfonso73
notifications@github.com

wrote:

Csound5 and csound~ 1.1.0 and Max 6.1.8 works perfectly.
Loaded some examples and they run perfectly.
so there's is definetly something wrong in csound~ 1.1.2 ( just
out
of
curiosity is it compiled for csound double? )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:12 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

still error 193.

i can try unistall csound 6 and the new csound~ and then install
the
old
csound5 and old csound~ to see if it works?
what do you think about it?
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:06 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

did it.
i can just delete the Max pref files to check if something
change...
really hard thing ti spot!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:03 PM, Steven Yi <
notifications@github.com>

wrote:

Unless I'm misunderstanding, did you move the .mxe in there?
And
did
you move the other folder out of the way to ensure we have a
clean
test?

On Thu, Aug 14, 2014 at 10:02 AM, Steven Yi <
stevenyi@gmail.com>
wrote:

That wouldn't do anything as that only affects Max's
locations
for
where to load. Having the .mxe in the same folder affects
the
OS's
library loading order, which is why I suggested the previous
steps.

On Thu, Aug 14, 2014 at 10:01 AM, alfonso73 <
notifications@github.com>
wrote:

for point 2 i just added the Csound6 folder into the File
Preferences
window of Max.
everything done.
but...guess what...
error 193

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 3:49 PM, Steven Yi <
notifications@github.com>
wrote:

How about trying this:

  1. Move the csound~.mxe into the folder where Csound is
    installed
    (i.e. c:\Program Files(x86)\csound6\bin)
  2. Move the folder where csound~ was installed to your
    desktop,
    or
    other location where Max won't normally see it
  3. Run Max and set the externals path to load from the
    Csound
    bin
    folder
  4. Copy some .maxpat and .csd examples to the csound bin
    folder
    and
    try running it

On Wed, Aug 13, 2014 at 7:38 PM, alfonso73
notifications@github.com

wrote:

yeah.
193 error.

Il giovedì 14 agosto 2014, Steven Yi
notifications@github.com

ha

scritto:

Did you copy the patch files to the same location as
the
.mxe
before
loading the patch?

On Wed, Aug 13, 2014 at 6:53 PM, alfonso73 <
notifications@github.com>
wrote:

btw the other dir are like yours.

i've just tried to run pluckedsynth.pat
from the Max runtime
and i have the
"Error 193 loading external csound~" message from Max
window

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:49 AM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

mhhh...i'm not logged as administrator....
your folder is C:\Users\Administrator
Documents\Max\Packages\csound~_v1.1.2-beta

mine is

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

so there's no -beta at the end

anyway as it is now Max does not see the external
so when i instantiate a csound~ object
i have this error in Max window

newobj csound~: No such object

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:35 AM, Steven Yi <
notifications@github.com>

wrote:

I have csound~ installed in:

C:\Users\Administrator\Documents\Max\Packages\csound~_v1.1.2-beta

and Csound 6.03.2 installed in:

c:\Program Files (x86)\Csound6

Max is installed in:

C:\Program Files (x86)\Cycling '74

I copy the examples from the csound~ examples into
one
folder
higher
where
the .mxe is. After that, I open Max Runtime and
open
pluckedsynth.pat
and
it loads and runs alright.

The version of pthreadGC2.dll I have here is also
2.9.1.0.
(I
should
maybe
package libpthreadGC2.dll with csound~.mxe, as it
looks
like
Michael
is
using a different pthread lib in his compiles.)

As it is now, are you getting the same error
message
or
no
error
message
at
all now (but also no csound~)?

On Wed, Aug 13, 2014 at 1:43 PM, alfonso73 <
notifications@github.com>

wrote:

and infact if i put the newer pthreadGC2 where
csound~
is
dependency
checker gives only

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

missing but no 64 architecture conflicts.

btw Max does not see csound~ from there.
this is very strange because on your system this
is
not a
problem
and
on
my
system the other externals in that dir are
correctly
loaded by
Max.
very tricky situation!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:35 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

and btw there's no pthreadGC2.dll freshly
installed
by
csound.

i have another pthreadGC2.dll ( GNU C
x86(mingw32)
2.9.1.0 )
in
the
SuperCollider folder wich is more recent and
marked
as
32 bit.

i run i dependency check for the freshly
installed
csound~ and
is
the
only
architecture conflict.
i guess because strangely enough both the
version
of
pthreadGC2.dll
in
the
system32 and in the 64 bit system folders are(
POSIX
Thread 32
ver
2.8.0
)....but if its 32 bit why dep check see it as
a
64
one?

...mhhh

should i copy the dll from SuperCollider?

but first we have to understand why i can't
see
the
csound~.mxe
from
its
default dir.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:24 PM, alfonso
santimone <
alfonso.santimone@gmail.com> wrote:

Steve i followed your path but as it is now i
have
a
csound~: No such object

all other externals from the default dir
where
csound~
installs
just
work
and max load those correctly.
Can you give me your paths?
where are csound~, csound and Max 6.1.8 32
bit?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:01 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

Hi Mike,
the other externals in the C:\Users\Live
Machine\Documents\Max
Packages\ dir are correctly loaded by max.
the only one that is not "seen" is csound~.
i
don't
know
why.

Steven i go try your procedure....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:48 PM, gogins <
notifications@github.com>

wrote:

You need to look at your environment
variables,
not
just
for
Csound
but
perhaps also for Max. Also maybe the
Windows
registry
for
Max.
These
are
things that might control where plugins and
libraries
are
loaded
from.

Regards,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 12:37 PM, alfonso73
<
notifications@github.com>

wrote:

i've moved the whole csound folder in the
main
Max
folder
have
copied
all
the .dll from csound dir to that dir
and the 193 error is back here again.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:33 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

ok. now the dependency checker does not
reveal
any
architecture
conflict.
actually turned out that i use to have
another
csound~.mxe
copy
in
the
Max
32 bit folder.
i removed.
so now i only have the one at

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

good news are that i have no more 193
error!!!

bad news are that now Max windows
claims
for
"csound~:
No
such
object"

????

all other externals from that folder
are
recognized....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:29 PM, Steven
Yi
<
notifications@github.com>
wrote:

Actually, just in case, just copy all
.dll's
from
Csound's
install\bin
folder to the location of csound~.mxe.

On Wed, Aug 13, 2014 at 12:29 PM,
Steven
Yi
<
stevenyi@gmail.com>

wrote:

Oh, I was thinking to copy the dll's
from
Csound's
install
folder in
Program Files(x86). I hesitate to
diagnose
using
Rory's
csound
version
as
I have no idea how it was compiled.

On Wed, Aug 13, 2014 at 12:21 PM,
alfonso73 <
notifications@github.com>

wrote:

uninstalled Cabbage64, copied
csound64.dll,
libsndfile-1.dll,
libwinpthread-1.dll, pthreadGC2.dll
from
Cabbage32
to
the
folder
where
csound~.mxe is and....
no go..still 193 error while trying
to
create
a
csound~
object.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:06 PM,
Steven
Yi <
notifications@github.com>

wrote:

Well having Rory's 64-bit csound
version
installed
would
most
certainly
cause all these problems. It's
likely
the
system's
loader
is
trying
to
load those before loading the
32-bit
csound
installed.

Two things you could try:

  1. Remove Rory's Csound
  2. Less intrusive, try copying
    all
    of
    the
    dll's
    into
    the
    same
    folder
    as
    csound~. They may then get picked
    up
    before
    Rory's
    (libcsound64.dll,
    libpthreadgc2.dll, etc.)

On Wed, Aug 13, 2014 at 11:58 AM,
alfonso73
<
notifications@github.com>
wrote:

same problem.

run another dependecy check
with
the
32
bit
version
of
dependency
checker

MAXAPI.DLL
MAXAUDIO.DLL

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL

API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive
from a
recent
Cabbage
version
compiled
for
64 bit architecture ( so i
guess
rory
is
using
a
64
bit
arch
compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone

www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52
PM,
Steven
Yi <
notifications@github.com>

wrote:

@alfonso73 : could you try
this
build:

http://www.kunstmusik.com/csound~_1.1.2.exe

I've just compiled it use
static
libstdc++
and
libgcc.
Let's
see
if
that
helps the situation.

On Wed, Aug 13, 2014 at 11:31
AM,
alfonso73 <
notifications@github.com>

wrote:

wrote:



Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#345 (comment).

@kunstmusik
Copy link
Member

Michael has written documentation on how to get Csound compiled that
is in the csound6/docs folder. You would need to checkout the latest
develop branch from Csound's git repository, then follow those
instructions. You would then need to download the Max SDK from Cycling
'74's website, then edit your Custom.make in your cs6 root folder to
add the location of that SDK, i.e.:

set(MAX_SDK_ROOT "C:/Users/Administrator/work/MaxSDK-6.1.4")

After that, when you run CMake everything should be setup to build
csound~. From there, if you go into the
csound6/fronteneds/max_csound_tilde/installer folder, you can run the
build-windows-installer.sh script. You would need to have Inno Setup
installed, and may need to modify the build-windows-installer.sh
script for the location of that (near the top of that file). After
that, you can build the installer using:

./build-windows-installer.sh develop

(assuming you are doing this in an MSYS shell).

This is a bit of a work if you don't already have a working Csound
build, as the build file for csound~ is done as part of the full
csound CMake build. (I had thought to separate out the csound~ part
into its own project but have not looked into what was required.)

@gogins: Could you try doing a csound~ build? All it requires
compared to a standard csound build is download the Max SDK and
setting that one environment variable in Custom.cmake. In a normal
build, it would then build the .mxe artifact within the
buildRoot/frontends/max_csound_tilde folder.

On Thu, Aug 14, 2014 at 12:06 PM, alfonso73 notifications@github.com wrote:

if you can give me some info on how to compile csound~
i can download VC express or whatever compile enviroment you use and try to
compile on Windows 7 here at my side.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 6:03 PM, Steven Yi notifications@github.com wrote:

I'll write an email to the Csound list to request assistance then.

On Thu, Aug 14, 2014 at 11:57 AM, gogins notifications@github.com
wrote:

Nope, windows 8 here.

Regards,
Mike
On Aug 14, 2014 11:49 AM, "Steven Yi" notifications@github.com wrote:

I looked up error 193 and didn't find much on Cycling '74's forums. I
checked and the standard windows error for 193 says something about
not being a valid win32 application. I have no idea though if the
error code being presented by Max is the windows error code though.

One thing we haven't really checked is if the issue has to do with my
building/testing on Windows Server 2012 rc2, which is similar to
Window 8.

@gogins: Do you have a Windows 7 setup? If so, could you perhaps try
downloading the Max Runtime and latest csound~ I compiled
(http://www.kunstmusik.com/csound~_1.1.2.exe) to see about
reproducing?

On Thu, Aug 14, 2014 at 11:10 AM, alfonso73 notifications@github.com
wrote:

yeah. i did the same check. funny things is that dependency check
give
the
same error about pthreadGC2.dll being 64 bit. but the old csound~
works
fine.
i try to reinstall csound 6 and csound~ 1.1.2.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:54 PM, Steven Yi notifications@github.com

wrote:

I checked and the dependencies for the older csound~ and the last
one
I built are the same, except for the difference of depending on the
libcsound64 version for CS5 vs CS6. Hopefully the pthreadGC2.dll
does
the trick.

On Thu, Aug 14, 2014 at 10:50 AM, Steven Yi stevenyi@gmail.com
wrote:

Well I'm pretty certain the issue has to do with dependent library
conflicts. csound~ 1.1.2 certainly is compiled for doubles and as
I
said, it works perfectly fine here. The situation on your computer
points to there being a conflict in versions of libraries, which
is
very difficult to sort out.

If you could try the pthreadGC2.dll, I'll run the older csound~ in
dependency walker to see if what I can find.

On Thu, Aug 14, 2014 at 10:47 AM, alfonso73
notifications@github.com

wrote:

Csound5 and csound~ 1.1.0 and Max 6.1.8 works perfectly.
Loaded some examples and they run perfectly.
so there's is definetly something wrong in csound~ 1.1.2 ( just
out
of
curiosity is it compiled for csound double? )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:12 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

still error 193.

i can try unistall csound 6 and the new csound~ and then install
the
old
csound5 and old csound~ to see if it works?
what do you think about it?
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:06 PM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

did it.
i can just delete the Max pref files to check if something
change...
really hard thing ti spot!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 4:03 PM, Steven Yi <
notifications@github.com>

wrote:

Unless I'm misunderstanding, did you move the .mxe in there?
And
did
you move the other folder out of the way to ensure we have a
clean
test?

On Thu, Aug 14, 2014 at 10:02 AM, Steven Yi <
stevenyi@gmail.com>
wrote:

That wouldn't do anything as that only affects Max's
locations
for
where to load. Having the .mxe in the same folder affects
the
OS's
library loading order, which is why I suggested the previous
steps.

On Thu, Aug 14, 2014 at 10:01 AM, alfonso73 <
notifications@github.com>
wrote:

for point 2 i just added the Csound6 folder into the File
Preferences
window of Max.
everything done.
but...guess what...
error 193

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 3:49 PM, Steven Yi <
notifications@github.com>
wrote:

How about trying this:

  1. Move the csound~.mxe into the folder where Csound is
    installed
    (i.e. c:\Program Files(x86)\csound6\bin)
  2. Move the folder where csound~ was installed to your
    desktop,
    or
    other location where Max won't normally see it
  3. Run Max and set the externals path to load from the
    Csound
    bin
    folder
  4. Copy some .maxpat and .csd examples to the csound bin
    folder
    and
    try running it

On Wed, Aug 13, 2014 at 7:38 PM, alfonso73
notifications@github.com

wrote:

yeah.
193 error.

Il giovedì 14 agosto 2014, Steven Yi
notifications@github.com

ha

scritto:

Did you copy the patch files to the same location as
the
.mxe
before
loading the patch?

On Wed, Aug 13, 2014 at 6:53 PM, alfonso73 <
notifications@github.com>
wrote:

btw the other dir are like yours.

i've just tried to run pluckedsynth.pat
from the Max runtime
and i have the
"Error 193 loading external csound~" message from Max
window

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:49 AM, alfonso santimone <
alfonso.santimone@gmail.com> wrote:

mhhh...i'm not logged as administrator....
your folder is C:\Users\Administrator
Documents\Max\Packages\csound~_v1.1.2-beta

mine is

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

so there's no -beta at the end

anyway as it is now Max does not see the external
so when i instantiate a csound~ object
i have this error in Max window

newobj csound~: No such object

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, Aug 14, 2014 at 12:35 AM, Steven Yi <
notifications@github.com>

wrote:

I have csound~ installed in:

C:\Users\Administrator\Documents\Max\Packages\csound~_v1.1.2-beta

and Csound 6.03.2 installed in:

c:\Program Files (x86)\Csound6

Max is installed in:

C:\Program Files (x86)\Cycling '74

I copy the examples from the csound~ examples into
one
folder
higher
where
the .mxe is. After that, I open Max Runtime and
open
pluckedsynth.pat
and
it loads and runs alright.

The version of pthreadGC2.dll I have here is also
2.9.1.0.
(I
should
maybe
package libpthreadGC2.dll with csound~.mxe, as it
looks
like
Michael
is
using a different pthread lib in his compiles.)

As it is now, are you getting the same error
message
or
no
error
message
at
all now (but also no csound~)?

On Wed, Aug 13, 2014 at 1:43 PM, alfonso73 <
notifications@github.com>

wrote:

and infact if i put the newer pthreadGC2 where
csound~
is
dependency
checker gives only

MAXAPI.DLL
MAXAUDIO.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

missing but no 64 architecture conflicts.

btw Max does not see csound~ from there.
this is very strange because on your system this
is
not a
problem
and
on
my
system the other externals in that dir are
correctly
loaded by
Max.
very tricky situation!

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:35 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

and btw there's no pthreadGC2.dll freshly
installed
by
csound.

i have another pthreadGC2.dll ( GNU C
x86(mingw32)
2.9.1.0 )
in
the
SuperCollider folder wich is more recent and
marked
as
32 bit.

i run i dependency check for the freshly
installed
csound~ and
is
the
only
architecture conflict.
i guess because strangely enough both the
version
of
pthreadGC2.dll
in
the
system32 and in the 64 bit system folders are(
POSIX
Thread 32
ver
2.8.0
)....but if its 32 bit why dep check see it as
a
64
one?

...mhhh

should i copy the dll from SuperCollider?

but first we have to understand why i can't
see
the
csound~.mxe
from
its
default dir.

a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:24 PM, alfonso
santimone <
alfonso.santimone@gmail.com> wrote:

Steve i followed your path but as it is now i
have
a
csound~: No such object

all other externals from the default dir
where
csound~
installs
just
work
and max load those correctly.
Can you give me your paths?
where are csound~, csound and Max 6.1.8 32
bit?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 7:01 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

Hi Mike,
the other externals in the C:\Users\Live
Machine\Documents\Max
Packages\ dir are correctly loaded by max.
the only one that is not "seen" is csound~.
i
don't
know
why.

Steven i go try your procedure....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:48 PM, gogins <
notifications@github.com>

wrote:

You need to look at your environment
variables,
not
just
for
Csound
but
perhaps also for Max. Also maybe the
Windows
registry
for
Max.
These
are
things that might control where plugins and
libraries
are
loaded
from.

Regards,
Mike


Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com

On Wed, Aug 13, 2014 at 12:37 PM, alfonso73
<
notifications@github.com>

wrote:

i've moved the whole csound folder in the
main
Max
folder
have
copied
all
the .dll from csound dir to that dir
and the 193 error is back here again.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:33 PM, alfonso
santimone
<
alfonso.santimone@gmail.com> wrote:

ok. now the dependency checker does not
reveal
any
architecture
conflict.
actually turned out that i use to have
another
csound~.mxe
copy
in
the
Max
32 bit folder.
i removed.
so now i only have the one at

C:\Users\Live
Machine\Documents\Max\Packages\csound~_v1.1.2

good news are that i have no more 193
error!!!

bad news are that now Max windows
claims
for
"csound~:
No
such
object"

????

all other externals from that folder
are
recognized....

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:29 PM, Steven
Yi
<
notifications@github.com>
wrote:

Actually, just in case, just copy all
.dll's
from
Csound's
install\bin
folder to the location of csound~.mxe.

On Wed, Aug 13, 2014 at 12:29 PM,
Steven
Yi
<
stevenyi@gmail.com>

wrote:

Oh, I was thinking to copy the dll's
from
Csound's
install
folder in
Program Files(x86). I hesitate to
diagnose
using
Rory's
csound
version
as
I have no idea how it was compiled.

On Wed, Aug 13, 2014 at 12:21 PM,
alfonso73 <
notifications@github.com>

wrote:

uninstalled Cabbage64, copied
csound64.dll,
libsndfile-1.dll,
libwinpthread-1.dll, pthreadGC2.dll
from
Cabbage32
to
the
folder
where
csound~.mxe is and....
no go..still 193 error while trying
to
create
a
csound~
object.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 6:06 PM,
Steven
Yi <
notifications@github.com>

wrote:

Well having Rory's 64-bit csound
version
installed
would
most
certainly
cause all these problems. It's
likely
the
system's
loader
is
trying
to
load those before loading the
32-bit
csound
installed.

Two things you could try:

On Wed, Aug 13, 2014 at 11:58 AM,
alfonso73
<
notifications@github.com>
wrote:

same problem.

run another dependecy check
with
the
32
bit
version
of
dependency
checker

MAXAPI.DLL
MAXAUDIO.DLL

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL

API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL

API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
GPSVC.DLL
IESHIMS.DLL

not found

CSOUND64.DLL
LIBSNDFILE-1.DLL
LIBWINPTHREAD-1.DLL
PTHREADGC2.DLL

detected as x64 architecture

the csound64.dll should derive
from a
recent
Cabbage
version
compiled
for
64 bit architecture ( so i
guess
rory
is
using
a
64
bit
arch
compiled
csound )

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone

www.facebook.com/alfonsosantimone

On Wed, Aug 13, 2014 at 5:52
PM,
Steven
Yi <
notifications@github.com>

wrote:

wrote:



Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub.

@rorywalsh
Copy link
Contributor

I can get this working on my Win8 machine if I:

  1. use '-static-libgcc -static' when building any dll that csound64.dll loads on startup
  2. add -+rtaudio=null to any .csd file that is to be used in max as it will disable the loading of rtpa.dll

@kunstmusik
Copy link
Member

@rorywalsh Could you do a pull request with the changes? As for rtaudio=null, that could probably be done automatically by csound~, no?

@rorywalsh
Copy link
Contributor

Will do, but note that my changes will cause plugin opcodes on all platform to be built with static linking. I'm not sure that something you wish to do. Anyway, I'll put in a pull request later and you can review it. And yes, it would be better to add -+rtaudio in csound~.

@vlazzarini vlazzarini added this to the 6.05.0 milestone Apr 9, 2015
@vlazzarini
Copy link
Member

Any movement in this one? Can we finalise it and close it (appears to be a cmake issue now)?

@rorywalsh
Copy link
Contributor

Hi Victor. I've absolutely zero Cmake chops so I'll have to leave this with someone who knows how to make these changes.

@vlazzarini
Copy link
Member

Steven is our go-to man for CMake. Do you have all the info you need to make these changes @kunstmusik?

@kunstmusik
Copy link
Member

I looked into this. We already had --static-libgcc for C artifacts set in the main CMakeLists.txt. I added a flag for --static-libstdc++ for C++ artifacts. I'm able to build most things but it fails on libcsnd6 as it complains about not having a reference to pthreads, but I seem to remember this being a problem before and am not sure if it's just me or due to the change I made.

@gogins and @rorywalsh : Could you test the latest in develop to make sure things are still compiling for you? Also, @rorywalsh could you test if change does what is needed for csound~?

@rorywalsh
Copy link
Contributor

Hi Steven. I'm afraid I'm only getting a chance to look into this now. It seems that Mike had no problems preparing the Windows installer for the last release, so I'm assuming that everything compiles Ok. I'm going to check now myself. If there are any issues I will report back to you.

@rorywalsh
Copy link
Contributor

It looks like csound~ is working now. But I'm getting a hang on exit. The problem, windows informs me, is to do with the libgcc dll. But if that's the case then it would seem that the -static-libgcc is not making any difference when building?

@alfonso73
Copy link
Author

Hi all guys,
i'm thinkin' about trying another compile of csound~.mxe and csound~.mxe64.
Has some progress on csound~ being made recently?
Maybe i need some special csound.dll version to try compiling for 64 bit
architecture?
Many thanks and all the best!
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Fri, May 8, 2015 at 2:42 PM, Rory Walsh notifications@github.com wrote:

It looks like csound~ is working now. But I'm getting a hang on exit. The
problem, windows informs me, is to do with the libgcc dll. But if that's
the case then it would seem that the -static-libgcc is not making any
difference when building?


Reply to this email directly or view it on GitHub
#345 (comment).

@rorywalsh
Copy link
Contributor

csound~ for 32bit Max is fine, but until Cycling74 supports building of
64bit objects with MiinGW you will need to use MSVC. It'll be quite a bit
of work I'd say. In fact, I think it might be a good idea to just port
Victor's csoundapi~ object in Pd to Max. It would be far simpler to
maintain in the long term.

On 14 May 2015 at 15:41, alfonso73 notifications@github.com wrote:

Hi all guys,
i'm thinkin' about trying another compile of csound~.mxe and csound~.mxe64.
Has some progress on csound~ being made recently?
Maybe i need some special csound.dll version to try compiling for 64 bit
architecture?
Many thanks and all the best!
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Fri, May 8, 2015 at 2:42 PM, Rory Walsh notifications@github.com
wrote:

It looks like csound~ is working now. But I'm getting a hang on exit. The
problem, windows informs me, is to do with the libgcc dll. But if that's
the case then it would seem that the -static-libgcc is not making any
difference when building?


Reply to this email directly or view it on GitHub
#345 (comment).


Reply to this email directly or view it on GitHub
#345 (comment).

@vlazzarini
Copy link
Member

Why would it be simpler?

@alfonso73
Copy link
Author

I guess is just a matter of workin on things to let the code be compatible
with MSVC compiler.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, May 14, 2015 at 4:52 PM, vlazzarini notifications@github.com
wrote:

Why would it be simpler?


Reply to this email directly or view it on GitHub
#345 (comment).

@rorywalsh
Copy link
Contributor

It's far more lightweight than the Max object from what I can tell. Plus, I
can follow your code, just about!

On 14 May 2015 at 15:52, vlazzarini notifications@github.com wrote:

Why would it be simpler?


Reply to this email directly or view it on GitHub
#345 (comment).

@vlazzarini
Copy link
Member

I am not sure about it. The source is OK as far as I can see, and it is being maintained. The trouble is to do with building and linking in Windows. I thought this was solved by your contribution as discussed above. Shouldn't we close this ticket?

@rorywalsh
Copy link
Contributor

32bit version is fine. Alfonso is talking about a 64bit version. 64bit
objects can't be built with MinGW.

On 14 May 2015 at 15:58, vlazzarini notifications@github.com wrote:

I am not sure about it. The source is OK as far as I can see, and it is
being maintained. The trouble is to do with building and linking in
Windows. I thought this was solved by your contribution as discussed above.
Shouldn't we close this ticket?


Reply to this email directly or view it on GitHub
#345 (comment).

@rorywalsh
Copy link
Contributor

When I say can't I mean I failed in my attempts and the cycling74
developers can't manage it either. I'm sure however that it could be done,
if in the hands of the right person!

On 14 May 2015 at 16:00, Rory Walsh rorywalsh@ear.ie wrote:

32bit version is fine. Alfonso is talking about a 64bit version. 64bit
objects can't be built with MinGW.

On 14 May 2015 at 15:58, vlazzarini notifications@github.com wrote:

I am not sure about it. The source is OK as far as I can see, and it is
being maintained. The trouble is to do with building and linking in
Windows. I thought this was solved by your contribution as discussed above.
Shouldn't we close this ticket?


Reply to this email directly or view it on GitHub
#345 (comment).

@vlazzarini
Copy link
Member

I built a 64bit Csound with mingwn64 here, so it is possible. I can't however commit to maintain this build.

@vlazzarini
Copy link
Member

It seems that we should close this ticket, since the 64bit windows is a separate issue.

@alfonso73
Copy link
Author

Would you mind victor making a short tutorial on how to compile Csound on
mingw64?
Anyway the thing is that Max SDK seems to compile only with Visual Studio
and not on mingw.
Yes 64 bit is a separate issue. Should we open another ticket and close
this one?

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, May 14, 2015 at 5:17 PM, vlazzarini notifications@github.com
wrote:

It seems that we should close this ticket, since the 64bit windows is a
separate issue.


Reply to this email directly or view it on GitHub
#345 (comment).

@vlazzarini
Copy link
Member

It's been a while, but I don't think I did anything terribly different. I downloaded mingw64, msys, cmake, etc (as for any ordinary build), build libsndfile with it, and placed it where cmake would see. Then I ran cmake and make. You can have a go, and ask questions in the list as you go along. I am closing this ticket, because it is done.

@alfonso73
Copy link
Author

ok thanks.
a.

www.elgallorojorecords.com
soundcloud.com/alfonsosantimone
www.facebook.com/alfonsosantimone

On Thu, May 14, 2015 at 5:40 PM, vlazzarini notifications@github.com
wrote:

It's been a while, but I don't think I did anything terribly different. I
downloaded mingw64, msys, cmake, etc (as for any ordinary build), build
libsndfile with it, and placed it where cmake would see. Then I ran cmake
and make. You can have a go, and ask questions in the list as you go along.
I am closing this ticket, because it is done.


Reply to this email directly or view it on GitHub
#345 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants