Forem: lia

How to encode files preserving folder hierarchy

lia — Wed, 30 Nov 2022 17:35:52 +0000

Using the Handbrake GUI can be amazing to encode all types of files, but it's hard to encode files inside their own original folders. You need to manually change the output path one by one.

So, this post will feature a CLI (command line interface) which uses the Handbrake CLI executable to encode all files inside a particular folder, preserving all folder hierarchy!

The main purpose of this CLI was to reduce files' sizes to occupy the least amount of space in the disk, but with the custom command feature, any Handbrake command can be used only requiring specific placeholders regarding the original file path and the encoded file path.

This CLI tool will also create a final output file containing statistics about the files encoded, including:

which files were encoded successfully and not successfully;
number of files encoded successfully and not successfully;
original file size;
encoded file size.

Installing

You will need Python installed. You can do that here.

For this CLI to work, the HandBrake CLI version must be installed. This installation can be found in this link under 'Downloads->Other->Command Line Version'

The CLI can be downloaded from here and the GitHub repository can be found here.

pip install havc

To check if the program was successfully installed, you can run the following command in the console:

havc -h

How to

For anymore information please have a look at this file.

Configuration

Initially, you will have to configure:

(-r) where your Handbrake CLI executable is located;
(-c) the folder which contains files to encode
(-e) as many file extensions you want to be encoded into another extension;
(-t) the target extension.

Like this:

havc -r "C:\Users\<username>\Desktop\HandBrakeCLI.exe" -c "C:\Users\<username>\Desktop\folder to convert" -e mp4 mkv -t m4v

Important
Note that the target extension cannot be the same as any extension searched for.

After this, an external configuration file will be configured and then the following command becomes valid (always using the saved configurations):

havc

This means that instead of always changing the folder to convert, you can have a specific folder for this purpose and then you don't have to reconfigure (at least the folder).

Update configuration

If any argument has to be modified just run the command with the necessary argument.
For instance, if the extensions to search for have to be modified, you simply run:

havc -e mov .avi mp4

Original Files

All original files will be moved to a different folder called 'TO-DELETE' by default. This name can also be change for something else by doing:

havc -d 'AnotherNameForFolder'

This folder will contain all the original files, and it's main purpose is to save all those files just in case any encoding goes wrong.
If you think everything's OK then this folder can be deleted.

Custom Handbrake command

By default, this CLI will run the following basic HandBrake CLI command:

HandBrakeCLI.exe --preset Very Fast 1080p30 -i "C:\Users\<username>\Desktop\original-file\originalFile" -o "C:\Users\<username>\Desktop\output-file\outputFile"

But you can also input a custom command using specific placeholders replacing both the original file and the output file, like this:

havc -cc "--preset Fast 720p30 -i {of} -o {cf}"

'of' stands for 'original file';
'cf' stands for 'converted file'.

Inside the program, {of} and {cf} will be replaced for the path of each file encountered in the configured folder. Then those files will be encoded to the target extension configured.

This custom command is saved until you replace it for another command or setting this feature to 'off':

havc -cc "off"

If 'off', the default command will be used.

Safety question

If you don't want to be bothered with the safety question and are certain the folder is the correct one to modify, you can also disable this feature by:

havc --no-safety-question

This will get saved, so be careful when modifying the folder to convert.

Shutdown computer when finished

If you have a long list of files to convert, you can always enable the shutdown feature which will shutdown your computer when all files were converted.

havc --shutdown

This will get saved, so be careful not to shutdown your computer by mistake. At the beginning of the encoding, the program will give a warning that the computer will be shutdown in the end.

Conclusion

I'm fully available to implement new features, fixing bugs and improve anything. Just comment here or open an issue in the GitHub repository.
Any suggestions I'm more than glad to consider them.
Any feedback is really appreciated.

For anymore information please have a look at this file.

The CLI can be downloaded from here and the GitHub repository can be found here.

Thanks for reading :D

How to schedule any file type to open at computer startup

lia — Mon, 28 Nov 2022 14:38:30 +0000

So, how about schedule certain programs or files to open first thing when your computer boots up? Or maybe you want them to open at a specific time of the day?

