crash: subscore+marker

Discussions, advice, bug reports and much more about the "bach" environment.
Post Reply
Nikola Kołodziejczyk
Posts: 18
Joined: Mon Mar 07, 2016 6:35 pm

crash: subscore+marker

Post by Nikola Kołodziejczyk » Sun Apr 24, 2016 4:46 pm

Greetings!
I am happily working with the new 0.7.9beta. When extracting part of the score with a marker fixed to the bar i am able to crash Max 7.2.2 on OS X Capitan Macbook Air Late 2012

<pre><code>
----------begin_max5_patcher----------
1209.3oc6Z0siapCD95jmBDWsQJsBafD3bWeNpphLfShaM1HrY2jSUe2OFaH
ARbxl1caN6ZsY2XBdFyLeyOlAz7yoS7y36vBeu+w6qdSl7yoSlnmpchIcmOw
uDsKmhDZ17yZjRNyetgDqoj2HoXolHnaVgbOEq4tmOCSx8UXir7yPrM9de63
kgvN8pTgj4aIrMqpw4RyxffEeNXtGLPOF0Od35PJzRkm88OAB7am6WSm1NL+
FQGC+jZw8ZsDuSKXeoWlWlcLC+Mw77WH1iSaGCMXGZG6I+IPuDKDnM3yvNpn
nDU+Cbs2CfYdRrP9hc9W.7vq.dCfAQK0GBRuF7ieMgunISjyqwdO3A7l4wHz
+Ofuw2mpQe5UAe3eB3yP4a+rFl8J8ZNSxPkFj7kZB5BvNcf8JmS40FEVmfdb
.LPWeDWKHbl5xjg0buLMHniVNmIj0HBSlgQkBBSTgxM6O0yREQYcvEDEarM8
VTVCkNxp9Hmzstd+hdlVD0sam+CsohyNtpycSyu92wowFIpTWR6rGrAvECfd
qQcsBPCwynPfkCXTP9WMi.kitaZJmWMP6A5+CzvX94SMDYlM2593+rAZfDcj
VLzbV69sGtZBIZ8ZJg0aHist6auLdZKmhWoCsVUfjnUAG9zgjtvtNGhfxkD1
Z9..YHnCFUGQkUThro.6gYOho7Jr+PCfu1ApNttgkKIs2oZH0ef26ehIy2DH
o9wpcc+0lNrZMkijKhNLoYcA2Heffjf.vhjzEijknWguUYMPMwU0XAlIQmCq
8BFp5vYyFSrfWpxnd8A3R3hzPXThEg8Bf4SjB4VsiDWVwqa22YH4sXxlsRcf
PijOllZ+hMTbaDzZdsjfKXb0sq5BhFaTfmFV0tJO6wLuYhnrZv+Hh5sQDUn0
HJ0cxnDgzd.kUhN5NTE30nFpz+1iERRShVFDY2UdiWiz3kQwvj+F96H66fzp
IW1ieAxN5dH+l97f2pt53KkZewz5ORoeOlRu3xozWIc9iT42QoxKO0ES2WSx
E1cu52Avy5ceCgtjSQ2ZBEek6FYk5q.FSBffv3SRzekvX5YIoUWJ87bJ2yry
Ef.f5ImuGYm2mJbAAV2eDDX25y3L76prG.vN9.tB9r+Pu.nqfO6OBFHzUvm8
G4.D4J3ydc1fXWAe1quDrvUv2R63aoqfuD63KwUvWpc7k5H3CZu9EnqT+Bzd
8KPWo9En85WftR8KP60u.ck5Wf1qeA5J0u.sW+BzUpeAZu9EnqT+Bzd8KPWo
9En85WftR8KP60u.ck5WBsW+RnKT+xwEjyKKQrBw4M.hZgCONXIa40Ei9wvW
al48a1e7hVCKsFvcRfg2aAFcuEX78TfGoZZawSd49kjBR9VDigoiBCe37gHi
oZ1EZChOMn4qFe7PGQcV2OkyaXcsZEv6aC5TO8R7GzVU8MtmtIsZmeb66I3M
048cpVW+tpD+AIWnrUDl4cEejojQ7rkTTfYCaFsBh.kQw593JvZeDdqpSxMn
Mg2UsA7LZS7cSahuAaC3toMg+E0FSTMpppqoO0pRqhnxM+toWQ0s7nJqjYNU
2DrpL8GI87alAUmukHw4xlZSOotaQjuYo7BbMqgn6UxosR9WS+OPtSrMo
-----------end_max5_patcher-----------
</code></pre>


the same goes for refreshing (bang) bach.score after recieving separate syntax data in all inlets, but I don’t have a clear demo yet, because i rewrote the patch not to use that functionality. It did not crash in the previous beta, thought - as far as this bang crash goes.

Thank You for Your continued work,

Nikola Kołodziejczyk

danieleghisi
Site Admin
Posts: 1349
Joined: Fri Dec 03, 2010 1:25 pm

Re: crash: subscore+marker

Post by danieleghisi » Mon Apr 25, 2016 12:39 am

Hi, you are right, the subscore routine had a bug connected with markers. It's fixed for next release.
As a workaround, if you need it: add an empty measure at the very end, and don't include this measure in the subdump. For instance, in your case add a second measure and send [subscore (1) (1)] . Sorry about this...

If you come across other quirks/crashes, don't hesitate to send us patches, this helps us improving the overall stability...
Thanks for reporting!
Daniele

Nikola Kołodziejczyk
Posts: 18
Joined: Mon Mar 07, 2016 6:35 pm

Re: crash: subscore+marker

Post by Nikola Kołodziejczyk » Fri May 20, 2016 5:15 pm

The crash occurs when I include the last OR the first measure in the subscore. I will then try make it in two passes, with one omitting the first and last bar, but with markers.

Nikola Kołodziejczyk
Posts: 18
Joined: Mon Mar 07, 2016 6:35 pm

Re: crash: subscore+marker

Post by Nikola Kołodziejczyk » Fri May 20, 2016 5:28 pm

Actually, it happens in more cases than that. I have multiple markers in the score with 7 voices. even when I do subscore of one voice from 3 to 6 (in 4 there is a marker attached to the start of the bar) it crashes, while the score has 40 bars for example.

Nikola Kołodziejczyk

danieleghisi
Site Admin
Posts: 1349
Joined: Fri Dec 03, 2010 1:25 pm

Re: crash: subscore+marker

Post by danieleghisi » Sat May 21, 2016 12:57 pm

Hi Nikola, do you have an example for this?
It might be already solved with the previous bug, but one never knows...
Thanks again for reporting,

d

Post Reply