petri-foo-devel Mailing List for Petri-Foo

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hello,

just testing petri-foo midi capabilities with qjackctl with no luck over
Ubuntu. Tried both Midi and ALSA connection without success.

Any clue?

Thank you!!

Hi Taneli,

I am interested in taking contributions but can't promise anything. I 
currently don't have time to commit to anything in-depth and I've spent 
a few years away from coding in any depth.

However, I've recently picked up one of my other projects (MDZ) which is 
also written in C, and have been picking away at it seeing what I can 
achieve while only having small pockets of free time here and there to 
work on it. So maybe in future I'll pick up Petri-Foo again - OR - maybe 
I won't.

The best thing I can suggest is you fork Petri-Foo on github, and work 
on your forked version and then make a pull-request. How long it takes 
me to get around to processing that is anyone's guess. There's already 
pull requests on there I've not processed.

I also don't recall what I was up to with some of the other branches. It 
was probably complicated... the ideas I wanted to achieve became too 
ambitious for my skills & time which was when I stopped coding almost 
altogether.

It's up to you of course, I won't begrudge you taking whichever choice 
suits your needs best :-)

James.

On 16/02/17 19:53, Kalvas, Taneli wrote:
> Dear James,
>
> I might do something independent of Petri-foo to satisfy my needs, but one option is that I modify the Petri-foo code. Are you interested in taking contributions?
>
> Taneli
>
> --
> Taneli Kalvas
> Ph.D., Researcher
> Department of Physics, room FL114
> P.O. Box 35 (YFL)
> 40014 University of Jyväskylä, Finland
> Mobile: +358-44-314-1602
> Fax:    +358-14-617-411
> Email:  tan...@jy...
> ________________________________________
> From: James Morris [ja...@jw...]
> Sent: Thursday, February 16, 2017 0:49
> To: Kalvas, Taneli; pet...@li...
> Subject: Re: [Petri-foo-devel] Pitch shifting capability
>
> Hi Taneli,
>
> Sorry, I haven't done any development on Petri-Foo for several years now
> so this is very unlikey to be implemented.
>
>
> James.
>
>
> On 15/02/17 18:34, Kalvas, Taneli wrote:
>> Hi!
>>
>> I do like Petri-Foo a lot, but for my use I would need to have a pitch shifting capability in addition to the current sample rate conversion.
>>
>> I can currently implement this by pitch shifting the sample outside Petri-Foo with the utility application that comes with the rubber band library for the key range I need, but this is quite clumsy. For a two octave range I need to set up a Petri-Foo dish with 24 patches and if I then want to change the ADSR... it becomes a nightmare.
>>
>> It would be much nicer to just have a selection in Petri-Foo on how to process the sample from note to note. Either use resampling (which changes both sample playback time and pitch) or use pitch shifting (with changed pitch, but same length). In this way inside Petri-Foo this would be only one patch and it would be controlled by a single set of parameters.
>>
>> What do you think? Could such a feature be implemented in Petri-Foo?
>>
>> Taneli
>>
>
>

Dear James,

I might do something independent of Petri-foo to satisfy my needs, but one option is that I modify the Petri-foo code. Are you interested in taking contributions?

Taneli

--
Taneli Kalvas
Ph.D., Researcher
Department of Physics, room FL114
P.O. Box 35 (YFL)
40014 University of Jyväskylä, Finland
Mobile: +358-44-314-1602
Fax:    +358-14-617-411
Email:  tan...@jy...
________________________________________
From: James Morris [ja...@jw...]
Sent: Thursday, February 16, 2017 0:49
To: Kalvas, Taneli; pet...@li...
Subject: Re: [Petri-foo-devel] Pitch shifting capability

Hi Taneli,

Sorry, I haven't done any development on Petri-Foo for several years now
so this is very unlikey to be implemented.

James.

On 15/02/17 18:34, Kalvas, Taneli wrote:
> Hi!
>
> I do like Petri-Foo a lot, but for my use I would need to have a pitch shifting capability in addition to the current sample rate conversion.
>
> I can currently implement this by pitch shifting the sample outside Petri-Foo with the utility application that comes with the rubber band library for the key range I need, but this is quite clumsy. For a two octave range I need to set up a Petri-Foo dish with 24 patches and if I then want to change the ADSR... it becomes a nightmare.
>
> It would be much nicer to just have a selection in Petri-Foo on how to process the sample from note to note. Either use resampling (which changes both sample playback time and pitch) or use pitch shifting (with changed pitch, but same length). In this way inside Petri-Foo this would be only one patch and it would be controlled by a single set of parameters.
>
> What do you think? Could such a feature be implemented in Petri-Foo?
>
> Taneli
>

Hi Taneli,

Sorry, I haven't done any development on Petri-Foo for several years now 
so this is very unlikey to be implemented.

James.

On 15/02/17 18:34, Kalvas, Taneli wrote:
> Hi!
>
> I do like Petri-Foo a lot, but for my use I would need to have a pitch shifting capability in addition to the current sample rate conversion.
>
> I can currently implement this by pitch shifting the sample outside Petri-Foo with the utility application that comes with the rubber band library for the key range I need, but this is quite clumsy. For a two octave range I need to set up a Petri-Foo dish with 24 patches and if I then want to change the ADSR... it becomes a nightmare.
>
> It would be much nicer to just have a selection in Petri-Foo on how to process the sample from note to note. Either use resampling (which changes both sample playback time and pitch) or use pitch shifting (with changed pitch, but same length). In this way inside Petri-Foo this would be only one patch and it would be controlled by a single set of parameters.
>
> What do you think? Could such a feature be implemented in Petri-Foo?
>
> Taneli
>

Hi!

I do like Petri-Foo a lot, but for my use I would need to have a pitch shifting capability in addition to the current sample rate conversion.

I can currently implement this by pitch shifting the sample outside Petri-Foo with the utility application that comes with the rubber band library for the key range I need, but this is quite clumsy. For a two octave range I need to set up a Petri-Foo dish with 24 patches and if I then want to change the ADSR... it becomes a nightmare. 

It would be much nicer to just have a selection in Petri-Foo on how to process the sample from note to note. Either use resampling (which changes both sample playback time and pitch) or use pitch shifting (with changed pitch, but same length). In this way inside Petri-Foo this would be only one patch and it would be controlled by a single set of parameters.

What do you think? Could such a feature be implemented in Petri-Foo?

Taneli

-- 
Taneli Kalvas
Ph.D., Researcher
Department of Physics, room FL114
P.O. Box 35 (YFL)
40014 University of Jyväskylä, Finland
Mobile: +358-44-314-1602
Fax:    +358-14-617-411
Email:  tan...@jy... 

