I'm still confused on burning at HQ vs SP, etc with VS9.

Trevor Andrew · Post by **Trevor Andrew** » Thu Aug 24, 2006 12:01 pm

Hi
Daniel

If my reply came across as aggressed or challenged, I apologise that was not my intension.
A bit of banter may be.

I was just interested in to how long the burn actually took from hitting the ‘Burn’ button.

If it’s a long time then rendering may be taking place, not to be expected if the properties are the same.

I was expecting the OP to reply ‘mine takes hours’

All the Best

Trevor

Post by **Ken Berry** » Thu Aug 24, 2006 12:07 pm

Daniel -- I think you may have misunderstood Trevor's original post. He didn't say it took 30 minutes 15. In fact, he didn't properly punctuate the sentence (sorry Trevor!!

) What he actually said, with punctuation, was 'The burner operation should take about 30 minutes -- 15 [minutes] to make the menus and 15 [minutes] to burn.'

daniel · Post by **daniel** » Thu Aug 24, 2006 12:16 pm

maddrummer3301 wrote: In other words
Ulead 70% = 8 Motion Pixel Depth Search
ATI....100% = 8 Motion Pixel Depth Search

...and as a comparison point, what is 100%?

I am always using 100% for slide shows and felt it made a subjective difference with pan/zooms, but have been curious as to what effect it could technically have.

Does not motion pixel search depths influence more output size or bit-rate than quality? If the search fails, I guess they encode the difference on a discrete basis while a movement would be defined with less bytes.

On the other side, with my has-been computer (Trevor could disagree) I must say I don't really feel the difference in encoding speed between 70 and 100. Someone really timed it?
Or is the encoder giving up after so many loops, meaning a faster machine has better results?
This is what happens for audio, the inner loop (rate loop) just times out and then they proceed to the outer (noise control) loop.

Trevor Andrew · Post by **Trevor Andrew** » Thu Aug 24, 2006 12:18 pm

E by gum lad, you must think I am reight daft, ... must be my yorkshire-dialect

Trevor

GeorgeW · Post by **GeorgeW** » Thu Aug 24, 2006 12:31 pm

Ken Berry wrote:Daniel -- I think you may have misunderstood Trevor's original post. He didn't say it took 30 minutes 15. In fact, he didn't properly punctuate the sentence (sorry Trevor!! ) What he actually said, with punctuation, was 'The burner operation should take about 30 minutes -- 15 [minutes] to make the menus and 15 [minutes] to burn.'

It's interesting how different people will interpret the same words differently. I read Trevor's comment, and thought 15 [minutes] to make the menus and 15 [minutes] to burn (so I think that was in line with his intentions).

However, the first thing that came to my mind was that the 15 [minutes] for the menus can really vary depending on the items that Daniel listed. The default settings in VS10 are to have motion menus and menu transitions. So depending on the person's computer equipment and menu complexity (as Daniel said), the menu rendering can take a while to process (more than 15 minutes). And that's not including the time to "customize" the menus.

When we post "estimated" times, we should also try to include key "reference" points. Like 15 minutes to burn a full dvd5 disc at 4x, or 15 minutes to render the menus (with a P4/AMD xxxx processor, and only a couple of menus / chapter points with little or no motion/transitions). Otherwise, someone with a slower machine and a few menus/chapter points wil wonder why theirs takes longer to render the menus...

Regards,
George

daniel · Post by **daniel** » Thu Aug 24, 2006 12:32 pm

Ken Berry wrote:Daniel -- I think you may have misunderstood Trevor's original post.

Oh thanks Ken , It never occured to me. Now it looks SO obvious.

I'm french-speaking and french is maybe more sensitive to punctuation (you know that!), because badly punctuated phrases can easily become incomprehensible, and usually provide for really funny concepts.
But I do know english people take vast liberties with commas. I just keep forgetting to include that in the parser.

Well, I must say it's much less funny as you write it Ken.

daniel · Post by **daniel** » Thu Aug 24, 2006 12:38 pm

trevor andrew wrote:E by gum lad, you must think I am reight daft, ... must be my yorkshire-dialect

Trevor

Don't be sad, it's better to be misunderstood, sometimes,
by continentals than to be really grumpy like some people from Birmingham you meet around here.

maddrummer3301 · Post by **maddrummer3301** » Thu Aug 24, 2006 1:28 pm

...and as a comparison point, what is 100%?
I am always using 100% for slide shows and felt it made a subjective difference with pan/zooms, but have been curious as to what effect it could technically have.
Does not motion pixel search depths influence more output size or bit-rate than quality? If the search fails, I guess they encode the difference on a discrete basis while a movement would be defined with less bytes.

If you have any MainConcept Programs you will find that ulead is using the same encoder so one can compare the settings against each other.
Only my opinion but I think ulead lets you set a higher compression than most programs. If you have the Advance=1 pretty sure 70%= a setting of 8 and 100%= a setting of 11. You can check that out yourself.

Can I edit Mpeg2 files?

daniel · Post by **daniel** » Thu Aug 24, 2006 1:42 pm

maddrummer3301. wrote:
Can I edit Mpeg2 files? :P

That's an easy one. Yes, but:

- you have to say "pretty please"
- you need to de-interlace then re-interlace with the opposite field order
- you need to select a different bit rate to avoid this pesky smart render
- you must do the last rendering below 50% quality to take it easy on the computer otherwise it lasts more than the canonical 30 min 15 including menu.

What did I win?