Still waiting your answer about JACK status with Yoshimi
El mar., 1 de ene. de 2019 02:59, <distro@xxxxxxxxxxxxxxxxx> escribió:
OK, there you have it and time has run out. It's all there on the table.
I am officially closing this thread. I am un-subbing so any more
commentary directed at myself or words directly relating to this pathetic
fail on the mailing list in regards to certain members, could only possibly
be a subversive attempt to bury and distort the truth.
For the sake of the mailing list, it would be respectful to close this
thread entirely with no further replies. I will not respond obviously as I
will not see it any further.
HOWEVER, My intent from post #1 was ask a simple question and provide
answer for GENERAL USERS aka (I by accident created new word by
miswording), still VERY relevant to this group apparently: the GENERAL USER
INTERFACE (fail) and the current GRAPHICAL USER INTERFACE, in regard to how
to simply connect your midi controller VIA the setting options in Yoshimi.
I have found the solution and have done was I stated to do, and provided a
draft step-by-step instruction that should get the general user working
with their midi controller.
You'll have to refer to the 12-2018 archives.
[yoshimi] [SOLVED] adding external midi controller
<https://www.freelists.org/post/yoshimi/SOLVED-adding-external-midi-controller,1>
Good bye and Viel Spass.
Dec 31, 2018, 10:56 PM by rainer.liffers@xxxxxxxxx:
Fine, mate.
It seems that you got my message, but I am also the forgive-and-forget
type. Make sure you won't misuse this aspect in the future.
May I suggest that, in order to demonstrate your "simple respect" point
and to reassure everyone else on this list, you start with an apology to
all people here who have their "heads up the jackass". Believe me, it will
work wonders.
Once you have done that, please answer the following question: *Why*
do you prefer to use ALSA instead of JACK?
On 1/1/19 12:32 pm, distro@xxxxxxxxxxxxxxxxx wrote:
way to go, justing testing this mailing list at this point to see how many
others people are actually focused on yoshimi. Look at all the responses
and words said by others.. Only one guy Diego had any desire to attempt to
help out.
Thus I am the only one (along with Diego) not making excuses or for no
good reason devolving (NOTE THE THREAD TOPIC) this thread into a pathetic
trolling attack mechanism.
The only reason I am still hanging around while I mess around with the
synth tonight is to see if anyone out there on the list actually cares
about the synth, or if there are only in fact a few people around who
circle jerk around and like to gang up on a person and keep matters off
point, probably disrespecting to the developer as well. Good job. Your
intent is fully on display and 'graphical' - hey my typing is getting
better.
Out of some simple respect, I will not participate or respond to stupid
relies, OK?
Dec 31, 2018, 10:23 PM by rainer.liffers@xxxxxxxxx:
Oh dear, oh dear, what have I done, dearest Distro?
I cannot tell you how much I now regret my critical remark.
No doubt, the way you argue is incredibly awesome and
convincing. In fact, it reminds me of my ex-wife, the only
other perfect human I am aware of.
Please believe me that I am full of remorse, and I can now
clearly see your superiority in all respects. I also
realise that, for the rest of my life, I have no choice but
to keep on asking myself: Why can't I be like you?
Sorry again, mate. so sorry.
On 1/1/19 11:52 am, distro@xxxxxxxxxxxxxxxxx wrote:
What an ass, whoops sorry for the mistype idiot #3 Hans perfect for a the
circle jerk
Dec 31, 2018, 9:51 PM by rainer.liffers@xxxxxxxxx:
G'day from WA, Distro-mate
*Begin of Aside*
Last time I checked, GUI was an acronym for *Graphical* User Interface,
*not* General User Interface. Just then, I checked again to be sure:
https://en.wikipedia.org/wiki/Graphical_user_interface
*End of Aside*
So much for being right all the time, Mr Perfect.
On 1/1/19 7:10 am, distro@xxxxxxxxxxxxxxxxx wrote:
OK. I have come to both a conclusion and resolution. I did get it to work
and I will explain how. But first I want to capstone and address the bad
dialogue that happened here. I also invite you to re-look into my simple
question and actual detailed outline/scenario that came with it. And then
to the next and final message in which I will simply and concisely type
instructions (for apparently users new and old) to comprehend current
situation briefly and also to note how to give short, efficient feedback.
Note my thread/email title. From step one, I type that name so others in
future, if needed, can search and find and answer QUICKLY AND WITHOUT GRIEF.
- GENERAL STATEMENT -
#1 I do want to point out (and I don't care, rudeness deserves rudeness)
ZB / Zbigniew was 100% wrong in not only facts or perception but his
attitude and response for me. I am a very informed linux user as well as
communicator and developer etc. Most of all I am a normal average person
who understands details and simple clear process and instructions are
important and to relate and communicate in writing and documentation
towards people not assuming they are overly familiar with utilities or
regularly use and fiddle with audio drivers, soundcards etc. Common sense
or they might not be coming with questions to a mailing list.
#2 Further there are a wide range of utilities available on linux, some
cli (commandline interface) and gui (general user interface). GUI exists
and is called General User Interace - for just that.. common regular
computers users, no in-depth "dependencies" or familiarity/knowledge based
requirements. Only a knucklehead would not understand this and just be
polite. I believe people can always change and improve, so I say this
purely as constructive criticism and feedback.
Never assume people's familiarity with any particular package or even
basely their remembrance of utilities. Some of the smartest and most
technical developers and linux users understand not to live in a box. This
had been a longstanding issues and why it literally took 2 decades for
basic simple GUI and toolkits to develop.
Any thank you to those who provided and attempted to help me resolve the
issue.
In my next final message, I will provide simple solution and pertaint
explanation. I assume Will can respond similarly regarding to verify the
ALSA issue and possible goals to improve the GUI (and Will, not realtime
connection, I obviously was talking about when a midi controller is plugged
in and recognized by the system).
- FOR WILL -
(please see message below.)
Will - please comment back on the ALSA issue see message below. So my
verdict or discovery here is (you can just verify)
###
Dec 31, 2018, 4:47 PM by distro@xxxxxxxxxxxxxxxxx:
Will,
yes to reiterate (and it appears you understand)
for example, with pkg alsa-utils, you can run command:
$ aconnect -i
RESULTS:
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'Impact LX25+' [type=kernel,card=1]
0 'Impact LX25+ MIDI 1'
1 'Impact LX25+ MIDI 2'
1. Now the key value here would be client 20: Impact LX25+
The identifier and which all other programs, whether it be the pkg
alsa-mixer will identify as the sound source (along with Intel, PulseAudio,
soundcards etc)
2. For an example, easily seen I assume VMPK is available widely for most
distros..
You can go to the Edit > Midi Connections. With ALSA selected as driver,
you'll see a drop-down where you can keyword: specify the driver, which
displays the identifier: "Impact LX25+"
3. Now in Yoshimi, under Yoshimi < Settings, under ALSA tab, you do have a
form-field it appears where you should be able to specify this value
"Impact LX25+" similarly. SEE form field "Alsa Midi Source"
See the logic? It is not a drop-down currently but a form text field. It
would be great at least if one could just pop in their midi-controller and
value. And obviously the coding behind making a simple drop-down would be
warranted if function.
4. So the question is: is this form field functional? Is there a method
into which one can specify their midi controller under ALSA. ( simple yes
or no on the first will suffice, latter question, if yes, how?)
In reference to below, note the difference,
$ aconnect -l
RESULTS
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 14: 'Midi Through' [type=kernel]
0 'Midi Through Port-0'
client 20: 'Impact LX25+' [type=kernel,card=1]
0 'Impact LX25+ MIDI 1'
1 'Impact LX25+ MIDI 2'
client 128: 'yoshimi' [type=user,pid=28366]
0 'input
THUS, naturally tried the client in the field, rebooted etc. No dice.
So still working on it, I am guessing then there is no direct way
currently to config ALSA?
#
Dec 31, 2018, 4:28 PM by willgodfrey@xxxxxxxxxxxxxxx:
Going back to the start...
First of all, please keep in mind that Yoshimi has a *very* small number of
people who can devote a lot of time to it. That small number being 1 - me
:(
When I first looked at the MIDI code it didn't attempt to make any
connection
at all (neither did most other software I came across). Some stuff did, and
used the ALSA port primitives to connect to the first device it saw. Which
was
highly dependent on what order things are started up, and assumed no
re-starts.
None of this mattered much to most people as qjackctl was used to quickly
link
stuff together by name, or they used session software. Also Rosegarden (my
sequencer of choice) could find Yoshimi and auto connect to it if
configured to
do so. That last bit is important because if it was not configured to, then
trying to connect via qjackctl would appear to work but Rosegarden ignored
the
connection - it had to be the boss.
Over a period of time I worked out how to identify a source by ID (rather
than
port number) if it was known, and provided the entry in the ALSA tab for
that.
If you know the ID the hardware reports (which may not be quite the same as
printed by aconnect -l) just enter that, save settings and Yoshimi will
find it
and connect to it every time it starts.
That did everything I wanted it to at that time, and apparently what
everyone
else wanted, so I moved on to other more important issues.
I would refer you to "The Short Yoshimi Guide.odt" in the "doc" directory
for
some more info on this.
This is the first time anyone has raised this since then, and although
I'll put
it on the list, I can tell you there is still much more that Yoshimi
*really*
needs.
If we were really smart we'd be able to find inputs in real time as they
appear, but although that is easy to suggest, it is enormously complex to
implement.
Yoshimi is first and foremost a soft-synth, When Cal forked it from Zyn
2.4.1
he initially stripped out everything that was not essential, and since I've
been in the driving seat I've tried to keep as close to that as seems
reasonable.
--
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.
Yoshimi source code is available from either:
https://sourceforge.net/projects/yoshimi
Or: https://github.com/Yoshimi/yoshimi
Our list archive is at: https://www.freelists.org/archive/yoshimi
To post, email to yoshimi@xxxxxxxxxxxxx