EDIT: Version 0.3.14.3 is now available, see the most recent post for details.
EDIT: Version 0.3.14.4 is now available, see the most recent post for details.

As per a reminder from B00daW, the .0cc file extension has been added

to the current development build of 0CC-FamiTracker.

Except for the additional file type association, .0cc files are identical to .ftm files; as long as an .0cc file is known to be certainly compatible with the official build, one may select "All Files (*.*)" in official builds (in fact previous versions of 0CC-FT as well) and open these .0cc modules in the same manner .ftm.bak files were opened. Future versions of 0CC-FamiTracker will take the file extension used in the currently opened module into account when performing optional validation of the module to ensure that its contents are supported within the most recent stable release, or any previous file format version as preferred in the configuration settings. It shall then be possible to save modules as .ftm files by default, and fall back to .0cc if any extra feature is found. The .0ci file extension has also been reserved for 0CC-FamiTracker instruments.

This site has full rights to add .0cc as one of the accepted file extensions for the FamiTracker format, or add 0CC-FT as a separate format, or do nothing. I am only responsible for informing 0CC-FamiTracker users of this change.

0cc2pt3 when tho

appreciated it, thanks. Longstanding incompatibility issues finally addressed. from now on we'll discern clearly which tool was used when composed.

Thanks again.

Awesome!

.0cc shall be the only accepted file extension for the 0cc format. Because all .ftm files (excluding those made in beta builds) are necessarily compatible with 0CC-FamiTracker, all entrants shall be expected to rename their modules if they use any feature specific to 0CC-FT, even before the next version of 0CC-FT is released.

This marks the first time the .0cc file extension gains acceptance.

Please compile and release a build that exports/accepts .0cc file format. At work currently but others say only developmental builds accept the format. If I can get home in time I'll compile it with Visual Studio...

Format extension changed to .0cc for this format and I updated the filenames associated with the one entry submitted thus far.

I have and use and prefer to use an old 0CC build which does not create .0cc files. Is this explicitly disallowed? Same question for old official FT files.

Because there is no mechanism to mark an 0CC-FT module as 0CC only in the file format, any existing FTM (except 0.5.0 beta modules) cannot be disallowed from being renamed to use .0cc, but then again dozens of people have submitted FamiTracker tracks under wildchip so I do not consider this an issue.

So 0cc is almost a superset of famitracker, and in fact I am almost certain there will be people using 0.3.x (single-digit) and submitting .ftm files as usual, since the submit form does not expressly put a file extension filter; but once again,

- 8k is a strict superset of at least 6 other formats, classic is also a strict superset of 2a03. Should a non-conformant entry show up in these categories, the other entrants will quickly recognize as such anyway, but those other formats exist nonetheless to impose some implicit lower limit (e.g. most people entering 64k would try hard to produce something that would not fit into 48k);

- Conversely, if a module requiring 0CC-FT features appears in famitracker, in such a way that the module produces necessarily different outputs to the channels between the two builds (e.g. using grooves, but not using two expansion chips), then the site shall have full rights to disallow these entries there or move them to the 0cc format upon concensus;

- People uploaded .gbs files for gameboy anyway when .mp3 was the only allowed file extension.

https://botb.club/~pp/builds/0CC-Famitracker_pre-0.3.14-03272016.zip < Here is a quickbuild of the current 0CC-Famitracker pre-0.3.14.

Please look at > https://github.com/HertzDevil/0CC-FamiTracker/commits/master < for all of the changes.

This build opens .0cc / .0ci files and saves them as well.

Thanks!

0CC-FamiTracker v0.3.14 is now released.

V0.3.14.0 - 03/29/16
Additions:
- Added the *.0cc file extension
- Added diagnostic information when loading invalid modules
- Added transpose dialog
Improvements:
- 2A03 instruments now implement the instrument interface
- FDS instruments are compatible with other channels (as untyped sequence
instruments)
- Multichip NSFs now skip writing to registers of unused sound chips
- Implemented FDS Zxx in exported NSFs
- Reordered main frame menu for clearer organization
- Re-added fine spectrum visualizer
Bug fixes:
- Fixed document wrapper for custom exporters crashing when retrieving a non-
existent instrument
- Fixed tracker crashing after importing any FTM containing bookmarks
- Fixed custom exporters crashing due to incompatible interface layouts
- Fixed DPCM functions in document wrapper crashing the tracker if the queried
sample does not exist
- Fixed certain multichip exported NSFs crashing due to VRC6 overwriting the
driver code in presence of FDS
- Fixed tracker ignoring "Backup files" option
- Fixed find / replace dialog not clearing wildcard effect name cache on new
searches
- Selection now always moves to current frame if multi-frame selection is
disabled (according to official build)
- Fixed selection with Shift + arrow keys allowing selection across frame
boundaries when option is disabled
- Fixed Shift + arrow keys not selecting entire rows when compact mode is
enabled
- Fixed selection errors when overflow paste mode is disabled
- Fixed 2A03 instrument not copying delta offset values on cloning
- Fixed BPM display showing values above maximum tempo at current refresh rate
- Fixed VRC6 channels sometimes generating an extra click on starting

The bug tracker

is the single authoritative source of all bug reports. All bug reports must be posted there publicly.

Version 0.3.14.1 has been released.

Since the current icon looks exceedingly similar to the old "OHC" icon, and also unfaithful to the actual logo used at Github, please consider using this

alternate sprite. (The admin crew here probably has a better idea than me at recolouring the icons for different purposes, but I attempted

those as well.)

i think virtually all the "trophy" icons currently in use were generated automatically using a program or script that i wrote, but that was mainly because a lot of newer formats were missing trophy icons altogether. any custom-made trophy icons for new formats are great as long as they use the same colors that other trophy icons use (which i assume you ensured)

0CC-FamiTracker 0.3.14.2

has been released.

@Jangler: The trophy icons were prepared by linearly interpolating the respective black and white colours of the NTRQ icon which used exactly #000000 and #FFFFFF.

0CC-FamiTracker 0.3.14.3 0.3.14.4 has been released.

This release gives the tracker an identity, ports most features from the official 0.5.0 beta, and adds various improvements to the frame editor.

You heard that right, 0CC-FamiTracker 0.3.14.4 can load 0.5.0 beta modules. Saving them back into 0.4.6-compatible FTM modules is straightforward, and those who are interested could take a look at this

implementation status.

The download link is here

, although people who have been using version 0.3.14.2 (or 0.3.14.3) should have seen a dialog box leading right into that release page directly. If you notice that the new EXE file is much larger compared to the previous release, it is because I used a less compact option for the UPX compressor (in fact the same as the 0.5.0 beta builds) so that there is less chance of antivirus software marking it as malware.

All the future 0.3.14.x releases will use this thread. 0.3.15.0 will use a new one. By the way, I am totally aiming for a quarterly release cycle so that each new release is available during the four seasons majors.

So, I dunno what's up, but when I try to download 0CC 0.3.14.4 via the link you provided, Windows Defender is removing it. It says it detects a trojan called Win32/Spursint.A!cl. Do you know what's going on there?

Any and every antivirus software reports hundreds of false positives involving the use of UPX to compress executables, and this cannot be helped. If for some reason whitelisting the 0CC-FT folder in Windows Defender does not work (at least you can in Windows 10), then maybe it is time to blacklist that software altogether hoping that another virus scanner will not report shit out of nothing.

These reports have always been inconsistent across machines and should be ignored. This actually includes the official 0.5.0 beta builds themselves.