John Rofrano
Forum Replies Created
-
John Rofrano
April 5, 2016 at 8:15 pm in reply to: Can’t preview CC in the preview window – only see first one and the others don’t show upYou can also check for updates from the Help menu (if I remember correctly). Just install the latest version over what you have and it will perform an upgrade.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
John Rofrano
April 4, 2016 at 11:38 pm in reply to: Can’t preview CC in the preview window – only see first one and the others don’t show upMake sure that you have the latest build for Vegas Pro 13.0. Earlier builds had a bug where CC would not update.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Greg Ball] “Does this work in FCP 7?”
Unfortunately, No. CoreMelt SliceX, TrackX, and DriveX are only available for FCP X. (hence the ‘X’ in their names) 😉
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
You’re welcome. There are no less that 4 places to add video FX: Media FX, Event FX, Track FX, and Bus FX. Each has their own behavior so your confusion is not uncommon. 😉
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
What are the specs of your computer? I had no problem with AVCHD files with my Intel Core i7 6-Core.
What camera are the files from? I only use Sony cameras so my files are usually compatible with Vegas Pro but some manufacturers create AVCHD files that are not as compliant.
You could convert them to Sony MXF which should play back smoothly.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Chris Randell] “I change the Media FX on the top video but whatever changes I make to it, happen to the video below it. “
That’s how Media FX are supposed to work. They affect the Media wherever it is used on the timeline. If you only want the FX to affect the new Event, then use Event FX instead.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[leonardo barone] “there is a way for deactivate it ?”
No. These are the waveform files that get displayed on the timeline. I agree it’s annoying that Sony leaves these scattered about on your hard drive but they are a necessary evil if you want to see the wave forms and there is no way to deactivate them or place them elsewhere. Feel free to delete them but they will get regenerated the next time you open a project that uses that media. It’s just an annoying design.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
We’re going to need more exact information if you want us to help you because obviously somewhere along the way, a setting is not what you think it is.
[Kay Gee] “My project is set to 1920 x 1080. Fine.”
Can you please post a screen shot of your project properties window?
[Kay Gee] “I render a sub-clip with a bunch of effects from that project, also at 1920 x 1080. “
Can you please post a screen shot of the exact render template that you used?
[Kay Gee] “The file is indeed that size, according to every possible way I can check.”
Try checking with MediaInfo and post what it thinks the video properties are.
[Kay Gee] “I import the clip I just rendered back into the project, and … it’s not 1920 x 1080. I have the annoying Black Bars of Failure all around it.”
Once again, a picture it worth a thousand words. If we could see what you are seeing… a screen shot of your Vegas Pro GUI showing the black bars would help.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
John Rofrano
April 1, 2016 at 9:55 pm in reply to: Grass Valley ADVC-HD50 HDMI to HDV converter and Sony Vegas Pro 13..[Jean-Pierre Desrochers] “I know there are issues about PC motherboard USB3 chipset.. I own an ASUS X99 motherboard so I’ll have to check if the Intensity Pro would be accepted and by the motherboard AND by Vegas itself.”
No, it’s not compatible. The BM web site states:
USB 3.0. Requires an x58 based motherboard with onboard USB 3.0, or a USB 3.0 PCI Express card and a x58 or P55 series motherboard.
I wouldn’t chance it. You might even want to look into a HDMI recorder like the Atoms Ninja. These files can be dropped right into Vegas Pro. As long as you don’t use too many files you should be OK but be warned that Vegas Pro has memory limitations when working with QuickTime files like these.
Like I said the Grass Valley ADVC-HD50 HDMI to HDV converter should work fine as long as your motherboard has a Firewire port or you add a Firewire PCIe card. Of course, Windows 7 has issue with some Firewire chipsets too.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
[Rob Cioffi] “1. What’s so special about this proposed format?”
Apple ProRes is the defacto standard for video professionals working on Macs. AVC/H.264 is the defacto standard for web video delivery. It makes perfect sense to me to want those formats if you are working on a Mac.
[Rob Cioffi] “2. I know SVP (or Windows) does not render ProRes. I’ve found a program called Scratch that claims to be the only Windows program that can genuinely render ProRes files.”
That’s sound like it will do the job but is the price really $650 for a one year subscription? You can buy a Mac Mini ($499) and Apple Compressor ($49) and for $548 USD render all the Apple ProRes files you want without even tying up your PC. I would be careful about how much you spend on this.
[Rob Cioffi] “I also found this for the H.264 piece”
Sorry, but the person in that video doesn’t have a clue what they are talking about. Sony Vegas Pro 12.0 supports H.264 right out of the box. Just use the Sony AVC or MainConcept AVC render formats and both will produce AVC/H.264 MP4 files for your client. DO NOT put H.264 in an AVI container.
[Rob Cioffi] “My plan is to render an AVI with the H.264 codec in SVP then import it into Scratch then directly render it to ProRes4444. Does anybody think this will work?”
It’s not a good idea to use a highly compressed Internet delivery format like H.264 to feed another encoder. Especially one that is generating high quality ProRes4444 files. You would need to render uncompressed to generate 4444 files to feed the ProRes4444 encoder but since the source is a 4:2:0 DSLR, you don’t need to deliver ProRes4444.
You should be delivering ProRes422 HQ. You would have to see what formats Scratch accepts to know what to render out of Vegas Pro. If you are working in HD, and scratch can accept Sony MXF, I would use the HD422 1920×1080 50Mbps template. BTW, ProRes422 HQ is 220 Mbps and 1 hour of NTSC/29.97fps footage is about 100GB in size so you should think about how you will deliver these large files.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com