In libpetrifoo/patch_private/patch_data.c

There is the following decleration:

static float    (*cc_arr)[16][CC_ARR_SIZE];

In your fork, the decleration is non-static.

Just wondered if you have any information/references about this?

Ideally we would get cmake to check the GCC version and #define 
something appropriate for us to act upon.

Cheers
James.

No I don't mind.

I've taken a different approach to what I described last night, as I 
quickly realized that approach didn't work and was far too complicated.

I'm approaching it from a features perspective now, looking at your list 
below and tackling your modifications one by one. It means all the 
commits will bear my name and won't directly reference your fork or 
commits at all, but I'll make sure you're credited in the Changelog & 
authors etc.

James.

On 14/12/15 20:27, Jean-Pierre Haenlin wrote:
> Hi,
>
> James, I have managed to make you work on Petri-Foo, I hope you don't
> mind :) Thank you anyway.
>
> I use meld too, it's a great tool. Take care that my first commits on
> Github where very messy, I was not friend with Git.
> If you need help, just ask me. Integrate what you want of my work and
> what will be missing I will reformulate it later.
>
> Perhaps must I make a documentation of the functions I have added ? Or
> is it clear for everybody ?
>
> The main modifications :
> - Ability to read loop points in the wav file
> - Make EG times longer
> - Make EG sliders logarithmic
> - Envelopes with exponential slope
> - Display sample characteristics in sample select window
> - Load last bank at startup
> - Ability to have the root note outside of the min/max notes range
>
>
> Jean-Pierre
>
>
> On 12/14/2015 12:06 AM, James Morris wrote:
>> As you know Jean-Pierre has a fork of Petri-Foo on the go with some
>> great improvements to Petri-Foo, as well as a couple of changes I'm less
>> keen on. His fork also came from a different point in history to the
>> current state of Petri-Foo which means I can't just merge his work the
>> easy way.
>>
>> The good news is I've found an approach I'm happy with for merging
>> Jean-Pierre's work into Petri-Foo that allows me to cherry pick the best
>> bits from each of his commits one by one.
>>
>> For reference, here's the procedure I'm using:
>>
>>
>> 1) install & configure meld
>> (a visual diff and merge tool http://meldmerge.org/)
>>
>> $ sudo pacman -S meld # or package manager of distro you use
>> $ git config --global merge.tool meld
>>
>>
>> 2) setup new remote and name it jph
>>
>> $ git remote add jph https://github.com/jphaenlin/Petri-Foo.git
>> $ git fetch jph
>>
>>
>> 3) create new branch called jph
>>
>> $ git branch -b jph
>>
>>
>> 4) cherry pick Jean-Pierre's first commit from the mod1 branch:
>>
>> $ git cherry-pick jph/mod1 7841331dfb714bb357c68716c178ff878a3b61fe
>>
>>
>> 5) Review changes and accept/reject them as required using meld.
>>
>> $ git mergetool
>> $ git cherry-pick --continue
>> (might need to cherry-pick a couple of times)
>>
>>
>> 6) set remote to track our new jph branch (don't confuse with jph remote)
>>
>> $ git push --set-upstream origin jph
>>
>> 7) ?
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Petri-foo-devel mailing list
>> Pet...@li...
>> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

Hi,

James, I have managed to make you work on Petri-Foo, I hope you don't 
mind :) Thank you anyway.

I use meld too, it's a great tool. Take care that my first commits on 
Github where very messy, I was not friend with Git.
If you need help, just ask me. Integrate what you want of my work and 
what will be missing I will reformulate it later.

Perhaps must I make a documentation of the functions I have added ? Or 
is it clear for everybody ?

The main modifications :
- Ability to read loop points in the wav file
- Make EG times longer
- Make EG sliders logarithmic
- Envelopes with exponential slope
- Display sample characteristics in sample select window
- Load last bank at startup
- Ability to have the root note outside of the min/max notes range

Jean-Pierre

On 12/14/2015 12:06 AM, James Morris wrote:
> As you know Jean-Pierre has a fork of Petri-Foo on the go with some
> great improvements to Petri-Foo, as well as a couple of changes I'm less
> keen on. His fork also came from a different point in history to the
> current state of Petri-Foo which means I can't just merge his work the
> easy way.
>
> The good news is I've found an approach I'm happy with for merging
> Jean-Pierre's work into Petri-Foo that allows me to cherry pick the best
> bits from each of his commits one by one.
>
> For reference, here's the procedure I'm using:
>
>
> 1) install & configure meld
> (a visual diff and merge tool http://meldmerge.org/)
>
> $ sudo pacman -S meld # or package manager of distro you use
> $ git config --global merge.tool meld
>
>
> 2) setup new remote and name it jph
>
> $ git remote add jph https://github.com/jphaenlin/Petri-Foo.git
> $ git fetch jph
>
>
> 3) create new branch called jph
>
> $ git branch -b jph
>
>
> 4) cherry pick Jean-Pierre's first commit from the mod1 branch:
>
> $ git cherry-pick jph/mod1 7841331dfb714bb357c68716c178ff878a3b61fe
>
>
> 5) Review changes and accept/reject them as required using meld.
>
> $ git mergetool
> $ git cherry-pick --continue
> (might need to cherry-pick a couple of times)
>
>
> 6) set remote to track our new jph branch (don't confuse with jph remote)
>
> $ git push --set-upstream origin jph
>
> 7) ?
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

As you know Jean-Pierre has a fork of Petri-Foo on the go with some 
great improvements to Petri-Foo, as well as a couple of changes I'm less 
keen on. His fork also came from a different point in history to the 
current state of Petri-Foo which means I can't just merge his work the 
easy way.

The good news is I've found an approach I'm happy with for merging 
Jean-Pierre's work into Petri-Foo that allows me to cherry pick the best 
bits from each of his commits one by one.

For reference, here's the procedure I'm using:

1) install & configure meld
(a visual diff and merge tool http://meldmerge.org/)

$ sudo pacman -S meld # or package manager of distro you use
$ git config --global merge.tool meld

2) setup new remote and name it jph

$ git remote add jph https://github.com/jphaenlin/Petri-Foo.git
$ git fetch jph

3) create new branch called jph

$ git branch -b jph

4) cherry pick Jean-Pierre's first commit from the mod1 branch:

$ git cherry-pick jph/mod1 7841331dfb714bb357c68716c178ff878a3b61fe

