Software error interns:: / Lassi / Main / XcodeProjects / authorCore / ../../Sonic/Common/FileSystem/FilesSpec.cp p, line 214

Hello,
This is a translation Reverso, saddened...
I realized a project still with Adobe EncoreCS5 English subtitles and at the time of verifying the project everything is OK but when I make generate he(it) marks me the recording of subtitles: software error interns:: / Lassi / Main / XcodeProjects / authorCore / ../../Sonic/Common/FileSystem/FilesSpec.cp p, line 214
What takes place t it?
Mélanie

Can't give any direct help... but 2 things stand out
AuthorCore means the error is generated by a code module licensed from Sonic... and those errors are notorius for being difficult, since the Sonic modules give out (from what I have read) errors that may, or may not, be reported back to the Adobe interface with any degree of accuracy
But... FileSpec makes me think of some saved messages that MAY help
As well as the below, right click the program icon and select Run as Administrator, which is NOT the same thing as running the computer with the Administrator account, and which fixes several "odd" problems... To create a two layer DVD (or a BluRay?), you MUST have Encore set to use the Run as Administrator option
Run as Administrator http://forums.adobe.com/thread/969395
Odd Errors http://forums.adobe.com/thread/670174
Long File Names or odd characters cause problems
Read http://forums.adobe.com/thread/588273
And #4 http://forums.adobe.com/thread/666558
And This Message Thread http://forums.adobe.com/thread/665641

Similar Messages

Internal Software Error While Building DVD

After running a "Check Project" with no errors, when I go to "Build Project" the progress bar progresses through ordering all of the audio and video for the DVD, and then when it starts to burn the content, I get the following error:
"internal software error: /Lassi/Main/XcodeProjects/AuthorCore/../../Sonic/DVDCreator/FormatLib/Vobulator/TitlePlan ner/CGOPGrouper.cpp, line 410"
Anyone...please!? Thank you.

If you have CS4, there is an update you need to do
Encore CS4 Roxio component problem http://forums.adobe.com/thread/400484?tstart=0
More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
Also... some things that are legal in Windows cause problems
Long File Names Cause Crashing http://forums.adobe.com/thread/588273
And #4 Here http://forums.adobe.com/thread/666558?tstart=0
And This Message Thread http://forums.adobe.com/thread/665641?tstart=0

In adobe Encore "internal software error"

If you try to create a DVD image in adobe encore,
It is not possible to create is displayed: "Volumes / Builds / Amawat / Main / XcodeProjects / AuthorCore / / / Sonic / DVDCreator / FormatL ib / Vobulator / BlockPlanner.cpp, line 217 internal software error...." He said.
Those of other projects can be created without any problems.
Please tell us the cause.
Machine specs
iMac (2013)
OS: 10.9.3
Memory: 16GB
Adobe Version: CS6
Since it has been translated using the "Google Translate" in this sentence,
There is a possibility that there is a portion that is disturbed, such as some grammar.
Please note.

This links may help
http://forums.adobe.com/thread/1309029 http://docs.roxio.com/patches/pxengine4_18_16a.zip
http://corel.force.com/roxio/articles/en_US/Master_Article/000012592-PX-Engine-Description -and-Download

Internal Software error PGC for encore CS3 !!! solved !!!

Almost everybody here knows the next error:
PGC "timeline name" has an error at xx:xx:xx:xy internal software error : %0, line timeline name - PGCINFO: name= timeline name, ref=BPGC, time=xx:xx:xx:xy
Where the y in time stands for the length of the timeline minus 2 frames. The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
It kept me awake for weeks and after reading this forum several times and comparing encore CS3 with encore 2.0 filenames I found the solution.
This Error is a bug in encore witch has nothing to do with blank filename spots and sonic coding or codecs or planning your workflow with a pencil but pure with the combination Adobe Premiere Pro CS3 and Encore CS3.
This is what generates the problem:
In Adobe Premiere Pro CS3 you build project with video, sound and chapters. Then you export the project via the Media Encoder not Multplexed.
Premiere CS3 then creates the following files:
filename.M2V (video file mpg)
filename.AC3 (audio file ac3)
filename.M2V.XMPSES (an adobe file with preview info and chapter pointers)
filname.XMP (??)
It is the .M2V.XMPSES file witch creates the PGC error. If you use the MULTIPLEX DVD option then ADOBE will not create the .M2V.XMPSES file so there will not be an error. This trick mentioned by ADOBE and many others is just to go around the bug instead of solving it. Also with multiplex you have just one sound track. I use two sound tracks like 5.1 and a 2.0 track witch you can choose in a menu.
Some people say it is the blank spots. Also not true. They have probably just erased the blank spots of the M2V file and forgot the .M2V.XMPSES file.
When you just delete the .M2V.XMPSES file and then open the M2V and AC3 file in Encore as a new asset, make a timeline and menu's and the project will built and burn. Only if you delete this .M2V.XMPSES file Encore takes a longer time to import the M2V file and will be without the chapter points.
Almost everything else will work like menu with sound and even a movie background (use M2V files). Only the motion buttons in a menu still wont work unless you use a black background !?!. Haven't figured this out yet. Only solution for this is use Encore 2.0. In this older version also the motion buttons will work without error's (everything else also so why buy CS3??)
Here is what you must do create a DVD without errors:
-Create a project in Premiere Pro, even with chapters.
-Write down all chapter points (minutes:seconds:frames)
-Create two new unique maps in explorer for example D:DVD1 and D:DVD2
-Export in Premiere with Media Encoder without the Multiplex:DVD but with NON to the D:DVD1 map
-Copy from D:DVD1 only the M2V and AC3 files to D:DVD2
-Start up Encore DVD CS3 or 2.0
-Create a new unique project in Encore for example "DVD" and save this in the map D:DVD2\
-Then use Save-as (under file) and pinpoint to D:DVD2\dvd to be sure that all Encore's files are placed in this folder.
-Select M2V file and make new timeline.
-Make chapter points (you wrote down the points, did you?)
-Create menu's, even with sound (AC3) and movie background (M2V)
-Then render project if you have used a video for menu background
-Finally Built and burnnnnnn!!
-If you like to use motion buttons in a menu then use Encore 2.0
I have double checked my work flow and it really works. I have built a project and burned with success Then I deleted the timeline and the M2V file. Copied the .M2V.XMPSES file in the used folder. Re loaded the M2V file in encore (this time much faster! and with chapter points). Tried to built and burn and back was the error. Also this happened in in Encore 2.0!!
Hope that this will solve the PGC error once and for all !!!
Marcel W
system:
acer aspire AMD 64 3800+
2 GB
250 GB hard drive for system
750 GB hard drive for movie
software Adobe Encore 3.0.1.008, Premiere PRO 3.2.0, Photoshop CS3 10.0, All upgraded
NERO 7
No Internet

> Where the y in time stands for the length of the timeline minus 2 frames.
This can actually vary, and so far at least, I don't think we've seen a pattern as to type of pgc error based on how many frames from the end it reports.
> The BPGC error can also be FPGC or DPGC dependant on how many menu's there are in the project.
Number of menus is not relevant; the iteration of the first letter is more related to subsequent occurrences of the error. In my current tests it did not always update; they may have been too similar.
> This is what generates the problem...
Well, the problem does not occur every time you do what you describe, any more than it occurs every time spaces are left in the file names. What you have is, as some other suggestions, a workaround. Thats not bad, and I wonder if you are onto something as to what is contributing to the problem.
So, on to the interesting part whether the xmpses file, or at least what Encore is doing with it, is contributing something. I took an old test project that throws the PGC error and did some experiments.
Background. I am a user who does get the pgc errors regularly, but not always. Creative Suite Production Premium, with PPro CS3 3.2.0 (374) and Encore 3.0.1.008. Pentium 4 2.8GHz 2G RAM, XP SP3, Multiple drives, Nvidia GEforce4 MX440 i.e. an older system. I have lots of stuff loaded and running, including virus protection and firewall, so there are any number of potential conflicts. But I get no crashes, and only one problem other than the pgc. (PPro and Encore monitor windows do this diagonal thing I suspect the display card, but the drivers are up to date. Maxing and then back to fit fixes it.)
If you want to attempt to replicate my studies, here is a link to my problem clip and the first Encore project I describe.
http://www.videoandcomputer.com/test/pgc_test.htm
This project involves a very short AVI export from PPro CS3 - just over 8 seconds - called pgcbad_clip1.avi. Just to answer any question, the source is dv camera capture, and the source and avi export I use are dv avi type 2. There were no effects added on the timeline.
Test 1: Create a project in Encore CS3. Use the sunset menu and delete all the buttons except "play all." Import the avi as a timeline. Set the timeline end action as "return to last menu" and set the button link to the timeline. Auto transcode. (Project settings are 8mbps max and a3c.) Check project shows okay; there is never a problem with that. Build to a DVD folder in a new folder. This project throws the pgc error.
Test 2: Now create a new Encore project in a new folder. Use the same process, except import as timeline the m2v and a3c files from the first run. (I.e. if the clip is pgcbad_clip1.avi, in the test1 project folders, there is a folder called pgcbad_clip1.avi that has 6 files.) Note that in the folder they are imported from is an xmpses file from the first project's encore transcode. The build again fails with the pgc error - same frame, etc, but I really think the frame number doesn't matter.
Test 3: Now create another new Encore project in a new folder. Use same process, but before importing the m2v and a3c as timeline, delete the xmpses file. Drumroll...... Build succeeds!
Go figure.
This is not the repeatable bug option weve been looking for, but based on a clip that always fails, it does demonstrate the odd event of deleting the xmpses file as a workaround. I wonder if that will give adobe something to work with.
Can anyone else get my clip to work/not work in a straight project?
Test 4: Just to answer the question since the avi file fails here, will the elemental option succeed? I exported elemental m2v and wav from PPro, used the same project process, and transcoded the wav. That build also works! I have seen this work both ways. I have had projects where the elemental failed, and an avi export worked. I do believe the elemental options work more consistently. But my project that I completed yesterday used all avi exports, animated buttons in the submenu, - no pgc error.

How do you get Encore to work? Internal software error.

I've made a new project with Encore CS4 consisting of mainly slideshows and about 2 movie timelines. I've created menus to be how i want them.
When i go to build the project about 9/10 it doesn;t work. Sometimes it just crashes and gives a crash report. other times it does all the building slideshows and motion menus then starts the prepare build and comes up with internal software error, and build stops.
This is extremely frustrating as it takes serveral hours to get to this stage every time because it has to re build all the slideshows.
It has only worked once, and it wasn;t quite what i wanted so i made some minor adjustments (added a pic in a slideshow, or music to a menu) and since have tried twice to rebuild it and it hasnt worked.
Encore seems like it could be really good but all its bugs make it a piece of crap.

I don't remember the dimensions, but I have read messages that pictures that are too large will cause problems... maybe someone will come along who knows the actual size and can tell you
Also... This is aimed a Premiere Pro, but may help
First, work through all of the steps here http://ppro.wikia.com/wiki/Troubleshooting
If your problem isn't fixed after you follow all of the steps, report back with the DETAILS asked for in the questions at the end of that link

Internal software error: .\Vobulator\BlockPlanner\BlockPlanner.cpp, line 217

What is this about?

I also got the "Internal Software Error...Vobulator...Line 17" error in Encore CS6. One of my timelines had diagonal gray bars for the last 50 or so seconds and the culprit was the chapter marker I had placed within that (apparently) forbidden zone. Once I removed the errant marker (who needed that one anyway?) the error messgage disappeared.
For the record, I had eliminated everything in the but the First Play video (in other words the Main Menu, two timelines and a playlist did not appear in the Flow Chart) and I still got the error message. I tried renaming the timelines, using underscores instead of spaces, etc.
I also tried running Encore as an Administrator - didn't work.
Removing the chapter marker in the greyed out area at the end of a video clip was the only solution that worked.
Now if I could only figure out why the end of that clip - and only that one clip - was grayed out...

