I read your subject and thought instantly of the answer 'thou shall
not use absynth!", then I realised it's a typo. As for an answer I'm
not really sure, either approach seems fine. My first thoughts were,
recursive UDO with the frequency ratios stored in a table?

Rory.


On 21 July 2010 06:57, Stefan Thomas  wrote:
> Dear community,
> I have in mind a sound consisting of some unsual partials (quoted at the end
> of the mail).
> My question is:
> Would You recommand to synthesize this sound with adsynt or with a set of
> oscil-opcodes?
> And if You would recommand adsynt, how could I get the desired partials?
> I would be thankful for any hint!
>
> Here my list of partials:
> iratio = 1.05555005944424078911 ; 15th root from 9/4
> ifundamental = icps
> ipartialB =icps*2.25
> ipartialC = icps*iratio^24
> ipartialD = icps*5.0625
> ipartialE = icps*iratio^35
> ipartialF = icps*iratio^40
> ipartialG = icps*11.390625
> ipartialH = icps*iratio^49
> ipartialI = icps*iratio^53
> ipartialK = icps*iratio^56;
> ipartialL = icps*iratio^58 ;
> ipartialM = icps*iratio^60
> ipartialN = icps*iratio^62
>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

p.s. I'm pretty sure the recursive UDO idea will only work if you
don't need to alter the individual amps of the partials later on.

On 21 July 2010 09:36, Rory Walsh  wrote:
> I read your subject and thought instantly of the answer 'thou shall
> not use absynth!", then I realised it's a typo. As for an answer I'm
> not really sure, either approach seems fine. My first thoughts were,
> recursive UDO with the frequency ratios stored in a table?
>
> Rory.
>
>
> On 21 July 2010 06:57, Stefan Thomas  wrote:
>> Dear community,
>> I have in mind a sound consisting of some unsual partials (quoted at the end
>> of the mail).
>> My question is:
>> Would You recommand to synthesize this sound with adsynt or with a set of
>> oscil-opcodes?
>> And if You would recommand adsynt, how could I get the desired partials?
>> I would be thankful for any hint!
>>
>> Here my list of partials:
>> iratio = 1.05555005944424078911 ; 15th root from 9/4
>> ifundamental = icps
>> ipartialB =icps*2.25
>> ipartialC = icps*iratio^24
>> ipartialD = icps*5.0625
>> ipartialE = icps*iratio^35
>> ipartialF = icps*iratio^40
>> ipartialG = icps*11.390625
>> ipartialH = icps*iratio^49
>> ipartialI = icps*iratio^53
>> ipartialK = icps*iratio^56;
>> ipartialL = icps*iratio^58 ;
>> ipartialM = icps*iratio^60
>> ipartialN = icps*iratio^62
>>
>>
>


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi,

It would have the same effect, but each method gives you different flexibility.

For adsynt, you would need to declare functions like this:

gifreq ftgen 1,0,16,  -2 , giratio^0, giratio^15, giratio^24...etc.

giamp ftgen 2, 0, 16, -2, giamp1, giamp2 ... etc.

You can also do it in the score:

f 1 0 16 -2 x y z d f f

Which may be good if you are editing the values in a spreadsheet.

Cheers,
Andrés

On Wed, Jul 21, 2010 at 10:26 AM, Stefan Thomas
 wrote:
> Dear community,
> what I forgot to mention, and which is not evident, all partials can be
> caltulated as exponentials of iratio:
> iratio = 1.05555005944424078911 ; 15te Wurzel aus 9/4
> ifundamental = iratio^0
> ipartialB =icps*iratio^15
> ipartialC = icps*iratio^24
> ipartialD = icps*iratio^30
> ipartialE = icps*iratio^35 ;
> ipartialF = icps*iratio^40;
> ipartialG = icps*iratio^45
> ipartialH = icps*iratio^49
> ipartialI = icps*iratio^53
> ipartialK = icps*iratio^56
> ipartialL = icps*iratio^58
> ipartialM = icps*iratio^60
> ipartialN = icps*iratio^62
>
>
> Does it make it maybee easier? What could be the andvantage of using the
> adsynt opcode?
>
> 2010/7/21 Rory Walsh 
>>
>> p.s. I'm pretty sure the recursive UDO idea will only work if you
>> don't need to alter the individual amps of the partials later on.
>>
>> On 21 July 2010 09:36, Rory Walsh  wrote:
>> > I read your subject and thought instantly of the answer 'thou shall
>> > not use absynth!", then I realised it's a typo. As for an answer I'm
>> > not really sure, either approach seems fine. My first thoughts were,
>> > recursive UDO with the frequency ratios stored in a table?
>> >
>> > Rory.
>> >
>> >
>> > On 21 July 2010 06:57, Stefan Thomas 
>> > wrote:
>> >> Dear community,
>> >> I have in mind a sound consisting of some unsual partials (quoted at
>> >> the end
>> >> of the mail).
>> >> My question is:
>> >> Would You recommand to synthesize this sound with adsynt or with a set
>> >> of
>> >> oscil-opcodes?
>> >> And if You would recommand adsynt, how could I get the desired
>> >> partials?
>> >> I would be thankful for any hint!
>> >>
>> >> Here my list of partials:
>> >> iratio = 1.05555005944424078911 ; 15th root from 9/4
>> >> ifundamental = icps
>> >> ipartialB =icps*2.25
>> >> ipartialC = icps*iratio^24
>> >> ipartialD = icps*5.0625
>> >> ipartialE = icps*iratio^35
>> >> ipartialF = icps*iratio^40
>> >> ipartialG = icps*11.390625
>> >> ipartialH = icps*iratio^49
>> >> ipartialI = icps*iratio^53
>> >> ipartialK = icps*iratio^56;
>> >> ipartialL = icps*iratio^58 ;
>> >> ipartialM = icps*iratio^60
>> >> ipartialN = icps*iratio^62
>> >>
>> >>
>> >
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>