5) Review changes and accept/reject them as required using meld.

$ git mergetool
$ git cherry-pick --continue
(might need to cherry-pick a couple of times)

6) set remote to track our new jph branch (don't confuse with jph remote)

$ git push --set-upstream origin jph

7) ?

Hi,

On the subject of the load sample dialog : What I wanted is to see the 
characteristics of the samples before I load them into the sampler. That 
was the simplest way I had to do this. We need a way to see the 
characteristics when they exist and to set them for a raw sample (that I 
does not use, so that's why I don't knew it was broken).

Jean-Pierre

On 12/12/2015 09:33 PM, James Morris wrote:
> Hi Jean-Pierre,
>
> Your work on Petri-Foo looks interesting, I'll try and look through it,
> and incorporate the modifications.
>
> I'm not particularly experienced in collaborative programming either,
> and have taken similar approaches to the changes also, no worries.
>
> It's motivating to have others to collaborate with.
>
> I've noticed in your fork the sample load dialog always has the options
> for raw data on show which I found confusing. In my version the raw data
> options are only available when the raw data check box is ticked - I
> prefer that.
>
> Anyway, raw data loading is broken in Petri-Foo itself, see issue #35:
> https://github.com/jwm-art-net/Petri-Foo/issues/35
>
> Cheers,
> James.
>
>
>
> On 12/12/15 10:48, Jean-Pierre Haenlin wrote:
>> Hi,
>>
>> I have made some modifications to PF on a Github fork.
>> I'm afraid that I don't have followed the best procedure to do that. I
>> should have send to James each evolution one after the other. But I'm
>> not an expert at "collaborative programming".
>> Now, Olivier is asking me how he can do to insert my version of PF in
>> the Linux distribution he wants to make. I don't know how I can help
>> him. I think James can incorporate in PF my modifications when he wants,
>> and in the meantime, everybody can use my version since it is freely
>> downloadable. How do you see the best way to evolve for PF.
>>
>> Jean-Pierre
>>
>> (https://github.com/jphaenlin/Petri-Foo)
>>
>>
>> On 12/07/2015 10:56 PM, tr...@tu... wrote:
>>> Hi James and thank you for your answer.
>>>
>>> The time/dedication factor is totally understandable and am thankfull
>>> for you saying it honestly.
>>>
>>> Would you be happy with someone taking on his/her behalf Petri Foo's
>>> maintenance ?
>>> Not promising anything at all here since I'm not able to do it myself
>>> (not being a coder), but I might find someone for that.
>>> ... we never know :)
>>>
>>> All the best,
>>> Olivier
>>>
>>>
>>>
>>> Le 2015-12-03 23:20, James Morris a écrit :
>>>> Hi Oliver,
>>>>
>>>> Thank you, it's nice to hear your appreciation.
>>>>
>>>> Currently at this point in time I do not have any plans to code on
>>>> Petri-Foo. As I mentioned on github, I'm not involved in coding anymore
>>>> (it was only ever a hobby of mine), but I also don't have the time to
>>>> get back into coding deeply enough to work on Petri-Foo.
>>>>
>>>> Unfortunately these things require a lot of dedication and commitment
>>>> which I just don't have anymore.
>>>>
>>>> Regarding the name, Petri-Foo is named after the Petri Dish as used by
>>>> science labs to hold samples - which is why the file extension for the
>>>> files Petri-Foo saves is *.dish. There's also the reference to
>>>> petrification, the paralyzation of audio, audio being turned to stone,
>>>> static, as in the case of a sample continually looping, unchanging. The
>>>> Foo part is just a common suffix, a placeholder, something unknown -
>>>> that could be anything.
>>>>
>>>> Cheers,
>>>> James.
>>>>
>>>>
>>>>
>>>>
>>>> On 03/12/15 00:57, tr...@tu... wrote:
>>>>> Hi all,
>>>>>
>>>>> I recently dived into petri-foo and I've got to say that I had a lot
>>>>> of
>>>>> fun with it so far. And my 5 years old niece had the same this
>>>>> afternoon
>>>>> when I sampled her voice, mine, my mother's one (who is her grand
>>>>> mother
>>>>> as well :) ) and my sister. Then we played all together on a 4 octaves
>>>>> keyboard and had laughs for almost 1 hour. Thanks to all the devs and
>>>>> testers and users of Petri-Foo (and Specimen of course) for bringing
>>>>> that afternoon to us :)
>>>>>
>>>>>
>>>>> On the last days, I've been searching for information, specifically on
>>>>> the non obvious functionnalities. That leads me to read at:
>>>>> - all the archives from the specimen mailing list
>>>>> - all the archives from this mailing list
>>>>> - the old Specimen manual (which is still usefull in some ways)
>>>>> - sourceforge bugtracker (pretty easy, only 15 bugs)
>>>>> - github issue tracker and pull request (both "closed" and "still
>>>>> active")
>>>>>
>>>>> I did enjoyed this motivation to bring some more new [feature request]
>>>>> and to had my voice to one other. And to make a really small
>>>>> contribution (see my pull request on github).
>>>>>
>>>>> Then James answered
>>>>> [https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417]
>>>>> and I'd like to ask you James if that answer is more of a "I've got no
>>>>> time to work on it now" kind of, as I saw (reading at the ML archives)
>>>>> that you've had some periods working on Petri-Foo and other without in
>>>>> the past, or if it's more like a "I'm not planning to work on
>>>>> petri-foo
>>>>> anymore at this point".
>>>>
>>>>
>>>>>
>>>>> I'm a bit interested about it.
>>>>>
>>>>> Anyway, thanks again for Petri-Foo.
>>>>> Cheers
>>>>> Olivier
>>>>>
>>>>> Oh yes, and I didn't read nothing about why you choose the name
>>>>> "petri-foo". It might be something really obvious because i didn't see
>>>>> this question asked, but if it's something relative to the another
>>>>> culture than mine so, I'm better to ask for that question here !
>>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Go from Idea to Many App Stores Faster with Intel(R) XDK
>>> Give your users amazing mobile app experiences with Intel(R) XDK.
>>> Use one codebase in this all-in-one HTML5 development environment.
>>> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
>>> _______________________________________________
>>> Petri-foo-devel mailing list
>>> Pet...@li...
>>> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Petri-foo-devel mailing list
>> Pet...@li...
>> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

Hello again,

Ok I've made a few comments on your commits on github, mainly regarding 
deleted files - hope you don't think I'm on the attack!

I think the best way forward is if you make a pull request, where any 
issues with changes can be resolved so we can get your work into Petri-Foo.

There's maybe a few other contributions floating around, I have a 
feeling some of the work Thomas did with Coverity may have got lost 
after I demanded white space be re-formatted to use spaces instead of tab.

Thanks all.

James.

On 12/12/15 22:33, James Morris wrote:
> Hi Jean-Pierre,
>
> Some nice work there, the exponential envelope and logarithmic sliders
> are great.
>
> The only thing I have issue with is what you've tried to do with the
> sample load dialog - I don't think it is the best approach.
>
> I much prefer the raw data options to remain hidden until the user
> wishes to load a raw sample, it's less cluttered. Using these options to
> display the currently selected sample is confusing and unexpected, at
> least in my mind.
>
> It would make more sense to have a seperate area for displaying the
> sample data format.
>
> So that is the only thing I'd like to see changed about what you've done.
>
> Incidentally, I've found the cause of Petri-Foo failing to load raw
> data, it was #ifdef'd out in libpetrifoo/sample.c for some unfathomable
> reason.
>
>
> Best regards,
> James.
>
>
> On 12/12/15 20:33, James Morris wrote:
>> Hi Jean-Pierre,
>>
>> Your work on Petri-Foo looks interesting, I'll try and look through it,
>> and incorporate the modifications.
>>
>> I'm not particularly experienced in collaborative programming either,
>> and have taken similar approaches to the changes also, no worries.
>>
>> It's motivating to have others to collaborate with.
>>
>> I've noticed in your fork the sample load dialog always has the options
>> for raw data on show which I found confusing. In my version the raw data
>> options are only available when the raw data check box is ticked - I
>> prefer that.
>>
>> Anyway, raw data loading is broken in Petri-Foo itself, see issue #35:
>> https://github.com/jwm-art-net/Petri-Foo/issues/35
>>
>> Cheers,
>> James.
>>
>>
>>
>> On 12/12/15 10:48, Jean-Pierre Haenlin wrote:
>>> Hi,
>>>
>>> I have made some modifications to PF on a Github fork.
>>> I'm afraid that I don't have followed the best procedure to do that. I
>>> should have send to James each evolution one after the other. But I'm
>>> not an expert at "collaborative programming".
>>> Now, Olivier is asking me how he can do to insert my version of PF in
>>> the Linux distribution he wants to make. I don't know how I can help
>>> him. I think James can incorporate in PF my modifications when he wants,
>>> and in the meantime, everybody can use my version since it is freely
>>> downloadable. How do you see the best way to evolve for PF.
>>>
>>> Jean-Pierre
>>>
>>> (https://github.com/jphaenlin/Petri-Foo)
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

Hi Jean-Pierre,

Some nice work there, the exponential envelope and logarithmic sliders 
are great.

The only thing I have issue with is what you've tried to do with the 
sample load dialog - I don't think it is the best approach.

I much prefer the raw data options to remain hidden until the user 
wishes to load a raw sample, it's less cluttered. Using these options to 
display the currently selected sample is confusing and unexpected, at 
least in my mind.

It would make more sense to have a seperate area for displaying the 
sample data format.

So that is the only thing I'd like to see changed about what you've done.

Incidentally, I've found the cause of Petri-Foo failing to load raw 
data, it was #ifdef'd out in libpetrifoo/sample.c for some unfathomable 
reason.

Best regards,
James.

On 12/12/15 20:33, James Morris wrote:
> Hi Jean-Pierre,
>
> Your work on Petri-Foo looks interesting, I'll try and look through it,
> and incorporate the modifications.
>
> I'm not particularly experienced in collaborative programming either,
> and have taken similar approaches to the changes also, no worries.
>
> It's motivating to have others to collaborate with.
>
> I've noticed in your fork the sample load dialog always has the options
> for raw data on show which I found confusing. In my version the raw data
> options are only available when the raw data check box is ticked - I
> prefer that.
>
> Anyway, raw data loading is broken in Petri-Foo itself, see issue #35:
> https://github.com/jwm-art-net/Petri-Foo/issues/35
>
> Cheers,
> James.
>
>
>
> On 12/12/15 10:48, Jean-Pierre Haenlin wrote:
>> Hi,
>>
>> I have made some modifications to PF on a Github fork.
>> I'm afraid that I don't have followed the best procedure to do that. I
>> should have send to James each evolution one after the other. But I'm
>> not an expert at "collaborative programming".
>> Now, Olivier is asking me how he can do to insert my version of PF in
>> the Linux distribution he wants to make. I don't know how I can help
>> him. I think James can incorporate in PF my modifications when he wants,
>> and in the meantime, everybody can use my version since it is freely
>> downloadable. How do you see the best way to evolve for PF.
>>
>> Jean-Pierre
>>
>> (https://github.com/jphaenlin/Petri-Foo)

Hi Jean-Pierre,

Your work on Petri-Foo looks interesting, I'll try and look through it, 
and incorporate the modifications.

I'm not particularly experienced in collaborative programming either, 
and have taken similar approaches to the changes also, no worries.

It's motivating to have others to collaborate with.

I've noticed in your fork the sample load dialog always has the options 
for raw data on show which I found confusing. In my version the raw data 
options are only available when the raw data check box is ticked - I 
prefer that.

Anyway, raw data loading is broken in Petri-Foo itself, see issue #35:
https://github.com/jwm-art-net/Petri-Foo/issues/35

Cheers,
James.

On 12/12/15 10:48, Jean-Pierre Haenlin wrote:
> Hi,
>
> I have made some modifications to PF on a Github fork.
> I'm afraid that I don't have followed the best procedure to do that. I
> should have send to James each evolution one after the other. But I'm
> not an expert at "collaborative programming".
> Now, Olivier is asking me how he can do to insert my version of PF in
> the Linux distribution he wants to make. I don't know how I can help
> him. I think James can incorporate in PF my modifications when he wants,
> and in the meantime, everybody can use my version since it is freely
> downloadable. How do you see the best way to evolve for PF.
>
> Jean-Pierre
>
> (https://github.com/jphaenlin/Petri-Foo)
>
>
> On 12/07/2015 10:56 PM, tr...@tu... wrote:
>> Hi James and thank you for your answer.
>>
>> The time/dedication factor is totally understandable and am thankfull
>> for you saying it honestly.
>>
>> Would you be happy with someone taking on his/her behalf Petri Foo's
>> maintenance ?
>> Not promising anything at all here since I'm not able to do it myself
>> (not being a coder), but I might find someone for that.
>> ... we never know :)
>>
>> All the best,
>> Olivier
>>
>>
>>
>> Le 2015-12-03 23:20, James Morris a écrit :
>>> Hi Oliver,
>>>
>>> Thank you, it's nice to hear your appreciation.
>>>
>>> Currently at this point in time I do not have any plans to code on
>>> Petri-Foo. As I mentioned on github, I'm not involved in coding anymore
>>> (it was only ever a hobby of mine), but I also don't have the time to
>>> get back into coding deeply enough to work on Petri-Foo.
>>>
>>> Unfortunately these things require a lot of dedication and commitment
>>> which I just don't have anymore.
>>>
>>> Regarding the name, Petri-Foo is named after the Petri Dish as used by
>>> science labs to hold samples - which is why the file extension for the
>>> files Petri-Foo saves is *.dish. There's also the reference to
>>> petrification, the paralyzation of audio, audio being turned to stone,
>>> static, as in the case of a sample continually looping, unchanging. The
>>> Foo part is just a common suffix, a placeholder, something unknown -
>>> that could be anything.
>>>
>>> Cheers,
>>> James.
>>>
>>>
>>>
>>>
>>> On 03/12/15 00:57, tr...@tu... wrote:
>>>> Hi all,
>>>>
>>>> I recently dived into petri-foo and I've got to say that I had a lot
>>>> of
>>>> fun with it so far. And my 5 years old niece had the same this
>>>> afternoon
>>>> when I sampled her voice, mine, my mother's one (who is her grand
>>>> mother
>>>> as well :) ) and my sister. Then we played all together on a 4 octaves
>>>> keyboard and had laughs for almost 1 hour. Thanks to all the devs and
>>>> testers and users of Petri-Foo (and Specimen of course) for bringing
>>>> that afternoon to us :)
>>>>
>>>>
>>>> On the last days, I've been searching for information, specifically on
>>>> the non obvious functionnalities. That leads me to read at:
>>>> - all the archives from the specimen mailing list
>>>> - all the archives from this mailing list
>>>> - the old Specimen manual (which is still usefull in some ways)
>>>> - sourceforge bugtracker (pretty easy, only 15 bugs)
>>>> - github issue tracker and pull request (both "closed" and "still
>>>> active")
>>>>
>>>> I did enjoyed this motivation to bring some more new [feature request]
>>>> and to had my voice to one other. And to make a really small
>>>> contribution (see my pull request on github).
>>>>
>>>> Then James answered
>>>> [https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417]
>>>> and I'd like to ask you James if that answer is more of a "I've got no
>>>> time to work on it now" kind of, as I saw (reading at the ML archives)
>>>> that you've had some periods working on Petri-Foo and other without in
>>>> the past, or if it's more like a "I'm not planning to work on
>>>> petri-foo
>>>> anymore at this point".
>>>
>>>
>>>>
>>>> I'm a bit interested about it.
>>>>
>>>> Anyway, thanks again for Petri-Foo.
>>>> Cheers
>>>> Olivier
>>>>
>>>> Oh yes, and I didn't read nothing about why you choose the name
>>>> "petri-foo". It might be something really obvious because i didn't see
>>>> this question asked, but if it's something relative to the another
>>>> culture than mine so, I'm better to ask for that question here !
>>>>
>>
>> ------------------------------------------------------------------------------
>> Go from Idea to Many App Stores Faster with Intel(R) XDK
>> Give your users amazing mobile app experiences with Intel(R) XDK.
>> Use one codebase in this all-in-one HTML5 development environment.
>> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
>> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
>> _______________________________________________
>> Petri-foo-devel mailing list
>> Pet...@li...
>> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

Hi,

I have made some modifications to PF on a Github fork.
I'm afraid that I don't have followed the best procedure to do that. I 
should have send to James each evolution one after the other. But I'm 
not an expert at "collaborative programming".
Now, Olivier is asking me how he can do to insert my version of PF in 
the Linux distribution he wants to make. I don't know how I can help 
him. I think James can incorporate in PF my modifications when he wants, 
and in the meantime, everybody can use my version since it is freely 
downloadable. How do you see the best way to evolve for PF.

Jean-Pierre

(https://github.com/jphaenlin/Petri-Foo)

On 12/07/2015 10:56 PM, tr...@tu... wrote:
> Hi James and thank you for your answer.
>
> The time/dedication factor is totally understandable and am thankfull
> for you saying it honestly.
>
> Would you be happy with someone taking on his/her behalf Petri Foo's
> maintenance ?
> Not promising anything at all here since I'm not able to do it myself
> (not being a coder), but I might find someone for that.
> ... we never know :)
>
> All the best,
> Olivier
>
>
>
> Le 2015-12-03 23:20, James Morris a écrit :
>> Hi Oliver,
>>
>> Thank you, it's nice to hear your appreciation.
>>
>> Currently at this point in time I do not have any plans to code on
>> Petri-Foo. As I mentioned on github, I'm not involved in coding anymore
>> (it was only ever a hobby of mine), but I also don't have the time to
>> get back into coding deeply enough to work on Petri-Foo.
>>
>> Unfortunately these things require a lot of dedication and commitment
>> which I just don't have anymore.
>>
>> Regarding the name, Petri-Foo is named after the Petri Dish as used by
>> science labs to hold samples - which is why the file extension for the
>> files Petri-Foo saves is *.dish. There's also the reference to
>> petrification, the paralyzation of audio, audio being turned to stone,
>> static, as in the case of a sample continually looping, unchanging. The
>> Foo part is just a common suffix, a placeholder, something unknown -
>> that could be anything.
>>
>> Cheers,
>> James.
>>
>>
>>
>>
>> On 03/12/15 00:57, tr...@tu... wrote:
>>> Hi all,
>>>
>>> I recently dived into petri-foo and I've got to say that I had a lot
>>> of
>>> fun with it so far. And my 5 years old niece had the same this
>>> afternoon
>>> when I sampled her voice, mine, my mother's one (who is her grand
>>> mother
>>> as well :) ) and my sister. Then we played all together on a 4 octaves
>>> keyboard and had laughs for almost 1 hour. Thanks to all the devs and
>>> testers and users of Petri-Foo (and Specimen of course) for bringing
>>> that afternoon to us :)
>>>
>>>
>>> On the last days, I've been searching for information, specifically on
>>> the non obvious functionnalities. That leads me to read at:
>>> - all the archives from the specimen mailing list
>>> - all the archives from this mailing list
>>> - the old Specimen manual (which is still usefull in some ways)
>>> - sourceforge bugtracker (pretty easy, only 15 bugs)
>>> - github issue tracker and pull request (both "closed" and "still
>>> active")
>>>
>>> I did enjoyed this motivation to bring some more new [feature request]
>>> and to had my voice to one other. And to make a really small
>>> contribution (see my pull request on github).
>>>
>>> Then James answered
>>> [https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417]
>>> and I'd like to ask you James if that answer is more of a "I've got no
>>> time to work on it now" kind of, as I saw (reading at the ML archives)
>>> that you've had some periods working on Petri-Foo and other without in
>>> the past, or if it's more like a "I'm not planning to work on
>>> petri-foo
>>> anymore at this point".
>>
>>
>>>
>>> I'm a bit interested about it.
>>>
>>> Anyway, thanks again for Petri-Foo.
>>> Cheers
>>> Olivier
>>>
>>> Oh yes, and I didn't read nothing about why you choose the name
>>> "petri-foo". It might be something really obvious because i didn't see
>>> this question asked, but if it's something relative to the another
>>> culture than mine so, I'm better to ask for that question here !
>>>
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

Of course, it's free open source software, anyone is welcome to modify 
and redistribute.

On 07/12/15 21:56, tr...@tu... wrote:
> Hi James and thank you for your answer.
>
> The time/dedication factor is totally understandable and am thankfull
> for you saying it honestly.
>
> Would you be happy with someone taking on his/her behalf Petri Foo's
> maintenance ?
> Not promising anything at all here since I'm not able to do it myself
> (not being a coder), but I might find someone for that.
> ... we never know :)
>
> All the best,
> Olivier
>
>
>
> Le 2015-12-03 23:20, James Morris a écrit :
>> Hi Oliver,
>>
>> Thank you, it's nice to hear your appreciation.
>>
>> Currently at this point in time I do not have any plans to code on
>> Petri-Foo. As I mentioned on github, I'm not involved in coding anymore
>> (it was only ever a hobby of mine), but I also don't have the time to
>> get back into coding deeply enough to work on Petri-Foo.
>>
>> Unfortunately these things require a lot of dedication and commitment
>> which I just don't have anymore.
>>
>> Regarding the name, Petri-Foo is named after the Petri Dish as used by
>> science labs to hold samples - which is why the file extension for the
>> files Petri-Foo saves is *.dish. There's also the reference to
>> petrification, the paralyzation of audio, audio being turned to stone,
>> static, as in the case of a sample continually looping, unchanging. The
>> Foo part is just a common suffix, a placeholder, something unknown -
>> that could be anything.
>>
>> Cheers,
>> James.
>>
>>
>>
>>
>> On 03/12/15 00:57, tr...@tu... wrote:
>>> Hi all,
>>>
>>> I recently dived into petri-foo and I've got to say that I had a lot of
>>> fun with it so far. And my 5 years old niece had the same this afternoon
>>> when I sampled her voice, mine, my mother's one (who is her grand mother
>>> as well :) ) and my sister. Then we played all together on a 4 octaves
>>> keyboard and had laughs for almost 1 hour. Thanks to all the devs and
>>> testers and users of Petri-Foo (and Specimen of course) for bringing
>>> that afternoon to us :)
>>>
>>>
>>> On the last days, I've been searching for information, specifically on
>>> the non obvious functionnalities. That leads me to read at:
>>> - all the archives from the specimen mailing list
>>> - all the archives from this mailing list
>>> - the old Specimen manual (which is still usefull in some ways)
>>> - sourceforge bugtracker (pretty easy, only 15 bugs)
>>> - github issue tracker and pull request (both "closed" and "still
>>> active")
>>>
>>> I did enjoyed this motivation to bring some more new [feature request]
>>> and to had my voice to one other. And to make a really small
>>> contribution (see my pull request on github).
>>>
>>> Then James answered
>>> [https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417]
>>>
>>> and I'd like to ask you James if that answer is more of a "I've got no
>>> time to work on it now" kind of, as I saw (reading at the ML archives)
>>> that you've had some periods working on Petri-Foo and other without in
>>> the past, or if it's more like a "I'm not planning to work on petri-foo
>>> anymore at this point".
>>
>>
>>>
>>> I'm a bit interested about it.
>>>
>>> Anyway, thanks again for Petri-Foo.
>>> Cheers
>>> Olivier
>>>
>>> Oh yes, and I didn't read nothing about why you choose the name
>>> "petri-foo". It might be something really obvious because i didn't see
>>> this question asked, but if it's something relative to the another
>>> culture than mine so, I'm better to ask for that question here !
>>>
>

I second that! :)  

