Sequence file version conflicts - TS_EngineNewExecution

Hej NI Community,
I have programmed an stand alone application, which can execute sequence files. The CVI application is programmed with CVI 7.0 and Teststand API 4.0. You can select a sequence file and run the application without the SequenceFileEditor...
My sequence file is programmed under Teststand 4.1 and uses sequence file library functions, which are developed with Teststand 4.0 (stored in different sequence files).
I can run the sequence file under Teststand 4.1 (SequenceFileEditor) without any error messages. My own application cannot run the sequence file. The function TS_EngineNewExecution comes back with a error message:
Error code: -2147352567
CA automation error string: Ausnahmefehler aufgetreten.
Teststand API error information:
wCode: 0
sCode: -17329
source: TSAPI
description: Error loading step 'In-Circuit-Test' of sequence 'MainSequence' in file 'bscan_demo.seq'.
Error loading step 'Insert name of step into operator interface' of sequence 'Load and run ICT program' in file 'Test_Library.seq'.
Type 'NumericLimitTest' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the file with the type conflict in the Sequence Editor and resave it.
The sequence file 'C:\Program Files\Sequences\Utility_Library.seq' could not be loaded.
helpFile:
helpContext: 0
errorParamPos: -1
I can resave the sequence to avoid this message. My own application can execute the sequence file after resaving. The library is saved now in Teststand 4.1 format. But this is not my interest.
Can anyone tell me, why the sequence editor (4.1) don't show me any error? How must I program my own application to avoid this error message?
Thanks a lot.
Solved!
Go to Solution.

Hej,
I'm posting my tracefile. I think its easier to unterstand. Here are tracing with the error:
0.000s      Program started
0.000s      Tracing started
0.002s      Function LoadPanel finished with no errors
0.000s      Initialize Teststand Engine
0.892s      Function -->   TS_NewEngine finished with no errors
0.000s      Function -->   TS_EngineRegisterUIMessageCallback finished with no errors
0.001s      Function -->   TS_EngineSetProperty finished with no errors
0.000s      Function InitEngine finished with no errors
0.000s      Start login process
0.000s      Function -->   TS_EngineNewPropertyObject finished with no errors
0.000s      Function -->   TS_PropertySetValBoolean finished with no errors
0.000s      Function -->   TS_PropertySetValBoolean finished with no errors
0.030s      Function -->   TS_EngineCallFrontEndCallback finished with no errors
0.000s      Function -->   TS_ExecutionGetProperty finished with no errors
0.000s      Function CallLoginLogoutCallback finished with no errors
0.000s      Show panel behind logon panel
0.017s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.003s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.011s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.224s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.247s      Waiting for Login
0.500s      Waiting for Login
0.086s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_ExecutionGetProperty finished with no errors
0.005s      Logon process done
0.000s      Check user
0.000s      Function -->   TS_EngineGetCurrentUser finished with no errors
0.000s      User can run any sequence
0.000s      Function CheckUserPrivilege finished with no errors
0.000s      Open sequence
0.000s      Show file select popup window
1.297s      Function -->   TS_EngineGetSeqFile finished with no errors
0.000s      Sequence file path is:
0.000s      c:\Program Files\Spectral Electronic\SW-ITS\Projects\BScan_Demo\bscan_demo.seq
0.000s      Function OpenSequence finished with no errors
0.000s      Check sequence
0.000s      Function -->   TS_SeqFileSequenceNameExists finished with no errors
0.000s      Function -->   TS_SeqFileSequenceNameExists finished with no errors
0.000s      Function -->   TS_SeqFileSequenceNameExists finished with no errors
0.000s      Function -->   TS_SeqFileSequenceNameExists finished with no errors
0.000s      Function -->   TS_SeqFileSequenceNameExists finished with no errors
0.000s      Function -->   TS_SeqFileSequenceNameExists finished with no errors
0.000s      All sequences found, iStartSequence automatically true
0.000s      Function CheckSequence finished with no errors
0.000s      Start execution of loaded sequecence
0.248s      Function -->   TS_SeqFileGetModelSeqFile finished with no errors
3.123s      An error has occurred in function: -->   TS_EngineNewExecution useProcessModel
Error code: -2147352567
CA automation error string: Ausnahmefehler aufgetreten.
Teststand API error information:
wCode: 0
sCode: -17329
source: TSAPI
description: Error loading step 'In-Circuit-Test' of sequence 'MainSequence' in file 'bscan_demo.seq'.
Error loading step 'Insert name of step into operator interface' of sequence 'Load and run ICT program' in file 'Test_Library.seq'.
Type 'NumericLimitTest' is invalid because it conflicts with the existing type of that name. To avoid this error message, you should open the file with the type conflict in the Sequence Editor and resave it.
The sequence file 'C:\Program Files\Spectral Electronic\SW-ITS\Sequences\Utility_Library.seq' could not be loaded.
helpFile:
helpContext: 0
errorParamPos: -1
0.015s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   CA_CreateObjHandleFromIDispatch finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
0.000s      Function -->   TS_UIMessageGetProperty finished with no errors
4.303s      An error has occurred in function: ExecuteSequence -> Test UUTs
Error code: -1
Error message: No error message
0.628s      Start free all resources
1.060s      Free all resources done
0.000s      Tracing stopped
0.000s      Programm ended

