Tag: Giocoso

Today, a few days earlier than planned, I'm releasing Version 3.20 of Giocoso. It's a very significant release and the version number has therefore jumped from 3.1x to 3.2x (specifically, from 3.12 to 3.20), as previously explained.

The two (relatively!) huge changes that have occurred are: 1) Ability to control a play (pause, resume, terminate, repeat etc) from within the playing Giocoso session's main play screen; and 2) Accurate timing information is now displayed (i.e., 'played X minutes of a piece that lasts Y minutes, therefore ending at Z clock time'). These were canvassed in some detail in an earlier blog piece. [...] 

Note: I've updated this post since originally written. The next release of Giocoso was due to be 3.13. I've subsequently decided to make it 3.20. I've therefore mentioned that version number in the update.

Giocoso Version 3.20 promises to be a really big version bump (so big, in fact, that I was thinking of calling it Version 4.0, but ultimately decided against it). It is currently scheduled for release in mid-December (after I've dog-fooded it for another few weeks). For anyone interested, the list of changes that are in the pipeline for the next release of Giocoso is visible in the program's changelog. [...] 

As I discussed in the last post here, Giocoso can be affected by the problem of 'fake, duplicate play completions' being inserted into its PLAYS table one second later than the real completion of a play is recorded.

I promised a fix: today is therefore the release day for Giocoso Version 3.09. The new version adds a trigger to the PLAYS table that prevents such fake duplicate plays being created in the future. The fix does not go back and eliminate any existing fake duplicates, since that would involve automatically deleting data from PLAYS, and that sort of thing is very tricky to get 100% right and thus not endanger good data. [...] 

A new version of Giocoso has been released, bringing its version number up to 3.07.

This is rather an important release, though not for particularly good reasons! [...] 

A new release of Giocoso has been made available, fixing a recently-discovered minor, but annoying, bug. This brings the current version of Giocoso up to 3.06.

The bug was that if you used any of the non-default methods of selecting music to play from the Play Music menu (such as Option 2, where you specify filters to control the selection, or Option 5, where a playlist is used to determine what to play and in what order), the number of 'selections' to be played would be remembered if you halted those non-default plays early and then switched to using Option 1's 'play music with defaults' menu option. For example: take Option 2 and say 'play only music that lasts less than 10 minutes': maybe that will generate a list of things to be played that numbers 1345. After playing 4 things from that list, you interrupt the play (by issuing an Autostop request, for example) but do not quit Giocoso. Then you take Play Music option 1: the default, randomised selection of music now takes place... but Giocoso will still declare that there are 1345 items to be played (the top right-hand corner will display something like 'Selection 1 of 1345'). That's because it's a bug of omission: the default play method didn't explicitly set the limit on plays, so if another play option did, the default play method was stuck using that number of selections. [...]