On 05/01/2013 03:51 PM, James Morris wrote:
>
> The best thing you can do is file a proper bug report:
> https://github.com/jwm-art-net/Petri-Foo/issues/new
>
> Please, do it properly, and stop posting to partially related mailing
> lists about it.
>
> A bug report detailing the problem will have a much higher chance of
> getting attention than some vague recollection of some problem
> posted to some partially-related mailing list which I then have to
> trawl through the archives of to see if my recollection was right or
> not.
>
> I'll do it when I have enough time and also happen to feel like working
> on it again. Sorry.
>
I did report it via mail a few times earlier. But ok, been there, done
that: https://github.com/jwm-art-net/Petri-Foo/issues/16
On 12/24/2012 04:22 PM, James Morris wrote:
> On 15/12/12 "rosea.grammostola"<rosea.grammostola(a)gmail.com> wrote:
>> On 08/21/2012 07:30 PM, James Morris wrote:
>>> On 21/08/12 James Morris<james(a)jwm-art.net> wrote:
>>>
>>>> cd Petri-Foo
>>>> cmake . -DBuildForDebug=1
>>>> make
>>>> sudo make install
>>>>
>>>> And tell me what the debug info says. If possible
>>>> subscribe and post to petri-foo-devel.
>>>
>>> PS run non-session-manager from a terminal to see petri-foo debug
>>> info under session management.
>>
>> [Petri-Foo.nAYAH] 11:10:07.222 ERROR: failed to create dir 'samples'
>> within '/home/derick/NSM Sessions/petri/Petri-Foo.nAYAH/'
>> [nsmd] Client "Petri-Foo" replied with: OK in 7.311000ms
>> .....[nsmd] Done.
>> /nsm/server/save says Saved.
>
>
>
> Sorry for my previous response to this.
>
>
> It's quite straightforward to fix this so Petri-Foo responds with
> ERR_UNSAVED_CHANGES rather than ERR_OK.
>
> Is it acceptable for a client to bring up a dialog window to provide
> the user with detailed information about what went wrong?
Petri-foo is still not working right in NSM, o my :(
hi all -
the third release of the csound floss manual is out at
www.flossmanuals.net/csound
there is a lot of new stuff in it. see below the "what's new" in detail.
thanks goes to all contributors, and in particular to alexandre abrioux
for his diligent proof reading.
all the csd example files (nearly 250 now) and audio samples can be
downloaded here:
http://csound-tutorial.net/filebrowser/download/576
they will also be included in the next release of csoundqt.
alex hofmann will push a printed version at lulu.com in a short time.
please let us know any bugs, errata and suggestions.
enjoy -
joachim and iain
WHAT'S NEW IN THIS RELEASE
New chapters:
03E ARRAYS (Tarmo Johannes, Joachim Heintz)
04H SCANNED SYNTHESIS (Christopher Saunders)
08B CSOUND AND ARDUINO (Iain McCurdy)
12B PYTHON INSIDE CSOUND (Andrés Cabrera, Joachim Heintz)
12C PYTHON IN CSOUNDQT (Tarmo Johannes, Joachim Heintz)
Revised chapters:
02A MAKE CSOUND RUN: Updated section about Windows install (Jim
Aikin) and new sections about Csound on Android and iOS (Jacques Laplat)
03A INITIALIZATION AND PERFORMANCE PASS has completely been
rewritten (Joachim Heintz)
04A ADDITIVE SYNTHESIS has been expanded (Iain McCurdy, Bjørn
Houdorf)
05B PANNING AND SPATIALIZATION now contains descriptions about
multi-channel audio in Csound in general, and VBAP and Ambisonics in
particular (Iain McCurdy, Joachim Heintz)
10A CSOUNDQT now contains a description of the options and
choices in CsoundQt's Configure Panel (Peiman Khosravi, Joachim Heintz)
10D CABBAGE has been updated and covers now some of the
exciting new developments (Rory Walsh)
12A THE CSOUND API has been revised and extended (Francois Pinot)
The OPCODE GUIDE has been updated (Iain McCurdy)
The METHODS OF WRITING CSOUND SCORES now contain a description
of Pysco (Jacob Joaquin)
General additions and changes:
The code examples now also carry some (hopefully) meaningful
names in addition to the numbers.
Many improvements to existing examples have been made by Iain
McCurdy.
Has anyone been able to email Jeremy Jongepier recently?
I've tried to contact him via my nomal address and me sourceforge one (don't
often use that). Both of these get rejected by a spam trap :(
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.