Talk:Frequency modulation encoding: Difference between revisions

Revision as of 07:00, 27 March 2023

Revision as of 08:30, 27 March 2023

Line 24:

::I'd need to read more in this specialized area to make any full informed comment. Lacking that, I can only just throw out possible ideas which I know will be wrong on the detail. One would be to rewrite the first sentence because it conflicts with what you just said. It says that it is a type of coding. So along the lines of "is an approach to storing data on disk drives using manchaster encoding" . An unrelated idea is to change the title to something like "Frequency modulation encoding (disk storage)" to clarify from the more common use of "FM". BTW I'm marking this as reviewed. Sincerely, <b style="color: #0000cc;">''North8000''</b> ([[User talk:North8000#top|talk]]) 13:09, 12 June 2022 (UTC)

== Instance of Manchester codingencoding? ==

I think this article, [[Run-length_limited]] and [[Differential_Manchester_encoding]] say that the frequency modulation encoding is a differential Manchester encoding erroneously. The encodings have the same aim of limiting run-length, but there are obvious differences (presence of the evenly-spaced clock and using sole change of frequency to tell 0 from 1 data bit apart in FME). NeitherNone of the three articles has an inline citation for such claim and I couldn't locate one in Google/Google Books. [[User:PaulT2022|PaulT2022]] ([[User talk:PaulT2022|talk]]) 07:00, 27 March 2023 (UTC)