Importing WSDL with external references issue

Hi guys,
pls help me on this:
I have a WSDL file which referes to external data types. Obviously, if I want to create a message mapping I can't see the WSDL data type. How are such situations resolved? How to import external types into PI?
Thx, A.

HI,
You have to inport the WSDL alongwith all its external references.
You can refer the following threads:
Import WSDL with external reference
Re: PI 7.1: Importing a wsdl file with references to other xsd files
http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm

Similar Messages

WSDL With External References

Hello,
I need to import a wsdl in external definition ,that has 2 xsds as external references.
But when I import the wsdl,I am not able to find the wsdl pointing to the two xsds .
Can anyone help me with the this?
Thanks in advance.
Regards,
Sriparna

Hello,
The xsds will stay as is. What you can do is:
1.) Open the WSDL ED
2.) Go to the External References Tab
3.) You will see a source and a name column
4.) Click on the name(column) of any xsd that you want to be referenced
5.) Press ctrl+c
6.) Open the XSD ED
7.) Click the edit button
8.) Under the Source field, press ctrl+v
9.) Save and activate
Hope this helps,
Mark

No messages under the 'Messages' tab for imported WSDL in External Definitions

Dear All,
I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
Regards,
Adil Khalil

Hi, imported wsdl shouldn't have any import instruction.
All import instruction should be changed to content of importing file.
I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
Hmm. but I imported you file and everything is fine
Message was edited by: Mikhail Koshkin

Using excel sheets with externa references

I was hopping someone could point me somewhere to begin here.
What if I am implementing CM solution in a financial department, which strongly uses excel spreadsheets, which means they're going to need external references from a file, to another .xls for example. Is there any thing about that matter in UCM?
ty

Post what you would like to do in Excel here
http://www.microsoft.com/mac/support

Importing WSDLs with references to schema

Hi all,
I am trying to invoke a webservice from PI and have imported the WSDLs for the same. But i couldn't see the various data types.
When i noticed that wsdl, i could see that there are rexternal references with relative path.
schemaLocation="..\External\external-common.xsd"/>
So i have a doubt about how to bring these references to PI. Since these are relative path, do i need to change them to absolute path?
If yes, how?
Thanks and best regards,
Kulwant

Hi Kulwant,
The schema files should always be present at the relative paths.
You try out by importing these schema files also under External Definitions along with the main WSDL and check whether they are referenced.
OR
Manipulate the WSDL in any of XML editior and to Include the schema files into the main WSDL. and then import the WSDL.
Regards,
AshwinM

Importing WSDL into External Definitions

Hi,
I got WSDLs from WAS WS Navigator, I have imported the WSDL from porttypes folder but I don't see any messages in the messages tab of External Definitions.
See below my WSDL
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns0="urn:xEM_MeasurementImportVi" targetNamespace="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document" xmlns:tns="urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document">
<wsdl:types>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
 <xs:complexType name="ArrayOfint">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="int" type="xs:int" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfString">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="String" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em.imp.consumption" xmlns:tns="urn:com.technidata.em.imp.consumption" elementFormDefault="qualified">
 <xs:complexType name="ReturnCode">
 <xs:sequence>
 <xs:element name="code" type="xs:int"/>
 <xs:element name="description" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfReturnCode">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="ReturnCode" type="tns:ReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:com.technidata.em" xmlns:tns="urn:com.technidata.em" elementFormDefault="qualified">
 <xs:complexType name="Measurement">
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true" minOccurs="0"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true" minOccurs="0"/>
 <xs:element name="pDescription" type="xs:string" nillable="true" minOccurs="0"/>
 </xs:sequence>
 </xs:complexType>
 <xs:complexType name="ArrayOfMeasurement">
 <xs:sequence>
 <xs:element maxOccurs="unbounded" minOccurs="0" name="Measurement" type="tns:Measurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:schema>
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:xEM_MeasurementImportVi" xmlns:tns="urn:xEM_MeasurementImportVi" elementFormDefault="qualified" xmlns:s1="urn:java/lang" xmlns:s2="urn:com.technidata.em.imp.consumption" xmlns:s0="urn:com.technidata.em">
 <xs:import namespace="urn:java/lang"/>
 <xs:import namespace="urn:com.technidata.em.imp.consumption"/>
 <xs:import namespace="urn:com.technidata.em"/>
 <xs:element name="checkConnection">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="checkConnectionResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pSystemId" type="xs:string" nillable="true"/>
 <xs:element name="pSystemTagId" type="xs:string" nillable="true"/>
 <xs:element name="pDate" type="xs:dateTime" nillable="true"/>
 <xs:element name="pValue" type="xs:double"/>
 <xs:element name="pUnit" type="xs:string" nillable="true"/>
 <xs:element name="pDescription" type="xs:string" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="xs:int"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImport">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="pMeasurements" type="s0:ArrayOfMeasurement" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="doMeasurementsImportResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfint" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodes">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getErrorCodesResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s2:ArrayOfReturnCode" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnits">
 <xs:complexType>
 <xs:sequence/>
 </xs:complexType>
 </xs:element>
 <xs:element name="getSupportedUnitsResponse">
 <xs:complexType>
 <xs:sequence>
 <xs:element name="Response" type="s1:ArrayOfString" nillable="true"/>
 </xs:sequence>
 </xs:complexType>
 </xs:element>
 </xs:schema>
