[ANN] ProcessPP

[Florian Schmidt]

This is totally alphabetagamma = unfinished and unpolished software. Release
early - release often is my guide here ;)

Here's the summary:

ProcessPP is the "realisation" of a rather silly idea: A livecoding
environment for C++. As C++ is not interpreted, but compiled, this indeed
does sound like a really silly idea. But the twist is that while “true”
livecoding cannot be done, it can be at least made as easy as possible to try
out new code snippets.
ProcessPP consists of three distinct parts
- procespp: A host application that can load shared objects and execute the
code contained in them
 - qprocesspp: A Qt GUI application which serves as an editor for hacking away
functions and to compile them easily into a shared object. Then it tells
processpp to load and run the shared object
 - libprocesspp: A shared library which is the “glue” between processpp and
user generated shared object files. Right now it only containes code for the
shared object to find out stuff like samplerate, buffersize, number of
input/output channels, etc..
For illustrative purposes here are the steps involved in making noise:
- File->Open from Template (choose process.template.cc)
 - Add some code in the inner loop to make noise
 - Process->Run
 - Hear the noise!!!
If the above don’t work, take a look at the log in the lower half of the main
window. Often some slight tweaks to the config file
(~/.config/Ugh!/process++.conf) need to be made.


Get it here: http://tapas.affenbande.org/wordpress/?page_id=91


Regards,
Flo

--
Palimm Palimm!
http://tapas.affenbande.org
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@...
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

[IOhannes m zmoelnig]

Florian Schmidt wrote:
> This is totally alphabetagamma = unfinished and unpolished software. Release
> early - release often is my guide here ;)

nice.
three remarks:

- add a README file (or something that explicitely lists the
dependencies; it took me a while to figure out that i need qscintilla2
instead of qscinitilla(1); i just noticed that this is mentioned on the
website)

- a quick way to find erroneous lines (that prevent the compilation to
finish); it would already help if the editor would display the line-number

- change the key-binding! Ctrl-C for _closing_ a module is really
totally out of what i had expected; i usually use Ctrl-C for copying
(like everybody else who is not yanking), i have lost quite some edited
files, because of this (and the weird layout of the confirmation dialog;
all yes/no/cancel dialogs i know will put the "cancel" as the right-most
button)


mfga.sdr
IOhannes
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@...
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

[Florian Schmidt]

On Thursday 11 September 2008, IOhannes m zmoelnig wrote:

> Florian Schmidt wrote:
> > This is totally alphabetagamma = unfinished and unpolished software.
> > Release early - release often is my guide here ;)
>
> nice.
> three remarks:
>
> - add a README file (or something that explicitely lists the
> dependencies; it took me a while to figure out that i need qscintilla2
> instead of qscinitilla(1); i just noticed that this is mentioned on the
> website)

Will do. this is part of the "totally unpolished,yada yada" part ;)

>
> - a quick way to find erroneous lines (that prevent the compilation to
> finish); it would already help if the editor would display the line-number


I;m sure QScintilla can do that. I'll look into it..  If you want to play
around it's in main_window.cc function setup_text_edit or something..

>
> - change the key-binding! Ctrl-C for _closing_ a module is really
> totally out of what i had expected; i usually use Ctrl-C for copying
> (like everybody else who is not yanking), i have lost quite some edited
> files, because of this (and the weird layout of the confirmation dialog;
> all yes/no/cancel dialogs i know will put the "cancel" as the right-most
> button)

You are of course totally right. will fix this ASAP and release 0.3. Thanks
for this.. I must have been out of my mind when i assigned hotkeys..


Regards and thanks for the feedback,
Flo


--
Palimm Palimm!
http://tapas.affenbande.org
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@...
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

[Florian Schmidt]

On Thursday 11 September 2008, Florian Schmidt wrote:

> > - change the key-binding! Ctrl-C for _closing_ a module is really
> > totally out of what i had expected; i usually use Ctrl-C for copying
> > (like everybody else who is not yanking), i have lost quite some edited
> > files, because of this (and the weird layout of the confirmation dialog;
> > all yes/no/cancel dialogs i know will put the "cancel" as the right-most
> > button)
>
> You are of course totally right. will fix this ASAP and release 0.3. Thanks
> for this.. I must have been out of my mind when i assigned hotkeys..

Changed it to CTRL+W in 0.3 [available now at
<http://tapas.affenbande.org/processpp/>]

Flo

--
Palimm Palimm!
http://tapas.affenbande.org
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@...
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev