In VP10, when I sort by Type in the Vegas Explorer window, the files within each type are sorted by Name. However in VP12-16, the order within each type seems to be random, and that makes it very difficult to locate files.
Can anyone see any logic to the order? Seems like a bug to me.
I very seldom use Explorer tab, but I wanted to see what you are seeing, however I cannot see where you selected 'Type'. What am I missing?
Top of the 2nd column in my screenshot. There's a chance your columns will be ordered differently, or you've hidden that column.
Got it 'Detail View'. I get the same results and would agree, it seems strange they would not retain alpha list. At first glance I thought they were by last modified, but I see exceptions to that as well.
A bug? I don't get what you are saying. Has probably to do with the fact that is was 60 years ago I learned the english language.
I like it that I am able to place them in every order I want by 1 click and in the Project Medialist there are a lot more possibillities the make a certain order. Look how my VPro 16 is handling that in the Explorer:
Ideally one could sort first by column A then by column B and be able to determine the hierarchy of sorting. I know Windows explorer and the underlying Windows list controls don't work that way.
I don't have time to think about it, but here is what I see on Windows 7 with Vegas 10 and 13.
A bug? I don't get what you are saying. Has probably to do with the fact that is was 60 years ago I learned the english language.
I like it that I am able to place them in every order I want by 1 click and in the Project Medialist there are a lot more possibillities the make a certain order. Look how my VPro 16 is handling that in the Explorer:
Your video illustrates the problem perfectly. At 0:10, when you've clicked "Type", the 5 x JPG results should be sorted alpha-numerically by Name, and below them the 12 x MP4 results should be sorted alpha-numerically by Name. But they are not. That is how Windows Explorer and other file explorers work, and how Vegas Pro worked in version 10 (and presumably before).
I don't have time to think about it, but here is what I see on Windows 7 with Vegas 10 and 13.
Thank you John. Perfect illustration.
I'm seeing the same thing. VP16/361 using Windows 8.1 .. Does appear to be a bug.
I can confirm this bug. It does not just affect the detail view. It also affects the list and thumbnail views if the detail view was sorted by type previously.
I believe that I got what you meant ( I think 😉)
Maybe it comes from my workflow that I never care about those places in de Explorer. Most for big projects I use project Media and there is still the old "modified by date option" in stead of the new one in the explorer the "last modified by date option".
When I want to arrange al my possible events I use the All Media tab and arrange the files trough "Modified".
When want first only the video events I use the tab Media by type>> Video and pictures by Stills a.s.o. Works always excellent ( for me).
Thanks for all the contributions. I'll try and explain why this was a problem for me yesterday...
We shot a load of stuff with an Olympus TG4. 45% are JPG images, 45% are ORF (RAW) images, and 10% are MOV videos. It's all sequentially numbered and we put it all in one folder. I wanted to choose which MOV files to keep and which to delete, so I sorted that folder by Type in an external file manager (Directory Opus, but it could have been Windows Explorer) and dragged them to the Vegas timeline. I then sorted by Type in the Vegas Explorer window so I could delete the unwanted files directly there as I reviewed them on the timeline, which is a normal workflow for me. But because the order was apparently random (within the listing of MOV files), it was very difficult to find each file.
I suppose this may have been due to a technical limitation when VP11 or VP12 was introduced, perhaps related to the move to 64-bit, but more likely it was an oversight.
The obvious solution is to put the files in separate folders and then just sort by Name, but of course that is an extra step.
Reported via support request [Ticket#2019031617000498] and added to the known issues list.