Has anybody else been plagued by a NTFS USB drive with Special Characters.
I used to be able to download shows with names that had special characters, but that no longer works. In fact, I can’t even rename some old files that contain them.
I suspect this to be due to the new linux 5 kernel ??? Special Characters work fine
on the /home partition that is EXT4.
Ok I’m not specifically familiar with tablo2go, but just, from what I don’t know, the issue is with the python scrip aka tablo2go - not directly related to NTFS or kernel 5.
Just speculation, the line OSError: [Errno 22] Invalid argument: ‘./TV/Riverdale/Riverdale - S03E16 - Chapter Fifty-One: BIG FUN.ts’ the invalid argument may be related to that colon you mentioned… special charterers in filenames are bothersome.
There were similar issues with capto, the developer ended up modifying the code to remove all characters from filenames -derriered from episode titles- to eliminate errors.
Now I’m not a developer, this was just speculation.
Even though Windows doesn’t support Special Characters, Linux used to be able to use them on Microsoft formatted NTFS drives. Just recently, my Linux system can no longer access Special Characters on NTFS drives.
ok then, you might have answered your own question. Your Traceback does state OSError: but again, I’m just digging at things. I use debian buster so I don’t know the intricates of Arch but I have discovered they have the most current and detailed documentation. I understand Arch to be a “rolling” release, so if it’s been upgraded and now things are different, you may check in there.
It has routines to remove characters and yet you have them… sounds flubbed-up, again I don’t use this app. (I’ve had success with capto).
The snipplet in your debug tracebak seems to be building file names for the HLS segments .ts files.
I would back up a bit… if tablo2to is suppose to sanitize filenames, why are you even getting them in the first place!? I understand you were able to deal with it previously, but if they are routines to:
# Clean a string of all bad characters
# Default ASCII ranges 48-57, 65-90, 97-122, - _ . are allowed,
# otherwise BAD_CHARS can be defined directly
I certainly don’t mean to discount the work and effort put into the application! Even though it may or may not be the best route, something’s getting through. I’m guess it started out as “it works for me” and elaborated on it so it could be shared with the community.
Although, I guess the OP question is why did my system work before and now it doesn’t. I think that’s better asked in Arch Linux support.