5 Replies Latest reply on Feb 21, 2012 11:07 AM by Rallymax-forum

    Export param UI goes wrong when exporting sequence?




      I'm making an exporter plug-in using Premiere Pro SDK 5.5.

      I'm adding some parameters in exSelGenerateDefaultParams. These including some tabs, groups and params in each group.


      But when exporting in sequence, the UI messed up, all the tab and group names don't show,  excluding the audio and video tab (which name already defined in PrSDKExportParamSuite.h).

      Sorry guys edited: the params name do shows, but not the groups and tabs names.


      When I export the file (clicking the file and Ctrl+M), the groups & tabs names show nomally.


      Another note, I removed some of Premiere already defined commons param like video width(ADBEVideoWidth), height (ADBEVideoHeight), or audio channels (ADBEAudioNumChannels), sample rate (ADBEAudioRatePerSecond), pretty much everything except for ADBETopParamGroup, ADBEVideoTabGroup, and ADBEAudioTabGroup. Since I have no need for them in my plug-in.


      Is the removal of those param the cause of my problem? Or something else? I'll very appreciate if any one encountered the same problems or have knowledge about them would help me.



        • 1. Re: Export param UI goes wrong when exporting sequence?
          Rallymax-forum Level 3

          it would seem that you do need those Params to keep the gui engine happy.  so just set them to .hidden = kPrTrue;

          if its not that its because you have HasVideo and HasAudio == false. one has to be true to draw the tabs.

          also the example throws you off a bit - you have to create the heirachy in Gen'DefaultP() but populate their values inc strings in PostProcess'()

          one thing missing in the example is that you need to do a GetParam() on every element in PostProcess'() to get the last-session preset - otherwise it'll use the default values. this matters big time coz when you do an Export you need that PostProcess step to fill in the presets set by the user vs the defaults.

          • 2. Re: Export param UI goes wrong when exporting sequence?
            Dinhmc01539 Level 1

            Thanks for your answear, Rally


            The problem is, I've already done all the above.

            When I create a new sequence and export it, the gui is fine. But after exporting, if i export it again, all the tab and group name (except for audio and video tab) are gone. So I think there is some thing done to the sequence when the exporter works. If I switch the format to something (like mp3, flv or whatever), and switch back, the gui is fine again.

            It makes me mad for several days since.

            • 3. Re: Export param UI goes wrong when exporting sequence?
              Rallymax-forum Level 3

              I've noticed that if you open the same thing again (eg Ctrl-M on the same sequence or in AME right-click RESET STATUS) that the gui is cached and doesn't call PostProcessParams() again. if you're mistakingly setting up the tabs in there that would explain why you don't get your gui.

              Delete the epr file as outlined in the docs on caching to experiment. Note that the current settings are not saved to this epr file until AME is closed... so if you hit STOP in the debugger instead of closing the program your epr will not get updated and you'll see the same preset corruption over and over again.

              • 4. Re: Export param UI goes wrong when exporting sequence?
                Dinhmc01539 Level 1

                Thanks, Rally


                I set up all my tabs and groups and params in GenDefaultPam(), only the group and tabs name are wrong, and only for second export onward.

                Curently trying the caching, but as far as i increased the ParamVersion, nothing has changed.

                And I noticed some other thing: Even the params are displayed normally in second export, its value range is mesed up too. For example, if "MyAwesomeParam" has min value of 10 and max value of 20, at first export if I enter 0, it jumps to 10 because the entered value is smaller than the min value. But in second export, if I enter 0, it stays 0.

                It is getting more and more confusing really.