The 1st fast 400m in a long time. Then lions pondered what their fastest 800m was & if they could hit a 6m30s pace again. The spreadsheet showed the last 800m was on April 23, 2022, but accessing the phone data would take some doing.
Helas, lions didn't consistently note the intervals. The notes were simply long & slow or short & fast. The last 3 800m's were on Feb 27, 2022 when 800m.mp4 was made. The phone recorded a 6m55s pace because it had the camera pole. More 800m's were on Feb 14, Feb 5, all at a 7m pace.
The fastest 800m's were before 2020, with the lunchbox. Lions routinely set that to 6m30s for the 800m, but it tracked slower. The fastest year was 2018, when lions routinely did 300m at a 6 minute pace & some at a 5:30 pace.
2018_05_28T02_44_08Z.kml showed 1600m or 1 mile repeats at a 6m45s pace.
2017_05_11T02_44_06Z.kml showed 800m repeats at a 6:41 pace.
2017_10_05T02_27_31Z.kml showed 800m repeats at a 6:44 pace.
Those were the only 2 outings with 800m's below a 7 handle.
Lions were doing many 400m at a 6:30 pace in 2017 & 2016. This became 400m at a 6:00 pace in 2018. While interval training was routine for most years, there was a long period from 2020-2021 with no interval training.
It seems ultramap repeated the same interval records in multiple files before 2017. Further data would require reviving more phones.
Lions rarely backed up the ultramap data after retiring phones. After much restoration of old phones, managed to recover all the workouts after mid 2020, early 2017- early 2019, late 2014 - mid 2016. Some of the data was in ultramap*.tar.xz files.
Paradoxically, lions have pondered using old phones for data backups, since they're now going over 128GB, the screens are more durable, & web based file management has gotten really good. The longevity of the flash is the mane unknown.
------------------------------------------------------------------------------------
Lions embarked on a new Android app phase, 1st the webphone buildup, then Sound Inspector. Android has been a lot more backwards compatible in the last 5 years than it was before. They seemed to shift investment in engagement to their AI projects.
The mane need was displaying a spectrogram of a sound file which you can pan & zoom around, play repeatedly from a precise starting point. The mane problem is decoding & converting the file in a reasonable amount of time. Then the complete spectrum in the highest resolution goes in a texture. For a 4 minute file, it's 11MB if the FFT window size is 4096, 1024 frequencies are shown, & 32 bits per pixel.
A spectrum is simpler than a waveform, in that you're not mipmapping the complete file or reading the original audio data for every navigation event. The spectrum allows seeing changes in areas of constant loudness, like a compressed file. Cinelerra might need a spectrum for the timeline, but it would greatly expand the index file code.
Comments
Post a Comment