AviSynth killing me.....

[bluebook]

OK, I know this has been seriously done to death (I've read ALL the guides here) but I REALLY need to convert PAL to NTSC and vice versa.

I am making a complilation DVD from both PAL and NTSC sources, and they don't mix on the same disk.

I have done the following.

AviSynth 2.5.5
both MPEG2DEC3.dll and DGDecode.dll in

Used DGIndex to create test.d2v and my very simple script looks like this

LoadPlugin("MPEG2Dec3.dll")
MPEG2Source("C:\Documents and Settings\Bluebook\My Documents\My Videos\DVD Rips\test.d2v")

Save as test.avs

I load the .avs file into TMPEGEnc and get the following error

MPEG"Source: couldn't open file
("C:\Documents and Settings\Bluebook\My Documents\My Videos\DVD Rips\test.avs, line 2)

I'm stuck here guys.

Oh and if the script is wrong, would someone be so kind as to post some complete scripts for 29.97 NTSC to PAL and PAL to 29.97 NTSC please

You are too kind.....

[Skynet107]

You actually don't need to create an d2v file at all. I don't know the type of source you have so the script will differ depending. AVISynth can import just about any video file including wmv and quicktime, as well as mpeg2 using the directshow option. It would look something like this for a PAL mpeg2 file.

DirectShowSource("c:\file.mpeg")
LanczosResize(720,346,0,0,576,304)
AddBorders(0,67,0,67)
AssumeFPS(23.976, true)

It will be different for interlaced sources etc. Post the exact type of file you have. Make sure you have DirectShowSource.dll, MPEG2Dec3dg.dll, DGDecode.dll etc. in your AVISynth plugins directory.

[NamPla]

Use "AviSource" or "DirectShowSource" instead of "MPEG2Source", as you are opening a "pseudo"-avi file not a mpeg2 file!

[fmctm1sw]

Doesn't TMPG work only in RGB colorspace? In that case you will need a converttorgb24() at the end.

[bluebook]

You actually don't need to create an d2v file at all. I don't know the type of source you have so the script will differ depending. AVISynth can import just about any video file including wmv and quicktime, as well as mpeg2 using the directshow option. It would look something like this for a PAL mpeg2 file.

DirectShowSource("c:\file.mpeg")
LanczosResize(720,346,0,0,576,304)
AddBorders(0,67,0,67)
AssumeFPS(23.976, true)

It will be different for interlaced sources etc. Post the exact type of file you have. Make sure you have DirectShowSource.dll, MPEG2Dec3dg.dll, DGDecode.dll etc. in your AVISynth plugins directory.

I have those .dll in place.

The source file could be all flavours of mpeg2 DVD material, both anamorphic and 4:3 interlaced and not.

But the one I have is an anamorphic 29.97 progressive NTSC at the moment.

Thanks

[mats.hogberg]

LoadPlugin("MPEG2Dec3.dll")
MPEG2Source("C:\Documents and Settings\Bluebook\My Documents\My Videos\DVD Rips\test.d2v")

This is the problem: a d2v isn't mpeg2 (regardless of the source) - and mpeg2dec3.dll fails.

/Mats

[Skynet107]

To save yourself a whole lot of trouble, get yourself a copy of fitcd. It will write the proper scripts for you everytime, regardless of the source.

You still don't state the format of the source file. It it's mpeg2 NTSC dvd format then use a script like this:

DirectShowSource("C:\video.mpv")

That's it. Then set your encoder to 16:9 29.97. (depending on the encoder, it will auto detect the frame rate) but you MUST set it to 16:9 yourself.

[bluebook]

To save yourself a whole lot of trouble, get yourself a copy of fitcd. It will write the proper scripts for you everytime, regardless of the source.

You still don't state the format of the source file. It it's mpeg2 NTSC dvd format then use a script like this:

DirectShowSource("C:\video.mpv")

That's it. Then set your encoder to 16:9 29.97. (depending on the encoder, it will auto detect the frame rate) but you MUST set it to 16:9 yourself.

Sorry, but what do you mean by format then?

The file I want to change from NTSC to PAL is an MPEG2 720x480 video file from a DVD. It is ripped free of it's audio.

I've got Fit CD now, and loaded the file.

It reports it as being what I say above.

I have generated the following - right, or have I clicked the wrong boxes?

# -= AviSynth v2.5.5.0 script by FitCD v1.2.4 =-


DirectShowSource("C:\Documents and Settings\Viv\My Documents\My Videos\New compilation\Blue Man Group\BlueMan.M2V")

LanczosResize(688,544,0,0,720,480)

AddBorders(16,16,16,16)

AssumeFPS(25.000, true)

#Trim(0,6506).FadeOut(150)

ConvertToRGB24() # For TMPGEnc or VFAPI


Thanks very much for the help BTW.

[FulciLives]

Where to begin ...

First of all you need to use the correct dll based on what version of DVD2AVI you are using. If you are using the "standard" version then the MPEG2DEC3.dll should work but if you are using DGDecode/DGMPGDec then you need to use the DGDecode.dll

Also be sure to "point" to the dll file the same way you do with the location of the D2V file. This does not need to be done though (script left as is) if you put the dll files in your Windows System or System32 folder (I forget which ... not sure if it even makes a dfference).

So that right there might be your problem (so far).

Here is a link to the DGDecode/DGMPGDec website: CLICK HERE

As for the AviSynth scripting for PAL to NTSC and vice versa ...

There are 4 possible ways of doing it based on the source:

NTSC to PAL
1.) Progressive 23.976fps NTSC to Progressive 25fps PAL
2.) Interlaced 29.970fps NTSC to Interlaced 25fps PAL