Imo, Petri-Foo is a very nice sampler and it
certainly merits continued maintenance/development. I am not a coder
either, but would be happy to "support" someone willing to give it a bit
of attention every now and then! 

brian 

On Mon, 07 Dec 2015 22:56:56
+0100, tr...@tu... wrote: 

> Hi James and thank you for your
answer.
> 
> The time/dedication factor is totally understandable and am
thankfull 
> for you saying it honestly.
> 
> Would you be happy with
someone taking on his/her behalf Petri Foo's 
> maintenance ?
> Not
promising anything at all here since I'm not able to do it myself 
>
(not being a coder), but I might find someone for that.
> ... we never
know :)
> 
> All the best,
> Olivier
> 
> Le 2015-12-03 23:20, James
Morris a écrit :
> 
>> Hi Oliver, Thank you, it's nice to hear your
appreciation. Currently at this point in time I do not have any plans to
code on Petri-Foo. As I mentioned on github, I'm not involved in coding
anymore (it was only ever a hobby of mine), but I also don't have the
time to get back into coding deeply enough to work on Petri-Foo.
Unfortunately these things require a lot of dedication and commitment
which I just don't have anymore. Regarding the name, Petri-Foo is named
after the Petri Dish as used by science labs to hold samples - which is
why the file extension for the files Petri-Foo saves is *.dish. There's
also the reference to petrification, the paralyzation of audio, audio
being turned to stone, static, as in the case of a sample continually
looping, unchanging. The Foo part is just a common suffix, a
placeholder, something unknown - that could be anything. Cheers, James.
On 03/12/15 00:57, tr...@tu... [2]wrote: 
>> 
>>> Hi all, I
recently dived into petri-foo and I've got to say that I had a lot of
fun with it so far. And my 5 years old niece had the same this afternoon
when I sampled her voice, mine, my mother's one (who is her grand mother
as well :) ) and my sister. Then we played all together on a 4 octaves
keyboard and had laughs for almost 1 hour. Thanks to all the devs and
testers and users of Petri-Foo (and Specimen of course) for bringing
that afternoon to us :) On the last days, I've been searching for
information, specifically on the non obvious functionnalities. That
leads me to read at: - all the archives from the specimen mailing list -
all the archives from this mailing list - the old Specimen manual (which
is still usefull in some ways) - sourceforge bugtracker (pretty easy,
only 15 bugs) - github issue tracker and pull request (both "closed" and
"still active") I did enjoyed this motivation to bring some more new
[feature request] and to had my voice to one other. And to make a really
small contribution (see my pull request on github). Then James answered
[https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417
[1]] and I'd like to ask you James if that answer is more of a "I've
got no time to work on it now" kind of, as I saw (reading at the ML
archives) that you've had some periods working on Petri-Foo and other
without in the past, or if it's more like a "I'm not planning to work on
petri-foo anymore at this point".
>> 
>>> I'm a bit interested about it.
Anyway, thanks again for Petri-Foo. Cheers Olivier Oh yes, and I didn't
read nothing about why you choose the name "petri-foo". It might be
something really obvious because i didn't see this question asked, but
if it's something relative to the another culture than mine so, I'm
better to ask for that question here !
> 
>
------------------------------------------------------------------------------
>
Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your
users amazing mobile app experiences with Intel(R) XDK.
> Use one
codebase in this all-in-one HTML5 development environment.
> Design,
debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
>
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140 [3]
>
_______________________________________________
> Petri-foo-devel
mailing list
> Pet...@li... [4]
>
https://lists.sourceforge.net/lists/listinfo/petri-foo-devel [5]

