Week Goals Revisited
- Implement the basic MVC application with homepage
- COMPLETE – It’s not much to look at, but the homepage exists:
- Create GitHub repo
- IN PROGRESS – I created a repo, but still need to update the README with instructions for using the app on different operating systems (and testing this with my teammates to make sure it actually works)
- Create baseline audio recording page functionality
- COMPLETE – I created a simple page that can record an audio signal. However, given that we know now that the microphone signal will be going through the EGG directly, I don’t think this version will be used in the final product, though it’s useful for testing now (instead, I think that the audio signal will come from VoceVista– though, the record page could still be useful for giving the singer visual/auditory cues to go through given warmups)
- Create baseline audio playback page functionality
- COMPLETE (ish?) – I didn’t exactly give a definition for “baseline” here, but I do have a basic version of the page, including a visual of the amplitude of the audio waveform. There’s still some things left to do, though: I’ll need to splice the audio signal into rows, allowing the user to scroll through a longer recording and syncing more seamlessly once we add the EGG signal. I also haven’t yet gotten the cursor to work (showing where the user is in playback)
- Help Melina with creating wireframes for application
- COMPLETE – we have designed basic versions of the main application views, which was very helpful for clarifying some things in the design (namely, the separation of recording pages from analytic pages, and we’re planning to have separate recording views for recording repertoire (the original vision) and for recording guided warmups (which ends up being more useful for formally tracking CQ over time)). Below, for example, is a view of the general idea for the CQ warmup page.
Overall, I’m pleased with this progress, as it gives us some good ground for developing the app further, and I’m on track with what we have on the schedule.
DearPyGUI
As noted in our team update, we’re seriously considering switching frameworks from TKinter to DearPyGUI for the sake of its more seamless mechanisms for data visualization. I’m a bit torn on this, because TKinter has very good documentation and is more of a standard choice– plus, I’ve already spent some time learning about it and getting the application started. On the other hand, I don’t want to be knee-deep into a TKinter application and suddenly realize that it doesn’t give us the functionality that we need– and I’d love to have a more modern look and feel for our app, though it’s not a top priority.
Goals for Next Week
- Write my parts for the Design Review report
- Research & make a decision about DearPyGUI (ASAP)
- Copy a sample DearPyGUI app and gauge its intuitiveness
- Determine a more specific list of plots that we’d like to have for our final project, and see if there’s anything that DearPyGUI clearly does better
- Rewrite what I’ve done so far if we do decide to switch
- Better documentation for code
- README file for setting up dependencies on different OS
- Better code comments
- Better MVP formalization
- Record Screen
- User can choose to either save/discard a recording instead of auto-saving
- User can customize naming a recording upon saving
- (Optional) Playback Screen (if we do switch to DearPyGUI, I don’t think I’ll have time for this)
- Add cursor that moves while playing
- Let user drag cursor to various points in the playback
- Add separation of signal into rows + scrolling