PAL to NTSC
1.) Progressive 25fps PAL to Progressive 23.976fps NTSC
2.) Interlaced 25fps PAL to Interlaced 29.970fps NTSC

My particular expertise (as I like to think) is PAL to NTSC ... I understand how to do NTSC to PAL but in "the real world" I have never done it that way (I live in the USA so use NTSC and therefore do not need to do NTSC to PAL) ... but the concept is the same ... just in reverse

Below is a link to another "old" post of mine that explains how to do a PAL DVD to NTSC DVD conversion using method 1 and 2 as outlined above:

PAL DVD to NTSC DVD Link

I don't think I have ever extensively written on the steps for doing the reverse (NTSC to PAL) ... at least not in such fine detail as the post above (on PAL DVD to NTSC DVD).

However the concept as I said is the same and my method is based on the method discovered/created by Xesdeeni (my hero). So if you can understand my PAL to NTSC scripting you can do the reverse by refering to Xesdeeni's own website guide (which has sample scripts for NTSC to PAL). Below is a link to Xesdeeni's website/guide on PAL <---> NTSC conversion:

CLICK HERE for Xesdeeni's PAL <---> NTSC conversion website/guide

Some notes about Xesdeeni's website/guide ...

It is old. You no longer need to worry about using AviSynth 2.x because there is now a version of the SmoothDeinterlacer.dll for AviSynth 2.5x (at one time this was not so). Also ignore his comments about using WSOLA.exe for the audio conversion (if needed).

If the script is being made for use with Cinema Craft Encoder (aka CCE) then be sure to add this at the end of the script: ConvertToYUY2(Interlaced=true) if dealing with interlaced video ... with progressive video use ConvertToYUY2(Interlaced=false)

If the script is being made for use with TMPGEnc Plus then be sure to add this at the end of the script: ConvertToRGB24(Interlaced=true) if dealing with interlaced video ... with progressive video use ConvertToRGB24(Interlaced=false)

I think I mentioned the following in my PAL DVD to NTSC DVD guide but alot of people seem to make mistakes with the audio conversion so below are some notes on that process:

For the audio (which I hope is just normal 2 channel Stereo/Mono otherwise things get more tricky) make sure you convert to a standard 16-bit 48k Stereo PCM WAV file first before you try to altar the length with BeSweet/BeSweet GUI and then be sure to make the FPS change by going from PCM WAV to PCM WAV. Once you have a corrected PCM WAV file (corrected for length that is) you can then convert it to AC-3 for the new DVD. Also at one time only the BETA version of BeSweet and the BeSweet GUI worked correctly for the FPS change but now the STABLE versions of both work A-OK in this regard. So get the STABLE versions NOT the BETA versions.

My guess is that your home made NTSC DVD is interlaced and not progressive in which case you do not have to altar the audio at all ... just the video. Only when you are going from progressive video to progessive video (either PAL to NTSC or vice versa) do you need to adjust the audio.

If you need any further help post here and I will try to help BUT I really hate "hand holding" so please try your best and experiment ect.