Links:
------
[1]
https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417
[2]
mailto:tr...@tu...
[3]
http://pubads.g.doubleclick.net/gampad/clk?id=254741911|+|amp|+|iu=/4140
[4]
mailto:Pet...@li...
[5]
https://lists.sourceforge.net/lists/listinfo/petri-foo-devel

Hi James and thank you for your answer.

The time/dedication factor is totally understandable and am thankfull 
for you saying it honestly.

Would you be happy with someone taking on his/her behalf Petri Foo's 
maintenance ?
Not promising anything at all here since I'm not able to do it myself 
(not being a coder), but I might find someone for that.
... we never know :)

All the best,
Olivier

Le 2015-12-03 23:20, James Morris a écrit :
> Hi Oliver,
> 
> Thank you, it's nice to hear your appreciation.
> 
> Currently at this point in time I do not have any plans to code on
> Petri-Foo. As I mentioned on github, I'm not involved in coding anymore
> (it was only ever a hobby of mine), but I also don't have the time to
> get back into coding deeply enough to work on Petri-Foo.
> 
> Unfortunately these things require a lot of dedication and commitment
> which I just don't have anymore.
> 
> Regarding the name, Petri-Foo is named after the Petri Dish as used by
> science labs to hold samples - which is why the file extension for the
> files Petri-Foo saves is *.dish. There's also the reference to
> petrification, the paralyzation of audio, audio being turned to stone,
> static, as in the case of a sample continually looping, unchanging. The
> Foo part is just a common suffix, a placeholder, something unknown -
> that could be anything.
> 
> Cheers,
> James.
> 
> 
> 
> 
> On 03/12/15 00:57, tr...@tu... wrote:
>> Hi all,
>> 
>> I recently dived into petri-foo and I've got to say that I had a lot 
>> of
>> fun with it so far. And my 5 years old niece had the same this 
>> afternoon
>> when I sampled her voice, mine, my mother's one (who is her grand 
>> mother
>> as well :) ) and my sister. Then we played all together on a 4 octaves
>> keyboard and had laughs for almost 1 hour. Thanks to all the devs and
>> testers and users of Petri-Foo (and Specimen of course) for bringing
>> that afternoon to us :)
>> 
>> 
>> On the last days, I've been searching for information, specifically on
>> the non obvious functionnalities. That leads me to read at:
>> - all the archives from the specimen mailing list
>> - all the archives from this mailing list
>> - the old Specimen manual (which is still usefull in some ways)
>> - sourceforge bugtracker (pretty easy, only 15 bugs)
>> - github issue tracker and pull request (both "closed" and "still
>> active")
>> 
>> I did enjoyed this motivation to bring some more new [feature request]
>> and to had my voice to one other. And to make a really small
>> contribution (see my pull request on github).
>> 
>> Then James answered
>> [https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417]
>> and I'd like to ask you James if that answer is more of a "I've got no
>> time to work on it now" kind of, as I saw (reading at the ML archives)
>> that you've had some periods working on Petri-Foo and other without in
>> the past, or if it's more like a "I'm not planning to work on 
>> petri-foo
>> anymore at this point".
> 
> 
>> 
>> I'm a bit interested about it.
>> 
>> Anyway, thanks again for Petri-Foo.
>> Cheers
>> Olivier
>> 
>> Oh yes, and I didn't read nothing about why you choose the name
>> "petri-foo". It might be something really obvious because i didn't see
>> this question asked, but if it's something relative to the another
>> culture than mine so, I'm better to ask for that question here !
>> 

Hi Oliver,

Thank you, it's nice to hear your appreciation.

Currently at this point in time I do not have any plans to code on 
Petri-Foo. As I mentioned on github, I'm not involved in coding anymore 
(it was only ever a hobby of mine), but I also don't have the time to 
get back into coding deeply enough to work on Petri-Foo.

Unfortunately these things require a lot of dedication and commitment 
which I just don't have anymore.

Regarding the name, Petri-Foo is named after the Petri Dish as used by 
science labs to hold samples - which is why the file extension for the 
files Petri-Foo saves is *.dish. There's also the reference to 
petrification, the paralyzation of audio, audio being turned to stone, 
static, as in the case of a sample continually looping, unchanging. The 
Foo part is just a common suffix, a placeholder, something unknown - 
that could be anything.

Cheers,
James.

On 03/12/15 00:57, tr...@tu... wrote:
> Hi all,
>
> I recently dived into petri-foo and I've got to say that I had a lot of
> fun with it so far. And my 5 years old niece had the same this afternoon
> when I sampled her voice, mine, my mother's one (who is her grand mother
> as well :) ) and my sister. Then we played all together on a 4 octaves
> keyboard and had laughs for almost 1 hour. Thanks to all the devs and
> testers and users of Petri-Foo (and Specimen of course) for bringing
> that afternoon to us :)
>
>
> On the last days, I've been searching for information, specifically on
> the non obvious functionnalities. That leads me to read at:
> - all the archives from the specimen mailing list
> - all the archives from this mailing list
> - the old Specimen manual (which is still usefull in some ways)
> - sourceforge bugtracker (pretty easy, only 15 bugs)
> - github issue tracker and pull request (both "closed" and "still
> active")
>
> I did enjoyed this motivation to bring some more new [feature request]
> and to had my voice to one other. And to make a really small
> contribution (see my pull request on github).
>
> Then James answered
> [https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417]
> and I'd like to ask you James if that answer is more of a "I've got no
> time to work on it now" kind of, as I saw (reading at the ML archives)
> that you've had some periods working on Petri-Foo and other without in
> the past, or if it's more like a "I'm not planning to work on petri-foo
> anymore at this point".

>
> I'm a bit interested about it.
>
> Anyway, thanks again for Petri-Foo.
> Cheers
> Olivier
>
> Oh yes, and I didn't read nothing about why you choose the name
> "petri-foo". It might be something really obvious because i didn't see
> this question asked, but if it's something relative to the another
> culture than mine so, I'm better to ask for that question here !
>
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
> _______________________________________________
> Petri-foo-devel mailing list
> Pet...@li...
> https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
>

Hi all,

I recently dived into petri-foo and I've got to say that I had a lot of 
fun with it so far. And my 5 years old niece had the same this afternoon 
when I sampled her voice, mine, my mother's one (who is her grand mother 
as well :) ) and my sister. Then we played all together on a 4 octaves 
keyboard and had laughs for almost 1 hour. Thanks to all the devs and 
testers and users of Petri-Foo (and Specimen of course) for bringing 
that afternoon to us :)

