Comments (30)
from musescore.
from musescore.
from musescore.
Fixes bugs and regressions introduced in #5623, #5922, and #6186.
from musescore.
Issues without PRs (yet):
(Issues with) PRs:
- #5381 - Fix #295588: add Petaluma font
- #5934 - Update Bravura to 1.39
- #6034 - fix #304880: wrong beam positions when changing spatium
- #6203 - Use "Merge matching rests" in the closed score SATB and barbershop templates
- #6206- fix #298820: Can't minimize Musescore or change virtual desktop on Linux with Gnome-based desktop environments
- #6218 - fix #305069: Chord symbols attached to fret diagrams don't play back
- #6219 - fix #306750: Chord symbol alignment incorrectly forces alignment between above & below chords and across staves, fix #306751: Chord symbol alignment changes default position without reason
- #6222 - fix #306816: Crash when select Realize Chord Symbols by right clicking chord symbol with Fretboard Diagram
- #6236 - fix #306964: Crash when change the numerical value of Fretboard Diagram “Maximum shift above”
- #6239 - fix translation of barline names in barlines inspector
- #6245 - fix #306878: Retain focus for non-modal dialogs
from musescore.
- #6223 - Fix Crash Case with Empty Trailing Measure command (https://musescore.org/en/node/306807)
from musescore.
from musescore.
Still not totally clear on the criteria for what is being considered, but to me these are good candidates. They are not regressions (well, not new regressions in 3.5 anyhow) but they do address some real pain points that are easily solved. And they don't involve new strings or otherwise require new documentation, they just allow things to work that people have every right to expect to work anyhow.
- #6238 - allow Ctrl+Delete from note input mode
- #6232 - Rhythm note input mode fixes and improvements
- #6207 - insert horizontal frame in front of frame using palette
- #6204 - Reimplement Shift+L/R for leading space while in edit mode upon notehead
from musescore.
The following issue needs to be resolved:
https://musescore.org/en/node/307005.
The following PR addresses it directly:
And then also
- #6268 - changes default playback sound for chord symbols to piano
Another possible approach is #6259 which disables chord symbol playback for pre-3.5 scores, but I think the consensus is #6268 is preferable.
from musescore.
- #6243 - restore backward compatibility for collision avoidance of rests
from musescore.
- #6248 fix issues with jumps and repeats (no regression, just plain bugfixing)
--> moved to 3.5.1 milestone
from musescore.
- #6246 - [Windows, Linux] Bold and underlined text is not displayed properly - a regression introduced by the workaround of PR #5794. This new PR simply disables the workaround for the bold+underlined case.
from musescore.
- #6249 - fix Save Online on Linux
from musescore.
- #6256 low risk MusicXML import/export improvements
from musescore.
By popular demand. Undoes the change to the default zoom type that was made in #5623.
from musescore.
- #6260 - Element dragging with modifier keys [ctrl/shift] incorrectly apply offsets of previous drags
from musescore.
from musescore.
from musescore.
I edited a comment above to list #6268 (changes default playback sound for chord symbols to piano) as the consensus on how to handle compatibility/surprise concerns for older scores with chord symbol playback.
from musescore.
Yet unresolved issues (without PRs, as those don't make sense there):
- Updating the MuseScore General (and for the Extensions the MuseScore General HQ) soundfont.
Solves several issues, at least these:- #232886: MuseScore_General.sf3: "Space Voice" panning issue.
- #291501: use of envelope delay phase in SoundFont causes bizarre playback behavior
- #299366: Choir sample on E3-F#3 adds octave pitch
- #299545: Incorrect Harmonica Range
- #305308: Marching band snare drum cymbals don't sound
- #305333: Bug Report on A4 for Double Bass
- Translation issues, some strings (12 in total) that had been 'translated' into en_US somehow made it back to Transifex as the source strings. Got translated into various other languages, but now show untranslated as they don't refer to the real source strings. Mentioned in https://t.me/MuseScoreTranslation/5522 ff.
from musescore.
- #6280 - fixes recent regression where Ctrl+Delete would become disabled after right-click
- #6281 - fixes bug in "realize chord symbols" command where override of jazz/literal interpretation was ignored
from musescore.
- #6283 - Add support for the Haiku operating system
This would really help to have this added to the 3.5 release, as it would make it easier for the folks over at HaikuPorts (Haiku’s main package management repo).
from musescore.
- #6297 - make sure unchecking "continue text" box for hairpin lines survives save (fixes a 3.5 regression caused by #5747)
from musescore.
- #6267 - fix a warning reg. a no longer existing tabStop, minor but harmless
- #6296 - fix #307548: Lines palette: duplicate symbols Not a regression, but a very small and harmless fix
- #6300 - fix #307593: prevent duplicated icon on Ubuntu Not a regression, but a very small and (hopefully, review needed) harmless fix
- #6305 - CMake: Print Qt version or useful error if it's not installed (very harmless but helpful for developers)
from musescore.
- #6265 - Partially fix #294768: tremolos don't have cue size
This PR also fixes an issue of the stem length becoming a bit longer than necessary for chords with tremolo strokes and a downward stem.
It also makes one-note tremolo layout slightly better.
from musescore.
- #6314 - Make the check for the soundfont name case insensitive
- #6315 - fix #307623: Y offsets change when stave space is changed
I'd like to see this PR in 3.5RC, even if not being a 3.5 regression, but it finally seems to make continuous mode with lyrics usable again:
from musescore.
No PR yet, but this is a serious regression that needs to be fixed:
- https://musescore.org/en/node/307721 (blank lines ignored at top of text)
from musescore.
I believe this is important for 3.5, otherwise people will employ workarounds that will break when this does get fixed:
- #6321 (corrects handling of chord symbol alignment with multiple chord symbols, use of autoplace toggle, and more(
from musescore.
No PR yet, but this is a serious regression that needs to be fixed:
- https://musescore.org/en/node/307721 (blank lines ignored at top of text)
- #6328 - fix #307721: blank lines ignored at top of text
- #6330 - Fix #307741 images attached to measures don't propagate between score and existing parts
- #6247 -fix #307005: chord playback default not consistent (is in 3.x, but not yet in 3.5rc)
from musescore.
Congratulations with 3.5 Release Candidate! https://musescore.org/en/3.5rc
from musescore.
Related Issues (20)
- Note highlighting on the piano keyboard ignores ottavas HOT 1
- Correct beam slants and endpoints for new cross-stave positions
- Style dialog - Enter does not activate OK button, Tab does not move focus to the button group HOT 3
- Muse Sounds "Tenors" plays a melisma when enter or selected G4
- Color Notes plugin note working HOT 2
- chord style does not get updated in view when loading a style file
- Muse Sounds tuba playback consistently drags behind other instruments.
- Shadow beneath menus missing in master (Qt6) HOT 2
- Clear measure makes hairpin started in previous measure lost
- Microtonal accidentals behave incorrectly with transposing instruments HOT 1
- Mixer should be able to recognize folders
- Chord Transition mode / display
- musicxml: hidden notehead is not imported correctly HOT 6
- Change sound flags reset behavior
- Remove "Exclude from parts" and "Exclude from score" properties for Staff text
- Implement correct properties for sound flag buttons HOT 1
- Sound flags added after generating parts do not appear in both main & part scores
- Snare Drum does not respect accents when given a dynamic HOT 2
- Soprano Saxophone staccato F#5 squeaks above mp
- A Control-Click (in MacOS) must be followed by mouseUp or the subsequent drag moves the score rather than navigating the contextual menu
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from musescore.