Page 1 of 1

Photoshop vid exports: one loads into VS and another doesn't

Posted: Fri Jun 19, 2009 2:59 am
by jbarchuk
Hi All!

This is an **EXTREMELY** long post because I include a ton of SUPER(C)
analysis data from 3 vid files, some detailed 'differences' between those
analyes, and a complete dxdiag at the very bottom of the post. if you reply
please don't quote much. LOL!!!

Details: Toshiba P35 laptop/XP-Home-SP3/2G RAM, VS Pro X2, and Photoshop CS4
Extended. Original vid recorded with Panasonic GS400 and ported into PC via
VS. I have *never* (ever-ever) run any 'wacky-funky internet downloaded
codec file.' Everything is stock-normal from Bill, Corel, and Adobe.

I don't know if VS or PS is the 'cause' of this problem though my intuitive
guess is that it's PS because I'm -experiencing- the problem under VS with a
file -created- -by- PS. But I can't fix it unless/until I know what the root
problem is. So if I can completely define the problem then I can go to the
PS forums to find the fix/cure.

Problem: Original file and one file video-exported by PS load just fine into
VS library, and another file created by PS doesn't. A short 30 second clip
exported from PS imports into VS library perfectly fine. But the full length
35 min vid exported by PS returns the scary 'not accesible' error.

Actually I made the long vid first but when it wouldn't load into VS I made
the 30 sec version for testing/troubleshooting purposes. When that one -did-
load into VS I am simply further baffled.

That error message is almost more annoying than any error itself. Hitting
'OK' returns 'unknown file format' *OR* 'not enough memory' *OR* 'copy
protected.' Well don't tell me what it *MIGHT* be tell me what it **IS**!!
Duh. I'd rather the whole thing crash out to a BSOD than tell me 'I'm sorry,
Dave, I can't do that for you.'

OK so I know it's not copyrighted because I created it myself, and there's
enough memory because I can load the original unshopped (same length) AVI
just fine, so it's gotta be a format/codec problem. Maybe. I think. LOL! No,
really, I have no clue. :) Or, maybe there's some other problem VS 'doesn't
know how to tell me about.'

Below I'm posting aaallll the gruesome details as reported SUPER(C)
'expanded analysis' of the original and both shopped files because I have no
clue what might be significant. But I'm leaving the audio portion out of the
original file because the shopped files report no audio tracks. (Is *that* a
'problem' for VS????) Nope, can't be that, as I said the short shopped
version has no audio and it loads fine.

Another possibly interesting note, the -original- file has -65749- frames
and the -shopped- file has -65750- frames.

But before you see all the details, to make analysis of all this SUPER(C)
info a little easier, I created three text files:

(a) original
(b)30 sec clip
(c)full length shopped version

...and ran a few greps on them to see some possibly significant differences:

A few items had identical data for all three files such as Kind of stream:
General, Stream identifier: 1, Count of video streams: 1, and I removed
those few lines from the reports.

Hmmm is these a clue? I see a few items where the a and b files are the same
and the c is different.


Yeesh that's a ton of data, I home someone sees something 'odd.' Any clues
here?

TYIA. Have a :) day!

Jim

That was a post that was too long. I've deleted all the superfluous text. Dump files, and the like have no meaning to members and staff of this web board. If you think you must post those files, zip them up into a text file, and attach the zip file. The best solution is to email those files to Corel, they are intended for the developers, not users.
Ron P.
Administrator

Posted: Fri Jun 19, 2009 9:51 am
by Trevor Andrew
Wow

From Video Studio do this

File ¡VPreferences-check Show Messages when...............
Start a new project

Insert the first video into the timeline

From the pop up window¡Xselect details, copy and paste the right hand panel to the forum

Repeat this for the other video files.

Remember to start a new project.


Wow

Posted: Fri Jun 19, 2009 11:44 am
by Clevo
Yeah we need to compare how Vs interpretes the video file properties to the above.

Can I ask what are you doing in PS CS4?

