It seems that Score does not work well with the VideoJS player. When the TimedMediaHandler extension is enabled and there is another media element on a page, TMH tries to apply VideoJS to Score elements that have sound="1" but results in a disabled player with sound source File:Undefined. See phabricator:T245377. For the time being I'm forcing the Kaltura player which plays nicely in all circumstances ($wgTmhWebPlayer = "mwembed";).
Extension talk:Score/Flow
phab:T306836 and phab:T306836 have been fixed, and I think with phab:T248418 VideoJS is now the default player on all wikis.
This situation is still not fixed, and unfortunately the Kaltura player has now been removed so that is no longer an option. Here is the situation:
1) When there are only Score audio elements on a page there is no problem, the VideoJS player is not invoked only the native browser player is used.
2) When there are only non-Score audio elements on a page there is no problem, the VideoJS player is invoked and the audio elements use the VideoJS player
3) When there are both Score audio elements and non-Score audio elements on a page, the VideoJS player is invoked by the non-Score audio elements and applied to all audio elements on the page including the Score audio elements, however the Score audio elements do not support VideoJS.
This should demonstrate the issue:
Non Score audio element:
Score audio element:
![{ \new PianoStaff << \new Staff \relative c'' { \set Staff.midiInstrument = #"violin" \clef treble \tempo 8 = 126 \time 3/16 r16 <d c a fis d>\f-! r16\fermata | \time 2/16 r <d c a fis d>-! \time 3/16 r <d c a fis d>8-! | r16 <d c a fis d>8-! | \time 2/8 <d c a fis>16-! <e c bes g>->-![ <cis b aes f>-! <c a fis ees>-!] } \new Staff \relative c { \set Staff.midiInstrument = #"violin" \clef bass \time 3/16 d,16-! <bes'' ees,>-! r\fermata | \time 2/16 <d,, d,>-! <bes'' ees,>-! | \time 3/16 d16-! <ees cis>8-! | r16 <ees cis>8-! | \time 2/8 d16\sf-! <ees cis>-!->[ <d c>-! <d c>-!] } >> }](http://upload.wikimedia.org/score/n/m/nmvsya0ea7s21sms50juo24783ltqri/nmvsya0e.png)
hmmm funny, it seems that VideoJS is not being invoked on Talk pages? My example above doesn't actually show the problem, because no VideoJS player is invoked here...
I tried to recreate the same example on my User page: User:Lwangaman#Testing_Score_and_non-Score_audio_elements_together, the VideoJS player is being invoked on the non-Score audio element whereas it is not being invoked on the Score audio element, and both are still playing nicely. So I'm a bit stumped, because this is not working well on another external wiki: https://en.seminaverbi.bibleget.io/wiki/User_talk:Johnrdorazio . So I'm really not sure what the heck is going on. Why is the VideoJS getting applied to Score audio elements on the external wiki but not on Mediawiki? Is there a magic setting that needs to be set in LocalSettings to prevent VideoJS being applied to Score audio elements?
Bugs with Score and other media players were fixed in Wikipedia's wiki instances around July 2024, see phab:T295514 and phab:T363630. The TimedMediaHandler JavaScript code that "infuses" the VideoJS player into video and audio tags (replacing the native browser player) was running on Score's audio player as well, and was breaking. I think if you update the TMH extension on your wiki the behavior should fix.
I haven't seen a spec for when audio should use the native browser player versus TMH/VideoJS. I think part of the rationale for infusing the VideoJS player into audio tags is that it could have subtitles (captions) which the VideoJS player can present with its [CC] button. Comments on those two Phabricator bug reports have a lot of details.
If yes. For how long? Isn't it better to keep the documentation "clean" and then move the discontinued/removed attributes to a seperate section?
Question moved and translated comment from user 188.149.213.172 Extension talk:Score/sv.
ABC support in Score is achieved by using abc2ly, but abc2ly is imperfect: there is a lot of ABC syntax it doesn't understand. I looked at the source of Score, and the assumption that the image will be always built with Lilypond runs throughout the extension. But I think Score could be modified to support more than one rendering engine. The current workflow of: "(1) coerce the source to Lilypond, (2) use Lilypond" could be changed to "(1) given the language the score is in, find the best suitable backend and coerce the source to it, (2) use that backend". This would use abcm2ps for ABC if possible, otherwise it would use abc2ly+lilypond. Would this be a sensible change to Score?
Mediawiki 1.34
Score 0.3.0 (0f4d4c1)
Not sure if this is an issue with my server configuration or a bug in the extension, hopefully someone can clarify. My server is setup to run under the user www-data, but new directories created under images/lilypond/... when generating new scores have the owner set to root instead of www-data as I would expect. This causes the pages that render scores in the wiki to throw a error saying that its impossible to copy the files to their destination ("mwstore://score-backend/score-render/..."). I can run chown on my images directory to set owner back to www-data and the error disappears, but I want to ensure that the directories are created with the correct owner in the first place. This problem doesn't occur with normal file uploads, only directories created by Score. Any ideas/suggestions for fixing this?
I am getting no sound the extension creates the files but doesn't convert to audio. I am not getting any errors or sound.
slight correction its ready to play, it would seem fluid synth isn't doing its job and when i comment it out it breaks with no fall back. since i configured lame the files are mp3 now rather than ogg but that shouldn't be a problem.
I can add a title when using ABC notation, but I can't add it when using LilyPond. How can I add a title when using LilyPond?
Examples:
ABC notation:
LilyPond:
See the example at :en:Help:Score#Adding_lyrics
Problem solved. Thanks!
May I ask how it was solved? If I try adding a "\header { Die Moldau }" to your example here it doesn't work?
With a header:
Musical scores are temporarily disabled.
Without a header:
Musical scores are temporarily disabled.
(Actually scores are now all showing as disabled?)
Musical scores are temporarily disabled.
The Lilypond extension has been disabled for several months now. Judging by the lack of activity at phab:T257066, I wouldn't expect it to return any time soon.
Use raw="1" to add header when using LilyPond.
seems to be here an A4 paper default with lilypond, I cant change it here
https://de.wikipedia.org/wiki/Benutzer:Reiner_Stoppok/Tanzlied_aus_Poniky
or turn it even off, to make reasonable explicit line breaks.
Cheers
It looks like you aren't setting it correctly. I copied your page here and modified it slightly
using the proper page size setting commands and got this error:
| error |
|---|
Processing `.../file.ly' Parsing... .../file.ly:19:2: error: GUILE signaled an error for the expression beginning here # (set-default-paper-size = "a3 'landscape") .../file.ly:22:3: error: GUILE signaled an error for the expression beginning here # (set-paper-size = "a3 'landscape") % Seitengröße auf DIN A4 quer setzen. warning: systems run off the page due to improper paper settings, setting default values Interpreting music...[8][16][24] Preprocessing graphical objects... Interpreting music... MIDI output to `file.midi'... Finding the ideal number of pages... Fitting music on 2 or 3 pages... Drawing systems... Layout output to `file.ps'... Converting to PNG...No variable named $defaultpaper in #<module 7f7a95562b80> Unbound variable: set-paper-size fatal error: failed files: ".../file.ly" exited with status: 1 |
That, at least, looks like something is happening.
With frescobaldi it works fine with a4 landscape in your manner. But in wikpedia a # creates error messages. My version is being ignored, and defaults to A4.
Maybe we have to escape the # somehow. But which escape sign? \ is already used.
Or an wiki escape sign?
The error even write: No variable named $defaultpaper in #<module 7f7a95562b80>
or
Converting to PNG...Unbound variable: set-paper-size
I tried the same syntax on my local wiki and got the same result.
I tried using lilypond from the command line and got similar results. Although it looks like I have a bit more information:
file.ly:18:2: error: GUILE signaled an error for the expression beginning here # (set-default-paper-size = "a3 'landscape") Wrong type argument in position 2 (expecting string): #<primitive-generic =>
I forgot to remove the = from your example.
Doing that and it works on the command line. From the available sizes, I liked "ansi d" best for this piece.
Now, to figure out why it doesn't work in MW.
ok, so it looks like the Score extension adds "-dsafe=#t" which tells lilypond to disable some stuff -- like paper sizes.
The way around this (maybe) is to file a task in phabricator asking WMF to set up a jail for lilypond.
Thanks for your insight. They fear everbody compiles a Tschaikowski Piano concerto no. 1. But either they open a Kerker, (dungeon, jail), or implement a reasonable paper choice tag, like four pages output a4 landscape, that would be one side of a partitura.
Where can I ask for it?
Phabricator is where requests like this are filed. Let me know when file a request so I can watch it.
Hopefully here
https://phabricator.wikimedia.org/T161293
ist is.
Who opens the thread there and makes triage? Nobody? Me?
I've asked the Bugwrangler to help out. Also, the bug was assigned to you and it shouldn't have been.
Greetings, I am attempting to install this extension, and after following the instructions for it and shellbox as best as I could, the Score extension shows in the Special:Version page but Lilypond does not show in the "installed software" section. When I try to create a score I get a "unable to find lilypond version" error. I was wondering if anyone else had dealt with this.
Lilypond was installed through the debian package manager.
I'd like to notice that in this extension we have mistake in notation of rests. As I know the correct notation is subsequently:
...so we have equantion:
 + |
= |  |
In present MediaWiki version of LiliPond is wrong notation, because is subsequently:
So in point of MediaWiki's view it is at the moment so...:
 + |
= |  |
Could anybody correct this failure in this extentension? Thanks in advance!
If I mixed up both rests and this version of LilyPond shows correctly, then I would like to retract this Thread. I was honestly convinced that I thought right.
/bin/bash: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8) /bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8) GNU LilyPond 2.19.56
This error I get after upgrading to 1.35.4.
Where can I found some more information about this?