[John Rofrano]

[Marius Dudu] “Does applying supersampling from Master Bus will make any difference, if FPS from project is 30 fps and rendered video 25 fps ? Or vice-versa, from 25 fps to 30 fps.”

A difference in the video quality? No.

Super Sampling will only affect motion created inside of Vegas Pro. This includes the media generators, pan/crop, track motion, FX, or transitions. It samples at a higher rate too smooth motion at the expense of compute power. It does not improve video quality itself.

If you want to see it’s effect, create a white circle with generated media and animate it moving across the screen and render that out. Look at it frame by frame. Then apply super sampling and when you look at it frame by frame, you will see motion blur added to make the movement much smoother because It adds interframe motion blur to these types of motion. BTW, you will only see this in the preview window if it’s set to Good or Best.

I’m not sure it would help with converting from 25fps to 30fps video since it works on internally generated video images.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Jan Rogowski] “I cannot figure out how to get my vegas image sequence to render with timeline relative frame numbers in the filenames. Surely this is possible?”

This is not possible because an image sequence is just a series of images without regard to timecode. All software that processes image sequences expects the first image to be zero with subsequent images incrementing by one. You can easily rename the files with 3rd party software after they are created but I’m not sure that other programs would still recognize them as an image sequence any more.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Seth Kopchu] “Instead of manually cutting the audio into sections, is there a way to set the pitch to gradually lower slowly but all at once”

No. The pitch shifting in Vegas Pro is only available on an entire event so gradually changing it is not possible.

You would need to find an audio plug-in that can alter the pitch which also supports automation so that you could do it over time.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Rob Bond] “My understand was Project markers are saved in the *.sfl file (which is located in the media folder along with the DVDA project file)”

That’s correct. Is that file being created? It must be in the same folder as the file it is the markers for. So if you have my-video.ac3 then my-video.ac3.sfl must be in the same folder along side it for DVD Architect to know that’s the markers for that file and it must have the same name including extensions as the file but with the added .sfl extension.

Have you tried loading it manually? There is an option in DVD Architect to load the markers file.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Mickey Power] “If I ever re-booted to it, I assume I wouldn’t get a picture right? And if I couldn’t get a picture I wouldn’t be able to boot back to my main system?”

I assume you do not get a boot screen with the Nvidia GTX 980 ti card so you would have to designate Snow Leopard as the boot drive and then could get stuck with no screen when there are no graphics drivers to load. I’m afraid this is correct.

Does your recovery partition work? When you boot and hold down Command+R are you taken to the recovery screen? If so, then that might be an option to reset the boot drive. This is why I stayed with Apple compatible graphics cards. Not having a boot screen leaves you little options for having multiple boot partitions like I have.

You can have dual graphics cards. Maybe you could pick up an older card that is compatible with Snow Leopard so that you can still use it?

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

Yea, that is what I expected.

And FCP Legacy is really finicky. I had it running fine on a Snow Leopard boot partition with my ATI Radeon HD 5870 graphics card. No problems. Then I decided to upgrade to the AMD Sapphire Radeon HD 7950 Mac Edition and FCP stopped working! It refused to start claiming that I didn’t have a compatible graphics card. I think what actually happened is that Snow Leopard didn’t have the right drivers for the newer card.

Luckily DVD Studio Pro continued to work and that’s all I really cared about because I use FCP X now. But I didn’t think going from the HD 5870 to the HD 7950 on the same OS would cause FCP to stop working but it did. ☹

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Bouke Vahl] “The source for DNxHD is open, but Apple chooses not to implement it.”

Why would they? They already have awesome intermedia codec (ProRes) that everyone uses. The short list of non-supported codecs (Avid DNxHD / DNxHR, CineForm, and Sony HDSR) is underwhelming. Most Apple editors use ProRes so this is really a non-issue unless you need to work with people on Windows who need to use DNx and CineForm because Windows doesn’t have a good intermediary codec. I would not want Apple to waste any time worrying about Windows codecs.

[Bouke Vahl] “Now, you can go torture yourself with a company that makes you hurt, I’m not that kind of guy.”

No torture here. I’m not affected by this. Apple will still support all of these codecs:

