Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 9 hrs, 13 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 21 hrs ago - more...
| The Following 2 Users Say Thank You to WhiteWolf For This Useful Post: | ||
|
2010-12-11
, 00:40
|
|
Posts: 456 |
Thanked: 1,580 times |
Joined on Dec 2009
|
#92
|
Alright,
I added an option for storing the data in a "log" file.
The log file is a simple csv file with ';' as column separator and "newline" as line separator.
The line format is as follows:
<id>;<date>;<time>;<value>;[dB | Linear]
E.g.:
449;2010-12-10;14:25:00.367;45;dB
The date is in ISO 8601 format.
The time is in "hh:mm:ss.zzz" format as described in http://doc.qt.nokia.com/4.7/qtime.html#toString.
If an already existing file is selected, data is appended to that file.
For the same file the id is continuously incremented during the same vumeter "process".
Consequently, the id is reset if, e.g., a new file is selected or vumeter is closed and restarted.
The newest version (0.10.1) is already in extras-devel.
I added an option for storing the data in a "log" file.
The log file is a simple csv file with ';' as column separator and "newline" as line separator.
The line format is as follows:
<id>;<date>;<time>;<value>;[dB | Linear]
E.g.:
449;2010-12-10;14:25:00.367;45;dB
The date is in ISO 8601 format.
The time is in "hh:mm:ss.zzz" format as described in http://doc.qt.nokia.com/4.7/qtime.html#toString.
If an already existing file is selected, data is appended to that file.
For the same file the id is continuously incremented during the same vumeter "process".
Consequently, the id is reset if, e.g., a new file is selected or vumeter is closed and restarted.
The newest version (0.10.1) is already in extras-devel.
| The Following 4 Users Say Thank You to Wonko For This Useful Post: | ||
|
|
2010-12-11
, 10:00
|
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#93
|
Another quick request - not about the application but how it's packaged specifically: As I'm sure you know, FApMan (and maybe Synaptic Package Manager does too) lets you view the changelogs for programs before installing them. You have updates listed for changes up to 0.0.5 I believe. Any chance you can add the rest for them and continue to keep the changelog going? I find that it's a wonderful way to know what else has been added and what has been fixed/changed in a glance. I don't mind dropping by this thread on the forum to see changes, but it makes things easier.
But, of course, it's a minor thing. So no rush, and the application is still great.
But, of course, it's a minor thing. So no rush, and the application is still great.
|
|
2010-12-11
, 16:14
|
|
Posts: 456 |
Thanked: 1,580 times |
Joined on Dec 2009
|
#94
|
Thanks for the hint.
Actually, I was updating the changelog.
Apparently, I didn't do this correctly.
Actually, I was updating the changelog.
Apparently, I didn't do this correctly.
| The Following 3 Users Say Thank You to Wonko For This Useful Post: | ||
|
|
2010-12-12
, 13:36
|
|
Posts: 456 |
Thanked: 1,580 times |
Joined on Dec 2009
|
#95
|
Just uploaded version 0.11.0 to extras devel.
The most important new feature is an "interpolation" option.
This option allows you to choose the number of "samples" used for calculating the volume level.
The number of "samples" is two to the power of the "interpolation level".
Consequently, possible sample numbers are (theoretically, see below) 1, 2, 4, 8, ... , 1024 for the interpolation levels 0, 1, 2, 3, ... , 10.
Thereby, the sample number only defines a maximum value.
The actual number of samples used for calculation may in fact be (much) lower, depending on how much data was ready for processing.
As what I can tell, the settings 1 and 2 practically result in the same sample number of 4.
Currently, there is also some odd issue where the reported volume level may get "stuck" at about 60 dB.
In this situation higher values are still shown but the level does not fall beneath 60 dB.
Setting the interpolation level to another value or selecting a source should resolve this situation.
The second new feature is an option for restoring the default values in the settings dialog.
Furthermore, the changelog should now be properly updated such that you can also follow the changes in your package managers.
Thanks again to Mentalist Traceur for reporting the issue and to lcuk for pointing me into the right direction to get this solved.
The most important new feature is an "interpolation" option.
This option allows you to choose the number of "samples" used for calculating the volume level.
The number of "samples" is two to the power of the "interpolation level".
Consequently, possible sample numbers are (theoretically, see below) 1, 2, 4, 8, ... , 1024 for the interpolation levels 0, 1, 2, 3, ... , 10.
Thereby, the sample number only defines a maximum value.
The actual number of samples used for calculation may in fact be (much) lower, depending on how much data was ready for processing.
As what I can tell, the settings 1 and 2 practically result in the same sample number of 4.
Currently, there is also some odd issue where the reported volume level may get "stuck" at about 60 dB.
In this situation higher values are still shown but the level does not fall beneath 60 dB.
Setting the interpolation level to another value or selecting a source should resolve this situation.
The second new feature is an option for restoring the default values in the settings dialog.
Furthermore, the changelog should now be properly updated such that you can also follow the changes in your package managers.
Thanks again to Mentalist Traceur for reporting the issue and to lcuk for pointing me into the right direction to get this solved.
 |
|
2010-12-20
, 22:55
|
|
Posts: 2,050 |
Thanked: 1,425 times |
Joined on Dec 2009
@ Bucharest
|
#96
|
Is there a way to disable trigger? Zero seems to trigger continuously and 100-120 is not really off.
Excellent app, though.
Excellent app, though.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
N900 dead and Nokia no longer replaces them. Thanks for all the fish.
Keep the forums clean: use "Thanks" button instead of the thank you post.
| The Following User Says Thank You to ndi For This Useful Post: | ||
|
|
2010-12-20
, 23:20
|
|
Posts: 456 |
Thanked: 1,580 times |
Joined on Dec 2009
|
#97
|
Originally Posted by ndi
Just uploaded version 0.11.1 to extras-devel.
Is there a way to disable trigger? Zero seems to trigger continuously and 100-120 is not really off.
This version disables the trigger when the "Trigger Value" is set to zero.
__________________
MeePasswords --- Q To-Do --- QZeeControl
Advanced Clock Plugin --- Binary Clock, Desktop Version --- libswt-hildon
Stultitia Simplex --- To-Do-O --- VU Meter --- Zeecontrol
My homepage with assorted posts about my apps, Qt/QML, etc.: http://ruedigergad.com
Advanced Clock Plugin --- Binary Clock, Desktop Version --- libswt-hildon
Stultitia Simplex --- To-Do-O --- VU Meter --- Zeecontrol
My homepage with assorted posts about my apps, Qt/QML, etc.: http://ruedigergad.com
| The Following 5 Users Say Thank You to Wonko For This Useful Post: | ||
Tip: save time coded measurement values.