Closed jlhunter2008 closed 6 years ago
Just to better help you under I am attaching the .conf file I created. I am running this on a Mac Mini but the folders being watched are on my Synology NAS.
You're missing the =
sign.
handbrakecli /Volumes/Macintosh%20HD/Users/"myusername"/Library/Applications/HandBrakeCLI
should be
handbrakecli=/Volumes/Macintosh%20HD/Users/"myusername"/Library/Applications/HandBrakeCLI
Also, I'm not sure about that encoded space in the path. I think you'll just want to leave it as a space, rather than "%20"
Steve,
I am still getting the same "java.io.IOException: Cannot run program "HandBrakeCLI": error=2, No such file or directory” error message.
On Dec 22, 2017, at 2:34 PM, Steve Hannah notifications@github.com wrote:
You're missing the = sign.
handbrakecli /Volumes/Macintosh%20HD/Users/"myusername"/Library/Applications/HandBrakeCLI should be
handbrakecli=/Volumes/Macintosh%20HD/Users/"myusername"/Library/Applications/HandBrakeCLI Also, I'm not sure about that encoded space in the path. I think you'll just want to leave it as a space, rather than "%20"
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shannah/handbrake-watcher/issues/3#issuecomment-353662054, or mute the thread https://github.com/notifications/unsubscribe-auth/AhKoZACnRXrFNTJkZfbbURBx3RwbAcTVks5tDAQvgaJpZM4RLS3t.
It doesn't seem to be picking up the config file. There are other ways to make it find HandBrakeCLI though:
e.g.
export PATH=$PATH:"/Path/to/Folder/Containing/HandBrakeCLI"
Then run handbrake watcher.
You can ensure that it can find it by using which
. E.g.
which HandBrakeCLI
This should show you the full path to your HandBrakeCLI binary. If it doesn't then adding to your PATH didn't work.
handbrake-watcher -Dhandbrakecli=/path/to/HandBrakeCLI
Should it be a .config or .conf file?
On Dec 22, 2017, at 2:47 PM, Steve Hannah notifications@github.com wrote:
It doesn't seem to be picking up the config file. There are other ways to make it find HandBrakeCLI though:
Just add the directory containing it to your PATH before running the script. e.g.
export PATH=$PATH:"/Path/to/Folder/Containing/HandBrakeCLI" Then run handbrake watcher.
You can ensure that it can find it by using which. E.g.
which HandBrakeCLI This should show you the full path to your HandBrakeCLI binary. If it doesn't then adding to your PATH didn't work.
You could add it on the command line handbrake-watcher -Dhandbrakecli=/path/to/HandBrakeCLI — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shannah/handbrake-watcher/issues/3#issuecomment-353663977, or mute the thread https://github.com/notifications/unsubscribe-auth/AhKoZFdbpmHHY0wXyMfxVpXg4J664-f9ks5tDAc3gaJpZM4RLS3t.
It should be called "handbrake.properties", and it should be located in the same directory you are running handbrake-watcher in.
The issue was with the filename of the properties file. Thank you! However, now I get this error message.
Watching . [15:19:41] hb_init: starting libhb thread [15:19:41] thread 700008e7f000 started ("libhb") unknown option (--first-subtitle=) Failed to convert file Exit code 1
I am trying to get the first english subtitle, which first-subtitle should do since I put eng for subtitle-lang-list
Any help would be appreciated.
Thanks.
On Dec 22, 2017, at 3:14 PM, Steve Hannah notifications@github.com wrote:
It should be called "handbrake.properties", and it should be located in the same directory you are running handbrake-watcher in.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shannah/handbrake-watcher/issues/3#issuecomment-353667937, or mute the thread https://github.com/notifications/unsubscribe-auth/AhKoZEMgclFhE5DvWounwIgPGzjIZTHAks5tDA28gaJpZM4RLS3t.
Command-line "flags" that don't have an associated value should be entered in the handbrake.flags property. E.g.
handbrake.flags=--first-subtitle --another-flag --a-third-flag --etc
BTW. Where did you hear about handbrake-watcher? I made it a while ago mainly for my own use, and I haven't received any issues (or indication that it was being used by others) until last week.
I found it in Google search and I’ll be honest it’s terrific.
On Dec 22, 2017, at 3:32 PM, Steve Hannah notifications@github.com wrote:
BTW. Where did you hear about handbrake-watcher? I made it a while ago mainly for my own use, and I haven't received any issues (or indication that it was being used by others) until last week.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/shannah/handbrake-watcher/issues/3#issuecomment-353670220, or mute the thread https://github.com/notifications/unsubscribe-auth/AhKoZF2qlnE4SUUn6NpIkYne0CIIdruzks5tDBHSgaJpZM4RLS3t.
Hi Steve,
I just stumbled upon this and it's perfect for the automation I want to put in place. I'm having an issue getting this working, and admit I know very little about coding so I'm certain it's something fundamental I'm not doing... anyway, I was hoping you could point me in the right direction.
I'm also getting "Cannot run program "HandBrakeCLI": error=2, No such file or directory", but only when I run handbrake-watcher without the "handbrake.properties" file in the directory I'm trying to run it from.
With the "handbrake.properties" saved in the directory I just get the following and no action, i.e. I have .mkv files in the directory, but the conversion process does not get initiated...
"Handbrake Watcher v1.0 Watching ."
I've attached a copy of my "handbrake.properties" file
Any help would be appreciated.
Thanks
Seb
@sebsez Probably better to start a new issue rather than include yours as a reply to an existing one.
I'm not sure why it's not doing any conversions. In looking at the code, it looks like the extension check is case sensitive. E.g. it will convert files with ".mkv" but not ".MKV". Is it possible that your files have the latter extension.
This is something that should probably be made case-insensitive.
@shannah - Thanks for your response... I've actually found the issue.... When I originally created the "handbrake.properties" it was using mac text edit, which initially creates a .rtf file.... this had some inherent format properties in it, so when I renamed the file to "handbrake.properties", watcher picked these up and did not like them..... I started again with a plain text file and all came good!
Thanks again.
PS: I do have another minor issue, I'll start a new thread for it.
@sebsez Thanks for posting this. Might help others in the future.
I admit I am a noob at this but I created the .config file and entered the path to HandbrakeCLI which is in my Applications folder, but I am still getting this error message. Any help would be appreciated.