FPGA An internal software error has occurred. memory write

Hi everybody
We are encountering an error during compilation of an FPGA VI. It is probably related to our use of FPGA block memory. We have a non-timed while loop that is reading from an FPGA host-to-target FIFO and writing into block memory (inside a sub-VI called z_scan_write.vi). In another loop (this one is timed-loop), there is a subVI called we z_scan_read.vi, inside which we read from the block memory.
Does anybody have an idea what is going wrong and how we could avoid this problem? Thank you very much in advance for any hint!
The full error message is as follows. Note that it refers to the above-mentioned two subVIs z_scan_write.vi and z_scan_read.vi...
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
nirviUIDToObject.vi<ERR>
Error getting object reference for UID.
All text parsed:
<CodeGenErr>
<ErrorCode>-61060</ErrorCode>
<DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
<Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
</ErrorInfoCallback>
</LineInfo>
<TreeInfo><TreeID>ProjItem</TreeID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
<UID>2747</UID>
<ObjectName>Memory Write 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>194</UID>
<ObjectName>Memory Read 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61060</ErrorCode>
<DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
<Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
</ErrorInfoCallback>
</LineInfo>
<TreeInfo><TreeID>ProjItem</TreeID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
<UID>2747</UID>
<ObjectName>Memory Write 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>194</UID>
<ObjectName>Memory Read 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
Solved!
Go to Solution.

Removing the two subVIs that read from/write to the block memory doesn't avoid the error showing up during compilation. The error details are obviously different now; they don't refer to the two subVIs (mentioned in the previous post) anymore...
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
nirviUIDToObject.vi<ERR>
Error getting object reference for UID.
All text parsed:
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>

When I try to burn a DVD in Premiere Elements 12 I get an Internal software error%0, line %

When I try to burn a DVD in Premiere Elements 12, I get an Internal software error %0, line %1. This is the first time that I have tried to use this program.

As suggested in the original reply in January, you will find best advice over on the video forum. Most of us here are photographers.
Click on the link below and copy and paste your question again. Good luck.
Video questions: Click here for Premiere Elements Forum

Slide Show ERROR, Internal software\Vobulator\BlockPlanner\.cpp Line 217

