internal software error: Vobulator/BlockPlanner/BlockPlanner.cpp, line 217 creating menu

Similar Questions

• Internal software error in PE9

  Hello

  I'm trying to 'share' a project.  I'm looking to make a DVD.

  I'm not having much luck.  Whenever I hit the button burn the following series of events takes place:

  It seems succesfully encode media because once this process is at 99% for a few moments, he goes to the media of compilation.  At the moment where he is compiling media he recorded 95%.  It takes a few minutes to up to 99% and then I get the following error:

  Internal software error: vobulator\blockplanner\block planner.cpp, line 215

  Anyone have any idea what this means and if yes, how can I solve this problem?

  Some information:

  The file is large (at least compared to what I usually do)-55 minutes of mpeg2.

  My computer description is:

  Dell Studio XPS 435MT

  Intel Core i7 processor

  920 @ 2.67 GHZ

  8 GB Ram

  64 bit

  Thanks for the help!

  Try initially "burn folder" to see if it's PRE or a problem with your burner or media.

  See you soon,.
  --
  Neale
  Insanity is hereditary, get you your children

• Continue to receive the Error Message: internal software error: internal software error: line 332

  Try to burn a DVD and I get an error message. The full message is:

  internal software error: / Volumes/versions/Amawat/Main/XcodeProjects/AuthorCore /... /... / Ulator/TitlePlanner/CVOBUPlanner.cpp Sonic, DVDCreator, FormatLib, Vob, line 332

  Don't know what that means. Was working fine this morning, came back and kept getting the message. I even got a new project from scratch and rebuilt everything and still get the error message.

  Help, please.

  What version of yet?

  The chapter on each other or too close to beginning or end markers?

  Several videos on a timeline?

  If this isn't the case, you use the dynamic linking?

• New burn to DVD problem in EP - 12 - get this error: '.\Vobulator\TitlePlanner\CVOBUPlanner.cpp, line 331. '

  Had problems recently with

  PE - 12 does not project load existing; now are asked to record the trial version

  created by A.T. Romano in Premiere Elements - see the discussion complete

  Saved this project by working from a project file "AutoSave", has managed to 'Turn on' the software and continue this project and launch new projects.

  Now came across this question in a new project when you save a DVD with menus simple, provided... models burn to DVD problem in EP - 12 - get this error: '.\Vobulator\TitlePlanner\CVOBUPlanner.cpp, line 331. '

  Before the "Activation" problem I had burned several DVD with and without menus/authoring...what has changed?

  Any help on this?  I have seen this error on the Adobe Encore forums as well...

  Thank you for your support.

  Mercenary of digital media

  The name never give up...

  a. I have not given up on stop markers yet... Please delete the timeline stop markers and determine if that Vobulator error is always present.

  Have you looked at the spacing between menu chronological markers, set up transitions and titles?

  Thanks for the follow-up. Keep a positive thought for the markers of the judgment in general or too close to the end if this is not the end.

  RTA

