pvc
Well-Known Member
- Joined
- Apr 12, 2023
- Messages
- 1,104
- Reaction score
- 398
Perhaps this will be a new DIY School Hearing Aids (v2.2) PDF file. I dunno yet?
First let's review some rules about client sessions;
But now let's talk about whether you wish to organize/limit the number of future fitting sessions (or not)? Client database session proliferation is likely to occur in a DIYer's database and not in a professional audiologist database. Why? Because DIYers like to experiment and may go off on a testing-tangent that results in adding a large number of fitting sessions.
The additional sessions are likely mostly the same, or worse (of no historical value because you decided to scrap the experimental fitting sessions, and revert back to your previous settings. When going off on a tangent I like to create a new temporary client for testing. After testing (and if I like the tested changes), then I can apply the tested changes to my real client, and optionally delete the test client. On the other hand (if I don't like the changes), then I can revert my hearing aid settings back to the settings from the real database (last session), and optionally delete the test client.
Let's look at the difference in client database sessions proliferation:
Scenario #1 I like the changes - Real Client (Larry Katari)
Session 1; Original Professional Settings
Session 2; Adjustments for SIN/Speech In Noise
Scenario #2 I don't like the changes - Real Client (Larry Katari)
Session 1; Original Professional Settings
Session 2; Revert back to Previous Settings
Scenario#3 (no effort to minimize client database sessions proliferation) Real Client (Larry Katari)
Session 1; Original Professional Settings
Session 2; Adjustments for SIN (Speech-In-Noise) Tweak
Session 3; Adjustments for SIN/Undo Tweak
Session 4; Adjustments for SIN/Second Tweak
Session 5; Adjustments for SIN/another Tweak
Session 6; Adjustments for SIN/another Tweak
Session 7; Adjustments for SIN/another Tweak
etc, etc, etc - depending on how much experimentation
First let's review some rules about client sessions;
- Each client has multiple sessions
- You can have as many sessions as you want
- Sessions are permanent and never-ever overwritten
But now let's talk about whether you wish to organize/limit the number of future fitting sessions (or not)? Client database session proliferation is likely to occur in a DIYer's database and not in a professional audiologist database. Why? Because DIYers like to experiment and may go off on a testing-tangent that results in adding a large number of fitting sessions.
The additional sessions are likely mostly the same, or worse (of no historical value because you decided to scrap the experimental fitting sessions, and revert back to your previous settings. When going off on a tangent I like to create a new temporary client for testing. After testing (and if I like the tested changes), then I can apply the tested changes to my real client, and optionally delete the test client. On the other hand (if I don't like the changes), then I can revert my hearing aid settings back to the settings from the real database (last session), and optionally delete the test client.
Let's look at the difference in client database sessions proliferation:
Scenario #1 I like the changes - Real Client (Larry Katari)
Session 1; Original Professional Settings
Session 2; Adjustments for SIN/Speech In Noise
Scenario #2 I don't like the changes - Real Client (Larry Katari)
Session 1; Original Professional Settings
Session 2; Revert back to Previous Settings
Scenario#3 (no effort to minimize client database sessions proliferation) Real Client (Larry Katari)
Session 1; Original Professional Settings
Session 2; Adjustments for SIN (Speech-In-Noise) Tweak
Session 3; Adjustments for SIN/Undo Tweak
Session 4; Adjustments for SIN/Second Tweak
Session 5; Adjustments for SIN/another Tweak
Session 6; Adjustments for SIN/another Tweak
Session 7; Adjustments for SIN/another Tweak
etc, etc, etc - depending on how much experimentation
Last edited: