Page MenuHomePhabricator

Playing midi again after listening all the way to the end doesn't work on chrome
Open, Needs TriagePublic


To reproduce:

  1. Visit in Chrome
  2. Press play and listen to song to the end.
  3. Press play button again.
  4. Hangs indefinitely.

I have tried this in Firefox ESR and it worked fine.

Event Timeline

Mvolz created this task.Aug 10 2018, 2:44 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 10 2018, 2:44 PM
Mvolz updated the task description. (Show Details)Aug 10 2018, 2:45 PM
Ebe123 added a project: TimedMediaHandler.
halfeatenscone added a subscriber: halfeatenscone.EditedJan 22 2019, 2:13 AM

I've noticed the same thing. FWIW, it seems to only happen with some instances. For example, the linked Five Little Ducks example fails consistently for me, but replaying the example at the top of consistently works.

Edit: I think this might be related to T181897. The examples in the Cadence article were added since the change from Timidity to fluidsynth. The ducks example is older, and features the distinctive initial crackle described in T50029. If I preview a trivial change to the score (e.g. adding a comment) to force it to be re-generated, the new version in the preview doesn't have this issue.

Ebe123 added a subscriber: Ebe123.Jan 22 2019, 3:07 AM

T203873 is the solution, and would be trivial (thus was available in GCI) to do.

mb added a subscriber: mb.Jan 23 2019, 4:37 AM

The faulty behaviour at disappears when some trivial changes to the Lilypond code are made. The smallest change I could introduce that would change the behaviour was to insert a space between the first \bar and the empty string ("") following it: from \bar"" to \bar "". (I also suggest that those \bar constructs are unnecessary/wrong and ought to be removed.)