Re: [PD] trying to get wg acre library to init - iemlib declaration

[Winfried Ritsch]

thanks for reporting,  it is now also changed in the git repo, with few other 
things. A new version is on the way end of the week,

mfg
 winfried


Am Montag, 1. April 2019, 03:06:52 CEST schrieb Scott R. Looney:
> thank you sir, that did the trick just fine. appreciate it!
> 
> best,
> scott
> 
> On Mon, Apr 1, 2019 at 1:39 AM IOhannes m zmoelnig  wrote:
> > On 01.04.19 09:20, Scott R. Looney wrote:
> > > hey folks i'm trying to get the IEM waveguide library examples to load
> > 
> > and
> > 
> > > having a bit of trouble. i'm on a Mac and i've installed the various
> > > dependencies (iemlib,zexy,iemmatrix) via Deken, but it seems like the
> > > initializing fails as objects like [lp1~] and [hp1~] aren't recognized.
> > 
> > so
> > 
> > > i think the [declare] objects might need tweaking. what i found a bit
> > > confusing is there was no iemlib1 or iemlib2, just iemlib when i
> > 
> > installed
> > 
> > > it via Deken. the iemlib init in the WG Demos is [declare -stdpath
> > 
> > iemlib],
> > 
> > > so if Deken installed iemlib to stdpath it seems the demo doesn't work.
> > 
> > iemlib recently switched from the separate iemlib1/iemlib2/iem_t3/...
> > libraries to a single "iemlib" binary.
> > 
> > probably acre still tries to load the old (no longer existing) libraries.
> > 
> > so: just fix the declare's to [declare -path iemlib -lib iemlib]
> > 
> > (or, if you want to play safe and support older iemlibs, use something
> > like:
> > [declare -path iemlib -lib iemlib -lib iemlib1 -lib iemlib2]
> > 
> > > i also checked iemlib library separately and it seems it is having
> > > issues
> > > as well and can't find things like [init] for example. i checked the
> > 
> > search
> > 
> > > path (Users/scottlooney/Documents/PD/Externals is the only entry) and
> > 
> > that
> > 
> > > window is set to use standard paths.
> > > guess this means that Deken doesn't
> > > solve path problems? should i be adding other paths?
> > 
> > no: deken is not a replacement for properly declaring dependencies in
> > your path.
> > you need to also specify the path:
> > [declare -path iemlib -lib iemlib]
> > 
> > in general, you should *not* add a library to your global search-paths
> > (and deken should not do so either), but us *local* paths (via [declare])
> > 
> > gfmasdr
> > IOhannes
> > 
> > ___
> > Pd-list@lists.iem.at mailing list
> > UNSUBSCRIBE and account-management ->
> > https://lists.puredata.info/listinfo/pd-list


-- 
--
- ao.Univ.Prof. DI Winfried Ritsch 
- rit...@iem.at - http://iem.at/ritsch
- Institut fuer Elektronische Musik und Akustik
- University of Music and Dramatic Art Graz
- Tel. ++43-316-389-3510 (3170) Fax ++43-316-389-3171 
--



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] trying to get wg acre library to init - iemlib declaration

[Scott R. Looney]

thank you sir, that did the trick just fine. appreciate it!

best,
scott

On Mon, Apr 1, 2019 at 1:39 AM IOhannes m zmoelnig  wrote:

