Resolves #372 Frameset already completed issues

This will still be an issue if latency in the network varies by more that 3 frames, something that can be resolved by disabling the receive buffer entirely.

components/streams/src/sender.cpp

@@ -274,7 +274,7 @@ void Sender::post(ftl::data::FrameSet &fs, ftl::codecs::Channel c, bool noencode
 		spkt.timestamp = fs.timestamp();
 		spkt.localTimestamp = fs.localTimestamp;
 		spkt.streamID = fs.frameset();
-		spkt.frame_number = 255;
+		spkt.frame_number = 0;
 		spkt.channel = c;
 		//spkt.flags = (last_flush) ? ftl::codecs::kFlagCompleted : 0;
 
@@ -298,7 +298,7 @@ void Sender::forceAvailable(ftl::data::FrameSet &fs, ftl::codecs::Channel c) {
 	spkt.timestamp = fs.timestamp();
 	spkt.localTimestamp = fs.localTimestamp;
 	spkt.streamID = fs.frameset();
-	spkt.frame_number = 255;
+	spkt.frame_number = 0;
 	spkt.channel = c;
 
 	Packet pkt;