Bryce Hoover

My feedback

  1. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Preference & Settings  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Bryce Hoover commented  · 

    Looking at the WorkspaceConfig.xml file before I edit the workspaces and afterwards, then re-examining that file after a software reboot, I've noticed the following.

    Editing the workspaces, deleting the default ones so that the only workspaces available are my 4 customs, the WorkspaceConfig.xml file reports NO BuiltIns (default workspaces).

    <prop.pair>
    <key>BuiltIns</key>
    <array>
    <array.type><ustring/></array.type>
    </array>
    </prop.pair>
    ---------------------------------------------
    <prop.pair>
    <key>UserNames</key>
    <array>
    <array.type><ustring/></array.type>
    <ustring>Audio_BH</ustring>
    <ustring>Color_BIG</ustring>
    <ustring>EFX_BH</ustring>
    <ustring>Edit_BH</ustring>
    <ustring>Audio_BH</ustring>
    <ustring>Color_BIG</ustring>
    <ustring>EFX_BH</ustring>
    <ustring>Edit_BH</ustring>
    </array>
    </prop.pair>

    Upon software reboot, the BuiltIns (default workspaces) are back and my customs do not appear in the WorkspaceConfig.mxl.

    <prop.pair>
    <key>BuiltInKeys</key>
    <array>
    <array.type><string/></array.type>
    <string>$$$/Premiere/FrontEnd/Learning=Learning</string>
    <string>$$$/Premiere/FrontEnd/AllPanels=All Panels</string>
    <string>$$$/Premiere/FrontEnd/Assembly=Assembly</string>
    <string>$$$/Premiere/FrontEnd/Editing=Editing</string>
    <string>$$$/Premiere/FrontEnd/Color=Color</string>
    <string>$$$/Premiere/FrontEnd/Effects=Effects</string>
    <string>$$$/Premiere/FrontEnd/Audio=Audio</string>
    <string>$$$/Premiere/FrontEnd/Metalogging=Metalogging</string>
    <string>$$$/Premiere/FrontEnd/Graphics=Graphics</string>
    <string>$$$/Premiere/FrontEnd/Libraries=Libraries</string>
    </array>
    </prop.pair>

    I then moved all the default workspaces to “Do Not Show” and placed my custom workspaces into the bar.
    I closed the open project, software went to home screen, I then chose the same project to reopen.
    Premiere took 8-9 minutes to reopen that project that I had just closed.
    During this time, the WorkspaceConfig.xml file was changed and my custom workspaces remained, and the defaults remained in the Do Not Show.

    <key>BuiltInKeys</key>
    <array>
    <array.type><string/></array.type>
    <string>$$$/Premiere/FrontEnd/Learning=Learning</string>
    <string>$$$/Premiere/FrontEnd/AllPanels=All Panels</string>
    <string>$$$/Premiere/FrontEnd/Assembly=Assembly</string>
    <string>$$$/Premiere/FrontEnd/Editing=Editing</string>
    <string>$$$/Premiere/FrontEnd/Color=Color</string>
    <string>$$$/Premiere/FrontEnd/Effects=Effects</string>
    <string>$$$/Premiere/FrontEnd/Audio=Audio</string>
    <string>$$$/Premiere/FrontEnd/Metalogging=Metalogging</string>
    <string>$$$/Premiere/FrontEnd/Graphics=Graphics</string>
    <string>$$$/Premiere/FrontEnd/Libraries=Libraries</string>
    </array>
    </prop.pair>

    <prop.pair>
    <key>UserNames</key>
    <array>
    <array.type><ustring/></array.type>
    <ustring>Audio_BH</ustring>
    <ustring>Color_BIG</ustring>
    <ustring>EFX_BH</ustring>
    <ustring>Edit_BH</ustring>
    <ustring>Audio_BH</ustring>
    <ustring>Color_BIG</ustring>
    <ustring>EFX_BH</ustring>
    <ustring>Edit_BH</ustring>
    </array>
    </prop.pair>

    I closed this project, software went to the home screen, I chose the same project AGAIN to reopen, and it took less than :30 to open, but longer than it should, much longer than it did before we upgraded to CC2019 13.1.2 (build 9).

    I can’t reboot the software without having to reconfigure workspaces, then my project load times increase dramatically (4-10 minutes after reconfiguration, before reconfiguration, :30 or less to open)

    Bryce Hoover shared this idea  · 
  2. 113 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    45 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Bryce Hoover commented  · 

    still broken on 13.1.2 (build 9) on PC.

    Bryce Hoover supported this idea  · 
  3. 428 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    43 comments  ·  Premiere Pro » Import  ·  Flag idea as inappropriate…  ·  Admin →
    Bryce Hoover supported this idea  · 
  4. 548 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    48 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    Bryce Hoover supported this idea  · 
  5. 6 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Bryce Hoover commented  · 

    I only use 4 custom workspaces.
    I've deleted the defaults, or moved them to overflow.
    I have a custom workspace for Edit, EFX, Audio, Color.
    I've named them Edit_BH, EFX_BH, Audio_BH, Color_BH.
    How can I figure out what WorkSpace# (UserWorkspace#.xml) = Edit_BH when I'm mapping it to my keyboard?

    Bryce Hoover supported this idea  · 
  6. 7 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Bryce Hoover shared this idea  · 

Feedback and Knowledge Base