> On 01.04.19 09:20, Scott R. Looney wrote:
> > hey folks i'm trying to get the IEM waveguide library examples to load
> and
> > having a bit of trouble. i'm on a Mac and i've installed the various
> > dependencies (iemlib,zexy,iemmatrix) via Deken, but it seems like the
> > initializing fails as objects like [lp1~] and [hp1~] aren't recognized.
> so
> > i think the [declare] objects might need tweaking. what i found a bit
> > confusing is there was no iemlib1 or iemlib2, just iemlib when i
> installed
> > it via Deken. the iemlib init in the WG Demos is [declare -stdpath
> iemlib],
> > so if Deken installed iemlib to stdpath it seems the demo doesn't work.
>
>
> iemlib recently switched from the separate iemlib1/iemlib2/iem_t3/...
> libraries to a single "iemlib" binary.
>
> probably acre still tries to load the old (no longer existing) libraries.
>
> so: just fix the declare's to [declare -path iemlib -lib iemlib]
>
> (or, if you want to play safe and support older iemlibs, use something
> like:
> [declare -path iemlib -lib iemlib -lib iemlib1 -lib iemlib2]
>
> >
> > i also checked iemlib library separately and it seems it is having issues
> > as well and can't find things like [init] for example. i checked the
> search
> > path (Users/scottlooney/Documents/PD/Externals is the only entry) and
> that
> > window is set to use standard paths.
> > guess this means that Deken doesn't
> > solve path problems? should i be adding other paths?
>
> no: deken is not a replacement for properly declaring dependencies in
> your path.
> you need to also specify the path:
> [declare -path iemlib -lib iemlib]
>
> in general, you should *not* add a library to your global search-paths
> (and deken should not do so either), but us *local* paths (via [declare])
>
> gfmasdr
> IOhannes
>
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Mute certain partials (sigmund~)?

[Peter P.]

Hi,

* William Brent  [2019-03-30 16:21]:
> If you're open to other processing options, I made an extern a while back
> that does FFT filtering relative to harmonic numbers. You feed it a signal
> and the continuous MIDI pitch output from [sigmund~], and then based on
> scalar values from a table you can boost/cut the amplitude of any given
> harmonic by index. I haven't maintained it at all, but you can get the
> source, help, and win/mac binaries here:
> 
> http://williambrent.conflations.com/pages/research.html#pitchEnv
Thank you, will give it a try within the next days!
> 
> That should give you the effect you want if I'm understanding you right.
> But if you specifically want to stick with analysis/resynthesis using
> [sigmund~], I gave a shot at a solution that produces mute/play flags for
> each [sigmund~] "track" by index. 
Actually, I have not yet understood what a sigmund~ "track" is, the help
patch does not say much. What is the difference between a track and a
partial?

Thanks again!
P



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] trying to get wg acre library to init - iemlib declaration

[IOhannes m zmoelnig]

On 01.04.19 09:20, Scott R. Looney wrote:
> hey folks i'm trying to get the IEM waveguide library examples to load and
> having a bit of trouble. i'm on a Mac and i've installed the various
> dependencies (iemlib,zexy,iemmatrix) via Deken, but it seems like the
> initializing fails as objects like [lp1~] and [hp1~] aren't recognized. so
> i think the [declare] objects might need tweaking. what i found a bit
> confusing is there was no iemlib1 or iemlib2, just iemlib when i installed
> it via Deken. the iemlib init in the WG Demos is [declare -stdpath iemlib],
> so if Deken installed iemlib to stdpath it seems the demo doesn't work.


iemlib recently switched from the separate iemlib1/iemlib2/iem_t3/...
libraries to a single "iemlib" binary.

probably acre still tries to load the old (no longer existing) libraries.

so: just fix the declare's to [declare -path iemlib -lib iemlib]

