Advertisement
stringflow

FlowTimer Update

Dec 2nd, 2019
906
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.12 KB | None | 0 0
  1. FlowTimer's visual cue is really bad and here's why:
  2. Most computer screens run at 60hz meaning they can display 60 images every second. What this means is that the timing of the visual cue will always snap to the nearest 1/60th of a second. Doesn't sound too bad, does it? Well in reality it could mean that an offset of 10,000ms and an offset of 10,015ms would display the visual cue at the exact same time. This is not an issue with the audio cue since modern audio devices play back audio at a frequency of 44,100 hz or higher, which allows for the precise adjustments needed for a good FlowTimer offset. Also there is no way to avoid this issue at all, so any visual cue will suffer from this.
  3.  
  4. I have started working on a port of the java edition FlowTimer over to a different programming language, C#. Lots of people had trouble getting the correct Java version, which frankly I completely understand. With the move over to a different language I'm hoping to see that less people have trouble getting FlowTimer running, as well as me having a more manageable code base meaning I can work on and update FlowTimer more quickly.
  5.  
  6. Moving to C# also has also one small drawback, it's going to be Windows only. You might be able to get it to run on other platforms through Wine, but I have no idea how that works. Non-Windows people might have to stick with the Java version in that case.
  7.  
  8. For this new FlowTimer project I have also decided to change how the program outputs the audio beeps. Instead of having the CPU try to schedule them, I'm electing to generate a sound file that is as long as the offset is with pure silence, then precisely place the beep sounds in the file and just play that sound file back. Since audio devices are made in a way to play back audio at a very precise speed I'm taking advantage of that with this method. This should hopefully be the final update ever to how the beeps are outputed.
  9. In addition to that I am toying with the idea of outright removing the visual cue for the reasons mentioned above. However that is just an idea for now.
  10.  
  11. Thank you for reading and if you have any feedback feel free to message me!
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement