Configuration Info
File Locations
Furnace configuration file locations vary by operating system:Configuration Files
| File | Purpose |
|---|---|
layout.ini | Positions, sizes, and docking for each window and tab |
midiIn_.cfg | Default MIDI input settings |
midiIn_*.cfg | Settings for each MIDI device Furnace has seen |
presets.cfg | User-created system presets |
furnace.cfg | All other settings |
furnace.log | Log of activity in the current or most recent Furnace session |
| Filenames ending in numbers | Rolling backups (1 is the most recent) |
Common Problems
Input notes aren't audible or sound different from the instrument, wavetable, or sample editor
Input notes aren't audible or sound different from the instrument, wavetable, or sample editor
Check the following:
Channel type and muting
Make sure the pattern editing cursor is in a channel appropriate to the instrument type, and check whether that channel is muted.
Note range limitations
All chips have limits on what notes can be played, whether within a frequency range or from a list of preset frequencies.
Wavetable size
For wavetables, check the size of the wavetable. If it doesn’t match what the chip expects, Furnace will automatically resample it as needed. An easy way to find out the correct size is to click the “Add” button in the list of wavetables.
Sample considerations
Many sample-based chips need multiple considerations:
- Sample memory limits: Use the sample editor to resize samples to fit or change which ones are loaded into which chip. Reference the memory composition window (in the “Window” menu under “Debug”).
- Sample length and loop positions: If the sample editor shows any highlighted (yellow) boxes or numbers, those will have to be adjusted by moving loop points, resampling, trimming, or padding the sample with silence.
- Sample format: Furnace will auto-convert samples to the correct format for the chip; in some cases, this can make a huge difference in sound.
See the chip’s documentation for more info on specific limitations.
Input notes are audible but aren't appearing in the pattern
Input notes are audible but aren't appearing in the pattern
Multi-ins isn't working
Multi-ins isn't working
Check the following:
- There can only be as many instruments playing as there are channels to play them.
- Playback may be set to “Mono”. Find it in the play/edit controls and change it to “Poly” or “Chord”.
Changing a note's volume seems to have no effect
Changing a note's volume seems to have no effect
Some channels don’t have adjustable volume, such as the triangle channel on the NES. See the chip’s documentation for more info.
Changing one note's volume or pitch affects other notes
Changing one note's volume or pitch affects other notes
Some chips share the same value across multiple channels, such as:
- The SID’s global volume
- The frequency of the noise channel and pulse channel 3 on the SN7
None of the sample editing buttons are working
None of the sample editing buttons are working
The track sounds different when exported to an audio file
The track sounds different when exported to an audio file
Check in the “Emulation” tab of the “Settings” window to see if the chip has different playback and render cores, and change them as necessary.
The track sounds different when exported to a VGM file
The track sounds different when exported to a VGM file
This can happen for several reasons:
- The VGM format doesn’t support all chips, or has incomplete support.
- The VGM format only supports a maximum of two instances of any chip.
- The VGM format cannot store mixer or patchbay settings.
- VGM players may introduce their own inaccuracies, whether due to the software itself (such as the deadbeef VGM player for the MD/Genesis) or the emulator it’s run on (common with volume macros on the Game Boy).
Window and Interface Issues
A window that should be visible, isn't
A window that should be visible, isn't
Check collapsed mode
If you see a title bar but no window, it’s in “collapsed” mode. Double-click the bar to open the window.
Restore from backup
If it only disappeared within the last few sessions, try restoring the window layout from a backup:
- Close Furnace.
- Open the configuration directory.
- Delete (or rename)
layout.ini. - Rename one of the numbered backup files to replace it. They’re numbered in reverse chronological order;
.1is the most recent. - Start Furnace again to see if the window shows up.
Manual edit
If none of the backups help (or you’re comfortable trying manual edits first):
- Close Furnace.
- Open
layout.iniin your preferred text editor. - Search the section headers for the name of the window; it will be in square brackets.
- Delete the
PosandSizelines beneath it. - If
Collapsedis set to1, change it to0. - Save the file.
- Start Furnace; the window should appear in its original position.
After changing a setting, Furnace crashes, is unresponsive, or is unreadable
After changing a setting, Furnace crashes, is unresponsive, or is unreadable
- Restore from backup
- Safe mode
- Clear configuration
Try restoring configuration from a backup:
- Close Furnace.
- Open the configuration directory.
- Delete (or rename)
furnace.cfg. - Rename one of the numbered backup files to replace it. They’re numbered in reverse chronological order;
.1is the most recent. - Start Furnace again to see if the issue clears up.
When I try to open a .fur file, an error dialog says it has an 'invalid info header'
When I try to open a .fur file, an error dialog says it has an 'invalid info header'
The module header format has changed considerably in Furnace versions after 0.6.8.3 (or more specifically, dev239 onward) in ways that are not backward compatible.
The only solution is to upgrade to a newer version of Furnace. Don’t worry, it will still open older modules.
Getting More Help
If your issue isn’t covered here:- Check the FAQ for more common questions
- Review the relevant chip documentation for chip-specific issues
- Check
furnace.login your configuration directory for error messages - Ask in the GitHub Discussions
- Report bugs on the GitHub Issues page