• 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.
The raw impulse response (IR) you get from the measurement (speaker + microphone) is the convolution of the speaker IR and the microphone IR:
raw-IR = speaker-IR ** microphone-IR

The speaker-IR is therefore simply the deconvolution of the raw-IR from the microphone-IR:

speaker-IR = raw-IR // microphone-IR

Looking at this in the frequency domain may be a bit more intuitive (simple division):

FFT(speaker-IR) = FFT(raw-IR) / FFT(microphone-IR)

I've been using this method for many years now. Works very well.

Am I missing something?

No doubt, your formulation is correct in general terms. But FFT convolution / deconvolution is circular in nature, this may cause severe edge effect (at both leading and trailing edges) if the signal is iFFT back to time domain. Even if you can manage to make it a linear convolution / deconvolution, some degree of edge effect will still exist. For example, do you think you can keep a 10ms 1kHz signal sampled at 48kHz intact in time domain by applying a 500Hz high pass filter? The edge effect will be attenuated to a negligible level when the signal in time domain is long enough and the data at edges are ignored.

My point is that, for a short-time signal such as the directly measured impulse response, one has to weigh the accuracy gained and the artifacts caused in the time-domain waveform presentation by the FFT deconvolution of sensors’ non-ideal transfer function.

Again, it is possible to save the FFT/FIR/IIR filtered/compensated data in time domain in MI.

BTW, MI allows synchronous average in time domain. This will increase the SNR in the directly measured impulse response.
 
No doubt, your formulation is correct in general terms. But FFT convolution / deconvolution is circular in nature, this may cause severe edge effect (at both leading and trailing edges) if the signal is iFFT back to time domain. Even if you can manage to make it a linear convolution / deconvolution, some degree of edge effect will still exist...
...The edge effect will be attenuated to a negligible level when the signal in time domain is long enough and the data at edges are ignored.

Sure, those nasty "edge effects" sometimes creep in. Not a big issue with impulse / step response measurements if the measurement included enough "dead time" at both ends of the test and response signals.

For example, do you think you can keep a 10ms 1kHz signal sampled at 48kHz intact in time domain by applying a 500Hz high pass filter?

No.

My point is that, for a short-time signal such as the directly measured impulse response, one has to weigh the accuracy gained and the artifacts caused in the time-domain waveform presentation by the FFT deconvolution of sensors’ non-ideal transfer function.

That may be true for "directly" measured impulse response, i.e., if a dirac was used as the test signal. However, most methods rely on a much longer test signal to achieve a better signal/noise ratio (MLS, sweep, pink noise, etc.). The impulse response is determined from the deconvolution of the DUT response and the test signal. Yet another source for "edge effects" if there is not enough dead time at both ends of the signals.

Again, it is possible to save the FFT/FIR/IIR filtered/compensated data in time domain in MI.

Aha! From your previous messages I was under the impression that this is not possible.
 
Administrator
Joined 2004
Paid Member
From the best I can figure, it's a go.

Why would you buy MI Pro, or why wouldn't you? I looked at what it will do in it's stock state like it was a couple months ago and decided to buy it. The day I was going to purchase it, I saw this group buy. So I've waited for a product I would buy anyway, but now it's greatly improved.

There is a lot to learn with this software package, and I am still learning on the RTX-6001 I have (love it so far!). But the two in combination are a very powerful package. Even if you're working with a sound card, the MI package is very powerful. Adding the Device test plan is what really did it for me. That is what I will end up with, that is unless I win the lottery. :)

So acg, why are you considering the MI package, and what do you want to do with it? From my own investigations, it is the only package out there that is so complete, and at $200 US, it isn't very expensive as software goes either. If you are going to be doing audio testing, I can't see a more capable package out there.

As you can see, I'm #1 on the list and fully intend to remain there. No way I'm backing out.

-Chris
 
Hi Chris,

My interest in MI Pro stems from the RTX unit that I am yet to even unbox (I will one day!).

