16.03.2021, 21:15
Whoa, Hoooooly carp I did not mean to be rude by the submission of multiple logs & jobs w/o verbose explanation I'm sorry! @~@;
I should not have included the 1st debug log even as some kind of reference. I thought of enumerating the jobs I remember doing for it, but forgot what exactly I did and in what order, because when I thought of enumerating that I had created the 2nd debug log already, which I actually had enumerated things for.
I pointed out earlier that "On my encoding attempts, I stop it midway when the estimates tell me it's going to encode the whole thing instead of the cuts I applied."
Though I realized only now what I failed telling: there was no error that occurred here; instead, it was not applying the custom cuts I put there. I started including "stopped" in one of my enumeration of activities I wrote earlier, but retracted it because I thought it would be redundant to the earlier note that "I stopped the job midway".
Anyway, the point of the debug logs was not for the finishing of the encoding, but of the job creation or how it extracted & processed its initialization. By that, it was intentional that I included multiple jobs in the debug log, from the creation of the job with the desired encoding settings & cuts, up to its stoppage or of letting it finish. I was hoping you'd get a pattern from the debug as to why it wouldn't process only the cuts I applied.
The moment it estimated that it's going to take an hour or so, it has already failed its job of following what I told it to do, so I stopped it.
I let the last job finish because I haven't gotten a proper output of that particular cut yet...and to see if it will succeed, which it did. This was the part about "failing then succeeding" (what a failed vague phrase I put there, I'm sorry), where an earlier attempt for cut 4050-4618 failed to be followed (2021-03-16@14_25_26_7310), then the next one I tried succeeded (2021-03-16@14_34_34_2410).
I was unable to think of anything else for having you get troubled with reading all that w/o enough verbose context, nor unable to sleep until I can finish at least this message first...though, all my fault, really... I'll be more considerate with the production of debug logs next time.
I should not have included the 1st debug log even as some kind of reference. I thought of enumerating the jobs I remember doing for it, but forgot what exactly I did and in what order, because when I thought of enumerating that I had created the 2nd debug log already, which I actually had enumerated things for.
I pointed out earlier that "On my encoding attempts, I stop it midway when the estimates tell me it's going to encode the whole thing instead of the cuts I applied."
Though I realized only now what I failed telling: there was no error that occurred here; instead, it was not applying the custom cuts I put there. I started including "stopped" in one of my enumeration of activities I wrote earlier, but retracted it because I thought it would be redundant to the earlier note that "I stopped the job midway".
Anyway, the point of the debug logs was not for the finishing of the encoding, but of the job creation or how it extracted & processed its initialization. By that, it was intentional that I included multiple jobs in the debug log, from the creation of the job with the desired encoding settings & cuts, up to its stoppage or of letting it finish. I was hoping you'd get a pattern from the debug as to why it wouldn't process only the cuts I applied.
The moment it estimated that it's going to take an hour or so, it has already failed its job of following what I told it to do, so I stopped it.
I let the last job finish because I haven't gotten a proper output of that particular cut yet...and to see if it will succeed, which it did. This was the part about "failing then succeeding" (what a failed vague phrase I put there, I'm sorry), where an earlier attempt for cut 4050-4618 failed to be followed (2021-03-16@14_25_26_7310), then the next one I tried succeeded (2021-03-16@14_34_34_2410).
I was unable to think of anything else for having you get troubled with reading all that w/o enough verbose context, nor unable to sleep until I can finish at least this message first...though, all my fault, really... I'll be more considerate with the production of debug logs next time.