Similar Messages

  • How to display sequence file version in report?

    We would like to add the sequence file version number
    (Edit>>Sequence File Properties...) to our reports and record it
    in the test result database.  How do you access this property from
    a step in the sequence? 

    OR use RunState.SequenceFile.Data.Version.
    For the Report Header:
    In a ModifyReportHeader callback, add a statement step that has this expression:
    Parameters.ReportHeader += RunState.SequenceFile.Data.Version
    This will append the SequenceFile Version to the header string. You will probably want to play with placement and may decide to insert more than just the version.
    Also, note that the ModifyReportHeader callback is only called when a Sequence is used to generate the report body. See the bottom of the Content tab of the Report Options Dialog (Configure>>Report Options) for this setting.
    For Database Logging:
    If you haven’t done this before, you will need to customize the schema and the database to include this additional “result”. I recommend adding a column to the UUT_RESULT table for this sort of information. If you have taken the TestStand I: Introduction course, this process is covered in Lesson 11. Otherwise, there is background information in the TestStand Help and Chapter 6 of the TestStand Reference Manual. The key will be found in Configure>>Database Options.
    Regards,
    Eric

  • How I can log Sequence File version number to database?

    Hi,
    As in the subject.
    How I can log Sequence File version number to database?
    There is nothing like that under Logging object.

    Do you need it in a separate field in the databse?
    One option is to just add it as an additional result in a step in your sequence file. 
    RunState.SequenceFile.AsPropertyObjectFile.Version
    Hope this helps,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • Sequence file Version number. How to prevent the automatic resetting build version number whilst auto-incrementing revision number?

    Hi,
    I've got my environment set this way that each save of the sequence file increase the revision part of version number. However, during that increase the build counter is reset to 0. How to prevent it?
    TS 4.2

    Mimi,
    It is pretty common practice in software revisioning to reset a minor number to 0 when a major moves up 1.  There are many different schemes out there.  If you google or bing software versioning schemes you'll see what I'm talking about.
    So looking at it from left to right:  Major.Minor.Revision.Build = 0.0.0.1 
    if you change the Revision it would be expected that anything to the right (in this case Build) would reset to 0.  0.0.1.0!
    Let's say your version is 8.34.56.23.  It would make sense that if you were to change the Major number (which means a Major release) to 9 then your version would go to: 9.0.0.0. 
    A version number is just a unique way to tell someone which specific software you are using so it really doesn't matter that it resets to 0.  Although it makes sense because if you kept your build number sequential and didn't reset it then it would get outrageously larger which would be more annoying than anything. 
    Again this is common accepted practice in industry.
    Good Luck,
    jigg
    CTA, CLA
    teststandhelp.com
    ~Will work for kudos and/or BBQ~

  • How do I make Step Types in the Type palette be "master" versions which all sequence files on a particular should use? (since this only seems to "half work")

    The situation I would like is to have a library of step types which sequence developers can use. Therefore if new step types need to be added, or existing ones modified - all that needs to be done is to roll out a new MyTypes.ini (for example), and the code modules/substeps.
    Scenarios:
    If I create types in MyTypes.ini (make sure "Attach to this file" is checked, so they get saved here). I can then create a sequence file using these step types. No problem so far.
    I can open the type palette, modify the step properties, and save. When I go back to my sequence file an asterisk appears (saying it needs to be saved, even if I have opened it from scratch). The properties have been updated to reflect what is in the Type Palette. Still no problem (Type versions are the same in the sequence file and type palette).
    This is where the problem appears:
    If I change a step type (in the Type Palette) from using a code module to using a Post-Step substep instead (changing the module adaptor to "None") - any instances do NOT update when you open sequence files. (The same happens vice versa also).
    Please note that the "Type version" listed in the sequence file DOES match that listed in the Type Palette - the properties are the same but the manner in which the code modules are called is DIFFERENT! This then can lead to to runtime errors if the old code module has been deleted for example.
    The only way around this is to open EVERY sequence file that contains an instance of the step type, and make sure that you have "Apply changes to all loaded instances of this type" checked in the step type properties dialog. This is is not a good solution since files could be missed, and is very time consuming if you have hundreds of sequence files!
    What I need is that the Type Palette on any particular station contains the MASTER copies of each type. These are loaded whenever a sequence file is loaded and NOT retreived from the sequence file. As discussed above this seems to work when you modify properties - but doesnt work fine if you change the way in which code modules are called.
    Am I doing something wrong or is this a limitation?

    I had a system recently containing seven sequence files, approx 20 subsequences in each, and around 10-20 steps in each sub-sequence. Every step (except for the NI non-code module types) was an instance of a step type.
    Each one of these steps had an Edit sub-step and a code module called through the code module adapter.
    In order to make these into "wrapped up" step types it was decided to move the code module to a Post-Step substep (as also done in the NI-IVI step types) - so that developers cannot fiddle with the code prototype or module.
    In order to do this I had to open all 7 of the sequence files, make the changes and then ensure that "Apply changes in this dialog to a loaded instances" was checked. This seems to sort of work, but some steps started causing Error 17502 (System Error) when you configure them (call the Edit substep). Over the course of the past few months I have had to effectively check every instance of a type to see if it works (deleting the step and replacing it when it doesnt). Other strange things happened like some of the step type instances now have the "None" (adapter) icon associated with them - but both still work.
    The idea of creating a type-def of a step type is a good one, but frustrating that it doesnt seem to fully work. Why should the sequence file also store a version of the step-type - which is what is effectively causing this problem - why not make it so that if you dont have the step types installed in the type palette - TOUGH! Message Edited by RichM on 03-15-2005 06:55 AM

  • Type conflict where type not found in sequence file

     Hi,
    from a central master sequence, I am starting several sequences from other sequence files in new executions. These sequences have individual types as input and output parameters, the types being defined within these sequence files.
    The master sequence only knows the names (as strings) of these types and when I do a "Find/Replace in files" in the master sequence file looking for those types, they are not found.
    However when I change one of the types in its respective sequence file while I have the master sequence file open, the master sequence file is shown with an asterisk and later I get a type conflict if the settings is to "Never allow automatic type conflict resolution". This is fairly awkward since the master sequence file is supposed to be password protected and no-one should have to touch it in a project.
    What can cause this behavior?
    Apparently, usage of these types spread around through all sequence files although they do not have any need for using the types from other files.
    Is it possible that it makes a difference whether the type was first defined in a type palette file or directly in a sequence file?
    Best regards,
    Peter

    Peter,
    using the data type as parameter in another sequence file will include the type definition in the calling sequence file, therefore changing it. I am not sure why the Find/Replace tool does not display it, but it shows up in the types palette of the file.
    When the data type is changed, it will result in a type conflict....
    So when trying to reproduce the issue with TS 2010, i receive an dialog for resolving type conflict when setting to never do an automatic resolve...
    Nevertheless, the calling sequence must be updated for sure if a used type is changed.
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • File Transport: Version conflict.

    Hi,
    I have a doubt on a particular scenario while transporting object from QA to PRD using File transport.
    I have exported a tpz file say 1.tpz from QA with say the following objects
    Obj_1(ver 1.0)
    Obj_2(ver 1.0)
    Obj_3(ver 1.0)
    Now before this 1.tpz is imported in PRD few more changes happend to Obj_3 and I exported again a file say 2.tpz
    Now this 2.tpz has only Obj_3(ver 2.0)
    Now the basis has by mistake Imported this 2.tpz file before importing the 1.tpz file. SO in my PRD the object Obj_3 is existing  with a advance version i.e 2.0
    Now my doubt is can we Import 1.tpz now in PRD and then again import 2.tpz ?
    I am having a feeling that we will definately get in version conflict. Even if I ignore the warning during transport and go ahead with this procedure of importing 1.tpz and then 2.tpz again, will it impact my scenarios.
    I am lookign for a quick suggestions.
    Regards,
    Rahul.

    Hi Rahul,
    If you import V1 file first & later V2, it will not impact on your scenarion & you wil be able to see latest object in PRD.
    But V2 is already imported so import of V1 may not be successful.
    You may generate a new export if possible & transport this. It should include all object with their lastest version.
    Regards
    Sushil

  • Getting the Test Stand version number of an old sequence file

    A customer wants a small change to a previous deployment.
    They have returned the original sequence file to me but the deployment is about two years old.
    Is there anyway that I can get the TestStand Version number from the old sequence file so that I will know which version to save it in.
    I am currently using TestStand 4.2.1.83. 
    Thanks,
    Sean
    Solved!
    Go to Solution.

    As Sean stated back in 2010, you can also read the version number in clear text. You can read some parts of the file in a text editor, the version number is one of those....
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • How do I read the Visual Source Safe version of a sequence file?

    I can read the TestStand Version using RunState.SequenceFile.Data.Version. I would like to sink the version numbers in VSS and TestStand up. How do I obtain the version number maintained by VSS.
    Thanks, Jeff

    One way to get the VSS version number is through the command line using the History command. See VSS help for more info. I think it would be possible to create an EXE step in TestStand that would execute the VSS command line and pipe the output to a file, where it could be read with some custom code. Of course it would be nice if there was a built-in TS step to do this. Here is an example of the VSS history command usage and it's output.
    ---- Example -----
    C:\DevStudio\Vss\win32>ss history $/tekcal-ni/projects/80e0x/80e0x.seq -#2
    History of $/tekcal-ni/projects/80e0x/80E0X.seq ...
    Label: "Beta1"
    User: Marki Date: 4/29/02 Time: 8:45a
    Labeled
    Label comment: Release to Customer Service.
    ***************** Version
    14 *****************
    User: Marki Date: 4/26/02 Time: 3:00p
    Checked in $/TekCal-NI/Projects/80E0X
    Comment: Changed delay time for DC Accuracy/Linearity from 0 to 100 mS.
    ---- End of Example -----
    If you just want the last version, use the "-#1" option instead of -#2 as in this example. VSS uses labels or whole number version numbers, so you would need to relate this to your TS version number, perhaps with a sequence file global variable.

  • Can I open the (.squ) sequence files using NI test stand 4.0 version?

    I have the sequence files created using ATETool Kit test Executive. But I have NI 4.0 test stand. I want to open the sequence files using NI 4.0 test stand. Can i do that?

    Hi,
    I am not familiar with ATETool kit Test Executive, but I doubt NI TestStand will open this. As you have both, have you tried it?
    TestStand does have a conversion tool for converting NI TestExecutive sequence files into TestStand sequence files.
    Maybe you could write a conversion tool to make the conversion for you if you have many ATETool kit Test Executive files.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Reload sequence file when changes on disk

    Hi,
    I wrote a custom user interface based on the TestStand (TS) Operator Interface. When I run a sequence file on it and I edit it in the TS editor and I restart an execution, it seems to keep loading the first one when I launch the execution. The only way I can do this is by restarting the GUI.
    I read a lot and tried many things and I can’t figure out what do I need to do to have the sequence file reload from disk on the 2nd execution after changes has been made.
    I tried many thing and it seems to work when I release the seq file 2 times (!). But, as expected, the 2nd time it get released, I get an error that the file was unloaded from the TestStand Engine. And the weird thing is that I don’t get the error when I run the 1st time or I don’t make changes to the seq file.
    Do you see anything wrong? Or have another suggestion how I could achieve that?
    Can I see which seq files are in the internal cache? That could be useful to debug.
    Thank you.
    A code snippet in C# is in attachement.
    Attachments:
    C#-code.rtf ‏2 KB

    A few more ideas:
    1) Are you perhaps using this file path with an ApplicationMgr or SequenceFileViewMgr API? You need to make sure that this file is not open by the ApplicationMgr or assigned to a sequencefileviewmgr as well. The applicationmgr or sequencefileviewmgr likely have a strong reference to the sequence file if you have assigned it or opened it with one of their APIs. You might want to try switching entirely to the applicationmgr APIs instead of using the engine APIs as that's probably less likely to lead to conflicts between the two.You could try ApplicationMgr.OpenSequenceFile() and ApplicationMgr.CloseSequenceFile().
    2) Have you tried this with a simple, empty sequence file and simple default Sequential process model to verify that it's not related to anything in the sequence file you are running or any code elsewhere in your application? It's possible for code in the sequence or process model itself to be calling GetSequenceFile or GetSequenceFileEx.
    3) Have you tried adding a delay between WaitForEndEx() and ReleaseSequenceFileEx()? This is not that likely to be the cause, but perhaps there is additional code required to execute in the execution thread after WaitForEndEx returns before the sequence file can be unloaded. If you add a small delay (i.e. Thread.Sleep(1000) between those lines of code it might work. This would not explain why the file couldn't be reloaded when you use GetSequenceFileEx with the UpdateFromDisk flag though so probably is not the problem.
    I tried to reproduce this problem in the sequence editor by running an
    execution with a sequence file, closing the sequence file, overwriting
    it with a different sequence file and reopening it and I was unable to
    reproduce the problem. I got the new file opened as expected. This is
    the equivalent situation since there is a completed execution still
    open. The sequence editor does not use the Unload flag on
    ReleaseSequenceFileEx, but it does use the UpdateFromDisk flag on
    GetSequenceFileEx() and it seems to work, correctly loading the new
    version of the file in this case. So there must still be something different in your case. I suspect that it's not the execution that has the extra reference in your case, but something else, perhaps the ApplicationMgr or SequenceFileViewmgr.
    Also, as a side issue, if you are writing a custom UI, I'd recommend using UIMessages to determine when an execution completes rather than WaitForEndEx(). Basically handle the ApplicationMgr.UIMessageEvent and look for UIMsg_EndExecution and check that the execution associated with the UIMessage is the one you care about. Using the UIMessage like this has a couple of advantages:
    1) It allows your UI to go back to executing in it's main message processing loop (Some things will not work correctly without this).
    2) It gives you the potential to track and handle running multiple executions in parallel. Just look for and track the multiple UIMessages that such executions generate.
    Please let us know if any of these ideas helps or if you are able to figure out the cause of the problem. If you are still unable to get it working and can't figure out the cause, please attach an example program and sequence files which reproduce the issue.
    Hope this helps,
    -Doug
    Message Edited by dug9000 on 03-02-2010 10:03 AM
    Message Edited by dug9000 on 03-02-2010 10:04 AM

  • Type List Order Numbers (typelisto​rdernum) change when opening a sequence file in Test Stand

    Could you please shed light on the reasons a sequence file changes upon opening in the Test Stand development environment?  
    Comparing the file before and after, I see that the typelistordernum changed on a few custom types that we defined for the program. . 
    To clarify the environment, I am using two work stations running the same version of Test Stand. The workstations are kept in sync using Sugar Sync. One would expect that a file saved on one workstation could be loaded on the other work station with no change.
    This also happens on files that we pull from version control (GIT). Once opened, they change, which presents a serious problem in avoiding version conflicts and keeping track of real changes. 
    Test Stand Version: 4.5.1

    ATE Coder wrote:
    In fact it turns out that conflict resolution is fairly hard to resolve.
    For instance, changing a type (add a comment) changes its time stamp. As a result, all sequence files referring to this type are now in conflict.
    On testing, Test Stand does not seem to flag these. So, they could be pushed into the repositories as is.
    Opening the sequence files on another machine (after pulling to code from repositories), Test Stand detects a conflict that in fact is no conflict at all. Now all these files need to be checked in and pushed up and then pulled down.  This increases the chances of code conflicts many folds and seems to be totally superfluous.
    Turning off automatic conflict resolution does not seem to resolve this issue.
    It would seem that for some reason (inertia?), NI pulled into Test Stand the same tight versioning it uses in LabVIEW. While in LabVIEW, where, in fact, one is editing compiled code, thins might add some value, Test Stand sequences are actually XML file -- source code, which call for a much more relaxed code versioning or none at all as making sure the code works as part of the debugging process and cannot be handled properly by 'versioning'. 
    I think you might not be using automatic conflict resolution the way it is intended.
    Are you using type palette files? If not, I highly recommend you do so. If you put the highest version of your types in a type palette file, use the default automatic conflict resolution settings, and distribute or deploy the type palette file to everywhere where the type is being used, you do not have to resave all of your sequence files everytime the type changes. Sequence files with older versions of the type will be automatically updated when they are loaded on machines that have the latest version in a type palette. This is what automatic conflict resolution does, it automatically/silently updates the types in the sequence files when they are loaded. No need to resave everything before hand. If you have trouble getting this working, let me know exactly what you are doing and what problems you are having and I will hopefully be able to suggest an alternative way of managing types that will not have those problems.
    Hope this helps,
    -Doug

  • How to edit 16bit TIFF image sequence file in FCP?

    Dear all,
    I have a number of 16 bit TIFF image sequence files (2048 x 1024 resolution) - some of them are RED footage, and others came directly from our f/x guy. We are going into a color correction session in a post house and we've been asked to provide a sequential 16 bit TIFF image sequence of the edited time line.
    I need to do a cross dissolve b/w most of the clips I have. I have created image sequence QT movie (reference files) from the TIFF images. Though they play fine in QT player, when I try importing into FCP, I am met with a "general error". I tried both dragging it into QT, as well as File --> Import.
    I am wondering what can I do to get these clips into FCP in order to apply the cross dissolve transitions I need. Is this a problem relating to the 16bit nature of the TIFF files?
    I tried exporting the TIFF image sequence standalone QT movie, and those imported fine. However, I have a feeling that the standalone movie conversion also decrease my bit depth from 16 to 8. (When I do my final TIFF output from FCP after dissolves / transitions had been applied, each TIFF file is now 8 MB instead of 12 MB, hence my suspicion that the bit depth is adjusted).
    Are there any settings I am missing, or does FCP simply don't support 16 bit image sequence reference file. As a test, I had also converted all my TIFF to jpg, and created jpeg image sequence reference file. These reference QT file can be successfully imported to FCP and I can edit them as if they are a clip.
    If FCP is not able to handle these files, what are my other options? After Effects?
    Any help is appreciated.
    Thank you.
    Michael
    <Edited by Moderator>

    As far as I know, both FCP and Color only support up to 10 bit color, which is 1024 levels for each color channel, more than enough for avoiding color banding.
    If you need 16 bit for sure, I believe AE will support 16 bit output. Another 16 bit application would be the extended version of Photoshop, which has some limited time line capability.

  • Is there a way to keep Deployment Utility from modifying sequence file paths?

    While the Deployment Utility appears to be a great tool, it does some things that I'd rather it didn't. One is that it modifies all paths in sequence that it is including from Absolute to Relative. While this is a nice feature for many reasons, it is a show-stopper for our uses. This is because as part of our distribution process, we also use a checksum routine to verify that the sequence files being run by the operators on the Test Stations we deploy to are running the correct (unmodified) version of the test software. By using Absolute paths, we can detect and prevent accidental editing/changing of the sequences or paths that we have deployed, but if we have to use relative paths that is something that we could work with also.
    So my questions are: 1. Can this path update 'feature' be disabled? and 2. If not, then will pre-setting all paths in a sequence cause the deployment utility to only copy the file and not update it (thus changing it's checksum)?
    I'm going to test the latter when I have time, and if there are any other suggestions that might be useful, I'm love to hear them.
    Thanks,
    -Jack 

    Rick,
    In my experimentation to see if using relative paths, I was able to prove that a sequence that uses them will not be updated - with one caveat; if the path that is referenced by the sequence is not itself in a sub-directory, i.e.; it's in a different branch of the relative directory structure with respect to the Target (such as the TestStand directory), then the sequence file is always updated and re-saved. An example is that we have a sequence in the Tools directory that calls a DLL in the FrontEnd directory of the Components\User path. This re-saving causes a checksum change and screws up our verification mechanism. 
    It is unfortunate that I cannot prevent the deployment utility from modifying sequence files - Since we control the entire Test environment, including the location that software gets installed to - Test Station custodians can't go installing the software in a different location, or worse, multiple locations, so we don't have the issue to worry about.
    Because of this 'better' method, we now have to re-evaluate how to control the installed version of the software, or use a different installer, such as CVI, which while it has been working for us, has it 's own issues that we're trying to get away from. I'm glad that I am finding out about this now before I've locked down the sequences so that I can probably move the features in the Tools to the Frontend Callback sequence. 
    It's almost always the case thought that one persons forced enhancement is another's 'feature' or worse 'bug'.
    Thanks for confirming the behavior on the Deployment utility for me.
    -Jack

  • How can I include multiple limits in the sequence file documentat​ion for custom step type?

    Hi,
    I have a custom Step Type that contains Measurements property under Results. Its type is Array of NI_LimitMeasurement.
    I would like to see the values in the sequence file documentation like NI_MultipleNumericLimitTest type.
    Is there any trick to do that?
    Thanks,
    Andras

    Hi Andras,
    I have made  a slight change to the sequencefile 'docgen_txt.seq'.
    In the Sequence 'Step Doc' is a section which handles MultipleNumericLimit step type. There is a precondition check on the step 'Add Multiple Numeric Limits' if the step is of type 'NI_MultipleNumericLimit'. As your step type is based on the MultipleNumeric Limit type, I have just removed this precondition and just relied on the existence of Parameters.Step.Result.Measurement. Equally you could add a new section in this sequence to handle your Custom Step Type which is only called when the precodition match your type name.
    Now when you run the DocGen tool it handles your custom step type.
    Find attached my modified sequencefile 'docgen_txt.seq'.
    Just copy the contents of '..\National Instruments\TestStand 3.5\Components\NI\Tools\DocGen' to the User folder. Then place the attached file in the User\Tools\DocGen overwritting the version that is in that folder.
    Then launch TestStand and try it out on your sequence file.
    If you are using the html version, then you will have to make the same change into Step Doc sequence of the docgen_html sequence file.
    Hope this helps
    Regards
    Ray Farmer
    Message Edited by Ray Farmer on 05-19-2007 05:28 PM
    Regards
    Ray Farmer
    Attachments:
    docgen_txt.seq ‏184 KB

Maybe you are looking for

  • How do I delete devices from my iCloud account

    I have several old devices that show up for account verification.  I can see them in my account details at settings in iCloud, but don't see a way to delete them.  Is there a way to delete those old devices?

  • Crystal Report Server 2008 - Schedule/Process/History Grayed Out on CMC

    Hi - I'm using Crystal Reports Server 2008 (11.5) and am unable to schedule reports - the schedule (as well as the Process and History) tabs are greyed out in the Central Management Console and don't appear at all in Infoview. In addition I can speci

  • Minimum order quantity ignored when past due

    SAP Business One 8.81 PL09 When running MRP for an item, the Minimum Order Quantity is ignored if an item is past due, meaning, the lead time makes it impossible to meet current requirements on time. From what I read, this appears to be by design in

  • Storage directory

    How can i change the storage directory of the applications and games I download. My internal memory is full and I want to change the storage directory and make it external storage. How can I do it in my phone lenovo A516? Solved! Go to Solution.

  • Disable Command Link (Button)

    From my backing Bean I would like to dynamically disable the buttons on my jsp form. How do you do it? I have tried as I would with fields but I get a failure.