HELP!: MediaCore ImporterProcess Error; ImporterInstance.cpp-641

As some of you may know, I've been working on a documentary about MONOPOLY. First off, I've been frustrated with Premiere's inability to handle projects with lots of footage (we have 300+ hours) so I've had to make a bunch of mini-projects in order to log and clip the footage. But that is not my major problem.
We're getting closer to having a rough-cut done, but earlier this week when I was editing, I began getting a message I had never seen before. As most of you probably know, when you boot a Premiere CS4 project, it loads the basic necessities and brings up the project workspace and then loads the media files into system memory. When it finished loading my project file (containing about 3000 assets), it appears fine at first. However, once you start doing any scrubbing through the timeline, you get an error message "MediaCore ImporterProcess has encountered an error" and "[..\..\Src\Importer\ImporterInstance.cpp-641]". On the Adobe Forums, I can find only a couple other people with similar errors, but I was not seeing the additional error wording that they saw.
The weird quirk is that while it is still loading the media files, you can edit, play through timelines, etc. (Playing a media clip temporarily halts loading of any other media files)
I went into Windows Event Viewer and saw that the ImporterProcess Server was hanging each time that this error box appeared, and it listed dvacore.dll in the additional details about the System Error. I tried replacing that .dll with the matching .dll from Encore's files, from a generic .dll site, and reinstalling Premiere and the whole CS4 suite, and none of those fixed the problem.
This week, I've probably spent about 5-6 hours on the phone with Adobe, either on hold or dealing with one of several low-level techs who don't actually use the software so when I describe the problem to them, they are just searching on Adobe's own forums suggesting things that I have already tried. Despite my best efforts to get this problem escalated to a Level 2 tech to try to get some actual help, Adobe has not followed up with me.
I took the project file plus assets and hooked it up to a completely different computer running CS4 (completely different computer specs) and sure enough got the same error. At this point, I have no clue what to do for a next step to get my project running again.
Anyone who can provide me help or is willing to come look at my machine would be truly appreciated and if you fix it, I'll take you out for a nice dinner and give you a shout out in the film's credits.
Kevin Tostado
[email protected]
My system's specs: Custom-built; Windows 7 Pro 64-bit; 12GB RAM; Intel i7 920; Nvidia Quadra FX 1700; Adobe CS4 Prod. Premium; Footage is primarily stored on a Drobo Pro with 16TB of storage and the majority is 720P 24P in .mxf media (P2).
Time spent on phone with Adobe techs who don't actually help me: 5-6 hours;
Time I've spent troubleshooting problem: 36+ hours
Time that could have been spent editing project lost: 6+ days
Frustration level: Through the roof and currently orbiting the Earth

Harm,
Thanks for the suggestion, but that wasn't feasible on our case with 2TB internals being the largest drives on the consumer market right now, and with our limited budget. Additionally, I have to find a software- or hardware-based RAID solution other than the Drobo where I was comfortable that the data was actually backed up redundantly and that I wouldn't lose access to one of the drives.

Similar Messages

HELP! Installation error:fontObject.cpp,line 506

I can't install the 'j2sdk-1_4_2-nb-3_5_1-bin-windows.exe', Java 2 SE Platform 1.4.2 with NetBeans IDE 3.5.1
I get this error:"Assertion failed:errno==0 && count == (size_t) size,file
../../../src/share/native/sun/awt/font/fontmanager/fontobjects/fontObject.cpp,line 506"
How can I do, please help me~~~
THANKS.......

Erm, you don't say what your OS is...
Generally, most try to download and install SDK and NetBeans separately (in that order).

Crash on opening a new project in Premiere [..\..\Core\PropertiesImpl.cpp-641]

I get this error every time I try to open a new project in Premiere [..\..\Core\PropertiesImpl.cpp-641] what is the problem?

