-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mac] how to transcode to original folder (next to the input file)? #329
Comments
@Stooovie See my comment here in your other issue:
|
The best solution then would be to have the script create a new "Transcoded" subfolder in the original folder. Any way to do that? |
@Stooovie One way of accomplishing this would be to create whatever directory you’d like the output to live in, change to that directory, and run the tool. A number of us run our own wrapper scripts to customize the process, myself included, and choosing the output is generally one of those things that gets handled there. @donmelton is correct in his assertion that the path of specific output location is the path towards data loss. Hope this helps a bit. Cheers! |
My scripts, the tools they invoke, and the files I run them on always end up with different file extensions, so I haven't had a problem outputting to the same directory. My scripts are in fact simple fish shell functions, they also move the original to the trash using "trash" from homebrew: I use these in conjunction with another fish function that grabs the finder selection and makes them the parameters to the function, so I select files then execute "conv (selection)" at shell prompt to batch convert (well, I also have a swift program for renaming automatically, so the command I usually do is really "rename-tv (selection) && conv (selection)") |
Hi, I love the tools but I can't figure out how to have the output files created next to the originals. That's always my preferred way to work. I'm on Big Sur. Thanks!
The text was updated successfully, but these errors were encountered: