[Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

[Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
Dear list,

As I built my Csound on Ubuntu more than one year ago, I would like to
update it to the current version (master). Mostly everything works fine
but I do get an error message regarding "SWIG" and something related to
that seems to cause an error in the cmake build process. I am not sure
what to do now, as the SWIG-version seems to be all right: "found
suitable version "2.0.11", minimum required is "2.0""

I placed the relevant excerpt of the messages below. Maybe someone has
an idea what causes that error and what I could do to overcome it?

Best regards,

Jan Jacob


[...]

-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11",
minimum required is "2.0")

-- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so

-- BUILD_PYTHON_INTERFACE is enabled.

-- BUILD_JAVA_INTERFACE is enabled.

-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling
BUILD_LUA_INTERFACE

-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE

-- BUILD_LUA_INTERFACE is disabled.

-- SWIG_USE_FILE:

CMake Error at interfaces/CMakeLists.txt:92 (include):

include called with wrong number of arguments. include() only takes one

file.



CMake Error at interfaces/CMakeLists.txt:112 (swig_add_module):

Unknown CMake command "swig_add_module".



-- Configuring incomplete, errors occurred!


[...]



sound      |      movement       |       object      |      space
sonic architecture     |      site: http://www.sonicarchitecture.de
spatial electronic composition    |    higher order ambisonic music

Am 03.03.2018 um 01:00 schrieb CSOUND automatic digest system:

> There are 17 messages totaling 2115 lines in this issue.
>
> Topics of the day:
>
>    1. Redefining f signals (3)
>    2. balance opcode sound artifact (4)
>    3. Noise detection (3)
>    4. --realtime flag (7)
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ----------------------------------------------------------------------
>
> Date:    Fri, 2 Mar 2018 00:05:04 +0000
> From:    jpff <[hidden email]>
> Subject: Re: Redefining f signals
>
> Two thoughts;
> 1: That ought to work
> 2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not
> work?
>
>
> On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:
>
>> Hello,
>>
>> I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.
>>
>> If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.
>>
>> I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.
>>
>> I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
>> Do you have some advice on how to handle a chain of optional f-signal processings?
>>
>> Best
>> Ruben
>>
>>
>> if (ifile1ch==1.000) goto monopvsanal
>> monopvsanal:
>> fsig1 pvsanal apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
>> goto postpvsanal
>> postpvsanal:
>>
>> if (iwanttoskipsecondpitch==1) goto postpvscale
>> if (ifile1ch==1.000) goto monopvscale
>> monopvscale:
>> fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
>> fsig1= fsig101
>> goto postpvscale
>> postpvscale:
>>
>> ;etc…add 10 similar modules
>>
>> if (ifile1ch==1.000) goto monopvsynth
>> monopvsynth:
>> a2ambL pvsynth fsig1
>> goto spatialization
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 00:07:55 +0000
> From:    jpff <[hidden email]>
> Subject: Re: Redefining f signals
>
> and...
>
> if (ifile1ch==1.000) goto monopvscale
> monopvscale:
>
> does not make much sense, ad yourtests/goto seem to be all i-rate so do
> not affect perf time
> xy
>
> On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:
>
>> Hello,
>>
>> I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.
>>
>> If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.
>>
>> I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.
>>
>> I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
>> Do you have some advice on how to handle a chain of optional f-signal processings?
>>
>> Best
>> Ruben
>>
>>
>> if (ifile1ch==1.000) goto monopvsanal
>> monopvsanal:
>> fsig1 pvsanal apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
>> goto postpvsanal
>> postpvsanal:
>>
>> if (iwanttoskipsecondpitch==1) goto postpvscale
>> if (ifile1ch==1.000) goto monopvscale
>> monopvscale:
>> fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
>> fsig1= fsig101
>> goto postpvscale
>> postpvscale:
>>
>> ;etc…add 10 similar modules
>>
>> if (ifile1ch==1.000) goto monopvsynth
>> monopvsynth:
>> a2ambL pvsynth fsig1
>> goto spatialization
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 10:00:08 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: Redefining f signals
>
> The manual notes that some opcodes have side effects on inputs, so re-using the variable should not
> be taken for granted. Check the man page.
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 2 Mar 2018, at 00:05, jpff <[hidden email]> wrote:
>>
>> Two thoughts;
>> 1: That ought to work
>> 2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not work?
>>
>>
>> On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:
>>
>>> Hello,
>>>
>>> I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.
>>>
>>> If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.
>>>
>>> I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.
>>>
>>> I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
>>> Do you have some advice on how to handle a chain of optional f-signal processings?
>>>
>>> Best
>>> Ruben
>>>
>>>
>>> if (ifile1ch==1.000) goto monopvsanal
>>> monopvsanal:
>>> fsig1 pvsanal apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
>>> goto postpvsanal
>>> postpvsanal:
>>>
>>> if (iwanttoskipsecondpitch==1) goto postpvscale
>>> if (ifile1ch==1.000) goto monopvscale
>>> monopvscale:
>>> fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
>>> fsig1= fsig101
>>> goto postpvscale
>>> postpvscale:
>>>
>>> ;etc…add 10 similar modules
>>>
>>> if (ifile1ch==1.000) goto monopvsynth
>>> monopvsynth:
>>> a2ambL pvsynth fsig1
>>> goto spatialization
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>        https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 10:06:21 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: balance opcode sound artifact
>
> I tried your soundfile but could not hear anything (which does not mean it is not there).
> What I am saying is that the opcode is what it is, it has been used in lots of applications
> and we should not change its behaviour (backwards compatibility).
>
> I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
> on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
> as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
> (way back in MUSIC 11) being the way it is.
>
> Once sourceforge is back up and appveyor is building again, you’re welcome to try this
> opcode (just replace balance by balance2).
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>
>> Aha! But then what can be causing this noise..? I am using the opcode
>> exactly as shown - did you try with the soundfile I attached?
>> If the balance opcode is supposed to add noise, is there perhaps
>> nother way I can achieve this same effect without added noise? (and
>> without changing ksmps)
>> Søren
>>
>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>> Balance finds the rms of the two signals at k-rate, but it applies
>>> the amplitude changes by interpolating linearly between k-rate
>>> values.
>>>
>>> It could well be that in the particular way you are using you hear
>>> some artefact. However that’s the behaviour of balance, and not
>>> a bug.
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>
>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>> beginning to think the problem is that balance is based on the rms
>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>> version of rms, and balance should be based (optionally) on that?
>>>> (that way I would not have to set ksmps = 1)
>>>> Or balance should internally use some a-rate interpolation?
>>>> Best regards,
>>>> Søren
>>>>
>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>> which - I now realize - is dependent on ksmps. If I make ksmps smaller
>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>> small bit of distortion.
>>>>>
>>>>> I wonder if this is just a limitation of digital filters - there will
>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>> feasible)
>>>>>
>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>
>>>>> Søren
>>>>>
>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>> Sounds fine here too as far as I can see.... actually seeing more than
>>>>>> listening right now, as I only have the laptop speakers.
>>>>>> Comparing the three different signals (clean from loscil, filtered, and
>>>>>> balanced) show the type of output I would expect from these opcodes.
>>>>>> Could
>>>>>> you describe the artifact you hear more in detail?
>>>>>> best
>>>>>> Oeyvind
>>>>>>
>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>>>>>
>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>> low-pass
>>>>>>> filtered sound
>>>>>>> ========================
>>>>>>> Prof. Victor Lazzarini
>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>> Maynooth University,
>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>> Tel: 00 353 7086936
>>>>>>> Fax: 00 353 1 7086952
>>>>>>>
>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>
>>>>>>>> The 'balance' opcode (also) seems to be introducing some noise, which
>>>>>>>> I
>>>>>>> think
>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>> Windows
>>>>>>>> 10/x64. Can someone please try the following code and confirm whether
>>>>>>> there
>>>>>>>> is a bug?
>>>>>>>>
>>>>>>>> <CsoundSynthesizer>
>>>>>>>> <CsOptions>
>>>>>>>> -o dac
>>>>>>>> </CsOptions>
>>>>>>>> <CsInstruments>
>>>>>>>> sr = 44100
>>>>>>>> ksmps = 32
>>>>>>>> nchnls = 2
>>>>>>>> 0dbfs  = 1
>>>>>>>> instr 1
>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>> ap tone as, 100
>>>>>>>> ap balance ap, as
>>>>>>>> outs ap, ap
>>>>>>>> endin
>>>>>>>> </CsInstruments>
>>>>>>>> <CsScore>
>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>> i 1 0 5
>>>>>>>> e
>>>>>>>> </CsScore>
>>>>>>>> </CsoundSynthesizer>
>>>>>>>>
>>>>>>>> loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>> f1093014.html
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>> Csound mailing list
>>>>>>> [hidden email]
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>        https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Oeyvind Brandtsegg
>>>>>> Professor of Music Technology
>>>>>> NTNU
>>>>>> 7491 Trondheim
>>>>>> Norway
>>>>>> Cell: +47 92 203 205
>>>>>>
>>>>>> http://www.partikkelaudio.com/
>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>> http://gdsp.hf.ntnu.no/
>>>>>> http://soundcloud.com/brandtsegg
>>>>>> http://flyndresang.no/
>>>>>> http://soundcloud.com/t-emp
>>>>>>
>>>>>> Csound mailing list
>>>>>> [hidden email]
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>        https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 13:12:26 +0000
> From:    Peter Burgess <[hidden email]>
> Subject: Re: Noise detection
>
> Right yes, noise is a vague term. For my specific purpose,  I'm thinking
> primarily full spectrum white noise or similar...  In which case you're
> right, examining an FFT probably is the sensible way to go here. The goal
> is to be able to auto detect unwanted white noise in samples and discard
> those containing too much of it.
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 15:34:40 +0100
> From:    joachim heintz <[hidden email]>
> Subject: Re: balance opcode sound artifact
>
> thanks, victor; i think this balance2 is a very good idea anyway.
> joachim
>
>
>
> On 02/03/18 11:06, Victor Lazzarini wrote:
>> I tried your soundfile but could not hear anything (which does not mean it is not there).
>> What I am saying is that the opcode is what it is, it has been used in lots of applications
>> and we should not change its behaviour (backwards compatibility).
>>
>> I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
>> on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
>> as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
>> (way back in MUSIC 11) being the way it is.
>>
>> Once sourceforge is back up and appveyor is building again, you’re welcome to try this
>> opcode (just replace balance by balance2).
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>
>>> Aha! But then what can be causing this noise..? I am using the opcode
>>> exactly as shown - did you try with the soundfile I attached?
>>> If the balance opcode is supposed to add noise, is there perhaps
>>> nother way I can achieve this same effect without added noise? (and
>>> without changing ksmps)
>>> Søren
>>>
>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>> the amplitude changes by interpolating linearly between k-rate
>>>> values.
>>>>
>>>> It could well be that in the particular way you are using you hear
>>>> some artefact. However that’s the behaviour of balance, and not
>>>> a bug.
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>
>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>> beginning to think the problem is that balance is based on the rms
>>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>>> version of rms, and balance should be based (optionally) on that?
>>>>> (that way I would not have to set ksmps = 1)
>>>>> Or balance should internally use some a-rate interpolation?
>>>>> Best regards,
>>>>> Søren
>>>>>
>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps smaller
>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>> small bit of distortion.
>>>>>>
>>>>>> I wonder if this is just a limitation of digital filters - there will
>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>> feasible)
>>>>>>
>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>
>>>>>> Søren
>>>>>>
>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>> Sounds fine here too as far as I can see.... actually seeing more than
>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>> Comparing the three different signals (clean from loscil, filtered, and
>>>>>>> balanced) show the type of output I would expect from these opcodes.
>>>>>>> Could
>>>>>>> you describe the artifact you hear more in detail?
>>>>>>> best
>>>>>>> Oeyvind
>>>>>>>
>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>>>>>>
>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>> low-pass
>>>>>>>> filtered sound
>>>>>>>> ========================
>>>>>>>> Prof. Victor Lazzarini
>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>> Maynooth University,
>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>> Tel: 00 353 7086936
>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>
>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> The 'balance' opcode (also) seems to be introducing some noise, which
>>>>>>>>> I
>>>>>>>> think
>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>> Windows
>>>>>>>>> 10/x64. Can someone please try the following code and confirm whether
>>>>>>>> there
>>>>>>>>> is a bug?
>>>>>>>>>
>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>> <CsOptions>
>>>>>>>>> -o dac
>>>>>>>>> </CsOptions>
>>>>>>>>> <CsInstruments>
>>>>>>>>> sr = 44100
>>>>>>>>> ksmps = 32
>>>>>>>>> nchnls = 2
>>>>>>>>> 0dbfs  = 1
>>>>>>>>> instr 1
>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>> ap tone as, 100
>>>>>>>>> ap balance ap, as
>>>>>>>>> outs ap, ap
>>>>>>>>> endin
>>>>>>>>> </CsInstruments>
>>>>>>>>> <CsScore>
>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>> i 1 0 5
>>>>>>>>> e
>>>>>>>>> </CsScore>
>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>
>>>>>>>>> loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>> f1093014.html
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Oeyvind Brandtsegg
>>>>>>> Professor of Music Technology
>>>>>>> NTNU
>>>>>>> 7491 Trondheim
>>>>>>> Norway
>>>>>>> Cell: +47 92 203 205
>>>>>>>
>>>>>>> http://www.partikkelaudio.com/
>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>> http://flyndresang.no/
>>>>>>> http://soundcloud.com/t-emp
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> [hidden email]
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>        https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>        https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 15:41:28 +0000
> From:    Søren Jakobsen <[hidden email]>
> Subject: Re: balance opcode sound artifact
>
> Sounds great, thanks - looking forward to the next successful build:)
>
> On 3/2/18, joachim heintz <[hidden email]> wrote:
>> thanks, victor; i think this balance2 is a very good idea anyway.
>> joachim
>>
>>
>>
>> On 02/03/18 11:06, Victor Lazzarini wrote:
>>> I tried your soundfile but could not hear anything (which does not mean it
>>> is not there).
>>> What I am saying is that the opcode is what it is, it has been used in
>>> lots of applications
>>> and we should not change its behaviour (backwards compatibility).
>>>
>>> I have added a balance2 opcode (untested yet) that calculates the
>>> amplitude scaling
>>> on a sample-by-sample basis. It is slightly more (but I expect not too
>>> much) expensive,
>>> as it calls a sqrt() per sample. I suspect this saving was the original
>>> motivation for balance
>>> (way back in MUSIC 11) being the way it is.
>>>
>>> Once sourceforge is back up and appveyor is building again, you’re welcome
>>> to try this
>>> opcode (just replace balance by balance2).
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>>
>>>> Aha! But then what can be causing this noise..? I am using the opcode
>>>> exactly as shown - did you try with the soundfile I attached?
>>>> If the balance opcode is supposed to add noise, is there perhaps
>>>> nother way I can achieve this same effect without added noise? (and
>>>> without changing ksmps)
>>>> Søren
>>>>
>>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>>> the amplitude changes by interpolating linearly between k-rate
>>>>> values.
>>>>>
>>>>> It could well be that in the particular way you are using you hear
>>>>> some artefact. However that’s the behaviour of balance, and not
>>>>> a bug.
>>>>> ========================
>>>>> Prof. Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>>
>>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>>> beginning to think the problem is that balance is based on the rms
>>>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>>>> version of rms, and balance should be based (optionally) on that?
>>>>>> (that way I would not have to set ksmps = 1)
>>>>>> Or balance should internally use some a-rate interpolation?
>>>>>> Best regards,
>>>>>> Søren
>>>>>>
>>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps
>>>>>>> smaller
>>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>>> small bit of distortion.
>>>>>>>
>>>>>>> I wonder if this is just a limitation of digital filters - there will
>>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>>> feasible)
>>>>>>>
>>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>>
>>>>>>> Søren
>>>>>>>
>>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>>> Sounds fine here too as far as I can see.... actually seeing more
>>>>>>>> than
>>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>>> Comparing the three different signals (clean from loscil, filtered,
>>>>>>>> and
>>>>>>>> balanced) show the type of output I would expect from these opcodes.
>>>>>>>> Could
>>>>>>>> you describe the artifact you hear more in detail?
>>>>>>>> best
>>>>>>>> Oeyvind
>>>>>>>>
>>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini
>>>>>>>> <[hidden email]>:
>>>>>>>>
>>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>>> low-pass
>>>>>>>>> filtered sound
>>>>>>>>> ========================
>>>>>>>>> Prof. Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>>> Maynooth University,
>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>
>>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>>
>>>>>>>>>> The 'balance' opcode (also) seems to be introducing some noise,
>>>>>>>>>> which
>>>>>>>>>> I
>>>>>>>>> think
>>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>>> Windows
>>>>>>>>>> 10/x64. Can someone please try the following code and confirm
>>>>>>>>>> whether
>>>>>>>>> there
>>>>>>>>>> is a bug?
>>>>>>>>>>
>>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>>> <CsOptions>
>>>>>>>>>> -o dac
>>>>>>>>>> </CsOptions>
>>>>>>>>>> <CsInstruments>
>>>>>>>>>> sr = 44100
>>>>>>>>>> ksmps = 32
>>>>>>>>>> nchnls = 2
>>>>>>>>>> 0dbfs  = 1
>>>>>>>>>> instr 1
>>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>>> ap tone as, 100
>>>>>>>>>> ap balance ap, as
>>>>>>>>>> outs ap, ap
>>>>>>>>>> endin
>>>>>>>>>> </CsInstruments>
>>>>>>>>>> <CsScore>
>>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>>> i 1 0 5
>>>>>>>>>> e
>>>>>>>>>> </CsScore>
>>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>>
>>>>>>>>>> loop.wav
>>>>>>>>>> <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>>> f1093014.html
>>>>>>>>>> Csound mailing list
>>>>>>>>>> [hidden email]
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Oeyvind Brandtsegg
>>>>>>>> Professor of Music Technology
>>>>>>>> NTNU
>>>>>>>> 7491 Trondheim
>>>>>>>> Norway
>>>>>>>> Cell: +47 92 203 205
>>>>>>>>
>>>>>>>> http://www.partikkelaudio.com/
>>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>>> http://flyndresang.no/
>>>>>>>> http://soundcloud.com/t-emp
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>> Csound mailing list
>>>>>> [hidden email]
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>        https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 10:47:00 -0500
> From:    "Dr. Richard Boulanger" <[hidden email]>
> Subject: Re: balance opcode sound artifact
>
> balance2 will be a nice addition.  Thanks
>
> Sent from my iPhone
>
>> On Mar 2, 2018, at 5:06 AM, Victor Lazzarini <[hidden email]> wrote:
>>
>> I tried your soundfile but could not hear anything (which does not mean it is not there).
>> What I am saying is that the opcode is what it is, it has been used in lots of applications
>> and we should not change its behaviour (backwards compatibility).
>>
>> I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
>> on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
>> as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
>> (way back in MUSIC 11) being the way it is.
>>
>> Once sourceforge is back up and appveyor is building again, you’re welcome to try this
>> opcode (just replace balance by balance2).
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>
>>> Aha! But then what can be causing this noise..? I am using the opcode
>>> exactly as shown - did you try with the soundfile I attached?
>>> If the balance opcode is supposed to add noise, is there perhaps
>>> nother way I can achieve this same effect without added noise? (and
>>> without changing ksmps)
>>> Søren
>>>
>>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>> the amplitude changes by interpolating linearly between k-rate
>>>> values.
>>>>
>>>> It could well be that in the particular way you are using you hear
>>>> some artefact. However that’s the behaviour of balance, and not
>>>> a bug.
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>
>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>> beginning to think the problem is that balance is based on the rms
>>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>>> version of rms, and balance should be based (optionally) on that?
>>>>> (that way I would not have to set ksmps = 1)
>>>>> Or balance should internally use some a-rate interpolation?
>>>>> Best regards,
>>>>> Søren
>>>>>
>>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps smaller
>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>> small bit of distortion.
>>>>>>
>>>>>> I wonder if this is just a limitation of digital filters - there will
>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>> feasible)
>>>>>>
>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>
>>>>>> Søren
>>>>>>
>>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>> Sounds fine here too as far as I can see.... actually seeing more than
>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>> Comparing the three different signals (clean from loscil, filtered, and
>>>>>>> balanced) show the type of output I would expect from these opcodes.
>>>>>>> Could
>>>>>>> you describe the artifact you hear more in detail?
>>>>>>> best
>>>>>>> Oeyvind
>>>>>>>
>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>>>>>>
>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>> low-pass
>>>>>>>> filtered sound
>>>>>>>> ========================
>>>>>>>> Prof. Victor Lazzarini
>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>> Maynooth University,
>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>> Tel: 00 353 7086936
>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>
>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> The 'balance' opcode (also) seems to be introducing some noise, which
>>>>>>>>> I
>>>>>>>> think
>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>> Windows
>>>>>>>>> 10/x64. Can someone please try the following code and confirm whether
>>>>>>>> there
>>>>>>>>> is a bug?
>>>>>>>>>
>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>> <CsOptions>
>>>>>>>>> -o dac
>>>>>>>>> </CsOptions>
>>>>>>>>> <CsInstruments>
>>>>>>>>> sr = 44100
>>>>>>>>> ksmps = 32
>>>>>>>>> nchnls = 2
>>>>>>>>> 0dbfs  = 1
>>>>>>>>> instr 1
>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>> ap tone as, 100
>>>>>>>>> ap balance ap, as
>>>>>>>>> outs ap, ap
>>>>>>>>> endin
>>>>>>>>> </CsInstruments>
>>>>>>>>> <CsScore>
>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>> i 1 0 5
>>>>>>>>> e
>>>>>>>>> </CsScore>
>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>
>>>>>>>>> loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>> f1093014.html
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Oeyvind Brandtsegg
>>>>>>> Professor of Music Technology
>>>>>>> NTNU
>>>>>>> 7491 Trondheim
>>>>>>> Norway
>>>>>>> Cell: +47 92 203 205
>>>>>>>
>>>>>>> http://www.partikkelaudio.com/
>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>> http://flyndresang.no/
>>>>>>> http://soundcloud.com/t-emp
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> [hidden email]
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>       https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>       https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 17:22:44 +0100
> From:    Rene <[hidden email]>
> Subject: --realtime flag
>
> Hello,
>
> Instruments using reinit opcode and --realtime flag seems to have a faulty
> behavior.
> The reinit is done for the complete instrument regardless of the reinit
> label and rireturn locations.
>
> (The included reinit.csd instrument prints Hello at every reinit)
>
> I am on linux, csound 6.10.0
>
> Is it normal?
>
>
>
> Best,
> René
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 17:52:13 +0100
> From:    Oeyvind Brandtsegg <[hidden email]>
> Subject: Re: Noise detection
>
> Spectral flatness or flux might be useable indicators in this case.
> If you need an example of how to implement it you could look at the code at
> https://github.com/Oeyvind/featexmod in the file analyze_audio.inc
>
> Best
> Oeyvind
>
>
> On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>
> wrote:
>
>> Right yes, noise is a vague term. For my specific purpose,  I'm thinking
>> primarily full spectrum white noise or similar...  In which case you're
>> right, examining an FFT probably is the sensible way to go here. The goal
>> is to be able to auto detect unwanted white noise in samples and discard
>> those containing too much of it.
>> Csound mailing list [hidden email] https://listserv.heanet.ie/
>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>> csound/issues Discussions of bugs and features can be posted here
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 17:07:04 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: --realtime flag
>
> It could be a bug.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 2 Mar 2018, at 16:23, Rene <[hidden email]<mailto:[hidden email]>> wrote:
>
> Hello,
>
> Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
> The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.
>
> (The included reinit.csd instrument prints Hello at every reinit)
>
> I am on linux, csound 6.10.0
>
> Is it normal?
>
> Best,
> René
> Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
> <reinit.csd>
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 17:48:33 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: --realtime flag
>
> Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]<mailto:[hidden email]>> wrote:
>
> It could be a bug.
>
> Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy
> Maynooth University
> Ireland
>
> On 2 Mar 2018, at 16:23, Rene <[hidden email]<mailto:[hidden email]>> wrote:
>
> Hello,
>
> Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
> The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.
>
> (The included reinit.csd instrument prints Hello at every reinit)
>
> I am on linux, csound 6.10.0
>
> Is it normal?
>
> Best,
> René
> Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
> <reinit.csd>
> Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 20:20:01 +0200
> From:    Tarmo Johannes <[hidden email]>
> Subject: Re: Noise detection
>
> Hi,
>
> This is probably not you are after but (from the manual):
>
> http://www.csounds.com/manual/html/pvstencil.html
> One of the typical uses of /pvstencil/ would be in noise reduction.
>
> Maybe you can reverse it somehow to get the noise level?
> "Skipping post-normalisation will keep the original noise print average amplitudes."
>
> I don't pretend I understand exactly how it is used.
>
> tarmo
>
> On reede, 2. märts 2018 18:52.13 EET you wrote:
>> Spectral flatness or flux might be useable indicators in this case.
>> If you need an example of how to implement it you could look at the code at
>> https://github.com/Oeyvind/featexmod in the file analyze_audio.inc
>>
>> Best
>> Oeyvind
>>
>>
>> On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>
>>
>> wrote:
>>> Right yes, noise is a vague term. For my specific purpose,  I'm thinking
>>> primarily full spectrum white noise or similar...  In which case you're
>>> right, examining an FFT probably is the sensible way to go here. The goal
>>> is to be able to auto detect unwanted white noise in samples and discard
>>> those containing too much of it.
>>> Csound mailing list [hidden email] https://listserv.heanet.ie/
>>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>>> csound/issues Discussions of bugs and features can be posted here
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 20:26:03 +0100
> From:    Rene <[hidden email]>
> Subject: Re: --realtime flag
>
> Hello,
>
> Tanks for your answer.
>
> I have tested from git (today download)
>
> csound-master : give same bug as 6.10.0
>
> csound-develop and csound-feature-realtime : (may be wrong version, i can't
> find 6.11)
> For both i can't test because i got a continuous message
>
> WARNING: instr 0 uses 3 p-fields but is given 0
>
> then csound hang.
>
>
> Best,
> René
>
>
>
>
>
>
>
>
> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>
>> Actually, can you try the latest (6.11)? This version has a completely
>> overhauled realtime mode, and I remembered testing reinit and it worked.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:
>>
>> It could be a bug.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>
>> Hello,
>>
>> Instruments using reinit opcode and --realtime flag seems to have a faulty
>> behavior.
>> The reinit is done for the complete instrument regardless of the reinit
>> label and rireturn locations.
>>
>> (The included reinit.csd instrument prints Hello at every reinit)
>>
>> I am on linux, csound 6.10.0
>>
>> Is it normal?
>>
>>
>>
>> Best,
>> René
>> Csound mailing list [hidden email] https://listserv.heanet.ie/
>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>> csound/issues Discussions of bugs and features can be posted here
>>
>> <reinit.csd>
>>
>> Csound mailing list [hidden email] https://listserv.heanet.ie/
>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>> csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list [hidden email] https://listserv.heanet.ie/
>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>> csound/issues Discussions of bugs and features can be posted here
>>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 20:03:41 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: --realtime flag
>
> The master branch is 6.10, old code. The develop branch is 6.11, e.g.
>
> Csound version 6.11 beta (double samples) Mar  1 2018
>
> Feature-realtime has been merged into develop, so that would have similar
> code.
>
> I tested your code and I am getting the WARNING, which I think it is a
> bug in the latest checked in code. That problem is there with or without
> —reatlime
>
> Once that is fixed, you can test it again.
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:
>>
>> Hello,
>>
>> Tanks for your answer.
>>  
>> I have tested from git (today download)
>>
>> csound-master : give same bug as 6.10.0
>>
>> csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
>> For both i can't test because i got a continuous message
>>
>> WARNING: instr 0 uses 3 p-fields but is given 0
>>
>> then csound hang.
>>
>>
>> Best,
>> René
>>
>>
>>
>>
>>
>>
>>
>>
>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>> Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:
>>
>>> It could be a bug.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>
>>>> Hello,
>>>>
>>>> Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
>>>> The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.
>>>>
>>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>>
>>>> I am on linux, csound 6.10.0
>>>>
>>>> Is it normal?
>>>>
>>>> Best,
>>>> René
>>>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>>> <reinit.csd>
>>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 20:09:04 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: --realtime flag
>
> actually, it’s a problem with realtime. I’ll fix it. I think it is to do with
> timout, not reinit.
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:
>>
>> Hello,
>>
>> Tanks for your answer.
>>  
>> I have tested from git (today download)
>>
>> csound-master : give same bug as 6.10.0
>>
>> csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
>> For both i can't test because i got a continuous message
>>
>> WARNING: instr 0 uses 3 p-fields but is given 0
>>
>> then csound hang.
>>
>>
>> Best,
>> René
>>
>>
>>
>>
>>
>>
>>
>>
>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>> Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:
>>
>>> It could be a bug.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>
>>>> Hello,
>>>>
>>>> Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
>>>> The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.
>>>>
>>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>>
>>>> I am on linux, csound 6.10.0
>>>>
>>>> Is it normal?
>>>>
>>>> Best,
>>>> René
>>>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>>> <reinit.csd>
>>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> Date:    Fri, 2 Mar 2018 21:29:44 +0000
> From:    Victor Lazzarini <[hidden email]>
> Subject: Re: --realtime flag
>
> I have fixed this now (in git develop), but there are a couple of caveats:
>
> 1) reinit should be avoided in --realtime mode: it stops performance to
> run a reinit pass, and that is not a good idea. Even though it runs the
> reinit on a separate thread, performance has to pause for reinitialisation.
>
> 2) opcodes like timeout would potentially have gaps in their time counting
> due to the reinit pause.
>
> In other words: although the instrument will work (with maybe some timout
> time counting issues), it’s not a good realtime instrument.
>
> ========================
> Prof. Victor Lazzarini
> Dean of Arts, Celtic Studies, and Philosophy,
> Maynooth University,
> Maynooth, Co Kildare, Ireland
> Tel: 00 353 7086936
> Fax: 00 353 1 7086952
>
>> On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:
>>
>> Hello,
>>
>> Tanks for your answer.
>>  
>> I have tested from git (today download)
>>
>> csound-master : give same bug as 6.10.0
>>
>> csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
>> For both i can't test because i got a continuous message
>>
>> WARNING: instr 0 uses 3 p-fields but is given 0
>>
>> then csound hang.
>>
>>
>> Best,
>> René
>>
>>
>>
>>
>>
>>
>>
>>
>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>> Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:
>>
>>> It could be a bug.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>
>>>> Hello,
>>>>
>>>> Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
>>>> The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.
>>>>
>>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>>
>>>> I am on linux, csound 6.10.0
>>>>
>>>> Is it normal?
>>>>
>>>> Best,
>>>> René
>>>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>>> <reinit.csd>
>>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>>
>> Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>          https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>
> ------------------------------
>
> End of CSOUND Digest - 1 Mar 2018 to 2 Mar 2018 (#2018-58)
> **********************************************************
>

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

rorywalsh
Hi Jan, are you building from the master branch, 6.10? I built on a fresh Linux machine some days ago without any problems. Can't vouch for the dev branch though. 

On 3 Mar 2018 7:59 a.m., "Jan Jacob Hofmann" <[hidden email]> wrote:
Dear list,

As I built my Csound on Ubuntu more than one year ago, I would like to update it to the current version (master). Mostly everything works fine but I do get an error message regarding "SWIG" and something related to that seems to cause an error in the cmake build process. I am not sure what to do now, as the SWIG-version seems to be all right: "found suitable version "2.0.11", minimum required is "2.0""

I placed the relevant excerpt of the messages below. Maybe someone has an idea what causes that error and what I could do to overcome it?

Best regards,

Jan Jacob


[...]

-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11", minimum required is "2.0")

-- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so

-- BUILD_PYTHON_INTERFACE is enabled.

-- BUILD_JAVA_INTERFACE is enabled.

-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_INTERFACE

-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE

-- BUILD_LUA_INTERFACE is disabled.

-- SWIG_USE_FILE:

CMake Error at interfaces/CMakeLists.txt:92 (include):

include called with wrong number of arguments. include() only takes one

file.



CMake Error at interfaces/CMakeLists.txt:112 (swig_add_module):

Unknown CMake command "swig_add_module".



-- Configuring incomplete, errors occurred!


[...]



sound      |      movement       |       object      |      space
sonic architecture     |      site: http://www.sonicarchitecture.de
spatial electronic composition    |    higher order ambisonic music

Am 03.03.2018 um 01:00 schrieb CSOUND automatic digest system:
There are 17 messages totaling 2115 lines in this issue.

Topics of the day:

   1. Redefining f signals (3)
   2. balance opcode sound artifact (4)
   3. Noise detection (3)
   4. --realtime flag (7)

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

----------------------------------------------------------------------

Date:    Fri, 2 Mar 2018 00:05:04 +0000
From:    jpff <[hidden email]>
Subject: Re: Redefining f signals

Two thoughts;
1: That ought to work
2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not
work?


On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:

Hello,

I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.

If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.

I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.

I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
Do you have some advice on how to handle a chain of optional f-signal processings?

Best
Ruben


if (ifile1ch==1.000) goto monopvsanal
monopvsanal:
fsig1   pvsanal         apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
goto postpvsanal
postpvsanal:

if (iwanttoskipsecondpitch==1) goto postpvscale
if (ifile1ch==1.000) goto monopvscale
monopvscale:
fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
fsig1= fsig101
goto postpvscale
postpvscale:

;etc…add 10 similar modules

if (ifile1ch==1.000) goto monopvsynth
monopvsynth:
a2ambL  pvsynth         fsig1
goto spatialization

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues

------------------------------

Date:    Fri, 2 Mar 2018 00:07:55 +0000
From:    jpff <[hidden email]>
Subject: Re: Redefining f signals

and...

if (ifile1ch==1.000) goto monopvscale
monopvscale:

does not make much sense, ad yourtests/goto seem to be all i-rate so do
not affect perf time
xy

On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:

Hello,

I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.

If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.

I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.

I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
Do you have some advice on how to handle a chain of optional f-signal processings?

Best
Ruben


if (ifile1ch==1.000) goto monopvsanal
monopvsanal:
fsig1   pvsanal         apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
goto postpvsanal
postpvsanal:

if (iwanttoskipsecondpitch==1) goto postpvscale
if (ifile1ch==1.000) goto monopvscale
monopvscale:
fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
fsig1= fsig101
goto postpvscale
postpvscale:

;etc…add 10 similar modules

if (ifile1ch==1.000) goto monopvsynth
monopvsynth:
a2ambL  pvsynth         fsig1
goto spatialization

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues

------------------------------

Date:    Fri, 2 Mar 2018 10:00:08 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: Redefining f signals

The manual notes that some opcodes have side effects on inputs, so re-using the variable should not
be taken for granted. Check the man page.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 00:05, jpff <[hidden email]> wrote:

Two thoughts;
1: That ought to work
2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not work?


On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:

Hello,

I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.

If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.

I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.

I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
Do you have some advice on how to handle a chain of optional f-signal processings?

Best
Ruben


if (ifile1ch==1.000) goto monopvsanal
monopvsanal:
fsig1   pvsanal         apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
goto postpvsanal
postpvsanal:

if (iwanttoskipsecondpitch==1) goto postpvscale
if (ifile1ch==1.000) goto monopvscale
monopvscale:
fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
fsig1= fsig101
goto postpvscale
postpvscale:

;etc…add 10 similar modules

if (ifile1ch==1.000) goto monopvsynth
monopvsynth:
a2ambL  pvsynth         fsig1
goto spatialization

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 10:06:21 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: balance opcode sound artifact

I tried your soundfile but could not hear anything (which does not mean it is not there).
What I am saying is that the opcode is what it is, it has been used in lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered, and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise, which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: <a href="tel:%2B47%2092%20203%20205" value="+4792203205" target="_blank">+47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 13:12:26 +0000
From:    Peter Burgess <[hidden email]>
Subject: Re: Noise detection

Right yes, noise is a vague term. For my specific purpose,  I'm thinking
primarily full spectrum white noise or similar...  In which case you're
right, examining an FFT probably is the sensible way to go here. The goal
is to be able to auto detect unwanted white noise in samples and discard
those containing too much of it.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 15:34:40 +0100
From:    joachim heintz <[hidden email]>
Subject: Re: balance opcode sound artifact

thanks, victor; i think this balance2 is a very good idea anyway.
        joachim



On 02/03/18 11:06, Victor Lazzarini wrote:
I tried your soundfile but could not hear anything (which does not mean it is not there).
What I am saying is that the opcode is what it is, it has been used in lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered, and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise, which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: <a href="tel:%2B47%2092%20203%20205" value="+4792203205" target="_blank">+47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 15:41:28 +0000
From:    Søren Jakobsen <[hidden email]>
Subject: Re: balance opcode sound artifact

Sounds great, thanks - looking forward to the next successful build:)

