- February 2019 (1)
- August 2017 (1)
- July 2017 (1)
- June 2017 (1)
- December 2016 (1)
- October 2016 (1)
- September 2016 (1)
- August 2016 (1)
- January 2016 (3)
- October 2015 (2)
- June 2015 (3)
- May 2015 (2)
- 1 of 4
- ››
This is a new version now, version 4.6, and it has quite a few new features, including a graphical way to set the silent and hidden measures for the Play then silent feature,a new count in option, work on the automatic rhythm changing, and several music notation related features along with many bug fixes and smaller changes . I've been working on it since January. To get it, visit the download page and you can install on top of your existing version. The Mac version isn't quite ready yet, just want to do some testing first before doing a new Mac build. Meanwhile, if you are very keen, visit the Bounce for Mac Beta download page it gives instructions on how to update your version of Bounce for Mac from the lastest Windows release. Or you can ask me for an early Mac beta. I hope to release the Mac build in the near future.
Including: New Visual Count In window Visual Count In (Ctrl + 289). This lets you show the bouncing balls bounce several times before the rhythm starts.
New graphical interface for the option to play and be silent at selected measures and to show / hide the bounce - you can set it to display the measures polymetrically when some of the measures are of different sizes - parts 1 and 2 have shorter measures than parts 3 and 4 in this screen shot. The yellow lines show where each pattern of play and silent measures repeats. White here is silence. You left click to set a measure to played or silent and right click to set the position of the yellow line for the pattern repeats. As before you can set it so the bounces are automatically hidden / shown whenever it plays or is silent. It's just a graphical user interface into the existing feature, but it does make it easier to use in some ways and you can also expand it to show the patterns of measures in all the parts for as many measures as you like - which may go on for a long time without repeating the whole thing exactly if each part repeats after a different number of measures, or some parts are polymetric..
Shows the new polychords feature in Bounce - sorry rather glitchy recording - and it's not an example of anything, just a sequence of chords I did while debugging, the sequence is C F C:F C F:C FM7:Dm7
You can now set it to highlight a region of the onscreen keyboard e.g. to show instrument range, or to show keyswitch regions.
Then ther'e a new feature "label by cycle of fifths". What it does is first find the closest to a fifth in the tuning, for instance, 31 steps in 53 equal. Then it starts from the F (as a "fifth" below the 1/1) and just goes around the cycle of fifths using that number of steps as the "fifth" to label all the scale steps in the tuning. So labels the note a fifth above that as C, next as G, D, A, E, B just as for twelve equal. In the other direction labels the flats. Then goes on to do the sharps and double flats, then the double sharps and triple flats, and so on until all the notes are labelled. Sometimes, e.g. in 72 equal, it gets back to the start without labeling all the notes because the notes form a smaller cycle - in this case a cycle of 12, so then it does those by adding +s or -s to the names it has found already. At the end of this every note will be labelled. But some tunings give quite surprising results when you do this.
In Pythagorean tunings and any tuning with the fifth sharper than in equal temperament, then the sharps are sharper than the flat of the note above, e.g. C# is sharper than Db so you get the notes labelled as C ... Db C# ... D. When you add in double sharps and double flats and so on that can make your head spin already. But in some of the more extreme temperaments, e.g. 13 equal, the same can happen to the note names too, e.g. in 13 equal, the B is sharper than the C because after you go around the cycle and get as far as the B, because your fifth is so sharp, then the B is raised enough in pitch to go above the original C. Similarly the E is above the F, in 13 equal.
Here is a screen shot for 31 equal, one of the more conventional arrangements of sharps and flats - the sharps are lower in pitch than the flats of the note above. This shows the positions of the double flats and double sharps as well. All this is worked out automatically by following around the cycle of fifths, using a "fifth"of 18 steps which is a little flat compared to twelve equal which is why the sharp is lower in pitch than the flat of the note above.
More examples here. Not at all suggesting that musicians should label notes this way :). It's just fun, and also helps you to see the interrelationships of the notes along the cycle of fifths. May also be useful for some of the smaller tunings. For more about this see my recent quora answer to: To be totally unconventional, should a piano with keys of E# and B# be produced? Would it be more versatile and more interesting? Expect it not to be one of the most used features. But it might be interesting to some.
There are many other new features including:
And many bug fixes.
For details of the changes, see Change log and Bug fixes.
This is a major update, and I've been working on it for seven months now, so it gets a new version number, 4.6 (I don't do minor versions as that system doesn't work so well when you have lots of updates, so individual versions are distinguished by the upload date). To get it, visit the download page and you can install on top of your existing version.
As I said, the Mac version isn't quite ready yet - the Bounce for Mac Beta download page it gives instructions on how to update your version of Bounce for Mac with the lastest Windows release. It's just that I've been working on it on Windows, with it sometimes used on a Mac, but not extensively tested at all. So, I want to test it for a while on the Mac after doing quite a major update before uploading the Mac Beta. Though the chances are it will work just fine as I haven't done anything that relates to Mac compatibility in this build as far as I know.
Comments
Post new comment