• These commercial threads are for private transactions. diyAudio.com provides these forums for the convenience of our members, but makes no warranty nor assumes any responsibility. We do not vet any members, use of this facility is at your own risk. Customers can post any issues in those threads as long as it is done in a civil manner. All diyAudio rules about conduct apply and will be enforced.

GB for Virtins MI Pro for RTX6001 autoranging/autoscaling & for soundcard end users

Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.
It would be interesting to understand the "rules" that were implemented for the autoranging. In another thread, the gist seems to be that different tests need different rules for autoranging. For instance, distortion tests need to select the ranges that give best linearity. Noise tests need to select the range to get best signal-to-noise; etc. With a flexible software package like MI Pro, different tests (plugins?) will need different autoranging "rules" to get the best results. How did you implement this? Does every plugin have it's own "rules"?

Hello mbrennwa,

I’m guessing the other thread you’re referring to is the one located at the URL below:

DIY Audio Analyzer with AK5397/AK5394A and AK4490

Demian is one of the members on the beta team and his comments, as is typical of him, are spot on.

The key concept is that auto-ranging is useful for making measurements of steady state signals or those with either small amplitude variations or that change slowly in their amplitude.

Auto-ranging is not appropriate for measuring signals such as music, noise signals with a high crest factor, tone bursts or voice. For the latter types of signals fixed-range should be used instead of auto-range.

Taking into consideration the above comments, I wish to point out Demian’s posting as per the above URL where he states:

“…This suggests the ranging should be selected as a function of the testing. And typically you may need a manual override…”

Demian’s comment above is totally appropriate. The nice thing is that the MI Pro software allows an end user to enable or disable auto-ranging quickly since its use is a situation dependent type of affair.

With respect to the “rules,” you’re seeking answers to which are more germane to Demian’s posting per the above URL in the first paragraph of his posting, I will let Virtins address that if they so choose.

What is far more exciting to me personally about the integration of MI Pro + the RTX6001 isn’t the auto-ranging per se, not that this feature isn’t worthwhile, it is. What really is the huge benefit to the end user is the proper scaling without any calibration.

To quote Jens:

“…An integrated measurement system will scale the results in absolute values like V, dBV , dBu or whatever the system has been set up for. With the RTX6001 this is different. The SW can generally only show (and output) values in dBFS, since it does not necessarily know the relationship between levels and dBFS. In most programs this can be calibrated, so that it will show scaled values instead of dBFS. The problem is though that if the user turns a knob on the RTX6001, this will no longer be correct, since the general purpose SW out there does not get this information automatically. Then the user would have to re-calibrate every time he changes an attenuator/gain setting. In reality this would be very annoying and could easily lead to errors, when it is forgotten…”

It is very important to note that MI Pro with its custom API for the RTX6001 is not limited in this fashion like Jens’ statement of “general purpose SW,” etc. - - MI Pro know when the attenuation / gains have changed on the RTX6001 for it linked to it via the USB HID remote control API interface so there is no need to re-calibrate every time an attenuator/gain setting is changed.

This is vastly different from the RTX6001 end user who uses ARTA, REW, audioTester etc., (i.e., “general purpose software”). Since the general purpose software doesn’t actually communicate via the remote control interface with the RTX6001 hardware the problems of having to re-calibrate every time he changes an attenuator/gain setting on the RTX6001 becomes an ugly reality to contend with, (ergo Jens statement above).

So in sum, the now successful integration of MI Pro + the RTX6001 hardware in the Spectrum Analyzer of MI Pro gives the user the ability to switch attenuations/gains on the RTX6001 and the RMS amplitude spectrum display to dBFS, dBu or dBV modes, etc. and yet the “whole system” (i.e., MI Pro + RTX6001) remains calibrated for absolute (not relative) measurements, which is just want we want.

V/R,

MI Pro
 
What really is the huge benefit to the end user is the proper scaling without any calibration.

I agree that autoscaling is great, and that's why I use it with my RTX6001 all the time.

The key concept is that auto-ranging is useful for making measurements of steady state signals or those with either small amplitude variations or that change slowly in their amplitude.

