(There's probably already some thread about this but this thread has a title in the voice of jerry seinfeld so it's the more important one)

It's been long enough... I think we should allow .dnf and whatever the j0cc file is in 0cc. Making another format for dn-famitracker is not a good idea when there's already a format that's basically just "non vanilla famitracker." One battle in the last 3 years is real sad.

As for what to rename it (if at all) - maybe famitracker+? (nonvanilla famitracker doesn't sound right and chocolate famitracker is crazy)

(PS I promise I'll start battling this if it's changed!)

airline food

i put my voice behind "famitracker+"

+1 for "famitracker+" unified all famitrackers format. i think that's better than a dn-format especially since another fork is ultimately an inevitability lol.

that said, some thoughts:

- i'd rather see a new format get created and 0cc potentially retired from hosting. not really a fan of changing the scope of an existing format so widely, even if it's moving towards more inclusive

- i think when this has come up before the prevailing thought was "well let's wait until dn-fami is in a more stable position" but it's starting to look like that might not happen, so maybe we should just do it

- it definitely sucks bigtime that dn-fami ver. 0.5+ breaks ALL module compatibilities with ALL prior famitrackers including itself. prior to that, you could save ftm/0cc that most likely opened in their respective programs, but now it is a trap. i can see this being a potential source of confusion, if it wasn't already, so i'd probably put info about this in giant bold letters on the lyceum at least.

- xhb voting will be hell, but you know what, voting for gameboy and adlib is already hell :p i kinda think it might be recommended for people to put their version info in the filename for xhbs like people do with lsdj

- relatedly, there is no visual distinction afaik between 0cc and j0cc modules

altogether though i'd say screw it, let's just do the format. it's going to be messy because famitracker development history is messy. that can't be avoided - we can deal with it, probably.

Famitracker+ sounds good for sure. Especially since it could encapsulate any future big forks. I would love to see Dn OHBs and I think this would enable that but also encourage more fami battles in general.

Famitracker+ is perfect (chocolate famitracker could sound crazy, but it also rocks ^^).

I'm all in for the format, looking that this Spring Tracks has vanilla again.

I'm STILL using DnFT 0.4.0.1, it's as smooth as it gets without compatibility issues.

fami+ and you could include famistudio in with the bargain

now that's an interesting idea

i could see it being its own format too

the issue with including famistudio is that it would preclude using famitracker(/fork) modules as bitpacks, since famistudio's ftm support is pretty unreliable.

yeah if you can already do nsf+ and specify +MMC5 in the bitpack, then likewise you should be able to do famitracker+ and specify +0CC in the bitpack... that sounds logical to me.

I mostly only do dn-fami 0.4.0.1 out of habit - it'd be nice to have a formal excuse to explore the capabilities of the other familytracker variants as well.

I see a lot of those problems as annoyances in the greater good of reviving beauty in the world

famistudio is definitely not part of famitracker+ IMO because, well, it's a sequencer, not a tracker. it should definitely be its own format

i support changing 0cc to famitracker+ to include j0cc/dnf/blah/ipitracker files (please do not submit ipitracker files (IYKYK)). though it will need some quite thorough documentation on the lyceum

chocolate famitracker sounds delicious, but it's also full of code instead of actual chocolate

anyway i support this initiative.

same here! i would say famistudio should also get it’s own format.

hey while we're at it, does anyone know what's up with forums banning necroposting???

serious reply: Fami+ good, changing old formats to new ones is always a bummer, keep that archived legacy goin if fami+ makes 0cc genuinely redundant otherwise just move it to how Defle is(?) or fakebit was... I will say though that's yet another NES format and it strengthens my resolve to advocate for another non-redundant .mid format ᕦ(ò_óˇ)ᕤ

put me down for fami+

I agree with famitracker+.
Famistudio should also get its own format due to it having OPN3 support, which no famicom tracker has...

NGL chocolate famitracker is a very fun title.

1 new format for every fami fork

Make it 2 per fork, just to be safe

famitracker2