Maybe you work remotely and need certain programs, folders or files to open when you start your computer while you can do your morning routine. If so, then this post will feature a program which will (hopefully) help you with that!

That was my problem! I did not like having to use Windows startup feature because it did not let me open programs at specific days. Even the Windows Task Scheduler was not simple enough and did not let me schedule programs at certain days and at startup in the same configuration. I hated having to close all my work programs manually on weekends.

So, I developed a command line interface (CLI) to do that exact task: schedule programs, folders or files (anything really) at startup but also at specific days.

Now, I'm a changed person and can finally have my work programs open at startup only on week days and forget about work completely (without reminders) on weekends.

Installing

You will need Python installed. You can do that here.

The CLI can be downloaded from here and the GitHub repository can be found here.

pip install progscheduler

To check if the program was successfully installed, you can run the following command in the console:

progscheduler -h

How to

For anymore information please have a look at this file.

Startup feature

Windows users

This program does not actually have the ability to start running automatically by itself when the computer boots up yet, so you have to copy the contents of this file right here (available on the GitHub repository) and paste them to a notepad on your computer. Don't forget to save the file with the .bat extension.
The purpose of the file is run the progscheduler program. So this needs to be in the following folder path:

C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

What this step does is to make Windows run all the files in this folder when it boots up (at startup).

Linux users

I don't own a Linux environment so this section will have to wait until I make sure I know how to explain this.

After this step, you should be able to boot up your computer and the program will run automatically.

Usage

For now, when the computer boots up, the program will not do anything. This is because we did not schedule anything yet.
To do this, you need to open a command prompt to start using the CLI.

Commands

When configuring you will need the following information about a program, folder or file:

path to program, folder or file;
desired name to describe this program, folder or file;
days to open;
time of the day to open; ##### Path The path can be the absolute path of an executable, a folder, a file, etc. If it's a program or a file, the path must include the extension.

IMPORTANT
If you want an executable to be schedule, some programs will not work with the original file path and it needs to be the path for a shortcut of that executable.
To use a shortcut, the extension of that file must be .lnk.

For instance, a path for a shortcut executable:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk

or a path for a folder:

C:\Users\<username>\Desktop\folder to open

or a path for a file,

C:\Users\<username>\Desktop\text file to open.txt

Alias

The alias is a name which will describe the file to be scheduled and it will be used for update the scheduling if needed in the future.

Days

The days will be the days in which you want something to be opened. It can be:

some specific days: monday, wednesday
everyday: monday, tuesday, wednesday, thursday, friday, saturday, sunday
weekdays: monday, tuesday, wednesday, thursday, friday
weekends: saturday, sunday

Time

The time can be at startup, in this case you don't have to specify anything because this is the default. Can also be a specific time of the day: 10:27.

The commands are available in the README.md file in the GitHub repository.

Create/Configure a schedule

If you want to schedule Paint to open only at week days at startup then the following command should work:

progscheduler -a paint -e "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk" -d weekdays

On the other hand, if you want to schedule Paint to open only on weekends and at 15:05, the following command should also work:

progscheduler -a paint -e "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk" -d weekends -t "15:05"

Now, if you want to change Paint to open only on Mondays at startup then:

progscheduler -a paint -d monday -t "at startup"

Note the alias is required when creating or modifying a schedule. An alias needs to be unique, because if not, it can configure the wrong configuration or create a non-sense configuration.

Scheduling in action

After we added a schedule and the next time the computer boots up, the program will run automatically and Paint will be opened.
The following image shows that a command prompt will be opened at startup and start running all schedules created.

If a specific time has been set, then the image does not change much, it will be running and when the specified time comes, the program will be opened and showed and this command prompt.

Upon closing this command prompt window, the program will not run anymore schedules so only close it when you know there's no files to be opened.
If closed, the next time the program will start running is:

if the computer boots up;
if you run manually the program-scheduler.bat;
if you run the command 'progscheduler' in a command prompt.

Other features

Delete a configuration

A configuration can also be deleted by the alias by simply typing in the command prompt:

progscheduler -del paint

Future features

Currently the program only opens any type of file, in the future, other options can be added by user request.

Conclusion

For anymore information please have a look at this file.

The CLI can be downloaded from here and the GitHub repository can be found here.

Thanks for reading :D