Al Bergstein
Forum Replies Created
-
Just rendered out another set of videos, and yes, the green line is still there (after upgrading Vegas yet again). It is ONLY showing up on 480 SD MP4 widescreen renders. So I suspect a bug with the software. I can render the same footage in 360 and it doesn’t get the green line. I am not using the “Upload for Youtube” add in. Though it is installed on the system. As I can reproduce it at will, I am calling this a bug.
Anyone else seeing this bug?
Al
-
I would have to agree with Tim’s assessment, and Nick makes great points too. Focusing on one market at a time is key. Each market has a different set of needs to fill to sell to it. None are the same, though many overlap.
As I build my video production company, I think of it as being back in college, (trade school more than big colleges). You need to build a portfolio that is compelling. You might have to work for nearly nothing or nothing to do that. You will produce crap at times because the client (there is always a client), may not share your vision, nor have the money to pay for it. It’s your new education you are building, so if you can’t afford to do that, stop now. Going into business undercapitalized is one of the biggest mistakes many people make. If you have to work other jobs to support building your portfolio, then do that. And as someone who survived in commercial photography in the 1970s and 80s, I would add that getting out and meeting people, selling yourself and your company, has to be an integral part of your work for the next 5 years, if not forever. There are few people in small business that have a steady flow of work. Don’t expect it.
Good luck and enjoy the ride!
Al
-
Yes.
Al
-
That’s the one. Thanks Syed! And I assume Andy, that’s the same kind of tutorial. Looks simple enough, I’ll just spend some time on this. You guys are great. I’ll show you what I come up with when it happens.
Al
-
I think that I would first try moving your media to a FW800 or TB. That’s a cheap way to test.
Al
-
Thanks AE.. I don’t think that this is what I’m thinking of. None of the effects there seem like the ones I’ve seen. It is more like being able to take a standard old black and white photo, create layers for foreground, middle ground and background, and then do something to those layers so that you independently move, say the camera angle dolly right or left, and each independent layer could move as if in 3D. It doesn’t need special glasses to get the effect, so it’s not real 3D. The difference from just a normal mask is that the depth affect appears as if it has true depth to the picture.
Al
-
Thanks Andy. I’ll pick up his book, but also see if he’s got it covered on Lynda.com. I’m doing some of his other lessons there. Now that I know where to start looking, that might be good.
I’ve looked at a lot of templates on the web, but none have that effect where you take a black and white, probably mask multiple layers of the photo and then do something to setup the depth effect with the various layers. Nothing fancy I’m sure.
Thanks again.
Al
-
I realize I probably need to clarify this post. I don’t want to achieve the effect of needing 3D glasses to see the effect, but what I’m trying to get to is a multlayer depth on one photo, which I assume I would do by masking areas of the background. But the effect I’m describing then achieves a kind of depth of field that is somewhere between true 3D and a standard B&W still. Naturally I can’t seem to find an example now that I want to show what I’m talking about (G). .
Hope this clarifies the question.
Al
-
Jim, to be clear, you are not working with your media and other large files directly on the drive with the OS on it are you? When you say you copy all your working files to your local drive, what exactly do you mean? If you are trying to run all your clips off your OS’s hard drive, that could be a problem. My assumption is that you are using your media files on an external FW800, eSata (with add on card) or Thunderbolt drive. You’ve got plenty of RAM and a great processor, so that’s not the issue.
If you are using the media on your local drive, how full is your hard disk? Rule of thumb is that it should not be allowed to be over 80% full, and even that is asking for problems.
If that’s not what you meant, then sorry about the misunderstanding.
Al
-
Phil, thanks for the update. You might want to try running on one monitor as an experiment for a few days. As to the discussion on the compatability mode, it’s the first time I’ve heard about running in compatability mode, The program is sold as being compatable with the latest W7 builds. For now, I’ll take compatability mode advice from Sony with a grain of skepticism.
It’s been my experience that New Blue has seemed to me very buggy, but the crashes I’ve experienced were not just NB, to be fair to them. I’ve had these crashes come and go while using Sony’s own plug ins. Less often lately, as I have gone back to using one monitor rather than two. It happens less with one monitor, but still does. I’m pushing a lot of MXF files (meaning 50Mbps so think large) , but I really don’t use much in the way of fx. I’ve not been experiencing problems with multicamera footage, which means that the code doesn’t break in those modules (for me). The crash dumps don’t reveal much of anything except exceptions that appear to be very generic. You would have to know more about the code to know if they matter, as they aren’t usually pointing to a module, but just exceptions. I routinely check my memory useage and I never get close to running anything more than about 6 GBs of total RAM useage.
I have been seeing a lot less crashes since I cut back to one monitor, and stripped out fx. I’ve been running all fx’s in separate timelines, rendering them and then importing them in to the main timeline. That *does* seem to help. Oddly enough, when I had a laptop last fall and into this winter(Samsung, W7, 64 bit, etc. which I’ve since sold due to no longer traveling) I had *no* crashes. I did not install New Blue, nor any other fx other than Sony’s. I pushed the same footage through it, including MOV and crashes were almost, but not totally non existant. They were dramtatically less. So what’s the difference? The OS was the same (Windows 7 Ultimate), the RAM identical, the version of Sony, Vegas, the same, and the same external eSata hard drive with the footage on it. The graphics cards were different, and no NBlue. Not picking specifically here on Nblue, as I bet I would find some issues with other fx providers if I bought their products. Has anyone been experiencing lots of crashes with Boris installed, for example?
I can’t imagine that Sony’s team, if they were looking, couldn’t reproduce these kinds of crashes. Most of us can likely reproduce them by just spending 2 or more hours on our computers, it seems.
But I’ll keep trying to gather some knowledge on this. Like I said, my sample size is too small. I do not suspect Windows 7. I don’t suspect my hard drive (as I don’t buy green drives nor program them to sleep). My machine does not act up at all with anything else I throw at it, so it really seems to be just a Sony problem. The crashes *only* happen within Sony Vegas 11.
Al