-
Videoon 1/3/2023
Not Responding
I'll give that a try. Never knew that even existed and at a brief glance, I'm not sure what use it would be to me anyway.
-
Videoon 1/3/2023
Not Responding
@Roger Bansemer Give this a try (no promises though) ... In Vegas Hub, turn off the Create Project Collection slider switch: What you have described has also happened to me, and turning off the Collection option stopped the lagging and normal transmission resumed. It would be preferable IMO if the switch was set to off as a default.
-
Videoon 1/2/2023
Not Responding
I've been working on a project for several days with V20 and it's been quite good. Only 4 or 5 "not responding" messages during the entire day. Then yesterday I continued on the same project and it lagged horribly, not responding every couple of minutes and so on to where I just quit. Today I've been having pretty good luck again. It seems that V20 is like a bad child that has tantrums for no reason. No reboot or anything can help. It has a mind of its own.
-
Offtopicon 12/31/2022
Getting audio from Vegas to RX9
Yes. Easy. In Vegas Pro go to Options/Preference/Audio (tab) and link 'Preferred Audio Editor' to RX9's .exe file in C;\Program Files. Then, on VP's timeline, R click on an audio event and in the context window that opens click on 'Open in Audio Editor' or the Copy option which will create a copy of the audio event on VP's timeline thus keeping the original audio intact. That was easy. Thanks so very much. Don't know what I'd do without everyone in the forum answering questions.
-
Videoon 12/27/2022
Border around non 16:9 image
Thank you very much. I never knew you could even do that.
-
Videoon 12/21/2022
Closed Captioning gone
I'll be darned. Guess this is another bug in V20..... I put the file on V19 and the captions appear.Thanks for the suggestion. When on earth are they going to fix this version?
-
Videoon 12/19/2022
Auto Tracking
I do, yes as Vegas now has the hooks to connect to AI engines. I just don't think it's at the top of the priority list (and rightly so) as there are more basic playback and performance issue to attend to. That's for sure. I started a new project today using Vegas17 and worked on it almost all day with not one crash or "not responding" I saved it for V17 and then moved to V20 and saved it there as a new project and almost immediately it lagged and was dealing with the "not responding" issue again. Only reason I'm using V20 is because of a few new features for color correcting, etc.
-
Videoon 12/13/2022
Masking and pan crop
1.Select the parameter Position 2.Right Click on Pan Crop Window3.Choose Restore Thank you very much. That one certainly wasn't obvious and it's baffled me for a long time.
-
Videoon 12/13/2022
Masking and pan crop
Did you select the Pan/Crop layer on the timeline at the bottom of the pop up screen? Yes. But after that is checked and then unchecked it does not revert to the original pan/crop so the clip can be tilted, etc.
-
Videoon 12/12/2022
Not Responding
Set your Dynamic RAM Preview max back to default if you use that option a lot.When you don't use Shift+B you can set it to 0 and you will see no or less your "not responding" anymore. I'm watching a Vegas tutorial on youtube by "scrapyard films" and he says to set dynamic range as high as possible and your advice is the opposite. I'm confused His video states this at about 1:00
-
Videoon 12/11/2022
Not Responding
Set your Dynamic RAM Preview max back to default if you use that option a lot.When you don't use Shift+B you can set it to 0 and you will see no or less your "not responding" anymore. I'll give that a try however I do use the preview render quite a bit.
-
Videoon 12/11/2022
Motion tracking with text in back of video
I've been fussing with the text behind an object using track motion and finally figured it out. I've put together a short video on how I did it using Vegas 20.
-
Videoon 12/10/2022
Not Responding
Thank you for the pics but I see 2x the same pic of File I/O and not one of the Video tab Sorry, my mistake.
-
Videoon 12/10/2022
Not Responding
. Working with V20 is horrible. Even with a new project with only a few video clips and one audio track on the timeline, the lag time and crashes are almost continues. I think I'm very lucky not seeings those problems and therefore I like to help you if possible.Therefore it's needed to see a few of your settings, screenshots of- Options/Preferences/Video- Options/Preferences/File I/O- Screen you get after Help/Check for Driver Updates Thank you. That is very kind of you. Hope you can spot something.
-
Videoon 12/10/2022
Not Responding
@Roger Bansemer all you have to do is open VP20 and the project. Highlight the entire project, copy (Ctrl c) and paste (Ctrl v) into 17 or 19. That works with the clips themselves and audio but if you have color balance, etc on the track level it would not carry over.
-
Videoon 12/10/2022
Not Responding
When you mention, can't "revert" are you talking about going to a previous version of Vegas? If so, just highlight and copy the timeline and paste it in a previous version. Yes, I can't revert to V17 or V19 after having started it in V20.
-
Videoon 12/10/2022
Not Responding
You are so lucky. I'm using 365. Maybe that a problem. I have no idea except now that I've started multiple projects with V20 I can't revert and it's made editing unpleasant where it use to be a joy.
-
Videoon 12/10/2022
Not Responding
I wonder if anyone in the team that writes the code for Vegas is seeing these posts. Working with V20 is horrible. Even with a new project with only a few video clips and one audio track on the timeline, the lag time and crashes are almost continues. It's strange because on some occasions it works OK. Other times it's impossible to use. I could capture a video of this situation using Snagit if someone from the Vegas team would like to actually see how poorly Vegas performs. I do know that downloading and dragging an audio selection from the Vegas Content onto the timeline really lags the entire editing process.
-
Videoon 12/2/2022
Broadcast Safe Zone not apparent in final render
@Roger Bansemer "I do know that if I take a rendered video that is broadcast safe and put it back into Vegas it bumps up the levels again..." I use an ancient version of Vegas Pro (4-17) to check that if I'm half asleep and/or really curious. Those versions don't attempt to "help you do your job". If you don't have an ancient version of Vegas Pro. Open the rendered file in a new Vegas Pro project. For the Pixel Format select Legacy (8-bit video levels). Set Preview to Best/Full The scopes will not be altered by any help from Vegas and you will see what other applications see before they screw up the levels beyond recognition. This helps. Thanks. So what I'll do is edit in Full Bit and if I want to edit already rendered switch to Legacy. I think I got it ! If you would be so kind, can you simply explain how the Full Bit is "helping me do my job" as it doesn't limit the levels to 100 automatically. I still have to go in and adjust levels just as I do with the Legacy setting.Sorry to be so stupid with this stuff. I've produced and edited 143 of our shows for PBS called "Painting and Travel" and this "full bit" thing has thrown me.
-
Videoon 12/2/2022
Broadcast Safe Zone not apparent in final render
Hi Roger, The Broadcast Levels fx is a holdover from analog television days, when levels were derived from voltages, and Chroma Slop up to 120 IRE was allowed. That fx could be safely removed today from Vegas. The Computer->Studio levels filter (or Full Range) projects should always be safe for PBS, since luminance and chroma are hard clamped at [16,235]. To maintain its integrity, the levels filter must always be placed last in the fx chain; even something as simple as a Sharpen filter can cause illegal highlight levels, if placed downstream. I've been reading all the posts about this 8 bit full and legacy and I still find it totally confusing. Guess I'm looking for a simple answer especially when some posts say to check out my cameras, etc. to see what they are capable of which doesn't help because some cameras might be capable of the higher range and others not, so it doesn't help if I have 5 or 6 cameras on one project each of different specs.I do know that if I have my project set to either 8bit full or legacy, I can edit and get my broadcast levels correct. At least they look right according to the scopes so is there a simple answer which one to use.I do know that if I take a rendered video that is broadcast safe and put it back into Vegas it bumps up the levels again so I guess I have to be careful if editing an already rendered video that I switch back to legacy.
-
Videoon 11/30/2022
Titler Pro 7 freezing up Vegas 20
I use Titler 7, latest version Vegas 20 214. If I have a pretty big title with lots of layers and lot of animations it takes a long time from the time I click the green check until control returns to Vegas. It'll grey out sometimes for five or so minutes. I just go grab a coffee and come back. Performance is definitely poor. Not sure how long you are waiting but might try waiting it out some. Once I've done it once, successive edits seem to return control much quicker. It's interesting to know others are having the same problems. I have tried waiting it out many times and sometimes it comes around and other times it doesn't no matter how long I might wait. It really isn't a feasible program if you have to wait 5 minutes to get a title which when it works is sometimes the case with me as well.
-
Videoon 11/30/2022
Titler Pro 7 freezing up Vegas 20
I do have the most recent version and still the same issues. Please do make sure to update to the newest version!
-
Videoon 11/29/2022
Broadcast Safe Zone not apparent in final render
Wow! I see what you mean. Taken the past half hour looking some of that information over and you are right... very confusing. I do see a difference in using the full and legacy settings however. On a clip I put on the timeline, the "full" has the limit on 109% and the legacy is 104%. Either way I'd have to adjust it so not sure where the "automatic" level comes in.I use several cameras but primarily a Panasonic DVX 200 and several Sony AX53's. I use a few other cameras but they are even older.One last question and then I hope to leave you alone. Is your advice is to stick with the "Full" setting and just work from there on new projects and not worry about the "legacy" and if I have to edit an already rendered video made with the "full" to change the preference back to legacy since it bumps up the levels again?
-
Videoon 11/29/2022
Broadcast Safe Zone not apparent in final render
Hi Roger, I didn't take it that way- I more meant do you want to take the time to understand it as it can be quite confusing. I avoided it for as long as I could. For the "new" auto mode in Vegas (8-bit full) start here.https://www.vegascreativesoftware.info/de/forum/vp18-notes-on-the-8-bit-full-level-option--122749/ Until that time we had to deal with levels manually. When I shot with a full range (0-255) camera it was easy- just add a computer to studio levels RGB filter at the end. However when I got one which shot video range (16-235) it got harder. It looked flat as it had no whites or blacks and the still images I used didn't as they were computer range (0-255). So I had to first manually convert the video to full range at the track or media level just to be able to see what I was doing accurately in the preview window. Then back to video levels manually to render a file that would play back properly. What is your footage? Nick has a user-created database of camera levels. You can easily do your own tests as described here (shoot with lens cap on for black and a light source for white, then check the histogram).https://www.vegascreativesoftware.info/us/forum/survey-what-min-max-levels-does-your-cam-shoot--84677/?page=1
Roger Bansemer
Offline, Last login 3/25/2023, Member since 9/3/2016