On 3/2/18, joachim heintz <[hidden email]> wrote:
thanks, victor; i think this balance2 is a very good idea anyway.
        joachim



On 02/03/18 11:06, Victor Lazzarini wrote:
I tried your soundfile but could not hear anything (which does not mean it
is not there).
What I am saying is that the opcode is what it is, it has been used in
lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the
amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too
much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original
motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome
to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps
smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more
than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered,
and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini
<[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise,
which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm
whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav
<http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: <a href="tel:%2B47%2092%20203%20205" value="+4792203205" target="_blank">+47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 10:47:00 -0500
From:    "Dr. Richard Boulanger" <[hidden email]>
Subject: Re: balance opcode sound artifact

balance2 will be a nice addition.  Thanks

Sent from my iPhone

On Mar 2, 2018, at 5:06 AM, Victor Lazzarini <[hidden email]> wrote:

I tried your soundfile but could not hear anything (which does not mean it is not there).
What I am saying is that the opcode is what it is, it has been used in lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered, and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise, which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
     https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: <a href="tel:%2B47%2092%20203%20205" value="+4792203205" target="_blank">+47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 17:22:44 +0100
From:    Rene <[hidden email]>
Subject: --realtime flag

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty
behavior.
The reinit is done for the complete instrument regardless of the reinit
label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?



Best,
René

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 17:52:13 +0100
From:    Oeyvind Brandtsegg <[hidden email]>
Subject: Re: Noise detection

Spectral flatness or flux might be useable indicators in this case.
If you need an example of how to implement it you could look at the code at
https://github.com/Oeyvind/featexmod in the file analyze_audio.inc

Best
Oeyvind


On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>
wrote:

Right yes, noise is a vague term. For my specific purpose,  I'm thinking
primarily full spectrum white noise or similar...  In which case you're
right, examining an FFT probably is the sensible way to go here. The goal
is to be able to auto detect unwanted white noise in samples and discard
those containing too much of it.
Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 17:07:04 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]<mailto:[hidden email]>> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues

------------------------------

Date:    Fri, 2 Mar 2018 17:48:33 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]<mailto:[hidden email]>> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]<mailto:[hidden email]>> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features

------------------------------

Date:    Fri, 2 Mar 2018 20:20:01 +0200
From:    Tarmo Johannes <[hidden email]>
Subject: Re: Noise detection

Hi,

This is probably not you are after but (from the manual):

http://www.csounds.com/manual/html/pvstencil.html
One of the typical uses of /pvstencil/ would be in noise reduction.

Maybe you can reverse it somehow to get the noise level?
"Skipping post-normalisation will keep the original noise print average amplitudes."

I don't pretend I understand exactly how it is used.

tarmo

On reede, 2. märts 2018 18:52.13 EET you wrote:
Spectral flatness or flux might be useable indicators in this case.
If you need an example of how to implement it you could look at the code at
https://github.com/Oeyvind/featexmod in the file analyze_audio.inc

Best
Oeyvind


On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>

wrote:
Right yes, noise is a vague term. For my specific purpose,  I'm thinking
primarily full spectrum white noise or similar...  In which case you're
right, examining an FFT probably is the sensible way to go here. The goal
is to be able to auto detect unwanted white noise in samples and discard
those containing too much of it.
Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 20:26:03 +0100
From:    Rene <[hidden email]>
Subject: Re: --realtime flag

Hello,

Tanks for your answer.

I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't
find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

Actually, can you try the latest (6.11)? This version has a completely
overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty
behavior.
The reinit is done for the complete instrument regardless of the reinit
label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?



Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here

<reinit.csd>

Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 20:03:41 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

The master branch is 6.10, old code. The develop branch is 6.11, e.g.

Csound version 6.11 beta (double samples) Mar  1 2018

Feature-realtime has been merged into develop, so that would have similar
code.

I tested your code and I am getting the WARNING, which I think it is a
bug in the latest checked in code. That problem is there with or without
—reatlime

Once that is fixed, you can test it again.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:

Hello,

Tanks for your answer.
  I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 20:09:04 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

actually, it’s a problem with realtime. I’ll fix it. I think it is to do with
timout, not reinit.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:

Hello,

Tanks for your answer.
  I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 21:29:44 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

I have fixed this now (in git develop), but there are a couple of caveats:

1) reinit should be avoided in --realtime mode: it stops performance to
run a reinit pass, and that is not a good idea. Even though it runs the
reinit on a separate thread, performance has to pause for reinitialisation.

2) opcodes like timeout would potentially have gaps in their time counting
due to the reinit pause.

In other words: although the instrument will work (with maybe some timout
time counting issues), it’s not a good realtime instrument.

========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:

Hello,

Tanks for your answer.
  I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

End of CSOUND Digest - 1 Mar 2018 to 2 Mar 2018 (#2018-58)
**********************************************************


Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
In reply to this post by Jan Jacob Hofmann
Dear Rory,

I *guess* I built the master branch of Csound 6.10:

Here is basically what I typed into terminal:

git pull
git branch
git checkout master


And here is a part of the result. I am not sure, if it is the master
branch though (see messages below)...

Best,

Jan Jacob

janjacobhofmann@janjacobhofmann-ThinkPad-T430:~/csound/csound$ git pull
remote: Counting objects: 17475, done.
remote: Compressing objects: 100% (60/60), done.
remote: Total 17475 (delta 8089), reused 8104 (delta 8073), pack-reused 9342
Empfange Objekte: 100% (17475/17475), 10.34 MiB | 1.42 MiB/s, Fertig.
Löse Unterschiede auf: 100% (13708/13708), abgeschlossen mit 1329
lokalen Objekten.
Von https://github.com/csound/csound
    2ef3d7c..a35793a  develop    -> origin/develop
    df47cff..e33b6bd  coverity_scan -> origin/coverity_scan
  * [neuer Branch]    feature/googletest -> origin/feature/googletest
  * [neuer Branch]    feature/midiex -> origin/feature/midiex
  * [neuer Branch]    feature/oboe -> origin/feature/oboe
    828b955..de5933a  feature/parser3 -> origin/feature/parser3
  * [neuer Branch]    feature/realtime -> origin/feature/realtime
    2645994..f5bcd83  master     -> origin/master
  * [neues Tag]       6.08.0     -> 6.08.0
  * [neues Tag]       6.08.1     -> 6.08.1
  * [neues Tag]       6.09.0     -> 6.09.0
  * [neues Tag]       6.09.1     -> 6.09.1
  * [neues Tag]       6.10.0     -> 6.10.0
  * [neues Tag]       6.10.0-1   -> 6.10.0-1
  * [neues Tag]       b6.08.0    -> b6.08.0
  * [neues Tag]       csound6.02.beta2 -> csound6.02.b




Subject: Re: Building (updating) Csound on Ubuntu 16.04 - some advice sought

From: Rory Walsh <[hidden email]>

Reply-To:A discussion list for users of Csound <[hidden email]>

Date: Sat, 3 Mar 2018 09:02:47 +0000

Content-Type: multipart/alternative

Hi Jan, are you building from the master branch, 6.10? I built on a
fresh Linux machine some days ago without any problems. Can't vouch for
the dev branch though.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Michael Gogins-2
In reply to this post by Jan Jacob Hofmann
Cmake version?

On Mar 3, 2018 04:58, "Jan Jacob Hofmann" <[hidden email]> wrote:
Dear list,

As I built my Csound on Ubuntu more than one year ago, I would like to update it to the current version (master). Mostly everything works fine but I do get an error message regarding "SWIG" and something related to that seems to cause an error in the cmake build process. I am not sure what to do now, as the SWIG-version seems to be all right: "found suitable version "2.0.11", minimum required is "2.0""

I placed the relevant excerpt of the messages below. Maybe someone has an idea what causes that error and what I could do to overcome it?

Best regards,

Jan Jacob


[...]

-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11", minimum required is "2.0")

-- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so

-- BUILD_PYTHON_INTERFACE is enabled.

-- BUILD_JAVA_INTERFACE is enabled.

-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_INTERFACE

-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE

-- BUILD_LUA_INTERFACE is disabled.

-- SWIG_USE_FILE:

CMake Error at interfaces/CMakeLists.txt:92 (include):

include called with wrong number of arguments. include() only takes one

file.



CMake Error at interfaces/CMakeLists.txt:112 (swig_add_module):

Unknown CMake command "swig_add_module".



-- Configuring incomplete, errors occurred!


[...]



sound      |      movement       |       object      |      space
sonic architecture     |      site: http://www.sonicarchitecture.de
spatial electronic composition    |    higher order ambisonic music

Am 03.03.2018 um 01:00 schrieb CSOUND automatic digest system:
There are 17 messages totaling 2115 lines in this issue.

Topics of the day:

   1. Redefining f signals (3)
   2. balance opcode sound artifact (4)
   3. Noise detection (3)
   4. --realtime flag (7)

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

----------------------------------------------------------------------

Date:    Fri, 2 Mar 2018 00:05:04 +0000
From:    jpff <[hidden email]>
Subject: Re: Redefining f signals

Two thoughts;
1: That ought to work
2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not
work?


On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:

Hello,

I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.

If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.

I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.

I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
Do you have some advice on how to handle a chain of optional f-signal processings?

Best
Ruben


if (ifile1ch==1.000) goto monopvsanal
monopvsanal:
fsig1   pvsanal         apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
goto postpvsanal
postpvsanal:

if (iwanttoskipsecondpitch==1) goto postpvscale
if (ifile1ch==1.000) goto monopvscale
monopvscale:
fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
fsig1= fsig101
goto postpvscale
postpvscale:

;etc…add 10 similar modules

if (ifile1ch==1.000) goto monopvsynth
monopvsynth:
a2ambL  pvsynth         fsig1
goto spatialization

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues

------------------------------

Date:    Fri, 2 Mar 2018 00:07:55 +0000
From:    jpff <[hidden email]>
Subject: Re: Redefining f signals

and...

if (ifile1ch==1.000) goto monopvscale
monopvscale:

does not make much sense, ad yourtests/goto seem to be all i-rate so do
not affect perf time
xy

On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:

Hello,

I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.

If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.

I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.

I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
Do you have some advice on how to handle a chain of optional f-signal processings?

Best
Ruben


if (ifile1ch==1.000) goto monopvsanal
monopvsanal:
fsig1   pvsanal         apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
goto postpvsanal
postpvsanal:

if (iwanttoskipsecondpitch==1) goto postpvscale
if (ifile1ch==1.000) goto monopvscale
monopvscale:
fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
fsig1= fsig101
goto postpvscale
postpvscale:

;etc…add 10 similar modules

if (ifile1ch==1.000) goto monopvsynth
monopvsynth:
a2ambL  pvsynth         fsig1
goto spatialization

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues

------------------------------

Date:    Fri, 2 Mar 2018 10:00:08 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: Redefining f signals

The manual notes that some opcodes have side effects on inputs, so re-using the variable should not
be taken for granted. Check the man page.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 00:05, jpff <[hidden email]> wrote:

Two thoughts;
1: That ought to work
2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not work?


On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:

Hello,

I have a question about use of the f-signals. I would like to create an instrument with a long chain of processes to be turned on and off by score parameters, and finally resynthesize the signal going through selected process.

If the analyzed signal is fsig1, I have to redefine it to fsig101 to avoid trouble. Still I would like to keep working on fsig1 through the various processes and resynthesize it as fsig1. If not the number of possible scenarios and combinations would grow enourmously depending on which processes are used.

I try to redefine fsig1 this way: fsig1=fsig101, to bring the result of scaling as input fsig1 to the next process. But this doesn’t work, Csound gets stuck at the first note and doesn’t seem to progress at all.

I include just some example lines from the csd to show the idea. I could include the whole file, but it’s long and messy.
Do you have some advice on how to handle a chain of optional f-signal processings?

Best
Ruben


if (ifile1ch==1.000) goto monopvsanal
monopvsanal:
fsig1   pvsanal         apostwarpL, ipvsfftsize, ipvsoverlap, ipvwinsize, ipvswintype
goto postpvsanal
postpvsanal:

if (iwanttoskipsecondpitch==1) goto postpvscale
if (ifile1ch==1.000) goto monopvscale
monopvscale:
fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
fsig1= fsig101
goto postpvscale
postpvscale:

;etc…add 10 similar modules

if (ifile1ch==1.000) goto monopvsynth
monopvsynth:
a2ambL  pvsynth         fsig1
goto spatialization

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 10:06:21 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: balance opcode sound artifact

I tried your soundfile but could not hear anything (which does not mean it is not there).
What I am saying is that the opcode is what it is, it has been used in lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered, and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise, which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 13:12:26 +0000
From:    Peter Burgess <[hidden email]>
Subject: Re: Noise detection

Right yes, noise is a vague term. For my specific purpose,  I'm thinking
primarily full spectrum white noise or similar...  In which case you're
right, examining an FFT probably is the sensible way to go here. The goal
is to be able to auto detect unwanted white noise in samples and discard
those containing too much of it.

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 15:34:40 +0100
From:    joachim heintz <[hidden email]>
Subject: Re: balance opcode sound artifact

thanks, victor; i think this balance2 is a very good idea anyway.
        joachim



On 02/03/18 11:06, Victor Lazzarini wrote:
I tried your soundfile but could not hear anything (which does not mean it is not there).
What I am saying is that the opcode is what it is, it has been used in lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered, and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise, which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 15:41:28 +0000
From:    Søren Jakobsen <[hidden email]>
Subject: Re: balance opcode sound artifact

Sounds great, thanks - looking forward to the next successful build:)

On 3/2/18, joachim heintz <[hidden email]> wrote:
thanks, victor; i think this balance2 is a very good idea anyway.
        joachim



