Hello y'all,

I'm trying to distribute a game which employs csound (called Zone: X), but
before I do, I need to package Csound for deployment. I want the game to be
easy to install and play, ideally it would be as simple as double clicking a
.exe. You see, part of the philosophy behind my game design is that it
should be accessible to a wide user base regardless of technical ability.  I
already tried adding the csound dll's to the folder, and while that gets it
to open, it doesn't get Csound working.  I also tried using 's
system() to load the paths for OPCODE64 and OPCODE, but to no avail.  Any
advice about how to distribute this game would be appreciated greatly.

Thank you,
Kevin Herald



--
View this message in context: http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html
Sent from the Csound - General mailing list archive at Nabble.com.

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Why don't you include the Csound installer with the game installation?

> On 6 Feb 2016, at 20:14, Z1X  wrote:
> 
> Hello y'all,
> 
> I'm trying to distribute a game which employs csound (called Zone: X), but
> before I do, I need to package Csound for deployment. I want the game to be
> easy to install and play, ideally it would be as simple as double clicking a
> .exe. You see, part of the philosophy behind my game design is that it
> should be accessible to a wide user base regardless of technical ability.  I
> already tried adding the csound dll's to the folder, and while that gets it
> to open, it doesn't get Csound working.  I also tried using 's
> system() to load the paths for OPCODE64 and OPCODE, but to no avail.  Any
> advice about how to distribute this game would be appreciated greatly.
> 
> Thank you,
> Kevin Herald
> 
> 
> 
> --
> View this message in context: http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html
> Sent from the Csound - General mailing list archive at Nabble.com.
> 
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi Kevin,

Could you describe a bit more of what you mean by "doesn't get Csound
working"?  Are there particular error messages you see?  If you have
the main Csound library loading, the rest should be an issue of
getting the OPCODE6DIR64  set up correctly (also, in your email you
mentioned OPCODE64; I'm not sure if that was a typo but the full name
should be used).

I think if you could describe the error a little more it'd give some
information we could use to help diagnose.

steven

On Sat, Feb 6, 2016 at 3:14 PM, Z1X  wrote:
> Hello y'all,
>
> I'm trying to distribute a game which employs csound (called Zone: X), but
> before I do, I need to package Csound for deployment. I want the game to be
> easy to install and play, ideally it would be as simple as double clicking a
> .exe. You see, part of the philosophy behind my game design is that it
> should be accessible to a wide user base regardless of technical ability.  I
> already tried adding the csound dll's to the folder, and while that gets it
> to open, it doesn't get Csound working.  I also tried using 's
> system() to load the paths for OPCODE64 and OPCODE, but to no avail.  Any
> advice about how to distribute this game would be appreciated greatly.
>
> Thank you,
> Kevin Herald
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>         https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Well I think that's a grand idea!  If I'm not mistaken the Linux version is a little involved, but to be fair, I guess a bit more technical ability can be expected of a linux user :)

Thanks,

Kevin Herald

On Sat, Feb 6, 2016 at 3:57 PM, Victor Lazzarini <Victor.Lazzarini@nuim.ie> wrote:

Why don't you include the Csound installer with the game installation?

> On 6 Feb 2016, at 20:14, Z1X <hallelujah.hephzibah@GMAIL.COM> wrote:
>
> Hello y'all,
>
> I'm trying to distribute a game which employs csound (called Zone: X), but
> before I do, I need to package Csound for deployment. I want the game to be
> easy to install and play, ideally it would be as simple as double clicking a
> .exe. You see, part of the philosophy behind my game design is that it
> should be accessible to a wide user base regardless of technical ability.  I
> already tried adding the csound dll's to the folder, and while that gets it
> to open, it doesn't get Csound working.  I also tried using <stdlib.h>'s
> system() to load the paths for OPCODE64 and OPCODE, but to no avail.  Any
> advice about how to distribute this game would be appreciated greatly.
>
> Thank you,
> Kevin Herald
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
> Csound mailing list
> Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list Csound@listserv.heanet.ie https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

That's odd that there is no console output.  I would have thought that
Csound would default to print out to stderr even when linked in and
used as a library.  Are you executing the .exe from a commandline to
start or just double-clicking?  If the latter, could you try the
former?

Also, csound is certainly used embedded via API from CsoundQT and
Cabbage.  Maybe one of the developers from those systems could comment
on how OPCODE6DIR64 is being set within those applications?

On Sat, Feb 6, 2016 at 6:45 PM, Kevin Legrismith  wrote:
> Alas, there is no console output from the .exe, regardless of whether it
> works (if Csound6 isn't hidden) or if it doesn't.  Also, Dr. Yi, I was
> working from memory, so it was an error, and I did wish to include the DIR
> suffix in my post, but no I didn't have the 6 in there; I was getting my
> info from https://csound.github.io/docs/manual/Configuring.html, so it was a
> little outdated.  Unfortunately this change didn't resolve the problem
> completely, because "set" appears to set environmental variables only for
> the duration of a cmd prompts life.  I'm looking into setx as a more
> permanent solution, but with no joy so far.
> On Sat, Feb 6, 2016 at 3:35 PM, Steven Yi  wrote:
>>
>> Hi Kevin,
>>
>> Could you describe a bit more of what you mean by "doesn't get Csound
>> working"?  Are there particular error messages you see?  If you have
>> the main Csound library loading, the rest should be an issue of
>> getting the OPCODE6DIR64  set up correctly (also, in your email you
>> mentioned OPCODE64; I'm not sure if that was a typo but the full name
>> should be used).
>>
>> I think if you could describe the error a little more it'd give some
>> information we could use to help diagnose.
>>
>> steven
>>
>> On Sat, Feb 6, 2016 at 3:14 PM, Z1X 
>> wrote:
>> > Hello y'all,
>> >
>> > I'm trying to distribute a game which employs csound (called Zone: X),
>> > but
>> > before I do, I need to package Csound for deployment. I want the game to
>> > be
>> > easy to install and play, ideally it would be as simple as double
>> > clicking a
>> > .exe. You see, part of the philosophy behind my game design is that it
>> > should be accessible to a wide user base regardless of technical
>> > ability.  I
>> > already tried adding the csound dll's to the folder, and while that gets
>> > it
>> > to open, it doesn't get Csound working.  I also tried using 's
>> > system() to load the paths for OPCODE64 and OPCODE, but to no avail.
>> > Any
>> > advice about how to distribute this game would be appreciated greatly.
>> >
>> > Thank you,
>> > Kevin Herald
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> > http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html
>> > Sent from the Csound - General mailing list archive at Nabble.com.
>> >
>> > Csound mailing list
>> > Csound@listserv.heanet.ie
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> > Send bugs reports to
>> >         https://github.com/csound/csound/issues
>> > Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> Csound@listserv.heanet.ie
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Hi,

Having a look at the CsoundQt source code (qutecsound.cpp:1000), here it is done by:

csoundSetGlobalEnv("OPCODE6DIR64", m_options->opcode6dir64.toLatin1().constData());

https://csound.github.io/docs/api/group__MISCELLANEOUS.html#ga0183dad9bbc4961d66a280e5292091ed

Greetings,

tarmo

On Saturday 06 February 2016 20:39:24 you wrote:

> That's odd that there is no console output. I would have thought that

> Csound would default to print out to stderr even when linked in and

> used as a library. Are you executing the .exe from a commandline to

> start or just double-clicking? If the latter, could you try the

> former?

>

> Also, csound is certainly used embedded via API from CsoundQT and

> Cabbage. Maybe one of the developers from those systems could comment

> on how OPCODE6DIR64 is being set within those applications?

>

> On Sat, Feb 6, 2016 at 6:45 PM, Kevin Legrismith <khlegrismith@gmail.com> wrote:

> > Alas, there is no console output from the .exe, regardless of whether it

> > works (if Csound6 isn't hidden) or if it doesn't. Also, Dr. Yi, I was

> > working from memory, so it was an error, and I did wish to include the DIR

> > suffix in my post, but no I didn't have the 6 in there; I was getting my

> > info from https://csound.github.io/docs/manual/Configuring.html, so it was

> > a little outdated. Unfortunately this change didn't resolve the problem

> > completely, because "set" appears to set environmental variables only for

> > the duration of a cmd prompts life. I'm looking into setx as a more

> > permanent solution, but with no joy so far.

> >

> > On Sat, Feb 6, 2016 at 3:35 PM, Steven Yi <stevenyi@gmail.com> wrote:

> >> Hi Kevin,

> >>

> >> Could you describe a bit more of what you mean by "doesn't get Csound

> >> working"? Are there particular error messages you see? If you have

> >> the main Csound library loading, the rest should be an issue of

> >> getting the OPCODE6DIR64 set up correctly (also, in your email you

> >> mentioned OPCODE64; I'm not sure if that was a typo but the full name

> >> should be used).

> >>

> >> I think if you could describe the error a little more it'd give some

> >> information we could use to help diagnose.

> >>

> >> steven

> >>

> >> On Sat, Feb 6, 2016 at 3:14 PM, Z1X <hallelujah.hephzibah@gmail.com>

> >>

> >> wrote:

> >> > Hello y'all,

> >> >

> >> > I'm trying to distribute a game which employs csound (called Zone: X),

> >> > but

> >> > before I do, I need to package Csound for deployment. I want the game

> >> > to

> >> > be

> >> > easy to install and play, ideally it would be as simple as double

> >> > clicking a

> >> > .exe. You see, part of the philosophy behind my game design is that it

> >> > should be accessible to a wide user base regardless of technical

> >> > ability. I

> >> > already tried adding the csound dll's to the folder, and while that

> >> > gets

> >> > it

> >> > to open, it doesn't get Csound working. I also tried using

> >> > <stdlib.h>'s

> >> > system() to load the paths for OPCODE64 and OPCODE, but to no avail.

> >> > Any

> >> > advice about how to distribute this game would be appreciated greatly.

> >> >

> >> > Thank you,

> >> > Kevin Herald

> >> >

> >> >

> >> >

> >> > --

> >> > View this message in context:

> >> > http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html

> >> > Sent from the Csound - General mailing list archive at Nabble.com.

> >> >

> >> > Csound mailing list

> >> > Csound@listserv.heanet.ie

> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> >> > Send bugs reports to

> >> >

> >> > https://github.com/csound/csound/issues

> >> >

> >> > Discussions of bugs and features can be posted here

> >>

> >> Csound mailing list

> >> Csound@listserv.heanet.ie

> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> >> Send bugs reports to

> >>

> >> https://github.com/csound/csound/issues

> >>

> >> Discussions of bugs and features can be posted here

> >

> > Csound mailing list Csound@listserv.heanet.ie

> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to

> > https://github.com/csound/csound/issues Discussions of bugs and features

> > can be posted here

>

> Csound mailing list

> Csound@listserv.heanet.ie

> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND

> Send bugs reports to

> https://github.com/csound/csound/issues

> Discussions of bugs and features can be posted here

Can I ask which libraries you have added already? In the app I'm
developing, I haven't bothered sorting through what parts of csound I
do and don't need yet, so all I've done is add the entire csound
folder to my c++ project directory, and add the relevant linkage and
search locations in my project. After that, csound seems to know what
to do, both in the linux and windows versions.

Pete

On Sun, Feb 7, 2016 at 9:36 AM, Tarmo Johannes
 wrote:
> Hi,
>
>
>
> Having a look at the CsoundQt source code (qutecsound.cpp:1000), here it is
> done by:
>
>
>
> csoundSetGlobalEnv("OPCODE6DIR64",
> m_options->opcode6dir64.toLatin1().constData());
>
>
>
> https://csound.github.io/docs/api/group__MISCELLANEOUS.html#ga0183dad9bbc4961d66a280e5292091ed
>
>
>
>
>
> Greetings,
>
> tarmo
>
>
>
> On Saturday 06 February 2016 20:39:24 you wrote:
>
>> That's odd that there is no console output. I would have thought that
>
>> Csound would default to print out to stderr even when linked in and
>
>> used as a library. Are you executing the .exe from a commandline to
>
>> start or just double-clicking? If the latter, could you try the
>
>> former?
>
>>
>
>> Also, csound is certainly used embedded via API from CsoundQT and
>
>> Cabbage. Maybe one of the developers from those systems could comment
>
>> on how OPCODE6DIR64 is being set within those applications?
>
>>
>
>> On Sat, Feb 6, 2016 at 6:45 PM, Kevin Legrismith 
>> wrote:
>
>> > Alas, there is no console output from the .exe, regardless of whether it
>
>> > works (if Csound6 isn't hidden) or if it doesn't. Also, Dr. Yi, I was
>
>> > working from memory, so it was an error, and I did wish to include the
>> > DIR
>
>> > suffix in my post, but no I didn't have the 6 in there; I was getting my
>
>> > info from https://csound.github.io/docs/manual/Configuring.html, so it
>> > was
>
>> > a little outdated. Unfortunately this change didn't resolve the problem
>
>> > completely, because "set" appears to set environmental variables only
>> > for
>
>> > the duration of a cmd prompts life. I'm looking into setx as a more
>
>> > permanent solution, but with no joy so far.
>
>> >
>
>> > On Sat, Feb 6, 2016 at 3:35 PM, Steven Yi  wrote:
>
>> >> Hi Kevin,
>
>> >>
>
>> >> Could you describe a bit more of what you mean by "doesn't get Csound
>
>> >> working"? Are there particular error messages you see? If you have
>
>> >> the main Csound library loading, the rest should be an issue of
>
>> >> getting the OPCODE6DIR64 set up correctly (also, in your email you
>
>> >> mentioned OPCODE64; I'm not sure if that was a typo but the full name
>
>> >> should be used).
>
>> >>
>
>> >> I think if you could describe the error a little more it'd give some
>
>> >> information we could use to help diagnose.
>
>> >>
>
>> >> steven
>
>> >>
>
>> >> On Sat, Feb 6, 2016 at 3:14 PM, Z1X 
>
>> >>
>
>> >> wrote:
>
>> >> > Hello y'all,
>
>> >> >
>
>> >> > I'm trying to distribute a game which employs csound (called Zone:
>> >> > X),
>
>> >> > but
>
>> >> > before I do, I need to package Csound for deployment. I want the game
>
>> >> > to
>
>> >> > be
>
>> >> > easy to install and play, ideally it would be as simple as double
>
>> >> > clicking a
>
>> >> > .exe. You see, part of the philosophy behind my game design is that
>> >> > it
>
>> >> > should be accessible to a wide user base regardless of technical
>
>> >> > ability. I
>
>> >> > already tried adding the csound dll's to the folder, and while that
>
>> >> > gets
>
>> >> > it
>
>> >> > to open, it doesn't get Csound working. I also tried using
>
>> >> > 's
>
>> >> > system() to load the paths for OPCODE64 and OPCODE, but to no avail.
>
>> >> > Any
>
>> >> > advice about how to distribute this game would be appreciated
>> >> > greatly.
>
>> >> >
>
>> >> > Thank you,
>
>> >> > Kevin Herald
>
>> >> >
>
>> >> >
>
>> >> >
>
>> >> > --
>
>> >> > View this message in context:
>
>> >> >
>> >> > http://csound.1045644.n5.nabble.com/A-game-using-Csound-tp5746960.html
>
>> >> > Sent from the Csound - General mailing list archive at Nabble.com.
>
>> >> >
>
>> >> > Csound mailing list
>
>> >> > Csound@listserv.heanet.ie
>
>> >> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>> >> > Send bugs reports to
>
>> >> >
>
>> >> > https://github.com/csound/csound/issues
>
>> >> >
>
>> >> > Discussions of bugs and features can be posted here
>
>> >>
>
>> >> Csound mailing list
>
>> >> Csound@listserv.heanet.ie
>
>> >> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>> >> Send bugs reports to
>
>> >>
>
>> >> https://github.com/csound/csound/issues
>
>> >>
>
>> >> Discussions of bugs and features can be posted here
>
>> >
>
>> > Csound mailing list Csound@listserv.heanet.ie
>
>> > https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>
>> > https://github.com/csound/csound/issues Discussions of bugs and features
>
>> > can be posted here
>
>>
>
>> Csound mailing list
>
>> Csound@listserv.heanet.ie
>
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>
>> Send bugs reports to
>
>> https://github.com/csound/csound/issues
>
>> Discussions of bugs and features can be posted here
>
>
>
> Csound mailing list Csound@listserv.heanet.ie
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
> https://github.com/csound/csound/issues Discussions of bugs and features can
> be posted here

Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here