If you do need to ask questions please make them specific ... also posting your actual AviSynth AVS script will be very usefull in troubleshooting.

Good Luck !!!

- John "FulciLives" Coleman

[bluebook]

Where to begin ...<snip>

If you need any further help post here and I will try to help BUT I really hate "hand holding" so please try your best and experiment ect.

If you do need to ask questions please make them specific ... also posting your actual AviSynth AVS script will be very usefull in troubleshooting.

Good Luck !!!

- John "FulciLives" Coleman

Wow - cheers John.

No mate, I don't want my hand held, and am trying stuff as I type here

I have just done a TMPEGEnc with the script posted above, and it changed time duration

This seems to be the problem all along.

I'm editing the audio seperately, 'cause I'm working with the full DTS track and don't want to lose quality there, but would prefer not to have to squeeze or stretch the audio to fit the video, if I can help it.

[Skynet107]

According to fitcd, your file is not a DVD file if it really is 688x544. Also, you have the assume framerate switch set to PAL, so it will encode in PAL format. Is this what you wanted? You also have to keep in mind that because of the unusual aspect ratio of the file, you are going to have black bars on the left and right hand side of the video. (because the aspect is less than 4:3)

Good luck and don't be afraid to experiment.

edit: because you are using TMPGEnc, you MUST ENSURE that it does NOT try to change your frame rate. Make sure it is set to the desired frame rate, and select "do not frame rate conversion"
If you don't do this, you will probably have time sync issues with the audio. Also, if you convert the format, you have to time stretch or shrink the audio as well. (assuming you don't encode the audio using TMPGEnc.

[FulciLives]

Well you can use the INTERLACED scripts even if your source is PROGRESSIVE this way you do not have to change the length of the audio ... however you will end up with INTERLACED output which seems a shame ... i.e., to "destroy" a perfectly good PROGRESSIVE source by making it INTERLACED when you do not NEED to do so.

However I do feel for you in the area of NOT wanting to adjust the length of the audio.

One other thing I should note here ...

There was a thread not too long ago where it was said (not really sure how true this is) that an interlaced 16x9 WS DVD is a "no no" and that a 16x9 WS DVD should only have progressive video (at least on the same "track" or "title").

Now ... I have made interlaced 16x9 WS DVD discs and have never noticed a problem when playing them back on a stand alone DVD player set up on a standard defination 4:3 television BUT these interlaced 16x9 WS DVD discs are pretty much untested on progressive EDTV/HDTV type televisions with a 16x9 aspect ratio (unfortunately I am to poor for such nice things LOL). I did send a sample of an interlaced 16x9 WS video (was an MPEG-2 file with muxed AC-3 audio) to gshelley61 once and he burned it to a DVD disc and played it back on his progressive 16x9 WS television (a plasma I think) and reported seeing no "weirdness".

So how big an issue this is ... I don't know!

- John "FulciLives" Coleman

[Abond]

@bluebook
Don't put in avisynth plugin folder both Mpeg2dec3.dll and DGdecode.dll. They both will be autoloaded and will conflict at Mpeg2 decoding. This probably is the cause for your error.
As you are using DGindex, leave only DGdecode in the folder. A good idea is everytime to test your script for errors in VirtualDubMod (I prefer this, VDub is also OK).
Don't use Directshowsource unless it is the only way to open the file. Every Directshow filter you are using at playback will kick-in and will change the properties of the image before Avisynth. For this reason Directshowsource is also very slow routine.
Well, I have read again your first post. I have made a DVD with two movies - one PAL and the other NTSC with GUIforDVDAuthor putting the movies in different titlesets and a still menu (in PAL ) to select the movie I want to watch. You can do the same, no need to encode with the same properties.

[FulciLives]

Additional notes ...

I hate to say this but there is a lot of wrong information floating about in this thread from other members here.

First of all ... forget the directshow business. Stick with using a D2V project file. As user Abond correctly points out ... using directshow to read a video file into AviSynth does not work all that well most of the time, hence the suggestion to stay away from using it whenever possible.

As for the autoload confusion on MPEGDEC3.dll and DGDecode.dll ... well I have never heard of this. You are only loading one or the other (with the LoadPlugin command) so I don't see "how" they could be confusing AviSynth. I could swear I've used both before without issues but currently my new computer only has one of them on it so I might be wrong here ... but I don't think so.