On 02/03/18 11:06, Victor Lazzarini wrote:
I tried your soundfile but could not hear anything (which does not mean it
is not there).
What I am saying is that the opcode is what it is, it has been used in
lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the
amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too
much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original
motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome
to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps
smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more
than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered,
and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini
<[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise,
which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm
whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav
<http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 10:47:00 -0500
From:    "Dr. Richard Boulanger" <[hidden email]>
Subject: Re: balance opcode sound artifact

balance2 will be a nice addition.  Thanks

Sent from my iPhone

On Mar 2, 2018, at 5:06 AM, Victor Lazzarini <[hidden email]> wrote:

I tried your soundfile but could not hear anything (which does not mean it is not there).
What I am saying is that the opcode is what it is, it has been used in lots of applications
and we should not change its behaviour (backwards compatibility).

I have added a balance2 opcode (untested yet) that calculates the amplitude scaling
on a sample-by-sample basis. It is slightly more (but I expect not too much) expensive,
as it calls a sqrt() per sample. I suspect this saving was the original motivation for balance
(way back in MUSIC 11) being the way it is.

Once sourceforge is back up and appveyor is building again, you’re welcome to try this
opcode (just replace balance by balance2).
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:

Aha! But then what can be causing this noise..? I am using the opcode
exactly as shown - did you try with the soundfile I attached?
If the balance opcode is supposed to add noise, is there perhaps
nother way I can achieve this same effect without added noise? (and
without changing ksmps)
Søren

On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
Balance finds the rms of the two signals at k-rate, but it applies
the amplitude changes by interpolating linearly between k-rate
values.

It could well be that in the particular way you are using you hear
some artefact. However that’s the behaviour of balance, and not
a bug.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:

I just had a chance to test it on a Mac and I'm hearing the same
noise. And when I change ksmps from 32 to 1 it goes away. I'm
beginning to think the problem is that balance is based on the rms
opcode (?) which is running at k-rate only. There should be an a-rate
version of rms, and balance should be based (optionally) on that?
(that way I would not have to set ksmps = 1)
Or balance should internally use some a-rate interpolation?
Best regards,
Søren

On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
I think what I'm hearing is some crackling 'incontinuity distortion'
which - I now realize - is dependent on ksmps. If I make ksmps smaller
there is less distortion, but even with ksmps = 1 (I guess then
control rate is equal to audio rate) I believe am still hearing a
small bit of distortion.

I wonder if this is just a limitation of digital filters - there will
always be a bit of distortion? (and ksmps = 1 is probably not
feasible)

Anyhow, I will try to find a friend's Mac to test with..

Søren

On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
Sounds fine here too as far as I can see.... actually seeing more than
listening right now, as I only have the laptop speakers.
Comparing the three different signals (clean from loscil, filtered, and
balanced) show the type of output I would expect from these opcodes.
Could
you describe the artifact you hear more in detail?
best
Oeyvind

2018-02-27 15:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

it sounds as I would expect on MacOs. I hear no artefact, just a
low-pass
filtered sound
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:

The 'balance' opcode (also) seems to be introducing some noise, which
I
think
should not be there - happens with v6.10 and also with v6.07 on
Windows
10/x64. Can someone please try the following code and confirm whether
there
is a bug?

<CsoundSynthesizer>
<CsOptions>
-o dac
</CsOptions>
<CsInstruments>
sr = 44100
ksmps = 32
nchnls = 2
0dbfs  = 1
instr 1
as loscil3 1.0, 1.0, 123, 1, 1
ap tone as, 100
ap balance ap, as
outs ap, ap
endin
</CsInstruments>
<CsScore>
f 123 0 0 -1 "loop.wav" 0 0 0
i 1 0 5
e
</CsScore>
</CsoundSynthesizer>

loop.wav <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>



--
Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
f1093014.html
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
     https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here



--

Oeyvind Brandtsegg
Professor of Music Technology
NTNU
7491 Trondheim
Norway
Cell: +47 92 203 205

http://www.partikkelaudio.com/
http://crossadaptive.hf.ntnu.no
http://gdsp.hf.ntnu.no/
http://soundcloud.com/brandtsegg
http://flyndresang.no/
http://soundcloud.com/t-emp

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
      https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 17:22:44 +0100
From:    Rene <[hidden email]>
Subject: --realtime flag

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty
behavior.
The reinit is done for the complete instrument regardless of the reinit
label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?



Best,
René

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 17:52:13 +0100
From:    Oeyvind Brandtsegg <[hidden email]>
Subject: Re: Noise detection

Spectral flatness or flux might be useable indicators in this case.
If you need an example of how to implement it you could look at the code at
https://github.com/Oeyvind/featexmod in the file analyze_audio.inc

Best
Oeyvind


On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>
wrote:

Right yes, noise is a vague term. For my specific purpose,  I'm thinking
primarily full spectrum white noise or similar...  In which case you're
right, examining an FFT probably is the sensible way to go here. The goal
is to be able to auto detect unwanted white noise in samples and discard
those containing too much of it.
Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 17:07:04 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]<mailto:[hidden email]>> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues

------------------------------

Date:    Fri, 2 Mar 2018 17:48:33 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]<mailto:[hidden email]>> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]<mailto:[hidden email]>> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email]<mailto:[hidden email]> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features

------------------------------

Date:    Fri, 2 Mar 2018 20:20:01 +0200
From:    Tarmo Johannes <[hidden email]>
Subject: Re: Noise detection

Hi,

This is probably not you are after but (from the manual):

http://www.csounds.com/manual/html/pvstencil.html
One of the typical uses of /pvstencil/ would be in noise reduction.

Maybe you can reverse it somehow to get the noise level?
"Skipping post-normalisation will keep the original noise print average amplitudes."

I don't pretend I understand exactly how it is used.

tarmo

On reede, 2. märts 2018 18:52.13 EET you wrote:
Spectral flatness or flux might be useable indicators in this case.
If you need an example of how to implement it you could look at the code at
https://github.com/Oeyvind/featexmod in the file analyze_audio.inc

Best
Oeyvind


On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>

wrote:
Right yes, noise is a vague term. For my specific purpose,  I'm thinking
primarily full spectrum white noise or similar...  In which case you're
right, examining an FFT probably is the sensible way to go here. The goal
is to be able to auto detect unwanted white noise in samples and discard
those containing too much of it.
Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here
Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here


Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 20:26:03 +0100
From:    Rene <[hidden email]>
Subject: Re: --realtime flag

Hello,

Tanks for your answer.

I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't
find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:

Actually, can you try the latest (6.11)? This version has a completely
overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty
behavior.
The reinit is done for the complete instrument regardless of the reinit
label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?



Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here

<reinit.csd>

Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/
cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 20:03:41 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

The master branch is 6.10, old code. The develop branch is 6.11, e.g.

Csound version 6.11 beta (double samples) Mar  1 2018

Feature-realtime has been merged into develop, so that would have similar
code.

I tested your code and I am getting the WARNING, which I think it is a
bug in the latest checked in code. That problem is there with or without
—reatlime

Once that is fixed, you can test it again.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:

Hello,

Tanks for your answer.
  I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 20:09:04 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

actually, it’s a problem with realtime. I’ll fix it. I think it is to do with
timout, not reinit.
========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:

Hello,

Tanks for your answer.
  I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

Date:    Fri, 2 Mar 2018 21:29:44 +0000
From:    Victor Lazzarini <[hidden email]>
Subject: Re: --realtime flag

I have fixed this now (in git develop), but there are a couple of caveats:

1) reinit should be avoided in --realtime mode: it stops performance to
run a reinit pass, and that is not a good idea. Even though it runs the
reinit on a separate thread, performance has to pause for reinitialisation.

2) opcodes like timeout would potentially have gaps in their time counting
due to the reinit pause.

In other words: although the instrument will work (with maybe some timout
time counting issues), it’s not a good realtime instrument.

========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952

On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:

Hello,

Tanks for your answer.
  I have tested from git (today download)

csound-master : give same bug as 6.10.0

csound-develop and csound-feature-realtime : (may be wrong version, i can't find 6.11)
For both i can't test because i got a continuous message

WARNING: instr 0 uses 3 p-fields but is given 0

then csound hang.


Best,
René








2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
Actually, can you try the latest (6.11)? This version has a completely overhauled realtime mode, and I remembered testing reinit and it worked.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]> wrote:

It could be a bug.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:

Hello,

Instruments using reinit opcode and --realtime flag seems to have a faulty behavior.
The reinit is done for the complete instrument regardless of the reinit label and rireturn locations.

(The included reinit.csd instrument prints Hello at every reinit)

I am on linux, csound 6.10.0

Is it normal?

Best,
René
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
<reinit.csd>
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
         https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

------------------------------

End of CSOUND Digest - 1 Mar 2018 to 2 Mar 2018 (#2018-58)
**********************************************************


Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here

Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
In reply to this post by Jan Jacob Hofmann
Dear Michael,

my cmake version is 3.5.1.

Cheers,

Jan Jacob

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Michael Gogins-2
I am using 3.9.1 and it works. What about your Python version? I am
using 2.7.14, 64 bit version.

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com


On Sat, Mar 3, 2018 at 8:32 AM, Jan Jacob Hofmann
<[hidden email]> wrote:

> Dear Michael,
>
> my cmake version is 3.5.1.
>
> Cheers,
>
> Jan Jacob
>
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
In reply to this post by Jan Jacob Hofmann
Dear Michael,

my python version is Python 2.7.12

Cheers,

Jan Jacob

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

joachim-3
In reply to this post by Jan Jacob Hofmann
hi jan jacob -

i had a look at interfaces/CMakeLists.txt:92 in my sources.  i found this:
     include(${SWIG_USE_FILE})

how does it look in your case?

it seems that this is part of a function which is only called if you
build with python or java or lua interface.  so you might try to call
cmake with disableing this option, or you set

        BUILD_PYTHON_INTERFACE:BOOL=OFF

in your cs6Make/CmakeCache.txt (in my case in line 127).

best -
        joachim



On 03/03/18 08:58, Jan Jacob Hofmann wrote:

> Dear list,
>
> As I built my Csound on Ubuntu more than one year ago, I would like to
> update it to the current version (master). Mostly everything works fine
> but I do get an error message regarding "SWIG" and something related to
> that seems to cause an error in the cmake build process. I am not sure
> what to do now, as the SWIG-version seems to be all right: "found
> suitable version "2.0.11", minimum required is "2.0""
>
> I placed the relevant excerpt of the messages below. Maybe someone has
> an idea what causes that error and what I could do to overcome it?
>
> Best regards,
>
> Jan Jacob
>
>
> [...]
>
> -- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11",
> minimum required is "2.0")
>
> -- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so
>
> -- BUILD_PYTHON_INTERFACE is enabled.
>
> -- BUILD_JAVA_INTERFACE is enabled.
>
> -- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling
> BUILD_LUA_INTERFACE
>
> -- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE
>
> -- BUILD_LUA_INTERFACE is disabled.
>
> -- SWIG_USE_FILE:
>
> CMake Error at interfaces/CMakeLists.txt:92 (include):
>
> include called with wrong number of arguments. include() only takes one
>
> file.
>
>
>
> CMake Error at interfaces/CMakeLists.txt:112 (swig_add_module):
>
> Unknown CMake command "swig_add_module".
>
>
>
> -- Configuring incomplete, errors occurred!
>
>
> [...]
>
>
>
> sound      |      movement       |       object      |      space
> sonic architecture     |      site: http://www.sonicarchitecture.de
> spatial electronic composition    |    higher order ambisonic music
>
> Am 03.03.2018 um 01:00 schrieb CSOUND automatic digest system:
>> There are 17 messages totaling 2115 lines in this issue.
>>
>> Topics of the day:
>>
>>    1. Redefining f signals (3)
>>    2. balance opcode sound artifact (4)
>>    3. Noise detection (3)
>>    4. --realtime flag (7)
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ----------------------------------------------------------------------
>>
>> Date:    Fri, 2 Mar 2018 00:05:04 +0000
>> From:    jpff <[hidden email]>
>> Subject: Re: Redefining f signals
>>
>> Two thoughts;
>> 1: That ought to work
>> 2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1" not
>> work?
>>
>>
>> On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:
>>
>>> Hello,
>>>
>>> I have a question about use of the f-signals. I would like to create
>>> an instrument with a long chain of processes to be turned on and off
>>> by score parameters, and finally resynthesize the signal going
>>> through selected process.
>>>
>>> If the analyzed signal is fsig1, I have to redefine it to fsig101 to
>>> avoid trouble. Still I would like to keep working on fsig1 through
>>> the various processes and resynthesize it as fsig1. If not the number
>>> of possible scenarios and combinations would grow enourmously
>>> depending on which processes are used.
>>>
>>> I try to redefine fsig1 this way: fsig1=fsig101, to bring the result
>>> of scaling as input fsig1 to the next process. But this doesn’t work,
>>> Csound gets stuck at the first note and doesn’t seem to progress at all.
>>>
>>> I include just some example lines from the csd to show the idea. I
>>> could include the whole file, but it’s long and messy.
>>> Do you have some advice on how to handle a chain of optional f-signal
>>> processings?
>>>
>>> Best
>>> Ruben
>>>
>>>
>>> if (ifile1ch==1.000) goto monopvsanal
>>> monopvsanal:
>>> fsig1     pvsanal     apostwarpL, ipvsfftsize, ipvsoverlap,
>>> ipvwinsize, ipvswintype
>>> goto postpvsanal
>>> postpvsanal:
>>>
>>> if (iwanttoskipsecondpitch==1) goto postpvscale
>>> if (ifile1ch==1.000) goto monopvscale
>>> monopvscale:
>>> fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
>>> fsig1= fsig101
>>> goto postpvscale
>>> postpvscale:
>>>
>>> ;etc…add 10 similar modules
>>>
>>> if (ifile1ch==1.000) goto monopvsynth
>>> monopvsynth:
>>> a2ambL     pvsynth     fsig1
>>> goto spatialization
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 00:07:55 +0000
>> From:    jpff <[hidden email]>
>> Subject: Re: Redefining f signals
>>
>> and...
>>
>> if (ifile1ch==1.000) goto monopvscale
>> monopvscale:
>>
>> does not make much sense, ad yourtests/goto seem to be all i-rate so do
>> not affect perf time
>> xy
>>
>> On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:
>>
>>> Hello,
>>>
>>> I have a question about use of the f-signals. I would like to create
>>> an instrument with a long chain of processes to be turned on and off
>>> by score parameters, and finally resynthesize the signal going
>>> through selected process.
>>>
>>> If the analyzed signal is fsig1, I have to redefine it to fsig101 to
>>> avoid trouble. Still I would like to keep working on fsig1 through
>>> the various processes and resynthesize it as fsig1. If not the number
>>> of possible scenarios and combinations would grow enourmously
>>> depending on which processes are used.
>>>
>>> I try to redefine fsig1 this way: fsig1=fsig101, to bring the result
>>> of scaling as input fsig1 to the next process. But this doesn’t work,
>>> Csound gets stuck at the first note and doesn’t seem to progress at all.
>>>
>>> I include just some example lines from the csd to show the idea. I
>>> could include the whole file, but it’s long and messy.
>>> Do you have some advice on how to handle a chain of optional f-signal
>>> processings?
>>>
>>> Best
>>> Ruben
>>>
>>>
>>> if (ifile1ch==1.000) goto monopvsanal
>>> monopvsanal:
>>> fsig1     pvsanal     apostwarpL, ipvsfftsize, ipvsoverlap,
>>> ipvwinsize, ipvswintype
>>> goto postpvsanal
>>> postpvsanal:
>>>
>>> if (iwanttoskipsecondpitch==1) goto postpvscale
>>> if (ifile1ch==1.000) goto monopvscale
>>> monopvscale:
>>> fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
>>> fsig1= fsig101
>>> goto postpvscale
>>> postpvscale:
>>>
>>> ;etc…add 10 similar modules
>>>
>>> if (ifile1ch==1.000) goto monopvsynth
>>> monopvsynth:
>>> a2ambL     pvsynth     fsig1
>>> goto spatialization
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 10:00:08 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: Redefining f signals
>>
>> The manual notes that some opcodes have side effects on inputs, so
>> re-using the variable should not
>> be taken for granted. Check the man page.
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 2 Mar 2018, at 00:05, jpff <[hidden email]> wrote:
>>>
>>> Two thoughts;
>>> 1: That ought to work
>>> 2: Does "fsig pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1"
>>> not work?
>>>
>>>
>>> On Fri, 2 Mar 2018, Ruben Sverre Gjertsen wrote:
>>>
>>>> Hello,
>>>>
>>>> I have a question about use of the f-signals. I would like to create
>>>> an instrument with a long chain of processes to be turned on and off
>>>> by score parameters, and finally resynthesize the signal going
>>>> through selected process.
>>>>
>>>> If the analyzed signal is fsig1, I have to redefine it to fsig101 to
>>>> avoid trouble. Still I would like to keep working on fsig1 through
>>>> the various processes and resynthesize it as fsig1. If not the
>>>> number of possible scenarios and combinations would grow enourmously
>>>> depending on which processes are used.
>>>>
>>>> I try to redefine fsig1 this way: fsig1=fsig101, to bring the result
>>>> of scaling as input fsig1 to the next process. But this doesn’t
>>>> work, Csound gets stuck at the first note and doesn’t seem to
>>>> progress at all.
>>>>
>>>> I include just some example lines from the csd to show the idea. I
>>>> could include the whole file, but it’s long and messy.
>>>> Do you have some advice on how to handle a chain of optional
>>>> f-signal processings?
>>>>
>>>> Best
>>>> Ruben
>>>>
>>>>
>>>> if (ifile1ch==1.000) goto monopvsanal
>>>> monopvsanal:
>>>> fsig1     pvsanal     apostwarpL, ipvsfftsize, ipvsoverlap,
>>>> ipvwinsize, ipvswintype
>>>> goto postpvsanal
>>>> postpvsanal:
>>>>
>>>> if (iwanttoskipsecondpitch==1) goto postpvscale
>>>> if (ifile1ch==1.000) goto monopvscale
>>>> monopvscale:
>>>> fsig101 pvscale fsig1,  ksecondpitchfinal, ikeepscalingform, 1
>>>> fsig1= fsig101
>>>> goto postpvscale
>>>> postpvscale:
>>>>
>>>> ;etc…add 10 similar modules
>>>>
>>>> if (ifile1ch==1.000) goto monopvsynth
>>>> monopvsynth:
>>>> a2ambL     pvsynth     fsig1
>>>> goto spatialization
>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>        https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 10:06:21 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: balance opcode sound artifact
>>
>> I tried your soundfile but could not hear anything (which does not
>> mean it is not there).
>> What I am saying is that the opcode is what it is, it has been used in
>> lots of applications
>> and we should not change its behaviour (backwards compatibility).
>>
>> I have added a balance2 opcode (untested yet) that calculates the
>> amplitude scaling
>> on a sample-by-sample basis. It is slightly more (but I expect not too
>> much) expensive,
>> as it calls a sqrt() per sample. I suspect this saving was the
>> original motivation for balance
>> (way back in MUSIC 11) being the way it is.
>>
>> Once sourceforge is back up and appveyor is building again, you’re
>> welcome to try this
>> opcode (just replace balance by balance2).
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>
>>> Aha! But then what can be causing this noise..? I am using the opcode
>>> exactly as shown - did you try with the soundfile I attached?
>>> If the balance opcode is supposed to add noise, is there perhaps
>>> nother way I can achieve this same effect without added noise? (and
>>> without changing ksmps)
>>> Søren
>>>
>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>> the amplitude changes by interpolating linearly between k-rate
>>>> values.
>>>>
>>>> It could well be that in the particular way you are using you hear
>>>> some artefact. However that’s the behaviour of balance, and not
>>>> a bug.
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>
>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>> beginning to think the problem is that balance is based on the rms
>>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>>> version of rms, and balance should be based (optionally) on that?
>>>>> (that way I would not have to set ksmps = 1)
>>>>> Or balance should internally use some a-rate interpolation?
>>>>> Best regards,
>>>>> Søren
>>>>>
>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps
>>>>>> smaller
>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>> small bit of distortion.
>>>>>>
>>>>>> I wonder if this is just a limitation of digital filters - there will
>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>> feasible)
>>>>>>
>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>
>>>>>> Søren
>>>>>>
>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>> Sounds fine here too as far as I can see.... actually seeing more
>>>>>>> than
>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>> Comparing the three different signals (clean from loscil,
>>>>>>> filtered, and
>>>>>>> balanced) show the type of output I would expect from these opcodes.
>>>>>>> Could
>>>>>>> you describe the artifact you hear more in detail?
>>>>>>> best
>>>>>>> Oeyvind
>>>>>>>
>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini
>>>>>>> <[hidden email]>:
>>>>>>>
>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>> low-pass
>>>>>>>> filtered sound
>>>>>>>> ========================
>>>>>>>> Prof. Victor Lazzarini
>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>> Maynooth University,
>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>> Tel: 00 353 7086936
>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>
>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>
>>>>>>>>> The 'balance' opcode (also) seems to be introducing some noise,
>>>>>>>>> which
>>>>>>>>> I
>>>>>>>> think
>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>> Windows
>>>>>>>>> 10/x64. Can someone please try the following code and confirm
>>>>>>>>> whether
>>>>>>>> there
>>>>>>>>> is a bug?
>>>>>>>>>
>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>> <CsOptions>
>>>>>>>>> -o dac
>>>>>>>>> </CsOptions>
>>>>>>>>> <CsInstruments>
>>>>>>>>> sr = 44100
>>>>>>>>> ksmps = 32
>>>>>>>>> nchnls = 2
>>>>>>>>> 0dbfs  = 1
>>>>>>>>> instr 1
>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>> ap tone as, 100
>>>>>>>>> ap balance ap, as
>>>>>>>>> outs ap, ap
>>>>>>>>> endin
>>>>>>>>> </CsInstruments>
>>>>>>>>> <CsScore>
>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>> i 1 0 5
>>>>>>>>> e
>>>>>>>>> </CsScore>
>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>
>>>>>>>>> loop.wav
>>>>>>>>> <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>> f1093014.html
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Oeyvind Brandtsegg
>>>>>>> Professor of Music Technology
>>>>>>> NTNU
>>>>>>> 7491 Trondheim
>>>>>>> Norway
>>>>>>> Cell: +47 92 203 205
>>>>>>>
>>>>>>> http://www.partikkelaudio.com/
>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>> http://flyndresang.no/
>>>>>>> http://soundcloud.com/t-emp
>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> [hidden email]
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>        https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>        https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 13:12:26 +0000
>> From:    Peter Burgess <[hidden email]>
>> Subject: Re: Noise detection
>>
>> Right yes, noise is a vague term. For my specific purpose,  I'm thinking
>> primarily full spectrum white noise or similar...  In which case you're
>> right, examining an FFT probably is the sensible way to go here. The goal
>> is to be able to auto detect unwanted white noise in samples and discard
>> those containing too much of it.
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 15:34:40 +0100
>> From:    joachim heintz <[hidden email]>
>> Subject: Re: balance opcode sound artifact
>>
>> thanks, victor; i think this balance2 is a very good idea anyway.
>>     joachim
>>
>>
>>
>> On 02/03/18 11:06, Victor Lazzarini wrote:
>>> I tried your soundfile but could not hear anything (which does not
>>> mean it is not there).
>>> What I am saying is that the opcode is what it is, it has been used
>>> in lots of applications
>>> and we should not change its behaviour (backwards compatibility).
>>>
>>> I have added a balance2 opcode (untested yet) that calculates the
>>> amplitude scaling
>>> on a sample-by-sample basis. It is slightly more (but I expect not
>>> too much) expensive,
>>> as it calls a sqrt() per sample. I suspect this saving was the
>>> original motivation for balance
>>> (way back in MUSIC 11) being the way it is.
>>>
>>> Once sourceforge is back up and appveyor is building again, you’re
>>> welcome to try this
>>> opcode (just replace balance by balance2).
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>>
>>>> Aha! But then what can be causing this noise..? I am using the opcode
>>>> exactly as shown - did you try with the soundfile I attached?
>>>> If the balance opcode is supposed to add noise, is there perhaps
>>>> nother way I can achieve this same effect without added noise? (and
>>>> without changing ksmps)
>>>> Søren
>>>>
>>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>>> the amplitude changes by interpolating linearly between k-rate
>>>>> values.
>>>>>
>>>>> It could well be that in the particular way you are using you hear
>>>>> some artefact. However that’s the behaviour of balance, and not
>>>>> a bug.
>>>>> ========================
>>>>> Prof. Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>>
>>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>>> beginning to think the problem is that balance is based on the rms
>>>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>>>> version of rms, and balance should be based (optionally) on that?
>>>>>> (that way I would not have to set ksmps = 1)
>>>>>> Or balance should internally use some a-rate interpolation?
>>>>>> Best regards,
>>>>>> Søren
>>>>>>
>>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps
>>>>>>> smaller
>>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>>> small bit of distortion.
>>>>>>>
>>>>>>> I wonder if this is just a limitation of digital filters - there
>>>>>>> will
>>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>>> feasible)
>>>>>>>
>>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>>
>>>>>>> Søren
>>>>>>>
>>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>>> Sounds fine here too as far as I can see.... actually seeing
>>>>>>>> more than
>>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>>> Comparing the three different signals (clean from loscil,
>>>>>>>> filtered, and
>>>>>>>> balanced) show the type of output I would expect from these
>>>>>>>> opcodes.
>>>>>>>> Could
>>>>>>>> you describe the artifact you hear more in detail?
>>>>>>>> best
>>>>>>>> Oeyvind
>>>>>>>>
>>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini
>>>>>>>> <[hidden email]>:
>>>>>>>>
>>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>>> low-pass
>>>>>>>>> filtered sound
>>>>>>>>> ========================
>>>>>>>>> Prof. Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>>> Maynooth University,
>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>
>>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>>
>>>>>>>>>> The 'balance' opcode (also) seems to be introducing some
>>>>>>>>>> noise, which
>>>>>>>>>> I
>>>>>>>>> think
>>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>>> Windows
>>>>>>>>>> 10/x64. Can someone please try the following code and confirm
>>>>>>>>>> whether
>>>>>>>>> there
>>>>>>>>>> is a bug?
>>>>>>>>>>
>>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>>> <CsOptions>
>>>>>>>>>> -o dac
>>>>>>>>>> </CsOptions>
>>>>>>>>>> <CsInstruments>
>>>>>>>>>> sr = 44100
>>>>>>>>>> ksmps = 32
>>>>>>>>>> nchnls = 2
>>>>>>>>>> 0dbfs  = 1
>>>>>>>>>> instr 1
>>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>>> ap tone as, 100
>>>>>>>>>> ap balance ap, as
>>>>>>>>>> outs ap, ap
>>>>>>>>>> endin
>>>>>>>>>> </CsInstruments>
>>>>>>>>>> <CsScore>
>>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>>> i 1 0 5
>>>>>>>>>> e
>>>>>>>>>> </CsScore>
>>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>>
>>>>>>>>>> loop.wav
>>>>>>>>>> <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>>> f1093014.html
>>>>>>>>>> Csound mailing list
>>>>>>>>>> [hidden email]
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Oeyvind Brandtsegg
>>>>>>>> Professor of Music Technology
>>>>>>>> NTNU
>>>>>>>> 7491 Trondheim
>>>>>>>> Norway
>>>>>>>> Cell: +47 92 203 205
>>>>>>>>
>>>>>>>> http://www.partikkelaudio.com/
>>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>>> http://flyndresang.no/
>>>>>>>> http://soundcloud.com/t-emp
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>> Csound mailing list
>>>>>> [hidden email]
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>        https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>         https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 15:41:28 +0000
>> From:    Søren Jakobsen <[hidden email]>
>> Subject: Re: balance opcode sound artifact
>>
>> Sounds great, thanks - looking forward to the next successful build:)
>>
>> On 3/2/18, joachim heintz <[hidden email]> wrote:
>>> thanks, victor; i think this balance2 is a very good idea anyway.
>>>     joachim
>>>
>>>
>>>
>>> On 02/03/18 11:06, Victor Lazzarini wrote:
>>>> I tried your soundfile but could not hear anything (which does not
>>>> mean it
>>>> is not there).
>>>> What I am saying is that the opcode is what it is, it has been used in
>>>> lots of applications
>>>> and we should not change its behaviour (backwards compatibility).
>>>>
>>>> I have added a balance2 opcode (untested yet) that calculates the
>>>> amplitude scaling
>>>> on a sample-by-sample basis. It is slightly more (but I expect not too
>>>> much) expensive,
>>>> as it calls a sqrt() per sample. I suspect this saving was the original
>>>> motivation for balance
>>>> (way back in MUSIC 11) being the way it is.
>>>>
>>>> Once sourceforge is back up and appveyor is building again, you’re
>>>> welcome
>>>> to try this
>>>> opcode (just replace balance by balance2).
>>>> ========================
>>>> Prof. Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>> Maynooth University,
>>>> Maynooth, Co Kildare, Ireland
>>>> Tel: 00 353 7086936
>>>> Fax: 00 353 1 7086952
>>>>
>>>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>>>
>>>>> Aha! But then what can be causing this noise..? I am using the opcode
>>>>> exactly as shown - did you try with the soundfile I attached?
>>>>> If the balance opcode is supposed to add noise, is there perhaps
>>>>> nother way I can achieve this same effect without added noise? (and
>>>>> without changing ksmps)
>>>>> Søren
>>>>>
>>>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>>>> the amplitude changes by interpolating linearly between k-rate
>>>>>> values.
>>>>>>
>>>>>> It could well be that in the particular way you are using you hear
>>>>>> some artefact. However that’s the behaviour of balance, and not
>>>>>> a bug.
>>>>>> ========================
>>>>>> Prof. Victor Lazzarini
>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>> Maynooth University,
>>>>>> Maynooth, Co Kildare, Ireland
>>>>>> Tel: 00 353 7086936
>>>>>> Fax: 00 353 1 7086952
>>>>>>
>>>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>>>
>>>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>>>> beginning to think the problem is that balance is based on the rms
>>>>>>> opcode (?) which is running at k-rate only. There should be an
>>>>>>> a-rate
>>>>>>> version of rms, and balance should be based (optionally) on that?
>>>>>>> (that way I would not have to set ksmps = 1)
>>>>>>> Or balance should internally use some a-rate interpolation?
>>>>>>> Best regards,
>>>>>>> Søren
>>>>>>>
>>>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>>>> I think what I'm hearing is some crackling 'incontinuity
>>>>>>>> distortion'
>>>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps
>>>>>>>> smaller
>>>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>>>> small bit of distortion.
>>>>>>>>
>>>>>>>> I wonder if this is just a limitation of digital filters - there
>>>>>>>> will
>>>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>>>> feasible)
>>>>>>>>
>>>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>>>
>>>>>>>> Søren
>>>>>>>>
>>>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>>>> Sounds fine here too as far as I can see.... actually seeing more
>>>>>>>>> than
>>>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>>>> Comparing the three different signals (clean from loscil,
>>>>>>>>> filtered,
>>>>>>>>> and
>>>>>>>>> balanced) show the type of output I would expect from these
>>>>>>>>> opcodes.
>>>>>>>>> Could
>>>>>>>>> you describe the artifact you hear more in detail?
>>>>>>>>> best
>>>>>>>>> Oeyvind
>>>>>>>>>
>>>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini
>>>>>>>>> <[hidden email]>:
>>>>>>>>>
>>>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>>>> low-pass
>>>>>>>>>> filtered sound
>>>>>>>>>> ========================
>>>>>>>>>> Prof. Victor Lazzarini
>>>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>>>> Maynooth University,
>>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>>
>>>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>>>
>>>>>>>>>>> The 'balance' opcode (also) seems to be introducing some noise,
>>>>>>>>>>> which
>>>>>>>>>>> I
>>>>>>>>>> think
>>>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>>>> Windows
>>>>>>>>>>> 10/x64. Can someone please try the following code and confirm
>>>>>>>>>>> whether
>>>>>>>>>> there
>>>>>>>>>>> is a bug?
>>>>>>>>>>>
>>>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>>>> <CsOptions>
>>>>>>>>>>> -o dac
>>>>>>>>>>> </CsOptions>
>>>>>>>>>>> <CsInstruments>
>>>>>>>>>>> sr = 44100
>>>>>>>>>>> ksmps = 32
>>>>>>>>>>> nchnls = 2
>>>>>>>>>>> 0dbfs  = 1
>>>>>>>>>>> instr 1
>>>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>>>> ap tone as, 100
>>>>>>>>>>> ap balance ap, as
>>>>>>>>>>> outs ap, ap
>>>>>>>>>>> endin
>>>>>>>>>>> </CsInstruments>
>>>>>>>>>>> <CsScore>
>>>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>>>> i 1 0 5
>>>>>>>>>>> e
>>>>>>>>>>> </CsScore>
>>>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>>>
>>>>>>>>>>> loop.wav
>>>>>>>>>>> <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>>>> f1093014.html
>>>>>>>>>>> Csound mailing list
>>>>>>>>>>> [hidden email]
>>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>>> Send bugs reports to
>>>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>> Csound mailing list
>>>>>>>>>> [hidden email]
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> Oeyvind Brandtsegg
>>>>>>>>> Professor of Music Technology
>>>>>>>>> NTNU
>>>>>>>>> 7491 Trondheim
>>>>>>>>> Norway
>>>>>>>>> Cell: +47 92 203 205
>>>>>>>>>
>>>>>>>>> http://www.partikkelaudio.com/
>>>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>>>> http://flyndresang.no/
>>>>>>>>> http://soundcloud.com/t-emp
>>>>>>>>>
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>        https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>> Csound mailing list
>>>>>>> [hidden email]
>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>> Send bugs reports to
>>>>>>>        https://github.com/csound/csound/issues
>>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>>> Csound mailing list
>>>>>> [hidden email]
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>         https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>         https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>          https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 10:47:00 -0500
>> From:    "Dr. Richard Boulanger" <[hidden email]>
>> Subject: Re: balance opcode sound artifact
>>
>> balance2 will be a nice addition.  Thanks
>>
>> Sent from my iPhone
>>
>>> On Mar 2, 2018, at 5:06 AM, Victor Lazzarini <[hidden email]>
>>> wrote:
>>>
>>> I tried your soundfile but could not hear anything (which does not
>>> mean it is not there).
>>> What I am saying is that the opcode is what it is, it has been used
>>> in lots of applications
>>> and we should not change its behaviour (backwards compatibility).
>>>
>>> I have added a balance2 opcode (untested yet) that calculates the
>>> amplitude scaling
>>> on a sample-by-sample basis. It is slightly more (but I expect not
>>> too much) expensive,
>>> as it calls a sqrt() per sample. I suspect this saving was the
>>> original motivation for balance
>>> (way back in MUSIC 11) being the way it is.
>>>
>>> Once sourceforge is back up and appveyor is building again, you’re
>>> welcome to try this
>>> opcode (just replace balance by balance2).
>>> ========================
>>> Prof. Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy,
>>> Maynooth University,
>>> Maynooth, Co Kildare, Ireland
>>> Tel: 00 353 7086936
>>> Fax: 00 353 1 7086952
>>>
>>>> On 1 Mar 2018, at 20:25, Søren Jakobsen <[hidden email]> wrote:
>>>>
>>>> Aha! But then what can be causing this noise..? I am using the opcode
>>>> exactly as shown - did you try with the soundfile I attached?
>>>> If the balance opcode is supposed to add noise, is there perhaps
>>>> nother way I can achieve this same effect without added noise? (and
>>>> without changing ksmps)
>>>> Søren
>>>>
>>>>> On 3/1/18, Victor Lazzarini <[hidden email]> wrote:
>>>>> Balance finds the rms of the two signals at k-rate, but it applies
>>>>> the amplitude changes by interpolating linearly between k-rate
>>>>> values.
>>>>>
>>>>> It could well be that in the particular way you are using you hear
>>>>> some artefact. However that’s the behaviour of balance, and not
>>>>> a bug.
>>>>> ========================
>>>>> Prof. Victor Lazzarini
>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>> Maynooth University,
>>>>> Maynooth, Co Kildare, Ireland
>>>>> Tel: 00 353 7086936
>>>>> Fax: 00 353 1 7086952
>>>>>
>>>>>> On 1 Mar 2018, at 17:02, Søren Jakobsen <[hidden email]> wrote:
>>>>>>
>>>>>> I just had a chance to test it on a Mac and I'm hearing the same
>>>>>> noise. And when I change ksmps from 32 to 1 it goes away. I'm
>>>>>> beginning to think the problem is that balance is based on the rms
>>>>>> opcode (?) which is running at k-rate only. There should be an a-rate
>>>>>> version of rms, and balance should be based (optionally) on that?
>>>>>> (that way I would not have to set ksmps = 1)
>>>>>> Or balance should internally use some a-rate interpolation?
>>>>>> Best regards,
>>>>>> Søren
>>>>>>
>>>>>>> On 2/27/18, Søren Jakobsen <[hidden email]> wrote:
>>>>>>> I think what I'm hearing is some crackling 'incontinuity distortion'
>>>>>>> which - I now realize - is dependent on ksmps. If I make ksmps
>>>>>>> smaller
>>>>>>> there is less distortion, but even with ksmps = 1 (I guess then
>>>>>>> control rate is equal to audio rate) I believe am still hearing a
>>>>>>> small bit of distortion.
>>>>>>>
>>>>>>> I wonder if this is just a limitation of digital filters - there
>>>>>>> will
>>>>>>> always be a bit of distortion? (and ksmps = 1 is probably not
>>>>>>> feasible)
>>>>>>>
>>>>>>> Anyhow, I will try to find a friend's Mac to test with..
>>>>>>>
>>>>>>> Søren
>>>>>>>
>>>>>>>> On 2/27/18, Oeyvind Brandtsegg <[hidden email]> wrote:
>>>>>>>> Sounds fine here too as far as I can see.... actually seeing
>>>>>>>> more than
>>>>>>>> listening right now, as I only have the laptop speakers.
>>>>>>>> Comparing the three different signals (clean from loscil,
>>>>>>>> filtered, and
>>>>>>>> balanced) show the type of output I would expect from these
>>>>>>>> opcodes.
>>>>>>>> Could
>>>>>>>> you describe the artifact you hear more in detail?
>>>>>>>> best
>>>>>>>> Oeyvind
>>>>>>>>
>>>>>>>> 2018-02-27 15:48 GMT+01:00 Victor Lazzarini
>>>>>>>> <[hidden email]>:
>>>>>>>>
>>>>>>>>> it sounds as I would expect on MacOs. I hear no artefact, just a
>>>>>>>>> low-pass
>>>>>>>>> filtered sound
>>>>>>>>> ========================
>>>>>>>>> Prof. Victor Lazzarini
>>>>>>>>> Dean of Arts, Celtic Studies, and Philosophy,
>>>>>>>>> Maynooth University,
>>>>>>>>> Maynooth, Co Kildare, Ireland
>>>>>>>>> Tel: 00 353 7086936
>>>>>>>>> Fax: 00 353 1 7086952
>>>>>>>>>
>>>>>>>>>> On 27 Feb 2018, at 14:43, sjakops <[hidden email]> wrote:
>>>>>>>>>>
>>>>>>>>>> The 'balance' opcode (also) seems to be introducing some
>>>>>>>>>> noise, which
>>>>>>>>>> I
>>>>>>>>> think
>>>>>>>>>> should not be there - happens with v6.10 and also with v6.07 on
>>>>>>>>>> Windows
>>>>>>>>>> 10/x64. Can someone please try the following code and confirm
>>>>>>>>>> whether
>>>>>>>>> there
>>>>>>>>>> is a bug?
>>>>>>>>>>
>>>>>>>>>> <CsoundSynthesizer>
>>>>>>>>>> <CsOptions>
>>>>>>>>>> -o dac
>>>>>>>>>> </CsOptions>
>>>>>>>>>> <CsInstruments>
>>>>>>>>>> sr = 44100
>>>>>>>>>> ksmps = 32
>>>>>>>>>> nchnls = 2
>>>>>>>>>> 0dbfs  = 1
>>>>>>>>>> instr 1
>>>>>>>>>> as loscil3 1.0, 1.0, 123, 1, 1
>>>>>>>>>> ap tone as, 100
>>>>>>>>>> ap balance ap, as
>>>>>>>>>> outs ap, ap
>>>>>>>>>> endin
>>>>>>>>>> </CsInstruments>
>>>>>>>>>> <CsScore>
>>>>>>>>>> f 123 0 0 -1 "loop.wav" 0 0 0
>>>>>>>>>> i 1 0 5
>>>>>>>>>> e
>>>>>>>>>> </CsScore>
>>>>>>>>>> </CsoundSynthesizer>
>>>>>>>>>>
>>>>>>>>>> loop.wav
>>>>>>>>>> <http://csound.1045644.n5.nabble.com/file/t339749/loop.wav>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sent from: http://csound.1045644.n5.nabble.com/Csound-General-
>>>>>>>>> f1093014.html
>>>>>>>>>> Csound mailing list
>>>>>>>>>> [hidden email]
>>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>>> Send bugs reports to
>>>>>>>>>>      https://github.com/csound/csound/issues
>>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>> Csound mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>>> Send bugs reports to
>>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> Oeyvind Brandtsegg
>>>>>>>> Professor of Music Technology
>>>>>>>> NTNU
>>>>>>>> 7491 Trondheim
>>>>>>>> Norway
>>>>>>>> Cell: +47 92 203 205
>>>>>>>>
>>>>>>>> http://www.partikkelaudio.com/
>>>>>>>> http://crossadaptive.hf.ntnu.no
>>>>>>>> http://gdsp.hf.ntnu.no/
>>>>>>>> http://soundcloud.com/brandtsegg
>>>>>>>> http://flyndresang.no/
>>>>>>>> http://soundcloud.com/t-emp
>>>>>>>>
>>>>>>>> Csound mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>>>> Send bugs reports to
>>>>>>>>       https://github.com/csound/csound/issues
>>>>>>>> Discussions of bugs and features can be posted here
>>>>>>>>
>>>>>> Csound mailing list
>>>>>> [hidden email]
>>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>>> Send bugs reports to
>>>>>>       https://github.com/csound/csound/issues
>>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>>> Csound mailing list
>>>>> [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>>> Send bugs reports to
>>>>>        https://github.com/csound/csound/issues
>>>>> Discussions of bugs and features can be posted here
>>>>>
>>>> Csound mailing list
>>>> [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>>> Send bugs reports to
>>>>        https://github.com/csound/csound/issues
>>>> Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>         https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 17:22:44 +0100
>> From:    Rene <[hidden email]>
>> Subject: --realtime flag
>>
>> Hello,
>>
>> Instruments using reinit opcode and --realtime flag seems to have a
>> faulty
>> behavior.
>> The reinit is done for the complete instrument regardless of the reinit
>> label and rireturn locations.
>>
>> (The included reinit.csd instrument prints Hello at every reinit)
>>
>> I am on linux, csound 6.10.0
>>
>> Is it normal?
>>
>>
>>
>> Best,
>> René
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 17:52:13 +0100
>> From:    Oeyvind Brandtsegg <[hidden email]>
>> Subject: Re: Noise detection
>>
>> Spectral flatness or flux might be useable indicators in this case.
>> If you need an example of how to implement it you could look at the
>> code at
>> https://github.com/Oeyvind/featexmod in the file analyze_audio.inc
>>
>> Best
>> Oeyvind
>>
>>
>> On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>
>> wrote:
>>
>>> Right yes, noise is a vague term. For my specific purpose,  I'm thinking
>>> primarily full spectrum white noise or similar...  In which case you're
>>> right, examining an FFT probably is the sensible way to go here. The
>>> goal
>>> is to be able to auto detect unwanted white noise in samples and discard
>>> those containing too much of it.
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/
>>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>>> csound/issues Discussions of bugs and features can be posted here
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 17:07:04 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: --realtime flag
>>
>> It could be a bug.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 16:23, Rene
>> <[hidden email]<mailto:[hidden email]>> wrote:
>>
>> Hello,
>>
>> Instruments using reinit opcode and --realtime flag seems to have a
>> faulty behavior.
>> The reinit is done for the complete instrument regardless of the
>> reinit label and rireturn locations.
>>
>> (The included reinit.csd instrument prints Hello at every reinit)
>>
>> I am on linux, csound 6.10.0
>>
>> Is it normal?
>>
>> Best,
>> René
>> Csound mailing list
>> [hidden email]<mailto:[hidden email]>
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can be posted here
>> <reinit.csd>
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 17:48:33 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: --realtime flag
>>
>> Actually, can you try the latest (6.11)? This version has a completely
>> overhauled realtime mode, and I remembered testing reinit and it worked.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 17:07, Victor Lazzarini
>> <[hidden email]<mailto:[hidden email]>> wrote:
>>
>> It could be a bug.
>>
>> Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy
>> Maynooth University
>> Ireland
>>
>> On 2 Mar 2018, at 16:23, Rene
>> <[hidden email]<mailto:[hidden email]>> wrote:
>>
>> Hello,
>>
>> Instruments using reinit opcode and --realtime flag seems to have a
>> faulty behavior.
>> The reinit is done for the complete instrument regardless of the
>> reinit label and rireturn locations.
>>
>> (The included reinit.csd instrument prints Hello at every reinit)
>>
>> I am on linux, csound 6.10.0
>>
>> Is it normal?
>>
>> Best,
>> René
>> Csound mailing list
>> [hidden email]<mailto:[hidden email]>
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can be posted here
>> <reinit.csd>
>> Csound mailing list
>> [hidden email]<mailto:[hidden email]>
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>> https://github.com/csound/csound/issues Discussions of bugs and
>> features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 20:20:01 +0200
>> From:    Tarmo Johannes <[hidden email]>
>> Subject: Re: Noise detection
>>
>> Hi,
>>
>> This is probably not you are after but (from the manual):
>>
>> http://www.csounds.com/manual/html/pvstencil.html
>> One of the typical uses of /pvstencil/ would be in noise reduction.
>>
>> Maybe you can reverse it somehow to get the noise level?
>> "Skipping post-normalisation will keep the original noise print
>> average amplitudes."
>>
>> I don't pretend I understand exactly how it is used.
>>
>> tarmo
>>
>> On reede, 2. märts 2018 18:52.13 EET you wrote:
>>> Spectral flatness or flux might be useable indicators in this case.
>>> If you need an example of how to implement it you could look at the
>>> code at
>>> https://github.com/Oeyvind/featexmod in the file analyze_audio.inc
>>>
>>> Best
>>> Oeyvind
>>>
>>>
>>> On Mar 2, 2018 14:12, "Peter Burgess" <[hidden email]>
>>>
>>> wrote:
>>>> Right yes, noise is a vague term. For my specific purpose,  I'm
>>>> thinking
>>>> primarily full spectrum white noise or similar...  In which case you're
>>>> right, examining an FFT probably is the sensible way to go here. The
>>>> goal
>>>> is to be able to auto detect unwanted white noise in samples and
>>>> discard
>>>> those containing too much of it.
>>>> Csound mailing list [hidden email]
>>>> https://listserv.heanet.ie/
>>>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>>>> csound/issues Discussions of bugs and features can be posted here
>>> Csound mailing list
>>> [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>>> Send bugs reports to
>>>          https://github.com/csound/csound/issues
>>> Discussions of bugs and features can be posted here
>>
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 20:26:03 +0100
>> From:    Rene <[hidden email]>
>> Subject: Re: --realtime flag
>>
>> Hello,
>>
>> Tanks for your answer.
>>
>> I have tested from git (today download)
>>
>> csound-master : give same bug as 6.10.0
>>
>> csound-develop and csound-feature-realtime : (may be wrong version, i
>> can't
>> find 6.11)
>> For both i can't test because i got a continuous message
>>
>> WARNING: instr 0 uses 3 p-fields but is given 0
>>
>> then csound hang.
>>
>>
>> Best,
>> René
>>
>>
>>
>>
>>
>>
>>
>>
>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>
>>> Actually, can you try the latest (6.11)? This version has a completely
>>> overhauled realtime mode, and I remembered testing reinit and it worked.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]>
>>> wrote:
>>>
>>> It could be a bug.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>
>>> Hello,
>>>
>>> Instruments using reinit opcode and --realtime flag seems to have a
>>> faulty
>>> behavior.
>>> The reinit is done for the complete instrument regardless of the reinit
>>> label and rireturn locations.
>>>
>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>
>>> I am on linux, csound 6.10.0
>>>
>>> Is it normal?
>>>
>>>
>>>
>>> Best,
>>> René
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/
>>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>>> csound/issues Discussions of bugs and features can be posted here
>>>
>>> <reinit.csd>
>>>
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/
>>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>>> csound/issues Discussions of bugs and features can be posted here
>>>
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/
>>> cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/
>>> csound/issues Discussions of bugs and features can be posted here
>>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 20:03:41 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: --realtime flag
>>
>> The master branch is 6.10, old code. The develop branch is 6.11, e.g.
>>
>> Csound version 6.11 beta (double samples) Mar  1 2018
>>
>> Feature-realtime has been merged into develop, so that would have similar
>> code.
>>
>> I tested your code and I am getting the WARNING, which I think it is a
>> bug in the latest checked in code. That problem is there with or without
>> —reatlime
>>
>> Once that is fixed, you can test it again.
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:
>>>
>>> Hello,
>>>
>>> Tanks for your answer.
>>>   I have tested from git (today download)
>>>
>>> csound-master : give same bug as 6.10.0
>>>
>>> csound-develop and csound-feature-realtime : (may be wrong version, i
>>> can't find 6.11)
>>> For both i can't test because i got a continuous message
>>>
>>> WARNING: instr 0 uses 3 p-fields but is given 0
>>>
>>> then csound hang.
>>>
>>>
>>> Best,
>>> René
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>> Actually, can you try the latest (6.11)? This version has a
>>> completely overhauled realtime mode, and I remembered testing reinit
>>> and it worked.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]>
>>> wrote:
>>>
>>>> It could be a bug.
>>>>
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>>
>>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Instruments using reinit opcode and --realtime flag seems to have a
>>>>> faulty behavior.
>>>>> The reinit is done for the complete instrument regardless of the
>>>>> reinit label and rireturn locations.
>>>>>
>>>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>>>
>>>>> I am on linux, csound 6.10.0
>>>>>
>>>>> Is it normal?
>>>>>
>>>>> Best,
>>>>> René
>>>>> Csound mailing list [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>> to https://github.com/csound/csound/issues Discussions of bugs and
>>>>> features can be posted here
>>>>> <reinit.csd>
>>>> Csound mailing list [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>> features can be posted here
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and
>>> features can be posted here
>>>
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and
>>> features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 20:09:04 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: --realtime flag
>>
>> actually, it’s a problem with realtime. I’ll fix it. I think it is to
>> do with
>> timout, not reinit.
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:
>>>
>>> Hello,
>>>
>>> Tanks for your answer.
>>>   I have tested from git (today download)
>>>
>>> csound-master : give same bug as 6.10.0
>>>
>>> csound-develop and csound-feature-realtime : (may be wrong version, i
>>> can't find 6.11)
>>> For both i can't test because i got a continuous message
>>>
>>> WARNING: instr 0 uses 3 p-fields but is given 0
>>>
>>> then csound hang.
>>>
>>>
>>> Best,
>>> René
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>> Actually, can you try the latest (6.11)? This version has a
>>> completely overhauled realtime mode, and I remembered testing reinit
>>> and it worked.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]>
>>> wrote:
>>>
>>>> It could be a bug.
>>>>
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>>
>>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Instruments using reinit opcode and --realtime flag seems to have a
>>>>> faulty behavior.
>>>>> The reinit is done for the complete instrument regardless of the
>>>>> reinit label and rireturn locations.
>>>>>
>>>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>>>
>>>>> I am on linux, csound 6.10.0
>>>>>
>>>>> Is it normal?
>>>>>
>>>>> Best,
>>>>> René
>>>>> Csound mailing list [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>> to https://github.com/csound/csound/issues Discussions of bugs and
>>>>> features can be posted here
>>>>> <reinit.csd>
>>>> Csound mailing list [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>> features can be posted here
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and
>>> features can be posted here
>>>
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and
>>> features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> Date:    Fri, 2 Mar 2018 21:29:44 +0000
>> From:    Victor Lazzarini <[hidden email]>
>> Subject: Re: --realtime flag
>>
>> I have fixed this now (in git develop), but there are a couple of
>> caveats:
>>
>> 1) reinit should be avoided in --realtime mode: it stops performance to
>> run a reinit pass, and that is not a good idea. Even though it runs the
>> reinit on a separate thread, performance has to pause for
>> reinitialisation.
>>
>> 2) opcodes like timeout would potentially have gaps in their time
>> counting
>> due to the reinit pause.
>>
>> In other words: although the instrument will work (with maybe some timout
>> time counting issues), it’s not a good realtime instrument.
>>
>> ========================
>> Prof. Victor Lazzarini
>> Dean of Arts, Celtic Studies, and Philosophy,
>> Maynooth University,
>> Maynooth, Co Kildare, Ireland
>> Tel: 00 353 7086936
>> Fax: 00 353 1 7086952
>>
>>> On 2 Mar 2018, at 19:26, Rene <[hidden email]> wrote:
>>>
>>> Hello,
>>>
>>> Tanks for your answer.
>>>   I have tested from git (today download)
>>>
>>> csound-master : give same bug as 6.10.0
>>>
>>> csound-develop and csound-feature-realtime : (may be wrong version, i
>>> can't find 6.11)
>>> For both i can't test because i got a continuous message
>>>
>>> WARNING: instr 0 uses 3 p-fields but is given 0
>>>
>>> then csound hang.
>>>
>>>
>>> Best,
>>> René
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2018-03-02 18:48 GMT+01:00 Victor Lazzarini <[hidden email]>:
>>> Actually, can you try the latest (6.11)? This version has a
>>> completely overhauled realtime mode, and I remembered testing reinit
>>> and it worked.
>>>
>>> Victor Lazzarini
>>> Dean of Arts, Celtic Studies, and Philosophy
>>> Maynooth University
>>> Ireland
>>>
>>> On 2 Mar 2018, at 17:07, Victor Lazzarini <[hidden email]>
>>> wrote:
>>>
>>>> It could be a bug.
>>>>
>>>> Victor Lazzarini
>>>> Dean of Arts, Celtic Studies, and Philosophy
>>>> Maynooth University
>>>> Ireland
>>>>
>>>> On 2 Mar 2018, at 16:23, Rene <[hidden email]> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Instruments using reinit opcode and --realtime flag seems to have a
>>>>> faulty behavior.
>>>>> The reinit is done for the complete instrument regardless of the
>>>>> reinit label and rireturn locations.
>>>>>
>>>>> (The included reinit.csd instrument prints Hello at every reinit)
>>>>>
>>>>> I am on linux, csound 6.10.0
>>>>>
>>>>> Is it normal?
>>>>>
>>>>> Best,
>>>>> René
>>>>> Csound mailing list [hidden email]
>>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports
>>>>> to https://github.com/csound/csound/issues Discussions of bugs and
>>>>> features can be posted here
>>>>> <reinit.csd>
>>>> Csound mailing list [hidden email]
>>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>>> https://github.com/csound/csound/issues Discussions of bugs and
>>>> features can be posted here
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and
>>> features can be posted here
>>>
>>> Csound mailing list [hidden email]
>>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to
>>> https://github.com/csound/csound/issues Discussions of bugs and
>>> features can be posted here
>>
>> Csound mailing list
>> [hidden email]
>> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
>> Send bugs reports to
>>          https://github.com/csound/csound/issues
>> Discussions of bugs and features can be posted here
>>
>> ------------------------------
>>
>> End of CSOUND Digest - 1 Mar 2018 to 2 Mar 2018 (#2018-58)
>> **********************************************************
>>
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
In reply to this post by Jan Jacob Hofmann
Dear Joachim,

yes, at interfaces/CMakeLists.txt:92  it looks exactly like this:

                 include(${SWIG_USE_FILE})

so I changed BUILD_PYTHON_INTERFACE:BOOL=OFF

in my cs6Make/CmakeCache.txt (in my case in line 125)


...and compiled again. The full output is to be seen below,
  to me like something still did not went well.

I also tried to comment out line 92 like this
// include(${SWIG_USE_FILE})

..but the result after compiling looked the same.

I wonder if I am using something else but the master branch.

Best,

Jan Jacob



janjacobhofmann@janjacobhofmann-ThinkPad-T430:~/csound/cs6make$ cmake
../csound-- /home/janjacobhofmann/csound/csound
-- Not using Custom.cmake file.
-- LIBRARY INSTALL DIR: lib
-- Building with 64-bit floats
-- BUILD_BIN_DIR set to /home/janjacobhofmann/csound/cs6make.
-- BUILD_LIB_DIR set to /home/janjacobhofmann/csound/cs6make.
-- BUILD_PLUGINS_DIR set to /home/janjacobhofmann/csound/cs6make.
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Could NOT find LUAJIT (missing:  LUAJIT_LIBRARY LUAJIT_INCLUDE_DIR)
-- Could NOT find MUSICXML (missing:  MUSICXML_LIBRARY
MUSICXML_INCLUDE_DIR)
-- Could NOT find PORTSMF (missing:  PORTSMF_INCLUDE_DIR)
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
suitable version "2.7.12", minimum required is "2.7")
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Found SWIG: /usr/bin/swig2.0 (found version "2.0.11")
-- Could NOT find VSTSDK2X (missing:  VSTSDK2X_INCLUDE_DIR)
-- Using atomic builtins.
-- USE_LRINT is enabled.
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Not using CURL for urls - not found.
-- GIT: /usr/bin/git
-- HASH: f5bcd83a9799536980d0f674bb7525f45f800490
-- Not building with new parser debugging.
-- Building with multicore support.
-- USE_GETTEXT is enabled.
-- Using GNU gettext.
-- Setting textdomain to /usr/local/share/locale.
-- Building on Linux.
--   ADDING LIBRT LIBRARY: /usr/lib/x86_64-linux-gnu/librt.so.
-- ## Building Opcodes ##
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
version "2.7.12")
-- BUILD_CHUA_OPCODES is enabled.
-- BUILD_DSSI_OPCODES is enabled.
-- BUILD_FLUID_OPCODES is enabled.
-- BUILD_JACK_OPCODES is enabled.
-- BUILD_LINEAR_ALGEBRA_OPCODES is enabled.
-- BUILD_OSC_OPCODES is enabled.
-- BUILD_IMAGE_OPCODES is enabled.
-- BUILD_PYTHON_OPCODES is enabled.
-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_OPCODES
-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_OPCODES
-- BUILD_LUA_OPCODES is disabled.
-- WIIUSE_H="", so disabling BUILD_WIIMOTE_OPCODES
-- WIIUSE_LIB="WIIUSE_LIB-NOTFOUND", so disabling BUILD_WIIMOTE_OPCODES
-- BUILD_WIIMOTE_OPCODES is disabled.
-- P5GLOVE_H="", so disabling BUILD_P5GLOVE_OPCODES
-- BUILD_P5GLOVE_OPCODES is disabled.
-- BUILD_FAUST_OPCODES is disabled.
-- BUILD_VST4CS_OPCODES is disabled.
-- VSTSDK2X_INCLUDE_DIR: VSTSDK2X_INCLUDE_DIR-NOTFOUND
-- BUILD_ABLETON_LINK_OPCODES is disabled.
-- BUILD_STK_OPCODES is enabled.
-- Building STK opcodes.
-- Could NOT find HDF5 (missing:  HDF5_LIBRARIES HDF5_INCLUDE_DIRS)
-- HDF5_FOUND="FALSE", so disabling BUILD_HDF5_OPCODES
-- BUILD_HDF5_OPCODES is disabled.
-- websockets_library="websockets_library-NOTFOUND", so disabling
BUILD_WEBSOCKET_OPCODE
-- BUILD_WEBSOCKET_OPCODE is disabled.
--
-- ## REALTIME AUDIO AND MIDI ##
-- APPLE="", so disabling USE_COREMIDI
-- COREMIDI_INCLUDE_PATH="COREMIDI_INCLUDE_PATH-NOTFOUND", so disabling
USE_COREMIDI
-- COREMIDI_LIBRARY="COREMIDI_LIBRARY-NOTFOUND", so disabling USE_COREMIDI
-- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so
disabling USE_COREMIDI
-- USE_COREMIDI is disabled.
-- APPLE="", so disabling USE_AUDIOUNIT
-- COREAUDIO_INCLUDE_PATH="COREAUDIO_INCLUDE_PATH-NOTFOUND", so
disabling USE_AUDIOUNIT
-- COREAUDIO_LIBRARY="COREAUDIO_LIBRARY-NOTFOUND", so disabling
USE_AUDIOUNIT
-- AUDIOUNIT_INCLUDE_PATH="AUDIOUNIT_INCLUDE_PATH-NOTFOUND", so
disabling USE_AUDIOUNIT
-- AUDIOUNIT_LIBRARY="AUDIOUNIT_LIBRARY-NOTFOUND", so disabling
USE_AUDIOUNIT
-- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so
disabling USE_AUDIOUNIT
-- USE_AUDIOUNIT is disabled.
-- USE_ALSA is enabled.
-- USE_PULSEAUDIO is enabled.
-- USE_PORTAUDIO is enabled.
-- Building rtpa module.
-- USE_PORTMIDI is enabled.
-- USE_JACK is enabled.
-- USE_FLTK is enabled.
-- BUILD_VIRTUAL_KEYBOARD is enabled.
--
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Building C++ interface library.
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11",
minimum required is "2.0")
-- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so
-- BUILD_PYTHON_INTERFACE is disabled.
-- BUILD_JAVA_INTERFACE is enabled.
-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling
BUILD_LUA_INTERFACE
-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE
-- BUILD_LUA_INTERFACE is disabled.
-- SWIG_USE_FILE:
CMake Error at interfaces/CMakeLists.txt:92 (include):
   include called with wrong number of arguments.  include() only takes one
   file.


-- JNI INCLUDE set to
/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include.
CMake Error at interfaces/CMakeLists.txt:158 (SWIG_ADD_MODULE):
   Unknown CMake command "SWIG_ADD_MODULE".


-- Configuring incomplete, errors occurred!
See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeOutput.log".
See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeError.log".

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Steven Yi
It might be the version of CMake (3.5), I saw this online:

https://github.com/robotology/yarp/issues/1178

On Sat, Mar 3, 2018 at 10:10 AM, Jan Jacob Hofmann
<[hidden email]> wrote:

> Dear Joachim,
>
> yes, at interfaces/CMakeLists.txt:92  it looks exactly like this:
>
>                  include(${SWIG_USE_FILE})
>
> so I changed BUILD_PYTHON_INTERFACE:BOOL=OFF
>
> in my cs6Make/CmakeCache.txt (in my case in line 125)
>
>
> ...and compiled again. The full output is to be seen below,
>  to me like something still did not went well.
>
> I also tried to comment out line 92 like this
> // include(${SWIG_USE_FILE})
>
> ..but the result after compiling looked the same.
>
> I wonder if I am using something else but the master branch.
>
> Best,
>
> Jan Jacob
>
>
>
> janjacobhofmann@janjacobhofmann-ThinkPad-T430:~/csound/cs6make$ cmake
> ../csound-- /home/janjacobhofmann/csound/csound
> -- Not using Custom.cmake file.
> -- LIBRARY INSTALL DIR: lib
> -- Building with 64-bit floats
> -- BUILD_BIN_DIR set to /home/janjacobhofmann/csound/cs6make.
> -- BUILD_LIB_DIR set to /home/janjacobhofmann/csound/cs6make.
> -- BUILD_PLUGINS_DIR set to /home/janjacobhofmann/csound/cs6make.
> -- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
> -- Could NOT find LUAJIT (missing:  LUAJIT_LIBRARY LUAJIT_INCLUDE_DIR)
> -- Could NOT find MUSICXML (missing:  MUSICXML_LIBRARY MUSICXML_INCLUDE_DIR)
> -- Could NOT find PORTSMF (missing:  PORTSMF_INCLUDE_DIR)
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> suitable version "2.7.12", minimum required is "2.7")
> -- Command "/usr/bin/swig2.0 -swiglib" failed with output:
>
> -- Found SWIG: /usr/bin/swig2.0 (found version "2.0.11")
> -- Could NOT find VSTSDK2X (missing:  VSTSDK2X_INCLUDE_DIR)
> -- Using atomic builtins.
> -- USE_LRINT is enabled.
> -- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
> -- Not using CURL for urls - not found.
> -- GIT: /usr/bin/git
> -- HASH: f5bcd83a9799536980d0f674bb7525f45f800490
> -- Not building with new parser debugging.
> -- Building with multicore support.
> -- USE_GETTEXT is enabled.
> -- Using GNU gettext.
> -- Setting textdomain to /usr/local/share/locale.
> -- Building on Linux.
> --   ADDING LIBRT LIBRARY: /usr/lib/x86_64-linux-gnu/librt.so.
> -- ## Building Opcodes ##
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> version "2.7.12")
> -- BUILD_CHUA_OPCODES is enabled.
> -- BUILD_DSSI_OPCODES is enabled.
> -- BUILD_FLUID_OPCODES is enabled.
> -- BUILD_JACK_OPCODES is enabled.
> -- BUILD_LINEAR_ALGEBRA_OPCODES is enabled.
> -- BUILD_OSC_OPCODES is enabled.
> -- BUILD_IMAGE_OPCODES is enabled.
> -- BUILD_PYTHON_OPCODES is enabled.
> -- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_OPCODES
> -- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_OPCODES
> -- BUILD_LUA_OPCODES is disabled.
> -- WIIUSE_H="", so disabling BUILD_WIIMOTE_OPCODES
> -- WIIUSE_LIB="WIIUSE_LIB-NOTFOUND", so disabling BUILD_WIIMOTE_OPCODES
> -- BUILD_WIIMOTE_OPCODES is disabled.
> -- P5GLOVE_H="", so disabling BUILD_P5GLOVE_OPCODES
> -- BUILD_P5GLOVE_OPCODES is disabled.
> -- BUILD_FAUST_OPCODES is disabled.
> -- BUILD_VST4CS_OPCODES is disabled.
> -- VSTSDK2X_INCLUDE_DIR: VSTSDK2X_INCLUDE_DIR-NOTFOUND
> -- BUILD_ABLETON_LINK_OPCODES is disabled.
> -- BUILD_STK_OPCODES is enabled.
> -- Building STK opcodes.
> -- Could NOT find HDF5 (missing:  HDF5_LIBRARIES HDF5_INCLUDE_DIRS)
> -- HDF5_FOUND="FALSE", so disabling BUILD_HDF5_OPCODES
> -- BUILD_HDF5_OPCODES is disabled.
> -- websockets_library="websockets_library-NOTFOUND", so disabling
> BUILD_WEBSOCKET_OPCODE
> -- BUILD_WEBSOCKET_OPCODE is disabled.
> --
> -- ## REALTIME AUDIO AND MIDI ##
> -- APPLE="", so disabling USE_COREMIDI
> -- COREMIDI_INCLUDE_PATH="COREMIDI_INCLUDE_PATH-NOTFOUND", so disabling
> USE_COREMIDI
> -- COREMIDI_LIBRARY="COREMIDI_LIBRARY-NOTFOUND", so disabling USE_COREMIDI
> -- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so disabling
> USE_COREMIDI
> -- USE_COREMIDI is disabled.
> -- APPLE="", so disabling USE_AUDIOUNIT
> -- COREAUDIO_INCLUDE_PATH="COREAUDIO_INCLUDE_PATH-NOTFOUND", so disabling
> USE_AUDIOUNIT
> -- COREAUDIO_LIBRARY="COREAUDIO_LIBRARY-NOTFOUND", so disabling
> USE_AUDIOUNIT
> -- AUDIOUNIT_INCLUDE_PATH="AUDIOUNIT_INCLUDE_PATH-NOTFOUND", so disabling
> USE_AUDIOUNIT
> -- AUDIOUNIT_LIBRARY="AUDIOUNIT_LIBRARY-NOTFOUND", so disabling
> USE_AUDIOUNIT
> -- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so disabling
> USE_AUDIOUNIT
> -- USE_AUDIOUNIT is disabled.
> -- USE_ALSA is enabled.
> -- USE_PULSEAUDIO is enabled.
> -- USE_PORTAUDIO is enabled.
> -- Building rtpa module.
> -- USE_PORTMIDI is enabled.
> -- USE_JACK is enabled.
> -- USE_FLTK is enabled.
> -- BUILD_VIRTUAL_KEYBOARD is enabled.
> --
> -- Command "/usr/bin/swig2.0 -swiglib" failed with output:
>
> -- Building C++ interface library.
> -- Command "/usr/bin/swig2.0 -swiglib" failed with output:
>
> -- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11", minimum
> required is "2.0")
> -- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so
> -- BUILD_PYTHON_INTERFACE is disabled.
> -- BUILD_JAVA_INTERFACE is enabled.
> -- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling
> BUILD_LUA_INTERFACE
> -- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE
> -- BUILD_LUA_INTERFACE is disabled.
> -- SWIG_USE_FILE:
> CMake Error at interfaces/CMakeLists.txt:92 (include):
>   include called with wrong number of arguments.  include() only takes one
>   file.
>
>
> -- JNI INCLUDE set to
> /usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include.
> CMake Error at interfaces/CMakeLists.txt:158 (SWIG_ADD_MODULE):
>   Unknown CMake command "SWIG_ADD_MODULE".
>
>
> -- Configuring incomplete, errors occurred!
> See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeOutput.log".
> See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeError.log".
>
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Michael Gogins-2
In reply to this post by Jan Jacob Hofmann
You should delete CMakeCache.txt after you make such changes. 

On Mar 3, 2018 12:10, "Jan Jacob Hofmann" <[hidden email]> wrote:
Dear Joachim,

yes, at interfaces/CMakeLists.txt:92  it looks exactly like this:

                 include(${SWIG_USE_FILE})

so I changed BUILD_PYTHON_INTERFACE:BOOL=OFF

in my cs6Make/CmakeCache.txt (in my case in line 125)


...and compiled again. The full output is to be seen below,
 to me like something still did not went well.

I also tried to comment out line 92 like this
// include(${SWIG_USE_FILE})

..but the result after compiling looked the same.

I wonder if I am using something else but the master branch.

Best,

Jan Jacob



janjacobhofmann@janjacobhofmann-ThinkPad-T430:~/csound/cs6make$ cmake ../csound-- /home/janjacobhofmann/csound/csound
-- Not using Custom.cmake file.
-- LIBRARY INSTALL DIR: lib
-- Building with 64-bit floats
-- BUILD_BIN_DIR set to /home/janjacobhofmann/csound/cs6make.
-- BUILD_LIB_DIR set to /home/janjacobhofmann/csound/cs6make.
-- BUILD_PLUGINS_DIR set to /home/janjacobhofmann/csound/cs6make.
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Could NOT find LUAJIT (missing:  LUAJIT_LIBRARY LUAJIT_INCLUDE_DIR)
-- Could NOT find MUSICXML (missing:  MUSICXML_LIBRARY MUSICXML_INCLUDE_DIR)
-- Could NOT find PORTSMF (missing:  PORTSMF_INCLUDE_DIR)
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.12", minimum required is "2.7")
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Found SWIG: /usr/bin/swig2.0 (found version "2.0.11")
-- Could NOT find VSTSDK2X (missing:  VSTSDK2X_INCLUDE_DIR)
-- Using atomic builtins.
-- USE_LRINT is enabled.
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Not using CURL for urls - not found.
-- GIT: /usr/bin/git
-- HASH: f5bcd83a9799536980d0f674bb7525f45f800490
-- Not building with new parser debugging.
-- Building with multicore support.
-- USE_GETTEXT is enabled.
-- Using GNU gettext.
-- Setting textdomain to /usr/local/share/locale.
-- Building on Linux.
--   ADDING LIBRT LIBRARY: /usr/lib/x86_64-linux-gnu/librt.so.
-- ## Building Opcodes ##
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.12")
-- BUILD_CHUA_OPCODES is enabled.
-- BUILD_DSSI_OPCODES is enabled.
-- BUILD_FLUID_OPCODES is enabled.
-- BUILD_JACK_OPCODES is enabled.
-- BUILD_LINEAR_ALGEBRA_OPCODES is enabled.
-- BUILD_OSC_OPCODES is enabled.
-- BUILD_IMAGE_OPCODES is enabled.
-- BUILD_PYTHON_OPCODES is enabled.
-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_OPCODES
-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_OPCODES
-- BUILD_LUA_OPCODES is disabled.
-- WIIUSE_H="", so disabling BUILD_WIIMOTE_OPCODES
-- WIIUSE_LIB="WIIUSE_LIB-NOTFOUND", so disabling BUILD_WIIMOTE_OPCODES
-- BUILD_WIIMOTE_OPCODES is disabled.
-- P5GLOVE_H="", so disabling BUILD_P5GLOVE_OPCODES
-- BUILD_P5GLOVE_OPCODES is disabled.
-- BUILD_FAUST_OPCODES is disabled.
-- BUILD_VST4CS_OPCODES is disabled.
-- VSTSDK2X_INCLUDE_DIR: VSTSDK2X_INCLUDE_DIR-NOTFOUND
-- BUILD_ABLETON_LINK_OPCODES is disabled.
-- BUILD_STK_OPCODES is enabled.
-- Building STK opcodes.
-- Could NOT find HDF5 (missing:  HDF5_LIBRARIES HDF5_INCLUDE_DIRS)
-- HDF5_FOUND="FALSE", so disabling BUILD_HDF5_OPCODES
-- BUILD_HDF5_OPCODES is disabled.
-- websockets_library="websockets_library-NOTFOUND", so disabling BUILD_WEBSOCKET_OPCODE
-- BUILD_WEBSOCKET_OPCODE is disabled.
--
-- ## REALTIME AUDIO AND MIDI ##
-- APPLE="", so disabling USE_COREMIDI
-- COREMIDI_INCLUDE_PATH="COREMIDI_INCLUDE_PATH-NOTFOUND", so disabling USE_COREMIDI
-- COREMIDI_LIBRARY="COREMIDI_LIBRARY-NOTFOUND", so disabling USE_COREMIDI
-- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so disabling USE_COREMIDI
-- USE_COREMIDI is disabled.
-- APPLE="", so disabling USE_AUDIOUNIT
-- COREAUDIO_INCLUDE_PATH="COREAUDIO_INCLUDE_PATH-NOTFOUND", so disabling USE_AUDIOUNIT
-- COREAUDIO_LIBRARY="COREAUDIO_LIBRARY-NOTFOUND", so disabling USE_AUDIOUNIT
-- AUDIOUNIT_INCLUDE_PATH="AUDIOUNIT_INCLUDE_PATH-NOTFOUND", so disabling USE_AUDIOUNIT
-- AUDIOUNIT_LIBRARY="AUDIOUNIT_LIBRARY-NOTFOUND", so disabling USE_AUDIOUNIT
-- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so disabling USE_AUDIOUNIT
-- USE_AUDIOUNIT is disabled.
-- USE_ALSA is enabled.
-- USE_PULSEAUDIO is enabled.
-- USE_PORTAUDIO is enabled.
-- Building rtpa module.
-- USE_PORTMIDI is enabled.
-- USE_JACK is enabled.
-- USE_FLTK is enabled.
-- BUILD_VIRTUAL_KEYBOARD is enabled.
--
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Building C++ interface library.
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11", minimum required is "2.0")
-- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so
-- BUILD_PYTHON_INTERFACE is disabled.
-- BUILD_JAVA_INTERFACE is enabled.
-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_INTERFACE
-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE
-- BUILD_LUA_INTERFACE is disabled.
-- SWIG_USE_FILE:
CMake Error at interfaces/CMakeLists.txt:92 (include):
  include called with wrong number of arguments.  include() only takes one
  file.


