Hi DaveT2,

I imported them via the card reader to my hard drive as per normal. They currently reside there, which is where I import them from, into the Vegas project

"Yesterday it was fine..."

For now, you need to go back to what you had yesterday, get the projects done and then find out why you were having problems from what the computer guy did.

In the future, do not upgrade/change anything when you have a short dead-line on projects.

And when you do make changes ALWAYS make a clone or other type of system backup FIRST!

If your computer guy does not know that then find another computer guy.

The reason I asked was because I thought the WD SES driver was a driver Western Digital uses for some of their external drives (passport, etc). If you are transferring to your internal drive and importing from that, you should be good. Check to see where your temp files are going. There are various areas from temp file, project properties and preferences.

Dave T2

Hi jamesl, please try switching your Project Media view mode from Thumbnails to either Details or List. I suspect that the error is occurring on thumbnail creation. We are aware of this issue and are working to resolve it ASAP. Please let me know if this does not resolve the issue.

Best,
Paddy
SCS

Hi Paddy,

Wow!! It's working again! Thank you so much! That gets me out of a bind at least until the next upgrade comes along (it is very convenient being able to see the thumbnails, but at least I can continue with the work).

Thank you all for taking the time to respond

Good to hear that you're able to get back to work. I do apologize for the inconvenience, as I said we are working to resolve the issue and it will be fixed soon. Thanks for replying.

Paddy
SCS

Nice job from SCS! I didn't know they even posted here.

FORUM ADMIN

what does ASAP mean!!!!

this is such a basic function - i now have 350+ photos that i can't see, and since they're dslr, ie, dsc_# it means i have to use another program to view them while trying to edit with them.

as i wrote in my other thread - how could something so basic and obvious get released?!!!

before i get REALLY upset, does anyone know if the previous release (394) exhibits this problem?

ASAP = As Soon As Possible. Or are you asking "Just when is ASAP"!

Leslie, are you having a Thumbnail issue too?

Trying here . . . .

Grazie

hello there old boy,

not a happy vegemite - at all!

yep, bl**dy seizing up on thumbnail creation (stills only - jpg AND png) - i mean how basic a function is that!?

i've over 350 dslr pics, complete with meaningless dsc_#'s to drop in on a tl, and am now trying to run either win explorer or bridge at the same time as vegas to find out what pic i'm using. i mean this isn't doing my creative juices any good at all, let alone my temper...

and yes, was asking WHEN is asap. i would have thought this is about as serious as it gets with a supposedly 'pro' nle?

how's it working out your end?

OK, some info Leslie: Project Media Pane IMPORT media uses the M$ Windows function for display. This is a choke point for the number of available thumbs to be seen. SCS are working on it. Time to delivery? I really wouldn't know.

I have MXF and they will not show on the "Import Media". I now continually use Vegas Explorer and import that way. I can see my Canon MXF Thumbs, no problem.

Are you saying you CAN'T see the stills on the Timeline?

G

no problem seeing stills on the tl (thankfully), and, as described earlier in this thread, if i use either list or detail view i don't get a freeze - but since i'm going to use bins to sort the pics, i'm somewhat stuffed to say the least!

would love to hear if anyone using 384 suffers this problem - i can't remember and certainly don't want to reinstall if i get the same sh*t!

oi vey, really don't need this ever so basic level bug with THIS sort of project ;-(

"would love to hear if anyone using 384 suffers this problem "

I went from 486 back to 394 and I do not have any of the problems in this thread.

So SCS has to now start over and figure out a way to fix the bugs of 394 without creating the new ones and/or re-introducing the old ones.

Seems that is all they do is swap bugs and/or create new ones trying to fix the old ones.

Last NLE I had was Ulead's/Corel's MediaStudioPro8 (MSP8). It had a lot of shared files and everytime they tried to fix bugs they would create new ones and/or re-introduce the old ones.

I am not sure about Vegas but it makes me wonder just how much shared code(s) it has. If it indeed has shared code then the possibility of having a bug free NLE is impossible! It will keep on going in circles and/or dead-end directions.

I would rather the code be 100 times larger if that is what it takes for bug free and stability than a compact/shared code that is forever buggy/unstable.

All is 100% stable on my system mainly because I do not push Vegas very hard, my workflow and other things I do and/or not do.

I never do a huge project. For instance with theater, I use the scenes to make a bunch of little projects instead of one big project. Little bites for Vegas to digest at a time.

That is my thoughts on this.

