Closed pul53gh closed 4 months ago
Hi, I could not reproduce it on my device. Does it happen in different browsers?
Hello, so I’ve actually fixed it myself. It turns out my MacBook was just so shitty that Signal would crash opening big midi files. It works fine on my pc and other laptop.
On Sat, Mar 9, 2024 at 12:38 AM ryohey @.***> wrote:
Hi, I could not reproduce it on my device. Does it happen in different browsers?
— Reply to this email directly, view it on GitHub https://github.com/ryohey/signal/issues/320#issuecomment-1986739580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AR7FTIFXNROA7WT5LIAU5GTYXKN6ZAVCNFSM6AAAAABDQJTQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWG4ZTSNJYGA . You are receiving this because you authored the thread.Message ID: @.***>
Thanks for confirming it!
Explanation: For context, I'm in the middle of a project rewriting a marching band piece to run it through Midis2Jam2. When I export the .mid through MuseScore, the instruments are all sorts of mismatched, so I run it through signal so I can reassign and adjust the channels as needed. However, after my latest update to the project, I can't change anything in the file with signal. When I click on one instrument, it freezes with a greyish (my chrome profile is grey so I'm guessing it's just that) screen for a second or two, then allows me to edit the channel, but then when I go to the next instrument, it fully locks up with a solid white screen, and I'm forced to reload the page and start over, which then the same thing will happen.
To Reproduce:
System and Program Info: