Numbering system for regions

Paul Fierlinger wrote on 8/18/2016, 5:14 PM
The automatic numbering of regions (command "R") ends at 99 after which no numbers appear anymore. This looks like there's nothing I can do about it if I want to even manually keep the count going. But just in case I'm missing something, I have to ask: ... or is there? Giving a name to the right of these tags is not viable for me; I just need to see a number where all the other ones appear.

Comments

Former user wrote on 8/18/2016, 6:04 PM
Instead of naming them, could you just give them a number as the name (100, 101, etc)
OldSmoke wrote on 8/18/2016, 6:30 PM
Vegasaur comes to mind. I can renumber markers and regions. How about TimelineTools?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

jetdv wrote on 8/18/2016, 6:47 PM
They are all continued to be numbered but the display of the number stops at 99. That's just how Sony decided to do it. But it's much higher now - it used to stop at 9.
videoITguy wrote on 8/18/2016, 7:14 PM
Instead of the silly number scheme of VegasPro or even an arbitrary name - use the
timecode of the timeline or timecode embedded in the clip/event to create a region name.

You can use a variety of arbitrary styles - perhaps the start mark timecode, or a combo name of begin and end timecode abbreviated - It is a good habit to create a well documented project. Using some built in functionality of the Timeline Tools notes tool can help you do this and more.
OldSmoke wrote on 8/18/2016, 7:17 PM
Sorry to say but even Vegasaur cant go beyond 99. It can name it higher but the white numbers end at 99. I also cant see how to fit 3 digits and more into the orange marker flag, only option is to go alpha numeric.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Grazie wrote on 8/18/2016, 11:54 PM
How about this:

Using a Spreadsheet Fill Series Numbers > Copy > Open Edit Details View > Paste

Any good for you?

G
wwaag wrote on 8/19/2016, 12:07 AM
@Grazie

+1 Very easy. Done this many times when events or regions exceed 100. Just bring up edit details and paste into Names making sure that the number of items pasted is the same as the number of regions or events.

Hopefully, in the next version, the little marker and region icons will be expanded to 3 digits so this type of workaround becomes unnecessary.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Grazie wrote on 8/19/2016, 4:49 AM
"Hopefully, in the next version, the little marker and region icons will be expanded to 3 digits so this type of workaround becomes unnecessary."

Yeah, Waggle, don't hold your breath too long.

I'm interested(?) to see/note just how fundamental the Vegas-Custodians will have been given the permissions and resources to make the requisite code changes needed not only for this improvement but all the others. If they do, then the Future is rosy.

G
JohnnyRoy wrote on 8/19/2016, 5:59 AM
It's probably also important to point out that Regions and Markers share the same numbering system. So if you drop Marker 1 and Marker 2 and add a Region, it will be Region 3. No way around this either. So if you drop markers while creating regions the numbering will be shared and not continuous.

~jr
Paul Fierlinger wrote on 8/19/2016, 8:33 AM
I had no idea this thread would have generated so much interest. Thank you all and I must try some of these suggestions, though something tells me that the workarounds might not be worth the trouble, which in turn uncovers that this is not too serious an issue for me and I can just as well live with no numbered tags.

For me it would be good enough if the fix would mean just having the tag count rotate back to 1 each time I hit 99.

To make that solution near perfect would be to have the ability to change the color of any new set of tags.

Absolute perfection would be to employ a three figure count and I would think this shouldn't take up all that much extra space to make it impractical.

@~jr: I find that quirkiness quite annoying as well and hopefully bringing this up just might generate some improvements in the future.
Grazie wrote on 8/19/2016, 9:01 AM
I've been coming here for 14 years. I've seen, had ideas and wishes bud, blossom, wither and die. Now and again there's sometimes just enough talented individuals to make a difference and either it gets absorbed into the code or some other solution is made real. This one? It will wither and blow away.

G
Paul Fierlinger wrote on 8/20/2016, 9:00 AM
On the other hand, I can't blame the developers. There must be so many more serious items on a long To Do list and even something as simple as this takes lots of time (except maybe make the numbers cycle instead of stop.) :)
PeterWright wrote on 8/23/2016, 10:10 PM

I've long been asking for the ability to choose colour for Markers - there are so many things to use markers for; being able to colour code for their function would be great.