Hello hello,
The second official source code release Petri-Foo is now available.
IMPORTANT: I have designated this release as a 'preview' release to
indicate this is still a work in progress so that users may be aware
things may change and their files may not be usable without alteration
in future versions.
HOWEVER: I feel Petri-Foo has moved along quite nicely since 0.0.1 in
April and would like to share that work with a few more of you than
are subscribed to the Petri-Foo developers list.
WHAT'S NEW.... and good (since 0.0.1):
* Default Patch
A default patch using a looped generated triangle wave sample, with an
ADSR, LFO, and MIDI CC setup with sensible/default values so a new
user can immediately hear audio.
* Selectable MIDI controllers
MIDI controllers are now selectable amongst all the other modulation
sources. This has two benefits, the first is being given the choice
(of course), and the second is that you can now control how much
effect the controller has.
* Patchlist context menu
You can now right-click on the patch list to get a context menu to
allow you to perform add, remove, rename, and duplicate operations on
patches.
* Keyboard tracking
Keyboard tracking has been added to all the parameters, and
additionally, to the envelopes where it modifies envelope duration.
* LFO Amplitude modulation
The LFOs now have amplitude modulation so that. For example, the
default patch uses this in combination with the MIDI Mod Wheel
controller to control pitch modulation.
* RAW sample format loading
Allows one to load files never intended to be heard :-)
* Removal of LASH support
* Removal of ALSA *audio* output (note: ALSA MIDI still supported)
* Miscellaneous bug fixes and GUI clean ups.
Home pages...
http://petri-foo.sourceforge.nethttp://github.com/jwm-art-net/Petri-Foo
Download...
http://sourceforge.net/projects/petri-foo/files/Source/petri-foo-0.0.2.tar.…
git clone git://github.com/jwm-art-net/Petri-Foo.git
Bug reports...
https://sourceforge.net/tracker/?group_id=404816
jwm.art.net(a)gmail.com
Mailing list...
https://lists.sourceforge.net/lists/listinfo/petri-foo-devel
please note, if you're not a member your messages ****are
automatically rejected**** :-p
cheers,
regards,
James.
> And this is what I'm wondering... could/should this be done with an LV2
extension?
>
I'm not qualified to answer that. Although, something like the HTTP Accepts
header and content negotiation comes to mind.
Hello all,
The recent zita-at1 release (0.2.2) had some test code in
it making it transpose everything down by an octave.
Fixed in 0.2.3, available now at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads>
Sorry for the unexpected noises, and thanks to Adrian
Knoth for reporting this bug.
--
FA
Hi,
Can anyone point me to a simple code example for how to determine the
phase at a specific time in a waveform?
ex. if I have a sample that is 5 seconds long and want to know the phase
at 2.5 seconds
I'm open to code in any language or a scripted example if such a tool
exists. If there is an ui which has that feature I am also interested.
Cheers
--
Patrick Shirkey
Boost Hardware Ltd
Hi *!
For those interested in Ambisonic surround sound: finally I've managed
to upload some side-by-side recordings of a Tetramic and the new ST450
which have been sitting on my harddisk for way too long.
http://stackingdwarves.net/download/TetraMic_vs_ST450/
Hopefully the recordings are worth your time even if you're not
currently shopping for a new surround microphone.
Attached is a README that goes with the audio files.
Enjoy,
Jörn
On Sun, 26 Jun 2011 12:35:22 +0200
louis cherel <cherel.louis(a)gmail.com> wrote:
> On 26/06/2011 09:43, Renato wrote:
> > Hello, this sounds good :) I tried compiling from git some weeks
> > ago but got errors and didn't have time to report, I'll try again
> > later today. May I ask:
> > 1) do the controls affect the sound in real time or only on the next
> > note? I noticed while playing with yoshimi that if for example you
> > tweak the filter cutoff frequency while a note is playing it won't
> > affect the current sound, but only the next note will be affected.
> > This would prevent making cool effects with automation...
> > 2) will this be merged in the main yoshimi project?
> >
> > cheers
> > renato
> For the errors, you may need to install libsm-dev and the fltk dev
> packages ( I don't know which they are ).
> To be sure, you can first install the official yoshimi package from
> the package manager of your distrib and next "make" the
> yoshimi-midiLearn branch.
>
ok, I managed to compile correctly. I would not want to install
system-wide though, so I tried to run from the local dir but got:
renato@acerarch ~/src/yoshimi-midi-learn/prove/yoshimi/src $ ./yoshimi
Default instrument tar file /usr/local/share/yoshimi/yoshimi-instruments.tar.gz not found
Failed to establish program bank database
Bad things happened, Yoshimi strategically retreats. Serious problems dealing with the instrument database
Flushing log:
Default instrument tar file /usr/local/share/yoshimi/yoshimi-instruments.tar.gz not found
Failed to establish program bank database
Bad things happened, Yoshimi strategically retreats. Serious problems dealing with the instrument database
should I point it to the yoshimi-instruments.tar.gz that's found one directory up (in the root of the cloned git)? how?
cheers
renato
output + backtrace
-----------------------------
canvas::ports_connected(3, 24, 2, 10)
canvas::ports_connected(1, 1, 4, 25)
canvas::ports_connected(1, 2, 4, 26)
canvas_cls::on_realize
Program received signal SIGSEGV, Segmentation fault.
0x000000000042b36c in ladish_room_proxy_get_recent_projects (proxy=0x0,
max_items=10, callback=0x4200a2 <add_recent_project>,
context=0x7fffffffd9b0) at ../proxies/room_proxy.c:481
481 if (!dbus_call(0, proxy_ptr->service, proxy_ptr->object,
IFACE_RECENT_ITEMS, "get", "q", &max_items, NULL, &reply_ptr))
(gdb) bt
#0 0x000000000042b36c in ladish_room_proxy_get_recent_projects (proxy=0x0,
max_items=10, callback=0x4200a2 <add_recent_project>,
context=0x7fffffffd9b0) at ../proxies/room_proxy.c:481
#1 0x000000000042013f in fill_project_dynmenu (
callback=0x4213b6 <ladish_dynmenu_add_entry>, context=0x7fffe4021700)
at ../gui/menu.c:141
#2 0x0000000000421683 in populate_dynmenu_menu (menu_item=0x7fffe4001c30,
dynmenu_ptr=0x7fffe4021700) at ../gui/dynmenu.c:167
#3 0x00007ffff730981c in g_closure_invoke ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007ffff731b019 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007ffff7324258 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007ffff732441f in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7 0x00007ffff4a566ce in gtk_widget_activate ()
from /usr/lib/libgtk-x11-2.0.so.0
#8 0x00007ffff494f94d in gtk_menu_shell_activate_item ()
from /usr/lib/libgtk-x11-2.0.so.0
#9 0x00007ffff494dce5 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x00007fffec4a9ed4 in ?? () from /usr/lib/libdbusmenu-gtk.so.3
#11 0x00007fffec4aadd8 in dbusmenu_gtk_parse_menu_structure ()
from /usr/lib/libdbusmenu-gtk.so.3
#12 0x00007fffec6b2a76 in ?? ()
from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#13 0x00007fffec6b2efa in ?? ()
from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#14 0x00007ffff488795b in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x00007fffec6b2ad8 in ?? ()
from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#16 0x00007fffec6b2efa in ?? ()
from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#17 0x00007fffec6b2ad8 in ?? ()
from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#18 0x00007fffec6b2de1 in ?? ()
from /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so
#19 0x00007ffff6e4b4eb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007ffff6e49bcd in g_main_context_dispatch ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ffff6e4a3a8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007ffff6e4a9f2 in g_main_loop_run ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007ffff4938af7 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#24 0x0000000000413881 in main (argc=1, argv=0x7fffffffe348)
at ../gui/main.c:194
Hi all - I'm just wondering if any "evil genius" (to use Jan's phrase from
two years ago!) had gotten a Tascam US-1641 interface working under any
flavor of Linux - (especially ubuntu studio)...
My google searches yield a bunch of stuff that's at least 2 years old -
wondering if anything's happened since...
Thanks! :)
--
--------------
Aaron Trumm
www.nquit.com
-------------
cxirxcxxcxcx"d#xxxx"""xxx""xid#dddoxddxidddd#dxxxxdxd#cxddcdodxdxohddhhdd#dixxxxxyxykx#x"ďdyxdxxxdfdddddrddxd
Il giorno 19/apr/2011 12:08, "Niccolò Belli" <darkbasic4(a)gmail.com> ha
scritto:
Il 18/04/2011 14:41, Niccolò Belli ha scritto:
> Where should I report the bug?
I reported it upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=33602
Please let me know if there is an -rt bug tracker.
Cheers,
Darkbasic
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-d...