2020-05-13, 05:35 PM
OK, some of this is on me, and I can probably work around this, but I noticed today after 3 times trying to record Ender's Game from my analog encoder that there appears to be a bug in the way movies are being named (specifically their enclosed folder).
I've attached my logs. The pertinent part is at 06:13 on 05/13/2020. You can see that the recording for Ender's Game starts, and at some point NextPVR decides it should use Enders.Game.(2013).ts as the file name, but it continues to use the DIRECTORY name of Ender's Game (2013). That causes ParallelProcessing.sh to fail with the following error:
bash: -c: line 0: syntax error near unexpected token `('
That's a problem for me because my channel blaster script uses ParallelProcessing.sh to help make sure the recording is actually working (and turn on the cable box if it isn't). I can obviously code around this on my end by assuming the recording is fine unless I get absolute confirmation it isn't, but it seems like the folder name needs to be renamed (or at least single quote escaped in the bash call) to avoid this issue.
BTW, I've posted this in the general area because it likely affects both Docker and Linux (not as sure about Windows). I happen to be using Docker in my case.
I've attached my logs. The pertinent part is at 06:13 on 05/13/2020. You can see that the recording for Ender's Game starts, and at some point NextPVR decides it should use Enders.Game.(2013).ts as the file name, but it continues to use the DIRECTORY name of Ender's Game (2013). That causes ParallelProcessing.sh to fail with the following error:
bash: -c: line 0: syntax error near unexpected token `('
That's a problem for me because my channel blaster script uses ParallelProcessing.sh to help make sure the recording is actually working (and turn on the cable box if it isn't). I can obviously code around this on my end by assuming the recording is fine unless I get absolute confirmation it isn't, but it seems like the folder name needs to be renamed (or at least single quote escaped in the bash call) to avoid this issue.
BTW, I've posted this in the general area because it likely affects both Docker and Linux (not as sure about Windows). I happen to be using Docker in my case.