</wsdl:types>
<wsdl:message name="checkConnectionIn_doc">
 <wsdl:part name="parameters" element="ns0:checkConnection"/>
</wsdl:message>
<wsdl:message name="checkConnectionOut_doc">
 <wsdl:part name="parameters" element="ns0:checkConnectionResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementImportResponse"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportIn_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImport"/>
</wsdl:message>
<wsdl:message name="doMeasurementsImportOut_doc">
 <wsdl:part name="parameters" element="ns0:doMeasurementsImportResponse"/>
</wsdl:message>
<wsdl:message name="getErrorCodesIn_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodes"/>
</wsdl:message>
<wsdl:message name="getErrorCodesOut_doc">
 <wsdl:part name="parameters" element="ns0:getErrorCodesResponse"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsIn_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnits"/>
</wsdl:message>
<wsdl:message name="getSupportedUnitsOut_doc">
 <wsdl:part name="parameters" element="ns0:getSupportedUnitsResponse"/>
</wsdl:message>
<wsdl:portType name="xEM_MeasurementImportVi_Document">
 <wsdl:operation name="checkConnection">
 <wsdl:input message="tns:checkConnectionIn_doc"/>
 <wsdl:output message="tns:checkConnectionOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementImport">
 <wsdl:input message="tns:doMeasurementImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="doMeasurementsImport">
 <wsdl:input message="tns:doMeasurementsImportIn_doc"/>
 <wsdl:output message="tns:doMeasurementsImportOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getErrorCodes">
 <wsdl:input message="tns:getErrorCodesIn_doc"/>
 <wsdl:output message="tns:getErrorCodesOut_doc"/>
 </wsdl:operation>
 <wsdl:operation name="getSupportedUnits">
 <wsdl:input message="tns:getSupportedUnitsIn_doc"/>
 <wsdl:output message="tns:getSupportedUnitsOut_doc"/>
 </wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
Appreciate your quick response.
Srini Sandaka

Hi,
I diagnose the problem, the problem with the name space length.
Orginal NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/document
Modified NameSpace: urn:xEM_MeasurementImportWsd/xEM_MeasurementImportVi/documen
The External Definitions is recognizing only 60 characters namespace. If the namespace exceed 60 characters it is not showing any messages in the messages tab.
Will make any problem to call the WebService from XI since we are changing the original namespace in the WSDL and imported into XI.
How can we overcome this problem, is it a limitation.
Thanks
Srini Sandaka

Problem Import WSDL with XSD import Schema

Hi SCN, i have problem
I have a WSDL that references an xsd, but the structure is not visible in PI.
 <wsdl:types>
 <xsd:schema targetNamespace="http://tempuri.org/Imports">
 <xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
 <xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
 <xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
 </xsd:schema>
 </wsdl:types>
 <wsdl:message name="iVistaHO_AddItemHO_InputMessage">
 <wsdl:part name="parameters" element="tns:AddItemHO" />
 </wsdl:message>
WSDL works well using SoapUI.
When imported to PI parameters is not displayed
I Need Help
Thank you.

Hi, Dihiansan. I don't understand your proposal
I need you see the structure in PI how in SoapUI.
It is possible?
Regards

Importing flv with external playback.. loop?!

Hi!
I'm trying to create google ads under the 50kb limit which is causing some headaches...anyway! I've noticed something. If I import my flv (which I've created in after effects) into adobe flash CS5.5 with "load external video with playback component" and then export the whole thing out as a SWF the file size is really small. 50 kb's compared to 795.6 kb's if the "embed flv in SWF" option is used.
So my problem is this, I want to use the option of "load external video with playback component" but I want the video to loop when it's exported out as an SWF. Is this actually possible?
I've tried some scripts which I've found, but I cant get it to work.
Any help or advice would be very much appreciated.
Many thanks!
M

Well yes, you can loop the video using the FLVPlayback, but I think you are missing the point of the 50kb google ad limit.
When you use FLVPlayback, you must also use an external .flv file. So besides the <50kb .swf file, you will also have the >700kb .flv file. You cannot just use the .swf. So together, those two files put you way over the 50kb limit.
Best wishes,
Adninjastrator

Import WSDL with xsd:long incorrectly results in INT4

When importing a WSDL, all fields marked as xsd:long result in INT4 in the proxy class. But long is [supposed to be|http://www.w3schools.com/schema/schema_dtypes_numeric.asp] 8-byte (64 bit). We thus get the following error:
SOAP:1.001 CX_SY_CONVERSION_OVERFLOW:XSLT exception.
An error occurred when deserializing in the simple transformation program
/1SAI/TXS291D096A2B8E35E8375E.
Overflow converting from '2147483648'
<xsd:element minOccurs="0" name="Available" type="xsd:long"/>

Hello Marc
The only way is to manually edit the WSDL file and replace xsd:long
with xsd:string with pattern="\d+" and length="<n>"or
xsd:decimal with fractionDigits="0" totalDigigs="<n>"
Afterwarts regenerate proxy and you'll see that the
technical ABAP-Type is changed to STRG/DEC.
addtional info:
We recomment to use
xsd:decimal with totalDigits="19"
fractionDigits="0"
This is the shortest DEC that is big enought to accept the largest
xsd:long.
Future sight:
In release SAP_BASIS 702 this workaround is already fixed,
here you can change the technical type for xsd:long in proxy
editor directly to STRG or DEC(0,19) without modify the WSDL.
Thanks
Kenny

17" MacBook Pro with external monitor issues under 10.6.4

I have a 17" MacBook Pro 2.4ghz "connected" to a 23" Apple cinema display. For years now I've been able to just connect and wake from sleep with the MBP closed and start working. Ever since I've upgraded to 10.6.4 I have had problems getting my external monitor to switch on. I've had them both in the my local service centre and had them tested and they're both working fine individually. I though it may have been a power supply or Nvidia problem but they're fine. I can't get my monitor to wake either with the MBP closed or open. The sleep light will be lit but there is nothing on the monitor. I've zapped the PRAM, reset the SMC, run DiskWarrior and repaired permissions. Nothing works. I've even followed Apples guide to using them together under clam mode. Still no joy. So for now I'm stuck without being able to use my monitor which has been tested and is functioning properly. I'm wondering if anyone else has the same issues.

that works, although the laptop isn't really close enough to my other monitor for that to make sense. I'd still like to know why it's acting this way.................... thanks for the feedback, though

Dreamweaver very slow when opening files with external links

Is there any way to fix Dreamweaver CS5 (Windows 7, 64bit) when opening files with external references?
For example, I have a very simple CSS file, and toward the top the file has a line that says:
@import url("https://fonts.googleapis.com/css?family=Ubuntu:500,700");
This causes the file to take around 20 seconds to open in DW. If I comment out the line or remove it, the file opens almost instantly. This behaviour is also present in files that contain an SSI.
DW often crashes before being able to open the file and I need to restart the app.
Can I disable DW from attempting to load the references?? It's obviously what is causing the issue IMO and would love to make DW workable again!

"Enable Related Files" isn't the fix for this issue. It's slightly different - I wanted to still load related files, but only the ones local to the file I was editing.
The fix was to use DW's Resolve To IP Address feature. It required adding a registry value - it fixed the issue straight away
This Adobe support doc helped: http://kb2.adobe.com/cps/887/cpsid_88742.html

Target Namespace in imported WSDL

Hello All,
I have an interface that sends data from SAP to 3rd party system.
3rd party team gave us the WSDL and some XSD's of the interface they have on their system.
Now, the problem - target namespace on that WSDL is more than 60 characters. Because of this PI 7.0 is unable to recognise XSD's which are external references on imported WSDL document.
When i reduced the target namespace on the WSDL manually to less than 60 characters and uploaded WSDL again, external references are identified by PI.
Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the future?
Can I delete target namespace from WSDL and use the WSDL as target namespace is optional?
Thanks
Chandra
Edited by: Chandra Sekhar H on Jul 19, 2010 10:45 AM

Now, can i use this WSDL by reducing the target namespace? Will it work? Will i get any problems because of this in the
future?
You can use the wsdl without any issue. If you need to know more: https://service.sap.com/sap/support/notes/901988
Regards,
Abhishek.

Issue with external WSDL in own Outbound interface using SOAP UI

Hello,
this is the issue:
a) Imported an external WSDL to PI as external definition
b) Added external definition to a sync. Service interface
c) Completed configuration and created a WSDL from the sender agreement in Directory (this is PI 7.1)
d) imported the WSDL from c) to soap UI which we are using for testing interfaces
 (already successful with other sync interface where the WSDL from c) contains a message type created in PI