• Status code: internal software error-223091 occurred in the DSA software. Please contact National Instruments support

  Hello

  I work with card 4461.

  When writing the data on the card I get this error

  The channel which has been set up had

  Update rate: 9210

  None of the samples: 87643

  Sample mode: finite samples

  Sync: Synchronization with AI0 even of the same device

  The values lie between 6 V and 1 .2V

  error occurred in the function .

  {Message of error =-223091 = "internal software error occurred in the software DSA. Please contact National Instruments Support.\n\nTask name: Magnet\n\nStatus Code:-223091 "}"

  The Stack Trace:

  «to nNIMSSAIL100.StatusObserverT<><>otNetApi > >.» CheckWithName (StatusObserverT<><>otNetApi > *, tCaseInsensitiveBasicString\\,_STL::allocator\\,nNIDMXS100::tLocaleConsideringWideStringComparitor\\,nNIDMXS100::tLocaleConsideringWideStringCaseForcer>* pName) \r\n

  to nNIMSSAIL100.StatusObserverT<><>otNetApi > >. Check (StatusObserverT<><>otNetApi > *) \r\n

  to nNIMSSAIL100.StatusObserverWrapperT<><>otNetApi > >. Check (StatusObserverWrapperT<><>otNetApi > *) \r\n

  to nNIMSSAIL100.WriteotNetApi >, class nNIMSSAIL100::AnalogWrite, double > (tTask *, Double *, UInt32, UInt32, UInt32, Double, Boolean, Boolean, tScaledDataFormat, StatusObserverT<><>otNetApi > *) \r\n

  to nNINETAI2005100.Write1DotNetApi >, class nNIMSSAIL100::AnalogWrite, double, double, cli::array^ > (task task, Double [] buffer, UInt32 numChannels, UInt32, UInt32 numSamples lines, Double timeout, Boolean autoStart, Boolean interlace) \r\n

  at NationalInstruments.DAQmx.Internal.AnalogSingleChannelWriterImpl.WriteMultiSample (Boolean autoStart, Double [] data) \r\n

  at NationalInstruments.DAQmx.AnalogSingleChannelWriter.WriteMultiSample (Boolean autoStart, Double [] data) \r\n

  Project.Analog1ChannelWriterTask.Write (Double [] data, Boolean AutoStart) in C:\\Project\\AnalogWriterTask.cs:line 446\r\n

  to Project.HardwareIO.WriteAO (Double [] Data, Boolean AutoStart) in C:\\Project\\HardwareIO.cs:line 120\r\n

  at Project.DataAcquisition.RunAcq (C:\\Project\\DataAcquisition.cs:line 182\r\n)

  at Project.DataAcquisition.Run (C:\\Project\\DataAcquisition.cs:line 68\r\n)

  at Project.Program.ThreadFunction (C:\\Project\\Program.cs:line 47\r\n)

  at System.Threading.ThreadHelper.ThreadStart_Context (Object state) \r\n

  at System.Threading.ExecutionContext.Run (ExecutionContext executionContext, ContextCallback callback, Object state) \r\n

  to System.Threading.ThreadHelper.ThreadStart ().

  TargetSite:

  {Void nNIMSSAIL100.StatusObserverT<><>otNetApi > >.} {CheckWithName (nNIMSSAIL100.StatusObserverT<><>otNetApi > *, nNIDMXS100.tCaseInsensitiveBasicString\,_STL::allocator\,nNIDMXS100::tLocaleConsideringWideStringComparitor\, nNIDMXS100::tLocaleConsideringWideStringCaseForcer > *)}

  I am using VS2005 c#

  Please tell me what wroing

  Kind regards

  Alok dandois

  Hey Alok,.

  This error code means that the revision of the map is more recent and not yet supported by the driver.  That the release of new versions of the same map with new features, the ID usually changes requiring a new version of DAQmx.  Try upgrading to the latest version of DAQmx and try again.

  While you're there.  See if you can find the product ID located in Device Manager (if you are using Windows).  Once in the Device Manager, right click on the device and click Properties.  Go to the Details tab, and then copy the entire string that is displayed under "Device Instance Id".  It should look something like PCI\VEN_xxxx & DEV_xxxx...  Paste in a reply in this thread can I be sure of your problem.

  Germano-

• Internal software error of LabVIEW FPGA Module - 61499

  I get the error next (in a pop-up window) in the phase of sompilation for the FPGA target with a vhdl IP. This error continues to occur even after restart LabVIEW and the PC. Someone at - it solved is this kind of problem before without having to re - install the software?

  Here is the error information:

  Error-61499 occurred at niFpgaXml_GetValue_String.vi<><><><>

  Possible reasons:

  LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has occurred. Please contact National Instruments technical support on ni.com/support.

  Additional information: lack the tag required XML (/ CompileServerList)

  As a first step, I can compile the vhdl IP node successfully. However, once when I'm running a VI with the FPGA, the bureau stop working. After that I restarted by force, it cannot perform the build of a vhdl IP node. Even without connecing to the jury of LabView, he pointed out errors before the end of the sompilation.

  Interestingly, the screw which also includes nodes IP vhdl that I properly compiled before, I can still run the VI to the Commission and it works correctly.

  Thank you

  Looks like your ActiveJobsList somehow has been corrupted. I saw occur when computers are hard stop or blue screen during compilation. I don't have that LabVIEW 2014 installed on my machine, so your path will be a little different, and the file extension will be a .txt or .xml instead of .json, but try this:

  Move the file "C:\Program Files (x 86) \National Instruments\LabVIEW 2014\vi.lib\rvi\CDR\niFpgaActiveJobList.json" (or your equivalent) out of the above directory (back it upward and delete essentially) and restart LabVIEW. Must regenerate the file and resolve the problem.

• An internal software error occurred. Error code 8. LabVIEW: File permission error.

  I just changed a few contasts to controls in an FPGA core program, so there need to be recompiled.

  but it after compiling the program showed the error.

  An internal software error occurred. Please contact National Instruments technical support on ni.com/support with the following information:

  Error 8 has occurred to copy in nicrio_StockOutputVhdlAndInstantiation.vi-> nirviGetInstantiation___cRioStock_io.vi-> nirviGetInstantiation___nirviEIOImplementation_modGen.vi-> nirviGetInstantiation___nirviEIOImplementation_modGen.vi.ProxyCaller

  Possible reasons:

  LabVIEW: File permission error. You do not have the correct permissions for the file.
  =========================
  NOR-488: Error detected DMA hardware.

  C:\NIFPGA86\clntTmp\TensionCo~65_FPGATarg~A7_FPGABase~A1_eogs1jH0~18\Crio9426IoNode.vhd

  Ca person the reasons for which he showed an error.

  

  Hello

  I have a few questions,

  1. If you redefine your controls with constants, that you always get the same behavior?

  2. what equipment you try to deploy to? If it's a cRIO, have you formatted your controller and reinstalled the software for it?

  3. I did a little research and it looks like a potential problem may be with firewall/antivirus. Here is the document that explains that:
  http://digital.NI.com/public.nsf/allkb/D8D46FD4DBD1015786257540003B2DC6

  You have an antivirus installed on the computer? You can try to disable it and rebuild the bitfile?

  Kind regards

• LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has Unknown

  Sir/Madam,

  Note Labview 2012 SP1 installed about 2 weeks ago.,.

  Accident occurred during the compilation of an fpga vi who worked satisfactorally in the past.

  When I restarted and went to the message recomplile "LabVIEW FPGA: an internal software error in the LabVIEW FPGA Module" see attached picture of popup.

  I reinstalled Labview in its entirety and backed out the changes I made to the vi but still get the same message.

  Thanks in advance

  Daryl

  It turns out that the question was in the VI and not of LabView FPGA module as the message may indicate. I created a vacuum vi, cut and pasted items in this from the vi error and recompiled and it ran very well.

  Somehow the vi has been corrupted internally.

  Thank you it's fixed.

• FPGA an internal software error occurred. writing of memory

  Hello world

  We encounter an error during the compilation of an FPGA VI. It is probably related to our use of block FPGA memory. We have a non-timed while loop which is reading a host-target FPGA FIFO and writing in memory block (inside a Subvi called z_scan_write.vi). In another loop (this one is timed loop), there's a Subvi we called z_scan_read.vi, within which read us of the memory block.

  Does anyone have an idea what goes wrong and how to avoid this problem? Thank you very much in advance for any suspicion!

  The full error message is as follows. Note that this is for the two subVIs z_scan_write.vi and z_scan_read.vi...

  An internal software error occurred. Please contact National Instruments technical support on ni.com/support with the following information:
  nirviUIDToObject.vi
  Error getting of to the UID object reference.
  All the analyzed text:

  
  -61060
  C:\Program Files (x 86) \National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi
  zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s
  
  
  ProjItem
  
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.z_scan_write.vi_FPGACompileCopy00000021.VI
  2747
  Memory write 'memory method Node '.
  
  
  ProjItem
  
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.z_scan_read.vi_FPGACompileCopy00000001.VI
  194
  Reading memory "memory Node method.
  
  
  ProjItem
  
  
  
  

  
  -61060
  C:\Program Files (x 86) \National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi
  zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s
  
  
  ProjItem
  
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.z_scan_write.vi_FPGACompileCopy00000021.VI
  2747
  Memory write 'memory method Node '.
  
  
  ProjItem
  
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.z_scan_read.vi_FPGACompileCopy00000001.VI
  194
  Reading memory "memory Node method.
  
  
  ProjItem
  
  
  
  

  
  -61106
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  
  
  
  2
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2803
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  3
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2816
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  
  

  
  -61106
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  
  
  
  2
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2803
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  3
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2816
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  
  

  
  -61106
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  
  
  
  2
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2803
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  3
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2816
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  
  

  
  -61106
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI
  
  
  
  2
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2803
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  3
  1
  
  C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI. Munge.main.vi_FPGACompileCopy00000001.VI
  2816
  Subvi: ' NEITHER. Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.VI'
  
  
  
  
  

  We could solve the problem. It was actually caused by the fact that we had set some subVIs to not reentrant. Their semifinal implementation (with the option to clone preallocate) solved the problem.

