Skip to content
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

Open
Stooovie opened this issue Mar 16, 2021 · 4 comments
Open
Assignees
Labels

Comments

@Stooovie
Copy link

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!

@lisamelton
Copy link
Owner

@Stooovie See my comment here in your other issue:

#312 (comment)

Yes, but you should never do that. This is because the output path name would likely be the same as the input path name and I prevent you from overwriting your original.

Please, never write to the same directory as your original files. This is how horrible data loss accidents happen.

@lisamelton lisamelton self-assigned this Mar 16, 2021
@Stooovie
Copy link
Author

The best solution then would be to have the script create a new "Transcoded" subfolder in the original folder. Any way to do that?

@khaosx
Copy link

khaosx commented Mar 16, 2021

@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!

@jpmhouston
Copy link

jpmhouston commented May 30, 2021

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:
function conv ; for f in $argv ; convert-video -q -o (dirname $f) $f && trash $f ; end ; end
function trans ; for f in $argv ; transcode-video -q --mp4 --no-log -o (dirname $f) $f && trash $f ; end end

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)")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants