Hi all,

Just a quick note to say that a new version of my concatenative synthesis
software, AudioGuide, is online for download.  It is written in python but
only works on OSX at the moment.  It uses csound for rendering and outputs
many different types of files for interacting with different programs.

http://www.benhackbarth.com/audioGuide/release.html

Please sign up to the release mailing list in the above link for future
updates.  A GUI is in the works :)

Best, Ben



--
View this message in context: http://csound.1045644.n5.nabble.com/AudioGuide1-2-tp5755947.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

Dear Ben,

I see you are using pysdif. As its author, please be aware that it is 
released under the GPL. In your project there are some ircam components for 
which no source code is provided (ircamdescriptor). Could you include this 
code in the tarball?

Thanks!
Eduardo Moguillansky

On Samstag, 6. Mai 2017 19:51:28 CEST, hackbarth wrote:
> Hi all,
>
> Just a quick note to say that a new version of my concatenative synthesis
> software, AudioGuide, is online for download.  It is written in python but
> only works on OSX at the moment.  It uses csound for rendering and outputs
> many different types of files for interacting with different programs.
>
> http://www.benhackbarth.com/audioGuide/release.html
>
> Please sign up to the release mailing list in the above link for future
> updates.  A GUI is in the works :)
>
> Best, Ben
>
>
>
> --
> View this message in context: 
> http://csound.1045644.n5.nabble.com/AudioGuide1-2-tp5755947.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 Eduardo,

Thanks for your work on pysdif!  Its a great tool :)

I'm using pysdif code downloaded from pypi in 2012, which is licensed as BSD
(as is indicated both on the pypi site as well as in the code itself). 
https://pypi.python.org/pypi/pysdif/0.1.4

It seems that, at some point after 2013, the license changed to GPL but it
is difficult to for me to tell when this happened from the git repo page,
which is more recent.  I would suggest incrementing the version of your
software so that users can tell the difference between the GPL version and
the BSD version.

Best,
Ben



--
View this message in context: http://csound.1045644.n5.nabble.com/AudioGuide1-2-tp5755947p5755987.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

Hi Ben,

I'm a little late, but just wanted to say thanks very much for the
release! It's very inspiring work indeed. I'll be very curious to see
what GUI you develop for this.

All best!
steven

On Tue, May 9, 2017 at 6:47 AM, hackbarth  wrote:
> Hi Eduardo,
>
> Thanks for your work on pysdif!  Its a great tool :)
>
> I'm using pysdif code downloaded from pypi in 2012, which is licensed as BSD
> (as is indicated both on the pypi site as well as in the code itself).
> https://pypi.python.org/pypi/pysdif/0.1.4
>
> It seems that, at some point after 2013, the license changed to GPL but it
> is difficult to for me to tell when this happened from the git repo page,
> which is more recent.  I would suggest incrementing the version of your
> software so that users can tell the difference between the GPL version and
> the BSD version.
>
> Best,
> Ben
>
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/AudioGuide1-2-tp5755947p5755987.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

There is a JavaScript MIDI interface in HTML5 depending on your
browser and device. So if you use HTML5 in your app you may be able to
receive MIDI and send it on to Csound via JavaScript.

To see if your gizmo supports it go here:

https://airtightinteractive.com/demos/webmiditest/

Chrome 58 on my computer supports it, and it also appears to be
supported on my tablet, but I don't have the cable I would need to do
a real test for the tablet.

Regards,
Mike

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


On Fri, May 19, 2017 at 12:57 PM, Brian Redfern  wrote:
> Hi everyone,
> I'm working on a new app for android, while midi isn't directly supporting
> within the csd as android has no midi support at the level of the csound api
> for android, I'm wondering if I can feasibly capture midi from the java side
> and turn those into channel messages on the fly to enable midi control of my
> new android app?
> 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

I don't see any reason why you couldn't process MIDI messages and use
SetChannel to pass values over the channel bus. It's probably a good
way to go as you could use the same CSD and send values from MIDI,
OSC, or any other data source. If you have the channel pointer cached,
it would be reasonably efficient too.

On Fri, May 19, 2017 at 12:57 PM, Brian Redfern  wrote:
> Hi everyone,
> I'm working on a new app for android, while midi isn't directly supporting
> within the csd as android has no midi support at the level of the csound api
> for android, I'm wondering if I can feasibly capture midi from the java side
> and turn those into channel messages on the fly to enable midi control of my
> new android app?
> 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