From 040ceb788d19e2723431d20e3e0c41b8477d00e6 Mon Sep 17 00:00:00 2001 From: tildearrow Date: Fri, 21 Feb 2025 16:23:21 -0500 Subject: [PATCH] .ftm import: improvements - cut/delay policy is now lax (why was it set to strict?) - macro release mode is now Active (issue #2376) --- src/engine/fileOps/ftm.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/engine/fileOps/ftm.cpp b/src/engine/fileOps/ftm.cpp index a637ef20c..03aef17d7 100644 --- a/src/engine/fileOps/ftm.cpp +++ b/src/engine/fileOps/ftm.cpp @@ -469,6 +469,7 @@ bool DivEngine::loadFTM(unsigned char* file, size_t len, bool dnft, bool dnft_si for (int i = 0; i < 256; i++) { for (int j = 0; j < 8; j++) { macros[i].push_back(DivInstrumentMacro(DIV_MACRO_VOL)); + macros[i][j].open|=9; } } @@ -2744,7 +2745,8 @@ bool DivEngine::loadFTM(unsigned char* file, size_t len, bool dnft, bool dnft_si } } - ds.delayBehavior=0; + // why? I thought FamiTracker was lax + //ds.delayBehavior=0; ds.version=DIV_VERSION_FTM; ds.insLen = ds.ins.size();