MIDI problems on Mojave.

[John Helly]

Confer:

https://music.stackexchange.com/questions/79409/error-initializing-coremidi-starting-logic-pro-x-on-mojave

I discovered this problem because I use LogicX also.  I'll check it out
on Catalina.

J.

On 12/28/19 13:29, Davide Liessi wrote:
> Il giorno sab 28 dic 2019 alle ore 21:54 John Helly
>  ha scritto:
>> 1. Audio MIDI Setup.app
> Are you sure this step is necessary?
> As far as I understand it should not be.
>
>> I have a bunch of macs and could help with testing; if that's useful.
> Thanks for the offer: it might indeed be very useful, I'll keep it in mind.
>
> Best wishes.
> Davide

-- 

University of Hawaii, Maui College / Mobile 760.840.8660

Re: QtWebEngine vs. Ubuntu 16.04

[mason]

On 12/29, Simon Albrecht wrote:
> In case you have an immediate idea why the machine might fail to boot
> into a live USB stick, please let me know—I’m going to try enabling USB
> legacy support in BIOS right now…

Was the USB not detected in the boot menu at all, or was it detected but
failed at some point after selecting it?


signature.asc
Description: PGP signature

Re: QtWebEngine vs. Ubuntu 16.04

[Simon Albrecht]

On 28.12.19 20:00, ma...@masonhock.com wrote:

On 12/28, Simon Albrecht wrote:

I want to spend as little time as possible on maintaining/upgrading
the OS. So I’m reluctant to ditch 16.04 just yet. Should I bite the
bullet and take the time to install 18.04?

18.04 has been out long enough that major bugs should have been worked
out by now.  Do you mostly stick to packages in the repo, or do you
often install third party packages?  The distro I use is Ubuntu-based,
and when I recently upgraded from 16.04 to 18.04 the only problems I ran
into were related to packages I had compiled from source and needed to
recompile against the upgraded system libraries.  You may also run into
issues if you have many PPAs added.  Otherwise, the upgrade should be
pretty smooth.


Does it make sense to skip 18 and wait for 20.04 in April?

I think for the smoothest upgrade process, upgrade to 18.04 and resolve
any issues that arise first, and then upgrade to 20.04 and resolve any
new issues.  The more things break at once, the harder it will be to
troubleshoot them.  You might also want to wait until 20.04 has been out
for a few months before you upgrade from 18.04 to 20.04.



Hi Mason,

thanks for the reply. I have learned from painful experience that it 
seems better to just reinstall the OS completely, avoiding any issues 
with the upgrade, and restore user data from backup. I have made all 
preparations for that and am trying to do it (freshly install 18.04).


In case you have an immediate idea why the machine might fail to boot 
into a live USB stick, please let me know—I’m going to try enabling USB 
legacy support in BIOS right now…


Best, Simon

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[Stanton Sanderson]

> On Dec 28, 2019, at 5:15 PM, Stanton Sanderson  
>> 
>> What is the behaviour you are observing?
> 
> Away from my machine. Will report ASAP.

Davide,

As you stated, the edited file is temporary and must be saved first to replace 
an existing pdf. Sorry for the noise.

Stan

Re: LilyJSSVG

[mason]

On 12/29, Paolo Prete wrote:
> this is a first TEST pre-beta-beta (etc. etc.) version of a graphic editor
> entirely in Javascript and generated by Lilypond itself. Made mainly for
> fun in my spare time.
> This GUI editor extends the functionality that I had experimented with the
> snippet published a few days ago for the tuning of curves through the mouse
> 
> https://github.com/paolo-prete/LilyJSSVG

Very cool!  I'm excited to try it.

Mason


signature.asc
Description: PGP signature

LilyJSSVG

[Paolo Prete]

Hello to all,

this is a first TEST pre-beta-beta (etc. etc.) version of a graphic editor
entirely in Javascript and generated by Lilypond itself. Made mainly for
fun in my spare time.
This GUI editor extends the functionality that I had experimented with the
snippet published a few days ago for the tuning of curves through the mouse

https://github.com/paolo-prete/LilyJSSVG

At the moment, in addition to the tuning of curves and beams, it is
possible to position texts, dynamics and articulations. The code is
designed to be easily extended, in order to add other objects to be
positioned, in addition to the ones mentioned above: I created a template
and a javascript API that allows this. For now, however, I still need to
test what has been implemented before adding more features.

Unlike the previous script, there is no need for copy and paste: the editor
offers a textarea that is automatically updated following mouse actions,
plus a button for compiling .ly files.

You can make any changes you want. Save / compile and go on modifying: the
functions requested by Urs have therefore been implemented.

It should be simple to use (a mini how-to is on the project's Github
homepage and in the example .ly file).

Everything is ready to be tried.
Please use version 2.19.83 for testing. At the moment I cannot provide
support for other versions.
Furthermore, in order to allow the editor to compile the Lilypond files, I
created a Python script which is also included in the project, and which
communicates with the editor by executing the compile command after
pressing the "compile" button. This script has been tested on Linux, but
should be compatible with other operating systems.
Finally: everything has been tested on Firefox and Chrome browsers: I do
not guarantee operation on other browsers, for now.

Of course, I need your help to continue all this. Thanks to everyone who
helped me with the Scheme part: now I need new support, because in the next
weeks I won't have much time.

In particular I need a person who does code cleaning for both Javascript
and Scheme. But above all, there is a need to test all this as much as
possible. Only in this way this project will have a future. If this works,
the next feature will be adding point-and-click.

And if this works, I would be glad if it could appear in openlilylib
project (waiting for Urs' feedback)

Best,
P

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[Stanton Sanderson]

Stan



> On Dec 28, 2019, at 3:45 PM, Davide Liessi  wrote:
> 
> What is the behaviour you are observing?

Away from my machine. Will report ASAP.

Re: Lyrics on rest question

[Aaron Hill]

On 2019-12-28 2:39 pm, Jacques Menu wrote:

How can the « "Syll.3" » lyric be placed under the eigth rest at the
beginning of measure 3 to obtain the same result with Lily as with the
others?


A couple options I can think of:

1) Hidden pitch in the \lyricsto voice context; place the rest in a 
simultaneous voice.

2) Use \lyricsto with a NullVoice that has the timing you want.
3) Use explicit durations in the Lyrics; do not use \lyricsto.


-- Aaron Hill

Re: Frescobaldi 3.1 Successes (happy to report)

[John Helly]

Seems to be. I just verified it a couple of times on Mojave.  No sound
output without doing it first.  No MIDI events show in the flashing
green light on Qsynth unless doing it first.
J.

On 12/28/19 13:29, Davide Liessi wrote:
> Il giorno sab 28 dic 2019 alle ore 21:54 John Helly
>  ha scritto:
>> 1. Audio MIDI Setup.app
> Are you sure this step is necessary?
> As far as I understand it should not be.
>
>> I have a bunch of macs and could help with testing; if that's useful.
> Thanks for the offer: it might indeed be very useful, I'll keep it in mind.
>
> Best wishes.
> Davide

-- 

University of Hawaii, Maui College / Mobile 760.840.8660

Re: ANN: Frescobaldi 3.1 has been released!

[Tim McNamara]

> On Dec 28, 2019, at 3:22 PM, Davide Liessi  wrote:
> 
> Il giorno sab 28 dic 2019 alle ore 20:01 Tim McNamara
>  ha scritto:
>> I downloaded the .dmg and installed on Catalina 10.15.1.  The app crashes on 
>> launch each time.  I have a log file for this which is attached as a PDF, as 
>> a non-programmer it’s gobbledygook to me.
> 
> Can you try running it again and checking the error messages in the
> Console application when Frescobaldi crashes?

That was what I attached to my previous e-mail, unless there is something 
different you are looking for.

Lyrics on rest question

[Jacques Menu]

Hello folks,

When converting the attached MusicXML file, extracted from the Echigo Jishi 
example, with musicxml2ly, I obtain a LilyPond file (simplified here) 
containing:


%%%
\version "2.19.83"
% automatically converted by musicxml2ly from SyllableOnRest_musicxml2ly.xml


\header {
  title =  "Syllable on rest"
}


PartPOneVoiceOne =  \relative e' {
  \clef "treble" \key c \major \time 2/4 | % 1
  \stemUp e4. ^\markup{ \bold {Allegro} } r8 | % 2
  \stemUp d8 -\mf \stemUp d4 \stemUp e8 \break | % 3
  r8 \stemUp e8 [ \stemUp f8 \stemUp a8 ]
}

PartPOneVoiceOneLyricsOne =  \lyricmode {
  \set ignoreMelismata = ##t
  \skip1 \skip1 "Syll.1" "Syll.2" "Syll.3" "Syll.4" "Syll.5"
  "Syll.6"
}


% The score definition
\score {
  <<

\new Staff
<<

  \context Staff <<
\mergeDifferentlyDottedOn\mergeDifferentlyHeadedOn
\context Voice = "PartPOneVoiceOne" {  \PartPOneVoiceOne }
\new Lyrics \lyricsto "PartPOneVoiceOne" { \set stanza = "1." 
\PartPOneVoiceOneLyricsOne }
  >>
>>

  >>
  \layout {}
  % To create MIDI output, uncomment the following line:
  %  \midi {\tempo 4 = 92 }
}
%%%

