primordic/IssueDupesLite huggingface dataset:
Repository: mpdf/mpdf

Issue #552: Proposal: Reducing the code base by using packages
Created: 2017-11-20T12:21:50Z
I've been wondering about ways of reducing the mpdf/mpdf code base in order to make it easier to maintain / document.
One way is to extract components with self-contained logic into their own composer packages, or drop them for existing packages.
As an example, src/Barcode and src/QrCode look generic enough to be extracted to: mpdf/barcode & mpdf/qrcode.
Those libraries could be used by other projects without requiring mpdf/mpdf and could get more ❤️  from the open source community (See #475 for example)
We could also decide to rely on third party librairies, like for example tecnickcom/tc-lib-barcode which was extracted from TCPDF.
Thoughts?

Duplicate issue #1632: Move fonts into an own optional repository
Created: 2022-04-02T21:17:42Z
Feature request
The repository is shipped with about 90mb folder of fonts. It would be nice to make that fonts optional.
The font directory seems already be configureable so already an own directry can be used: 
  
    
      mpdf/src/Config/ConfigVariables.php
    
    
        Lines 450 to 452
      in
      3b21745
    
  
  
    

        
          
           'fontDir' => [ 
        

        
          
           	__DIR__ . '/../../ttfonts' 
        

        
          
           ], 
        
    
  


So only splitting into a separate package example mpdf/fonts would be needed. Add the following class to that package then:
namespace Mpdf\Font;

class FontLocator {
   public static function locate() {
       return dirname(__DIR__) . '/ttfonts';
   }
}
so you can use as default in the config:
'fontDir' => array_filter([
    class_exists('\Mpdf\Font\FontLocator') ? \Mpdf\Font\FontLocator::locate() : null,
]),
If fonts are always require you could throw following exception:
throw new \RuntimeException('Install "mpdf/fonts" package or configure a custom "fontDir".');
For backward compatibility reasons "mpdf/fonts" can be first added as require of this package and in the next major release set to require-dev. With having it as own package also when it is set as require I can avoid that mpdf/fonts is installed by adding "replace": {"mpdf/fonts": "*"} to my project composer.json, this technic is used example to avoid install of polyfills of php versions when you already using that php version (example).

Closing comment (2022-04-02T21:20:26Z): Duplicate of #552, #841
Repository: mpdf/mpdf

Issue #283: Undesired mouseover effect on links in PDF
Created: 2016-12-14T07:02:41Z
Latest version of Chrome (Version 55.0.2883.95 (64-bit))
Mac OSX 10.10.5
MPDF 5.7.3
With a Chrome upgrade am now seeing an ugly yellow box appear on mouseover of all links in generated PDFs. The PDFs are fine in other browsers and native viewers, but not so hot in Chrome
I've attached a screenshot of the behaviour. It happens in new PDFs as well as ones created previously, so is Chrome related. Any thoughts on what could be causing it?

Duplicate issue #378: <a> tag is showing weird div on hover - see attached
Created: 2017-04-20T02:02:20Z
tag is showing weird div on hover.

mPDF version: 6.1
PHP versions: 5.6
This is a PHP code snippet I use
<?php


 $html = '';
        $url = "pdf page url";
        $url = urldecode($url);

        if (count($_POST) > 0) {

            $ch = curl_init($url);
            curl_setopt($ch, CURLOPT_HEADER, 0);
            curl_setopt ($ch, CURLOPT_RETURNTRANSFER, 1 );

            foreach($_POST as $name => $post) {
              $formvars = array($name => $post . " \n");
            }

            curl_setopt($ch, CURLOPT_POSTFIELDS, $formvars);
            $html = curl_exec($ch);
            curl_close($ch);

        } elseif (ini_get('allow_url_fopen')) {
            $html = file_get_contents($url);

        } else {
            $ch = curl_init($url);
            curl_setopt($ch, CURLOPT_HEADER, 0);
            curl_setopt ( $ch , CURLOPT_RETURNTRANSFER , 1 );
            $html = curl_exec($ch);
            curl_close($ch);
        }

        if ($html) {
            $mpdf = new mPDF('utf-8', 'A4-L');

            //$mpdf->useSubstitutions = true; // optional - just as an example
            //$mpdf->SetHeader($url . "\n\n" . 'Page {PAGENO}');  // optional - just as an example
            $mpdf->allow_charset_conversion = TRUE;

            $mpdf->CSSselectMedia = ['screen', 'print']; // assuming you used this in the document header
            $mpdf->setBasePath($url);
            //$mpdf->SetHTMLFooter("<h2>djhfhf</h2>");
            $mpdf->WriteHTML($html, 0);

            $mpdf->Output();
        } else {
            echo 'Error generating PDF';
        }

### This is a HTML code snippet I use


COMPLETE ORDER

Closing comment (2017-04-20T11:08:16Z): Duplicate of #283
Repository: mpdf/mpdf

Issue #176: Invalid fixed-positioned barcode alignment in barcodes example
Created: 2016-07-08T10:49:48Z

Duplicate issue #364: CSS right ignored in position absolute on development branch
Created: 2017-03-29T09:17:39Z
I have this problem
In the development branch the CSS right variable doesn't seem to be parsed correctly.
These are mPDF and PHP versions I am using
mPDF dev-development 94bfea1 (latest)
PHP 7.1.3
This is a PHP code snippet I use
<?php

$pdf = new Mpdf\Mpdf;

$html = <<<HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
	<title>Test PDF</title>
	<style type="text/css">
		.address { position: absolute; right: {$pdf->rMargin}mm; top: {$pdf->tMargin}mm; font-size: 0.9em; text-align: right; }
	</style>
</head>
<body>
	<div class="address">
		address-div
	</div>
	Normal text
</body>
</html>
HTML;

$pdf->WriteHTML($html);
$pdf->Output('Test.pdf', 'D');
Output in Mpdf 7:

Output in mPDF 6.1.3:

I've verified the values of $pdf->rMargin & $pdf->tMargin, they're 15 & 16 respectively.

Closing comment (2017-07-17T17:03:21Z): Closing as duplicate of #176
Repository: mrlt8/docker-wyze-bridge

Issue #1195: Quit working with Web-RTC card
Created: 2024-05-13T21:15:22Z
Bridge is working fine, but the WebRTC card no  longer displays the camera. I'm using url: rtsp://127.0.0.1:8554/ski-hut-deck. The card displays mse;streams: wrong response on DESCRIBE.

Duplicate issue #1230: WebRTC 404, SetRemoteDescription called with no ice-ufrag
Created: 2024-05-26T02:18:37Z
Describe the bug
Provide a clear and concise description of the issue and include logs if applicable.
WebRTC streams are failing to connect in Frigate
Error in Question (produced by Frigate)
SetRemoteDescription called with no ice-ufrag" stream=alley
docker-wyze-bridge Docker Compose:
version: "2.4"
services:
  wyze-bridge:
    logging:
      driver: "syslog"
      options:
        syslog-address: "udp://192.168.1.244:2514"
        syslog-format: "rfc3164"
        tag: "wyze-bridge"
    container_name: wyze-bridge
    restart: unless-stopped
    image: mrlt8/wyze-bridge:latest
    ports:
        - 1936:1935 # RTMP
        - 8556:8554 # RTSP
        - 8888:8888 # HLS
        - 8889:8889 #WebRTC
        - 8189:8189/udp # WebRTC/ICE
        - 5500:5000 # WEB-UI
    environment:
        - WB_AUTH=False
        - WYZE_EMAIL=${WYZE_EMAIL}
        - WYZE_PASSWORD=${WYZE_PASSWORD}
        - API_ID=redacted
        - API_KEY=redacted
        - ROTATE_CAM_ALLEY_CAMERA=2
        - ENABLE_AUDIO=True
        - WB_IP=192.168.1.244
    networks:
      - proxy

networks:
  proxy:
    external: true

Relevant docker-wyze-bridge logs:
[WyzeBridge] 172.18.0.1 - - [26/May/2024 02:15:00] "POST /living-room-camera/ HTTP/1.1" 404 -
Relevant Frigate config:
go2rtc:
  streams:
    alley:
    - webrtc:http://192.168.1.244:8889/alley-camera/
    backyard:
    - webrtc:http://192.168.1.244:8889/backyard-camera/
    living_room:
    - webrtc:http://192.168.1.244:5500/living-room-camera/
  webrtc:
    candidates:
    - 192.168.1.244:8555
    - stun:8555

Environment  (if applicable)

Affected Camera(s): Wyze Cam v3
Affected Camera Firmware: 4.36.11.8391
Affected Bridge Version: 2.9.3, 2.9.4, 2.9.5, 2.9.6, 2.9.7
Bridge type:

 Docker Compose/Docker Run
 Home Assistant
 Other

Closing comment (2024-07-16T13:37:39Z): Could this be related to #1195? Frigate reports incorrect SDP as the error, Home Assistant may be reporting a different error for SDP, "wrong response on DESCRIBE"
Repository: mrlt8/docker-wyze-bridge

Issue #721: Unable to Auth - "Temporary failure in name resolution"
Created: 2023-02-14T21:07:16Z
Full error:
2023/02/14 21:02:21 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
2023/02/14 21:02:31 [WyzeBridge] HTTPSConnectionPool(host='auth-prod.api.wyze.com', port=443): Max retries exceeded with url: /user/login (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f3b30239720>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

Not sure why it's getting a DNS error, no other containers are getting this error.
Was able to ping from other containers. (No ping or curl/nslookup/etc installed on your native docker image to test dns)
It does seem it's not inheriting the DNS from the host for some reason. (I just updated to latest image then saw this error.)
root@487fe88230d4:/app# cat /etc/resolv.conf 
nameserver 127.0.0.11
options ndots:0

vs other containers/host:
>cat /etc/resolv.conf

nameserver 192.168.1.144
search .

Was there any recent changes to anything that would cause it to no longer inherit DNS/resolv.conf?

Duplicate issue #1014: adding credentials in compose file locks your Wyze account for too many login attempts
Created: 2023-10-12T23:52:19Z
I wanted it to automatically login so I added API keys to find out that didn't do it.  I now added my Wyze credentials into the docker compose in Portainer and when I deployed it I was suprised to see that I was locked out of my account.  I knew that because a. Nothing loaded in Wyze Bridge and then it would ask me to login again, b. Login into the Wyze app told me there were too many attempts and I had to wait 15minutes.
I'm on v2.4.0 in docker.  I have 4 Wyze cameras and I also have sub stream enabled which makes it show 8 cameras in Wyze Bridge (if that is the problem, not sure)

Closing comment (2023-10-18T15:16:03Z): Potentially related to #721?
Repository: mrlt8/docker-wyze-bridge

Issue #211: "stream is down", no further ability to see cameras
Created: 2021-10-30T03:06:52Z
wyze-bridge    | 2021/10/28 17:48:58 [RTSP][DINING-ROOM] 📕 Client stopped reading
wyze-bridge    | 2021/10/28 17:48:58 [RTSP][OUTSIDE-GARAGE] 📕 Client stopped reading
wyze-bridge    | 2021/10/28 17:48:58 [RTSP][OUTSIDE-GARAGE] ❌ '/outside-garage' stream is down
wyze-bridge    | 2021/10/28 17:49:35 [RTSP][PROJECT-ROOM] 📖 New client reading
wyze-bridge    | 2021/10/28 17:49:46 [RTSP][PROJECT-ROOM] 📕 Client stopped reading
wyze-bridge    | 2021/10/28 17:49:55 [Outside Garage] [FFMPEG] [Errno 32] Broken pipe
wyze-bridge    | 2021/10/28 17:50:05 [RTSP][BASEMENT] 📕 Client stopped reading
wyze-bridge    | 2021/10/28 17:50:15 [RTSP][BASEMENT] 📖 New client reading
wyze-bridge    | 2021/10/28 17:50:23 [RTSP][GARAGE] ❌ '/garage' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][PROJECT-ROOM] ❌ '/project-room' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][BASEMENT] 📕 Client stopped reading
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][OTHER] ❌ '/other' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][MUSIC-ROOM] ❌ '/music-room' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][BASEMENT] ❌ '/basement' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][DINING-ROOM] ❌ '/dining-room' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][FAMILY-ROOM] ❌ '/family-room' stream is down
wyze-bridge    | 2021/10/28 17:50:25 [RTSP][LIBRARY] ❌ '/library' stream is down
this has happened several times, usually after about a day. all the streams go "down" and I get nothing.
cameras are still available via the wyze app.
Restarting the container a couple of times brings things back - but not always on the first restart.
what information can I get to help troubleshoot this?

Duplicate issue #256: [FFMPEG] [Errno 32] Broken pipe
Created: 2021-11-29T19:22:57Z
Since the firmware upgrade that introduced DTLS, this project has been essentially unusable.  If I run the docker container from cmdline I see constant "Client stopped reading" "New client reading" messages until eventually a stream goes down, get a broken pipe error and then the rest of the streams stop working. I have to constantly kill the container and restart it.

Closing comment (2021-12-01T04:31:50Z): Related to #211? Is this still an issue in v1.0.4?
Repository: mrlt8/docker-wyze-bridge

Issue #505: 🚷 Invalid credentials? Error
Created: 2022-08-12T21:08:09Z
I've had docker-wyze-bridge running for over a year.  At some point in the last 5-7 days I started getting a credentials error.  I hadn't updated either firmware or the bridge in some time although I've since updated the bridge in an attempt to fix the error.
I've removed the container and the directory and completely reinstalled but I still get that error,
The credentials work on both the Wyze website and in the app. I hadn't edited the credentials or anything else in the docker-compose.yaml in months before this happened.  Nothing has changed on my network that I can think of...
This is what I'm seeing:
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] 🚀 STARTING DOCKER-WYZE-BRIDGE v1.8.1
wyze-bridge    |
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] 🔍 Could not find local cache for 'user'
wyze-bridge    |  * Serving Flask app 'frontend'
wyze-bridge    |  * Debug mode: off
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] 🔍 Could not find local cache for 'auth'
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
wyze-bridge    |  * Running on all addresses (0.0.0.0)
wyze-bridge    |  * Running on http://127.0.0.1:5000
wyze-bridge    |  * Running on http://172.16.57.2:5000
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] Press CTRL+C to quit
wyze-bridge    | 2022/08/12 20:57:19 [WyzeBridge] 🚷 Invalid credentials?