• Internal software error error-224606 in MIO

  Hello

  I get this error-224606: "internal software error has occurred in the MIO software. Please contact National Instruments. »

  It happens when I try to use the DAQmx controls Task.vi to abandon a task that awaits a digital triggering of an analog acquisition that has no time-out.

  I'm using LabVIEW 2010 sp 1.  My version of DAQmx is 9.2.3.  The camera I use is a DAQPad-6016

  When I was running this software on a USB-6251, I had no such problem.

  All solutions?  Thank you

  Hi pgaastra,

  Hmm, the error you see certainly seems buggy and should be the subject of an investigation.  However, I'm not sure about the validity of the abandonment of a task in the middle to access the DAQmx Read.  There is a better way to achieve your final goal.

  The easiest way is to simply ask the number of samples available.  You would then only call DAQmx Read after there is a number not null samples available.  See the code attached below.

  Best regards

• FPGA internal software error

  Hello

  I'm under LV 2010 SP1, I don't know what version of the FPGA module I have, but I think it has been upgraded during the SP1 update.  The error is less.  It refers to two of the four globals, I use communicate a FPGA timed to a non-timed loop loop.

  My code has compiled since the upgrade, but not since the addition of the globals...

  I'll appreciate any help on this.

  Roger

  An internal software error occurred. Please contact National Instruments technical support on ni.com/support with the following information: nirviUIDToObject.vireference object get error for UID. All the analyzed text:
  -61103 1NI. Munge.S3 Global.vi_FPGACompileCopy00000001.vi21C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi4624Global Variable: ' NEITHER. Munge.S3 Global.vi_FPGACompileCopy00000001.vi'31C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11890Global Variable: ' NEITHER. Munge.S3 Global.vi_FPGACompileCopy00000001.vi'
  -61103 1NI. Munge.S2 Global.vi_FPGACompileCopy00000001.vi21C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11881Global Variable: ' NEITHER. Munge.S2 Global.vi_FPGACompileCopy00000001.vi'31C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11878Global Variable: ' NEITHER. Munge.S2 Global.vi_FPGACompileCopy00000001.vi'
  -61103 1NI. Changed Munge.AO Global.vi_FPGACompileCopy00000001.vi21C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11906Global Variable: ' NEITHER. Changed Global.vi_FPGACompileCopy00000001.vi Munge.AO'31C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi4622Global Variable: ' NEITHER. Changed Global.vi_FPGACompileCopy00000001.vi Munge.AO'41C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11905Global Variable: ' NEITHER. Changed Global.vi_FPGACompileCopy00000001.vi Munge.AO'
  -61103 1NI. Munge.S3 Global.vi_FPGACompileCopy00000001.vi21C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi4624Global Variable: ' NEITHER. Munge.S3 Global.vi_FPGACompileCopy00000001.vi'31C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11890Global Variable: ' NEITHER. Munge.S3 Global.vi_FPGACompileCopy00000001.vi'
  -61103 1NI. Munge.S2 Global.vi_FPGACompileCopy00000001.vi21C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11881Global Variable: ' NEITHER. Munge.S2 Global.vi_FPGACompileCopy00000001.vi'31C:\NIFPGA\compilation\CardiaLen2_FPGATarget_CardiaLen2IO(FPG_86098CD2\MungedForFPGA\NI. Munge.CardiaLen2 IO (FPGA).vi_FPGACompileCopy00000001.vi11878Global Variable: ' NEITHER. Munge.S2 Global.vi_FPGACompileCopy00000001.vi'
  -61103 1NI. Changed Munge.AO Global.vi_FPGACompileCopy00000001.vi21

  Snip...

  Unfortunately, even if you can guarantee that the written word never happen at the same time if you write only once per carton, LabVIEW FPGA currently only has not the ability to position the system globals arbitratio for multiple entries on the diagram can cause this error.  What I would say is that you write the overall each iteration of the loop outside the structure of the case and that he wire simply the value on a tunnel on the structure of the case.  This will allow you always change the value each time through and will eliminate the error of code generation.

  If you want to send your comments about this particular use case of LabVIEW FPGA R & D, I would recommend that you post your idea in the Exchange of ideas of LabVIEW FPGA.

• Internal software error PrE11 burn to DVD

  Reference Dell Quad processor C:250GHD (pre here) D: 600GHD w / free 400 G (project here).  Converted from 60 movies of 13 minutes (avg) Reg 8 & 8 Supreme via projector, movie converter, Pyro has / V Linc, in computer in an AVI file.  Now burn to DVD with menu.  With the help of 5 files at a time. always less than 1 h, with main Start Menu & Stop markers on each clip file.  Do not spend time editing, use only the Smart Fix on all files.

  Some burn very well, but some give me the following error after that 99 percent complete on burn progress bar:

  "Software internal error: \Vobulator\Block Planner\Block Planner.cpp, line 215.

  There, it will stay frozen until I have the stop, restart and sometimes I restart and it completes the burning process, and sometimes he repeats the error.  It takes about 2-3 hours to find out.

  Can you tell me what it is?  Maybe I can avoid something.

  The error of Vobulator told me that things are bad, just at the end (as your % indicates), and it has to do with the progrma is not able to create the necessary video DVD structure.

  First thing I'd do, look to see if you have to stop at the end of the timeline marker. If so, remove that and test again.

  Good luck

  Hunt

• Cannot export DVDs even - internal software error

  This is the error code:

  internal software of the volumes: error, versions, mango, xcode projects/authorcore /... /... /Sonic/DVDCreator/FormatLib/Vobulator/TitlePlanner/CGOPGrouper.c pp, line 410

  Tried to export disk image but no luck either

  Thanks Stan,

  OK, I fixed it by starting a new complete project and re do the project. Then he worked... weird. I did the exact same thing project too:

  Intro / first video game created with a menu > in static menu with a Play All and 3 separate chapter links. (Not very complicated so it was easy to match exactly)

  Just for the reference of the foregoing response of Stan: I had 3 videos on my calendar, I was Admin, I had gaps in my timeline in Prem (which won't matter in any way, as I wasn't using dynamic links) and not substitutions. So I can't tell any of them were the factor affecting. I think it's just "one of those bugs.

  Thanks stan anyway, appreciate your reply.

• Unrecoverable internal error: 'fpsane.cpp', line 280 or 281

  Hi all

  I have a problem that convert screw of LV2010 at LV86.

  I use LV2010 to save the screws that the previous version LV86, then use LV86 to open the screws that have been save as version LV86.

  He always come out this error: unrecoverable internal error: 'fpsane.cpp', line 280 or unrecoverable internal error: 'fpsane.cpp', line 281

  Can someone help me?

  Thank you in advance!

  Hi, thanks.

  I found a root failed.

  RefNum LV2010 image control is NOT compatible with the LV86.

• Unrecoverable internal error: 'ThEvent.cpp', line 190

  HiI have a project in Labview 8.5. The project is made of: Statechart module and vision. The project contains hundreds of vi. When I run the project I get the common error: unrecoverable internal error: 'ThEvent.cpp', line 190. When I try to study the problem using probes and break points, the problem does not appear. When the error Labview does not record debug information.

  Concerning

  Gabi

  Hello

  I found the problem in the camera driver that I use. I change the way I work with the camera and it fix the problem.

  Regrads

  Gabi