-- JNI INCLUDE set to /usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include.
CMake Error at interfaces/CMakeLists.txt:158 (SWIG_ADD_MODULE):
  Unknown CMake command "SWIG_ADD_MODULE".


-- Configuring incomplete, errors occurred!
See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeOutput.log".
See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeError.log".

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

rorywalsh
I'm also use 3.5. Maybe you can just nuke the Csound dir and start again.

On 3 Mar 2018 4:23 p.m., "Michael Gogins" <[hidden email]> wrote:
You should delete CMakeCache.txt after you make such changes. 

On Mar 3, 2018 12:10, "Jan Jacob Hofmann" <[hidden email]> wrote:
Dear Joachim,

yes, at interfaces/CMakeLists.txt:92  it looks exactly like this:

                 include(${SWIG_USE_FILE})

so I changed BUILD_PYTHON_INTERFACE:BOOL=OFF

in my cs6Make/CmakeCache.txt (in my case in line 125)


...and compiled again. The full output is to be seen below,
 to me like something still did not went well.

I also tried to comment out line 92 like this
// include(${SWIG_USE_FILE})

..but the result after compiling looked the same.

I wonder if I am using something else but the master branch.

Best,

Jan Jacob



janjacobhofmann@janjacobhofmann-ThinkPad-T430:~/csound/cs6make$ cmake ../csound-- /home/janjacobhofmann/csound/csound
-- Not using Custom.cmake file.
-- LIBRARY INSTALL DIR: lib
-- Building with 64-bit floats
-- BUILD_BIN_DIR set to /home/janjacobhofmann/csound/cs6make.
-- BUILD_LIB_DIR set to /home/janjacobhofmann/csound/cs6make.
-- BUILD_PLUGINS_DIR set to /home/janjacobhofmann/csound/cs6make.
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Could NOT find LUAJIT (missing:  LUAJIT_LIBRARY LUAJIT_INCLUDE_DIR)
-- Could NOT find MUSICXML (missing:  MUSICXML_LIBRARY MUSICXML_INCLUDE_DIR)
-- Could NOT find PORTSMF (missing:  PORTSMF_INCLUDE_DIR)
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.12", minimum required is "2.7")
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Found SWIG: /usr/bin/swig2.0 (found version "2.0.11")
-- Could NOT find VSTSDK2X (missing:  VSTSDK2X_INCLUDE_DIR)
-- Using atomic builtins.
-- USE_LRINT is enabled.
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Not using CURL for urls - not found.
-- GIT: /usr/bin/git
-- HASH: f5bcd83a9799536980d0f674bb7525f45f800490
-- Not building with new parser debugging.
-- Building with multicore support.
-- USE_GETTEXT is enabled.
-- Using GNU gettext.
-- Setting textdomain to /usr/local/share/locale.
-- Building on Linux.
--   ADDING LIBRT LIBRARY: /usr/lib/x86_64-linux-gnu/librt.so.
-- ## Building Opcodes ##
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.12")
-- BUILD_CHUA_OPCODES is enabled.
-- BUILD_DSSI_OPCODES is enabled.
-- BUILD_FLUID_OPCODES is enabled.
-- BUILD_JACK_OPCODES is enabled.
-- BUILD_LINEAR_ALGEBRA_OPCODES is enabled.
-- BUILD_OSC_OPCODES is enabled.
-- BUILD_IMAGE_OPCODES is enabled.
-- BUILD_PYTHON_OPCODES is enabled.
-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_OPCODES
-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_OPCODES
-- BUILD_LUA_OPCODES is disabled.
-- WIIUSE_H="", so disabling BUILD_WIIMOTE_OPCODES
-- WIIUSE_LIB="WIIUSE_LIB-NOTFOUND", so disabling BUILD_WIIMOTE_OPCODES
-- BUILD_WIIMOTE_OPCODES is disabled.
-- P5GLOVE_H="", so disabling BUILD_P5GLOVE_OPCODES
-- BUILD_P5GLOVE_OPCODES is disabled.
-- BUILD_FAUST_OPCODES is disabled.
-- BUILD_VST4CS_OPCODES is disabled.
-- VSTSDK2X_INCLUDE_DIR: VSTSDK2X_INCLUDE_DIR-NOTFOUND
-- BUILD_ABLETON_LINK_OPCODES is disabled.
-- BUILD_STK_OPCODES is enabled.
-- Building STK opcodes.
-- Could NOT find HDF5 (missing:  HDF5_LIBRARIES HDF5_INCLUDE_DIRS)
-- HDF5_FOUND="FALSE", so disabling BUILD_HDF5_OPCODES
-- BUILD_HDF5_OPCODES is disabled.
-- websockets_library="websockets_library-NOTFOUND", so disabling BUILD_WEBSOCKET_OPCODE
-- BUILD_WEBSOCKET_OPCODE is disabled.
--
-- ## REALTIME AUDIO AND MIDI ##
-- APPLE="", so disabling USE_COREMIDI
-- COREMIDI_INCLUDE_PATH="COREMIDI_INCLUDE_PATH-NOTFOUND", so disabling USE_COREMIDI
-- COREMIDI_LIBRARY="COREMIDI_LIBRARY-NOTFOUND", so disabling USE_COREMIDI
-- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so disabling USE_COREMIDI
-- USE_COREMIDI is disabled.
-- APPLE="", so disabling USE_AUDIOUNIT
-- COREAUDIO_INCLUDE_PATH="COREAUDIO_INCLUDE_PATH-NOTFOUND", so disabling USE_AUDIOUNIT
-- COREAUDIO_LIBRARY="COREAUDIO_LIBRARY-NOTFOUND", so disabling USE_AUDIOUNIT
-- AUDIOUNIT_INCLUDE_PATH="AUDIOUNIT_INCLUDE_PATH-NOTFOUND", so disabling USE_AUDIOUNIT
-- AUDIOUNIT_LIBRARY="AUDIOUNIT_LIBRARY-NOTFOUND", so disabling USE_AUDIOUNIT
-- COREFOUNDATION_LIBRARY="COREFOUNDATION_LIBRARY-NOTFOUND", so disabling USE_AUDIOUNIT
-- USE_AUDIOUNIT is disabled.
-- USE_ALSA is enabled.
-- USE_PULSEAUDIO is enabled.
-- USE_PORTAUDIO is enabled.
-- Building rtpa module.
-- USE_PORTMIDI is enabled.
-- USE_JACK is enabled.
-- USE_FLTK is enabled.
-- BUILD_VIRTUAL_KEYBOARD is enabled.
--
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Building C++ interface library.
-- Command "/usr/bin/swig2.0 -swiglib" failed with output:

