Help! "Contains unsupported media or has an invalid directory structure"
I have FCP 7 and I'm trying to Log and Transfer HD video recorded on a Canon 5D. I keep getting "contains unsupported media or has an invalid directory structure."
Any idea's?
Okay... I'm still getting the same message.
This is what I'm seeing...
Similar Messages
-
"00004.MTS" contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media.
when i try log transfer from a sony nex-vg10 but my buddy can do it with no problem on my cam an macIf you copy the recordings from AVCHD cameras, you must copy the entire storage device with its directory structure intact.
I have even tried copying BACK files onto the camera and they do not show up in the transfer window under the last clip.
There is no information for those clips in the AVCHD storage device's directory index files. That means there is no way for the computer to find them.
Your last resort is most likely [ClipWrap|http://www.divergentmedia.com/clipwrap] now, unless you can get the storage device exactly back into the state it is supposed to be according to the index file. -
"AVCHD" contains unsupported media or had an invalid directory structure
"AVCHD" contains unsupported media or had an invalid directory structure
I brought this error message upon myself... and am looking for a way to recover the files and access them in Final Cut Express. I have successfully processed video in the past.... so it's operator error.
How did I mess it up? By treating my video files the same way as I treat my jpg files.... Creating a new folder for each day's shooting, and simply moving the files into the folder.
I preserved the CLIPINF and STREAM files.. but discard the the rest of the files.
I tried recreating the file structure but that hasn't seemed to work. I'll buy a new card, reformat it, and use that as a template for file structure, but that will take a few days.
So .. I have put the files into the following file structure, but that doesn't seem to work because I have tossed the other supporting files when I "cleaned up" my 8GB Flash Card.
AVCHD
BDMV
CLIPINF
00051.CPI
00052.CPI
00060.CPI
STREAM
00051.MTS
00052.MTS
00060.MTS
Have tried to recreate the file structure, but of course the contents of other files are incorrect
AVCHD
BDMV
CLIPINF
INDEX.BDM
MOVIEOBJ.BDM
PLAYLIST
STREAN
AVF_INFO
AVIN0001.BNP
AVIN0001.INP
AVIN0001.INT
So... my questions are simple:
1: Can I recreate the data and reindex the files from the STREAM and CLIPINF files?
2: If I can, how do I do it?
3: If I completely destroyed the integrity of my video... let me know that too.. I'll have lost 9 months of work... but it will keep me from screwing up the video on my next trip!
Thanks
Ira Serkes
[email protected]This may or may not apply, but I recently had this problem as well and found a solution that fixed the camcorder back to its original settings, though it only works if 1) the camera worked with Log and Transfer at some point and 2) you are paranoid like me and saved your raw mts files.
Though I had been using the camera for about a month using Log & Transfer perfectly well I used the Finder to delete all the files, which I thought would be faster than using Delete All in the camcorder. When I turned the recording on the camera said it needed to reformat its Image Database, so I punched Yes. Then after I recorded the L&T window said invalid directory structure.
What I eventually did was drag the entire contents of the hard disk off into their own folder (with the date and the camera name) and then pulled an old copy I'd made of working movie files back onto the hard drive. Then I used the camcorder's Delete All function, and then dragged all the contents of the folders with my new footage into the corresponding folders of the camera's hard disk. I was once again able to use the L&T function (even with the old semi-corrupt data), and also any new footage I record is A-OK, even after the camera has asked me if it can (once again) reprogram the Image Database.
I can't explain it, but possibly there are hidden files connected to the files we can see (possibly viewable in the Terminal if you speak Linux) and when the camera comes from the factory they make it good and when the camera tries to do it on its own it doesn't work so well. In short, maybe the camera is a little unstable. -
"Invalid directory structure" AVCHD with Log & Trnasfer FCP 7
i was brought a hard drive with AVCHD files. i have been trying to import those AVCHD files into FCP 7 using the Log & Capture tool, but whenever i select the AVCHD folder i am told ""No Name" contains unsupported media or has an invalid directory structure. Please choose a folder whose directory structure matches supported media."
i have been trying to find out what the correct directory structure of AVCHD files should be.
here is what my folders look like:
AVCHD > BDMV > (contained within the BDVM folder) BACKUP, CLIPNF, PLAYLIST, STREAM, INDEX.BDM & MOVIEOBJ.BDM
is this structure correct? how does one interlace that footage once it has been imported into FCP? the video was shot in interlaced but i have to work with it in ProRes 422!When a camera's card is archived to a disk, it must be the entire card, not just the folders within it.
This is best achieved by making a Disk Image.
When you use Log & Transfer, select the card, not the folders inside. Or in this case, you might get away with selecting the hard drive itself.
have to work with it in ProRes 422!
ProRes also works with interlaced footage. -
Invalid Directory Structure Error
So I recently purchased a Panasonic AG-HMC40 and it's my first experience with a non tape camera. When I tried to get the footage onto my computer Final Cut wouldn't recognize it. It worked in iMovie but I would rather not lose quality by transferring it through that first. When I try to open the folder within the log and transfer screen I get an error message that says that it contains unsupported media or "Invalid Directory Structure." I'm on FCP 6.0.5.
I quite believe it.
Can you exactly describe what you're doing and how FCE behaves?
Do you see a preview of the clips after connecting the camera?
Try to import using iMovie, when this works, it should in FCE somehow, too.
I googled a bit around and found someone having the same problem (but unfortunately in german language).
He has formatted the SD card using the camera, then it worked. But the clips beeing on the SD card before are still lost. But if you backup before, you can convert the .mts files into .mov and then import it into FCE.
Some other possible source of errors:
- is the HF 100 power cable connected for transfer? (it has to be)
- did you see the "mode selection" screen when connecting to your Mac?
- if yes, did you select the "PC mode" there?
- does the USB port you are using work with other devices?
- can you try using an SD Card reader instead of the camera?
- do you see the camera device icon after connecting to your mac?
- can you try it on another Mac if it works? (if not, it may be a manufacturing issue)
At moment no more ideas... -
LOG AND TRANSFER [invalid directory structure warning]
I have just learned to use media manager and have cleaned out and archived some of my p2 and projects in FCP. I went to log and transfer some footage and am getting the message.
"This file has invalid directory structure. Please choose a folder whose directory structure matches the supported media??
PREVIOUSLY, before I became familiar with media manger, I had gone through files, P2 contents files and taken out some audio files that i know I didn't use. I discovered this is a mistake and returned all files but one to their appropriate contents files. One of them, I couldn't find where it came from so I just took it out of the trash and placed it on the source hardrive where all my P2 footage is stored.
Is this lone audio file causing the warning message? Please help.
catherineShane, out local P2 wonk, will chime in if he's dealt with this but you need to talk to Panasonic.
bogiesan -
Anyone know what 'Invalid directory structure ' means?
Hi
I am trying to solve a problem with some P2 media I am trying to import from external hard drive to FCP 5.1.2.
I have 21 reels of it - all labeled in a similar way - but only one (of the 21) isn't importing and gives me the following warning (from FCP).
"name of my folder/ reel" has invalid directory structure. Please choose a folder whose directory structure matches the supported media.
I suppose it has something to do with my folder/ directory not matching the contents (for some reason) but how can I correct this?
Thanks
macbookpro Mac OS X (10.4.8)Archive and install would be the only advice I could give at this time, It's missing a critical leopard file.
-
Hi
+"CANON" has invalid directory structure ..+ I'm working on FCP 6.0 and I get that message during Log and Transfer. The CANON directory is on the camera CANON HF100.
I have two iMac 5.1 with FCP 6.0 on the other iMac there is no problem. Plug in the camera open Log and Transfer and the "CANON" comes up with all clips.
Settings in FCP is the same - as I see them
Been reading and testing for hours. Any hint?Just testing. Media backup not so important. Problem solved. I made a software update
-
Importing from P2 cards..."invalid directory structure"
FCP 5.1
P2 cards
I am trying to import the material from the P2 cards.
I actually tranfered the content of the cards on my desktop and tried to File/Import/P2 Panasonic. I chose the Contents folder and i get this message: "invalid directory structure"...
I have been able to do this operation in the past, but suddenly this happens.
Any idea on what's going on?First off, does the CONTENTS folder have all six folders inside it?
Second, do the folders have any additional naming to them other than CONTENTS? Like CONTENTS 1, CONTENTS 2. Can't do that....has to be CONTENTS only...no additional naming.
Third, is this you issue:
http://lfhd.blogspot.com/2007/01/p2-folder-naming-tip.html
Shane -
Invalid directory structure in Log and Transfer w/ AVCHD & stills
Using FCE 4.01 I have been happily using Log & Transfer for material from Panasonic AG-HMC70P AVCHD Camera. Last night I shot some material using an SD card that had some still photo files on it from a Nikon Coolpix. Now FCE won't read the SD card for L&T. Gives me the invalid drectory structure error message. I tried deleting the Nikon related files in Finder, but it still won't work. Any hope for getting these files into FCE somehow?
First, I would lock the SD card so it can't be erased or written to. I would also copy the entire SD card to a folder on a hard drive for backup purposes.
If the camera can play back the video clips, then you could try using one of these utilities to salvage your clips. You may have to try them to find out which one will work in your situation, as the directory has been corrupted in some way by using the SD card in two different cameras.
Voltaic
VLC Media Player
Panasonic AVCHD transcoder (unfortunately this is Windows only)
Mac Video Converter
There are other conversion utilities if none of these work for you.
Unfortunately you have found out the hard way that you should never use an SD card in more than one, single camera/camcorder. But don't lose hope, one of these utilities should do the trick. As long as the camera can play back the video clips, there is a way to get them, even if you have to play back via the analog output and convert the analog out to digital. -
Help diagnosing "The selected certificate has errors: Invalid Signature"
I am unable to sign a PDF using a new certificate I have received. I have tried Acrobat X and XI. I have also tried importing both the root and issuing CAs as trust anchors. Those certs seem to verify fine. This issue appears to be with the signature on my cert.
My suspicion is that the issue stems from the issuing CA's use of the "AlternateSignatureAlgorithm", 1.2.840.113549.1.1.10 RSASSA-PSS, for my user cert. Acrobat does not seem to recognize this algorithm. It simply lists the OID value when I look at the signature algorithm under details.
The certificate is validated fine using certutil.exe and works fine when I use it for client SSL authentication. I am using Windows 7 and have tried both 32 and 64 bit PCs.
Has anyone experienced this before?
================ Certificate 0 ================
================ Begin Nesting Level 1 ================
X509 Certificate:
Version: 3
Serial Number: 100000
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Issuer:
CN=xyz QA CA
O=xyz Technical Resources Ltd
C=US
NotBefore: 11/15/2012 2:14 PM
NotAfter: 11/16/2022 2:14 PM
Subject:
CN=xyz Issuing CA
Public Key Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
Algorithm Parameters:
05 00
Public Key Length: 2048 bits
Public Key: UnusedBits = 0
0000 30 82 01 0a 02 82 01 01 00 e3 0b d4 99 e6 01 f1
0010 0e a4 e1 82 8a 8c 39 27 62 7a 03 23 fe 03 3f b5
0020 0d b6 fa c2 1b 86 44 d6 2f 76 65 b0 02 ff 83 69
0030 b7 6a 8d b2 d7 22 74 e3 04 9a 01 ec 4c 0f de ff
0040 c3 db 8f b5 c1 d3 7d 80 f5 ca cc ca 6d ef df 2a
0050 31 25 18 0b 92 1b 4b 1f 41 c0 5f b6 b2 7e f4 43
0060 99 43 01 cf c2 60 de 79 75 ec dc 61 11 ea 87 d0
0070 76 56 a6 4f 00 4a 31 94 37 a5 37 7b 0d 61 49 74
0080 67 88 31 df 81 16 a2 ed 5c 77 6b 23 6b 92 35 c8
0090 b3 05 cc 5a 06 3c a3 b3 6c d8 ad 1e 66 28 4e 90
00a0 3f ad 66 db 6d 13 dd c8 44 29 a0 4f 62 9c f5 5a
00b0 c1 7e 84 fc e6 24 57 c2 bd ce f1 80 b7 bd 13 b8
00c0 9f d1 8a bb 41 43 67 9f 68 25 f6 a6 a2 be 44 89
00d0 11 4f 12 3d 2d d3 85 be 38 f9 97 bd e1 ce 5c 8c
00e0 4e d4 ce be 19 0b a7 91 5d ee 1e c1 84 2c 2a 5e
00f0 bb e5 4a fb 7f 2a f4 b8 06 2b 63 1f d9 c3 d9 d3
0100 5a 13 2d ea 19 63 dd 7c e5 02 03 01 00 01
Certificate Extensions: 9
2.5.29.19: Flags = 1(Critical), Length = 5
Basic Constraints
Subject Type=CA
Path Length Constraint=None
2.5.29.14: Flags = 1(Critical), Length = 16
Subject Key Identifier
8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
2.5.29.15: Flags = 1(Critical), Length = 4
Key Usage
Certificate Signing, Off-line CRL Signing, CRL Signing (06)
2.5.29.35: Flags = 1(Critical), Length = 7e
Authority Key Identifier
KeyID=c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
Certificate Issuer:
Directory Address:
CN=xyz QA CA
O=xyz Technical Resources Ltd
C=US
Certificate SerialNumber=00 96 b6 de 15 a7 4b 97 ac
2.5.29.31: Flags = 0, Length = 36
CRL Distribution Points
[1]CRL Distribution Point
Distribution Point Name:
Full Name:
URL=http://pki.xyzre.qa1/crls/root-ca.crl
1.3.6.1.5.5.7.1.1: Flags = 0, Length = 37
Authority Information Access
[1]Authority Info Access
Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
Alternative Name:
URL=http://pki.xyzre.qa1/root-ca.cer
2.5.29.32: Flags = 0, Length = 6e
Certificate Policies
[1]Certificate Policy:
Policy Identifier=2.16.840.1.101.3.2.1.48
[1,1]Policy Qualifier Info:
Policy Qualifier Id=CPS
Qualifier:
http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/documents/test_policy.pdf
1.3.6.1.4.1.311.21.1: Flags = 0, Length = 3
CA Version
V0.0
1.3.6.1.4.1.311.20.2: Flags = 0, Length = c
Certificate Template Name (Certificate Type)
SubCA
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Signature: UnusedBits=0
0000 41 a4 3f 79 99 d2 aa fa f9 4b 88 0c a6 be 6f 40
0010 0b df 10 93 f5 bb 48 c7 1f 89 73 73 09 58 b4 22
0020 f2 b8 0f 78 b1 da 16 81 cd 2d 86 5a 22 90 67 cd
0030 22 03 56 d5 c2 f4 df 79 b2 2a 82 e0 2e 5a 9a c3
0040 92 b5 4d f2 fe 3d 6b f0 97 b0 b7 85 b6 e9 99 4c
0050 f5 87 34 81 bc 27 f0 77 a1 c6 b2 50 b1 c8 b6 2f
0060 6f 01 61 0d 1d bc cd 3b 07 2d 18 71 d3 f1 f2 03
0070 78 e6 82 24 27 b1 65 d5 4b be 6c 20 f7 60 30 4c
0080 49 42 07 4c 13 d9 7d 77 7f 10 a4 32 bc 30 d4 82
0090 bf 40 06 0f 84 32 43 65 67 47 d0 19 59 0e e7 c2
00a0 d9 c1 10 0a 5e df a2 18 04 86 e5 e4 09 80 99 75
00b0 fd 21 ad 86 5f 77 ab 5d aa 79 74 ed eb ba c4 e8
00c0 f1 fb b2 ae 6a dd 07 5c cc 3d 93 99 ff 45 e6 f6
00d0 c6 d6 d3 22 69 c3 43 50 c0 69 e4 7f 3e 73 df 76
00e0 6f 9d fc 73 ed 54 0b 49 3b 6f c8 99 32 b1 9b d5
00f0 15 bd 5f 40 07 a2 f2 92 0e 74 2b f2 01 39 52 b0
Non-root Certificate
Key Id Hash(rfc-sha1): 8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
Key Id Hash(sha1): e7 a5 38 8b 64 5e bd 6e ee 7b 3f 61 bb 8a ed 2c cc 4b 2c 2f
Cert Hash(md5): 69 84 7c 7c d8 2a 35 12 e9 6b e8 6a fd ca be 92
Cert Hash(sha1): eb 2f 11 1b b0 c2 92 a0 14 74 50 42 50 1e de c5 53 de d7 df
---------------- End Nesting Level 1 ----------------
CERT_MD5_HASH_PROP_ID(4):
69 84 7c 7c d8 2a 35 12 e9 6b e8 6a fd ca be 92
CERT_SHA1_HASH_PROP_ID(3):
eb 2f 11 1b b0 c2 92 a0 14 74 50 42 50 1e de c5 53 de d7 df
CERT_KEY_IDENTIFIER_PROP_ID(20):
8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
Cannot find the certificate and private key for decryption.
================ Certificate 1 ================
================ Begin Nesting Level 1 ================
X509 Certificate:
Version: 3
Serial Number: 96b6de15a74b97ac
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Issuer:
CN=xyz QA CA
O=xyz Technical Resources Ltd
C=US
NotBefore: 11/13/2012 3:35 PM
NotAfter: 11/13/2032 3:35 PM
Subject:
CN=xyz QA CA
O=xyz Technical Resources Ltd
C=US
Public Key Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
Algorithm Parameters:
05 00
Public Key Length: 2048 bits
Public Key: UnusedBits = 0
0000 30 82 01 0a 02 82 01 01 00 d2 5f 7d c0 c5 25 7f
0010 2c 4c a2 4a 9b 6f e7 7a 35 cd 9a 2a 88 30 36 9b
0020 f8 a4 d8 31 64 72 36 1c 1b 2c dc 73 11 d6 57 a2
0030 97 91 6d bb d0 3c 13 65 28 4d 78 4e e1 c7 06 ac
0040 16 c1 2a 62 39 ba 39 f9 a1 b9 4a 14 39 28 58 0d
0050 f4 97 83 d5 ee 45 91 4a 41 06 e5 b9 60 40 20 48
0060 85 f4 2d 8e 04 7f 81 12 3a 26 e1 0f 21 32 49 bc
0070 20 ef 12 69 5a 20 a4 51 65 6d 85 4c 0f 4c 91 4c
0080 26 47 27 a7 9e 49 e0 f7 56 08 fc 90 47 11 6c a9
0090 b8 81 c6 83 c8 b2 2d e8 c4 ba 8b 45 32 c5 dd a0
00a0 d9 1c 85 10 d6 6b 42 50 9a 42 d6 e4 51 32 73 59
00b0 92 5b d1 44 82 dc be 75 65 94 e7 4a 79 15 ed 23
00c0 f8 a3 3e 28 92 31 75 5c fa b9 1b 6d e0 c3 d0 24
00d0 7a 09 86 d0 2d c7 42 eb 6b fc 95 ed 62 13 21 35
00e0 2f 0e b6 cd c2 c3 66 d4 a6 1b 53 15 49 64 ac 34
00f0 11 20 8b e4 46 bc 60 68 3e 1b cb 5c b8 05 f4 a8
0100 0a a3 53 d0 37 2a 2d 73 01 02 03 01 00 01
Certificate Extensions: 7
2.5.29.19: Flags = 1(Critical), Length = 5
Basic Constraints
Subject Type=CA
Path Length Constraint=None
2.5.29.14: Flags = 1(Critical), Length = 16
Subject Key Identifier
c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
2.5.29.15: Flags = 1(Critical), Length = 4
Key Usage
Certificate Signing, Off-line CRL Signing, CRL Signing (06)
2.5.29.35: Flags = 1(Critical), Length = 7e
Authority Key Identifier
KeyID=c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
Certificate Issuer:
Directory Address:
CN=xyz QA CA
O=xyz Technical Resources Ltd
C=US
Certificate SerialNumber=00 96 b6 de 15 a7 4b 97 ac
2.5.29.31: Flags = 0, Length = 36
CRL Distribution Points
[1]CRL Distribution Point
Distribution Point Name:
Full Name:
URL=http://pki.xyzre.qa1/crls/root-ca.crl
1.3.6.1.5.5.7.1.1: Flags = 0, Length = 37
Authority Information Access
[1]Authority Info Access
Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
Alternative Name:
URL=http://pki.xyzre.qa1/root-ca.cer
2.5.29.32: Flags = 0, Length = 6e
Certificate Policies
[1]Certificate Policy:
Policy Identifier=2.16.840.1.101.3.2.1.48
[1,1]Policy Qualifier Info:
Policy Qualifier Id=CPS
Qualifier:
http://csrc.nist.gov/groups/ST/crypto_apps_infra/csor/documents/test_policy.pdf
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.5 sha1RSA
Algorithm Parameters:
05 00
Signature: UnusedBits=0
0000 69 25 3a 36 f1 13 25 88 73 94 eb cf 5b 70 2e 86
0010 8c 0d 7a 8f 3a 49 0e 42 18 da c9 00 26 68 ea 42
0020 cd 2a 24 43 0d ec 6b 15 73 14 33 69 c2 60 3d 40
0030 1c 4d 59 12 7a e9 03 00 81 ba 1e 50 55 05 bd 60
0040 88 84 bb 8e e3 f5 ce 00 42 ae fd 01 05 fd bc 5f
0050 af cc e3 a4 4d f2 84 8b 9b 0d 24 16 d6 d4 51 da
0060 50 9c c4 69 d6 b8 18 be e5 5c 48 b8 8a a3 d4 22
0070 0e 26 f2 15 d8 ff 19 34 d4 1d 69 50 02 51 da e8
0080 ad 05 a3 2f 1c e9 0f da e3 4c 36 c4 cd 6e a5 76
0090 88 19 90 78 ad fe 94 62 46 91 2b 0a 36 df e2 ea
00a0 4a a9 f4 5c dc 77 4d e5 f4 ab e9 b9 da f6 b0 9f
00b0 6c f5 50 74 14 19 05 df 96 b5 ee af a3 31 a5 af
00c0 8f 6c be 67 43 78 55 0e 39 46 80 05 12 5f c2 4f
00d0 24 fc 13 f7 e5 ee 64 0f dd 9a 49 5c 57 10 1c 4b
00e0 7a 9f 5a 1f 0c ec 5b 8d b4 c4 ed d8 09 cc 1c d9
00f0 9f 04 3f 85 ab 95 48 8e 77 e0 91 81 39 46 fb a3
Signature matches Public Key
Root Certificate: Subject matches Issuer
Key Id Hash(rfc-sha1): c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
Key Id Hash(sha1): f0 fc 52 1c c1 a6 16 2d 28 c1 71 84 ae d4 18 87 74 c4 f8 1c
Cert Hash(md5): c9 af 16 63 9e 51 7b 8e 22 25 96 d7 a7 66 fa ab
Cert Hash(sha1): e6 0b ef c1 fb e6 94 13 dc 9f 26 80 33 31 43 d9 ec af d7 be
---------------- End Nesting Level 1 ----------------
CERT_MD5_HASH_PROP_ID(4):
c9 af 16 63 9e 51 7b 8e 22 25 96 d7 a7 66 fa ab
CERT_SHA1_HASH_PROP_ID(3):
e6 0b ef c1 fb e6 94 13 dc 9f 26 80 33 31 43 d9 ec af d7 be
CERT_KEY_IDENTIFIER_PROP_ID(20):
c5 91 51 88 76 e2 a4 13 5a 2f 11 84 29 54 de cf 4f 93 28 eb
Cannot find the certificate and private key for decryption.
================ Certificate 2 ================
================ Begin Nesting Level 1 ================
X509 Certificate:
Version: 3
Serial Number: 1500000003a24d67389af826d7000000000003
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.10 RSASSA-PSS
Algorithm Parameters:
30 00
Issuer:
CN=xyz Issuing CA
NotBefore: 11/15/2012 3:13 PM
NotAfter: 11/15/2013 3:13 PM
Subject:
[email protected]
CN=(e) Hugh Kelley
Public Key Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.1 RSA (RSA_SIGN)
Algorithm Parameters:
05 00
Public Key Length: 2048 bits
Public Key: UnusedBits = 0
0000 30 82 01 0a 02 82 01 01 00 e4 55 77 34 c0 b7 58
0010 55 cd 71 1e da d4 83 fd f4 bd a5 d5 26 52 6c 7e
0020 8d 74 ea 0a b6 2c 0c ae b4 8f fc 95 07 9b 1a d4
0030 e1 9f ed e3 7e d7 f4 f0 04 2c e4 ed 4c 49 2b d7
0040 b4 42 c0 1c 12 7c b8 76 22 83 e6 d9 44 78 ce 26
0050 20 5c 9c 71 30 3c 78 01 74 fa ac f9 7b b3 83 28
0060 a8 18 52 10 d4 a5 f0 29 40 15 40 16 5c 90 4b 5d
0070 c4 57 9d 3d 29 4e ce 80 b1 f1 ae 17 a4 cc 85 0b
0080 a2 5e 73 0f ac 0f ff 8b 05 0c b9 f2 17 b3 ad 2f
0090 b7 33 c7 ac bf 16 0f 09 2a e6 b7 f9 90 42 0b 6f
00a0 3b 7f df 86 e6 e9 33 b6 d5 2d be 5f 65 4b 87 45
00b0 d4 53 fc 8e de 0f 49 fd 8b 84 f5 2e cd 00 a9 cd
00c0 0c b2 e2 7e 3e f9 e3 28 2f 9a 55 85 3e b8 b2 3a
00d0 89 ce 19 bd 88 b2 74 da 42 ac bf 07 6c 4a b8 2e
00e0 94 36 3b 28 f0 45 ec 59 f4 22 f3 03 47 85 ef 4c
00f0 ba f5 24 3e 55 60 8b e8 6e e3 e9 1e bf 3c c9 75
0100 88 9c 39 6c 20 66 c0 92 85 02 03 01 00 01
Certificate Extensions: 10
1.3.6.1.4.1.311.21.7: Flags = 0, Length = 30
Certificate Template Information
Template=1.3.6.1.4.1.311.21.8.11609700.13554795.12405411.13975648.10011376.129.8742862.14 66929
Major Version Number=100
Minor Version Number=5
2.5.29.37: Flags = 0, Length = 22
Enhanced Key Usage
Client Authentication (1.3.6.1.5.5.7.3.2)
Secure Email (1.3.6.1.5.5.7.3.4)
Encrypting File System (1.3.6.1.4.1.311.10.3.4)
2.5.29.15: Flags = 1(Critical), Length = 4
Key Usage
Digital Signature, Key Encipherment (a0)
1.3.6.1.4.1.311.21.10: Flags = 0, Length = 28
Application Policies
[1]Application Certificate Policy:
Policy Identifier=Client Authentication
[2]Application Certificate Policy:
Policy Identifier=Secure Email
[3]Application Certificate Policy:
Policy Identifier=Encrypting File System
1.2.840.113549.1.9.15: Flags = 0, Length = 37
SMIME Capabilities
[1]SMIME Capability
Object ID=1.2.840.113549.3.2
Parameters=02 02 00 80
[2]SMIME Capability
Object ID=1.2.840.113549.3.4
Parameters=02 02 00 80
[3]SMIME Capability
Object ID=1.3.14.3.2.7
[4]SMIME Capability
Object ID=1.2.840.113549.3.7
2.5.29.14: Flags = 0, Length = 16
Subject Key Identifier
c2 1d d2 c8 90 64 9c 38 a9 66 9d 12 8b 1a a6 ab a8 72 2a 11
2.5.29.35: Flags = 0, Length = 18
Authority Key Identifier
KeyID=8a 54 1f f7 43 b9 fd 19 3f 82 28 08 13 3d fa 73 42 11 e3 6f
2.5.29.31: Flags = 0, Length = 44
CRL Distribution Points
[1]CRL Distribution Point
Distribution Point Name:
Full Name:
URL=http://pki.xyzre.qa1/crls/xyz Issuing CA.crl
1.3.6.1.5.5.7.1.1: Flags = 0, Length = 45
Authority Information Access
[1]Authority Info Access
Access Method=Certification Authority Issuer (1.3.6.1.5.5.7.48.2)
Alternative Name:
URL=http://pki.xyzre.qa1/xyz Issuing CA.crt
2.5.29.17: Flags = 0, Length = 50
Subject Alternative Name
Other Name:
Principal [email protected]
RFC822 [email protected]
Signature Algorithm:
Algorithm ObjectId: 1.2.840.113549.1.1.10 RSASSA-PSS
Algorithm Parameters:
30 00
Signature: UnusedBits=0
0000 51 58 a1 89 fc fe 9d b3 67 36 9f 4d 41 75 9e 9f
0010 b8 30 10 3b c8 f1 0b 6a b8 ab 84 73 2e 91 7e 05
0020 e0 3a 5b 34 cd 0a 35 bd e0 f6 c2 7c 7f d0 d6 b3
0030 03 3d 8c dd 52 04 7f 62 55 a5 14 a7 5a 20 77 5d
0040 0f bb f6 4d a3 8c 2e 98 76 39 f4 30 18 bf be 5f
0050 0c 62 20 40 39 34 e6 de d2 dd 01 dd e9 bb d0 e5
0060 1e 93 93 0e de c4 c5 86 9e 15 72 ea 4c 37 5c 6c
0070 3d dc 69 8d 17 9d f8 b6 2a 51 1f f5 bc f5 fb 58
0080 2c 03 4f 88 b8 58 a3 cd ca 38 28 3a c9 34 79 4a
0090 46 7c de a1 a8 fa 28 34 1f 23 96 69 51 f1 c7 41
00a0 0b c8 a9 39 71 6c 4f 57 81 7f ec a7 2f 65 b9 97
00b0 c8 2d 1e 24 ff fc d9 58 5c 07 e9 2c 83 77 64 a9
00c0 8f 5d 42 9e c3 ea 85 88 39 7b 23 56 38 6d c9 15
00d0 4c 80 de cf 00 e0 73 27 e2 f1 b3 d4 c9 b5 83 74
00e0 4f 6e 6f 03 2f df c1 29 24 de 6a 70 cf de d4 1f
00f0 fb 07 08 85 89 f9 08 f7 68 5c 68 29 2e 3c 6c de
Non-root Certificate
Key Id Hash(rfc-sha1): c2 1d d2 c8 90 64 9c 38 a9 66 9d 12 8b 1a a6 ab a8 72 2a 11
Key Id Hash(sha1): 42 9c bd 63 60 4c d2 a8 55 bd 1b f4 70 25 34 cd 72 38 ca 8c
Cert Hash(md5): af 8b 1e 76 71 f5 53 f4 93 62 1d e7 5e a8 d1 ff
Cert Hash(sha1): 4f 3b d3 48 ba 05 65 dd 99 bb 33 65 5b 5e ba 13 28 fe 2d 80
---------------- End Nesting Level 1 ----------------
CERT_MD5_HASH_PROP_ID(4):
af 8b 1e 76 71 f5 53 f4 93 62 1d e7 5e a8 d1 ff
CERT_SHA1_HASH_PROP_ID(3):
4f 3b d3 48 ba 05 65 dd 99 bb 33 65 5b 5e ba 13 28 fe 2d 80
CERT_KEY_PROV_INFO_PROP_ID(2):
Key Container = {0136F9BB-2135-4642-827C-B883E0BDAF41}
Unique container name: 1119ced7dad9cbd7d39924c9f35b5886_f10cfee5-eccc-4ef4-b0fb-7042bc1815c3
Provider = Microsoft Enhanced Cryptographic Provider v1.0
ProviderType = 1
Flags = 0
KeySpec = 1 -- AT_KEYEXCHANGE
CERT_CEP_PROP_ID(87):
Enrollment Policy Url: ldap:
Enrollment Policy Id: {D8416D24-E050-45B1-B348-B9218292357C}
Enrollment Server Url: Q-PKI-01.xyzre.qa1\xyz Issuing CA
Request Id: 3
Flags = 0
DefaultNone -- 0
Url Flags = 20 (32)
PsfAllowUnTrustedCA -- 20 (32)
Authentication = 2
Kerberos -- 2
Enrollment Server Authentication = 2
Kerberos -- 2
CERT_REQUEST_ORIGINATOR_PROP_ID(71):
Q-APPDEV7-01.xyzre.qa1
CERT_KEY_IDENTIFIER_PROP_ID(20):
c2 1d d2 c8 90 64 9c 38 a9 66 9d 12 8b 1a a6 ab a8 72 2a 11
Unique container name: 1119ced7dad9cbd7d39924c9f35b5886_f10cfee5-eccc-4ef4-b0fb-7042bc1815c3
PP_KEYSTORAGE = 1
CRYPT_SEC_DESCR -- 1
KP_PERMISSIONS = 3f (63)
CRYPT_ENCRYPT -- 1
CRYPT_DECRYPT -- 2
CRYPT_EXPORT -- 4
CRYPT_READ -- 8
CRYPT_WRITE -- 10 (16)
CRYPT_MAC -- 20 (32)
D:(A;ID;GAGR;;;SY)(A;ID;GAGR;;;BA)(A;ID;GAGR;;;S-1-5-21-2052111302-1708537768-839522115-2 4370)
Allow Full Control NT AUTHORITY\SYSTEM
Allow Full Control BUILTIN\Administrators
Allow Full Control xyzRE\hugh.kelley
Private Key:
PRIVATEKEYBLOB
Version: 2
aiKeyAlg: 0xa400
CALG_RSA_KEYX
Algorithm Class: 0xa000(5) ALG_CLASS_KEY_EXCHANGE
Algorithm Type: 0x400(2) ALG_TYPE_RSA
Algorithm Sub-id: 0x0(0) ALG_SID_RSA_ANY
0000 52 53 41 32 RSA2
0000 ...
048c
Encryption test passed
CertUtil: -dump command completed successfully.Hi Hugh,
As you figured out the certificate was using a signature algorithm that Acrobat did not understand. The "signature algorithm" is a composite of the the digest algorithm (e.g. sha1), and the encryption algorithm (e.g. RSA). Acrobat understands the following digest algorithms; MD5, SHA-1, RIPEMD-160, SHA-256, SHA384, and SHA512. As far as encryption algorithms go, it understands DSA and RSA. Just to make things a little more complicated, version XI also can handle elliptic curve, but versions 6 thru 10 were limited to DSA & RSA. If you are using a digital ID created with the DSA encryption algorithm then the only digest algorithm Acrobat can use with is SHA-1. Just like you saw sha1RSA, you could also use a digital ID with the sha1DSA signature algorithm. If you are using RSA then it will pair with all six digest algorithms I noted above (e.g. sha256RSA).
The Probabilistic Signature Scheme is not something Acrobat understands at all.
Steve -
F4v has an invalid file structure on Firefox
Hi, i'm trying to play external videos using netStream.
My script work fine with .flv files, but with .f4v it doesn't work with Firefox (i've tried versions 3.6 and 4): I get NetStream.Play.FileStructureInvalid
F4v files was exported using Media Encoder from Premiere.
Here's a part of my code:
ncConnection = new NetConnection();
ncConnection.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
ncConnection.addEventListener(SecurityErrorEvent.SECURITY_ERROR, securityErrorHandler);
ncConnection.connect(null);
nsStream = new NetStream(ncConnection);
nsStream.addEventListener(NetStatusEvent.NET_STATUS, netStatusHandler);
nsStream.client = this;
nsStream.bufferTime = BUFFER_TIME;
nsStream.play("http://www.domain.com/myVideo.f4v");
Does anybody know what causes this problem?
Thank you!It's probably a server issue.
I was testing with f4v on server A and swf on server B.
If I turn the tables (swf on server A and f4v on server B) it works
I tested f4v in a server C and works too.
So, when f4v is on server A (could I say his brand?) with remote swf, firefox doesn't read it -
FCP7 Log and Transfer, Unsupported Media . . .
Last night I used two different SDHC cards in my Canon Vixia HFS100. FCP7 will import clips via Log and Transfer from one, but not the other. It just ignores everything on it (but I have 1.4 GB of recordings on it).
When I copy the card to a hard drive and point Log and Transfer to that folder, I get the message "CANON contains unsupported media or has an invalid directory structure"
Before using this card, I did a full initization of the card. I compared the directory structures of the two. They appear identical. I haven't messed with either in the Finder.
How do I tell what is wrong? How do I fix it? Or should I just try converting with something like Voltaic? I'm an FCP beginner. So, I would rather not stray too far from its work flow.
Thanks!On the card that you are having trouble with:
1) make sure there are no still images
2) make sure there is no non-hd video (log and transfer works with AVCHD HD video clips, not MPEG SD clips)
3) if possible, all the hd video clips should be of one quality/size/format setting
4) in the log and transfer window, click on the gear shaped icon in the top center of the screen to set the Log and Transfer Preferences:
Set the Import Preferences for AVCHD to Plain Stereo:
Click OK, then restart FCP, reconnect the camera and try again.
MtD -
FCP "unsupported media" message
I am using a Canon XF105. I went to log and transfer the footage from the card reader and keep getting the message: "(File name) contains unsupported media or has an invalid directory structure." Any idea why/what to do?
Did you install the Canon XF log and transfer plugin?
http://software.canon-europe.com/software/0040354.asp -
Warning
100EOS7D contains unsupported media or has an invalid directory struture. Please choose a folder whose directory structure matches supported media.
I did not knowingly change anything that I have been doing for months... any ideas?? Thanks.This type of message appears when there is material in multiple formats on the same card.
You may want to go through the card while it is in the camera and verify that all the material is in the same format and that none of the files are corrupted.
x
Maybe you are looking for
-
OSX Print in Black and White on an HP Color printer?
I have an HP8500 Color printer connected to OSX 10.8.3 through a JetDirect port. The OSX Driver for the HP8500 does not have the option to print in color or B&W that the windows driver has. As a consequence, even when printing in B&W from a PPT deck,
-
Title says it all pretty much.
-
Podcast Videocast/ Audio only not showing up in itunes podcast feed
Hi Everyone, I work on a site called Truthdig and we can't get our latest audio (mp3) only podcast to show up in our itunes podcast feed, latest podcast episodes have been video. is this what is causing the problem? Could it be something else? Advice
-
hi, I am using the report export feature of oracle APEX. IT is working fine except i m getting something like this (div tag start)div id="report_19777432813352373_catch""First Name" in the first column of the report and the report ending with (div ta
-
Can anyone help me download missing plug-in?
I want to play a video clip in my Safari browser, and I get the following message: Safari cannot find the internet plug-in The page "Menus, Recipes, Videos, Tips: Football party Foods: Parties: Party Ideas: Food Network" has content of MIME type "app