>"I was responding to the claim that .dv doesn't work - just correcting wrong information."
We like to inform people how to make media that works right in FCP, without any issues.
If you need to render anything on the timeline, then something isn't right. That's clue #1 that a setting is wrong. Why convert the footage to .dv and then need to render it before you work with it, and whenever you make any changes to it, rather than encoding it right in the first place...to something like DV/NTSC (what FCP works with in terms of DV) or ProRes?
Yes, it works. But it doesn't work flawlessly, and can lead to issues later on. This is why we tell people to avoid doing that...by saying it won't work. Sure, I guess we should say "it's far from ideal, you will be doing a few more steps than needed to get it to work, and you will constantly be rendering...but if you do it this way, you won't need to do any of that."
And yes, we "get in a rut" when explaining how to do things properly...because we want to help you do things to be right, properly. Let's compare this to building a house. Yes, you can use one kind of wood over another, and no, you don't need to measure exactly in order to get the studs in place. Will it work...yes. Will it be stable and last? Questionable.
There are right ways of doing things. If you choose to ignore our advice on what the proper ways of doing things are...fine. That isn't going to stop us from saying that certain ways of doing things is wrong and won't work....because they are wrong. FCP isn't designed to work with .DV files...that's the realm of iMovie. FCP prefers DV/NTSC...and since you are converting footage to be used in FCP...why not do it right to begin with? Instead of wrong and then doing extra things to allow it to work "OK?"