It looks like there is a difference between the par file interpreter and the music controls within fractint. I see that yes, if you try to run a par file with all zeros, it does reset the values to the default (1/2/3/...). But according to your thought that Fractint interpreted zero as a one, wouldn't you expect it to show all ones instead of 1/2/3...? Nevertheless...while generating a par and playing with sound parameters entering all zeros stays as all zeros and is in fact written to a generated par file as all zeros. I am going to take a break and test what happens with just a few zeros entered in.................... I entered 1/-3/5/0/2/4/6/0/7/9/11/13 ( threw in two 0s, a -3 and a 13 to test for "illegal" values). For ease of comparison:

1   -3   5   0   2   4   6   0   7   9   11   13         values entered during generation via ctrl+f->F7

1    3   5   0    2   4   6   0   7   9   11   12         values shown after resuming generation and
                                                                            returning via ctrl+f->F7. These are also the same
                                                                            values saved in the par file via <b>.

1   3    5   4    2   4   6   8   7   9    11   12       values shown after saving the par and regenerating it
                                                                           then checking values in ctrl+f->F7

My conclusions:

when the developers (mostly Robin Bussell , Jonathan and Tim, if I recall) were working on the sound parameters, there was clearly a test for illegal values built into the sound module (<ctrl+f>). The sound module test considered the 13 and -3 to be illegal and the 0 to be legal. In the case of numbers >12 they reset to 12. Negative numbers are reset to their positive value. I know that in the fractint code many other numerical sequences start with 0 not 1. I am not a coder, so I don't know the details of why, but I got caught by that once somewhere else...maybe in screen coordinates, which start at 0,0 not 1,1. Not conclusive, but another hint, imo.

there is the question of why they didn't include a "Scale map B (0)" on the Scale Mapping Screen, when 0 is clearly an allowed value when entered via the ctrl+f method. That would have allowed for a completed octave B(x) to B(x+1). Even better would have been to shift the map so that C(x)=0 and C(x+1)=12.

when the par file is saved, the values accepted by the <ctrl+f> screen are the same as those saved in the par.

the parameter parser that is used to generate the image from the par considers the 0 to be illegal (an error IMO) and replaces it with the default value for that note - in the example above, D# is reset to 4 and G is reset to 8. I think that is an error, because the sound module clearly allows for a 0 value.

It would be nice to have the option to turn the note off completely - say, with a legal entry of "off"

As for your concerns about the negative hertz values...Robin wrote the code for the synth integration I am quite sure. I have no idea at all whether any negative hertz values are indeed passed on to the synthesizer. Low hz values are inaudible (especially to an old fart like me where <20hz = silence)). For all I know Robin coded in a zero value for any sub zero hz values to pass to the synth. I, for one, would absolutely hate not to be able to enter any value I wanted into the Hertz= parameter. How else to shift the overall pitch downward? Even WAY downward? Or upward? I suppose you could do that playing tricks with the screen resolution, but that is way too cumbersome and imprecise.

an aside - Back in the early days of the sound files (v.15 thru v.18 or so) there was a pronounced pause between the calculation of one pixel to the next. Sort of like fractint was taking a deep breath before spitting out the next series of notes on the next pixel. I liked that a lot, since it made for a natural pause which gave a great starting point for a new musical phrase.

Bill

On 5/8/2011 12:58 PM, Jay Litwyn wrote:

I mean when I run my parameters, with zeros, FracTint considers them to be invalid, so it replaces them with the defaults; 1/2/3...If it did *not* consider zeros to be invalid, and I am thinking that zero is a very reasonable reprezentation of resting, then I would not be forced to wonder what negative Hertz values mean. In my synthesizer, negative Hertz values *can* mean waves that start with a negative phase. I don't think OPL allows that.
----- Original Message -----

From: Bill Jemison

To: fractint@mailman.xmission.com

Sent: Sunday, May 08, 2011 12:32 PM

Subject: Re: [Fractint] A meaning for scalemap=0/0/0/0/0/0/0/0/0/0/0/0;silence.

not sure what you mean - if you run the Arcade_Variation2 and then go to the tone map screen you are seeing 1/2/3...? That is not at all what I see after multiple attempts. I see exactly what is in the par file 12/12/12/12/12/12/1/1/1/1/1/1. I suggest that you try it again.

Anyone else?

On 5/8/2011 12:54 AM, Jay Litwyn wrote:
If I load those parameters, then I end up with 1/2/3/...
----- Original Message -----

From: Bill Jemison

To: Fractint and General Fractals Discussion

Sent: Friday, May 06, 2011 2:10 PM

Subject: Re: [Fractint] A meaning for scalemap=0/0/0/0/0/0/0/0/0/0/0/0;silence.

Hi Jay,

Actually, what I think is happening is that it indeed does keep the note at 0, however, if you try to enter a number above 12, say a 15, it resets the value to 12. Making those changes (0s and 15s) to the <ctrl+F> F7 screen and then generating a bit and returning, you will find 0's and 12's. The reason I don't think it is internally resetting to 1 becomes painfully obvious if you enter all values of 12's and 1's as I did on this:

Arcade_Variation2   { ; This works nicely under DOSbox.
                     ; Fractint Version 2004 Patchlevel 10
                     ; tone map 1's and 12's
reset=2004 type=mandelcloud passes=1 center-mag=-0.5/0/0.6666667
params=-37 float=y maxiter=100 inside=0 periodicity=3 hertz=360
polyphony=9 wavetype=7 attack=1 decay=0 sustain=15
srelease=0 scalemap=12/12/12/12/12/12/1/1/1/1/1/1 orbitdelay=1500
showorbit=yes sound=x/fm/quant colors=@default.map
}

Bill

On 5/6/2011 1:20 AM, Jay Litwyn wrote:
Suibject-Was: Re: [Fractint] DOSBox and MusicFractals

Test               { ;  I was just thinking that scalemappings to zero 
could
                     ;  signify a rest. Even though I used this 
version of
                     ;  Fractint Version 2004 Patchlevel 4
                     ;  to write these parameters, when I load them, 
it is
                     ;  interpretting them as defaults one to twelve.
  reset=2004 type=latoocarfian
  function=sin/flip/cos/asin
  center-mag=-0.000684158/4.31882/0.7141089/1.3384/4\
  1.6505097310925407/3.76194921054549525
  params=2.71828182845905/2.71828182845905/2.7182818\
  2845905/2.71828182845905 float=y maxiter=4000
  inside=0 outside=atan cyclerange=1/1 hertz=331
  sound=x/pc/fm/quant polyphony=6 wavetype=7
  attack=0 decay=15 sustain=15 srelease=3
  scalemap=0/0/0/0/0/0/0/0/0/0/0/0
  orbitdelay=1000 showorbit=yes
  } 



_______________________________________________
Fractint mailing list
Fractint@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint
_______________________________________________
Fractint mailing list
Fractint@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint
_______________________________________________
Fractint mailing list
Fractint@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint
_______________________________________________
Fractint mailing list
Fractint@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint
_______________________________________________
Fractint mailing list
Fractint@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractint