I'm currently using a new fork/mod of Dn-Famitracker right now and its actually really amazing! The problem is 1. It's a fantasy chip now (5E01)
2. It used the same file format as 0CC-Famitracker so I really want to request this as a separate format so it indicates that you need E-Famitracker to open this extension.
By the way here's the GitHub page of the tracker in question.
https://github.com/EulousDev/E-FamiTracker/releases/tag/E0.0.1.0

This tracker also just added support for the AY8930 and the dev plans to add more chips in the future. I think this tracker has a lot of promise.

this seems like it will confuse a lot of people.
people are already confused by vanilla-ft and 0cc-ft formats and 0cc files in ftm battles happen way too often (or files that are actually ftm but made with 0cc, so that they dont load correctly in vanilla)

there are also issues with playing .0cc files made with j0cc or whatever, because the newer versions fix some volume-stuff with expansion chips and it behaves different in the original 0cc-ft

soo, are 0cc-renders that are rendered in j0cc or dn-ft instead of 0cc wrong? what stops me from writing my own fork with changed volume behaviour or different sound (that is still saved as .0cc and technically opens correctly in the original 0cc-ft) but sounds completely different in my version of the tracker..?

i personally think rendering .0cc in j0cc or dn-ft for the 0cc-format is as illegal as rendering .ftm in 0cc for the vanilla ft-format.

______________________________

i say all of this not because i dont like the idea of a new format but because i think the name sucks. will we get even more illegal entries because people think "i used famitracker for this and it saved to .0cc, so it has to be correct"?

my opinion: sounds cool, but only add it if they change the name and file extension to something else.

i think the ftm/0cc debacle can be fixed by just merging it all into one format, like s3xmodit. if someone wants to force people to only use one type of format they can state so in the bitpack

as for e-famitracker honestly i dont think it should be added yet. all it really has to offer atm is a fantasy chip, and personally that just doesnt interest me at all. what it seeks out to add in the future is way more exciting to me, but well the future isnt now sadly

As for the file format thing, i'm pretty sure that the latest version allows users to save to the tracker's own format, .eft.

I do agree with Melon that the tracker isn't exactly developed yet, but I do like the tracker a lot as it is and want to see where it goes.

i really like the idea of merging it into one format (although thats not the actual topic of this thread)

Merging kinda only works for s3xmodit because all the old formats are literally dead and there's only 1 authority maintaining modern standards, OpenMPT.

This is simply not the case with the dozen branches of FT.

I'm also not a fan of a universal merge and then subsequent instructions in the bitpack. It'd be a pain for users to have to download the new flavor-of-the-week-ft-fork just to play what looks like a vanilla .ftm.

My personal solution has always been to prepend the file names like 05beta-something.ftm or uber-something.ftm or 0cc-something.ftm etc.

A good temp solution for OP is to host a wildchip and then link the tracker in the bitpack. As is the best flexibility of the format.

More importantly, since when the fuck is AY8930/P emulation a thing o_0

i'd also say not yet, simply because i feel like it needs some time to grow, stabilize, and define itself as a program first. it's definitely a cool program, but i feel like if we add it just as it's being released and in alpha state, more would need to change as the program is being worked on. i'd say once ay8930 emulation is finalized should it be considered for a format, but as it is right now i'd have to agree with kleeder and mel on this. even then, i think a sound blaster format is more warranted than a full on e-famitracker format since i believe that one hasn't had much tracker support being worked on it until e-ft came along, but that's just me. i'll probably change my mind on this when more chipsets are added in future updates; for right now i'm mainly thinking people would be more interested in ay8903 than they would 5e01. no offense, of course! just a bit more analysis and observationing = w=/

do people still submit .ftm to nsf compos?? if so then i'd argue that we are Not Yet Ready

E

maybe we need specific how to playback the file with merged format. like how in bytebeat you specify how it's run (i.e. infix, rpn, compile) + 8k, 22k, stuff