Page Category: Giocoso

1.0 Introduction

Giocoso's main program display, when you finally get it running, consists of three distinct 'areas', as follows:

The particular colours displayed for the text used in each area will vary, depending on your choice of terminal profile colours (here, I'm using 'Blue on Black', which is why all the horizontal lines look blue) and your choice of Giocoso colour scheme with the --displaycolour runtime parameter, or the DISPLAYCOLOR persistent configuration file parameter. Here, I'm using the default, 'newclassic' scheme which attempts to impart a bit of meaning into the display by its choices of colour: green is just boilerplate; blue is persistent information that depends on inputs you have provided when running Giocoso; yellow is dynamic information that changes depending on what Giocoso is playing or doing at any given time; white is just for text labels. [...] 

1.0 Introduction

Upgrading to Giocoso version 2 from any previous Giocoso version 1 installation uses the same --checkver runtime parameter as you'd have used when moving between different point releases of Giocoso version 1: it's extremely easy, non-destructive and requires mere moments to complete.

In this article, I'll start with a Linux Lite installation of Giocoso 1.13 (the last version of Giocoso version 1) and show you how I end up with a fully-functioning Giocoso version 2. I'll start by showing you that Giocoso version 1 is running, via a database, thanks to the command giocoso --dbname=main, perfectly happily: [...] 

1.0 License (or Licence)

If you launch Giocoso with the --license (or --licence) runtime parameter, the program will fetch and display the GNU General Public Licence Version 2 under which Giocoso is licensed. All other runtime parameters you might accidentally (or otherwise!) throw onto the command line are silently ignored. Thus, this command:

giocoso --license [...] 

1.0 Introduction

Giocoso runs in two basic 'playback modes': Direct Play Mode, where you tell Giocoso what music exists and where it can be found on disk; and Database Play Mode, where a database persistently stores details of what music exists and where it can be found on disk.

The advantage of using a database as the 'source' of information about what can be played is that Giocoso can select from its data in all sorts of different ways. If you want to listen to music that lasts longer than 20 minutes but less than 30 minutes, Giocoso can do that -because the database stores the duration of each piece of music it knows about. If you want to listen to 'some Beethoven', that's fine too: the database stores the composer name associated with each recording it knows about. A database, in other words, lets you filter and select music to be played via all sorts of qualities intrinsic to the music files themselves. Giocoso can even go one step further: it is able to pick something from the database entirely at random. That will mean the music you listen to will be unexpected -and hopefully, more 'fresh' and enjoyable as a result. [...] 

1.0 Introduction

There are some fairly obvious things that need to be true before you can successfully use Giocoso as a music player, but it's probably a good idea to spell them out anyway!

First and foremost, you must store your digital music files in the lossless FLAC format. Giocoso only plays FLAC and will not (by design!) play APE, WAV, MP3, OGG or any other digital music format. It was designed to play classical music: it takes the view that classical music needs to be listened to in as high quality as possible. Lossless formats are the only way to do that. It’s also a piece of open source software and therefore was designed to play open source audio formats only: the Free, Lossless Audio Codec seemed to invite itself to the party, given the huge clues in its name! I am aware that there are other open source lossless audio codecs out there (such as ALAC): none are as ubiquitous or as cross-platform as FLAC. FLAC, therefore, it must be! [...] 

1. Why doesn't Giocoso play anything other than FLAC? What if I want to play MP3s?

There are two answers to this question, really. First: Giocoso is a classical music player, and classical music deserves to be taken seriously; which in turn means listening to it in the best possible quality. Therefore, the audio codec in which you store your digital music ought to be lossless, in my opinion.

Now: there are several lossless codecs out there I could have supported. Lossless WMA is Microsoft-proprietary and I have no idea whether it's on life-support or will remain properly supported and developed by Microsoft in the years ahead. Apple Lossless (ALAC) used to be Apple-proprietary, but has been open source and royalty-free since 2011... but the clue is the name: it's mostly going to be used on Apple hardware and Giocoso is primarily a Linux player. That doesn't leave a whole lot of lossless audio codecs that are genuinely and broadly cross-platform and non-proprietary. FLAC, however, fits the bill. [...] 

1.0 Introduction

Giocoso Version 2 introduces the concept of separate source and destination databases. That is, the source database is a permanent store of where, physically, music files exist on your hard disk, whilst the destination database is a permanent store of what music has been played and when. If you get Giocoso to use the source database to decide on what music to play next, you're running Giocoso in Database Play Mode. If you instead tell Giocoso specifically what music to play next, providing your own details about the physical location of those music files, then you are not using a source database at all and are instead running Giocoso in Direct Play Mode.

If you run Giocoso in Database Play Mode, all completed plays of music are always stored in the same database as was used to source the plays in the first place. That is, in Database Play Mode, source and destination database are always (and irrevocably) the same. You do not need to specify a destination database in Database Play Mode (and it's ignored if you try anyway!) [...] 

Errors when creating or refreshing a database:

1) Creating a database where --dbname parameter specifies a name that would conflict with a filename already found to be present in the .local/share/giocoso folder. If, for example, a file called main.db exists in that folder, and you say --createdb=main, then this warning will appear, as asking to create a database named 'main' implies the creation of a file called 'main.db', which already exists and which Giocoso will not over-write: [...]