hi there

 

strange things happens

 

i´ve xrecieved a couple of p2 files dvcpro hd then suddenly the chrome is not more x recieving p2 material i go normal to xrecieve from p2 folder but the browser to check out for the clip xml is not more opening it takes a while and then i´m back in the normal liquid overview!

I´ve tried the same card from another chrome xe which was also importing footage so far easily but it happens then the same problems! Now both systems cant import any p2 footage more!

any ideas how to get the xrecieve again back going!

 

thanks for any ideas 

Try and import from a completely different P2 card. It sounds like the data on the P2 card itself might be corrupt.

Thats not the problem since i´ve imported that card both machines will not xrecieve anything from p2 cards from any place the clip browser is not opening

any ideas 

OK, I understand. When you use XReceive it starts up a DLL that does the actual job of communicating with the camera. If the clip browser isn't starting, then there's something wrong either with the DLL or with how it's being loaded. I think your best option is to just re-install Liquid over itself. This should restore the DLLs if missing, re-register them if they need to be re-registered, etc. Then see if it works.

Yep that what i thought as well but after install liquid over itself it doesn´t make changes!

 

any ideas

 

thanks manu 

still the importdoesn´t work any ideas

cheers manu

Please take a look in the XReceive directory (C:\Program Files\Avid\Avid Liquid 7\XReceive by default) at the properties for the XReceiveP2.dll. What does it have for version number, and what's the size of the file?

Also, try deleting the XReceiveP2.ini file in that directory. This should be created each time you execute XReceive from P2.

That was it you are the man

 

i deleted the .ini and after that it was back working!

 Can you explain why?

Thank you very much!

 Manu

Normally the DLL creates the .ini file. It may be that it was trying to create a new .ini file before calling the dialog and ran into a file problem. Or it may read the old .ini file to set some default values and it couldn't read the file properly. In either case it might abort the execution of the DLL. Without having the source code (and I don't) it's impossible to say exactly why.

The important thing is that you're back up and running.

great thanks a lot

 

cheers manu