On the last days, I've been searching for information, specifically on 
the non obvious functionnalities. That leads me to read at:
- all the archives from the specimen mailing list
- all the archives from this mailing list
- the old Specimen manual (which is still usefull in some ways)
- sourceforge bugtracker (pretty easy, only 15 bugs)
- github issue tracker and pull request (both "closed" and "still 
active")

I did enjoyed this motivation to bring some more new [feature request] 
and to had my voice to one other. And to make a really small 
contribution (see my pull request on github).

Then James answered 
[https://github.com/jwm-art-net/Petri-Foo/issues/14#issuecomment-161447417] 
and I'd like to ask you James if that answer is more of a "I've got no 
time to work on it now" kind of, as I saw (reading at the ML archives) 
that you've had some periods working on Petri-Foo and other without in 
the past, or if it's more like a "I'm not planning to work on petri-foo 
anymore at this point".

I'm a bit interested about it.

Anyway, thanks again for Petri-Foo.
Cheers
Olivier

Oh yes, and I didn't read nothing about why you choose the name 
"petri-foo". It might be something really obvious because i didn't see 
this question asked, but if it's something relative to the another 
culture than mine so, I'm better to ask for that question here !

Hello,

I have uploaded petri-foo to coverity. If you want to help fixing the bugs found by static analysis, or just want to have a look at the defects, I will add you to the project, no questions asked.

https://scan.coverity.com/projects/4600

Thanks,
Thomas

On Thu, 10 Jul 2014 17:11:58 +0200
br...@am... wrote:

>   
> 
> Hello everyone, 
> 
> I'm really enjoying Petri-Foo, it's truly a
> powerful application (I especially like being able to layer samples so
> easily!). 

Thankyou...

> 
> I was wondering if there is a manual available? There are
> some things that aren't clear to me (such as the various functions in
> the sample edit window). 

No, no manual.

> 
> Any help much appreciated! (I'd also like to
> help with testing the git version.. Where can I find it? Will it
> replace my current version (KXStudio) or can I use both versions?) 
> 
> brian 
>   

I can't remember where development got to on the git version.

I don't have time nor inclination right now.

James.

Hello everyone, 

I'm really enjoying Petri-Foo, it's truly a
powerful application (I especially like being able to layer samples so
easily!). 

I was wondering if there is a manual available? There are
some things that aren't clear to me (such as the various functions in
the sample edit window). 