FitCD is nice but I only really use it when I am converting a downloaded XviD or DivX to DVD format. It is really only "safe" to use in my book when you are dealing with PROGRESSIVE video be it progressive 25fps PAL or progressive 23.976fps NTSC. The scripting it provides for PAL <---> NTSC conversion is worthless when you are dealing with INTERLACED video or de-interlaced progressive 29.970fps NTSC (though I can't imagine a commericially made DVD would ever have that form of NTSC on it but this does happen sometimes with XviD and DivX files).

Also Skynet107's comments on FitCD are really bizarre. For instance the sample FitCD AviSynth AVS script that you posted shows that the source is 720x480 and being resized to 688x544 and then "padded out" to 720x576 yet Skynet107 thinks you are starting out with 688x544 which simply means, in short, that Skynet107 has no clue how to read AviSynth scripting or even how FitCD really works. Not to be harsh but wrong information here is only going to make an already "tricky-to-do" conversion even harder!

So far I have been working on the assumption (based on your comments) that you are dealing with DVD sources here ... but I just noticed that you said that you have a progressive 29.970fps NTSC source in the mix so I'm guessing NOT all of your source material is from DVD (i.e., a direct DVD Rip).

That really shouldn't be much of a problem ... adjusting the AviSynth AVS script accordingly ... from those based on a DVD source to one based on an AVI source etc. BUT ... I have a feeling that the progressive 29.970fps NTSC source is gonna be a tough nut to convert to PAL correctly.

Oh one more thing I need to say ...

The comment made about the TMPGEnc Plus option called, "DO NOT FRAME RATE CONVERSION" is way wrong (sorry again Skynet107). If you are using AviSynth AVS scripting you DO NOT need to checkmark that option! Now that option can be used for PAL <---> NTSC conversion but only under certain circumstances which I would rather NOT go into now otherwise I might confuse things so all you need to know is that this option should NOT be checkmarked.

OK ... I will try to explain WHEN/HOW to use that option briefly since I may be "challenged" by someone on this topic.

It can only be used (correctly) when you import a progressive 25fps PAL source or a progressive 23.976fps NTSC source with the intention of changing from one format to the other.

For instance ... you use the PAL DVD template (in Wizard Mode) but load a progressive 23.976fps NTSC source ... if you checkmark the option, "DO NOT FRAME RATE CONVERSION" the NTSC frame rate will speed up from 23.976fps to 25fps since you are using the PAL DVD template (it will also be resized correctly). This will not drop or add frames (which in such a case is what you want) and the video will end up changing length (i.e., running time) ... audio must also be changed.

If in this same instance you DO NOT checkmark the option, "DO NOT FRAME RATE CONVERSION" frames will be added or deleted ... in our example frames would be added to change 23.976fps into 25fps and if you were doing the opposite (PAL to NTSC) then frames would be dropped to change 25fps to 23.976fps. This is BAD of course with the only "benefit" being that the video will remain the same length (i.e., running time) so audio will not have to be changed to stay in sync. As I said though this is bad (the added/dropped frames) as it will cause strange motion 'stutter' since frames are being added/dropped.

However when you use AviSynth AVS scripting the conversion from PAL to NTSC (or vice versa) is being done within the script.

Example ... if the source is NTSC but the script is converting it to PAL then when you load the script into TMPGEnc Plus (or whatever MPEG encoder you use) it will be seen as a PAL video source ... therefore you would set up the encode as you would if the video source was PAL to begin with ... hence no need what-so-ever to mess with the option, "DO NOT FRAME RATE CONVERSION". In other words DO NOT checkmark it!

I hope this is making sense hehehe

- John "FulciLives" Coleman

P.S.
AviSynth scripting is the most "elegant" way of doing NTSC <---> PAL conversions. It can be done with just TMPGEnc Plus but only when the source is progressive video (though god help you if you have a progressive 29.970fps NTSC source). If the source is interlaced then AviSynth scripting is the only real decent way to get the conversion done well (in good quality with proper frame rate adjustment). Also by learning to do these conversions with AviSynth AVS scripting you open yourself up to the option of using any MPEG encoder that can use such scripts ... not just TMPGEnc Plus. I for instance use Cinema Craft Encoder aka CCE with these scripts.

[FulciLives]

... Well, I have read again your first post. I have made a DVD with two movies - one PAL and the other NTSC with GUIforDVDAuthor putting the movies in different titlesets and a still menu (in PAL ) to select the movie I want to watch. You can do the same, no need to encode with the same properties.

First of all it is totally "out-of-spec" to have a single DVD contain both PAL and NTSC (unless one side is all NTSC and the other side is all PAL but most consumer grade dual sided DVD recordable discs suck ass so you are better off using 2 separate DVD recordable discs).

So putting PAL and NTSC on the same DVD disc is a big "no no".

Will it work though? ...

It can if you do it "correctly" i.e., making sure that you do not mix PAL and NTSC on the same "track" or "title set" but ...

The menu (if you have a menu) has to be either PAL or NTSC and this is where you get into trouble. Not all stand alone DVD players can handle both formats. So having a menu will "muck things up" unless you have a stand alone DVD player that is capable of converting PAL to NTSC or vice versa and you have it set according to your TV ... (or the DVD player is PAL/NTSC capable and you DO NOT convert but have a multi-system TV).

Even if you have no menu not all stand alone DVD players can handle both formats (PAL and NTSC) so again you are in trouble.

In reality this just doesn't work if you intend to have the final DVD work properly.

- John "FulciLives" Coleman

[bluebook]

According to fitcd, your file is not a DVD file if it really is 688x544. Also, you have the assume framerate switch set to PAL, so it will encode in PAL format. Is this what you wanted? You also have to keep in mind that because of the unusual aspect ratio of the file, you are going to have black bars on the left and right hand side of the video. (because the aspect is less than 4:3)

Good luck and don't be afraid to experiment.

edit: because you are using TMPGEnc, you MUST ENSURE that it does NOT try to change your frame rate. Make sure it is set to the desired frame rate, and select "do not frame rate conversion"
If you don't do this, you will probably have time sync issues with the audio. Also, if you convert the format, you have to time stretch or shrink the audio as well. (assuming you don't encode the audio using TMPGEnc.

OK forget the Fit CD bit, this is where I am now.

I have a 720x576 anamorphic progressive .m2v file. This is definite.

I don't care really if the output is progressive or interlaced, But I assume because it's anamorphic to begin with, it will just stay that way as long as the box is used in TMPEGEnc to add the metadata flag.

I wrote the script

directshowsource("<path to file>")
lanczosresize(720,480)
assumeFPS(23.976, true)
converttoRGB24()

If I tick the "don't framerate conversion" box I get an NTSC file which is 3.38 long.

If I don't tick the framerate box, I get an NTSC file which is 4.32 long.

The original PAL file is 4.21 long.

I hate this now, I really do......



EDIT:

FORGET THIS POST! I've just seen the above replies so I'm going to start from scratch.

Back when I have more news. Thanks to all the above replies......

[Abond]

Well, it is going to be an interesting thread. I am seeing you want to convert PAL to NTSC. Well there is a bit easier method. Encode (if you want with avisynth) the pal changing ONLY the resolution - that means do not change the frame rate. After encoding complete use DGPulldown to pulldown 25 fps to... 29.97 fps . Look here: http://forum.doom9.org/showthread.php?s=baf497331c3e5044932ab53f299b0025&threadid=88031
It seems it is working...

[bluebook]

Well, it is going to be an interesting thread. I am seeing you want to convert PAL to NTSC. Well there is a bit easier method. Encode (if you want with avisynth) the pal changing ONLY the resolution - that means do not change the frame rate. After encoding complete use DGPulldown to pulldown 25 fps to... 29.97 fps . Look here: http://forum.doom9.org/showthread.php?s=baf497331c3e5044932ab53f299b0025&threadid=88031
It seems it is working...

I've just tried this.

Started with a PAL file of 1:43:17

And used .avs script to simply re-size the video, and set TMPEGEnc to PAL output.

Used DGPulldown and the file is now.......

1:43:18. Only one frame difference!

I think that just may be good enough.

Does someone more knowledgable than me point out the obvious flaw here......

[FulciLives]

Well I just finished reading ALL of the pages (17) of that doom9 thread.

This is very exciting. A shame I didn't find out about it until just now although that thread did just start less than 2 months ago. In other words this is a very new PAL to NTSC solution.

I can't try it right now though. I'm working on a video project now and then I got another one I need to do after the one I'm working on now so it will probably be a week or so before I can play around with this.

I can't wait to try it

- John "FulciLives" Coleman

P.S.
For those interested you do NOT need to read the doom9 thread. Just go to the following website and download the program. Be sure to read the doc files that come with it!

http://neuron2.net/dgpulldown/dgpulldown.html

*** EDIT ***
Just to explain briefly ...
This method allows one to take a 25fps PAL video source (progressive or interlaced) and re-encode it in such a way so that it is NTSC DVD compatible BUT the new NTSC will be both progressive AND the same length (running time) as the original PAL video ... thus no change at all is needed for the audio.

Normally when you do a PAL to NTSC conversion you either end up with interlaced NTSC (with no change in audio needed) or a progressive NTSC (with a change in audio length needed).

So this solution is very unique and will make things much easier!

[dphirschler]

John is pretty much your guide here. Listen to him. Here is my two cents.

You have two issues here. First you need to be able to load the file into AviSynth. This bit of code works for me.

loadplugin("C:\Program Files\AviSynth 2.5\plugins\MPEG2Dec3.dll")
v=MPEG2source("c:\video\work\bonjovi.d2v")

also this:

LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\MPEGDecoder.dll")
v=MPEGsource("c:\video\work\Boston.VOB")

Here are my NTSC to PAL to NTSC functions:
http://pigseye.kennesaw.edu/~dhirschl/avisynth.html#pal2ntsc
http://pigseye.kennesaw.edu/~dhirschl/avisynth.html#ntsc2pal

Please note that my functions are dealing with interlaced video, not 3:2 telecined film. For that I would receommend working with your progressive source (inverse telecining if necessary).

Also, I have not addressed the audio. It should be a simple 4% stretch for film based material. Other than that, you shouldn't have to change it.

John is probably more experienced than I am. I have done only one PAL to NTSC conversion, but it worked flawlessly. I am currently working on a NTSC to PAL conversion. I have it converted and now I am about to check the audio sync. I'll report back.


Darryl

[Abond]

If your NTSC is film (23.976 fps) with DGpulldown you can pulldown it to 25 fps (the audio will stay in synch).

[FulciLives]

I am SO excited over this new method (gotta love those doom9 gurus) that I created a new THREAD here on videohelp.com to "advertise" this new method.

I was afraid this exciting new news would get missed by a lot of people since this here THREAD makes no mention in the title of PAL to NTSC conversion etc.

Here is the new thread I made: CLICK HERE

@Abond
Have you actually tried this new method yet for PAL to NTSC conversion?

- John "FulciLives" Coleman

[Abond]

Actualy no. I played with a small clip (23.976) and looked afterwards for the duration, audio synch and overall smoothness at playback but... only on computer (not on DVD player and TV). I have a project to try this one, but have no time to start with it.
Erhm, in fact I am living in PAL area

[Skynet107]

Fulci writes an encoding novel. News at 11.

[FulciLives]

Also Skynet107's comments on FitCD are really bizarre. For instance the sample FitCD AviSynth AVS script that you posted shows that the source is 720x480 and being resized to 688x544 and then "padded out" to 720x576 yet Skynet107 thinks you are starting out with 688x544 which simply means, in short, that Skynet107 has no clue how to read AviSynth scripting or even how FitCD really works. Not to be harsh but wrong information here is only going to make an already "tricky-to-do" conversion even harder!

Relax, I was dead tired when I replied. You are not the god of encoding, so relax already.

I'm sorry you took it personally and had to be an ass about it on top of that. Shame on you!

- John "FulciLives" Coleman

[Zisguy1]

You do sometimes come across as a bit condescending, John (at least from here). The habit of capitalizing words FOR emphasis even though it would sound funny IF spoken aloud that way is a little annoying too (but that's just me, lots of people do this and it annoys me every time ).

On the positive side, you're pretty good at cutting through the muddle & clearing up misinformation. Always nice to have someone around who knows what they're talking about.

Just a bit of (hopefully) constructive criticism. Cheers...

[FulciLives]

On the positive side, you're pretty good at cutting through the muddle & clearing up misinformation. Always nice to have someone around who knows what they're talking about.

This part is nice

I pattern my typing after my speech pattern which is based on my idol ... William Shatner

I've been found of Art Bell for a while now too ... Art Bell interviewing William Shatner would be one fun night of radio!

As for the other stuff ... you should have seen me in the past ... as of late I've been really good behavior wise. :P

- John "FulciLives" Coleman