FR-AV 2 Question

[-mjk-]

lol, it's not "some enigmatic software thing." Somehow the system file is being deleted. It happens with the DP-24/32 also.

But I don’t see why it should happen at all. Seems to me it’s something that should happen under the hood, with no need to trouble the user.

The machine is telling you the problem, you just have to stop theorizing and troubleshoot it.

In normal operation there is no reason for that file to be missing. It is somehow being deleted. We have seen this on the DP machines. If it's missing it will be recreated on the SD card, but the point is, it lives on the SD card.

 

[Regal1956]

Troubleshoot what? Nowhere in the user manual is there a description of this problem. And when this warning appears, I simply press the F4 button, the warning disappears and I’m able to record with no further interruptions. So what’s the point of this warning screen?

As for “stop theorizing and troubleshoot it,” if neither the user manual nor anyone else explain what this warning screen means, how am I supposed to troubleshoot? Forgive me for saying this, but you’re faulting me for not knowing what no one is telling me.

In fact, I’ve apparently solved the problem. Pressing F4 makes the screen go away every time, and I’m able to get on with recording. So my objection is that this warning is pointless. It requires a user action where no alternative action is possible. Software engineers have a variety of terms for such pointless steps: digital hurdle, micro-interaction friction, unnecessary complexity, user friction. All these terms describe the same thing. They’re a violation of the “Keep It Simple, Stupid” axiom for good software design.

 

[Mark Richards]

What mj, a professional audio engineer, is telling you is that it's not normal for the system file suddenly to not be on the SD card.

You need to find out *why* it's happening.
Either
1. You are somehow inadvertantly deleting it; or
2. The SD card is not a tested/approved card, and erratic behavior results; or
3. The firmware is not up to date; or
4. You have a defective unit.

You can troubleshoot 1,2, and 3 yourself. If that yields no joy, then it could be 4, and at that point only TASCAM support can resolve it.

If you continue to "just press F4", you may come to seriously regret taking the easy way out. The message is a warning something is very wrong, and the operating system just saved your bacon.

ps TASCAM is no longer known for producing steller user manuals. We try on this site to help overcome the deficiencies of TASCAM's user manuals, most times successfully; but sometimes not, in particular concerning TASCAM products with which we don't have hands-on experience. But we try.

I have no experience with your recorder, nor do I have the user manual handy. But I do know that where necessary for the product, TASCAM places information about the use of tested SD cards at the beginning of the manual; and usually provides a complete list of messages, error codes, and their meaning at the back of the manual. I'm surprised (but maybe I shouldn't be) that something as important as the system file message isn't there.

 

[Regal1956]

Okay, I just spoke to Sweetwater (where I bought my FR-AV 2) tech support. The tech support person seemed as mystified as I am, and said Sweetwater would send me a replacement. So we’ll see if my current device is in fact defective.

Just to frame this situation from the view of a user with no software or technical training, please consider the following.

Here’s the warning screen I’m seeing:
File Not Found
Make System File

But in the user manual, here’s the closest thing I can find to what I’m seeing:
File Not Found
The file was not found or might be damaged.
Check the relevant file.

First, notice these aren’t the same message, and they’re telling the user to do two different things. “Make system file” isn’t the same as “check the relevant file.” Second, in either of these directives, what precisely is the user supposed to do? There’s nothing here a user with no specialized training would understand. The manual offers no clear procedure for carrying out either of these directives. So neither are actionable by the user in any realistic way.

A common mistake in user manuals is to write as though addressing people who are already experts in the device being described. Too often, technical writers make no real effort to put themselves in the shoes of users confronting a complex device for the first time. I hasten to add that, as one who’s written an instructional method myself, I understand how hard this is to do. Writing a good instruction manual is an art unto itself. That said, many companies clearly regard user manuals as an annoying detail, to be done with little effort and expense.

I’ll close with a suggestion to tech experts. When talking to non-experts, please understand that we don’t always share your deeper understanding of the matter at hand. For example, if I’m talking to non-musicians about composing music, I don’t assume they know what parallel fifths are. Though it’s basic knowledge to me, it isn’t to them. So I meet them at their level, not mine.

Tech experts are wise to do the same.