Wasn't aware that I had done anything like that...Connor MacLeod wrote:Then you shouldn't have insinuated your theory was superior and that you had "proven" the alternate theor(ies) wrong.
Nope, not even remotely. Changes (either a little or a lot) each time someone makes a new post with new information. I certainly don't know everything there is to know about this topic (far from it, obviously), so my ideas (I'm not even going to call them theories anymore) are easily influenced by new information.Connor MacLeod wrote:Your standing isn't very firm, obviously.
Not sure what comprehensive theory I originally posted...all I said is that I've always subscribed to the particle bolt idea, that the beam doesn't necessarily travel at c, and that there is insufficient evidence from ANH and ESB to conclude that the beams are massless.Connor MacLeod wrote:Thats apparently what you are saying now, but you weren't saying that before, and that is what is/was being reacted to. If you are now admitting that your theory is not as comprehensive as you originally asserted, whcih it sounds like you are, then there is no further problem.
*nod* We're basically discussing how to interpret what we're seeing at the moment. But clearly this discussion "depends greatly upon your own point of view"Connor MacLeod wrote:I thought I've shown its *not* inconsistent with the evidence... or rather an interpretation of it.
*nod* But even the ICS books are subservient to the films themselves. The trick is finding an instance wherein there aren't multiple ways to interpret what's going on. The problem with the c beam theory is that it's vague in terms of describing the visible element. If there weren't the visible element problem to deal with, that'd be one thing and I'd almost certainly have no leg to stand on (and probably wouldn't have brought it up in the first place). But the visible element not propogating with the beam seriously bothers me. Either the luxons are intelligent and know when to show a visible element, or there's something else at work here. You later say this (sorry for quoting out of order):Connor MacLeod wrote:Unless you can demonstrate it represents a direct contradiction with a higher-order source, there is no contradiction( And technically, the AOTC ICs is *canon*)
The waste glow is decaying in a manner that is not only consistent with the vector of the beam, but in a manner that is STL in nature and directly presents the visual appearance of a forward-moving bolt. This seems way too specific to be just a "waste glow" side effect of the beam. The particle decay would likely simply give off a general waste glow, creating a more visible ray, such as the 'beams' seen in something like Trek or B5 -- actual rays rather than 'bolts.' Consider the notion: what would cause the particles to decay in just that fashion, more often than not precisely timed with the timing of the beam power ramp-up? It doesn't make sense, given the explanation provided for the nature of the beam. This suggests to me that either the nature of the beam is described inaccurately or that it really isn't moving at c.Connor MacLeod wrote:It can be *used* as a tracer, but thats not neccesarily why its there. Technically its simply a side effect of the beam - the massless partticles are decaying into visible light - hencee the reference of "waste glow".
Well, in order to use the rate of expansion to measure the distances involved, you have to know some reference distance to get a frame of reference for your calculations. We do know Alderaan has a diameter of 12,500 km (based on its Earth-like properties and the statement in the WotC Coruscant and the Core Worlds RPG supplement), so are you saying that you're using that to measure the distances and expansion rate? Further, how does this negate a 75,000km figure, which is allegedly stated in the ANH novelization? I'm very confused as to what you're saying hereConnor MacLeod wrote:But in this instance, I am also referring to other evidence (like the explosion of the planet, and the distances involved there.)
Because we can use the rate of expansion to measure the distances involved, in an approximate fashion, don't you think?
Because the distances involved would be clearly greater than 75,000 km
Well, I consider the canon hierarchy in terms of analogy. The films are flawless depictions of what actually transpired. The radio dramas, novelizations, and so forth are exactingly accurate recreations of these events, to the point where they can almost be regarded as "true," like the film. Then you get the technical journals, such as the ICS and VD books, which we assume to be written by "experts" in the SW universe. Then you get the novelizations, which are written by historical authors, constructing their assessment of what happened based on researched fact. As such, anything in this level is immediately suspect, especially when it comes to technical detail. This type of author would, in my estimation (which is, of course, subjective), focus more on accurately describing the historical events and their figures rather than the technology, which s/he would leave up to the technical journals to account for. As such, it's nice when this type of source does corroborate other information, but when it doesn't, it's very easy to ignore.Connor MacLeod wrote:Doesn't matter what your opinion is. If you're going to ignore it, you have to have a valid reason for doing so.
That's the way I interpret the canon hierarchy under the SoD mentality.
I'm uncertain what you mean here -- I was explaining my approach, reasoning, and what I feel I have thus far accomplished. I'm not entirely sure what your response is meant to indicate. Can you calrify?Connor MacLeod wrote:I've already discussed this in detail. Just what point remains unclear to you, exactly?
Oh, I wouldn't say that's true at all. In research, people focus on very specific aspects of a greater whole all the time. That's simply what I'm doing in this instance -- looking at one particular piece of data and assessing the validity of its accepted interpretation.Connor MacLeod wrote:That's the probelm. You can't focus on just one aspect. That's overly simplistic.
Converting from 24 to 30 fps is called 3:2 pull down. More information here on 3-2 pulldown. It's not a matter of frames being different but a matter of fields being added.Connor MacLeod wrote:It makes a difference. Not only in terms of accuracy (theatrical trailer is the "orginal" cut basically) but it *does* make a difference. timing a single frame at 30 fps is going to result in a drastically different time compared to 1 frame at 24 fps.
I can do a reverse 3:2 pulldown on my footage if you really insist on me doing so and recalculate all my figures. I'm fairly sure they'll remain at least mostly the same if not completely unchanged.
Okay, that's what I figured.Connor MacLeod wrote:Yes, it would, but it would also lead to the beam scattering I mentioned. (plus it would be hard to have an invisible component, since a massless beam moves faster than a particle beam.)
Not based on what threads I've read so far (the one with Marc and then the really long one called "Observed Properties..." that Mad pointed out). At least, not in the same way with the same type of explanation behind it.Connor MacLeod wrote:But they *aren't* flaws. Do you think these considerations haven't been taken into account before?