which produces:




while MusicScore, Finale 2014 and Sibelius 7.1.3 all produce:




How can the « "Syll.3" » lyric be placed under the eigth rest at the beginning 
of measure 3 to obtain the same result with Lily as with the others?

Thanks for your help!

JM




SyllableOnRest.xml
Description: XML document

Re: Question about GPL license

[mason]

On 12/28, Paolo Prete wrote:
> In these days, I worked at my Javascript script which allows to place
> Lilypond's grobs with the mouse. I think I'm ready to share a test
> version on Github.  From what I see, the only license that I can use
> for it is GPLv3.

In order to make your code compatible with Lilypond (and potentially
Frescobaldi), then it should be under GPLv3 or another
GPLv3-compatible[1] license.  If you choose another GPLv3 compatible
license, then your code can be distributed alone under the terms of your
chosen license, or alongside Lilypond and/or Frescobaldi under the terms
of the GPLv3.

> I just saw this article about the bad sides of this license:
> 
> https://fodina.de/en/2019/lilypond-snippets-and-the-gpl/

This is unfounded FUD.  You can ignore it, or search the archives for
prior discussion of it.

Mason

[1] https://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses


signature.asc
Description: PGP signature

Question about GPL license

[Paolo Prete]

Hello all,

In these days, I worked at my Javascript script which allows to place
Lilypond's grobs with the mouse. I think I'm ready to share a test version
on Github.
>From what I see, the only license that I can use for it is GPLv3.

Can you confirm that?

I just saw this article about the bad sides of this license:

https://fodina.de/en/2019/lilypond-snippets-and-the-gpl/

Again: it seems that GPLv3 is the only choice, but if you are aware of any
other possible option, please let me know.

Best,
Paolo

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[Davide Liessi]

Il giorno sab 28 dic 2019 alle ore 22:30 Stanton Sanderson
 ha scritto:
> Another behavior noted (change from previous versions): the new pdf generated 
> when editing an existing file does not replace the old pdf.

I cannot reproduce this.
If I change an existing document, save it and compile it, the new PDF
replaces the old one.
If I change an existing document, DO NOT save it and compile it, the
viewer shows the new PDF, which is saved in a temporary location, and
the old PDF is not replaced.
This is the usual behaviour of Frescobaldi.

It would be a bug if after changing, saving and compiling an existing
document the new PDF did not replace the old one.

What is the behaviour you are observing?

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[Davide Liessi]

On 12/28/19 13:11, Stanton Sanderson wrote:
> An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the 
> following error message reported:
>>  ImportError: Bad magic number in 
>> /Applications/Frescobaldi.app/Contents/Resources/site.pyc

Il giorno sab 28 dic 2019 alle ore 22:24 John Helly
 ha scritto:
> I confirm same behavior.

I can reproduce the issue.
Issue opened at https://github.com/frescobaldi/frescobaldi/issues/1232.
I will investigate it.

Best wishes.
Davide

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[Stanton Sanderson]

> On Dec 28, 2019, at 3:23 PM, John Helly  wrote:
> 
> I confirm same behavior.
> J.
> 
> On 12/28/19 13:11, Stanton Sanderson wrote:
>> (Mac OS Mojave (current), Frescobaldi 3.1 from dmg)

Another behavior noted (change from previous versions): the new pdf generated 
when editing an existing file does not replace the old pdf. 

Re: Frescobaldi 3.1 Successes (happy to report)

[Davide Liessi]

Il giorno sab 28 dic 2019 alle ore 21:54 John Helly
 ha scritto:
> 1. Audio MIDI Setup.app

Are you sure this step is necessary?
As far as I understand it should not be.

> I have a bunch of macs and could help with testing; if that's useful.

Thanks for the offer: it might indeed be very useful, I'll keep it in mind.

Best wishes.
Davide

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[John Helly]

I confirm same behavior.
J.

On 12/28/19 13:11, Stanton Sanderson wrote:
> (Mac OS Mojave (current), Frescobaldi 3.1 from dmg)
>
> An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the 
> following error message reported:
>
>>  ImportError: Bad magic number in 
>> /Applications/Frescobaldi.app/Contents/Resources/site.pyc
>>
>>
>> The document has not been changed.
>>
> Stan

-- 

University of Hawaii, Maui College / Mobile 760.840.8660

Re: ANN: Frescobaldi 3.1 has been released!

[Davide Liessi]

Il giorno sab 28 dic 2019 alle ore 20:01 Tim McNamara
 ha scritto:
> I downloaded the .dmg and installed on Catalina 10.15.1.  The app crashes on 
> launch each time.  I have a log file for this which is attached as a PDF, as 
> a non-programmer it’s gobbledygook to me.

Can you try running it again and checking the error messages in the
Console application when Frescobaldi crashes?

Thanks.
Davide

Re: [Frescobaldi] Frescobaldi 3.1 Successes (happy to report)

[Stanton Sanderson]

(Mac OS Mojave (current), Frescobaldi 3.1 from dmg)

An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the 
following error message reported:

>  ImportError: Bad magic number in 
> /Applications/Frescobaldi.app/Contents/Resources/site.pyc
> 
> 
> The document has not been changed.
> 

Stan

Frescobaldi 3.1 Successes (happy to report)

[John Helly]

Aloha.

 1. Tried unsuccessfully to build from scratch on 10.14.6 (Mojave) and
ran into a series of python dependency problems that I haven't fully
solved.
 2. Downloaded the 3.1 dmg and successfullly run it on 10.14.6 (Mojave)
and 10.15.2 (Catalina).  Nice job.
 3. Tested on 10.14.6 with Qsynth and works fine but dependent on the
following startup order (as before):
 1. Audio MIDI Setup.app
 2. Qsynth + soundfont specification in Qsynth setup (also need to
turn up gain knob)
 3. Frescobaldi 3.1.app

Thanks for the great work.  I have a bunch of macs and could help with
testing; if that's useful.

J.

-- 

University of Hawaii, Maui College / Mobile 760.840.8660

Re: QtWebEngine vs. Ubuntu 16.04

[mason]

On 12/28, Simon Albrecht wrote:
> I want to spend as little time as possible on maintaining/upgrading
> the OS. So I’m reluctant to ditch 16.04 just yet. Should I bite the
> bullet and take the time to install 18.04?

18.04 has been out long enough that major bugs should have been worked
out by now.  Do you mostly stick to packages in the repo, or do you
often install third party packages?  The distro I use is Ubuntu-based,
and when I recently upgraded from 16.04 to 18.04 the only problems I ran
into were related to packages I had compiled from source and needed to
recompile against the upgraded system libraries.  You may also run into
issues if you have many PPAs added.  Otherwise, the upgrade should be
pretty smooth.

> Does it make sense to skip 18 and wait for 20.04 in April?

I think for the smoothest upgrade process, upgrade to 18.04 and resolve
any issues that arise first, and then upgrade to 20.04 and resolve any
new issues.  The more things break at once, the harder it will be to
troubleshoot them.  You might also want to wait until 20.04 has been out
for a few months before you upgrade from 18.04 to 20.04.

> If I should try within 16.04, here’s some sites I checked out on a
> brief search:
> 
>  –
> the ppa mentioned there doesn’t exist anymore
> 
> – the answers here seem to suggest setting up a whole different route
> of installing Qt, which seems like overkill
>  – this also seems like
> overkill if all I need is the ‘subpackage’ QtWebEngine

Mixing and matching packages from different Qt versions is likely to get
messy.  You might try this PPA,[1] which installs newer Qt versions to
/opt without conflicting with the version already on your system.  I
haven't tested it, but it may work for Frescobaldi.

Mason

[1] https://launchpad.net/~beineri


signature.asc
Description: PGP signature

Re: ANN: Frescobaldi 3.1 has been released!

[mason]

Sorry, forgot to copy the list.

On 12/28, ma...@masonhock.com wrote:
> On 12/28, Urs Liska wrote:
> > Ubuntu 16.04 is a LTS release with (IIRC) five years of support. So it
> > is not unreasonable for someone to use it. However, we (Frescobaldi)
> > seem to have been hit by this five-year term since we're dealing with
> > a change in the Qt framework that has phased out support for a module
> > over (again, IIRC) 2-3 years. So all *current* Linux distributions
> > ship with a Qt version that only includes QtWebEngine and not QtWebKit
> > anymore. There has been a range of Qt versions including both.
> >
> > The question is whether a project like Frescobaldi can reasonably be
> > expected to actively support such an old OS, even if it's LTS. I'd
> > assume that lTS guarantees you security patches but not that every new
> > software will run.
> 
> Right, LTS means continued security updates (only for packages in the
> Main repository, in Ubuntu's case), but three years into the release
> users cannot expect to run bleeding edge software without ever running
> into dependency issues.  It seems that most developers make an effort to
> support Ubuntu's current stable release (although Kdenlive does not,
> support Bionic, also due to Qt dependencies), but it is common for large
> projects not to support the previous stable release.
> 
> > Before upgrading to a newer OS it might be an option to use a current
> > Qt/PyQt downloaded or compiled from somewhere. @Simon you could do us
> > a huge favor by exploring that possibility and providing information
> > about it for the Wiki.
> 
> I have not tested this, but these PPAs[1] install newer versions of Qt
> to /opt, so that they do not conflict with the version of Qt already on
> the system.  This may be sufficient for Frescobaldi.
> 
> Mason
> 
> [1] https://launchpad.net/~beineri