Autoranging is a different beast, and I would like to understand how the "ranging rules" are implemented in MI Pro. Does every function/plugin have it's own "rules" to select the best range for its given application?
 
Please add me to the list

1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1

Email sent.
33 - lgo51 - one full pkg:nod:
 
I'm also in for this group buy. Email on the way.

(Thanks for the heads up by PM, too busy with life to read the diyaudio forum daily ;-)



1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
 
Hi, 35- vzaichenko please ;)

1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
______________

The email is sent.

Thank you,
Valery
 
Last edited:
Email sent for #36.

1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
 
Member
Joined 2009
Paid Member
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
39- raudi
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
39- raudi
40 - RE604
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
39- raudi
40 - RE604
41 - bmac_2780

Looks like I just missed out on $10 discount :sigh: . No probs, auto scaling with my RTX6001 is a fantastic feature, looking forward to receiving this
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
39- raudi
40 - RE604
41 - bmac_2780
42 - BE718

Im in + Test Plan
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
39- raudi
40 - RE604
41 - bmac_2780
42 - BE718
43 - nlate
 
1- anatech
2- kevinkr
3- lemon
4- PH104
5- douggoldberg
6- bk856er
7- mlloyd1
8- tjencks
9- agdr
10- waltzingbear
11- Dennis Hui
12- jwilhelm
13- 1audio (Demian)
14- soongsc
15- jhenderson01075
16- jazid
17- lbud4
18- diyaudnut
19- SilentGrace
20- acg
21- Ghianni
22- etlasr
23- B&W_arthur
24- markus22ch
25- niner
26- Microfast
27- gpauk
28- örjan
29- ymwong
30- cddumat
31- deanoUK
32- duster1
33- lgo51
34- jasse
35- vzaichenko
36- Mituisho
37- oyvind
38- ergo
39- raudi
40 - RE604
41 - bmac_2780
42 - BE718
43 - nlate
44- firev1

In for the full package, thanks!
 
I just came across this GB.
I do not have RTX6001. With this customized software work properly with any USB sound card? If yes, I will add myself to the list.

Hello Tony,

Yes, MI Pro will work properly with any USB sound card so long as that sound card has a Windows driver (MME or ASIO). As an example of someone who’s currently signed up for the MI Pro GB who’s using the trail version of MI now with a USB sound card (MOTU) please see this link:

New DAC and Headphone Amp | Page 2 | Audio Science Review (ASR) Forum

V/R,

MI Pro
 
2 MI Pro GB’ers have not emailed me yet with their ordering details yet

Hello Everyone,

The vast majority of MI Pro GB’ers have emailed me as per the instructions, i.e., out of 44 GB’ers 42 have sent their emails to me, i.e., 95.45%.

However, two individuals who have signed up for the MI Pro GB have not yet sent their ordering information to my AOL email. I don’t wish to name them by name here, but I have sent both of these individuals several private diyaudio messages and yet I have only heard back from one via my diyaudio private message system saying he’s going to make a decision (that was sometime back however). The other has not written back to me on my diyaudio private message system or to my AOL email.

The MI Pro GB ends at the end of this month and I have been sending Virtins Technology the complete listing showing who’s ordered what, their email address, names, addresses (where to send their MI Pro USB dongle to), etc.

Virtins Technology will be sending out the PayPal invoices to all the MI Pro GB’ers (I won’t be involved in sending out the invoices so you know it is coming from Virtins via their email domain and their PayPal account).

It is impossible of course for Virtins Technology to email these two individuals with their respective PayPal invoices for the MI Pro GB without my getting their ordering information just as the vast majority of people have done.

All the people who have emailed my AOL email address I have sent email replies back to, confirming their MI Pro order.

Respectfully request that MI Pro GB’ers write back to my AOL email address which is mi_pro AT aol DOT com vs. sending private diyaudio messages to me (due to my diyaudio private message inbox being very close to maximum capacity).

For the two MI Pro GB’ers who still owe me their ordering information, please following my posting # 61 located here: http://www.diyaudio.com/forums/grou...utoscaling-soundcard-users-7.html#post5455995

V/R,

MI Pro
 
Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.