[David Komer]

I shot 25P with a DVX-100. Also- see https://forums.creativecow.net/thread/8/917816

Please unravel this mystery 🙂

[David Komer]

Ah, seems like question 1 was answered at-

https://forums.creativecow.net/thread/8/917816

Though I’m still a little confused on, if I wanted to use the clip properly in premiere. I’ve set up a 25P project- i.e. same settings as PAL DV but no field ordering. The footage looks fine, but it needs to render. Seems like this is more of a compression question so I’ll move it over to there…

For question 2, I understand that the useable image should be 768×432 (sq. pixels. 720×432 PAL-shaped), which leaves room of 144 pixels for the black bars. In virtualdub, I’m seeing that 69 off the top and 75 off the bottom looks right.

[David Komer]

https://help.youtube.com/support/youtube/bin/answer.py?answer=132460&topic=16612

[David Komer]

Ah, whups- didn’t realize that with Flash it’s the player that makes a difference, not the publishing. Ignore the bit about “If that bundled FLV player was published from Flash greater than 9.0.115”, but the rest holds true 🙂

[David Komer]

I’m not familiar with vPIP, but at a glance it seems like it has a bundled FLV player. If that bundled FLV player was published from Flash greater than 9.0.115, then the following should work:

1) Encode a h.264 video.
2) Rename the extension from .mov (or mp4, depending on the tool you’re using) to .flv (seems funny, but it’s the truth)
3) Upload that flv and point it at vPIP

If the bundled flv player doesn’t work with that, then it seems vPIP will also work with a swf. If you don’t want to deal with making a custom player in Flash, then you can also check out the JW media player- https://www.longtailvideo.com/players/jw-flv-player/

[David Komer]

I would guess, based on problems I’ve run into, that Daniel’s statement of “develop in house solutions” is probably about right for whatever software they’re using. Not necessarily scripted solutions, but different tools for different parts of the process.

“Compression”, on the software side, isn’t just a one-tool job if you are die-hard in getting the absolute best quality. There could be better solutions than this, but where I’m at now is: if I need to de-interlace it first, then I use FieldsKit or Magic Bullet Frames. If I need to resize it from rectangular pixels to square, then I use VirtualDub resizing with lanczos3. If my target is FLV then I use FlixPro. If my target is H.264 then I use Procoder (I’ve tested against MainConcept Reference- and for my test footage I did not see much of a difference, but I’m sure the opposite is true sometimes. I’m satisfied enough to use Procoder though). It’s a slow workflow, but it’s using what I find to be the best tool for each stage of the process.

If you’re looking for a “swiss-army-knife” solution from source to H.264 or MPEG-2 on PC, and don’t want to deal with avisynth and virtualdub, then Procoder is your best option in my opinion- much better than Squeeze in my tests. Though that was a while back and against an older version…

We’re moving to Apple though, and can’t budget for Episode at the moment, so I really hope Compressor 3 will do all the jobs pretty well (I’m trying to convince the director to move over to progressive so we won’t have to deal with deinterlacing)!