Any help much appreciated! (I'd also like to
help with testing the git version.. Where can I find it? Will it replace
my current version (KXStudio) or can I use both versions?) 

brian 

Hi Alberto,

On Mon, 9 Jun 2014 12:04:42 +0200
Alberto <alb...@gm...> wrote:

> Sorry, but my English is not good.
> 
> Two questions on your application:
> 
> - How do you change the base note to trigger the sample? Defaults to
> C5 but I need to change it. I've tried many ways and I do not see how.

Use the middle button on a three button mouse.

> - Could you add more notes on the same midi channel to create
> keyboard maps? for example, sample 1 in F5, A5 sample 2, sample 3 in
> C6, etc ... If possible, how is it done?

No it isn't possible in Petri-Foo and it is highly unlikely Petri-Foo
will ever have that functionality - it isn't designed for that and would not be trivial to bolt on.

> 
> I can not find documentation on PETRI-FOO. You could work on your
> project by performing a manual in Spanish on its implementation.
> In English I can not do it, xD;

Sorry I don't speak Spanish! 

> 
> PETRI-FOO I need for my live concerts.
> 
> Application is quick, is perfect for triggering samples and effects in
> live performance.
> Works great!

Glad you like it. Unfortunately I have not been in a position to
maintain/develop it for some time so you would probably be advised to
look at the alternatives (some of which I think may have the
functionality you request).