signature.asc
Description: PGP signature

Re: Overriding Script symbol with markup

[Kieren MacMillan]

Hi Daniel,

> What property of Script do I need to override in order to replace the symbol 
> with markup?

Here’s an example I have in my include code:

\version "2.19.83"

pocoAccent =
  -\tweak stencil #ly:text-interface::print
  -\tweak self-alignment-X #-0.5
  -\tweak text \markup \override #'(baseline-skip . 0.5) \center-column { 
\normal-text \italic \fontsize #-1 "poco" \musicglyph #"scripts.sforzato" }
  -\accent

{ c'1^\pocoAccent }

Hope that helps!
Kieren.


Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info

Overriding Script symbol with markup

[Daniel Rosen]

What property of Script do I need to override in order to replace the symbol 
with markup?

Example:

{ \override Script.? = \markup { foo }
  c'1\trill }

would print "foo" instead of the trill symbol.

DR

Re: ANN: Frescobaldi 3.1 has been released!

[Urs Liska]

Am 28.12.19 um 14:08 schrieb Ralph Palmer:

Hi, Urs -

On Sat, Dec 28, 2019 at 3:47 AM Urs Liska > wrote:


Ubuntu 16.04 is a LTS release with (IIRC) five years of support.
So it
is not unreasonable for someone to use it. However, we (Frescobaldi)
seem to have been hit by this five-year term since we're dealing
with a
change in the Qt framework that has phased out support for a
module over
(again, IIRC) 2-3 years. So all *current* Linux distributions ship
with
a Qt version that only includes QtWebEngine and not QtWebKit anymore.
There has been a range of Qt versions including both.

The question is whether a project like Frescobaldi can reasonably be
expected to actively support such an old OS, even if it's LTS. I'd
assume that lTS guarantees you security patches but not that every
new
software will run.

Before upgrading to a newer OS it might be an option to use a current
Qt/PyQt downloaded or compiled from somewhere. @Simon you could do
us a
huge favor by exploring that possibility and providing information
about
it for the Wiki.
In addition it would be good to have a list of distributions that
include the "new" module, both modules, or only the "old" modules
(i.e.
won't work with Frescobaldi 3.1).

Urs


As I've said before, I'm a novice at command line Linux, but I'm 
attaching a screenshot of my command line search (locate) for 
QtWebEngine and QtWebKit. I'm running Ubuntu 18.04.3 LTS.


Hope this helps,



You should not "locate" package files but use "apt" (the package 
manager) for that (as Knute has also pointed out).


As I tried to say earlier you can simply follow the instructions on 
Frescobaldi's Wiki:


|# install dependencies sudo apt install python3-pyqt5 
python3-pyqt5.qtsvg python3-pyqt5.qtwebengine python3-poppler-qt5 git |


Then clone the repositories:

|# clone repositories mkdir ~/git cd ~/git git clone 
https://github.com/wbsoft/frescobaldi git clone 
https://github.com/wbsoft/python-ly |


(you may change the directories if you want)

and finally create a wrapper script to properly start your Git-Frescobaldi:

|# create wrapper script # (make sure ~/bin exists and is in the search 
path (or adapt)) echo "#!/bin/bash" > ~/bin/frescobaldi echo 
"PYTHONPATH=~/git/python-ly:$PYTHONPATH python3 
~/git/frescobaldi/frescobaldi $@" >> ~/bin/frescobaldi chmod +x 
~/bin/frescobaldi # check invocation through command line (from any 
working directory) frescobaldi |


HTH
Urs



Ralph

--
Ralph Palmer
Brattleboro, VT
USA
(he, him, his)
palmer.r.vio...@gmail.com 

Re: ANN: Frescobaldi 3.1 has been released!

[Knute Snortum]

I have my own question.  In the INSTALL document it states that
Poppler 0.82.0 or greater is required.  On my Ubuntu 19.10 system I
have only version 0.80.0 and I'm having trouble building it from
source.  Also, my Poppler seem to be tied to python3-poppler-qt which
is at 0.24.2-3build5.

So will building Poppler by itself mess up my system?  What will
happen with Poppler below its required version?

---
Knute Snortum
(via Gmail)

Re: ANN: Frescobaldi 3.1 has been released!

[Colin Campbell]

On 2019-12-28 1:11 a.m., Andrew Bernard wrote:

Thank you Wilbert and the team.

With an existing Ubuntu 19.04 Frescobaldi 3.0.0 installation, all I
had to do was install from the tarball and add the following:

apt install python3-pyqt5.qtwebengine



Running Fedora 31 and an existing 3.0.0 Frescobaldi. Like Andrew, all I 
needed to do was force the install of


python3-pyqt5.qtwebengine


Cheers,

Colin

--
A good juggler can always find work.
- attributed to L. Pacioli (1445 - 1517)

Re: ANN: Frescobaldi 3.1 has been released!

[Knute Snortum]

On Sat, Dec 28, 2019 at 5:08 AM Ralph Palmer  wrote:

> As I've said before, I'm a novice at command line Linux, but I'm attaching a 
> screenshot of my command line search (locate) for QtWebEngine and QtWebKit. 
> I'm running Ubuntu 18.04.3 LTS.
>
> Hope this helps,
>
> Ralph

Try this.  First type in

sudo apt update

Enter your password.  Then type in

apt search qtwebengine

You should be able to scroll your output with a mouse.  If not, try typing

apt search qtwebengine | less

Now you can page up and down.  Look for something like
"python3-pyqt5.qtwebengine". Type "q" to exit.

If you found it, then type

sudo apt install python3-pyqt5.qtwebengine

---
Knute Snortum
(via Gmail)

Re: ANN: Frescobaldi 3.1 has been released! How to install with windows?

[yming tsang]

Hi, Wilbert:

Thank you for the new version of Frecobalsi v3.1.

I am a window 10 user, I have a hard time installing the new frecobaldi v3.1.
I download the frecobaldi 3.1.tar.gz and extract it to a folder. Then I click 
on setup .py  NOTHING happen.
I need help to install.

Thank again,
Ming

Sent from Mail for Windows 10

Re: ANN: Frescobaldi 3.1 has been released! How to install with windows?

[Bernhard Kleine]

What to do to install Frescobaldi 3.1 on windows?

Kind regards

Bernhard

Am 27.12.2019 um 11:20 schrieb Wilbert Berendsen:
> Dear Friends,
>
> Frescobaldi 3.1 has been released! There are many new features.
>
> Most notably:
>
> - A new Fonts dialog to select fonts for text, and with more recent
>   LilyPond versions, also for music.
>
> - The Music View is completely rewritten under the hood. New
>   possiblities:
>
>   * Copy selected music to PDF, SVG or EPS in addition to PNG and JPG.
>
>   * Zoom much deeper than ever before: thanks to tile-based rendering
> the Music View can zoom in virtually unlimited.
>
>   * New layout modes: horizontal/vertical, continuous/non continuous,
> rotation, etc.
>
> And there are many other little feature improvements and bug fixes.
> Lastly, many improvements under the hood pave the way for new exiting
> future possibilities, such as good multicore compile support, and
> support for much more file formats in the Manuscript viewer etc.
>
> I am very grateful to many co-developers that now contribute on a
> regular basis: Urs Liska, Peter Bjuhr, and many others.
>
> See all changes in the ChangeLog:
> https://github.com/frescobaldi/frescobaldi/blob/master/ChangeLog
>
> Download the source tarball at:
> https://github.com/frescobaldi/frescobaldi/releases
>
> Please give packagers some time to prepare Windows/MacOSX installers,
> they will be announced when ready.
>
> Note that Frescobaldi is now part of the GitHub organisation with the
> same name :-) to reflect that I'm certainly not the only one managing
> this project :-)
>
> Note to distributors and users of a git checkout: the MO (Message
> Object) files with the translations are not in git anymore, but they are
> built manually before packaging a source tarball.See INSTALL. When
> installing from the source tarball it is not needed to build the MO
> files.
>
> Other notes:
>
> - A recent version of the poppler library is needed to make vector
>   graphics drawing and copying in the Music View work well.
>
> - Frescobaldi does not use QtWebkit anymore, but instead now depends on
>   QtWebEngine and its related modules.
>
> Thanks to ALL the translators and contributors!
> Enjoy!
> Merry Christmas and happy new year!
>
> |_|  .  |) |) \./
> | | /-\ |  |   |
> ' ''   ''  '   '
>  . .  _ |  |
>  |\| |- \/\/
>  ' '  ~
> \./  _  .  |)
>  |  |- /-\ |\
>  '   ~'   '' '  
>
>
-- 
spitzhalde9
D-79853 lenzkirch
bernhard.kle...@gmx.net
www.b-kleine.com, www.urseetal.net
Ich darf auch auf mein neues Buch "Falter in Lenzkirch" aufmerksam machen 
(Infos bei mir)
-
thunderbird mit enigmail
GPG schlüssel: D5257409
fingerprint:
08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09




