3DS:BAX/makebax: Difference between revisions
From Hacks Guide Wiki
More actions
m fixed info template under section "command line usage" |
m linux is there |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Page WIP|notes= | {{Page WIP|notes= | ||
* Needs instructions for macOS | * Needs instructions for macOS users | ||
** Note that since the makebax <code>release.zip</code> only provides Windows binaries, these OSes will likely need some form of Wine in their instructions. | ** Note that since the makebax <code>release.zip</code> only provides Windows binaries, these OSes will likely need some form of Wine in their instructions. | ||
* Might need troubleshooting info | * Might need troubleshooting info | ||
| Line 18: | Line 18: | ||
|-|Windows= | |-|Windows= | ||
<span> | |||
# On the ffmpeg website, click on the Windows icon and then the <code>Windows builds by BtbN</code> option | # On the ffmpeg website, click on the Windows icon and then the <code>Windows builds by BtbN</code> option | ||
# On that page, download the file whose name ends with <code>win64-gpl.zip</code> | # On that page, download the file whose name ends with <code>win64-gpl.zip</code> | ||
| Line 28: | Line 29: | ||
# In the window that opens, find the option named <code>Path</code>, click on it, and click '''Edit...''' | # In the window that opens, find the option named <code>Path</code>, click on it, and click '''Edit...''' | ||
# In the window that opens, click '''New''', paste the file path you copied earlier, then press Enter and click '''OK''' | # In the window that opens, click '''New''', paste the file path you copied earlier, then press Enter and click '''OK''' | ||
</span> | |||
|-|macOS= | |-|macOS= | ||
| Line 40: | Line 43: | ||
|-|Windows= | |-|Windows= | ||
<span> | |||
# Download <code>release.zip</code> from the makebax releases page. | # Download <code>release.zip</code> from the makebax releases page. | ||
# Extract the <code>release.zip</code> to a folder and move it to any location of your choice | # Extract the <code>release.zip</code> to a folder and move it to any location of your choice | ||
</span> | |||
|-|macOS= | |-|macOS= | ||
WIP | WIP | ||
|-|Linux= | |-|Linux= | ||
# Download <code>release.zip</code> from the makebax releases page. | |||
# Extract the <code>release.zip</code> to a folder (if not done automatically) and move it to any location of your choice, then <code>cd</code> to that location. | |||
# In a terminal window, use your system's package manager (such as <code>apt</code>, <code>dnf</code> or <code>pacman</code>) while sudo or root to install Wine. | |||
</tabber> | |||
====Section II - Converting the video==== | ====Section II - Converting the video==== | ||
# Copy the video you wish to convert into the makebax folder | # Copy the video you wish to convert into the makebax release folder | ||
# Inside that folder, hold SHIFT and right-click anywhere in the empty space - in the resulting menu, click the option that opens a terminal, Command Prompt, or PowerShell window | # Inside that folder, hold SHIFT and right-click anywhere in the empty space - in the resulting menu, click the option that opens a terminal, Command Prompt, or PowerShell window | ||
# Use ffmpeg to transcode your desired video into IVF format | # Use ffmpeg to transcode your desired video into IVF format | ||
| Line 57: | Line 64: | ||
# Use makebax to convert your <code>.IVF</code> file to a <code>.BAX</code> file | # Use makebax to convert your <code>.IVF</code> file to a <code>.BAX</code> file | ||
#* When running the command, put the full filename of one of the makebax <code>.EXE</code>s (e.g. <code>makebax-win64.exe</code>) before the command. | #* When running the command, put the full filename of one of the makebax <code>.EXE</code>s (e.g. <code>makebax-win64.exe</code>) before the command. | ||
#* If you named your converted video <code>converted.ivf</code>, the command would be <code><makebax EXE filename> "converted.ivf" "output.bax"</code> | #* If you named your converted video <code>converted.ivf</code>, the command would be <code><makebax EXE filename> "converted.ivf" "output.bax"</code> (Linux users need to prefix with <code>wine</code>) | ||
# Copy <code>output.bax</code> to <code>sdmc:/bax/</code> on your console's SD card | # Copy <code>output.bax</code> to <code>sdmc:/bax/</code> on your console's SD card | ||
{{success|You have created a usable .BAX file. It will be played (chosen at random, if you already had a .BAX file before this) when your 3DS next boots.}} | {{success|You have created a usable .BAX file. It will be played (chosen at random, if you already had a .BAX file before this) when your 3DS next boots.}} | ||
| Line 80: | Line 87: | ||
* For best performance, the block size should be an integer multiple of the number of available hardware threads (logical processors). This is why the default block size is 48: it's a multiple of the most common PO2 and MO6 multithread setups. | * For best performance, the block size should be an integer multiple of the number of available hardware threads (logical processors). This is why the default block size is 48: it's a multiple of the most common PO2 and MO6 multithread setups. | ||
* BAX files should not surpass the 32MiB mark. makebax doesn't enforce this limit, but BAX does. | * BAX files should not surpass the 32MiB mark. makebax doesn't enforce this limit, but BAX does. | ||
[[Category:Nintendo 3DS guides]] | |||