Crash punch cuts in 19.3

Paul_oz53 · Post by **Paul_oz53** » Wed Aug 14, 2019 13:06

Yesterday I top and tailed a recording in CutListEditor, which I have done numerous times without problems. However, instead of long-press Blue, I opted for long-press Yellow as I intended to experiment with "punch" cuts.

I then selected "3. punch", whereupon it crashed.

Attached is the crash log, which I note has a changed format relative to my previous crash logs, notably the inclusion of dmesg data from line 371to the end. Firmware is 19.3 - 20190809.

adoxa · Post by **adoxa** » Wed Aug 14, 2019 17:26

Looks like I assume the IN cuts match the OUT cuts, which does not appear to be the case in your situation (there's at least one more OUT cut than IN cut). What are your marks? I would expect an initial IN cut (top), pairs of OUT/IN (remove the ads), and a final OUT cut (tail; this can be omitted, as that's what "both" is for). If you've already tailed, there would be no final OUT, so that would mean OUT is less than IN, not more.

Paul_oz53 · Post by **Paul_oz53** » Wed Aug 14, 2019 18:00

adoxa wrote: ↑
Wed Aug 14, 2019 17:26
Looks like I assume the IN cuts match the OUT cuts, which does not appear to be the case in your situation (there's at least one more OUT cut than IN cut). What are your marks? I would expect an initial IN cut (top), pairs of OUT/IN (remove the ads), and a final OUT cut (tail; this can be omitted, as that's what "both" is for). If you've already tailed, there would be no final OUT, so that would mean OUT is less than IN, not more.

It was a simple top and tail edit - no ads involved. May have inadvertently set more than one OUT at the start.

As best I recall, I navigated to the start program marker and pressed long-Green. I then decided to move a fraction further in and pressed long-Green again. I then went to the end of program and pressed long-RED. I probably pressed ZERO to reinsert an end mark too. Then long-Yellow and selected PUNCH and crash.

Attached is the screenshot of the program as I marked it. I still have the cuts file too if that's of any use.

adoxa · Post by **adoxa** » Thu Aug 15, 2019 16:16

Fix submitted. In the meantime the workaround is simple: remove the mark after the final out (it's implicit, and the fix is going to remove it, anyway).

Paul_oz53 · Post by **Paul_oz53** » Thu Aug 15, 2019 19:29

adoxa wrote: ↑
Thu Aug 15, 2019 16:16
Fix submitted. In the meantime the workaround is simple: remove the mark after the final out (it's implicit, and the fix is going to remove it, anyway).

Thanks Adoxa. Look forward to the update.