I am a hobbyist with some amps, phono stages, speakers, pre-amps, dac's, turntables, power supplies etc. to build or finish building and am in no way commercialised nor ever will be: it's just a hobby. Mi Pro is just something that looks good from the outside and to be honest I am too busy to sift through the intimates of selecting software when there is free stuff available such as REW which does ok for me right now and when I realise that I need more experience to determine just what it is that I actually require. Saying that, the MI Pro stuff seems to tick more boxes especially with its RTX integration and when I consider my position on the learning curve I will front up with the $$$ for the GB and hopefully save myself a great deal of consternation and decision making down the track and I'll just be able to get in and learn the software and get my stuff done with least delay.

Otherwise, I'll just wait and spend the time that I don't want to spend to research and make the best software decision that I can. The RTX won't be coming out of its box for a few months so I have time...but it would be nice to just chose something and run with it...

At least those are my thoughts.

Cheers,

Anthony
 
Administrator
Joined 2004
Paid Member
Hi Anthony,
Sounds reasonable. One thing the GB will do for you is help to learn the software at the same time with all the other people who bought the package. Given that you have already spent what you did on the RTX (wise move), the price for the MI Pro software, plus the integration and the Device Test Plan makes an exceptional package. Why the Device Test Plan? So that you can make the same tests without error every time. I can't tell you how often I forget to record something, or I miss a test. It's annoying. Once you get going with it you'll understand where I'm coming from. Of course, if you also do acoustic testing you might very well be better served with the entire MI package - every test.

Now, if I'm not mistaken, buying MI Pro after the GB will not include the integration and it will be another $100 option. So buying with the group will save you not only the 10%, but also the $100 on the integration.

I think MI Pro (member) should check what I've said here as he knows exactly how this is running. I've already made my selections and so I haven't paid as much attention to this as I would if I was still trying to decide. Just being honest with you.

-Chris
 
Well, I've finally had a glance through the MI Pro manual online and there are at least a couple of add-ons that would be very useful for me: Device Test Plan looks good; LCR Meter will prove very useful; perhaps the Vibrometer as well, depending on functionality. Trouble is that I cannot find a manual for the Vibrometer module.

@VIRTINS ...are you able to provide a manual said add-on module? I would like to see how it works.
 
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.
 
Well, I've finally had a glance through the MI Pro manual online and there are at least a couple of add-ons that would be very useful for me: Device Test Plan looks good; LCR Meter will prove very useful; perhaps the Vibrometer as well, depending on functionality. Trouble is that I cannot find a manual for the Vibrometer module.

@VIRTINS ...are you able to provide a manual said add-on module? I would like to see how it works.


Hello acg,

My apologies for not responding to you and others in a more timely manner in the last couple of days, i.e., we’ve been very busy with beta testing of the MI Pro and its custom API that remotely controls the RTX6001, etc., and I’ve lost track of time a bit :)

Anyway, if you’re interested in purchasing MI Pro and two or more add-on modules, it makes a lot more sense for you to just buy the whole MI “full package,” for than you get all the MI add-on modules for basically the same price of MI Pro via this discounted GB and two add-on modules, i.e., MI Pro + all MI add-on modules for ~$450 USD with free updates for life on everything. You would actually spend more $$$ to buy MI Pro and three or more add-on modules vs just buying the MI “full package” instead.

The MI manual has some information on the Vibrometer module per para 5.2.16 of the MI manual. I will ask my contact at Virtins concerning if there is other documentation for it. I have attached a JPEG screenshot of that section of the MI manual for your convenience to this message.

Of course if you have any specific questions about this module, or anything else in MI that you need answered, please feel free to ask and Virtins will be sure to respond quickly.

V/R,

MI Pro
 

Attachments

  • Vibrometer MI Manual Screenshot.JPG
    Vibrometer MI Manual Screenshot.JPG
    105.4 KB · Views: 253
So, the GB sits at 31 out of the necessary 42 with two weeks to go. Are there people signed up from other sites? Will it still go ahead?
Without the GB incentive I doubt I will purchase MI Pro, at least for now.

Hello again acg,

The MI Pro GB is a "go" and no longer requires the 42 minimum order as originally stated as per my previous posting # 148 @ GB for Virtins MI Pro for RTX6001 autoranging/autoscaling & for soundcard end users

I wish to thank anatech (Chris) for his assistance in answering these questions while I was busy with too many other things on my overly long “to do list” at present :spin:

