Working isn't the question, last weekend I was helping someone who recorded a short demo piece at 24/96 (and the file said, actually, 32bit/96K) but was brickwall filtered at 22.05KHz and was 16bit (but it was 96k). Sound stuff under Win gives a lot of folks problems without giving any warnings.
Don't get me wrong lots of things might work but there are some that have gone months and even years under an illusion of working.
Last edited:
Latency is happening "outside" of MATAA, depends on the operating system and audio driver software. Take a look at the mataa_audio_guess_latency function to figure out the latency of your set up.
...then you fix it
Sure, mataa_import_FRD does it. In fact, *.frd files are just an ASCII, so importing to Octave is trivial.
Then something was wrong with your configuration. Take a look at the manual. And check your set up using the mataa_selftest function.
Anything recent will do. I am usually running 4.0 or 4.2, but I started MATAA development with 2.x.
Not sure what you're referring to. MATAA+TestTone will do 24 bit out of the box. Or 32 bit.
Depends on how you define "good enough". The data quality (sample rate, sample depth) are the same with TestTone or PlayRec. TestTone is a bit slower, because it shuffles data between Octave and the audio hardware by writing/reading to/from files on disk. That's slow, but works very reliably on all kinds of different platforms.
I guess it would be best to stop these off-topic disucssions in this thread. Please either start a new thread about MATAA (let me know!), or go to the MATAA mailing list. Let's focus this thread to the OP question.
- Status
- This old topic is closed. If you want to reopen this topic, contact a moderator using the "Report Post" button.