SCI2FB: Difference between revisions

From Sierra Wiki
Jump to navigationJump to search
Andrew Branscom (talk | contribs)
Andrew Branscom (talk | contribs)
Line 75: Line 75:
<blockquote>
<blockquote>
Download from here:
Download from here:
* <div id="DL">[[Image:ZIP.png|ZIP File]] [[File:SCI2FB(wSRC).zip|SCI2FB(wSRC).zip]] <span class="DLInfo"> (ZIP file) [34.7 KB]</span> (includes source)
* <div id="DL">[[Image:ZIP.png|ZIP File]] [[File:SCI2FB1.01(wSRC).zip|SCI2FB1.01(wSRC).zip]] <span class="DLInfo"> (ZIP file) [34.7 KB]</span> (includes source)
</blockquote>
</blockquote>



Revision as of 23:16, 22 June 2025

SCI2FB

Version 1.01
Author: Brandon Blume
2023-03-05
  This article is a tool stub page. You can
help the Sierra Wiki by expanding it.
SCI2FB
Latest Version:  1.01
Release Date:  2023-03-05[1]
Company: Template:N/A
Development Status:  {{{DevStatus}}}
Publication Status:  Published
Developer(s): Brandon Blume
Interface: CLI
Language: C++
Open Source: Open
Source Availability:  Yes
License: GNU
Type: Template:SCISndConverter
Relevant Engine: SCI
Platform: Windows
Localization: English
Website: N/A




Description

Brandon Blume's SCI2FB Converts Sierra SCI instrument patch resource files for the Yamaha FB-01/IBM Music Feature Card to one or two SysEx bank files (depending on how many are stored in the patch file) for use with the Yamaha FB-01 (or an emulator) and software. so you can capture the instruments from Sierra games.

Used in conjunction with its companion program FB2SCI, one can collect a library of FB-01 bank files from SCI games, extract the individual voices, and build your own bank files for use with SCI fangames or even other SCI games that never received official FB-01/IMF support. Or if you just like the sounds from a game you can extract them for use in other projects. SCI2FB is currently maintained by Brandon Blume.


Features


Requirements


Version History

v1.01 (Mar 5, 2023):

  • Added support for older SCI patch banks that contain only one SysEx bank (before it would simply assume those files were invalid)
  • Cleaned up the code a bit

 
v1.00 (Mar 4, 2023):

  • Initial release


Development Status

Maintained


Usage


Options


Download

Download from here:


Known issues


Credits


References

  1. From the README


Also See