Anyone use K3B to rip/encode

[Mr_Roboto]

I'm using K3B on Linux to rip/encode DVDs. I want to bump the aggressiveness of it and thread count (it seems to only use 2/6 of my cores.) I'm wondering if anyone has done this before, as transcode doesn't seem to be listed in the external programs you can pass parameters to. Thoughts?

Click to read more...

 

[Fish]

Never used K3B. Ive used Handbrake to rip and encode. Easy enough.

 

[Mr_Roboto]

Never used K3B. Ive used Handbrake to rip and encode. Easy enough.

I'm just trying to eek every bit of performance out of it. The rip seems to be 30ish minutes by its self using dvd::rip with a bit less for encode, so I think I'm going to wind up stuck about where I am unforunately.

In other news, I'm about out of disk space. Maybe this wasn't such a great thing to discover, 500G of mirrored storage lasted me a long time till I started ripping DVDs

 

[Fish]

IIRC even doing a twice over with handbrake was about 20 minutes. I know [MENTION=1317]ThirdgenTa[/MENTION] and I have gone back and forth over quality by encoding and ripping.

Handbrake will straight up rip and encode DVDs at the same time.

 

[Thirdgen89GTA]

While handbrake technically transcodes in most cases they call it encoding.

Handbrake is the gold standard right now.

500 isn't enough at all. You want to have about 4tb.

Check out the 10bit nightly builds of handbrake h265. Very high efficiency. But you'll need more cpu time.

 

[Mr_Roboto]

While handbrake technically transcodes in most cases they call it encoding.

Handbrake is the gold standard right now.

500 isn't enough at all. You want to have about 4tb.

Check out the 10bit nightly builds of handbrake h265. Very high efficiency. But you'll need more cpu time.

Is it clock or core sensitive? I've got a Phenom II 1055T (6 core) and it seems like what I'm using now is built around dual cores.

 

[Thirdgen89GTA]

Is it clock or core sensitive? I've got a Phenom II 1055T (6 core) and it seems like what I'm using now is built around dual cores.

The more cores and more speed you have the happier it gets.

 

[Thirdgen89GTA]

Just as an FYI, H265 takes about twice as long to encode as H264, but file sizes are on average about 30%-40% smaller, some as much as 50% smaller.

H265 shows much more benefit with 1080p and 4k content. For 480p DVD stuff, it doesn't have too much improvement over H264.