lasconic wrote
Chordnames and Figured bass styles are already hidden in Style - Text
Style.
I don't see why they should be selectable in the Text Tool bar (the bottom
bar when your enter a text), or why this bar should be displayed at all
for these 2 types.
Same for right click - text
ChurchOrganist wrote
Are there instructions anywhere on upgrading the MuseScore Development
Environment to QT 5?
If it's just a case of installing the QT 5 binaries I can probably cope
with it, but if I need to start sorting out fresh links to MinGW etc, then
I'm afraid I will need some
Exactly same behaviour (compile succeeds, run fails on loading .qrc
resources) here in a slightly different the system:
Mint 14 64bit
Qt 5.1.0 64bit installed from offline installer
cmake 2.8.9 (default in distro)
gcc 4.7.2 (default in distro)
Commit c4e95c776 (yesterday evening) compiled
It is not up to me to make objections! Just out of curiosity:
1) You are an organist, I am not. Is McCoy's Jeux (I think you refer to the
1.4 version) good enough (flexible enough) to be worth including an
organ-specific sound font? I played with it years ago and I have no specific
recollections
lasconic wrote
The font should be the same.
Even with the same fonts, a different freetype version might be enough to
generate slightly different rasterizations.
Any idea is welcome, but I would prefer to solve the root cause.
Yes, but it is important to detect (and then, if possible, solve)
Hello John,
Thanks for the intro and welcome aboard!
I'm the person assigned as mentor to your project; I saw you already walked
a good way on yourself, but do not hesitate to contact me at any moment: in
the MuseScore fora and in the IRC #musescore channel, I go under the
nickname Miwarre, and
I noticed that some guitars lack string data in instruments.xml. Not being
particularly familiar with guitars beyond THE guitar, before messing with
the file, I would prefer someone could confirm the following details:
1) *Soprano guitar*: does it exists? I found surprisingly few references for
And now about basses and bass guitars.
1) The instruments.xml file contains entries for: A) bass guitar, B)
acoustic bass, C) electric bass. Are they 3 different instruments or A) is
just a generic name for both B) and C)?
2) *MIDI*: They are assigned 3 different MIDI channels: A) 34, B) 32, C)
Marc, thanks for the reply.
Now that you say it, I think I remember having read about this equivalence
acoustic bass lt;=gt; contrabass in another thread either here on the ML
or in the fora.
Just to avoid future repetitions of the question, I think I will change the
acoustic bass entry in this
About the lt:initgt; tag, see for instance:
https://github.com/musescore/MuseScore/blob/master/share/templates/instruments.xml#L7934
--
View this message in context:
http://dev-list.musescore.org/Bass-guitars-in-instruments-xml-tp7578800p7578822.html
Sent from the MuseScore Developer
AndreiTuicu wrote
The number of strings that are set in the staff properties should match
the number of lines from the tab.
No, it should not. There is plenty of instruments for which the number of
strings is different from the number of tab lines, for instance most of the
lute models (and most
Thanks to David for unearthing the original source of these data
(palaeo-organology?).
ChurchOrganist wrote
I suspect the multitude of guitars have been added to cater for mariachi
bands which, according to Wikipedia use several sizes of guitars.
AndreiTuicu wrote
If for example I select a button using TAB and press Return, the button
will not be clicked, instead the system break action will be triggered. If
I'm editing text in a textbox and press CTRL+A I'm not selecting the whole
text, instead I'm triggering the action that selects
There seem to be problems with enum's in the current plug-in framework:
according to documentation, to be accessible to QML, enum's should be
defined *within* a QObject derived class.
See
https://qt-project.org/doc/qt-5/qtqml-cppintegration-data.html#enumeration-types
or
Jojo-Schmitz wrote
From: Joachim Schmitz [mailto:
jojo@
]
From: Maurizio M. Gavioli [mailto:
miwarre@
]
https://qt-project.org/doc/qt-5/qobject.html#Q_ENUMS:
In addition, the class defining the enum has to inherit QObject as well as
declare the enum using Q_ENUMS().
Here's where
Aaaalleluja, lleluja, alleeluuj
*Demo:*
I was planning to provide one or two short demo scores of historic
tablatures; say, one Dowland piece for lute (or one Hume piece for viol) for
the French tab style and one Verdelot madrigal tabulated for lute by A.
Willaert for Italian tab
Sorry for the double post; afterwards posting to the forum, I realized the
dev-list is probably a much better place.
Having spent several days trying to 'clean up' the situation for bar lines
with little result, I'll note here the most important issues and
inconsistencies I noticed, trying to
I'll take the issue http://musescore.org/en/node/30941 as an example (but
other examples exist and more or less anybody met this anomaly once) and
specifically the sample score posted in the thread last comment (
http://musescore.org/en/node/30941#comment-129056 ):
I think (part of?) the problem
Marc Sabatella wrote
Thanks for looking into this further! [...]
I see two possible strategies:
1) *Score::layoutSystem()* checks for potential courtesy elements before
adding another measure to the system.
2) *Score::layoutSystemRow()* checks for available room before adding the
A small detail: I discovered that the 'standard' FreeSans.ttf coming with my
distro has a different structure than FreeSerif: if open with FontForge, it
lacks kerning data for Latin (as 'our' FreeSans does); possibly they are in
the old-style 'kern' table rather than in the GPOS table / 'kern'
I start by limiting my observations to Linux, where I can analyse things more
thoroughly. My system: Linux Mint 17 64bit, with self compiled sources with
Qt Creator 3.1.2 and Qt lib 5.2.1. MuseScore built-in .ttf fonts are used as
they come in the current master.
I had the additional problem that
Ok, let's use the big guns...
I run ttx on the current MuseScore FreeXxxx.ttf fonts and on your Mac and
non-Mac variants (downloaded from your github PR). Leaving aside for the
moment being the bold variants, these are the results.
*1) Common tables*: All fonts contains the following tables
OK, one .ttf is worth a thousand words... ;)
you (as well as everybody else) can download my attempts so far from:
http://vistamaremusica.com/extras/FreeSans.ttf
and
http://vistamaremusica.com/extras/FreeSerif.ttf
Both kerns correctly in my MuseScore and contain all the original data. I
Marc Sabatella wrote
No dice. Neither of those fonts kern correctly for me on any of my three
systems. Again, both Linux systems are running Qt 5.4; there, neither
font kerns at all. My Windows machine has Qt 5.3. On that machine, your
FreeSerif will kern the rj but not the Te or the VA.
Marc Sabatella wrote
I am using Ubutnu 14.04, and 31 the July 2012 version of FontForge.
Linux Mint 17 here, which is a derivative of pretty much the same as your OS
(I never manage to remember the correspondence between the two lines). I
used the same FontForge as you up to 3 days ago, when I
Just for future reference, it might be helpful to other Linux Mint users.
I used the following procedure on an old notebook with a fresh installation
of Linux Mint 17.1 (Rebecca) without any trace of previous MuseScore or
custom Qt installation (Mint 17.1 comes with Qt 5.2.1):
1) Added the PPA
lasconic wrote
According to https://bugreports.qt.io/browse/QTBUG-18980 Harfbuzz-NG is
the default *shaper* now in Qt 5.4.
Glad to know! This seems a step in the right direction.
My understanding is that the font *layouting rendering* is still
different per platform[...]
Thanks for the
Jim Newton wrote
Thanks. I have not talked to Miwarre before.
You did, you did... It's me...
Your suggestion to create a public accessor for items is more or less what
I am doing in the mean time.
I would not encourage creating public accessors to FiguredBassItem's, unless
really necessary
Maurizio M. Gavioli wrote
[...] But the under-notated (for our 'modern' feelings) B.c. in most of
the XVIII c. music is hard to realize automatically [...]
Of course, it is a typo; I was meaning the XVII c.!
Maurizio
--
View this message in context:
http://dev-list.musescore.org
A) Properties
Currently the plug-in documentation generated from comments in the source
code uses a C/Qt notation in properties:
*) MuseScore objects are prefixed with Ms:: (like Ms::Measure)
*) String returned values are labelled as QString
*) Returned pointers are notated as C pointers
While looking for ways to improve / extend font support via Qt, I found this
Stack Overflow post:
http://stackoverflow.com/questions/24673444/which-opentype-gsub-features-does-qt-4-8-support
(which, its title notwithstanding, also deals with GPOS features, like
kern, and also covers 5.3).
I have
First of all, I have no suggestions on the maintenance points.
About the main topic, FWIW I also believe that bug fixes are always welcome!
With a few notices:
1) Users do not always care (or even know) about product versions (many do
not even care about which OS they use...). I assume that
Jim Newton wrote
So I experimented with playback and it indeed sounds horrible.
What I want to do now, is something like the Explode command.
This I'll have musescore translate the encoded Figured Bass into notes on
a staff which the user can then manipulate manually.
Does not sound simple...
lasconic wrote
1- I agree that too short delays have consequences. However MuseScore has
an update checker and it will nag users every week or so to upgrade to a
more recent version. Also, I prefer having more user support to do with a
simple answer (Please upgrade) than not having a good
Jim Newton wrote
BTW does the Figured Bass notation in musescore support the tasto solo
keyword?
In which sense? By definition tasto solo passages have no figures, so
there would be nothing to store the flag into.
--
View this message in context:
During the discussion on the recent PR for Figured Bass realisation, by going
by bits and pieces, things became unncessarily complex and the global
picture harder to get.
My impression is that, once we start from the basic 'rule': sharp = major
| flat = minor, there is a quite simpler way to
lasconic wrote
Yes, the update notifier works well on Windows and Mac. I test it for
every release.
It's completely disabled on Linux and BSDs since it's the role of the
package management system on each platform.
Oh, I see, this explains everything. Thanks.
--
View this message in
Jim Newton wrote
Is there a way to store tasto solo in the figured base data structure,
and a way for the user to enter it. Consequently, there would be a way to
programmatically detect the difference between missing FB and tasto solo.
As I said, the standard situation is to have no figured
Jim Newton wrote
I'm working on a function which extends (adds notes to) some chords
according to a particular algorithm.
I'm using the function chord-score()-addNote() to insert the notes.
Unfortunately, this function creates notes whose note-line() is 0. I
guess this gets rectified later.
Jim Newton wrote
> It seems to me that the only thing ornaments and articulations have in
> common is the manner which they get rendered in print. Although, it get
> the impression when dealing with the code, that they should both be
> represented as two subclasses of some common class.
This is
heuchi wrote
after Werner's change to fix compilation with Qt5.5 I'm getting warnings
like this:
/home/joern/MuseScoreQt55/libmscore/element.cpp: In member function
‘virtual QPointF Ms::Element::pagePos() const’:
/home/joern/MuseScoreQt55/libmscore/element.cpp:520:34: warning: suggest
It occurred to me that some of the complexities we are regularly facing with
linked staves may stem from the fact that the current concept of staff
linking gathers together two rather different types of links:
1) The *score part = separate part* link: the basic idea here is
that the two staves
ChurchOrganist wrote
>
> lasconic wrote
>> In any case, it should already be possible to create instruments.xml file
>> to send CC messages at any point of the score to an external or internal
>> synth, even in MuseScore 2.0.3. Anyone tried it already?
> Yes - that was how registrations changes
FWIW, as the one who coded most of the tab feature, I second lasconic in his
opposition to anything tied to a specific instrument; for instance, the
piano Ped. feature is there, but it is not specifically tied to a staff
being a piano staff, for it being used or usable (the user is ultimately
Thanks for the reply, lasconic.
lasconic wrote
> Maybe you have another Qt installed by your system?
Sure I have: the Mint 17.3 distro comes with Qt 5.3. However it should not
matter, as Qt 5.4 and 5.8 are installed in my home and, for instance, while
using Qt 5.8, it finds everything it needs
Oh well, MY FAULT!
Cleaning more accurately before switching between versions of the MuseScore
sources DOES WORK!
(After almost a year of working only in Java, it is surprising how one
looses familiarity with details and how much hodgy-podgy C++ dev would
seem...)
byan61 wrote
> I made some changes for adding a linked Jianpu staff to a standard staff
> and converting the note pitch/tpc values to Jianpu note numbers. See the
> picture below.
> I am currently using layout of the standard staff. I still need to to put
> all the Jianpu note numbers on the same
Two years have passed and things do not seem to be very different. Qt code
base now does include HarfBuzz (since a few versions), but it is unclear to
me if it uses it at all and if it gives an application any (more or less)
direct access to it.
I could do a scan of recent forum topics / issues
Jojo-Schmitz wrote
> Works just fine on Windows. Only that load/create mp3 dialog needs to be
> dismissed
Do you mean that you (and possibly other as well) can open an existing score
via the "File | Open..." menu command? That it may be a Linux specific issue
or perhaps specific to my system?
*Context*: self-compiled today master under Linux Mint 17.3, Qt 5.8, Qt
Creator 4.2.1
*Description*: the programme crashes with a segmentation fault when the
"exec()" method is called for many of the dialogue boxes. For instance:
*Steps*:
1) Start MuseScore
2) Select menu item "File | Open..."
50 matches
Mail list logo
