Welcome to Magle International Music Forums! A community covering a wide array of musical genre. You are currently viewing our boards as a guest which gives you limited access to view most discussions and articles. By joining our community you will have access to post topics, communicate privately with other members, upload your own music and photos, and access many other special features. Registration is absolutely free so please, join our community today!

Interesting project! I guess that it would be possible to use the "create bootable usb stick" feature of Ubuntu to move the .iso image to usb like any other live-cd? Also I assume it should be possible to install to a usb (or any external) drive too? Of course with the limitations that comes with it compared to a traditional hard-drive install...

I guess that it would be possible to use the "create bootable usb stick" feature of Ubuntu to move the .iso image to usb like any other live-cd? Also I assume it should be possible to install to a usb (or any external) drive too? Of course with the limitations that comes with it compared to a traditional hard-drive install...

On Linux, you can simply dump it with "dd if=GOtoGO.iso of=/dev/sdX" on the whole device (not partitions like /dev/sdX1).

I don't know, what the bootable usb stick feature of Ubuntu exactly does.
If it simply does this, it will work. If it tries to modify the image while copying, probably not.

For a simple file manager, desktop, GO, archive manager, and text editor, this Live CD is rather large (over 600Megs) in comparison to doing it with Puppy Linux remastered (comes to about 250Megs). Any reason for taking this route rather than a remastered Puppy?

The greatest disadvantage with Puppy Linux (last time I tried it) was the lack of localizations done in an easy way and also both the audio and display settings seemed to need a reset more or less every other reboot (even on the same computer). But I can agree that both the size and performance of Puppy was incredible.

If I had more time I would really like to create a customized (remastered) live (cd)/installer that was built with only the absolutely necessary things to run GO (scripted to start when system starts and when closed shut down the system) that could be used for true console embedding projects (no desktop environment, no display manager, no network, no browser needs to be included).

Anyway, I still think that this project is highly interesting as it makes it easy for anyone to get a fully functional GO environment to try out without the need to install anything themselves. If you want to create a remastered Puppy version with GO then that would be just fine to compare with!

The CD has not been optimized for size. I eg. selected a more capable editor from the KDE desktop, as it easily allowes the user to control the file encoding. This pulls in some KDE libraries, which increases the size. 300 MB size difference are irrelevant, if you consider the trend in sample set sizes and the storage device sizes. It also includes a installer.

If I had more time I would really like to create a customized (remastered) live (cd)/installer that was built with only the absolutely necessary things to run GO (scripted to start when system starts and when closed shut down the system) that could be used for true console embedding projects (no desktop environment, no display manager, no network, no browser needs to be included).

I have thought about the embedded use case and in my option, the system is useable for that, if it has been installed with the Live installer.
* I want to go crash safe - just pull the power plug and don't care for a proper shutdown (A few syncs are still missing in GO)
* It already starts GO and loads the last used organ
* For configuration, you need a GUI (monitor, keyboard) anyway - so simply disconnect them afterwards and ignore the GUI staff
* If network port is not connected, the network stuff does not matter.

I admit, that the current version shows some not necessary delays in startup - I can eliminate them later, if no other issues turn up.

Hi Martin,
I have try your GO Live it is an intersting project.
More precisely I installed it on hard disk and
I created a usb stick using ImageWrite.

But my need is a bit different.
I figure user who does not have the practice of computers and a well know organ console.
I want to have two options:
1 "GO" with no graphical interface to be used but only the console midi.
2 "GO" standard using a small desktop manager like LXDE (like your GO LIVE)
or XFCE
If there is a monitor it's possible swith using grub

So my linux GO box is a bit different I use ubuntu 13.04 64bit.
It's a handly configured machine wiithout desktop manager only fluxbox.
First time it's configured using ssh -X then
In 30'' must start up and upload grandorgue sample sets ( 2,5 GB ).

About Swell
If there were a simple Crescendo when I do change I can upload only a file .organ and user without computers experience can continue to use a good standard midi organ.

I don't see any issue with using 2) also for 1). Compared to current sample set requirements, the overhead of a lightweight "desktop" is neglactable.
PC compatible hardware feature a graphic card, so there should be no problem with running it without any display connected.
For remote access to GO (eg. instead of connecting a display to the GO box access it from a laptop over the network), my idea is to use VNC (not yet implemented).

GO Live was just a first proof of concept - it has not been optimited for fast boot. Instead I have spent time to get GO crash safe [you shut down by just pulling the power plug].
My last build happend some time ago, so it should be updated ["zypper update", if it is installed on the hard disk]. Probably after the next openSuSE release, I'll work on an updated version.

An .organ file only describes a organ - it should not contain any configuration or personalisation. The same, unchanged ODF should be used for all users of that organ. Therefore stuff like setter content is not part of the ODF.
PS: The crescendo can be programmed via MIDI [you just need as minimum CrescendoNext + the normal Set button].

You can:
* run it from a CD without installation (I would recommend >= 2GB of RAM).
* run it from a USB stick
The remaining part of the USB stick will be used to persist changes across reboots.https://en.opensuse.org/SDB:Live_USB_stickhttps://en.opensuse.org/SDB:Create_a..._using_Windows
* Install it via the Yast Live Installer. Just a few hints:
- I would recommend changing the file system from ext4 to xfs during installation
- The installer asks 2-3 time to create a user. Deny it every time.
- As this system is intended for a organ only PC, it does not require any login.

Extending this concept and only considering USB sticks and not CDs, would it be possible to have GO live with a capability to have a choice of one or more sample sets and ODFs on the same stick, - using currently available sample sets. Maybe aimed more at the organ only PC or console embedding?

Cheers MIKE.

How many roads must a man walk down ... ... before he admits he's lost?

Building such a image is not a technical problem. For redistribution, the sample sets need to have apropriate licenses (eg. CC BY-SA as used by Lars sample sets)
Shipping a GO Live with multiple samplesets as part of the GO project is a hosting issue. The GO demo set is only about 21MB. A good sampleset takes GBs of space - such things would in my option missuse the free hosting options at sourceforge.net.

If you installed GO live (or have put it on a USB stick), just enable your network card via Yast, dowload the samplesets via Firefox, disable the network and extract it. The GO live system includes all necessary tools this.

GO allows you to configure switching organs via MIDI, so after configuration, you can use multiple samplesets without any monitor/mouse/keyboard attached to your computer.
I try to create a crash-safe GO Live (= there is no need for a proper shutdown of the computer). If you want to persist modified organ settings (eg. general/divisial content), you need to trigger save [also possible via MIDI].

I should probably have made it more clear that I was suggesting downloading currently available sample sets from where ever they are now, not that they should be hosted by Sourceforge. As you say GO live has the tools to do this.

Cheers MIKE.

How many roads must a man walk down ... ... before he admits he's lost?

It adds support for organ packages (*.orgue - help includes the format specification). The user just needs to drop the file in the organ package directory and at the next start, GO will make all included samplesets available - or you can register organ packages at other locations. Organ settings are releated to organ packages, so they are kept, if you move/rename organ packages.