Hi Sandeep,
I removed my Blackmagic Desklink Quad Video Capture Card and am now getting the following error:
[..\..\Core\Propertiealmpl.ccp-569
My System information is as follows:
System Board = ASUS PGX 58D-E , Core i7 CPU x 980, 3.33 GHz
What is the OS and version = Windows 8.1 Pro 64 bit
Are you on a Domain / workgroup = No Network
What is the Graphics Card installed on the system = GeForce GTX 580
How much Ram do you have = 28G
Drive 1 - 1 TB SSD Samsung 840 EVO
Drive 2 - 1TB SSD Samsung 840 EVO
Drive 3 - 2TB HD
CD-ROM 1 - Pioneer BW-RW BDR-206
CD-ROM 2 - Pioneer Bw-RW BDR-206
Do you use any external Hard Drive = None
Are you using security software e.g. Norton, etc = Windows
All other applications work Word, PowerPoint, Excel, and Adobe PS, AU, AE IL
Thanks for your help,
Bill

I have encountered the new error "Fatal internal error fpinit.cpp line 7398

I get the error message "Fatal internal error fpinit.cpp line 7398".
I use:
TestStand 2.0
LabView 7.1
Vision 7.1
uEye USb Camera
I've included into my TestStand programm some new steps that control the uEye USB Camera.
I use following steps (all steps written in LabView):
- Initialze Camera
- Wait
- Close Camera
- Wait
I have the settings "Load dynamically" in TestStand"
If I use also the setting "Unload after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)
I detected also that sometimes in this case a constant in a other vi is emty.
Normally I use the setting "Unload when sequence file is closed" then I have the problem only sometimes at the first turn.
If the initialize Camera step is succesfull I have no problem with further camera steps.
Regards
Alexander
Attachments:
lvlog02-18-10-09-34-10.txt ‏1 KB
Copy of Error.jpg ‏76 KB
Copy of Error2.jpg ‏42 KB

Hi Alex,
I'd suggest to replace all ctl. with new ones.
Perhaps one of them is corrupt.
You will find a documentation about preferred execution system
in the LabVIEW help. I also attached this files.
Regards
DianaS
Attachments:
help1.gif ‏37 KB
help2.gif ‏11 KB

Premier Pro CS3 Error "time.cpp-390"

Please help!
Whenever I try to manipulate my timeline in Adobe Premier Pro CS3 on a short film that is nearing it's deadline, I get this error "time.cpp-390" followed by the software crashing. Any help?
Adobe no longer provides support for their product and their tech support help line is utterly useless. I have google searched the error and searched the forums... I own 15 CS3 Creative Suites and if they think I am upgrading to CS5.5 after this customer service experience... I may be moving to FC7.
I really need to fix this!
Thank you for any help you can be.

The event viewer gives me nothing, unfortunately. Thank you for the help though! I did find a solution though...
Reinstalling the software (the ONLY solution offered by Adobe support people) was entirely a waste of time. So was the nearly two hours I spent talking to four people on their support line just trying to get them to help me. I learned that if I just kept asking for a superviser, they would keep letting me talk to someone different. Apperantly, there is no end in the number of people who are considered "supervisors" at adobe...
Adobe provided no useful assistance other then telling me to reinstall the software. I am actually more than simply dissapointed with the complete lack of support and complete lack of effort in helping me find a solution to the issue. I actively suggest people use something other than Premier Pro for no other reason than a lack of integrity by the company in supporting thise who spend thousands of dollars on their products. Anyway... I hate them and I'm tired of crying about it.
SOLUTION TIME!!!
Ok, so here is the solution. The ONLY solution was to copy the timeline and the bin into a new, fresh project file. I started a new, empty project, then copy/pasted the timeline from the old to the new project. I did the same with the emaining contents of the bin and voila! the error stopped happening. I have NO IDEA why... but I know that it works and it only took me two days to figure out. In fact, all of the projects I have that are in various stages of completion, must be coppied into new projects in order to work. In other projects, I don't get the time.cpp-390 error, it just simply will not insert a clip no matter what I do.
So, I'm glad it works... I just wish I knew what the problem was.

Fatal Internal Error : "LinkObj.cpp

Hi,
I currently upgraded the system from labview 8.0 to labview 8.0.1 and did a mass complile.
However after doing that I am getting an error message reading "Fatal Internal Error : "LinkObj.cpp", line 587" everytime I close a particular sequence in TestStand. This error never used to occur before the update.
The error seems to occur when it tries to unload a particular VI which I use to add tasks in MAX.
I have tried repairing Labview but the problem still exists.
I would appreciate any help
Kewal
Attachments:
error message.JPG ‏15 KB

OK, now it's getting comical...
I removed the second mathscript node from clasclap.vi and created a dummy LV math operation to replace it. Called the new vi clasclap_part.vi (attached) and added it to the project in place of clasclap.vi. Built the dll as usual. BTW, I'm using the standard calling convention here, not the C language convention.
RESULTS: All of the called functions return zeros, even clasclap_part.vi. But some good news: the dll isn't crashing Visual Studio anymore.
Now I'm realizing that the functions returning zeros issue greatly overshadows the reason I originally started this thread. If I don't get any response, I'll start an independent thread that someone might take an interest in....
What might be helpful here would be if someone could (hopefully easily) take the summer .vis and the clasclap_part.vi and build their own dll. Then, try to call it from VB6 and/or any other language or compiler. What do you get?
(FWIW, I never mentioned that I'm not a fan of VB or Visual Studio. LabVIEW is far superior IMHO)
Here is the revised VB code which calls the dll:
Private Declare Function Summer Lib "summerlib" (ByVal a As Long, ByVal b As Long) As Long
Private Declare Function Mathscriptsummer Lib "summerlib" (ByVal a As Long, ByVal b As Long) As Long
Private Declare Function Doublesummer Lib "summerlib" (ByVal x As Double, ByVal y As Double) As Double
Private Declare Function Clasclap_part Lib "summerlib" (ByVal x As Double) As Double
Sub Form_Load()
Dim x, y, fx As Double
Dim a, b, sum As Long
a = 1#
b = 2#
x = 1.2345
y = 2.3456
fx = 1
sum = Summer(a, b)
fx = Doublesummer(x, y)
sum = Mathscriptsummer(a, b)
y = Clasclap_part(290.01)
End Sub
Thanks,
Ted
Attachments:
clasclap_part.vi ‏276 KB

"Fatal internal error:"memory.cpp",line 593"

I need some help.
Can some please explain what i am doing wrong here. i have created a Dll from a LV 7.0 vi. The header file looks something like this:
typedef struct {
long dimSize;
double elt[1];
} TD2;
typedef TD2 **TD2Hdl;
typedef struct {
double f0;
double df;
TD2Hdl magnitude;
} TD1;
void __cdecl Spectrum(double freq, double amp, TD1 *Spec);
And i have the following code where i allocate memory and attempt to call 'Spectrum':-
TD1 *Power;
double frequency=10, amplitude=1;
Power = (TD1 *) malloc(sizeof(TD1));
(*Power).magnitude = (TD2**)malloc(sizeof(TD2));
*(*Power).magnitude = (TD2*)malloc(5000*sizeof(TD2));
(*Power->magnitude)->dimSize = 5000;
for (i=0; i<500;
i++) {
(*Power->magnitude)->elt[i] = 0;
Spectrum(frequency, amplitude, Power);
I keep getting Fatal internal error: "memory.cpp", line 593" when it tries to call Spectrum. I believe i have allocated memory correctly although i may be wrong. (I was getting 'exception' errors before). The VI i used to create the Dll contains a basic 'Function Generator' (sine wave) and a 'Power Spectrum'.
I have looked at the Knowledge base and dll examples that come with LV 7.0 and have tried setCINArray and NumericArrayResize but have not had any luck. It seems like the documentation is for LV 6.0 and 6.1.
Has anybody seen this or have any idea why i am getting this?
Thanks

> Can some please explain what i am doing wrong here. i have created a
> Dll from a LV 7.0 vi. The header file looks something like this:
>
> double frequency=10, amplitude=1;
> Power = (TD1 *) malloc(sizeof(TD1));
> (*Power).magnitude = (TD2**)malloc(sizeof(TD2));
> *(*Power).magnitude = (TD2*)malloc(5000*sizeof(TD2));
>
> (*Power->magnitude)->dimSize = 5000;
>
> for (i=0; i<500; i++) {
> (*Power->magnitude)->elt[i] = 0;
> }
>
> Spectrum(frequency, amplitude, Power);
>
> I keep getting Fatal internal error: "memory.cpp", line 593" when it
> tries to call Spectrum. I believe i have allocated memory correctly
> although i may be wrong. (I was getting 'exception' errors before).
> The VI i used to create the Dll contains a basic
'Function Generator'
> (sine wave) and a 'Power Spectrum'.
> I have looked at the Knowledge base and dll examples that come with LV
> 7.0 and have tried setCINArray and NumericArrayResize but have not had
> any luck. It seems like the documentation is for LV 6.0 and 6.1.
>
It looks to me like you are constructing arrays to pass to LV using
malloc, instead of the labview.lib functions for creating or resizing LV
array handles.
You should refer to the manual on Calling External code for details on
the construction of an array.
Greg McKaskle

Fatal Internal error: "oleautomgr.cpp", line 2832

Hi,
I have a program developped with LV 8.2.1.
Now I have import this application with LV 8.5; if I run the VIs in Labview it works; when I run my program (executable version) I got this error
"Fatal Internal error: "oleautomgr.cpp", line 2832"
I got the error after I open a Diadem connection.
Another information: first time I have import the program in LV 8.5 and I have save the prj, LV ask me to overwrite all the VIs of the "Diadem addons". (Diadem connectivity); so I have uncheck "read only" in Diadem.llb and I have save the Vi.
Someone can help me?
Thanx a lot

For the community's future reference, this issue was resolved by the customer calling in for support, at which time it was determined that a Mass Compile of the VIs was necessary to eliminate the error. The process to mass compile is described here.
-Sam F, DAQ Marketing Manager
Learn about measuring temperature
Learn how to take voltage measurements
Learn how to measure current

Fatal Internal error: "oleautomgr.cpp", line 2832 when sending data by means of ActiveX methode

I have experienced error "Fatal Internal error: "oleautomgr.cpp", line 2832" during sending data to CAN card IXXAT iPCI-I XC16/PCI. LabVIEW communicates with that card by means of ActiveX methodes via "VCI Wrapper" which is COM object interface. Mass compiling of the project does not help. Card is initialized and configured propely. The driver card is working propely.
LabVIEW version is 8.5
The efect of that error is that labview completly shot down.
I appraciate any suggetions
thanks a lot

Hello,
Please try to reinstall the drivers for the CAN card, then make sure you close all references to the ActiveX control (at all levels) using the Automation Close primitive in LabVIEW.
Regards,
Emil

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

Internal error: "memory.cpp", line 593 with PXI 8175

Hi,
I have created a program with Labview RT 7.0 which makes acquisition, storage and display of data with PXI controllers 8175.
I used Datasocket for the data display on a deported computer.
Because of the number of the Datasocket tags used, instead of sending values all the time, I'm sending value for the deported computer only if the user needs to see it.
For example : if the user needs to see data, so only Datasocket tags for data display will be active, and if the user needs to see parameters values, so only parameters datasockets tags will be active. And, if the display program is in "standby" mode, almost all datasocket aren't active.
So when the user needs to see data values, he opens the data values window of the display program, and then, the datasockets tags for data value are now active, but : sometimes at this moment, the PXI stops with an "internal error "memory.cpp" line 593"!
The only solution is to manually reboot the PXI, the programmatically reboot doesn't work in this case of error. But it is far away from the displaying computer.
The error happens regularly after a 2 weeks period of standby. So I though about a memory overflow, I checked all the arrays, and none of them is growing to the infinity.
If someone knows about this problem, I will be very happy to learn about how to get rid of it!!!
Best Regards,
G Liagre
Best regards,
G Liagre

Hi Rob, Hi Matthieu,
Thank you for your reply.
I found in the database many reply about this error, but none of them were helpfull for me.
I tryed your link to the knowledge data base, but the error described there is for dll association in LabView and interface nodes.
I didn't used any interface node in my code.
The problem is that I cannot test my program on the PXI because I don't have access to it rightnow (only by remote desktop, and with a 56k modem..)
Let me give you a part of this huge code.
I suspect this part of the code to be the one which create the problem, but it's not sure.
If you find something obviously wrong, tell me!
Best regards,
G Liagre
Best regards,
G Liagre
Attachments:
Communication.zip ‏931 KB

TS1368 I cannot sync my iTunes library to my iphone 5 can you help I get error message connection could not be established to iPhone

I cannot sync my iTunes library to my iphone5 can you help I get error message a connection could not be established to the iPhone

Yes it is.
Initially I got an error message saying can't connect because of Date & Time settings.
Went in and re-verified that those were correct.
Tried to update downloads and then got a new error message: "Can't connect to iTunes Store".
I live in the US and that's where I created my iTunes a/d and Apple ID.
I am currently in India --- can that coause confusion re date & time?

Stop labview application from MS VC got internal error: image.cpp line 11450

Hi:
I need to control a labview application (It's been compiled as exe file)from my MS VC program. I tried using PostMessage(hWnd, WM_CLOSE) from whithin my program as MSDN suggested method to stop an application
cleanly. However, when i put my program in debugging mode and run it step by step, the LV program generate an internal error "image.cpp linexxxx" after it reached that PostMessage() call. in run mode , the Labview app simply ignore the WM_CLOSE message sent from my program.
So is there any other ways to stop labview application from VC program?
Thank you!
ls

> So is there any other ways to stop labview application from VC
> program?
You can use ActiveX. Turn the server on for your built app, open a
connection from VC, and use the app or VI properties to get LV to exit.
Greg McKaskle

HELP!HELP!HELP! Microsoft error message

Please help! When I try to edit a certain scene IN FLASH CS3,
microsoft error message pops up to send an error report. i was just
using that scene earlier today. WHAT THE HELL HAPPENED?
i can't even test the scene or movie! please help!
message:
Error signature
Appname: flash.exe AppVer 9.0.0.494

Hi, did you find a solution to this? I have the same problem
- except I can't even open any of my Flash files now. I'm heading
to tech support.

Installing Elements 11 on Mac. Need help with install error "Setup wants to make changes."

Installing Elements 11 on Mac 10.8.2. Need help with install error: Setup wants to make changes. Type your password to allow this." After entering Adobe password, nothing happens. Locked from further installation. Any ideas? Adobe phone support could not help.

Just before letting changes (installation in this case) be made on the system, Mac OS prompts for password & this has to be the Mac system password. This password prompt is the system's own native prompt & would accept the system password only. Please make sure it is the right system password (all/admin rights) and the installaion should run.

HELP!: MediaCore ImporterProcess Error; ImporterInstance.cpp-641

Similar Messages

Maybe you are looking for