The beta testing is going well thus far (my many things to the entire beta team for their hard work :)!!).

Hoping to see you join the MI Pro GB prior to the end of this month.

V/R,

MI Pro

P.S. With duster1 now joining, we're currently at 32 MI Pro GB'ers and counting.
 
Dear soongsc,

Thank you for posting this message. Your posting caused me to look at the spam folder of my AOL email and for whatever reason both your 6 July and diyaudio end user markus22ch’s 3 July MI Pro GB email orders were both located in that AOL spam folder.

I have moved them to the AOL in-box and, in theory, AOL should from this point forward not send yours or his emails to the spam folder. I have also sent both of you an email confirming the MI Pro GB order along with a JPEG screen capture showing that your respective emails had gone to the AOL spam folder (why, I have no idea??:confused:).

Thank you for bringing this matter to my attention once again, (if you hadn’t, I would never have poked around to find out what the problem was). I have been replying to each MI Pro GB order that comes in with a confirmation email reply (as one would naturally expect).

Wishing you a great day!

V/R,

MI Pro
 
@acg

In addition to MI Pro's reply in Post #231, Section 2.6.2.9 "Oscilloscope Y Scale" of software manual is also relevant to the vibrometer function. Basically, the software knows what kind of sensors are connected in the system through Sensor Sensitivity, which are configured via [Setting]>[Calibration]>"Sensor Sensitivity". For example, if accelerometers are found, then the vibrometer function will be available. The software is able to convert acceleration data to velocity and displacement data through integration. Statistical data can then be derived for acceleration, Velocity and Displacement. The integration is actually done in frequency domain with adjustable integration cutoff frequency in order to avoid accumulated integration errors. Both SI and English units are supported.
 
Bravo, that means that the GB achieved the target and the RTX6001 autoranging--autoscaling goes well!
Dear lemon,

Yes, the auto-ranging and auto-scaling are currently working very well with the RTX6001 and can be turned on or off on demand by the end user. When the MI Pro software is controlling the RTX6001 the front panel controls of the RTX6001 are controlled via software, but the end user can elect to return control via the MI Pro software back to the RTX6001 and do manual knob turning on the front panel of the RTX6001, (and go back again if they elect to with the MI Pro software to having it remote control the RTX6001), etc.

The beta team has been testing the MI Pro integration with the RTX6001 since approximately the beginning of this month with Virtins having released now its 3rd beta version to the team several days ago. The software works in this fashion with both the ASIO or MME drivers.

]We’re currently working on putting out some screenshots and a pdf Quick Start Guide for MI Pro + the RTX6001 and posting such to this MI Pro GB diyaudio forum shortly. The current (draft) Quick Start Guide is 10 pages but that may be modified a bit in size depending on feedback from the beta team.


Only a few days remain for people to join the discounted pricing on the MI Pro software. In addition to the better pricing that already exist for this MI Pro GB there exist another $10 USD discount on top of that for the next 8 people who sign up as per my earlier posting # 74 in this forum, i.e., MI Pro GB orders # 33 through # 40.

Thus far, the majority of people are opting to purchase MI “full package” (i.e. MI Pro + all MI add-on modules too) with free worldwide express / registered mail shipping of the USB dongle to them. For MI Pro GB purchasers’ whom have not signed onto the MI “full package” the majority of them have signed up for MI Pro + the “Device Test Plan” add-on module.

It is important to point out too, that any current individuals whom have already signed up for the MI Pro GB have the flexibility to change their orders until the end of this month, e.g., change for example from MI Pro + one add-on to MI “full package” or whatever. Doing such changes will NOT change their order sequence number (ergo discount per my posting # 74) on the listing. To change ones’ existing order, please just email me your changes before the end of July 2018 to mi_pro AT aol DOT com

Regardless of which MI Pro GB software package a given person ends up choosing to purchase via this GB it is important to note that they get free lifetime updates for that particular package from Virtins Technology.

I hope this answers your questions. If not, please feel free to write back more and watch this space for we’ll be posting something to it here shortly with some screenshots, etc.

V/R,

MI Pro
 
the auto-ranging and auto-scaling are currently working very well with the RTX6001 and can be turned on or off on demand by the end user.


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"?
 
Status
This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.