I'm putting together a slide show DVD. There are a total of 7 slide shows containing 480 pictures. All pictures are jpg's about 1000X1600 pixels and 500KB-700KB each. I have 3 menus for navigation. Not all of the chapter menu buttons point to a "slide show", some of them point to a picture inside certain slide shows according to my client's requests. (example, slide show 1 contains 70 pictures. Chapter 1 points to "slide show 1" Chapter 2 points to "slide show 1 photo 50"). All slide shows are linked so that when the first slide show is over, it will automatically "end action" to the next slide show etc... All my settings are typical. NTSC 4:3 SD 720X480 progressive.
There are NO video files in my DVD at all. No timelines at all. No audio at all.
The Symptoms/problem that I'm getting is this, when I try to Preview my DVD and ALSO when I try to build my DVD, the build will go through and "build the slide shows" then after it does that, this will come up
I've read some of the previous posts (one of them is in French for cryin out loud. Had to use Bing translator and it sounds all weird). What I can gather is this,
Re: internal software error: .\Vobulator\BlockPlanner\BlockPlanner.cpp, line 217
I found out it was due to selecting an image file as the video layer
in a menu, causes the error everytime. I just paste the image in with
'edit in photoshop' instead now. But thanks."
Another person said just about the same thing... The only problem is, I have no idea what this means. I don't know what it means to "select an image file as the video layer in a menu..."
Hardware/software is as follows:
custom build:
i5 processor (4 core) 2.6ghz
8 GB RAM 1333MHz
300GB C: drive (2X150 GB 10K RPM Raptors)
1.2TB D: drive (2X7,200 RPM 640GB WD's)
Burner is LG Super multi
secondary burner is Sony Commercial Blu-Ray burner
Video card is Saphire Build (Radeon 5450 PCI-E 16X)
Windows 7 X64 Pro
All Adobe is CS5 Production package.
If I'm leaving anything out, please let me know.
HELP! and Thanks. I'd really love to fix this without rebuilding the whole DVD. Take long time.
TEX

You really gain nothing by posting the same thing twice... http://forums.adobe.com/thread/971701

An internal software error has occurred. Error code: 1003

Dear, I am working on a FPGA programming. When I use the VI: "High Throughput Add Function". Some error occur.
Internal software error(s):
Error code: 1003 (refer to details)
Details:
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 1003 occurred at E:\Program Files (x86)\National Instruments\LabVIEW 2012\vi.lib\rvi\FXPMathLib\FxpAdd\modGen\nifxpmath_Add_EmitCode.vi: There's a broken VI

Hello Yjin,
Can you show me a VI in which this error occurs?
Which software versions are you using?
An easy way to find this information is as follows:
http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4?OpenDocument
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Error -20023 internal software error

Hola a todos. Soy un nuevo usuario del labview y mientras intento aprender algo me he topado con un error que no entiendo a la salida de un filtro:
Software error ocurred in no asociated comand id on axis control error -20023 internal software error please contact ni for suppor
Lo que hace el programa no es problema. La cosa es que si quito el filtro funciona bien.
Para hacerlo funcionar utilizamos una señal simulada de una 9239 creada con MAX.
Si alguien puede darme alguna idea, se lo agradeceré un monton.
Attachments:
prueba3.vi ‏291 KB

Hola Gonzalo el código de error es de un filtro y el VI que estas utilizando para interpretar los errores no te da una descripción adecuada porque ese es para Motion, y en este caso no lo estas usando por eso la descripción del error no tiene sentido.
Aquí el erro puede ser por poner rangos inválidos en la frecuencia de muestre, o corte, o debido a que no hay información en el waveform. La siguiente liga tiene mas información:
http://digital.ni.com/public.nsf/allkb/ABBD3A7BC25E17C8862561270058A4A0?OpenDocument
Saludos
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Internal Software Error occurred in MIG software DAQmx

Hi All, I have a very disturbing problem. Ever since upgrading to Labview 2011 and NIDAQ951f1 I get errors like the following in code that uses DAQmx:
Error -229771 occurred at DAQmx Create Channel (AO-Voltage-Basic).vi:1
Possible reason(s):
Internal Software Error occurred in MIG software. Please contact National Instruments Support.
The strangest thing is that this happen only when I run the VI while a LV project is open! It does not matter wether the VI is part of the project or not. As soon as I open any project (or create a new empty project) the error occurs when I run any DAQmx code. To test I am using one of the DAQmx example files: Cont Gen Voltage Wfm-Int Clk-On-Board Regeneration.vi for now, but the problem occurs with the other examples as well.
I tried to resolve the issue by removing all NI software and doing a clean install, but the problem persists. Needless to say I cannot do any development this way.
Any idea what's going on? Please advice.
Best regards,
Dixie

Hello Dixie,
There is a knowledge base topic treating this issue --> http://digital.ni.com/public.nsf/allkb/03123D0E8A36C48E862577A4005B6BAA?OpenDocument
Have you already had a look at it?
The problem you have can also be somewhere network-related. As some networking feature are handled by the Project Explorer, this can explain why you encounter the issue only when it is open. I propose that you first check the knowledge base and then keep me updated. I will give you further info if that does not solve the issue.
Cédric | NI Belgium

Internal Software Error in MIG

Running Windows XP SP 3
Labview 8.2
Error:
Error -229665 occurred at DAQmx Create Channel (DO-Digital Output).vi:1
Internal Software Error occurred in MIG software. Please contact National Instruments Support.
No new devices installed.
When opening MAX no devices listed in Device & Interface category. Same error with other VIs.

Did not work for me as the tool returns an error.
Instead I used MAX : Tool>>Reset Configuration Data after making sure I first exported all my configuration (devices, tasks, channels, scales...) as described here. Then the Max config was imported back in.
L.
PS: The issue manifests itself with DAQ Device control drop downs not seeing/finding any device: the drop down does not drop at all.
Some VIs using Daqmx open with many GUI object not showing up at all, and LV stops responding. (LV 2011). This issue appeared first after installing daqmx on a Win 7-64 laptop...

Internal Software error

Hi,
When I compile my fpga target vi i got an internal software error shown in the attached picture.
The program I'm working on is somehow complicated and the target file size is about 801KB and I also used 15 target-scoped FIFOs to transfer data within the target. I've also attached the log file. Does anyone know what caused this problem? Thanks in advance.
Attachments:
Untitled.png ‏40 KB
lvlog2011-10-06-13-05-10.txt ‏4 KB

It is an internal error generated by the application. I think the disc is still ok since the application is still preparing the data for burning to the disc and the actual burning has not yet started. Try running the program again and see if the error is still the same. If it displays a constant error every time you try burning the project, it is either the application can’t handle the size of the data that is going to be burned or there is an error in your system.
Run a disk check on your computer to see if there is any error that is preventing the application from working properly.
Right click on drive C and then select Properties.
Click Tools tab.
Click Check Now button.
Check Automatically fix file system errors and then click Start.
If no error was found try launching the application again. If it’s the same, use other video editing application where you can burn a video also.
http://www.techyv.com/

FPGA Internal software error

Hi,
I'm using labview 2009. When I compile the fpga target vi, i got the following message:
" An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:#,910x,907x,911x,783x;781x,785x;784x,910x,907x,911x,783x;781x,785x;784x,9101;9102;9103;9104,9072;9073;9074;9144;9601;9602;9611;9612;9631;9632;9641;9642,9111;9112;9113;9114;9116;9118,7830;7831;7833;7811;7813,7851;7852;7853;7854;7841;7842,9101;9102;9103;9104,9072;9073;9074;9144;9601;9602;9611;9612;9631;9632;9641;9642,9111;9112;9113;9114;9116;9118,7830;7831;7833;7811;7813,7851;7852;7853;7854;7841;7842,Onboard,Onboard,Onboard,Onboard,Onboard,Derived,Derived,Derived,Derived,Derived#,,,,,,,,,,CONST_TCO_SPI,12.5,13.5,11.25,14.5,12.25,9.25,13.5,7.5,11.25,8.5CONST_TSU_SPI,2,4,3,2,4,4,4,4,4,4CONST_TH_SPI,4,4,4,4,4,4,4,4,4,4CONST_TSU_PLUS_TH_SPI,6,8,7,6,8,8,8,8,8,8#,,,,,,,,,,CONST_TSU_SSMISO,6,6,6,6,6,6,6,6,6,6CONST_TH_SSMISO,4,4,4,4,4,4,4,4,4,4CONST_TSU_PLUS_TH_SSMISO,10,10,10,10,10,10,10,10,10,10#,,,,,,,,,,CONST_9201_TCO_SPI,10,10,10,14.5,12.25,9.25,10,7.5,11.25,8.5
Method Name: <b>Compile For Target</b>"
Does anyone know what caused this problem? Thanks in advance.

Hello Kb1126,
To better be able to answer your question could you please share what RIO device you are working with, the RIO device software and any relevent Xilinix tools versions, as well as the possible version installed on your RT target (assuming you are using a RT controller to interface with your FPGA).
Thanks,
Blayne Kettlewell

Software error interns:: / Lassi / Main / XcodeProjects / authorCore / ../../Sonic/Common/FileSystem/FilesSpec.cp p, line 214

Similar Messages

Maybe you are looking for