Danny Fye
www.dannyfye.com/ccm

thanks danny,

looks like i might roll back to 394....

gone back to 11 which i still have installed (always keep two versions going).

working perfectly.

i need to moan - so you can ignore the rest of this post....

what is happening at scs!? how can you release without checking BASIC functions, and how do you break what was working in a previous version?

it makes me both sad and angry that i keep paying for software that keeps bloating with unnecessary gimmicks while its basic functions keep failing.

thankfully i'm no longer at the mercy of client deadlines, because if i was vegas would be long gone, no matter how attached i am to it.

shame on you scs for steadily degrading what was once the very best of nles!

I've mentioned this before, but it's worth mooting again, albeit slightly differently, but hopefully not preachy. grin

With a huge legacy code base, there is doubtless a lot of needless complexity. There are always places where the devs have got it working and quickly shut the lid in case it breaks with a view to going back and doing it properly later on, which almost never happens due to the next deadline promised by marketing / sales.

What that amounts to is called technical debt and once it's borrowed, it's awfully hard to pay back, especially if the original dev or devs have left. This is because unless the people in charge are into say four week sprints (see SCRUM.ORG) where there are only one or two items that will provide tangible business value, and the rest is refactoring, then the dev team are hamstrung, and so the more the technical debt increases.

The other syndrome is called 'whack a mole', where teams make a change and something, seemingly unrelated breaks. This can be cured by ring fencing delicate areas of code with an exhaustive as is possible suite of unit tests. This provides a safety net. If the tests break upon check in of code, the change someone just made broke it.

While I appreciate UI's are much harder to test, there are tools around, e.g. Test Complete.

Also a good way to help ensure code doesn't break is to endeavour to make each module or suite of classes as independently testable as possible. It's interesting how easy it is to modify parts of the code to include new parts of functionality, but the danger there is that what needs to be added may not belong in that area, and is a violation of both SRP (Single Responsibility Principle) and OCP (Open Closed Principle). Everything should do little well, and a rose by any other name is not a rose. Think of a toaster and a kettle, that share the same thermostat, as unlikely as that may seem.

I always strive to ask myself two questions when coding, or better pair programming, "How are we going to test this?" and "Could it be any simpler?"

It's all too easy to go off coding, especially when it's cool, but ultimately any code that is released must be at least as robust as that which went before.

There, that's my two cents...

I have been getting this issue a lot just today. Not sure what I did but once I get 1-2 clips into the timeline, the 2nd or 3rd freezes up. I also can't view my Project Media tab at all as one click of the tab freezes up the entire program. This hasn't happened before and just started happening today. Fresh computer restarts, change from thumbnail to list view, and adjusting the RAM settings haven't done anything to stop this from happening.

Sucks that I have a TV episode to get together on a certain deadline and I can't work on the .veg file in Vegas Pro 11 as a backup. I already did a bunch of work on it and hate to do that all over again, especially if I run into the same road block again. If I can't figure it out in the next day or 2, I'm going to have to restart what I just did. Pretty bummed right now.

wozwick,

Please locate the following folder (you may need to enable Show hidden files and folders in Windows' Folder and search options):

C:\Users\[user name]\AppData\Local\Sony\Vegas Pro\12.0\Media Pool Thumbnails

Delete the contents of that folder. Then return to Vegas and switch your Thumbnails view to List or Details.

Thanks,
Paddy
SCS

Whatever - Vegas 12 IS astonishing happy to hang/ lock up/ or red-frame.

About a month ago I thought that I could change fully from my very stable V11 to the newest 486 V12 - but I quickly learned: not so.

It may be my Vegas "unsupported" Mac Pro with native Win 7 ultimate, of course - but V12 hangs as happily now as it did when I installed its first version.
Probably I could set preview RAM or whatever to whatever or change whatever to whatever - but I do not have so much time anymore for all these experiments-in-the-blind...

Absolutely no problem, however: V11 is still as rock stable here as ever after build 700 and I can edit for 8-9 hours a DAY without one single hickup....

... but still, and that is just my most humble opinion, V12 should not hang/lock so badly with the same media that V11 just deals with perfectly.

Example: last week I put some Vegas 12 made 4K png screen-shots onto a Vegas 12 time-line - and then it started: hang -red frame -lock- %#!// (pardon my french).
As I did not have much time I simply started V11 and put the very same V12 made png's onto the V11 timeline and did the same editing again: and quite as expected: No problems whatsoever - and the project was quickly finished.