-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11", minimum required is "2.0")
-- PYTHON_LIBRARY: /usr/lib/x86_64-linux-gnu/libpython2.7.so
-- BUILD_PYTHON_INTERFACE is disabled.
-- BUILD_JAVA_INTERFACE is enabled.
-- LUAJIT_LIBRARY="LUAJIT_LIBRARY-NOTFOUND", so disabling BUILD_LUA_INTERFACE
-- LUA_H_PATH="LUA_H_PATH-NOTFOUND", so disabling BUILD_LUA_INTERFACE
-- BUILD_LUA_INTERFACE is disabled.
-- SWIG_USE_FILE:
CMake Error at interfaces/CMakeLists.txt:92 (include):
  include called with wrong number of arguments.  include() only takes one
  file.


-- JNI INCLUDE set to /usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include;/usr/lib/jvm/default-java/include.
CMake Error at interfaces/CMakeLists.txt:158 (SWIG_ADD_MODULE):
  Unknown CMake command "SWIG_ADD_MODULE".


-- Configuring incomplete, errors occurred!
See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeOutput.log".
See also "/home/janjacobhofmann/csound/cs6make/CMakeFiles/CMakeError.log".

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
       https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Csound mailing list [hidden email] https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND Send bugs reports to https://github.com/csound/csound/issues Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
In reply to this post by Jan Jacob Hofmann
Dear Steven,

yeah, that looks a lot like my problem. I would like to update my cmake
3.5.1 to 3.10. As there is a multitude of very different descriptions on
the net about how to do that I am very insecure which way to go as I do
not want to break things. Has somebody a hint for me how to do it in the
right way?

Else I might want also to follow Joachims an Michaels advice again...

Best,

Jan Jacob


 > It might be the version of CMake (3.5), I saw this online:

 > https://github.com/robotology/yarp/issues/1178

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Steven Yi
Hi Jan Jacob,

I think 3.5 must be fine and the problem may be with Swig.  I checked
here and with Bash on Ubuntu on Windows I have equivalent of Ubuntu
16.04 installed. Here it is Cmake 3.5.1 and Swig 3.0.8. I think the
error you are getting has to do with looking for a UseSWIG.cmake and
not finding it, then trying to include it.

Could you try:


sudo apt install swig


then try deleting your CMakeCache.txt file in your build folder and
re-running cmake.

steven

On Sat, Mar 3, 2018 at 12:00 PM, Jan Jacob Hofmann
<[hidden email]> wrote:

> Dear Steven,
>
> yeah, that looks a lot like my problem. I would like to update my cmake
> 3.5.1 to 3.10. As there is a multitude of very different descriptions on the
> net about how to do that I am very insecure which way to go as I do not want
> to break things. Has somebody a hint for me how to do it in the right way?
>
> Else I might want also to follow Joachims an Michaels advice again...
>
> Best,
>
> Jan Jacob
>
>
>> It might be the version of CMake (3.5), I saw this online:
>
>> https://github.com/robotology/yarp/issues/1178
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

Jan Jacob Hofmann
In reply to this post by Jan Jacob Hofmann
Dear Steven, dear list

success - Csound 6.10 is installed and works!!! Thanks to all of you for
the plenty responses!



Here is what I finally did:


sudo apt install swig

To my surprise Terminal told me, that swig was already updated to the
latest release, wich is version 3.08.
It also suggested to run sudo apt autoremove

..and some of the old files got removed

I checked:
swig -version

And the answer was

SWIG Version 3.0.8

Then I deleted CMakeCache.txt and I compiled again. Now it compiled
perfectly, the result is a bliss:

csound --version
0dBFS level = 32768.0
--Csound version 6.10 (double samples) Mar  3 2018

Thanks again so much!

Best,

Jan Jacob

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
Reply | Threaded
Open this post in threaded view
|

Re: [Csnd] Building (updating) Csound on Ubuntu 16.04 - some advice sought

joachim-3
congrats — and thanks for describing what you did; certainly good to know.
        joachim



On 03/03/18 21:53, Jan Jacob Hofmann wrote:

> Dear Steven, dear list
>
> success - Csound 6.10 is installed and works!!! Thanks to all of you for
> the plenty responses!
>
>
>
> Here is what I finally did:
>
>
> sudo apt install swig
>
> To my surprise Terminal told me, that swig was already updated to the
> latest release, wich is version 3.08.
> It also suggested to run sudo apt autoremove
>
> ..and some of the old files got removed
>
> I checked:
> swig -version
>
> And the answer was
>
> SWIG Version 3.0.8
>
> Then I deleted CMakeCache.txt and I compiled again. Now it compiled
> perfectly, the result is a bliss:
>
> csound --version
> 0dBFS level = 32768.0
> --Csound version 6.10 (double samples) Mar  3 2018
>
> Thanks again so much!
>
> Best,
>
> Jan Jacob
>
> Csound mailing list
> [hidden email]
> https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
> Send bugs reports to
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
>

Csound mailing list
[hidden email]
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
        https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here