I’m guessing UI release by Tuesday is out. That’s when I would get into the Beta testing. I’m a little Terminal challenged. But really nice to see your efforts in this regard.
I ran this 1 time, but forgot, and closed my laptop lid, sending it to sleep.
When I resumed, the program seemed to stall, so I shut down that command window.
When I try running it again, I get :
Not an ARRAY reference at script/capto.pl line 104.
Also, I see that it stuffs files into /tmp. Is there a way to change this ?
Thanks, Kurt
Hey @tgwaste, seriously slick tool, thanks. Question for you on a Mac OS install: I originally went through the install process in my downloads folder, now that I’ve moved Capto to it’s final home on my hard drive I can still interact via the CLI but every time I do an export command (every variation of ./capto -e *) it generates a full set of export data but instantly closes out with 0 of 0% completed.
I tried to update the location of ffmpeg via ./capto -ffmpeg ~/Dropbox/Project\ Name/Media/Tablo/ffmeg but I don’t get any sort of confirmation. I reconfirm the IP and that does show a conf. I think the issue is that I don’t know how to properly update the ffmpeg location, but something else might be screwing up the export. I moved capto/ffmpeg back to the originally-named download folder (capto.v0.3.macos) and the export process worked perfectly again.
Anyway, I’ve got a couple beers coming your way regardless, but some help would be appreciated.
I do have capto/ffmpeg in the same folder: tested in the original download folder and export worked, moved the download folder and renamed to ‘Capto’, then tried a new batch of exports, no longer ran successfully.
I could go through the install process again in the new location, otherwise I’ll test specifying the ffmpeg location.
Really, really, well done. Love how you have a plex naming option.
A few questions:
Do you plan on open sourcing this?
If not, would you consider providing builds for different architectures, such as 32bit Intel or ARM?
I’ve got an old Pentium 4 in my network closet that’s running Plex on Ubuntu, and I’d rather download on that machine. Eventually I may replace it with a Raspberry Pi.
I am not able to open source the project. I signed an NDA with Tablo agreeing to not release source that exposes the API elements. I realize there are others who may be doing this but I am unsure of their situation. My guess is they figured out the API without signing an NDA. Not sure why Tablo is allowing the distribution on their forums. I could be wrong though
I have updated to version 0.4 which includes a version for 32bit linux. You will have to test this. I do not plan on doing a Raspberry Pi release at the moment as I would have to dig mine out of a box in storage to even start.
This version also changes the behavior of the -ffmpeg switch. Now that switch is used to designate a custom path to ffmpeg once and store that setting so you don’t need to do it everytime. This is for @atllta.
Unfortunately, I’m still finding a way to screw things up. I downloaded capto 0.4, unzipped into ~/Dropbox/RevProj/Capto/, then updated the IP and set the new ffmpeg location. I’m able to update the listings, see episode info, etc., but when I run an export it instantly finishes with 0% complete.
Question, should the ffmpeg path be specified as the folder or the direct path when run in terminal? E.g., /Dropbox/RevProj/Capto/ or /Dropbox/RevProj/Capto/ffmpeg?
After a couple of ffmpeg attempts, I deleted everything and ran through the install process fresh, still no luck. Lastly, tested in my original install location /Downloads/ and the export works perfectly. So, not sure what I can do to get Capto away from my original download & test location.
Definitely hit a dead end, thought the ffmpeg adjustment was the trick.
Thanks for this tool! Just started using Capto to transfer stuff over into my Plex Media Server folders, and for the most part it’s working great although there’s one small glitch I’ve run into with episodes names that have an apostrophe in them. If I issue “-f plex” of course it tries to use the episode name in the file name, and if there’s an apostrophe in the episode name, the script will die with an error like the following:
sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file
Which of course makes perfect sense, since the apostrophe isn’t escaped properly, the shell script is going to expect there to be a terminating apostrophe surround the string.
Of course it works fine if I manually specify a file name, but that defeats the purpose of having Capto automatically name the files for me