> Thank you very much for your help.
> Alberto Bringas

Best regards,
James.

> ________________________________________________
> http://www.albertobringas.es
> alb...@gm...

*reggae-dancehall radio show on ALIGRE FM PARIS 93.1 www.dancehallecho.net
<http://www.dancehallecho.net>*
*http://facebook.com/dancehallecho* <http://facebook.com/dancehallecho>

Hi All,

I have filed issues on github regarding all recent issues discussed
here.

https://github.com/jwm-art-net/Petri-Foo/issues?state=open

I will get round to resolving them when I get round to it.

All welcome to speed things up.

James.

2011	Jan	Feb (75)	Mar (17)	Apr (34)	May (8)	Jun (50)	Jul (29)	Aug (46)	Sep	Oct (2)	Nov (1)	Dec (5)
2012	Jan (7)	Feb	Mar	Apr	May	Jun (37)	Jul (20)	Aug (4)	Sep	Oct	Nov (5)	Dec (1)
2014	Jan (1)	Feb (4)	Mar	Apr (9)	May (2)	Jun (1)	Jul (2)	Aug	Sep	Oct	Nov	Dec
2015	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (14)
2017	Jan	Feb (4)	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

petri-foo-devel Mailing List for Petri-Foo

petri-foo-devel — The Petri-Foo mailing list