ConnectHD 3.0

Laurence wrote on 5/24/2006, 7:13 AM

I just upgraded to ConnectHD 3.0. There are a couple of new options that look quite interesting. One is the ability to deinterlace and remove pulldown on capture, another is the ability to capture to a smartrenderable format (like what you get if you use Gearshift).

One question I have is how much bigger are the smartrenderable Cineform AVIs, and does it take any longer to capture and convert them?

Back to post

Comments

David Newman wrote on 6/2/2006, 8:40 AM

V2.5 (the V2.4 text wasn't updated -- should be though in 3.0.2)

malowz wrote on 6/4/2006, 2:30 PM

the 3.0.2 still has to re-render. im converting with avisynth-avs2avi using rgb24 colorspace, the file show in vegas as 24b. and using it in vegas was perfect. but, when render some effect, the preview file as 32b, and it re-render when rendering to new track for example. so, i guess to work it shoud be 24b all the time? or because vegas use rgb32 it generate a file with "rgb32" info?

if i use hdlink to convert, it shows 32b. selective prerender aparently just do a DSC, whitout render, but, get more space from us.

Jayster wrote on 6/4/2006, 6:25 PM

malowz - your shorthand was quite hard to follow..

im converting with avisynth-avs2avi using rgb24 colorspace
Converting what to what?

the file show in vegas as 24b
What does this mean?

when render some effect, the preview file as 32b

Sorry, but this is nearly impossible to follow. Only thing I can guess, is that if you even touch an avi then smart rendering won't help.

Different subject <a few messages up in this same thread> with regards to being able to render CFDI at different quality from within Vegas, I was able to do that after having installed 2.1. The dialog was Render As->Custom->Video->Configure and it said "Low HD" and "Medium HD" and "High HD". The documentation on the website said this referred to output file size (probably compression level) and advised that the difference between medium and high would not be noticeable in most cases. If something changed in the new 3.0 (i.e that there is now a more noticeable difference) that would be interesting to know.

David Newman wrote on 6/4/2006, 8:35 PM

Defaulting to Medium over Large (or High) was a discision made to deal with slow PCs. Medium is very good, but not as good as Large/High, which is in turn not as good as the three additional levels offered in Prospect HD (High Optimized, FilmScan 1 and FilmScan 2.) However there are diminishing returns. If medium works for you, you should stick with it as the disk space is smaller and editing performance a little higher. I use medium on projects that I only intend for DVD output -- which is a lot of the time. For all other projects I use High, or on Prospect HD go for "FilmScan 1". However even the quality test we did (http://www.cineform.com/technology/HDVQualityAnalysis051011/HDVQualityAnalysis051011.htm) uses medium -- CineForm in High is even better than that quality analysis (High wasn't available in Vegas at the time of that test.)

David Newman
CTO, CineForm

malowz wrote on 6/4/2006, 9:42 PM

im converting with avisynth-avs2avi using rgb24 colorspace
> Converting what to what?
hdv transport stream, using avisynth frameserving, and using avs2avi, a CLI program to open the frameserve file, and compress using a VFW codec (CFHD in this case) - using using RGB24 as color space to feed video to encoder.

the file show in vegas as 24b
> What does this mean?
24 bits.
http://en.wikipedia.org/wiki/RGB#24-bit_representation

when render some effect, the preview file as 32b
>Sorry, but this is nearly impossible to follow. Only thing I can guess, is that if you even touch an avi then smart rendering won't help.
this is not the point. the pre-render file shows as 32bits, then vegas would re-render the part thas was previously rendered. (render twice)

Laurence wrote on 6/5/2006, 12:14 AM

It wasn't that long ago that the following was posted on the Cineform site:
_______________________________________________________________

Cineform generally recommends you use the Mid range file size when doing m2t to CFHD conversions. This is for a few reasons:

1. Quality gained by changing from medium to high file size is minimal. It is possible you wont even see the change in quality.

2. The difference in file size is rather large. We recommend the mid range not only because of disk storage considerations, but also because of bandwidth considerations. The more data that has to be moved and processed, the less RT performance you will get while editing in an Aspect HD RT project. For example, with a 3 GHz HT P4, and 1 GB of dual channel DDR @ 800 MHz, you may be able to play 4 streams of video in real-time. However, if that video is created using the large file size it may cut that performance by 1/3 or even 1/2 without noticably changing the quality of the video.
_______________________________________________________________

David Newman wrote on 6/5/2006, 7:35 AM

Now we have dual-core PC everywhere why not use the best quality. :)

Ben1000 wrote on 6/5/2006, 11:27 AM

Howdy...

For anyone interested, we produced this week's version of our podcast using the new 3.0 codec, also using the 'deinterlace' setting to convert our Z1 footage to progressive...

http://www.neo-fight.tv

Best,

Benjamin

----------------------------------------------------------
http://www.neo-fight.tv [The "Techno-Debate" Video Podcast]

bruceo wrote on 7/20/2006, 8:17 PM

On the shortened captured videos do you notice the audio going out of synch somewhere in the video as well?

bruceo wrote on 7/20/2006, 8:18 PM

Yes that staement is very misleading. One of the main reasons I upgraded.