public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: [LAU] Yoshimi Command Line Interface (fwd)
Date: Mon, 5 Nov 2018 11:40:29 +0100	[thread overview]
Message-ID: <8C681C4E-8963-4BFD-834F-8FDB1BD3E7C8@pipkrokodil.se> (raw)
In-Reply-To: <Pine.LNX.4.64.1811041758080.23263@server2.shellworld.net>

Hi!
What is it really?
TO me it sounds like a new hole operating system but talking of instrument banks make me think about music and music editing.
/A

> 4 nov. 2018 kl. 23:59 skrev Linux for blind general discussion <blinux-list@redhat.com>:
> 
> Folks,
> Sharing the below in case some of you are in a position  to help them test this   interface.
> Karen
> 
> 
> 
> ---------- Forwarded message ----------
> Date: Sun, 4 Nov 2018 22:53:21 +0000
> From: Will Godfrey <willgodfrey@musically.me.uk>
> To: linux-audio-user@lists.linuxaudio.org
> Subject: [LAU] Yoshimi Command Line Interface
> 
> Our formal command line access is now almost complete. There are just a few
> remaining areas to be improved. The latest push has seen all the synth engine
> controls completed. We're not *quite* ready for a release, but would very much
> like people to try things out. We are actively looking for problems and
> inconsistencies between the CLI and GUI.
> 
> Bank and root management have some naming and adjustment controls missing, and
> the effects parameters are not done - the effects themselves are, and so are
> effect presets. These were done quite a long time ago, and are being reviewed.
> 
> The final missing piece in the jigsaw is copy/paste. This is an interesting
> one. I've a feeling that once the basic structure is organised, it will just
> slot into place like MIDI-learn, and reading limits/defaults did.
> 
> There is likely to be some shuffling to get the most user-friendly command and
> parameter names. There is a huge amount of name duplication. Although this is
> convenient for developers and for the GUI, it makes it harder for CLI users to
> follow. We've already changed some of these to synonyms - and indeed also made
> some of the GUI names more relevant - but based on user feedback they may
> change again.
> 
> There is now an extremely comprehensive and context sensitive help system in
> place. Typing '?' will give you the command information relative to your
> current context, but you can get any other context usually with just the first
> two or three letters, so while in the Part context '? sub' will show all the
> SubSynth commands, and '? li' will show all the dynamic settings that can be
> listed - such as what instruments are in the current bank.
> 
> As usual the source code for the current 'master' is available from either:
>    https://sourceforge.net/projects/yoshimi
> Or:
>    https://github.com/Yoshimi/yoshimi
> 
> 
> -- 
> Will J Godfrey
> http://www.musically.me.uk
> Say you have a poem and I have a tune.
> Exchange them and we can both have a poem, a tune, and a song.
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user@lists.linuxaudio.org
> https://lists.linuxaudio.org/listinfo/linux-audio-user
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list


  reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion [this message]
   ` Linux for blind general discussion
   ` Linux for blind general discussion

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8C681C4E-8963-4BFD-834F-8FDB1BD3E7C8@pipkrokodil.se \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).