I get no problem here (Linux x64, Csound 5.10 floats beta).

There was a problem many years ago with a mismatch between the code and 
the hetro file format (which remains very primitive and non-portable), 
and which (IIRC) gave some problems with old het files, but nothing more 
recently.

Richard Dobson




Aaron Johnson wrote:
> From: jpff >
> To: csound@lists.bath.ac.uk 
> Date: Tue, 22 Sep 2009 18:27:38 +0100
>  >>>>> "Aaron" == Aaron Johnson  > writes:
> 
>  Aaron> I saw elsewhere that 5.08 had a problem with noise when using 
> hetro and
>  Aaron> adsyn. I can confirm that I'm getting unlistenable results here, 
> too.
> 
>  Aaron> Can any of the developers confirm that this is fixed in 5.10, or 
> will be
>  Aaron> fixed in the next version?
> 
> I cannot confirm this.  I have no record of a complaint and/or example
> of any problem.
> 
> ==John ffitch
> 
> Hi John,
> 
> Try the manual 'adsyn' example...I did so with several different file 
> '.het' files, and I got a very 'dirty' , noisy distorted result. 
> Attached is a sample problematic .csd and an accompanying .het file. All 
> I get from the result is an extremely harsh output file.
> 



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Also, isn't the het file format dependent on byte order or float/double?

On 9/23/09, Richard Dobson  wrote:
> I get no problem here (Linux x64, Csound 5.10 floats beta).
>
> There was a problem many years ago with a mismatch between the code and
> the hetro file format (which remains very primitive and non-portable),
> and which (IIRC) gave some problems with old het files, but nothing more
> recently.
>
> Richard Dobson
>
>
>
>
> Aaron Johnson wrote:
>> From: jpff >
>> To: csound@lists.bath.ac.uk 
>> Date: Tue, 22 Sep 2009 18:27:38 +0100
>>  >>>>> "Aaron" == Aaron Johnson > > writes:
>>
>>  Aaron> I saw elsewhere that 5.08 had a problem with noise when using
>> hetro and
>>  Aaron> adsyn. I can confirm that I'm getting unlistenable results here,
>> too.
>>
>>  Aaron> Can any of the developers confirm that this is fixed in 5.10, or
>> will be
>>  Aaron> fixed in the next version?
>>
>> I cannot confirm this.  I have no record of a complaint and/or example
>> of any problem.
>>
>> ==John ffitch
>>
>> Hi John,
>>
>> Try the manual 'adsyn' example...I did so with several different file
>> '.het' files, and I got a very 'dirty' , noisy distorted result.
>> Attached is a sample problematic .csd and an accompanying .het file. All
>> I get from the result is an extremely harsh output file.
>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>

Steven Yi wrote:
> Also, isn't the het file format dependent on byte order or float/double?
> 
>

Byte order certainly; and unless it has been changed (there were 
proposals...), based on 16bit shorts for ms timestamps, so a maximum 
duration of 32.767 seconds. Not much of a header!


Richard Dobson





Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

This sounds ridiculous even for the punched card era. Who devised
such senseless header?

Victor
----- Original Message ----- 
From: "Richard Dobson" 
To: 
Sent: Wednesday, September 23, 2009 5:50 PM
Subject: [Csnd] Re: Re: What's up with hetro/adsyn?


> Steven Yi wrote:
>> Also, isn't the het file format dependent on byte order or float/double?
>>
>
> Byte order certainly; and unless it has been changed (there were 
> proposals...), based on 16bit shorts for ms timestamps, so a maximum 
> duration of 32.767 seconds. Not much of a header!
>
>
> Richard Dobson
>
>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound" 



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

victor wrote:
> This sounds ridiculous even for the punched card era. Who devised
> such senseless header?
> 


I should perhaps have written full sentence - there is not much of a 
header. In fact, a single short giving the number of harmonics. 
thereafter, each track amp and freq (written sequentially) is demarcated 
by a single short. In essence, a set of integer binary breakpoint files. 
This has been in Csound since I first used it, back in the late 80s on 
the Atari ST. May have come all the way from Music11.

Optimized for storage on a floppy disk, and use on a computer with 4MB 
RAM and a 10MB hard disk, I guess. And in the original CDP Atari-based 
system we had a full graphic editor for adsyn data files. I imagine if I 
dusted off the ancient Atari Falcon from under the stairs, it would all 
still work.

Richard Dobson


> Victor
> ----- Original Message ----- From: "Richard Dobson" 
> 
> To: 
> Sent: Wednesday, September 23, 2009 5:50 PM
> Subject: [Csnd] Re: Re: What's up with hetro/adsyn?
> 
> 
>> Steven Yi wrote:
>>> Also, isn't the het file format dependent on byte order or float/double?
>>>
>>
>> Byte order certainly; and unless it has been changed (there were 
>> proposals...), based on 16bit shorts for ms timestamps, so a maximum 
>> duration of 32.767 seconds. Not much of a header!
>>



Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

Instead of monkeying with this antique, we should make sure that there
are better ways of doing the same thing in Csound.

And there are, are there not? It should simply be documented what to
use for newer pieces.

Regards,
Mike

On 9/23/09, Richard Dobson  wrote:
> victor wrote:
>> This sounds ridiculous even for the punched card era. Who devised
>> such senseless header?
>>
>
>
> I should perhaps have written full sentence - there is not much of a
> header. In fact, a single short giving the number of harmonics.
> thereafter, each track amp and freq (written sequentially) is demarcated
> by a single short. In essence, a set of integer binary breakpoint files.
> This has been in Csound since I first used it, back in the late 80s on
> the Atari ST. May have come all the way from Music11.
>
> Optimized for storage on a floppy disk, and use on a computer with 4MB
> RAM and a 10MB hard disk, I guess. And in the original CDP Atari-based
> system we had a full graphic editor for adsyn data files. I imagine if I
> dusted off the ancient Atari Falcon from under the stairs, it would all
> still work.
>
> Richard Dobson
>
>
>> Victor
>> ----- Original Message ----- From: "Richard Dobson"
>> 
>> To: 
>> Sent: Wednesday, September 23, 2009 5:50 PM
>> Subject: [Csnd] Re: Re: What's up with hetro/adsyn?
>>
>>
>>> Steven Yi wrote:
>>>> Also, isn't the het file format dependent on byte order or float/double?
>>>>
>>>
>>> Byte order certainly; and unless it has been changed (there were
>>> proposals...), based on 16bit shorts for ms timestamps, so a maximum
>>> duration of 32.767 seconds. Not much of a header!
>>>
>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>