• Apple Animation codec
• Apple Intermediate codec
• Apple ProRes (all versions)
• AVCHD (including AVCCAM, AVCHD Lite, and NXCAM)
• AVC-ULTRA (including AVC-LongG, AVC-Intra Class 50/100/200/4:4:4, and AVC-Intra LT)
• Canon Cinema RAW Light (requires the camera manufacturer’s plug-in software)
• DV (including DVCAM, DVCPRO, and DVCPRO50)
• DVCPRO HD
• H.264
• HDV
• HEVC (requires macOS High Sierra 10.13)
• iFrame
• Motion JPEG (OpenDML only)
• MPEG IMX (D-10)
• QuickTime formats
• REDCODE RAW (R3D) (requires the camera manufacturer’s plug-in software)
• Uncompressed 8-bit 4:2:2
• Uncompressed 10-bit 4:2:2
• XAVC (including XAVC-S)
• XDCAM HD/EX/HD422
• XF-AVC

That’s not a trivial list. Most of my “old” footage is HDV and AVCHD which is still supported and newer codecs like AVC-ULTRA, XAVC , and HEVC are all supported.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Andrew Johnstone] “I appreciate tat there are downsides to this workflow, a mirrored raid is not as fast as a single RAID and there is also the danger of drive failure from overuse. “

Actually, a mirrored RAID 1 is slower than a single hard drive. I would suggest you use a RAID 5 at a minimum or even no RAID at all would be faster than a RAID 1 although without redundancy.

[Andrew Johnstone] “Problem: Now, not only do I have a back up of the original rushes on my mirrored RAID, I also have a duplicate of all the material in the film’s ‘library’.”

This is actually an opportunity to reorganize how you work. I avoid this problem because all of my camera card media is on a separate portable drive from my projects. I ingest media to a camera card drive. Then when I’m ready to start editing, I transfer from that drive to my projects drive by importing into the Library. This gives me a back of up original media on a separate drive in case of project drive failure (because there are no more “tapes” to go back to!). ????

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

Funny, I just saw this after updating Compressor today. So here is a screenshot from the latest Apple Compressor 4.4.2:

Compressor is finally 64-bit and so it “natively” won’t load 32-bit codecs. Luckily, Apple is still providing a 32-bit binding for now. You can see the daemon running here in my gfxCardStatus app:

So Apple is simply declaring that it will no longer support the 32-bit daemon in future releases, and the codec developers need to jump on the 64-bit bandwagon.. Why? Who knows… maybe future GPU enhancements will make it impossible to maintain 32-bit compatibility? The point is that codec developers have had enough time to update to 64-bit. If they want to remain relevant they have no choice now.

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com

[John Rofrano]

[Bouke Vahl] “[John Rofrano] “It is 32-bit because it is discontinued.”
Very strange logic…”

Let me state it the way I intended it… “it is 32-bit because it was discontinued at a time when 32-bit was all their was”.. Not because the manufacturer did not upgrade it to 64 bit.

[Bouke Vahl] “A codec has nothing to do with 32 or 64 bit operating systems. “

It does at the application level. If the codec is called by an application, it needs an application binding. If the application is 64-bit and the codec is 32-bit they cannot talk to each other unless the application provides backward compatible 32-bit binding support. This is the same reason why 32-bit audio VST’s cannot load into a 64-bit DAW unless they provide some kind of backward compatible binding. This is where the problem lies.

[Bouke Vahl] “How come 4:3 black and white mono TV sets are still supported by all broadcasters, and their specs require you to keep them in mind?”

For the same reason that HD TV’s support interlaced video. Someone did not have the guts to drop interlace support when it was clearly not needed anymore. So day after day, young videographers ask the questions, “why are their lines in my video” and we have to remind them that back in 1920 (almost 100 years ago!!!) they couldn’t get an election beam to excite the phosphorous on the cathode-ray tube fast enough so inventors came up with this ingenious idea to scan 1/2 the lines at a time and thus preserve the picture quality. And the young videographer should answer, “why should I care 100 years later?” …and they should not have to! we should move on and let old technology that has outlived it’s useful purpose die. But that’s just my humble opinion.

BTW, TV is a bad analogy in the US because we banded the broadcast of analog signals and the US government even provided people with free analog-to-digital converters. If you have an old analog TV is is now useless without a digital converter box. Why? Because there was money to be made in selling the analog bandwidth!!! So I guess it’s OK to kill old technology if you can make money off of doing so.

IMHO, a few years after the 64-bit processor was introduced, Microsoft and Apple should have stopped making 32-bit versions of their Operating Systems and all of this would have been solved. But they didn’t. Would it have hurt? …Did it hurt when Apple discontinued the floppy disk drive? Yup! Did it hurt when Apple discontinued the CD ROM drive? Yup. Did it hurt when Apple discontinued all external ports on their laptops except USB-C? Ouch!!! That one is still hurting BIG TIME! (says this 2018 MacBook Pro owner) …but this too shall pass. ????

~jr

http://www.johnrofrano.com
http://www.vasstsoftware.com