[Ed Dooley]

I agree, as I already posted the same thing, about the vertical blur. But there’s no need to use gaussian blur, which blurs pixels in all directions, unnecessarily blurring the horizontal sharpness. The flicker is only happening vertically, which is why Motion Blur, set to vertical, is the way to go.
Ed

[Tom Matthies] “I’ve found that a small amount of Gaussian blur or a vertical blur will often take the edge off of a still with excess resolution. Try different amounts until you find the right setting for a particular still.
“

[Ed Dooley]

And……. try the flicker filter, that’s what it’s there for. I personally use a little vertical Motion Blur in PhotoShop before bringing stills into FCP, but the Flicker filter works too.
Ed

[Ed Dooley]

I’ve read of problems with earlier versions of Compressor creating Program streams, but I thought it was fixed by v2. A Transport Stream, the M2T for example, won’t play (as you’ve found). I’m not at my Mac so I can’t walk through the menus, but from memory you should be able to simply create a Program stream by selecting the Mux option in the Extras tab.
If you need this right away and you can’t get Compressor to do it right you can easily create a regular MPEG-2 in Compressor, take the separate video and audio files into MPEG Streamclip https://www.squared5.com/
and mux them together into an MPEG-2 Program stream, easy, and it’s free.
Ed

[Ed Dooley]

Hmmm, Compressor creates an MPEG-2 Program, or Transport, Stream by following the advice I gave. It should mux the audio into the video and create a .mt2 file, which should be video and audio together. If you’re getting a playable MPEG-2 video file and a separate audio file, there are freeware muxers available to create a Program stream. MPEG Streamclip is good:

https://www.squared5.com/svideo/mpeg-streamclip-mac.html

Ed

[Ed Dooley]

Go to a preset, such as a Custom MPEG-2, duplicate the MPEG-2 setting ans open that. Go to the Extras Tab and select Multiplexed MPEG-1/Layer2 Audio.
Ed

[Ed Dooley]

Kevin,
Not to steer you away from Compressor and DVDSP, but Adobe Encore is also an authoring
solution for Mac. As for the DV footage, David is right, that you should be able to create decent DVDs from mini-DV footage. The HD idea you had made me think you were trying to upscale DV to HD. But, you’re doing an art show, do you need to author this to a DVD, and in the process, compressing an already compressed format even more? If you’re able to play the piece from a laptop (or even a desktop) to the projector, I would strongly suggest that you eliminate the MPEG-2 DVD completely and instead compress a high data-rate H.264 QT, which you can export right out of FCP or QT Pro. It will look far, far better than an authored DVD.
Ed

[Ed Dooley]

It’s not clear to me that he’s trying to encode to MPEG-2 in Toast. His post says he’s burning a QT file to a DVD. If that’s the case, Toast is a fine tool for that, and the problem is probably elsewhere. If he is trying to encode in Toast, then David’s right.
Not sure, but the thing that caught my attention is that he’s trying to turn a sows ear into a silk purse, by shooting in mini-DV then trying to get HD out of it. Of course it looks good on the computer monitor, and it will look like crap when enlarged.
Ed

[David Roth Weiss] “[medal27] “My first attempts at test burning(exported Quicktime(animation codec) file from After Effects) to DVD from Roxio Toast have been really disappointing. The quality looks really pixelated, not as sharp and crisp as I’d like it to.”

I hate to be the tider of bad news, but it makes litle difference what codec you use to create your video because you’re just going to destroy it by encoding to DVD with Toast. Toast is CD/DVD burning software that, basically as an after thought, happens to include a DVD encoding app, and a very poor consumer grade DVD encoding app at that. Sorry!!!
“

[Ed Dooley]

But there isn’t an extra render. You’re using 10bit Uncompressed video.
If what you mean is “why the extra step?” Rich and David have answered.
If you search the posts you’ll find some discussion about the relative
advantages of exporting a self-contained or reference video or exporting
directly from FCP to Compressor (either pre-rendered or not). Other than
tying up FCP it has mainly to do with how key frames are rendered and compressed.
Ed

[jay lee] “Hi Rich,
Thank you for your reply.
Why that extra render…..why not go straight to Compressor from the FC timeline?
Other than my issues obviously.
“

[Ed Dooley]

You should join the innobits forum, they answer that exact problem (with a workaround for now). They also say that there may be a Universal version in a month or so.
Ed

Here’s what they say:
>>>>There is a permanent solution in the works.
Meanwhile the workaround for 8 cores is to disable some of the cores.
When starting BitVice, turn off at least one core.
(You can turn all back on again once BitVice has started, though. That is unless you first want to start several other BitVices to run concurrently. To do that, take a look at this “Power TIP, (If you feel the need for speed.)” https://www.innobits.com/f/index.php?topic=1188.0 )

If you have not done so before, you need to install the “Computer Hardware Understanding Development (CHUD) Tools” from Apple.
You will find the 31.7 MB .dmg file here https://developer.apple.com/tools/download/

When installed, a “Processor” icon appears in the “Hardware” section of the System Preferences window, see picture. Click this icon to change the CPU settings. That window may of course look different depending on which Mac model you have and how many CPUs it has. You can make changes there anytime, at least with BitVice. The work in progress on the CPUs you disable will automatically be migrated to the CPUs which are still enabled.<<< [jay lee] “Bitvice demo crashing on both our new 8-core machines. Very dissapointing!!
“

[Ed Dooley]

Never had that problem, but it’s a good idea to convert MP3s to AIFF 48khz anyway.
Ed

[Jurij Magoga] “Even if mp3s can be imported in FCP sequences, i’ ve experienced problems trying to trimming them after the render, and the same problems occured even with AIFF file encoded with a wrong properties ( i.e. 44.100 KHz instead of 48 KHz).
The file plays good quite a bit but at sometimes it jumps randomly like a playhead on a scratched record. “