Duplicate issue #518: 2FA Auth Code not working on 1.8.4
Created: 2022-08-20T04:14:39Z
Howdy, similar to #83 and #93, my 2 factor authentication code never works and keeps requesting a new one. It doesn't seem to be credential related because if I put the wrong credentials, it fails earlier in the process. Any tips to debug this?
2022/08/20 04:06:46 [WyzeBridge] 💬 SMS code requested
2022/08/20 04:06:46 [WyzeBridge] 📝 Add verification code to /tokens/mfa_token.txt
2022/08/20 04:09:50 [WyzeBridge] 🔑 Using “123456” for authentication
2022/08/20 04:09:51 [WyzeBridge] 🚷 Wrong Code?
2022/08/20 04:09:51 [WyzeBridge] Error: 400 Client Error: Bad Request for url: https://auth-prod.api.wyze.com/user/login

Thanks for the great work, I'm looking forward to getting this up and running.

Closing comment (2022-08-20T04:31:08Z): hmm, just tried this myself and it seems to be working:
[WyzeBridge] 🔐 MFA Token Required
[WyzeBridge] 💬 SMS code requested
[WyzeBridge] 📝 Add verification code to /tokens/mfa_token.txt
[WyzeBridge] 🔑 Using 471018 for authentication
[WyzeBridge] ✅ Verification code accepted!

Are you adding quotes " around the token?
Could potentially be related to #505 where the production api is having some authentication issues.
Edit looks like the script isn't catching the left/right double quotation marks (“ and ” are not the same as ")..?
Repository: mrlt8/docker-wyze-bridge

Issue #1084: Delayed video via Blue Iris
Created: 2024-01-13T15:13:46Z
I use the bridge with Blue Iris and I've started to notice delayed video with the latest version (2.7.0). If I restart the bridge the delay is better but gets worse over time. The video is delayed between 2 minutes to over 4 minutes (on the Pan V2) after a few hours.  I suspect that "Audio sync - bridge will now try to make minor adjustments to try to keep the video and audio in sync" could have something to do with it but I don't use the audio feature on any of my Wyze cameras.

Duplicate issue #1079: Audio Sync issues causing video to be unavailable (Cam V2)
Created: 2024-01-12T15:45:06Z
Recent updates have lead to my Cam V2 no longer producing video.
The log is filled with messages about slow video, and of the 3 cameras I have (2 v3 and one v2) only the v2 one is dropping like this.
Disabling audio for the individual camera does not appear to do anything (using ENABLE_AUDIO_CAM_NAME=False), but disabling audio globally fixes it.

Closing comment (2024-01-19T15:26:54Z): Another datapoint: DWB 2.7.0 running a single v3 Pro FW: 4.58.11.4679, getting significant (2h+ within 24h restart of DWB) video lag.
Quite possibly related to #1084 (edit: also #1088).
Repository: mrlt8/docker-wyze-bridge

Issue #529: Add-on not working on mac M1
Created: 2022-08-26T14:16:57Z
I am running home assistant with HASSOS AARCH64 image virtualized with UTM.
When the add-on gets started I always receive the following error:
[FATAL tini (6)] exec flask failed: Exec format error
version add-on: 1.8.6
Version hass-os: 8.5
version home assistant: 2022.8.7

Duplicate issue #604: [FATAL tini (8)] exec flask failed: Exec format error 
Created: 2022-11-10T04:08:18Z
Yes, me again... been enjoying this plugin too much.
Environment:
HASSIO on M1 Mac via UTM Virtualization. aarch64.
I've installed the Add-On, but when starting it it immediately throws an error: [FATAL tini (8)] exec flask failed: Exec format error

Closing comment (2022-11-10T14:30:48Z): This seems related to #529.
Not exactly sure what is going on, but I'll try to look into it again.
Repository: mrlt8/docker-wyze-bridge

Issue #133: Issues trying to get the Wyze Doorbell Cam working
Created: 2021-09-17T14:06:39Z
Moving the Doorbell/WYZEDB3 related discussion over to a new issue.
Originally posted by @tbrausch in #68 (comment)

Duplicate issue #150: Syntax for ROTATE_DOOR
Created: 2021-09-29T04:23:04Z
What is the syntax for the ROTATE_DOOR env variable? I tried =true and even = camera name but couldn't get it.
Thank you for adding this feature, I am excited to use it.

Closing comment (2021-09-30T03:50:49Z): The rest of my issues are tracked in: #133
Repository: mudler/LocalAI

Issue #2368: Native windows version?
Created: 2024-05-22T02:58:23Z
Helllo, I personally find LocalAI very nice, but wish to compare it's efficiency to llama (and derivatives).
Is a windows version (with cpu only option) gonna be available soon?

Duplicate issue #3788: Binary
Created: 2024-10-11T09:32:26Z
Does local ai has precompile binary for woindows

Closing comment (2024-10-11T13:06:33Z): Dup of #2368
Repository: mudler/LocalAI

Issue #4170: Error: rpc error: code = Unknown desc = unimplemented
Created: 2024-11-17T04:40:55Z
Error: rpc error: code = Unknown desc = unimplemented
Using whisper-large-q5_0, localai/localai:v2.23.0-hipblas-ffmpeg image
Also for tarnished-9b-i1
Error: failed to load model with internal loader: could not load model: rpc error: code = Unknown desc = unsupported model type /build/models/tarnished-9b.i1-Q4_K_M.gguf (should end with .onnx)