signature.asc
Description: OpenPGP digital signature

Re: [Frescobaldi] Re: ANN: Frescobaldi 3.1 has been released!

[Stanton Sanderson]

Wilbert & Davide,

Sincere thanks for the wonderful update and rapid port to Mac. I am in awe!

Happy New Year to you and your families.

Stan
Illinois, USA

Re: ANN: Frescobaldi 3.1 has been released!

[Ralph Palmer]

Hi, Urs -

On Sat, Dec 28, 2019 at 3:47 AM Urs Liska  wrote:

> Ubuntu 16.04 is a LTS release with (IIRC) five years of support. So it
> is not unreasonable for someone to use it. However, we (Frescobaldi)
> seem to have been hit by this five-year term since we're dealing with a
> change in the Qt framework that has phased out support for a module over
> (again, IIRC) 2-3 years. So all *current* Linux distributions ship with
> a Qt version that only includes QtWebEngine and not QtWebKit anymore.
> There has been a range of Qt versions including both.
>
> The question is whether a project like Frescobaldi can reasonably be
> expected to actively support such an old OS, even if it's LTS. I'd
> assume that lTS guarantees you security patches but not that every new
> software will run.
>
> Before upgrading to a newer OS it might be an option to use a current
> Qt/PyQt downloaded or compiled from somewhere. @Simon you could do us a
> huge favor by exploring that possibility and providing information about
> it for the Wiki.
> In addition it would be good to have a list of distributions that
> include the "new" module, both modules, or only the "old" modules (i.e.
> won't work with Frescobaldi 3.1).
>
> Urs
>

As I've said before, I'm a novice at command line Linux, but I'm attaching
a screenshot of my command line search (locate) for QtWebEngine and
QtWebKit. I'm running Ubuntu 18.04.3 LTS.

Hope this helps,

Ralph

-- 
Ralph Palmer
Brattleboro, VT
USA
(he, him, his)
palmer.r.vio...@gmail.com

Re: QtWebEngine vs. Ubuntu 16.04

[Urs Liska]

I'd expect it's not possible to update just QtWebEngine but the complete Qt 
framework. I imagine that would involve two installations (Qt and PyQt) and 
then make Frescobaldi use it. Probably one wouldn't want *every* app to use 
that "alien" package, though.

Urs


Am 28. Dezember 2019 11:44:36 MEZ schrieb Simon Albrecht 
:
>Hi everybody,
>
>On 28.12.19 09:46, Urs Liska wrote:
>> Before upgrading to a newer OS it might be an option to use a current
>
>> Qt/PyQt downloaded or compiled from somewhere. @Simon you could do us
>
>> a huge favor by exploring that possibility and providing information 
>> about it for the Wiki. 
>
>This is sort of a two part question, since I’m unsure whether to just 
>upgrade (i.e. reinstall) the OS or figure out installing QtWebEngine in
>
>16.04.
>
>I want to spend as little time as possible on maintaining/upgrading the
>
>OS. So I’m reluctant to ditch 16.04 just yet. Should I bite the bullet 
>and take the time to install 18.04? Does it make sense to skip 18 and 
>wait for 20.04 in April?
>
>If I should try within 16.04, here’s some sites I checked out on a
>brief 
>search:
>
> – 
>the ppa mentioned there doesn’t exist anymore
>
>
>– the answers here seem to suggest setting up a whole different route
>of 
>installing Qt, which seems like overkill
> – this also seems like 
>overkill if all I need is the ‘subpackage’ QtWebEngine
>
>I’m sorry this is somewhat helpless on my part—I do these things far
>too 
>rarely to get by sensibly…
>
>Best, Simon

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Re: QtWebEngine vs. Ubuntu 16.04

[Simon Albrecht]

Hi everybody,

On 28.12.19 09:46, Urs Liska wrote:
Before upgrading to a newer OS it might be an option to use a current 
Qt/PyQt downloaded or compiled from somewhere. @Simon you could do us 
a huge favor by exploring that possibility and providing information 
about it for the Wiki. 


This is sort of a two part question, since I’m unsure whether to just 
upgrade (i.e. reinstall) the OS or figure out installing QtWebEngine in 
16.04.


I want to spend as little time as possible on maintaining/upgrading the 
OS. So I’m reluctant to ditch 16.04 just yet. Should I bite the bullet 
and take the time to install 18.04? Does it make sense to skip 18 and 
wait for 20.04 in April?


If I should try within 16.04, here’s some sites I checked out on a brief 
search:


 – 
the ppa mentioned there doesn’t exist anymore
 
– the answers here seem to suggest setting up a whole different route of 
installing Qt, which seems like overkill
 – this also seems like 
overkill if all I need is the ‘subpackage’ QtWebEngine


I’m sorry this is somewhat helpless on my part—I do these things far too 
rarely to get by sensibly…


Best, Simon

Re: ANN: Frescobaldi 3.1 has been released!

[Davide Liessi]

Il giorno sab 28 dic 2019 alle ore 10:19 Jacques Menu
 ha scritto:
> I’ve switched to it on Mac OS 10.14.6 (Mojave, which still allows 32bit apps 
> to be run), and it runs fine.

Good to know!

Anyway, the application bundle contains only 64 bit code.

Best wishes.
Davide

Re: ANN: Frescobaldi 3.1 has been released!

[Jacques Menu]

Hello Wilbert and Davide,

Thanks a lot for the great job issuing this Frescobaldi 3.1 release!

I’ve switched to it on Mac OS 10.14.6 (Mojave, which still allows 32bit apps to 
be run), and it runs fine.
Will let you know should any issue arise.

A happy new year 2020 to all lilyponders!

JM

> Le 28 déc. 2019 à 10:00, Davide Liessi  a écrit :
> 
> Il giorno ven 27 dic 2019 alle ore 11:21 Wilbert Berendsen
>  ha scritto:
>> Please give packagers some time to prepare Windows/MacOSX installers,
>> they will be announced when ready.
> 
> The Mac installer (DMG containing application bundle) is now available at
> https://github.com/frescobaldi/frescobaldi/releases
> 
> The application bundle should work on macOS 10.12 Sierra and later:
> otherwise, please report the failure (either with a GitHub issue or by
> email to me).
> It might work also on previous versions of macOS: if it does, please
> let us know (either with a GitHub issue or by email to me).
> 
> Merry Christmas and a happy new year to you all!
> Davide
> 

Re: ANN: Frescobaldi 3.1 has been released!

[Davide Liessi]

Il giorno ven 27 dic 2019 alle ore 11:21 Wilbert Berendsen
 ha scritto:
> Please give packagers some time to prepare Windows/MacOSX installers,
> they will be announced when ready.

The Mac installer (DMG containing application bundle) is now available at
https://github.com/frescobaldi/frescobaldi/releases

The application bundle should work on macOS 10.12 Sierra and later:
otherwise, please report the failure (either with a GitHub issue or by
email to me).
It might work also on previous versions of macOS: if it does, please
let us know (either with a GitHub issue or by email to me).

Merry Christmas and a happy new year to you all!
Davide

Re: ANN: Frescobaldi 3.1 has been released!

[Urs Liska]

Am 28.12.19 um 01:01 schrieb ma...@masonhock.com:

On 12/28, Simon Albrecht wrote:

I happen to have a little problem with that as well; here on my Ubuntu
16.04 machine neither apt nor synaptic can find any variation of
qtwebengine5. There are several variations of webkit or so, but that’s
probably something different, right? What can I do?

The first version of Ubuntu to package qtwebengine was 18.04 Bionic.[1]
Is upgrading an option for you, or do you need to stick with 16.04?



Ubuntu 16.04 is a LTS release with (IIRC) five years of support. So it 
is not unreasonable for someone to use it. However, we (Frescobaldi) 
seem to have been hit by this five-year term since we're dealing with a 
change in the Qt framework that has phased out support for a module over 
(again, IIRC) 2-3 years. So all *current* Linux distributions ship with 
a Qt version that only includes QtWebEngine and not QtWebKit anymore. 
There has been a range of Qt versions including both.


The question is whether a project like Frescobaldi can reasonably be 
expected to actively support such an old OS, even if it's LTS. I'd 
assume that lTS guarantees you security patches but not that every new 
software will run.


Before upgrading to a newer OS it might be an option to use a current 
Qt/PyQt downloaded or compiled from somewhere. @Simon you could do us a 
huge favor by exploring that possibility and providing information about 
it for the Wiki.
In addition it would be good to have a list of distributions that 
include the "new" module, both modules, or only the "old" modules (i.e. 
won't work with Frescobaldi 3.1).


Urs



Mason

[1]
https://packages.ubuntu.com/search?keywords=qtwebengine=sourcenames

Re: ANN: Frescobaldi 3.1 has been released!

[Andrew Bernard]

Thank you Wilbert and the team.

With an existing Ubuntu 19.04 Frescobaldi 3.0.0 installation, all I
had to do was install from the tarball and add the following:

apt install python3-pyqt5.qtwebengine

since the majority of the dependencies I already have in place. I hope
this tiny sliver of information may be helpful to some.

All works fine.

Andrew

On Fri, 27 Dec 2019 at 21:21, Wilbert Berendsen  wrote:

> Frescobaldi 3.1 has been released! There are many new features.