Hi,
is it possible to record multi channel speech audio and down sample it
2 stereo channels BUT with horizontal audio positioning of each audio
channel ie. like dolby surround effect.
I'm not looking to make multi channel podcast, just a plain stereo
podcast. Ok, not just plain, maybe better term is enhanced podcast
with "dolby surround" or "binaural" effect so that different voices
appear to be coming from different positions.
The idea is to make a podcast with 5 (or more/less people) and record
each of them individually and to make an stereo file for distribution
but such that each person has a distinct "location" in your ear. So
you can hear that person A is in front of you, person B is on the far
left, person C is to the right but closer to center... and so on.
I would maybe have 3 channels sometimes and sometimes maybe 7
channels, it differs by the amount of guests there are in each podcast
show.
Is there some linux audio tool which I could feed 3-7 wav tracks and
define where in horizontal space I want each channel to be located -
and it makes final stereo track with this "binaural" or "Dolby
surround" enhanced podcast?
Thank you in advance.
--
http://kernelreloaded.blog385.com/
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241
Skype: valent.turkovic
On 3/13/07, Georg Holzmann <georg.holzmann(a)student.kug.ac.at> wrote:
> Hallo!
>
> > I'm not looking to make multi channel podcast, just a plain stereo
> > podcast. Ok, not just plain, maybe better term is enhanced podcast
> > with "dolby surround" or "binaural" effect so that different voices
> > appear to be coming from different positions.
> [...]
> > Is there some linux audio tool which I could feed 3-7 wav tracks and
> > define where in horizontal space I want each channel to be located -
> > and it makes final stereo track with this "binaural" or "Dolby
> > surround" enhanced podcast?
>
> Yes, there are various implementations of binaural spatialization in
> Pure Data (and I guess also in Supercollider and CSound ...).
>
> I am just making some ready-made tutorial patches regarding this topic
> for the linux audio conference - so if you wait some days you can have
> them !
>
> LG
> Georg
>
Great! I would love to gave it!
Thank you in advance.
Valent.
Greetings all,
For the impatient, download at:
http://ico.bukvic.net/Max/munger1~_1.0.0.tar.gz
(270KB, includes source, Linux-Pd-i386, Mac-Max-i386, and Win32-Max-i386
binaries, and 3 cases of beer)
OVERVIEW
========
munger1~ (March 12, 2007 1.0.0 release)
a realtime multichannel granulator
a.k.a. the swiss-army-knife of realtime granular synthesis
a flext (cross-platform PD & Max/MSP) port of
the munger~ object from the PeRColate library (0.9 beta5)
http://www.music.columbia.edu/PeRColate/
Original PeRColate library by:
Dan Trueman http://www.music.princeton.edu/~dan/
R. Luke DuBois's http://www.lukedubois.com/
Flext port and additions by:
Ivica Ico Bukvic http://ico.bukvic.net
Ji-Sun Kim hideaway(a)vt.edu
http://www.music.vt.eduhttp://www.cctad.vt.edu
Released under GPL license
(whichever is the latest version--as of this release, version 2)
For more info on the GPL license please visit:
http://www.gnu.org/copyleft/gpl.html
ACKNOWLEDGEMENTS
================
Many thanks to Dan Trueman for open-sourcing this great object!
SOURCE INSTALL
==============
If you simply intend to use prebuilt binaries, please skip to the INSTALL
section. Otherwise take a big breath and read on...
1) You need stk library which can be downloaded from:
http://ccrma.stanford.edu/software/stk/
2) You need to also install latest flext library (this is a library that
allows for creation of externals for both Max/MSP and PD using the same
source). Version 0.4.x can obtained from the following link:
http://grrrr.org/ext/flext/
Latest CVS version (0.5.1) is found in the Pure-Data CVS (this one is
recommended):
http://sourceforge.net/cvs/?group_id=55736
3) If you are using latest CVS version (0.5.1) Before compiling the source
you will need to add the following to the top of the flext/source/flstk.h
file right below the #define __FLSTK_H:
#ifdef PI
#undef PI
#endif
This step will probably become quickly obsolete once Thomas updates CVS.
Until then, this is needed to be able to compile flext against stk.
4) To compile flext, read flext instructions (it boils down to running
build.sh with appropriate parameters and then editing two simple config
files, i.e. "build pd gcc build" or "build max gcc" or "build max msvc"
etc.)
Your will need to edit buildsys/config-<platform-compiler-pdormax>.txt to
adjust paths to various folders.
Then you will need to edit config.txt file. You do not need to include
SndObj for this external but you do need stk option to be properly set. On
Windows+MSVC, STK flag at the time of this release does not work, so you
will have to use included testmunger1 MSVC project file and adjust path
settings to compile munger1~.
5) Once stk and flext are compiled, go into munger1~ folder and type:
<path to flext folder>/build.sh <platform> <compiler> <build/clean/install>
NB: on Mac <build/clean/install> is not needed. On Windows, please use MSVC
and open the testmunger1 project file in the root of the folder.
6) Once compiled, your binary will be created in a <maxorpd-platform>
subfolder (i.e. pd-linux, or max-darwin), followed by another subfolder
which reflects whether a threaded or singlethread flext was used. Inside you
will find your external.
INSTALL
=======
You can either use the prebuilt externals (found in the bin/ folder) or ones
built using the "SOURCE INSTALL" instructions above. Binaries are provided
for Intel-based Macs, Win32, and Intel-based Linux OS. The included prebuilt
binaries DO NOT REQUIRE you to install flext or stk as these are statically
linked.
1) Copy the external in your externals folder (i.e. /usr/lib/pd/extra or
C:\Program Files\Cycling '74\MaxMSP 4.6\Cycling '74\externals\, or
"Applications/MaxMSP 4.6/Cycling '74/externals)
2) Copy appropriate help file (found in the help/ folder) into the help
folder (i.e. /usr/lib/pd/doc/5.reference or C:\Program Files\Cycling
'74\MaxMSP 4.6\max-help, or "Applications/MaxMSP 4.6/max-help)
NB: Pd help file has a ".pd" extension, while Max/MSP help file has a
".help" extension.
3) Start your app (PD or Max) and create object called munger1~. Right-click
(ctrl-click on Macs) and select "help" and this should open the help file
with additional documentation.
Questions? See OVERVIEW for contact and Q&A info.
Enjoy!
FAQ
===
The following is Ico's FAQ, so it may or may not reflect other project
participants' opinions, including original author(s) of munger~, flext, etc.
Q: Why porting to flext?
A: Flext library (by Thomas Grill) is a layer which allows creation of
externals for both Max/MSP and PD without any alterations to the code
(obviously once it is adapted to use flext). While there have been a number
of Max/MSP <-> PD external ports in the past, many of them have become
outdated because such attempts required either maintaining one code full of
ugly #ifdefs, or worse--maintaining two sources. Either way, what usually
turned out to be the case is that original authors did not have the time,
interest, or simply the software/hardware to deal with the newly generated
overhead and/or test the code, while volunteers who made the original
porting efforts eventually moved on to other projects. The result was/is
outdated and/or broken externals. Flext circumvents this problem by allowing
one clean code to compile on both platforms while also supplying in many
cases cleaner (more legible) API and (as a whipped cream on top)
object-oriented environment (C++).
Q: Why bother with PD <-> Max/MSP cross-platform compatibility...
...when I use only <insert-your-favorite-application-here>?
...<insert-your-favorite-application-here> is better?
A: Choice is what makes us human (this is also what makes Arts so vibrant
and exciting). And while everyone's welcome to express their own
preferences, we also have to realize that in this case these same
preferences are also the main cause of a virtual divide which manifests
itself at everyone's detriment. Wouldn't it be nicer if we could share
externals transparently, or even better, open PD patches in Max and
vice-versa? This would help in both the cross-pollination of ideas as well
as creative efforts. This project has also taught me that creating
flext-ready externals is as easy if not easier (due to the aforesaid API's
legibility) than native objects (whether that be PD or Max/MSP). Finally, if
all else fails, such externals are bound to reach wider audience, and are
much easier to maintain if cross-platform compatibility is to be pursued.
Q: If flext is so cool, why don't we see more porting efforts?
A: Good question. The fact is that flext is much more widely known among PD
users than it is among the Max/MSP community, so this seemingly one-way road
may have contributed to the current situation. One could only hope that
projects like this may help reverse this unfortunate trend.
Q: So, is all really that peachy in the flext-land?
A: Well, our lives teach us that nothing is truly free in this world. Flext
is no exception. Its "fees," however are not tied to our checkbooks. Rather,
they manifest themselves in a slightly greater CPU overhead in signal flow
due to message translation. Thus, one could consider flext a "middle-person"
between the <app-of-your-choice> and the external. This, however, in today's
world is so negligible that during the testing phase I was unable to measure
any noticeable CPU-overhead difference.
Another consideration is that flext might not be complete (see KNOWN ISSUES
for an example). That being said, in its current state it did the trick for
a relatively complex external such as munger~ or even FFTEASE collection
which had been ported several years ago. All this leads me to believe that
it is more than ready for the day-to-day use.
Q: I already have Dan and Luke's awesome PeRColate lib. Why should I
download this one?
A: This is a cross-platform port of the latest version with several new
features. Thus, it allows for those platforms which have not had the beta6
available (Linux, Windows) to finally dig into all the goodies it brings.
Plus you also get the cool stuff such as verbose modes, discrete panning,
more thorough documentation, up to 500 grains per sample (instead of 50), up
to 24-channel output (instead of 2 or 16, depending which one you used),
etc.
KNOWN ISSUES
============
munger1~ has been tested extensively on Linux+PD, OSX+Max/MSP and
Win32+Max/MSP setups, suggesting that it should work on other setups as
well. Your mileage may vary, though.
Currently there is only one known issue in the wild which requires changes
to flext in order to be fixed. Namely, if you use munger1~ object in
conjunction with an external buffer in PD (known as an array) and if you
dubiously decide to delete that particular buffer in the middle of your
performance while munger1~ is still associated with it, this will
[unsurprisingly] crash PD. Max/MSP currently has a check implemented against
that via flext layer so Max/MSP will simply stop outputting anything until
buffer is reset. The flext author is aware of this and PD fix should appear
in the flext CVS hopefully soon. That being said, the lingering question is
why would you want to do this in the first place...
FYI, even though munger1~ allows up to 500 simultaneous grains per sample
and has been compiled with all available optimizations (SSE, Altivec is
supposedly available via flext but has not been tested), on MBP (Core Duo
1.83GHz) I was unable to get more than 160 simultaneous grains per sample
(or ~32,000 grains/second) without dropouts, even though CPUs were not
getting maxed out, so something else might be the cause of this limitation
(flext?). Win32 machine (3-year old AMD64 3000+) fared marginally better at
around 165 simultaneous grains per sample (or ~33,000 grains/second) before
its CPU was maxed out. Linux on the same AMD64 3000+ hardware fared the
best. It topped off at 47,999 grains per second at 48KHz sampling rate which
for some reason the sampling rate appears to be the upper limit (i.e. if you
run PD or Max/MSP at lower sampling rates, your upper limit will be
restricted to the sampling rate), even though the code allows for multiple
initiations of grains per cycle. This, however, is also the way original
munger~ works.
An interesting bit is that while on Linux/PD combo 48K grains are already
reached when we get 64 simultaneous grains, on Win32/Mac even 160
simultaneous grains yield only ~32-33K grains. Could this be a flext bug?
Best wishes,
Ivica Ico Bukvic, D.M.A.
Composition, Music Technology, CCTAD, CHCI
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-1137
(540) 231-5034 (fax)
ico(a)vt.edu
http://www.music.vt.edu/people/faculty/bukvic/
There have been a few edits on our "deveopment"-wiki
apps-devel.linuxaudio.org !
sorry for the confusion:
http://apps.linuxaudio.org is the "real" site.
http://apps-devel.linuxaudio.org/ is our *test server* that we use to
experiment with PHP, plugins, designs, software updates, etc - it's
actually a 1:1 mirror, but not intended for the public. - we ought to
set up a jailed webserver behind openvpn for testing, but we're just not
there yet :(
robin
> a configuration option
Build configuration, or DSSI configure() ?
The latter would fix it, while (it seems?) the former
would mean distros having to choose between better
sound and project compatibility on behalf of their
users, which is not much of a choice.
If you do mean the latter, then your previous fix
seems better - a user can always choose to
downgrade, or a packager find creative ways to
provide both.
I suppose a packager could include libraries built both
with and without the option... but that's a
compatibility minefield (with other ad-hoc packages
from other distros).
Hoping you did mean DSSI configure,
Chris
Hi all,
If you're thinking of packaging hexter 0.6.0 for your
favorite distribution, please wait for version 0.6.1.
I've been talking with Anthony Green about his efforts
to package hexter 0.6.0 for Fedora, and it seems I made
a mistake.
hexter 0.6.0 can sound radically different from hexter 0.5.9,
depending on the patch used, and I didn't want anyone's
existing projects to break if they upgraded. So I changed
the way hexter 0.6.0 installs: it installs as hexter6.so, while
hexter 0.5.9 installs as hexter.so, so the two versions can
coexist.
This works well enough for people who install from source,
but Anthony pointed out that this makes things difficult for
people packaging hexter for distributions. For most distros,
when one upgrades, the old files are removed, meaning
hexter.so would disappear and existing projects would
break. Distros with something akin to Gentoo's SLOT
mechanism can have multiple versions installed
simultaneously, but the majority of hexter users will have
no need for anything but the latest version.
What I'm going to do with version 0.6.1 instead is make
it install as hexter.so, just like 0.5.x versions, and add
a configuration option which will optionally make it sound
like 0.5.9. Problem solved: existing projects can easily
be made to sound like they originally did, and everyone
can have the latest and greatest hexter installed.
Expect 0.6.1 sometime this coming week. Thanks,
Sean Bolton
*About:
Mammut will FFT your sound in one single gigantic analysis (no windows).
These spectral data, where the development in time is incorporated in
mysterious ways, may then be transformed by different algorithms prior to
resynthesis. An interesting aspect of Mammut is its completely
non-intuitive sound transformation approach.
*Homepage:
http://www.notam02.no/arkiv/doc/mammut/
*Screenshot:
http://www.notam02.no/arkiv/doc/mammut/mammut.png
Changes 0.57 -> 0.59
---------------------
-Added workaround for rare sound corruption bug.
-Added the "Redo it!" buttons. (The same as pressing "Undo" + "Do it!")
-If playing while pressing a "Do it!" or "Redo it!" button, continue
playing after processing as well.
-Added the "Random Phases" toggle button in the "Multiply Phase" dialog.
Checking this button will freeze the sound. Thanks to Tim Blechman for
the idea.
-Fixed looping which wasn't turned off if using a different sampling rate.
-Added "make install" and "make uninstall"
-Fixed animation bug. (should allways be shown now)
-Fixed a couple of more int->uint32 time variable cases. Hopefully, the
animation stuff shouldn't stall the machine anymore.
Hi everyone,
As I said yesterday when I said the migration to linuxaudio.org was
postponed till 1st April, there are still a few issues asking for
comments.
It has been suggested by a few people(Ivica Ico Bukvic, Jan Weil) that
the email addresses linux-audio-xxxxx(a)linuxaudio.org was kind of
redundant. The following suggestions were made :
¤ just switch the names to announce(a)linuxaudio.org,
dev(a)linuxaudio.org, and user(a)linuxaudio.org.
¤ Make aliases : linux-audio-dev(a)linuxaudio.org -> dev(a)linuxaudio.org
To this Leonard Ritter replied that this could lead to more spam.
IMO, since we are working on a spamassassin+mailman interfacing, it
should not be a problem. The aliases seem the solution that could make
everyone happy since both type of addresses would work and the lists
would keep their "historical" names.
Ready, steady... FLAME !
__________________
Marc-Olivier Barre,
Markinoko.
PS : please reply to both lists (I'll try to be swift on moderating
users that are not registered on both lists) so everyone can enjoy
your comments :-)