(or, if you want to play safe and support older iemlibs, use something like:
[declare -path iemlib -lib iemlib -lib iemlib1 -lib iemlib2]

> 
> i also checked iemlib library separately and it seems it is having issues
> as well and can't find things like [init] for example. i checked the search
> path (Users/scottlooney/Documents/PD/Externals is the only entry) and that
> window is set to use standard paths. 
> guess this means that Deken doesn't
> solve path problems? should i be adding other paths?

no: deken is not a replacement for properly declaring dependencies in
your path.
you need to also specify the path:
[declare -path iemlib -lib iemlib]

in general, you should *not* add a library to your global search-paths
(and deken should not do so either), but us *local* paths (via [declare])

gfmasdr
IOhannes



signature.asc
Description: OpenPGP digital signature
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

[PD] [PD-announce] CfP Audio Mostly 2019: A Journey in Sound, 18-20th September 2019, University of Nottingham, UK

[Hug Daniel]

(Apologies for cross-postings, please re-distribute at will)
___
Audio Mostly 2019: A Journey in Sound
18th to 20th September 2019
University of Nottingham, Nottingham, UK

www.audiomostly.com
Facebook: https://www.facebook.com/AudioMostly/
Twitter:  https://twitter.com/AudioMostly @AudioMostly
___

AUDIO MOSTLY 2019
Audio Mostly is an audio focused interdisciplinary conference on design, 
interacting with sound and technology, which embraces applied theory and 
practice-based research.

It is an annual conference which brings together thinkers and doers from 
academia and industry who share an interest in sonic interaction and the use of 
audio for interface design. This remit covers product design, auditory 
displays, computer games and virtual environments, new digital musical 
instruments, educational applications and workplace tools, as well as the 
topics listed below. It further includes fields such as the psychology of sound 
and music, cultural studies, systems engineering, and everything in between in 
which sonic Human-Computer Interaction plays a role.

Audio Mostly 2019 will be an inclusive event for all, bringing together a whole 
range of people and communities. It will be a lively and sociable mix of oral 
and poster paper presentations, demos, and workshops. We welcome submissions 
from industry, academia and interested parties in each of these categories.

As in previous years, the Audio Mostly 2019 proceedings will be published by 
the Association for Computing Machinery (ACM) (to be confirmed) and made 
available through their digital library. Regular papers, posters and 
demos/installations will be double-blind peer reviewed. It is envisaged that 
there will be a special issue of a journal relating to the conference, as with 
previous years.


CONFERENCE THEME - A Journey in Sound
The special theme for the conference this year is A Journey in Sound and we 
would particularly welcome papers relating to this theme for at the conference 
this year. We often have different experiences of sound and music though out 
our lives, there are sounds that remind us of different places and people. We 
also have different playlists and songs that take us back and remind us of 
certain times and events. Throughout our lives we are interacting with sounds 
and music, we are on a journey in sound. This year the theme of the conference 
is open to interpretation, but people might think about the following, in 
relation to the theme:


  *   Sonic aspects of digital stories, documentaries and archives
  *   The soundtrack to our lives. Archiving and sharing sound
  *   The emotional potential of a sound, how might this be used to support 
interaction
  *   The different uses of music across different settings
  *   The re-use of recollections and memories by composers & sound designers
  *   The development of musical tools that can let us express our experiences 
over time
  *   Socio-technical uses of AI create highly personalised soundtracks that 
respond to one's context
  *   Adaptive music use in journeys, time and the creative use of data

Audio Mostly 2019 encourages the submission of regular papers (oral/poster 
presentation) addressing such questions and others related to the conference 
theme and the topics presented below.


LIST OF TOPICS
The Audio Mostly conference series is interested in sound Interaction Design & 
Human-Computer Interaction (HCI) in general. The conference provides a space to 
reflect on the role of sound/music in our lives and how to understand, develop 
and design systems which relate to sound and music - we are particularly 
interested in this from a broad HCI perspective. We encourage original regular 
papers (oral/poster presentation) addressing the conference theme or other 
topics from the list provided below. We welcome multidisciplinary approaches 
involving fields such as music informatics, information and communication 
technologies, sound design, music performance, visualisation, composition, 
perception/cognition and aesthetics.

* Accessibility
* Aesthetics
* Affective computing applied to sound/music
* AI, HCI and Music
* Acoustics and Psychoacoustics
* Auditory display and sonification
* Augmented and virtual reality with or for sound and music
* Computational musicology
* Critical approaches to interaction, design and sound
* Digital augmentation (e.g. musical instruments, stage, studio, audiences, 
performers, objects)
* Digital music libraries
* Ethnographic studies
* Game audio and music
* Gestural interaction with sound or music
* Immersive and spatial audio
* Interactive sonic arts and artworks
* Intelligent music tutoring systems
* Interfaces for audio engineering and post-production
* Interfaces or synthesis models for sound design
* Live performing arts
* Music information retrieval &