Posted: Fri Jun 19, 2009 11:54 am
by mitchell65
jbarchuk wrote:Original file and one file video-exported by PS load just fine into
VS library, and another file created by PS doesn't. A short 30 second clip
exported from PS imports into VS library perfectly fine. But the full length
35 min vid exported by PS returns the scary 'not accesible' error.

I use Adobe CS3 and you can't edit videos in Photoshop CS3. I'm surprised that PS CS4 can handle video as I thought you would use Premier Pro for video.

Posted: Fri Jun 19, 2009 3:46 pm
by jbarchuk
Hi All!

Thanks much - responding to several replies...

> File .Preferences-check Show Messages when...............
> Start a new project
> Insert the first video into the timeline

Didn't know about that popup detail box. Handy-dandy for checking
incompatibilities like this for sure.

*UN*fortunately I got little more than more wacky/inconsistent feedback from
it. [sigh]

For the -original- AVI uvs090131-001-org.avi :

Microsoft AVI files
24 bits, 720 x 480, 4:3, 29.97 fps
Lower Field First
DV Video Encoder -- type 1
DV Audio -- NTSC, 32.000 kHz, 12 Bit, Stereo

For the shopped 30-sec clip uvs090131-001-org-30sec.avi I got no popup!!!
Nothing/nada. I tried every possibility of 'new project' I could think of:
blanked out the timeline and library, even restarted VS, it simply wouldn't
produce a popup when dragged to the timeline.

Then worse, for the full length shopped AVI uvs090131-001-after-ps.avi I got
the -same- ...'not accessible' when adding to the library, and -no- 'info'
popup!!. Uuuurrppbbbttt...

That was half-why I included all that SUPER(C) info in the hope that it'd
have -some- relevant info.

Maybe for both the no-popup and the 'inaccesible' problems there's some
temp/cache subdirectory I can clear out? I do system tools - cleanup once in
a while but I just noticed I've got *1G* of Documents And Setting - Local
Settings - Temp junk laying around but actually nothing that looks related
to VS or Corel.

> Can I ask what are you doing in PS CS4?

> I'm surprised that PS CS4 can handle video

I shoulda been clearer but I thought it was obvious I meant 'extended.'

Been using VS since V6 for vids but not much with filters/effects, and was
having another problem with *that* that I'm *not* gonna get into here (maybe
another topic grumble-grumble.) Been using PS since CS2 which is obviously
the purely awesome gold standard for stills. Video editing started with CS3
Extended but at the time I missed the less expensive upgrade window. So I'm
trying the CS4E and might upgrade to that just for the stills but also
wanted to try the vid editing. PS *can't* do the 'project level' editing tha
VS can do - and it *shouldn't* IMO. But if I can get better
filter/sharp/layer qualities from the PS stills processing techniques than
from VS then it's worth the extra time involved.

When this Q gets solved I'm gonna delete all the above -unnecessary-
detailed file info so it doesn't get found by the search engines. LOL!

Have a :) day!

Jim

Posted: Fri Jun 19, 2009 4:19 pm
by mitchell65
I have never been able to get the "Show message etc" Pop up to work. The appropriate box in Preferences is checked! As it's never worked I don't miss it!

Posted: Fri Jun 19, 2009 4:58 pm
by Trevor Andrew
Hi Jim

The option to show messages, if it generates the info window then the inserted file is compatible.
By that I mean the video properties are suitable for setting the project properties in video studio.

Your first successful video showed:-

Microsoft AVI files
24 bits, 720 x 480, 4:3, 29.97 fps
Lower Field First
DV Video Encoder -- type 1
DV Audio -- NTSC, 32.000 kHz, 12 Bit, Stereo

Bog standard DV-Avi files, probably from a Mini DV type camcorder.
I would have expected 48.000 kHz, 16 Bit, Stereo for the audio, that¡¦s set in the camera.

For the second video at least you were able to add it to the timeline.
Right click this file and select properties. What are they? Compare them to the original.
Is there any difference?

The third appears to be totally corrupt, having incompatible/incorrect properties.

I haven¡¦t got my head round why your using third party software to edit your original video file.
The original DV-Avi video file is ideal for VS editing.
In fact DV-Avi files are the best video files that can be edited, giving no editing problems.