-- 


Andrés


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

one advantage of NOT using adsynt, but having N independent  
oscillators: then you can have an own envelope for each partial. this  
is what happens in nature (see for instance the plots of an alto  
saxophone tone in curtis roads' computer music tutorial page 315), and  
you can re-create this behaviour rather easily by having different  
oscillators with different envelopes.

	joachim


Am 21.07.2010 um 11:26 schrieb Stefan Thomas:

> Dear community,
> what I forgot to mention, and which is not evident, all partials can  
> be caltulated as exponentials of iratio:
> iratio = 1.05555005944424078911 ; 15te Wurzel aus 9/4
> ifundamental = iratio^0
> ipartialB =icps*iratio^15
> ipartialC = icps*iratio^24
> ipartialD = icps*iratio^30
> ipartialE = icps*iratio^35 ;
> ipartialF = icps*iratio^40;
> ipartialG = icps*iratio^45
> ipartialH = icps*iratio^49
> ipartialI = icps*iratio^53
> ipartialK = icps*iratio^56
> ipartialL = icps*iratio^58
> ipartialM = icps*iratio^60
> ipartialN = icps*iratio^62
>
>
> Does it make it maybee easier? What could be the andvantage of using  
> the adsynt opcode?
>
> 2010/7/21 Rory Walsh 
> p.s. I'm pretty sure the recursive UDO idea will only work if you
> don't need to alter the individual amps of the partials later on.
>
> On 21 July 2010 09:36, Rory Walsh  wrote:
> > I read your subject and thought instantly of the answer 'thou shall
> > not use absynth!", then I realised it's a typo. As for an answer I'm
> > not really sure, either approach seems fine. My first thoughts were,
> > recursive UDO with the frequency ratios stored in a table?
> >
> > Rory.
> >
> >
> > On 21 July 2010 06:57, Stefan Thomas  > wrote:
> >> Dear community,
> >> I have in mind a sound consisting of some unsual partials (quoted  
> at the end
> >> of the mail).
> >> My question is:
> >> Would You recommand to synthesize this sound with adsynt or with  
> a set of
> >> oscil-opcodes?
> >> And if You would recommand adsynt, how could I get the desired  
> partials?
> >> I would be thankful for any hint!
> >>
> >> Here my list of partials:
> >> iratio = 1.05555005944424078911 ; 15th root from 9/4
> >> ifundamental = icps
> >> ipartialB =icps*2.25
> >> ipartialC = icps*iratio^24
> >> ipartialD = icps*5.0625
> >> ipartialE = icps*iratio^35
> >> ipartialF = icps*iratio^40
> >> ipartialG = icps*11.390625
> >> ipartialH = icps*iratio^49
> >> ipartialI = icps*iratio^53
> >> ipartialK = icps*iratio^56;
> >> ipartialL = icps*iratio^58 ;
> >> ipartialM = icps*iratio^60
> >> ipartialN = icps*iratio^62
> >>
> >>
> >
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi, 
I’m a newbie so if my question is stupid… excuse me !

In the case of the additive synthesis, i would like to know if it is possible to use the opcode adsyn (on the place of adsynt) without use a file produced by the Hetro opcode (.het). So, it would be possible to attribute a precise envelope and evolutions of frequency to every partial in a rather practical way. It would be enough to edit a file text then “to translate” it with het_import and use it for adsyn.

If this way is possible, i would just like to know until how much about partial can one go, because the help is not very clear on this point.

If somebody had an answer, it would be great !!

Julia




Le 21 juil. 2010 à 12:34, Andres Cabrera a écrit :

> Hi,
> 
> It would have the same effect, but each method gives you different flexibility.
> 
> For adsynt, you would need to declare functions like this:
> 
> gifreq ftgen 1,0,16,  -2 , giratio^0, giratio^15, giratio^24...etc.
> 
> giamp ftgen 2, 0, 16, -2, giamp1, giamp2 ... etc.
> 
> You can also do it in the score:
> 
> f 1 0 16 -2 x y z d f f
> 
> Which may be good if you are editing the values in a spreadsheet.
> 
> Cheers,
> Andrés
> 
> On Wed, Jul 21, 2010 at 10:26 AM, Stefan Thomas
>  wrote:
>> Dear community,
>> what I forgot to mention, and which is not evident, all partials can be
>> caltulated as exponentials of iratio:
>> iratio = 1.05555005944424078911 ; 15te Wurzel aus 9/4
>> ifundamental = iratio^0
>> ipartialB =icps*iratio^15
>> ipartialC = icps*iratio^24
>> ipartialD = icps*iratio^30
>> ipartialE = icps*iratio^35 ;
>> ipartialF = icps*iratio^40;
>> ipartialG = icps*iratio^45
>> ipartialH = icps*iratio^49
>> ipartialI = icps*iratio^53
>> ipartialK = icps*iratio^56
>> ipartialL = icps*iratio^58
>> ipartialM = icps*iratio^60
>> ipartialN = icps*iratio^62
>> 
>> 
>> Does it make it maybee easier? What could be the andvantage of using the
>> adsynt opcode?
>> 
>> 2010/7/21 Rory Walsh 
>>> 
>>> p.s. I'm pretty sure the recursive UDO idea will only work if you
>>> don't need to alter the individual amps of the partials later on.
>>> 
>>> On 21 July 2010 09:36, Rory Walsh  wrote:
>>>> I read your subject and thought instantly of the answer 'thou shall
>>>> not use absynth!", then I realised it's a typo. As for an answer I'm
>>>> not really sure, either approach seems fine. My first thoughts were,
>>>> recursive UDO with the frequency ratios stored in a table?
>>>> 
>>>> Rory.
>>>> 
>>>> 
>>>> On 21 July 2010 06:57, Stefan Thomas 
>>>> wrote:
>>>>> Dear community,
>>>>> I have in mind a sound consisting of some unsual partials (quoted at
>>>>> the end
>>>>> of the mail).
>>>>> My question is:
>>>>> Would You recommand to synthesize this sound with adsynt or with a set
>>>>> of
>>>>> oscil-opcodes?
>>>>> And if You would recommand adsynt, how could I get the desired
>>>>> partials?
>>>>> I would be thankful for any hint!
>>>>> 
>>>>> Here my list of partials:
>>>>> iratio = 1.05555005944424078911 ; 15th root from 9/4
>>>>> ifundamental = icps
>>>>> ipartialB =icps*2.25
>>>>> ipartialC = icps*iratio^24
>>>>> ipartialD = icps*5.0625
>>>>> ipartialE = icps*iratio^35
>>>>> ipartialF = icps*iratio^40
>>>>> ipartialG = icps*11.390625
>>>>> ipartialH = icps*iratio^49
>>>>> ipartialI = icps*iratio^53
>>>>> ipartialK = icps*iratio^56;
>>>>> ipartialL = icps*iratio^58 ;
>>>>> ipartialM = icps*iratio^60
>>>>> ipartialN = icps*iratio^62
>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> Send bugs reports to the Sourceforge bug tracker
>>>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>>> csound"
>>> 
>> 
>> 
> 
> 
> 
> -- 
> 
> 
> Andrés
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
> 



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Julia,

no, it's not a stupid question. The documentation is confusing.
I'm not sure what you mean about 'how much about a partial', but your  
het file can be as long as you'd like. Each partial can have as many  
breakpoints as you need and
last however long you want. For instance, a simple example with two  
partials

2,
-1,0,16000,10000,1,20000,10000,30000,10000
-2,0,440,10000,500,20000,4500,30000,700
-1,0,10000,10000,1,20000,16000,30000,200000
-2,0,500,10000,1000,20000,600,30000, 1000



On 23 Jul 2010, at 23:42, Julia Blondeau wrote:

> Hi,
> I’m a newbie so if my question is stupid… excuse me !
>
> In the case of the additive synthesis, i would like to know if it is  
> possible to use the opcode adsyn (on the place of adsynt) without  
> use a file produced by the Hetro opcode (.het). So, it would be  
> possible to attribute a precise envelope and evolutions of frequency  
> to every partial in a rather practical way. It would be enough to  
> edit a file text then “to translate” it with het_import and use it  
> for adsyn.
>
> If this way is possible, i would just like to know until how much  
> about partial can one go, because the help is not very clear on this  
> point.
>
> If somebody had an answer, it would be great !!
>
> Julia
>
>
>
>
> Le 21 juil. 2010 à 12:34, Andres Cabrera a écrit :
>
>> Hi,
>>
>> It would have the same effect, but each method gives you different  
>> flexibility.
>>
>> For adsynt, you would need to declare functions like this:
>>
>> gifreq ftgen 1,0,16,  -2 , giratio^0, giratio^15, giratio^24...etc.
>>
>> giamp ftgen 2, 0, 16, -2, giamp1, giamp2 ... etc.
>>
>> You can also do it in the score:
>>
>> f 1 0 16 -2 x y z d f f
>>
>> Which may be good if you are editing the values in a spreadsheet.
>>
>> Cheers,
>> Andrés
>>
>> On Wed, Jul 21, 2010 at 10:26 AM, Stefan Thomas
>>  wrote:
>>> Dear community,
>>> what I forgot to mention, and which is not evident, all partials  
>>> can be
>>> caltulated as exponentials of iratio:
>>> iratio = 1.05555005944424078911 ; 15te Wurzel aus 9/4
>>> ifundamental = iratio^0
>>> ipartialB =icps*iratio^15
>>> ipartialC = icps*iratio^24
>>> ipartialD = icps*iratio^30
>>> ipartialE = icps*iratio^35 ;
>>> ipartialF = icps*iratio^40;
>>> ipartialG = icps*iratio^45
>>> ipartialH = icps*iratio^49
>>> ipartialI = icps*iratio^53
>>> ipartialK = icps*iratio^56
>>> ipartialL = icps*iratio^58
>>> ipartialM = icps*iratio^60
>>> ipartialN = icps*iratio^62
>>>
>>>
>>> Does it make it maybee easier? What could be the andvantage of  
>>> using the
>>> adsynt opcode?
>>>
>>> 2010/7/21 Rory Walsh 
>>>>
>>>> p.s. I'm pretty sure the recursive UDO idea will only work if you
>>>> don't need to alter the individual amps of the partials later on.
>>>>
>>>> On 21 July 2010 09:36, Rory Walsh  wrote:
>>>>> I read your subject and thought instantly of the answer 'thou  
>>>>> shall
>>>>> not use absynth!", then I realised it's a typo. As for an answer  
>>>>> I'm
>>>>> not really sure, either approach seems fine. My first thoughts  
>>>>> were,
>>>>> recursive UDO with the frequency ratios stored in a table?
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>> On 21 July 2010 06:57, Stefan Thomas >>>> >
>>>>> wrote:
>>>>>> Dear community,
>>>>>> I have in mind a sound consisting of some unsual partials  
>>>>>> (quoted at
>>>>>> the end
>>>>>> of the mail).
>>>>>> My question is:
>>>>>> Would You recommand to synthesize this sound with adsynt or  
>>>>>> with a set
>>>>>> of
>>>>>> oscil-opcodes?
>>>>>> And if You would recommand adsynt, how could I get the desired
>>>>>> partials?
>>>>>> I would be thankful for any hint!
>>>>>>
>>>>>> Here my list of partials:
>>>>>> iratio = 1.05555005944424078911 ; 15th root from 9/4
>>>>>> ifundamental = icps
>>>>>> ipartialB =icps*2.25
>>>>>> ipartialC = icps*iratio^24
>>>>>> ipartialD = icps*5.0625
>>>>>> ipartialE = icps*iratio^35
>>>>>> ipartialF = icps*iratio^40
>>>>>> ipartialG = icps*11.390625
>>>>>> ipartialH = icps*iratio^49
>>>>>> ipartialI = icps*iratio^53
>>>>>> ipartialK = icps*iratio^56;
>>>>>> ipartialL = icps*iratio^58 ;
>>>>>> ipartialM = icps*iratio^60
>>>>>> ipartialN = icps*iratio^62
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>>> "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>
>>
>>
>> -- 
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Julia,

no, it's not a stupid question. The documentation is confusing.
I'm not sure what you mean about 'how much about a partial', but your  
het file can be as long as you'd like. Each partial can have as many  
breakpoints as you need and
last however long you want. For instance, a simple example with two  
partials

2,
-1,0,16000,10000,1,20000,10000,30000,10000
-2,0,440,10000,500,20000,450,30000,700
-1,0,10000,10000,1,20000,16000,30000,200000
-2,0,500,10000,1000,20000,600,30000, 1000


This can be imported with het_import and then run with adsyn.

Victor


On 23 Jul 2010, at 23:42, Julia Blondeau wrote:

> Hi,
> I’m a newbie so if my question is stupid… excuse me !
>
> In the case of the additive synthesis, i would like to know if it is  
> possible to use the opcode adsyn (on the place of adsynt) without  
> use a file produced by the Hetro opcode (.het). So, it would be  
> possible to attribute a precise envelope and evolutions of frequency  
> to every partial in a rather practical way. It would be enough to  
> edit a file text then “to translate” it with het_import and use it  
> for adsyn.
>
> If this way is possible, i would just like to know until how much  
> about partial can one go, because the help is not very clear on this  
> point.
>
> If somebody had an answer, it would be great !!
>
> Julia
>
>
>
>
> Le 21 juil. 2010 à 12:34, Andres Cabrera a écrit :
>
>> Hi,
>>
>> It would have the same effect, but each method gives you different  
>> flexibility.
>>
>> For adsynt, you would need to declare functions like this:
>>
>> gifreq ftgen 1,0,16,  -2 , giratio^0, giratio^15, giratio^24...etc.
>>
>> giamp ftgen 2, 0, 16, -2, giamp1, giamp2 ... etc.
>>
>> You can also do it in the score:
>>
>> f 1 0 16 -2 x y z d f f
>>
>> Which may be good if you are editing the values in a spreadsheet.
>>
>> Cheers,
>> Andrés
>>
>> On Wed, Jul 21, 2010 at 10:26 AM, Stefan Thomas
>>  wrote:
>>> Dear community,
>>> what I forgot to mention, and which is not evident, all partials  
>>> can be
>>> caltulated as exponentials of iratio:
>>> iratio = 1.05555005944424078911 ; 15te Wurzel aus 9/4
>>> ifundamental = iratio^0
>>> ipartialB =icps*iratio^15
>>> ipartialC = icps*iratio^24
>>> ipartialD = icps*iratio^30
>>> ipartialE = icps*iratio^35 ;
>>> ipartialF = icps*iratio^40;
>>> ipartialG = icps*iratio^45
>>> ipartialH = icps*iratio^49
>>> ipartialI = icps*iratio^53
>>> ipartialK = icps*iratio^56
>>> ipartialL = icps*iratio^58
>>> ipartialM = icps*iratio^60
>>> ipartialN = icps*iratio^62
>>>
>>>
>>> Does it make it maybee easier? What could be the andvantage of  
>>> using the
>>> adsynt opcode?
>>>
>>> 2010/7/21 Rory Walsh 
>>>>
>>>> p.s. I'm pretty sure the recursive UDO idea will only work if you
>>>> don't need to alter the individual amps of the partials later on.
>>>>
>>>> On 21 July 2010 09:36, Rory Walsh  wrote:
>>>>> I read your subject and thought instantly of the answer 'thou  
>>>>> shall
>>>>> not use absynth!", then I realised it's a typo. As for an answer  
>>>>> I'm
>>>>> not really sure, either approach seems fine. My first thoughts  
>>>>> were,
>>>>> recursive UDO with the frequency ratios stored in a table?
>>>>>
>>>>> Rory.
>>>>>
>>>>>
>>>>> On 21 July 2010 06:57, Stefan Thomas >>>> >
>>>>> wrote:
>>>>>> Dear community,
>>>>>> I have in mind a sound consisting of some unsual partials  
>>>>>> (quoted at
>>>>>> the end
>>>>>> of the mail).
>>>>>> My question is:
>>>>>> Would You recommand to synthesize this sound with adsynt or  
>>>>>> with a set
>>>>>> of
>>>>>> oscil-opcodes?
>>>>>> And if You would recommand adsynt, how could I get the desired
>>>>>> partials?
>>>>>> I would be thankful for any hint!
>>>>>>
>>>>>> Here my list of partials:
>>>>>> iratio = 1.05555005944424078911 ; 15th root from 9/4
>>>>>> ifundamental = icps
>>>>>> ipartialB =icps*2.25
>>>>>> ipartialC = icps*iratio^24
>>>>>> ipartialD = icps*5.0625
>>>>>> ipartialE = icps*iratio^35
>>>>>> ipartialF = icps*iratio^40
>>>>>> ipartialG = icps*11.390625
>>>>>> ipartialH = icps*iratio^49
>>>>>> ipartialI = icps*iratio^53
>>>>>> ipartialK = icps*iratio^56;
>>>>>> ipartialL = icps*iratio^58 ;
>>>>>> ipartialM = icps*iratio^60
>>>>>> ipartialN = icps*iratio^62
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>          https://sourceforge.net/tracker/? 
>>>> group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>>> "unsubscribe
>>>> csound"
>>>>
>>>
>>>
>>
>>
>>
>> -- 
>>
>>
>> Andrés
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

True, but I found using the python interface to Loris more powerful.

MKG from cell phone

On Jul 23, 2010 7:35 PM, "Victor Lazzarini" <Victor.Lazzarini@nuim.ie> wrote:

Julia,

no, it's not a stupid question. The documentation is confusing.
I'm not sure what you mean a...

-2,0,440,10000,500,20000,450,30000,700

-1,0,10000,10000,1,20000,16000,30000,200000
-2,0,500,10000,1000,20000,600,30000, 1000

This can be imported with het_import and then run with adsyn.

Victor

On 23 Jul 2010, at 23:42, Julia Blondeau wrote:

> Hi,
> I’m a newbie so if my question is stupid… excuse me !
>
> In the case of the additive synthe...

On 24/07/2010 00:36, Victor Lazzarini wrote:
> Julia,
>
> no, it's not a stupid question. The documentation is confusing.
> I'm not sure what you mean about 'how much about a partial', but your
> het file can be as long as you'd like. Each partial can have as many
> breakpoints as you need and
> last however long you want.


I'm somewhat out of touch with things hetro and adsyn - has the code 
been modernised? It (hetro file format, such as it is) was always based 
on (signed) 16bit values representing time points in msecs, so that the 
longest available duration was 32.767 seconds.


Richard Dobson



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I think you're right, this probably is still the case.

Victor
On 24 Jul 2010, at 08:18, Richard Dobson wrote:

> On 24/07/2010 00:36, Victor Lazzarini wrote:
>> Julia,
>>
>> no, it's not a stupid question. The documentation is confusing.
>> I'm not sure what you mean about 'how much about a partial', but your
>> het file can be as long as you'd like. Each partial can have as many
>> breakpoints as you need and
>> last however long you want.
>
>
> I'm somewhat out of touch with things hetro and adsyn - has the code  
> been modernised? It (hetro file format, such as it is) was always  
> based on (signed) 16bit values representing time points in msecs, so  
> that the longest available duration was 32.767 seconds.
>
>
> Richard Dobson
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Hi Stefan,

as far as i know the Loris opcodes of Csound do not work at the moment. 
The last version of Loris i can get to build together with Csound is version
1.5.2. And even then,  using an example with lorisplay and lorisread
produces no errors but there is simply no sound generated.

Did someone get it to work yet - and how - or can i file it as a bug for
later reference?

Menno

Please file it as a bug. We might need to ask Kelly Fitz for some help.

Victor
On 27 Jul 2010, at 19:49, menno wrote:

>
> Hi Stefan,
>
> as far as i know the Loris opcodes of Csound do not work at the  
> moment.
> The last version of Loris i can get to build together with Csound is  
> version
> 1.5.2. And even then,  using an example with lorisplay and lorisread
> produces no errors but there is simply no sound generated.
>
> Did someone get it to work yet - and how - or can i file it as a bug  
> for
> later reference?
>
> Menno
> -- 
> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Now that we are at it. Shall I fill a bug report for ATS opcodes too?  
They work find in cosund double but in the float the output is rather  
glitchy unless ksmp is 1.

Thanks

P


On 27 Jul 2010, at 20:07, Victor Lazzarini wrote:

> Please file it as a bug. We might need to ask Kelly Fitz for some  
> help.
>
> Victor
> On 27 Jul 2010, at 19:49, menno wrote:
>
>>
>> Hi Stefan,
>>
>> as far as i know the Loris opcodes of Csound do not work at the  
>> moment.
>> The last version of Loris i can get to build together with Csound  
>> is version
>> 1.5.2. And even then,  using an example with lorisplay and lorisread
>> produces no errors but there is simply no sound generated.
>>
>> Did someone get it to work yet - and how - or can i file it as a  
>> bug for
>> later reference?
>>
>> Menno
>> -- 
>> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Yes, with a CSD example, please!
On 27 Jul 2010, at 20:07, Peiman Khosravi wrote:

> Now that we are at it. Shall I fill a bug report for ATS opcodes  
> too? They work find in cosund double but in the float the output is  
> rather glitchy unless ksmp is 1.
>
> Thanks
>
> P
>
>
> On 27 Jul 2010, at 20:07, Victor Lazzarini wrote:
>
>> Please file it as a bug. We might need to ask Kelly Fitz for some  
>> help.
>>
>> Victor
>> On 27 Jul 2010, at 19:49, menno wrote:
>>
>>>
>>> Hi Stefan,
>>>
>>> as far as i know the Loris opcodes of Csound do not work at the  
>>> moment.
>>> The last version of Loris i can get to build together with Csound  
>>> is version
>>> 1.5.2. And even then,  using an example with lorisplay and lorisread
>>> produces no errors but there is simply no sound generated.
>>>
>>> Did someone get it to work yet - and how - or can i file it as a  
>>> bug for
>>> later reference?
>>>
>>> Menno
>>> -- 
>>> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I've written to Kelly Fitz to see if he can help us.

Victor
On 27 Jul 2010, at 20:07, Victor Lazzarini wrote:

> Please file it as a bug. We might need to ask Kelly Fitz for some  
> help.
>
> Victor
> On 27 Jul 2010, at 19:49, menno wrote:
>
>>
>> Hi Stefan,
>>
>> as far as i know the Loris opcodes of Csound do not work at the  
>> moment.
>> The last version of Loris i can get to build together with Csound  
>> is version
>> 1.5.2. And even then,  using an example with lorisplay and lorisread
>> produces no errors but there is simply no sound generated.
>>
>> Did someone get it to work yet - and how - or can i file it as a  
>> bug for
>> later reference?
>>
>> Menno
>> -- 
>> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
>> Sent from the Csound - General mailing list archive at Nabble.com.
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

allright, i will file the Loris problem as a bug.

Also i confirm that the ATS opcodes are working okay in Csound double and
Ubuntu.
In Windows there is a problem when analyzing with one or two filter settings
of ATSA.
ATSA errors - ID: 2993171

Menno

Sure I will do that on Monday as I'm going away tomorrow morning.

Best,

Peiman

On 27 Jul 2010, at 20:15, Victor Lazzarini wrote:

> Yes, with a CSD example, please!
> On 27 Jul 2010, at 20:07, Peiman Khosravi wrote:
>
>> Now that we are at it. Shall I fill a bug report for ATS opcodes  
>> too? They work find in cosund double but in the float the output is  
>> rather glitchy unless ksmp is 1.
>>
>> Thanks
>>
>> P
>>
>>
>> On 27 Jul 2010, at 20:07, Victor Lazzarini wrote:
>>
>>> Please file it as a bug. We might need to ask Kelly Fitz for some  
>>> help.
>>>
>>> Victor
>>> On 27 Jul 2010, at 19:49, menno wrote:
>>>
>>>>
>>>> Hi Stefan,
>>>>
>>>> as far as i know the Loris opcodes of Csound do not work at the  
>>>> moment.
>>>> The last version of Loris i can get to build together with Csound  
>>>> is version
>>>> 1.5.2. And even then,  using an example with lorisplay and  
>>>> lorisread
>>>> produces no errors but there is simply no sound generated.
>>>>
>>>> Did someone get it to work yet - and how - or can i file it as a  
>>>> bug for
>>>> later reference?
>>>>
>>>> Menno
>>>> -- 
>>>> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>>> "unsubscribe csound"
>>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Menno,

Later versions of Loris include the opcodes so you don't need to build  
them separately anymore (they seem to be out-of-date anyway). All you  
need to do is to build Loris with csound support, which is enabled by  
letting configure find the csound headers (eg: add CPPFLAGS=-I), which is much simpler. Then run the csound examples  
using --opcode-lib= and they should be OK. There is  
a problem with lorismorph, but lorisplay & lorisread are working.

Kelly Fitz said that these opcodes are NOT for realtime (although you  
can play csound directly to dac using them), so forget trying to MIDI  
them up.

Regards

Victor
On 27 Jul 2010, at 19:49, menno wrote:

>
> Hi Stefan,
>
> as far as i know the Loris opcodes of Csound do not work at the  
> moment.
> The last version of Loris i can get to build together with Csound is  
> version
> 1.5.2. And even then,  using an example with lorisplay and lorisread
> produces no errors but there is simply no sound generated.
>
> Did someone get it to work yet - and how - or can i file it as a bug  
> for
> later reference?
>
> Menno
> -- 
> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Actually the problem was different. ATSsinnoi does not output the  
noise component correctly (although ATSaddnz does with the same file).  
This is in both float and double versions.

I've filed a bug report.

P

On 27 Jul 2010, at 20:15, Victor Lazzarini wrote:

> Yes, with a CSD example, please!
> On 27 Jul 2010, at 20:07, Peiman Khosravi wrote:
>
>> Now that we are at it. Shall I fill a bug report for ATS opcodes  
>> too? They work find in cosund double but in the float the output is  
>> rather glitchy unless ksmp is 1.
>>
>> Thanks
>>
>> P
>>
>>
>> On 27 Jul 2010, at 20:07, Victor Lazzarini wrote:
>>
>>> Please file it as a bug. We might need to ask Kelly Fitz for some  
>>> help.
>>>
>>> Victor
>>> On 27 Jul 2010, at 19:49, menno wrote:
>>>
>>>>
>>>> Hi Stefan,
>>>>
>>>> as far as i know the Loris opcodes of Csound do not work at the  
>>>> moment.
>>>> The last version of Loris i can get to build together with Csound  
>>>> is version
>>>> 1.5.2. And even then,  using an example with lorisplay and  
>>>> lorisread
>>>> produces no errors but there is simply no sound generated.
>>>>
>>>> Did someone get it to work yet - and how - or can i file it as a  
>>>> bug for
>>>> later reference?
>>>>
>>>> Menno
>>>> -- 
>>>> View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>
>>>>
>>>> Send bugs reports to the Sourceforge bug tracker
>>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>>> Discussions of bugs and features can be posted here
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>>> "unsubscribe csound"
>>>>
>>>
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>         https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>>> "unsubscribe csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>          https://sourceforge.net/tracker/?group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
>> "unsubscribe csound"
>>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>           https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Thank you for the energy you've put in Victor.
I downloaded and build Loris1.7 and it found the Csound headers. There was a report from Loris while building doing 14 tests and it all passed them. 
I did a quick test with csound and loris; it was not succesfull yet but i will do some serious tests during the week to come and report back about my findings.
bye,
Menno

--- On Wed, 7/28/10, Victor Lazzarini  wrote:

> From: Victor Lazzarini 
> Subject: [Csnd] Loris (was Re: Re: Re: Re: Re: Re: Re: Re: shall I use absynth)
> To: csound@lists.bath.ac.uk
> Date: Wednesday, July 28, 2010, 2:19 PM
> Menno,
> 
> Later versions of Loris include the opcodes so you don't
> need to build them separately anymore (they seem to be
> out-of-date anyway). All you need to do is to build Loris
> with csound support, which is enabled by letting configure
> find the csound headers (eg: add CPPFLAGS=-I csound headers>), which is much simpler. Then run the
> csound examples using --opcode-lib=
> and they should be OK. There is a problem with lorismorph,
> but lorisplay & lorisread are working.
> 
> Kelly Fitz said that these opcodes are NOT for realtime
> (although you can play csound directly to dac using them),
> so forget trying to MIDI them up.
> 
> Regards
> 
> Victor
> On 27 Jul 2010, at 19:49, menno wrote:
> 
> > 
> > Hi Stefan,
> > 
> > as far as i know the Loris opcodes of Csound do not
> work at the moment.
> > The last version of Loris i can get to build together
> with Csound is version
> > 1.5.2. And even then,  using an example with
> lorisplay and lorisread
> > produces no errors but there is simply no sound
> generated.
> > 
> > Did someone get it to work yet - and how - or can i
> file it as a bug for
> > later reference?
> > 
> > Menno
> > --View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
> > Sent from the Csound - General mailing list archive at
> Nabble.com.
> > 
> > 
> > Send bugs reports to the Sourceforge bug tracker
> >            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> > Discussions of bugs and features can be posted here
> > To unsubscribe, send email sympa@lists.bath.ac.uk
> with body "unsubscribe csound"
> > 
> 
> 
> 
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk
> with body "unsubscribe csound"
> 
> 






Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Both lorisread and lorisplay work here (Loris 1.7 & OSX). Please  
report any findings to the Loris developers too (Kelly Fitz), as we  
cannot do anything about them.

Victor
On 29 Jul 2010, at 18:51, menno wrote:

> Thank you for the energy you've put in Victor.
> I downloaded and build Loris1.7 and it found the Csound headers.  
> There was a report from Loris while building doing 14 tests and it  
> all passed them.
> I did a quick test with csound and loris; it was not succesfull yet  
> but i will do some serious tests during the week to come and report  
> back about my findings.
> bye,
> Menno
>
> --- On Wed, 7/28/10, Victor Lazzarini   
> wrote:
>
>> From: Victor Lazzarini 
>> Subject: [Csnd] Loris (was Re: Re: Re: Re: Re: Re: Re: Re: shall I  
>> use absynth)
>> To: csound@lists.bath.ac.uk
>> Date: Wednesday, July 28, 2010, 2:19 PM
>> Menno,
>>
>> Later versions of Loris include the opcodes so you don't
>> need to build them separately anymore (they seem to be
>> out-of-date anyway). All you need to do is to build Loris
>> with csound support, which is enabled by letting configure
>> find the csound headers (eg: add CPPFLAGS=-I> csound headers>), which is much simpler. Then run the
>> csound examples using --opcode-lib=
>> and they should be OK. There is a problem with lorismorph,
>> but lorisplay & lorisread are working.
>>
>> Kelly Fitz said that these opcodes are NOT for realtime
>> (although you can play csound directly to dac using them),
>> so forget trying to MIDI them up.
>>
>> Regards
>>
>> Victor
>> On 27 Jul 2010, at 19:49, menno wrote:
>>
>>>
>>> Hi Stefan,
>>>
>>> as far as i know the Loris opcodes of Csound do not
>> work at the moment.
>>> The last version of Loris i can get to build together
>> with Csound is version
>>> 1.5.2. And even then,  using an example with
>> lorisplay and lorisread
>>> produces no errors but there is simply no sound
>> generated.
>>>
>>> Did someone get it to work yet - and how - or can i
>> file it as a bug for
>>> later reference?
>>>
>>> Menno
>>> --View this message in context: http://csound.1045644.n5.nabble.com/shall-I-use-absynth-tp1676290p2256192.html
>>> Sent from the Csound - General mailing list archive at
>> Nabble.com.
>>>
>>>
>>> Send bugs reports to the Sourceforge bug tracker
>>>             https://sourceforge.net/tracker/?group_id=81968&atid=564599
>>> Discussions of bugs and features can be posted here
>>> To unsubscribe, send email sympa@lists.bath.ac.uk
>> with body "unsubscribe csound"
>>>
>>
>>
>>
>> Send bugs reports to the Sourceforge bug tracker
>>            https://sourceforge.net/tracker/? 
>> group_id=81968&atid=564599
>> Discussions of bugs and features can be posted here
>> To unsubscribe, send email sympa@lists.bath.ac.uk
>> with body "unsubscribe csound"
>>
>>
>
>
>
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body  
> "unsubscribe csound"
>



Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"