furnace VS trippy

https://github.com/tildearrow/furnace/discussions/1605

I already have the chips. 10x AY from AliExpress for £7 and they turned out to be the real deal.

If you haven't heard of it, there's another cool tracker making great strides right now, Furnace:

https://github.com/tildearrow/furnace

Allows you to compose tunes on several chips / platforms in the one song.

Download the software from their releases page (in the "assets" down under the changelog).

Open source software can sometimes contain malware. That said, in this case I think it's unlikely. These malware scanners are based on heuristics and will often warn you about software that hasn't been downloaded by many people yet. Just make sure you're getting it from the real source: https://github.com/tildearrow/furnace/releases

Maybe you also just want “generic old console sound” but I’m going to try to be more on target here. This is a fairly new, standalone software environment with support for emulating many different classic sound chips. I’m not sure exactly how it works in SNES mode and it may not be that user friendly if you’re used to a DAW but it at least claims to have an SNES mode and it’s free.

My favorite tracker in my opinion is Furnace. It supports many systems, from the PC speaker to to the most recent FM soundcards. It also has a customizable interface and is fully DefleMask compatible. It's completely free too! Link to Furnace Tracker

[3] https://github.com/fujiapple852/trippy/issues/1104

You are right that showing packet loss for intermediate hops is a frequent source of confusion.

Rather than leave it out, I added a status column which shows different statuses for intermediate hops (blue if the hop responds to less than 100% of probes and brown if it responds to 0%) vs the target hop (amber and red).

Where this breaks down is when dealing with ECMP for UDP & TCP tracing, as a given hop (ttl) may represent the target for a given round of tracing but not for the next. The mistake, imho, is to associate _any_ data with a hop (ttl) rather than the hop in the context of a tracing flow.

That is why Trippy had a number of features aimed at helping with ECMP, such as Paris and Dublin tracing, and the ability to filter tracing by unique flow id. I've covered these quite a bit in the 0.8.0 [0] and 0.9.0 [1] release notes if you want to know more.

[0] https://github.com/fujiapple852/trippy/releases/tag/0.8.0

Tracing flows: breakdown complex UDP/TCP ECMP traces into individual flows (i.e. common network path); render a chart of flows in GraphViz DOT format (example)

u/queiss_ the 0.8.0 release note has a section covering this, but the TL;DR is: