Hi,
See https://musescore.org/en/node/20099
I would still love to have a plugin or even a core tool to add fingerings
to a piano score in MuseScore!
lasconic
2017-08-25 20:26 GMT+02:00 Tommaso Cucinotta :
> On 23/08/2017 22:24, Tommaso Cucinotta wrote:
>
>> b) show
On 23/08/2017 22:24, Tommaso Cucinotta wrote:
b) show in full light the next key-sequence I'm waiting for with option 1.b)
above, however also show in half-light (darker) the subsequent key-sequence
I gave a shot at this "look-ahead" feature, a snapshot of it working is at:
[+list]
On 23/08/2017 22:33, Ariel Aramburu wrote:
"*System Exclusive*.
This message type allows manufacturers to create their own messages (such as bulk
dumps, patch parameters, and other non-spec data) and provides a mechanism for
creating additional MIDI Specification messages. The
You could use http://electronicmusic.wikia.com/wiki/System_exclusive or you
could send events using another protocol than MIDI.
MuseScore embeds an OSC server, it doesn't send OSC message during playback
but it could. OSC might be a lot more flexible than MIDI for your purpose
(but I guess it
On 23/08/2017 00:29, Ariel Aramburu wrote:
Nice video !!!
Thanks, I'm working on a better one, showing some more features :-), and with
someone helping with the camera :-)...
Have you seen this keyboard with integrated lights ? (
meddelande-
> Från: Tommaso Cucinotta [mailto:tommaso.cucino...@gmail.com]
> Skickat: den 23 augusti 2017 00:14
> Till: mscore-developer@lists.sourceforge.net
> Ämne: Re: [Mscore-developer] ?= Compiling MuseScore on Linux
> (Ubuntu=?utf-8?q? 17.04)
>
> On 21/08/2017 13:48, To
//
-Ursprungligt meddelande-
Från: Tommaso Cucinotta [mailto:tommaso.cucino...@gmail.com]
Skickat: den 23 augusti 2017 00:14
Till: mscore-developer@lists.sourceforge.net
Ämne: Re: [Mscore-developer] ?= Compiling MuseScore on Linux
(Ubuntu=?utf-8?q? 17.04)
On 21/08/2017 13:48, Tommaso Cucinotta wrote
On 21/08/2017 13:48, Tommaso Cucinotta wrote:
your facebook link doesn't work btw.
security settings for that post changed to allow outsiders, now you should see
it.
Video now (with poor recording abilities being quite evident :-)):
On 20/08/2017 16:24, Tommaso Cucinotta wrote:
3) the MuseScore version I succesfully managed to finally compile, tweak/modify
and use, is origin/2.2 (standard Qt 5.7 from Ubuntu 17.04)
double-checking commits, I found out the confusion: this was actually based on
2.0.3, now I forward-ported
a <
> m...@outsideshore.com>; Tommaso Cucinotta <tommaso.cucino...@gmail.com>
> *Subject:* AW: Re: [Mscore-developer] ?= Compiling MuseScore on Linux
> (Ubuntu?==?utf-8?q? 17.04
>
>
>
> Building 2.1 or 2.2 on/for Linux is IMHO legitimate as many distributions
> d
That cherry-pick would only be needed in 2.0.2 or older, as 2.0.3 and later
have it already.
Tommaso Cucinotta schrieb
>On 20/08/2017 22:14, Lasconic wrote:
>> Where is patch 5320fa196 ?
>
>perhaps I had mistakenly copied the hash after cherry-pick, instead of before
>;-P ? anyway,
Building 2.1 or 2.2 on/for Linux is IMHO legitimate as many distributions don't
provide the former and MuseScore doesn't provide nightlies for the latter.
Tommaso Cucinotta schrieb
>On 20/08/2017 21:21, Marc Sabatella wrote:
>> Still, the more important question is the one I asked -
gmail.com>
Subject: AW: Re: [Mscore-developer] ?= Compiling MuseScore on Linux
(Ubuntu?==?utf-8?q? 17.04
Building 2.1 or 2.2 on/for Linux is IMHO legitimate as many distributions don't
provide the former and MuseScore doesn't provide nightlies fo
On 20/08/2017 21:21, Marc Sabatella wrote:
Still, the more important question is the one I asked - is there a
reason you are building 2.2 at all?
the answer is similar to the one previously given in my prior post about the "why
2.0.x"...
... convenience, ease and speed of getting started,
On 20/08/2017 22:14, Lasconic wrote:
Where is patch 5320fa196 ?
perhaps I had mistakenly copied the hash after cherry-pick, instead of before
;-P ? anyway, the patch was that simple 1-liner with a reset() call.
your facebook link doesn't work btw.
security settings for that post changed
Where is patch 5320fa196 ?
The patch from https://github.com/musescore/MuseScore/commit/ae7495b7633d50
a15e2bc3767add73ffb40817f9 is already in the 2.2 branch
https://github.com/musescore/MuseScore/blob/2.2/zerberus/zerberusgui.cpp#L99
your facebook link doesn't work btw.
lasconic
2017-08-20
Could be, or it might just be that while 5.4 is recommended and what
released builds use, 5.3 might technically be sufficient.
Still, the more important question is the one I asked - is there a reason
you are building 2.2 at all? Normally, people should *not* be doing that,
especially for
On 20/08/2017 16:43, Marc Sabatella wrote:
If you do a search of the issue tracker you should find previous discussion of
this.
indeed,
https://musescore.org/en/node/71001
and patch 5320fa196 applied nicely and removed the spurious dialog, thanks!
I might have missed this discussion, but there a reason you are building
2.2? New development should normally be on master.
Anyjow, my understanding is the spurious Loading dialog on Linux of using
the wrong Qt version. I believe 2.2 is supposed to use 5.4, some newer
versions aren't totally
On 18/08/2017 19:15, Lasconic wrote:
Werner and I build several time daily from the command line. Werner
on Linux and I, on MacOSX.
Also for every commit on the 2.2 and master branch, Travis runs on
the command line on Ubuntu 14.04
https://travis-ci.org/musescore/MuseScore/jobs/265942105
So
Werner and I build several time daily from the command line. Werner on
Linux and I, on MacOSX.
Also for every commit on the 2.2 and master branch, Travis runs on the
command line on Ubuntu 14.04
https://travis-ci.org/musescore/MuseScore/jobs/265942105
So there is something very particular in
On 18/08/2017 17:41, Ralf Mattes wrote:
Where did you get your sources from and how exactly did you try to build.
Hi,
so I guess from answers to your post that the problem we're facing is that core
devels build from some IDE, so the command-line is not used that often.
Hmm - that allmost
22 matches
Mail list logo