e) testing this interface results in an error:
Error message in MONI:
SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_TestTrigger_Testm~</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:props. Value</SAP:P3>
<SAP:P4>s missing in queue context. Target XSD requires a~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_Test_Testm; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:props. Values missing in queue context. Target XSD requires a</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
This is the message as it looks like in soapUI:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://jusit.hp.com/sys/common/">
 <soapenv:Header/>
 <soapenv:Body>
 <props>
 <com:Property>
 <com:PropertyName>A</com:PropertyName>
 <com:PropertyValue>1</com:PropertyValue>
 </com:Property>
 </props>
 </soapenv:Body>
</soapenv:Envelope>
This is the payload in MONI as it comes from SOAP UI (using http connection):
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<props xmlns:com='http://jusit.hp.com/sys/common/' xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/'>
 <com:Property>
 <com:PropertyName>A</com:PropertyName>
 <com:PropertyValue>1</com:PropertyValue>
 </com:Property>
 </props>
This is the payload as it looks like in Mapping Test in Enterprise Repos. from implemented ext.def.:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:props xmlns:ns0="http://jusit.hp.com/sys/common/">
 <ns0:Property>
 <ns0:PropertyName>A</ns0:PropertyName>
 <ns0:PropertyValue>1</ns0:PropertyValue>
 </ns0:Property>
</ns0:props>
Is there any restriction with external definitions to be used in PI which could be the reason for this strange behaviour?
The implementation contained a message type created in PI earlier which was running successful!
The problem came up with the external definition!
Thank you for your help!
Best regards
Dirk

Hi,
the problem is not the mapping as it is 1:1 with the same message on both sides.
But when I replace the "com"s with "ns0" and "props" with "ns0:props" in the request in soap UI
the payload will be accepted and mapping is successful!
So the issue is about the modification soap UI is doing on the imported WSDL.
a) Generated request in soap UI from imported WSDL: FAILS in PI!!!!
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:com="http://test.ap.com/sys/common/">
 <soapenv:Header/>
 <soapenv:Body>
 <props>
 <com:Property>
 <!You may enter the following 2 items in any order>
 <com:PropertyName>?</com:PropertyName>
 <com:PropertyValue>?</com:PropertyValue>
 </com:Property>
 </props>
 </soapenv:Body>
</soapenv:Envelope>
b) Modified request in soap UI from imported WSDL: WILL BE PROCESSED IN PI
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://test.ap.com/sys/common/">
 <soapenv:Header/>
 <soapenv:Body>
 <ns0:props>
 <ns0:Property>
 <!You may enter the following 2 items in any order>
 <ns0:PropertyName>B</ns0:PropertyName>
 <ns0:PropertyValue>5</ns0:PropertyValue>
 </ns0:Property>
 </ns0:props>
 </soapenv:Body>
</soapenv:Envelope>
But is there any possibility to avoid this effect in soap UI?
Regards
Dirk

Import SAP WSDL into External Definition

Hi Friends,
I'd like to import a WSDL into XI External Definition. However, the WSDL is gained from Web AS Web Service Navigator. So it is a zip file and consists of three WSDL files. How can I import them into the external definition?
Thanks + Regards
Jerome

Hi Jerome,
If you have three wsld files then aren't those three messages?
have you tried importing them as external definitions one by one?
you can check how the message structre looks like
when you try to use the external definition inside a
message mapping (remember you don't create message type from external definitions)
Futher reference:
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
BTW
while creating external defnitions (WSDL)
you can only choose wsld file or XML - nothing else
Regards,
michal

Final Cut 7 audio sync issue with external audio

Ok, I've seached around a lot and still haven't found the solution for this common issue, which is sync between video and audio wich were recorded in two different devices.
My video is from a conference (a lady speaking all the time) ProRess 29.97 and my audio is wav recorded at 44.1 Khz. I have already converted my external audio to a fine AIFF 48 Khz, and I have already re-imported it with the correct 29.97 easy setup, as it shows on this video www.youtube.com/watch?v=Nt-nfelM8KA. That helped a lot but audio still goes out on sync when playback goes further (not that much, but it shows).
On Premiere Pro, that wav file a correctly in sync, and I have had this issue before with FCP and now it has come back! help!
Anyone found a real solution for this issue?

Why not just use Premier? FCP is going to slowly die out anyways....
Anyhow, a work around... using the speed change tool (sss) adjust the audio to be the same length of the video so it is in sync... Press command-J, make note of the percentage you sped up your audio. Now open your audio in STP, select all of your audio go to Process>Timestretch and adjust the audio and apply the same percentage.
Listen to your audio. STP's time stretch is excellent because it adjusts the speed without changing the pitch.
Save as, re-import your audio.

Importing WSDL with external references issue

Similar Messages

Maybe you are looking for