# Updating a OpenClip with a publish **URL:** \ **Category:** Flame Questions\ **Tags:** openclip\ **Created:** [August 3, 2023, 10:03pm UTC](https://forum.logik.tv/t/updating-a-openclip-with-a-publish/8916 "2023-08-03T22:03:03Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![cnoellert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/cnoellert/32/559_2.png) [@cnoellert](https://forum.logik.tv/u/cnoellert)\ **Post date:** [August 4, 2023, 5:16am UTC](https://forum.logik.tv/t/updating-a-openclip-with-a-publish/8916/4 "2023-08-04T05:16:30Z")
> [@finnjaeger](#): > > also whatbwiuld be nifty is to have both patternbrowsed versions and regular openclips combined - imagine having a something named nuke\_version and a batch\_version in case you are doing both flame and nuke work on the same shot (or maya or whatever). I know this works right now but i cant have all my nuke versions appear by patternbrowsing, its either or, right? …and you can mux openclips with different shit. You can force it in batch so that means you can force it with some scripting. > [@Publishing / unmanaged framestore workflow AKA how to make smaller archives for those that don't archive good](https://forum.logik.tv/t/publishing-unmanaged-framestore-workflow-aka-how-to-make-smaller-archives-for-those-that-dont-archive-good/5040/34): > > Let’s give this is a try. The aim of this approach is to mux a diverse group of element types into a single openClip with the ability to dynamically view and load the metadata associated with those diverse types. This technique relies on establishing an id range for element types that gets directly mapped to the version number alongside a plain text version prefix. We’ll start by setting up a few ground rules. First version ranges: Comp 1-99 Precomp 100-199 Roto 200-299 Denoise 300-399 W… --- _[View the full topic](https://forum.logik.tv/t/updating-a-openclip-with-a-publish/8916)._