Oh, wow, well thanks for the heads up for MATAA! However, I am totally against "we should all use the same software". Also, MATAA was certainly not made with user friendliness in mind, and I don't think Matlab/Octave is for everyone. But yeah, I prefer MATAA over everything else ;-)
Absolutely. But a community-driven project depends on the number of users/contributors. 😉
Still, MATAA can not replace a real-time analysis software and this is what most RTX-Users will focus on.
Still, MATAA can not replace a real-time analysis software and this is what most RTX-Users will focus on.
SY, reviewed this product Multi-Instrument, a powerful multi-function virtual instrument software - Virtins Technology
in Linear Audio
DT
can't find the review, must be somewhere else
in Linear Audio
DT
can't find the review, must be somewhere else
Last edited:
I can report that the RTX works well under Linux. I'll do some of my basic DAC tests shortly.
Testing the ADC under Linux will need to wait until I get a suitable software package running.
It does sound very good on a quick superficial test.
Testing the ADC under Linux will need to wait until I get a suitable software package running.
It does sound very good on a quick superficial test.
I just updated Win 10 to the creator update to see if the new USB UAC 2 driver worked. It doesn't at this time. . .
I did a set of RMAA loopback tests at 192-24. The levels are all very close to clipping so not the best possible performance. I generated an HTML report but don't know how to share it here.
The 60 Hz noise is lower in the +20 dB in/out. Its really low in any case.
Here is a summary at least:
I did a set of RMAA loopback tests at 192-24. The levels are all very close to clipping so not the best possible performance. I generated an HTML report but don't know how to share it here.
The 60 Hz noise is lower in the +20 dB in/out. Its really low in any case.
Here is a summary at least:
Attachments
That's getting a bit off topic, but (1) why do you think that most users will focus on real time analysis and (2) why would MATAA not be suitable for this?
I know my needs fall into the following categories,
1. Adequate management of measured data to collectively study the factors that influence sound coloration, and weight them.
2. Conduct series of measurements integrated into a design process to linearize the total system as much as possible.
3. Real time monitoring and logging of data to catch problems.
4. Criteria based data capture within a range before and after the criteria occurs.
5. Quality control metrics of measurements.
Sent from my iPhone using Tapatalk
1. Adequate management of measured data to collectively study the factors that influence sound coloration, and weight them.
2. Conduct series of measurements integrated into a design process to linearize the total system as much as possible.
3. Real time monitoring and logging of data to catch problems.
4. Criteria based data capture within a range before and after the criteria occurs.
5. Quality control metrics of measurements.
Sent from my iPhone using Tapatalk
Hello All,
What do you folks mean by "real time"?
By definition FFT is in the frequency domain, not time.
DT
What do you folks mean by "real time"?
By definition FFT is in the frequency domain, not time.
DT
There are many perspectives as to what "real time" refers to. Mostly, "as it occurs" is considered real time which you can associate the time stamp when it occurred and respective to other events occurring, but when you get to control systems, control loops are strictly controlled in different ways to preserve the gain and phase margins in multiple loops.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
Last edited:
Real-time means being capable of capturing spurious events as well, which many analyzers cannot do. In spectral analysis of e.g. EMC one would need to capture burst events that are not periodic. For audio this could be useful depending on application.
Whoa, that was 10 years ago! MATAA is still doing its tricks in my workshop...
I didn't like how aX scrambled the MATAA command examples in their layout. If you also don't like it, you can take a look at my original text before aX layout happened.
In this context I understand "real time" as "show and process the data at the same time as things happen". Like in the attached video, which I made using playrec with GNU Octave on my Linux laptop mic/soundcard (quick and dirty!).
Oh wow, nice video. I was not aware of this Octave add-on. I would consider this kind of acquisition as real-time too.
For my purposes "real time" means for example seeing the effect of adjusting the distortion trim on an ultra low distortion oscillator as I adjust it.
With a Shibasoku 725 the meter responds immediately as I adjust (probably 10 - 50 mS delay but its not perceived). Some software will show changes pretty quickly. Others really require running a test, processing and then displaying. Depending on the test that may be quick or may be really time consuming.
I hope this adds clarity.
With a Shibasoku 725 the meter responds immediately as I adjust (probably 10 - 50 mS delay but its not perceived). Some software will show changes pretty quickly. Others really require running a test, processing and then displaying. Depending on the test that may be quick or may be really time consuming.
I hope this adds clarity.
Real Time is kind of a squishy topic
Real Time is kind of a squishy topic.
I recall, back in the day, I would walk across campus to the computer center and drop off a batch of IBM punch cards. Next day I would walk back across campus and pick up the cards and if I did not make any errors I would also get a print out. With the overnight latency there was no sense of real time analysis.
Real time is like real money, you do not want to spend it waiting.
DT
Real Time is kind of a squishy topic.
I recall, back in the day, I would walk across campus to the computer center and drop off a batch of IBM punch cards. Next day I would walk back across campus and pick up the cards and if I did not make any errors I would also get a print out. With the overnight latency there was no sense of real time analysis.
Real time is like real money, you do not want to spend it waiting.
DT
Real Time is traditionally used for software. Those fancy self-drive cars have real-time software. They better have!
The software that updates your account statement after you take money from an ATM doesn't need to be real-time.
The opposite of real time processing is batch processing. Banking software traditionally is batch-processing, like reconciling all accounts overnight. However, even banking software is slowly moving towards (almost) real-time processing.
Jan
The software that updates your account statement after you take money from an ATM doesn't need to be real-time.
The opposite of real time processing is batch processing. Banking software traditionally is batch-processing, like reconciling all accounts overnight. However, even banking software is slowly moving towards (almost) real-time processing.
Jan