User talk:MoreNet

From Wikipedia, the free encyclopedia
Jump to: navigation, search



Hello, MoreNet, and welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Here are some pages that you might find helpful:

I hope you enjoy editing here and being a Wikipedian! Please sign your name on talk pages using four tildes (~~~~); this will automatically produce your name and the date. If you need help, check out Wikipedia:Questions, ask me on my talk page, or place {{helpme}} on your talk page and ask your question there. Again, welcome!  - Ahunt (talk) 23:22, 2 January 2010 (UTC)

Canvas element[edit]

Okay, look. There are a number of problems with your edit. For one, it's poorly written; "For 3D graphics, there is WebGL. Natively supported by Mozilla Firefox, Google Chrome, Safari, and Opera. See also support for legacy browsers." is just sentence fragments. Second, you're adding a whole bunch of external links in your legacy section that violate the policy on external links. The page isn't meant to be an advertisement for things like that. Stop adding this text. — HelloAnnyong (say whaaat?!) 07:05, 5 March 2010 (UTC)


Could you explain "incompatible"? I believe it is highly misunderstandable.--Regression Tester (talk) 23:49, 6 September 2011 (UTC)

FFmpeg, libavcodec, and libavformat projects are split to and at March 13 2011. They both release same name "libavcodec" software, but their APIs are changing gradually, and they are incompatible. --MoreNet (talk) 05:21, 7 September 2011 (UTC)

The API is completely compatible between FFmpeg and libav. Or can you give an example that this is not true?--Regression Tester (talk) 09:31, 7 September 2011 (UTC)
For example, line 453, is using avformat_alloc_output_context2(), but this function does not exist in and using avformat_alloc_context() in --MoreNet (talk) 17:45, 7 September 2011 (UTC)
So what you are saying is that they are not incompatible but that libav only provides a subset of FFmpeg's features? (This was the original intention: The fork happened when additional libavfilter features where added to FFmpeg that users wanted but some developers were against.) This information probably makes sense in the article, don't you agree?--Regression Tester (talk) 13:42, 8 September 2011 (UTC)


As I understand the libav homepage, they do not claim to provide FFmpeg, so I am not convinced the information you added makes sense in the FFmpeg article.--Regression Tester (talk) 23:51, 6 September 2011 (UTC)

Same as libcodec. As and split, Libav is releasing "ffmpeg, avconv, avserver, and avprobe" tools. Both releasing command line tool "ffmpeg". is not the project for libavcodec. and are both "ffmpeg" projects. In Ubnutu 11.10, software is released by the package name "ffmpeg". MoreNet (talk) 05:28, 7 September 2011 (UTC)

I understand what tools libav is providing (note that they have deprecated ffmpeg, so in the future, they will not provide any of the tools that originated in FFmpeg). What I mean is that there is an article called FFmpeg and you added a lot of information about a project that claims it is not FFmpeg. I wonder if that makes sense.--Regression Tester (talk) 09:34, 7 September 2011 (UTC)
At they say "ffmpeg will be kept in its current state for some time, so no scripts or frontends using it will break. However it will not be developed further." Are you really sure they will "in the future, they will not provide any of the tools that originated in FFmpeg"?
I suspect, that is what deprecated means, yes (after some time ).--Regression Tester (talk) 13:39, 8 September 2011 (UTC)

Disambiguation link notification for October 29[edit]

Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited WebSocket, you added links pointing to the disambiguation pages Python and Haskell (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 11:14, 29 October 2012 (UTC)

Apple A7 memory technology[edit]

I noticed that in this edit you added the fact that the Apple A7 has a single-channel 64-bit memory interface. I was wondering, where did you find out the A7 has a single-channel 64-bit interface as apposed to a dual-channel 32-bit interface. Your change might be correct, but while I agree that the A7's memory interface is 64-bits wide (that fact appears in the current citation), couldn't it be either 1 x 64 or 2 x 32? It is known that the A7 package in the iPhone 5S has two Elpida 4 Gb LPDDR3 chips. So two chips each with a bus width of 32-bits seems like it could be a possibility. If you could provide a source for the fact that the A7's memory interface is actually single-channel (i.e. 1 x 64), that would be great. —RP88 (talk) 02:23, 23 September 2013 (UTC)