View Full Version : this is wierd......


Adam Lawrence
February 13th, 2002, 11:59 AM
Hello....

I have a Xl1 which i recently took some footage..i captured
16:9 frame mode.

I did some touch ups in post without reducing the size or
making it widescreen ina 4:3 aspect ratio.

Then i tried outputting it back into the XL1 through firewire.

I get a clean picture but it "jumps" or "skips" here and there.

what could be this problem?

I wonder if outputting back with 16:9 is a problem but
I tried this after reducing the size and reoutputting at a 4:3 ratio
with the widescreen look and i still had the problem with even more of a jump and skip....

Any suggestions?

Rob Lohman
February 15th, 2002, 04:48 AM
Looks like some connection or computer problems to me.
Perhaps your harddrive cannot keep up with the data
stream? Did you capture it without any dropped frames?
(are you really really sure?)

If your harddrive is not the problem your connection
with firewire might be the problem. Some ppl have
reported problems with certain built-in firewire ports.
Sometimes it helps to install a different card. Otherwise
it might be your cable?

Just some suggestions.

Adam Lawrence
February 15th, 2002, 10:38 AM
well...

My machine is brand new with two 17 gig harddrives and 1.6 AMD
256 RAM.

It captures to the machine fine...
I have a wester digital PCI firewire.
Im not sure if it could be the cable..

I might try switching out fire wire cards and and try it then..or switching
cables, and then try it.

I tried outputting some video i had that was stock and 720x480
back to the XL1 and it ran smoothlty...but for some reason the
video i captured is really jumpy.

Don Palomaki
February 15th, 2002, 06:03 PM
Jitttery? Did the field order get reversed?

Adam Lawrence
February 15th, 2002, 06:14 PM
hmmm
field order?

you mean from bottom first or vise versa?

no didnt do much to it but changed the color
thats it..

how would i know if the fields were reversed?

Don Palomaki
February 16th, 2002, 07:57 AM
Field order means whether the even or odd lines are scanned first. Direction of scan remains the same. If the field order is reversed, movement can get a sort of jittery look. Totally still things look OK.

Dan Dorsey
February 23rd, 2002, 10:02 PM
I am experiencing the same problem. I can edit all day ad everything is fine. But when I go to export to my XL-1s or any camera for that matter, it is jumpy and will "hiccup". Please help.

Ed Smith
February 24th, 2002, 11:07 AM
Same problem, here as well, and it would sometimes speed up/ fastforward for no reason.

Has Adobe put a bug in the program or something!? ;+)

Ed Smith

Dan Dorsey
February 24th, 2002, 05:55 PM
Mine speeds up as well. Someone on another board just recommended to try the "print To Tape" feature instead. I think I have already tried this, but it won't hurt again. I had the most success, and almost layed down to tape a seamless 20 minute segment by minimizing my program and clip monitor and playing directly from the timeline to the camera. I shouldn't have to do all of this!

Dan Dorsey
February 24th, 2002, 08:10 PM
When I am sending th Timeline to tape it will flash to the blue screen of my VTR for a second and then run again creating a jumpcut eyesore. I haven't slept in 3 nights because of this.

Adam Lawrence
February 25th, 2002, 10:29 AM
I recently found one of the problems affilated with my output problem..

In after effects when i rendered the movie out the 3:2 pull down was
on...this ofcourse samples yout frames at 24fps...thus giving the jumpy
look when i output to the camera..i rerendered it with the pulldown off
and reexported it.. it seemed to capture fine and smoothly....

but thats the only thing i can think of so far....

Ed Smith
February 25th, 2002, 11:01 AM
The thing is though I am not even using any effects or other programs for this production just simple cuts. The only problem which I thought it could have been was the length (1hr10mins), but now I don't think that would be the problem.

Don't you just hate computers!!! ;+)

Oh well back to the drawing board - or computer.

Ed Smith

Guest
February 26th, 2002, 09:35 AM
I think the problem may be this: The XL1s is not shooting in true 16:9 but rather anamorphic (scrunched by the optically switchable lens.) After editing, you sent it back as a 'true' 16:9 aspect ratio format and the camera did not recognize the code and starting 'hitching' on you.

Adam Lawrence
February 26th, 2002, 10:29 AM
well when i was outputting..i took the 16:9 captured footage and scaled it
down to fit into a 4:3 ratio giving the letterbox look. then re rendered it
to go to output so that might of not been the problem in my situation.
but if it were to happen that sure would interfere with your transfer..

StormFront
September 22nd, 2002, 09:52 PM
I have had my xl1 for about a year, I have the same exact issue as the guy at the top of the thread. THe problem is has got to be something software related, by this I mean OS and drivers. I have been fighting with this for some time now and I am just as frustrated as anyone. I talked to a senior tech at Canon, the only resolution we could come up with is sending to him and they could look at it.

Problem uno:The cam won't come back for a long , long time

Problem 2:They will likely say "it worked for us."

I have hooked my cam up to a DVC deck with firewire and it worked fine both ways. Another mysterious event is sometimes if I re-install servicepack 2 for win 2K Pro everything works correctly, as soon as I reboot problem returns to ruin my life. I can't figure out what changes after I reboot.

So the interface works, it's just picky about the signal.

Just to let you know about what I have tried, I am a IT guy at a television station, that should let you know I HAVE TRIED IT ALLLLLLLLLLLLLLL.

And if you are wondering my current system is a dual proc monster with plenty of moxy. It meets and exceeds all dv editing req's.

In closing I beleive your issue is both the cam being picky about the 1394 signal, and the software on your box not formatting it right. This problem is going to cost me some money. I will either have to invest in a dv deck or a cheap dv camera to use as a deck. Which by the way will work great if you are wondering. The horrible optics of a 500 dollar cam don't matter when you use it as a deck. I used a little JVC that did a good job.

Take a look at this article and let me know what you think.

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q243174&

Jon Eriksson
September 23rd, 2002, 04:49 AM
<<<-- Originally posted by Randall3 : I think the problem may be this: The XL1s is not shooting in true 16:9 but rather anamorphic (scrunched by the optically switchable lens.) After editing, you sent it back as a 'true' 16:9 aspect ratio format and the camera did not recognize the code and starting 'hitching' on you. -->>>


The image size should not have anyhting to do with this - the 16:9 issue is not valid in post since it in fact is the same resolution as 4:3. but the pixels are 'stretched' to a different size.

I hope you guys figure it out (don't use fire-wire myself, so I haven't come across this problem). Good luck!

Jeff Donald
September 23rd, 2002, 05:21 AM
To me this sounds more like computer issues than XL1 troubles. I would suggest that each of you still experiencing problems to post in the appropriate PC or Mac forums here. Your issues could be related to the OS, editing program, hardware/hard drive etc. The more details on OS version, software version, drive brand etc the faster these issues can be solved. thanks and sorry I couldn't help more.

Jeff

StormFront
September 23rd, 2002, 09:20 AM
If it is a computer issue totaly then why do other cameras perform perfectly on the same system??

Adam Lawrence
September 23rd, 2002, 09:36 AM
Ive had this problem in the past and i figured out that it was my hard drive.
I had an old ABIT mother board that didnt support ultra DMA for my hard drive...I would suggest to look into that...I would try updating your drivers.
I ran out and bought a new mother board and everything ran flawless.

Jeff Donald
September 23rd, 2002, 09:39 AM
This topic is 7 months old and in my opinion involves several nonrelated issues. Canon uses a FireWire protocol called Basic. This can cause capture problems for some users. Canon does not provide any updates or firmware updates for the cameras involving this issue. It complies with FireWire standards. However, some NLE software has difficulty with FireWire Basic. The fix is for the software company to provide a fix, update or script. It is my opinion that multiple unrelated issues are being discussed and people may try suggested fixes that are not appropriate for their problems and would waste their time. If everyone posts to the appropriate Mac or PC forum with complete info about their system, computer, software, NLE etc. more detailed and appropriate help may be forthcoming.

Jeff