Duplicate issue #4199: llama-cpp of LocaAI 2.23.0 doesn't load custom .gguf files
Created: 2024-11-19T10:13:46Z
LocalAI version:
2.23.0, podman installation, tried with latest-gpu-nvidia-cuda-12 and latest-aio-gpu-nvidia-cuda-12
`
Environment, CPU architecture, OS, and Version:
Standard Debian 12 (96 GB memory) with two Nvidia Tesla P40 gpus (each 24 GB memory)
Describe the bug
LocalAI fails to load custom .gguf files. In this case its dolphin-2.5-mixtral-8x7b.Q5_K_M.gguf. Following error message appears with all backends
ERR [llama-cpp] Failed loading model, trying with fallback 'llama-cpp-fallback', error: failed to load model with internal loader: could not load model: rpc error: code = Canceled desc = 
It loads and works without issue on version 2.22.1.
To Reproduce
Update LocalAI images to version 2.23.0 and load the "custom" model dolphin-2.7-mixtral-8x7b.Q5_K_M.gguf.
Expected behavior
Loading should work.
Logs
Multiple lines of following messages for all backends.
ERR [llama-cpp] Failed loading model, trying with fallback 'llama-cpp-fallback', error: failed to load model with internal loader: could not load model: rpc error: code = Canceled desc =

Closing comment (2024-11-19T10:25:41Z): Maybe related to #4170
Repository: musescore/MuseScore

Issue #24898: Tremolo on Muse Piano doesn't play all notes in chord
Created: 2024-09-23T23:52:53Z
Issue type
Muse Sounds bug
Description with steps to reproduce
Add tremolo between two chords on Muse Piano. It plays first chord, then tremolo only between highest note from first chord and lowest from second, then plays some strange sound with I think all notes from both chords.
Supporting files, videos and screenshots

  
    
    

    2024-09-24.01-38-08.mp4
    
  

  

  


What is the latest version of MuseScore Studio where this issue is present?
OS: Fedora Linux 40 (Workstation Edition), Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.2-242570931, revision: github-musescore-musescore-3130f97
Regression
I was unable to check
Operating system
Fedora 40
Additional context
No response
Checklist

 This report follows the guidelines for reporting bugs and issues
 I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
 I have attached all requested files and information to this report
 I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Duplicate issue #25325: Tremolo makes a strange sound at the end of the measure at slow tempos and the notes between the treble and bass clef are not synchronized
Created: 2024-10-27T08:10:16Z
Issue type
General playback bug
Description with steps to reproduce

Create a new score.
Then put a slow tempo
Put some notes and add tremolo to them. It should not make that weird sound at the end of the measure. Also the notes should be synchronized.

Supporting files, videos and screenshots

  
    
    

    Ekrano.irasymas.2024-10-27.095818.mp4
    
  

  

  


What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367
Regression
I was unable to check
Operating system
Windows 11
Additional context
No response
Checklist

 This report follows the guidelines for reporting bugs and issues
 I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
 I have attached all requested files and information to this report
 I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Closing comment (2024-10-29T16:53:09Z): Closing as duplicate of #24898
Repository: musescore/MuseScore

Issue #12823: [MU4 Issue] Inclomplete message when checking for language update
Created: 2022-08-12T13:11:11Z
Describe the bug
Inclomplete message when checking for language update
To Reproduce
Steps to reproduce the behavior:

Edit > Preferences > Languages
Make sure language is set to "System default"
Click on 'Check for language updates'
See error:


Expected behavior
The language should be named, either "Deutsch" (in my case) or "System Language" (or similar):

like it is when having selected "Deutsch" as the language
(and yes, that string hadn't been translated until a minute ago)
Platform information

OS: Windows, MuseScore self-built from latest master branch

Duplicate issue #13096: [MU4 Issue] Missing or incorrect text in dialog from 'Check for language updates' button
Created: 2022-08-31T12:28:18Z

Closing comment (2022-08-31T12:30:25Z): Duplicate of #12823 :)
(And see #12917 for the fix)
Repository: musescore/MuseScore

Issue #13381: [MU4 Issue] Instrument sound preview has fixed note duration when playing MIDI keyboard
Created: 2022-09-16T10:52:00Z
Describe the bug
Sound preview was partially re-implemented by fixing #11234, but still doesn't work like in MuseScore2.
It should work like you playing instrument, note should last as long as you pressing key on MIDI keyboard (using Flute, Violin etc.).
Now it has fixed note duration like in note input mode.
To Reproduce

Select measure on Flute
Press key on MIDI keyboard for 2 seconds - sound should last 2 seconds

MuseScore2

  
    
    

    bandicam.2022-09-16.13-49-07-277.mp4
    
  

  

  


MuseScore4

  
    
    

    bandicam.2022-09-16.13-50-08-302.mp4
    
  

  

  


Expected behavior
Should work like in MuseScore2
Platform information
macOS, Windows, Linux
Additional context
#11234

Duplicate issue #19179: MIDI Keyboard Loopback in Audition State (while Input Mode OFF) - Redesign Fixed Note Length Loopback Limitation
Created: 2023-08-26T17:23:51Z
Your idea
For directly composing on Musescore using MIDI controller/keyboard, it is productive to play-by-hands several candidate musical phrases before placing MS4 into Input Mode for score note entry.  Under MS3 this was a very productive workflow.  With MS4 each note "audition-play" loopback is fixed length duration with maximum 999ms, making this awkward, esp. for piano composers writing complex arpeggiations.
This occurs with all audio sources: 1) MSBasic, 2) 3rd party SF2 soundfonts, 3) MuseSounds and 4) 3rd party VSTs

Loss of productivity for composers (but less of an issue for Transcribers)
Major show-stopper for using MS4 with Synthewizer VSTs!!

Recommendations:

In "audition state" MIDI keyboard loop-back should be a pass-through (not limited to fixed note on-off note length) [Regression MS3]
Also add options to allow pass-through for piano pedal, and other CCs (including Mod Wheel) [New Feature Request]

Problem to be solved
Composing with VST Synthesizers require adjusting large number of synth parameters such as oscillators, routing/effects, cutoff filters, LFOs, ADSR and lots of CC controls.  This is not possible with current 999ms max and fixed note length limitations.
Prior art
Pass through seems normal for another notation software, and of course, all DAWs.
Additional context
MS 4.1.1
Tested with Windows and Linux MS 4.1.1.
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

Closing comment (2023-08-26T21:42:41Z): The fixed note duration issue is a duplicate of #13381. That has been scheduled for 4.2 with high priority, so fingers crossed :)
For the pedal / CC feature request, I'd recommend to open a new dedicated feature request.
Repository: musescore/MuseScore

Issue #15371: [MU4 Issue] When system markings are duplicated in score, they are also duplicated in parts
Created: 2022-12-19T10:23:14Z
Describe the bug
When a score has duplicated system markings, e.g.

These markings are also duplicated in the parts:

As can be seen. this doesn't seem to affect text lines, but normal tempi, rehearsal marks are clearly affected. (I haven't tested all other types of marking.)
To Reproduce
Steps to reproduce the behavior:

Create score from a template that has these duplicate system markings (SATB + keyboard, or chamber orch/symphony orch)
Put some tempi and other system markings in
Open some parts and behold

Expected behavior
In parts, all system markings should appear only once, on the top stave. (Yes, eventually this will become configurable, just as it will be in the full score.)
Platform information
OS: Artix Linux, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-223481440, revision: github-musescore-musescore-7dae648

Duplicate issue #15549: [MU4 Issue] Multiple instances of system text when re-showing voices
Created: 2022-12-24T01:06:39Z
When in a part with multiple voices, when you hide one voice then make it reappear, system elements like tempi and rehearsal marks reoccur for each voice, and are linked to each part's visibility
Reproduce with two voices:
-Create a score with one instrument having two voices
-Add a system element, like a rehearsal mark or a tempo mark
-Go to the part with the instrument with two voices and hide one voice
-Make this voice reappear- there are now two system elements
-Hide either voice- the duplicate element is hidden as well
-Show this voice again- the duplicate element reappears.
This scales to three and four voices as well- hiding one voice and making it reappear seems to create a new instance of the system element attached to the voice
What should happen is that, no matter how many voices are shown in a part, the system elements should only occur once.
MuseScore 4.0.0, MacOS 13.0.1

Closing comment (2022-12-24T15:13:36Z): Thanks for the video!
It appears that this will be fixed by #15389.
As such, I'll close this as a duplicate of #15371.
Repository: musescore/MuseScore

Issue #12786: [MU4 Issue] Maximized windows do not appear full screen on some display scales
Created: 2022-08-11T09:30:05Z
Describe the bug
Maximized windows do not appear full screen on some display scales.
To Reproduce

Set to a specific display scale (175% or 225% in my environment)
Open MuseScore and maximize window
See gaps around the window

Expected behavior
There should not be gaps around the window.
Screenshots
Display scale: 175%

Platform information

OS: Windows 11

Additional context
My display resolution is 2880x1920.
Checked with Public Alpha

Duplicate issue #15599: [MU4 Issue] On a HiDPI display, MuseScore's window doesn't fully maximize
Created: 2022-12-26T09:21:59Z
Describe the bug
On a 4K screen with HiDPI set, when maximizing MuseScore's main window, it doesn't fully maximize. A couple of pixels from the content underneath the window are still visible on each corner of the window.
Notice the weird visual bug where, above MuseScore's chrome, the regular Windows min-max-close chrome elements are drawn, but squished. (pic 2)
To Reproduce
Steps to reproduce the behavior:

Open MuseScore.
Maximize the main window (either by typing Win-UpArrow, or the maximize widget on the top right of the window).

Expected behavior
MuseScore's maximized window should encompass the entire screen.
Screenshots


Platform information

Windows 11
4K screen
DPI set to 150%

Closing comment (2022-12-26T15:07:43Z): Thanks for reporting! This is a duplicate of #12786, which already has a fix that will be included in the next patch release.
If you want, you can try it out in the latest nightly build from the master branch: https://musescore.org/en/nightly-builds
Repository: musescore/MuseScore

Issue #11340: [MU4 Issue] New Score - Opens complete new instance when score already open
Created: 2022-04-25T11:49:12Z
Describe the bug
Creating a new score when a score is already open automatically opens a complete new instance of MuseScore.
To Reproduce
Steps to reproduce the behavior:

Open a score
With score open, select "File > New ..."
See described behavior

Expected behavior
Like Logic, Sibelius, or other popular applications that are both resource intensive and use VST, there should be a separate instance opened as a window on top of existing instance, without a redundant icon in the OS dock/systray.
User should be prompted with choice to close existing score or open new instance.
New instance should open, but without redundant icon.
User can toggle between sessions using navigation window (maybe under View?).
Screenshots



Platform information
OS: macOS 12.2, Arch.: x86_64
MuseScore version (64-bit): 4.0.0-2214419458
revision: github-musescore-musescore-df96a36

Duplicate issue #15286: [MU4 Issue] Unable to open multiple different scores in the same MU instance + crashing
Created: 2022-12-17T20:26:15Z
Describe the bug
When opening or creating a score, instead of opening a new tab in the current instance, a new instance of MuseScore 4 is launched. This also occasionally causes the former instance to crash.
To Reproduce
Steps to reproduce the behavior:

Open a score
Open another score or create a new score
Sometimes, the former instance will close unexpectedly.
The new score will open in a new MU4 instance instead of in a new tab. If the former instance closed, the new instance will show the "last session closed unexpectedly" dialog

Expected behavior
It should have opened the score in a new tab, similar to parts and similar to how it works in MU3.
Platform information

OS: Win 11

Closing comment (2022-12-18T10:38:20Z): Duplicate of #11340 for the multi-instance report.
"Needs Info" for the crash
Repository: musescore/MuseScore

Issue #17877: Playback has different pitch when switching between audio devices (in Preferences) with different sample rate during one session
Created: 2023-06-06T14:50:05Z
Issue type
General playback bug
Bug description
No response
Steps to reproduce

Make sure your two audio devices connected have different sample rate (e.g. 44 and 48 kHz)
Run MU
Check playback
Go to Preferences>I/O>Audio device
Switch to another audio device
Check playback - playback has different pitch

Screenshots/Screen recordings
I have external Audient iD14 with 44kHz

and internal Realtek with 48kHz

MuseScore Version
4.1
Regression
No. In MS3 changing between audio devices during one session doesn't work
Operating system
Windows10
Additional context
After MU restart all good

Duplicate issue #21813: Playback gets transposed by 3 semitones
Created: 2024-03-04T20:26:10Z
Issue type
General playback bug
Bug description
I am using the MuseSounds strings (Bass-Violin 1) sounds, and occasionally the playback will be transposed down 3 semitones for no obvious reason. When I open and close the program it usually fixes it, but it sometimes happens again the next time I launch Musescore.
Steps to reproduce

Open a file that uses the MuseSounds strings sound (unknown if this is the cause)
Change audio source through disconnecting the current output?
Click on a note to play it, or press the play button

Screenshots/Screen recordings
No response
MuseScore Version
4.2.1.2.240230937
Regression
I don't know
Operating system
Windows 11
Additional context
No response

Closing comment (2024-03-05T16:10:10Z): I believe this is a duplicate of #17877
Repository: musescore/MuseScore

Issue #17815: MusicXML import and export - Implement swing tempo
Created: 2023-06-01T12:23:55Z
Your idea
Implement MusicXML import and export for swing tempo as shown in this example
https://www.w3.org/2021/06/musicxml40/musicxml-reference/examples/swing-element/
Problem to be solved
This is how swing works in Musescore:

  
    
    

    exported_in_musicxml.mp4
    
  

  

  


And this is how it sounds after exporting in MusicXML and opening mxl file:

  
    
    

    imported_from_musicxml.mp4
    
  

  

  


Prior art
No response
Additional context
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.0-231462149, revision: github-musescore-musescore-2be9061

Duplicate issue #18752: MusicXML exporting: swing and straight tempo markings do not fully export.
Created: 2023-07-21T18:00:11Z
Issue type
Other type of issue
Bug description
Swing and straight tempo markings do not fully export when exporting to MusicXML. Instead just the text is exported:
    <measure number="2" width="315.07">
      <direction>
        <direction-type>
          <words default-y="0.24" relative-y="20.00" font-weight="bold" font-size="12">Swing</words>
          </direction-type>
        </direction>

should be:
    <measure number="2" width="315.07">
      <direction>
        <direction-type>
          <words default-y="0.24" relative-y="20.00" font-weight="bold" font-size="12">Swing</words>
          </direction-type>
          <sound>
            <swing>
              <first>2</first>
              <second>1</second>
              <swing-type>eighth</swing-type>
            </swing>
          </sound>
        </direction>

Steps to reproduce

Create a MuseScore project with a Swing element
Export to MusicXML
Import the MusicXML into MuseScore
Listen to the score and note that there is no swing playback

Screenshots/Screen recordings
Before Export:

After Export:


(see that the swing playback is disabled)
MuseScore Version
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.0-231921402, revision: github-musescore-musescore-2e3a93a
Regression
I don't know
Operating system
Windows 11
Additional context
The MuseScore and MusicXML files:
files.zip

Closing comment (2023-07-21T18:07:56Z): Probably duplicate of #17815
but this issue contains more details
Repository: musescore/MuseScore

Issue #24431: MuseScore 4 freezing when hiding an instrument (Mac only, memory leak)
Created: 2024-09-04T07:56:21Z
Issue type
Crash or freeze
Description with steps to reproduce
I have a score with two instruments (vocal + piano).
I can hide the piano without trouble, but when I try hiding the vocals, I get the spinning wheel of death.
MuseScore 4.4.0.242390800 on Mac (Sonoma 14.6.1)
Tomkins - Then_David_Mourned - SS.zip
Supporting files, videos and screenshots

Also see #24431 (comment)
What is the latest version of MuseScore Studio where this issue is present?
OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.0-242390800, revision: github-musescore-musescore-0fcd11b
Regression
Yes, this used to work in MuseScore 4.3.2
Operating system
macOS 14
Additional context
No response
Checklist

 This report follows the guidelines for reporting bugs and issues
 I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
 I have attached all requested files and information to this report
 I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Duplicate issue #24502: Musescore Memory Leak When Hiding a Vocal Part with 2 Voices in the Instruments Side Panel
Created: 2024-09-06T13:54:54Z
Issue type
Crash or freeze
Description with steps to reproduce

Go to existing score with a vocal part with 2 voices throughout
Click the eye button in the left hand panel
Await the spinning wheel of doom and your system running out of memory

Supporting files, videos and screenshots

[Screen Recording 2024-09-06 at 14.49.49.zip](https://github.com/user-attachments/files/16908950/Screen.Recording.2024-09-06.at.14.49.49.zip)
diagnostic.zip
What is the latest version of MuseScore Studio where this issue is present?
MuseScore Studio version (64-bit): 4.4.1-242490810
Regression
I was unable to check
Operating system
OS: macOS 14.6, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.1-242490810, revision: github-musescore-musescore-0b3dd00
Additional context
No response
Checklist

 This report follows the guidelines for reporting bugs and issues
 I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
 I have attached all requested files and information to this report
 I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Closing comment (2024-09-06T14:01:16Z): Duplicate of #24431. But we already have a fix, you can try it out: https://github.com/musescore/MuseScore/actions/runs/10726246723/artifacts/1897956050

Awesome, thanks! Must have missed this when looking at older issues :)
Repository: musescore/MuseScore

Issue #10922: [MU4 Task] (Re-)Implement playback for multi-measure repeats
Created: 2022-03-27T13:25:36Z
Task description
The new MPE playback rendering system does not yet support playback for multi-measure repeats (single-measure repeats do work). The old MIDI rendering system did (before it was replaced for playback; it is still used for MIDI export nowadays).

Duplicate issue #17248: 2 and 4 bar repeat symbol: playback bug
Created: 2023-04-14T19:17:23Z
Issue type
General playback bug
Bug description
The two bar repeat symbol (like % but for 2 bars) doesn't give the correct playback. Instead it functions like the single bar symbol and repeats the last bar only once.
The 4 bar repeat symbol doesn't give any playback at all.
Steps to reproduce

Write 2 or 4 bars of music
place the 2/4 bar repeat symbol in the next bar
start playback

Screenshots/Screen recordings
No response
MuseScore Version
4.0.2
Regression
I don't know
Operating system
Windows 10
Additional context
No response

Closing comment (2023-04-14T20:26:22Z): Hi! This is a duplicate of #10922. It's being worked on!
Repository: music-assistant/support

Issue #287: stuttering and soft playback from spotify to Sonos speaker
Created: 2022-06-02T13:30:46Z
version : 2022.6.0 BETA 0 / HA 2022.6.0
The integration finds all my spotify songs and suchm but I haven't had a good playback yet.
(1) Sound volume is low compared to regular spotify -> sonos on the same system.
I've got it set to '5 (which is more than sufficient  )', but needed to increase it to '17' ... which is quite loud when I use my sonos app to play something else.
(2) For some reason the active song on Sonos is listed as "mediaplayer.hobbyruimte.flac' or "mediaplayer.hobbyruimte.ogg" ('hobbyruimte' being the name of the Sonos speaker I'm trying to use as a target.
(3) I've only ever get a few seconds of playback before the sound stops for a few seconds and continues.
It is as if music assistant is trying to transcode and/or the buffer used to stream the music from spotify to sonos is too small to allow the stream to work.
System : virtual pc environment (Proxmox) using 4 out of 8 cores and 8 Gb memory.
CPU: Intel i7
The same system is running a PiHole with 2 cores assigned.
Note :  I am running Folding@Home which uses +/- 50% of available CPU capacity ...  disabling that add-on did not apear to resolve the stutter.

Duplicate issue #296: V.06b2: music shortly stutters when opening MA
Created: 2022-06-03T12:33:37Z
When music is playing and I re-open MA on HA, the music sometimes get shortly interrupted. Of course not very reproducible. Only saw it happen when the background tasks got activated (turning arrow)
Not noticed in any older version

Closing comment (2022-06-06T21:30:10Z): Most likely a duplicate: #287
Repository: music-assistant/support

Issue #3903: Unmute not working with squeezelite
Created: 2025-04-19T21:33:03Z
What version of Music Assistant has the issue?
2.5.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

 Yes

The problem
Mute is working but when I press it again to unmute, nothing happens sound is only coming back after toggle pause/play button.
How to reproduce

Install the music assistant addon in HA
Install squeezelite (I used the Fedora package to confirm the issue is not my esp)
Connect to the server, play a stream, mute and try to unmute

Music Providers
RadioBrowser
Player Providers
squeezelite
Full log output
log.log
Additional information
Same issue in 2.6.0b3
What version of Home Assistant Core are your running
2025.4.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)
Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot

 Yes

Duplicate issue #3944: After restarting squeezelite, nothing can be heard until the volume is changed
Created: 2025-04-30T06:59:02Z
What version of Music Assistant has the issue?
2.5.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

 Yes

The problem
When I restart my RaspberryPi with piCorePlayer and several squeezelite instances, the players are recognized immediately and you can press play directly. However, you can only hear something once you have adjusted the volume.
How to reproduce
Install piCorePlayer
Connect squeezelite with MA and play Musik
restart the piCorePlayer
Press play in MA -> nothing to hear
change Volume -> you can hear Musik
Music Providers
Internetradio
Filesystem (local disk) [music]
Player Providers
Squeezelite (slimproto players)
Full log output
MA_log.txt
Additional information
I dont know what i should try.
What version of Home Assistant Core are your running
2025.4.4
What type of installation are you running?
Home Assistant Core
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)
Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot

 Yes

Closing comment (2025-05-01T10:01:28Z): Possibly related to #3903
Repository: music-assistant/support

Issue #387: deprecated NumberEntity
Created: 2022-06-17T14:53:01Z
already discussed, but to help with the migration to Issues, and reminder:
2022-06-17 15:59:51 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number is setting deprecated attributes on an instance of NumberEntityDescription, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
2022-06-17 15:59:51 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number::CrossfadeDurationEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
2022-06-17 15:59:51 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number is setting deprecated attributes on an instance of NumberEntityDescription, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
2022-06-17 15:59:51 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number::VolumeNormalizationTargetEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.

running:
Home Assistant Core 2022.7.0.dev20220617
Home Assistant Supervisor 2022.06.dev0903
Home Assistant OS 8.2

Duplicate issue #556: HA BETA - 2022.7.0b0 - Deprecation Warnings
Created: 2022-06-29T23:50:53Z
What version of Music Assistant has the issue?
2022.6.9
The problem
Warnings in HA log with v2022.7.0b0.
How to reproduce
Install HA 2022.7.0b0
Relevant log output
2022-06-29 19:45:06 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number is setting deprecated attributes on an instance of NumberEntityDescription, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
2022-06-29 19:45:06 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number::CrossfadeDurationEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.
2022-06-29 19:45:06 WARNING (MainThread) [homeassistant.components.number] custom_components.mass.number::VolumeNormalizationTargetEntity is overriding deprecated methods on an instance of NumberEntity, this is not valid and will be unsupported from Home Assistant 2022.10. Please report it to the custom component author.

Additional information
No response
What version of Home Assistant Core are your running
2022.7.0b0
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
ODROID

Closing comment (2022-06-30T10:29:14Z): Thanks for informing us! This one was reported earlier: Duplicate of #387