Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.mac.system > #109977 > unrolled thread

trimming mkv files?

Started byWilliam Hanna <bill@invalid.invalid>
First post2017-11-10 21:48 -0800
Last post2017-11-15 17:48 +0000
Articles 18 — 7 participants

Back to article view | Back to comp.sys.mac.system


Contents

  trimming mkv files? William Hanna <bill@invalid.invalid> - 2017-11-10 21:48 -0800
    Re: trimming mkv files? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2017-11-11 06:18 -0500
      Re: trimming mkv files? William Hanna <bill@invalid.invalid> - 2017-11-11 13:11 -0800
    Re: trimming mkv files? Alan Browne <alan.browne@freelunchvideotron.ca> - 2017-11-11 12:36 -0500
      Re: trimming mkv files? Your Name <YourName@YourISP.com> - 2017-11-12 09:32 +1300
        Re: trimming mkv files? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2017-11-11 16:16 -0500
          Re: trimming mkv files? Alan Browne <alan.browne@freelunchvideotron.ca> - 2017-11-11 18:42 -0500
          Re: trimming mkv files? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-11-12 03:40 +0000
        Re: trimming mkv files? Alan Browne <alan.browne@freelunchvideotron.ca> - 2017-11-11 18:41 -0500
          Re: trimming mkv files? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-11-12 03:41 +0000
            Re: trimming mkv files? Alrescha <alrescha@gmail.com> - 2017-11-12 19:30 +0000
    Re: trimming mkv files? William Hanna <bill@invalid.invalid> - 2017-11-12 15:34 -0800
      Re: trimming mkv files? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2017-11-12 22:26 -0500
        Re: trimming mkv files? William Hanna <bill@invalid.invalid> - 2017-11-12 21:37 -0800
          Re: trimming mkv files? Your Name <YourName@YourISP.com> - 2017-11-13 19:12 +1300
            Re: trimming mkv files? William Hanna <bill@invalid.invalid> - 2017-11-13 11:57 -0800
            Re: trimming mkv files? heron stone <heron@invalid.invalid> - 2017-11-14 20:41 -0800
              Re: trimming mkv files? Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-11-15 17:48 +0000

#109977 — trimming mkv files?

FromWilliam Hanna <bill@invalid.invalid>
Date2017-11-10 21:48 -0800
Subjecttrimming mkv files?
Message-ID<101120172148407427%bill@invalid.invalid>
i want to do some tests of various compression settings 
   when converting video files to h265
using Super265 is time-consuming... 
   up to two hours for larger/longer files

so i'd like to take a really good looking mkv
   and trim it to about 3 minutes 
   and do the tests on that

? what do i need to do that


thanks

[toc] | [next] | [standalone]


#109978

FromJF Mezei <jfmezei.spamnot@vaxination.ca>
Date2017-11-11 06:18 -0500
Message-ID<5a06dc7e$0$5757$b1db1813$5890f3ee@news.astraweb.com>
In reply to#109977
On 2017-11-11 00:48, William Hanna wrote:
> i want to do some tests of various compression settings 
>    when converting video files to h265
> using Super265 is time-consuming... 



Handbrake is able to extract/convert portions of a video.

At top middle, the "Chapters" button can be changed to seconds at which
point you can choose the range of seconds in the original you wish to be
copied to the output.

And Handbrake can do H.265 for you.

[toc] | [prev] | [next] | [standalone]


#109981

FromWilliam Hanna <bill@invalid.invalid>
Date2017-11-11 13:11 -0800
Message-ID<111120171311209891%bill@invalid.invalid>
In reply to#109978
thanks you all

i'll give Handbrake a try



In article <5a06dc7e$0$5757$b1db1813$5890f3ee@news.astraweb.com>, JF
Mezei <jfmezei.spamnot@vaxination.ca> wrote:

> On 2017-11-11 00:48, William Hanna wrote:
> > i want to do some tests of various compression settings 
> >    when converting video files to h265
> > using Super265 is time-consuming... 
> 
> 
> 
> Handbrake is able to extract/convert portions of a video.
> 
> At top middle, the "Chapters" button can be changed to seconds at which
> point you can choose the range of seconds in the original you wish to be
> copied to the output.
> 
> And Handbrake can do H.265 for you.

[toc] | [prev] | [next] | [standalone]


#109979

FromAlan Browne <alan.browne@freelunchvideotron.ca>
Date2017-11-11 12:36 -0500
Message-ID<e6GdnT7UjOO4qJrHnZ2dnUU7-SXNnZ2d@giganews.com>
In reply to#109977
On 2017-11-11 00:48, William Hanna wrote:
> i want to do some tests of various compression settings when
> converting video files to h265 using Super265 is time-consuming... up
> to two hours for larger/longer files
> 
> so i'd like to take a really good looking mkv and trim it to about 3
> minutes and do the tests on that
> 
> ? what do i need to do that

Handbrake.  However, note that the settings on Handbrake will affect the 
quality of the output segment unless carefully set so your short clip 
may not represent the original.

You could use Davinci resolve as well, but I'm not sure if it reads .MKV 
and again the settings in Davinci will affect the output clip.

[toc] | [prev] | [next] | [standalone]


#109980

FromYour Name <YourName@YourISP.com>
Date2017-11-12 09:32 +1300
Message-ID<ou7mo8$1iev$1@gioia.aioe.org>
In reply to#109979
On 2017-11-11 17:36:37 +0000, Alan Browne said:
> On 2017-11-11 00:48, William Hanna wrote:
>> i want to do some tests of various compression settings when
>> converting video files to h265 using Super265 is time-consuming... up
>> to two hours for larger/longer files
>> 
>> so i'd like to take a really good looking mkv and trim it to about 3
>> minutes and do the tests on that
>> 
>> ? what do i need to do that
> 
> Handbrake.  However, note that the settings on Handbrake will affect 
> the quality of the output segment unless carefully set so your short 
> clip may not represent the original.
> 
> You could use Davinci resolve as well, but I'm not sure if it reads 
> .MKV and again the settings in Davinci will affect the output clip.

Settings always affect the output ... that's what settings are there 
for. If they did affect the output, then there wouldn't be any need for 
settings at all.  ;-)

[toc] | [prev] | [next] | [standalone]


#109982

FromJF Mezei <jfmezei.spamnot@vaxination.ca>
Date2017-11-11 16:16 -0500
Message-ID<5a076898$0$40117$b1db1813$306e51c2@news.astraweb.com>
In reply to#109980
On 2017-11-11 15:32, Your Name wrote:

> Settings always affect the output ... that's what settings are there 
> for. If they did affect the output, then there wouldn't be any need for 
> settings at all.  ;-)


ffmpeg (the engine behind handbrake) has the -copy function which allows
you to copy a stream untouched (and you can specify to copy only a
portion of the source, but what is copied is copied without changes (but
that also means that the first portion may be incomplete image until the
next keyframe that has full image).


[toc] | [prev] | [next] | [standalone]


#109984

FromAlan Browne <alan.browne@freelunchvideotron.ca>
Date2017-11-11 18:42 -0500
Message-ID<Fa2dnY-gc6FGF5rHnZ2dnUU7-SmdnZ2d@giganews.com>
In reply to#109982
On 2017-11-11 16:16, JF Mezei wrote:
> 
> ffmpeg (the engine behind handbrake) has the -copy function which allows
> you to copy a stream untouched (and you can specify to copy only a
> portion of the source, but what is copied is copied without changes (but
> that also means that the first portion may be incomplete image until the
> next keyframe that has full image).

I'll keep that in mind.  So far I only use ffmpeg to convert video from 
the security camera when needed.

-- 
"My Twitter has become so powerful that
  I can actually make my enemies tell the truth."
..Donald Trump

[toc] | [prev] | [next] | [standalone]


#109985

FromLewis <g.kreme@gmail.com.dontsendmecopies>
Date2017-11-12 03:40 +0000
Message-ID<slrnp0fglf.1e9q.g.kreme@snow.local>
In reply to#109982
In message <5a076898$0$40117$b1db1813$306e51c2@news.astraweb.com> JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 2017-11-11 15:32, Your Name wrote:

>> Settings always affect the output ... that's what settings are there 
>> for. If they did affect the output, then there wouldn't be any need for 
>> settings at all.  ;-)


> ffmpeg (the engine behind handbrake) has the -copy function which allows
> you to copy a stream untouched (and you can specify to copy only a
> portion of the source, but what is copied is copied without changes (but
> that also means that the first portion may be incomplete image until the
> next keyframe that has full image).

IIRC,

ffmpeg -i original.mp4 -ss "00:25:13.00" -t "00:00:10.00" -c copy clip.mp4

Will create a 10 second clip starting at 25 minutes and 13 seconds and
will not re-encode it. In newer versions of ffmpeg, this would be
equivalent.

ffmpeg -i original.mp4 -ss "00:25:13.00" -to "00:25:23.00" -c copy clip.mp4

-- 
I get the feeling that some people's idea of heaven is an "I told you
so" T-shirt - mmalc

[toc] | [prev] | [next] | [standalone]


#109983

FromAlan Browne <alan.browne@freelunchvideotron.ca>
Date2017-11-11 18:41 -0500
Message-ID<Fa2dnYygc6ETF5rHnZ2dnUU7-SmdnZ2d@giganews.com>
In reply to#109980
On 2017-11-11 15:32, Your Name wrote:
> On 2017-11-11 17:36:37 +0000, Alan Browne said:
>> On 2017-11-11 00:48, William Hanna wrote:
>>> i want to do some tests of various compression settings when
>>> converting video files to h265 using Super265 is time-consuming... up
>>> to two hours for larger/longer files
>>>
>>> so i'd like to take a really good looking mkv and trim it to about 3
>>> minutes and do the tests on that
>>>
>>> ? what do i need to do that
>>
>> Handbrake.  However, note that the settings on Handbrake will affect 
>> the quality of the output segment unless carefully set so your short 
>> clip may not represent the original.
>>
>> You could use Davinci resolve as well, but I'm not sure if it reads 
>> .MKV and again the settings in Davinci will affect the output clip.
> 
> Settings always affect the output ... that's what settings are there 
> for. If they did affect the output, then there wouldn't be any need for 
> settings at all.  ;-)

Agreed and smiley noted.  To date I've yet to find a simple 1:1 setting 
that guarantees the o/p will be of the same quality as the input in 
either app.  So converting .mkv (that lost episode of "Mary Truehart, 
girl nymphomaniac" that I missed, for example) to .mp4 for the Apple TV 
is a PITA if I want perfection in conversion.

-- 
"My Twitter has become so powerful that
  I can actually make my enemies tell the truth."
..Donald Trump

[toc] | [prev] | [next] | [standalone]


#109986

FromLewis <g.kreme@gmail.com.dontsendmecopies>
Date2017-11-12 03:41 +0000
Message-ID<slrnp0fgnh.1e9q.g.kreme@snow.local>
In reply to#109983
In message <Fa2dnYygc6ETF5rHnZ2dnUU7-SmdnZ2d@giganews.com> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> On 2017-11-11 15:32, Your Name wrote:
>> On 2017-11-11 17:36:37 +0000, Alan Browne said:
>>> On 2017-11-11 00:48, William Hanna wrote:
>>>> i want to do some tests of various compression settings when
>>>> converting video files to h265 using Super265 is time-consuming... up
>>>> to two hours for larger/longer files
>>>>
>>>> so i'd like to take a really good looking mkv and trim it to about 3
>>>> minutes and do the tests on that
>>>>
>>>> ? what do i need to do that
>>>
>>> Handbrake.  However, note that the settings on Handbrake will affect 
>>> the quality of the output segment unless carefully set so your short 
>>> clip may not represent the original.
>>>
>>> You could use Davinci resolve as well, but I'm not sure if it reads 
>>> .MKV and again the settings in Davinci will affect the output clip.
>> 
>> Settings always affect the output ... that's what settings are there 
>> for. If they did affect the output, then there wouldn't be any need for 
>> settings at all.  ;-)

> Agreed and smiley noted.  To date I've yet to find a simple 1:1 setting 
> that guarantees the o/p will be of the same quality as the input in 
> either app.  So converting .mkv (that lost episode of "Mary Truehart, 
> girl nymphomaniac" that I missed, for example) to .mp4 for the Apple TV 
> is a PITA if I want perfection in conversion.

It is not a PITA, it is impossible. There is no such thing as perfection
when converting.

-- 
Supposing there was justice for all, after all? For every unheeded
beggar, every harsh word, every neglected duty, every slight... every
choice... Because that was the point, wasn't it? You had to choose. You
might be right, you might be wrong, but you had to choose, knowing that
the rightness or wrongness might never be clear or even that you were
deciding between two sorts of wrong, that there was no right anywhere.
And always, always, you did it by yourself. You were the one there, on
the edge, watching and listening. Never any tears, never any apology,
never any regrets... You saved all that up in a way that could be used
when needed. --Carpe Jugulum

[toc] | [prev] | [next] | [standalone]


#109993

FromAlrescha <alrescha@gmail.com>
Date2017-11-12 19:30 +0000
Message-ID<oua7g1$cad$1@dont-email.me>
In reply to#109986
Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:

> It is not a PITA, it is impossible. There is no such thing as perfection when converting.

Of course, which is why one remuxes for the Apple TV instead of converts. 
:-)

-- 
A.

[toc] | [prev] | [next] | [standalone]


#109997

FromWilliam Hanna <bill@invalid.invalid>
Date2017-11-12 15:34 -0800
Message-ID<121120171534123189%bill@invalid.invalid>
In reply to#109977
report on results...

i converted a 4.85 GB h264 movie to h265 
   using both Super265 and HandBrake

results:

   Super265 
   compression level 18
   size = 2.66 GB
   time = 72 minutes

   HandBrake
   compression level 18
   size = 1.86 GB
   time = 194 minutes

they look about the same 
   but the Super265 version
   might look a little better

and the time difference is significant

thanks for your input

[toc] | [prev] | [next] | [standalone]


#110006

FromJF Mezei <jfmezei.spamnot@vaxination.ca>
Date2017-11-12 22:26 -0500
Message-ID<5a0910c9$0$41278$b1db1813$f9722a78@news.astraweb.com>
In reply to#109997
On 2017-11-12 18:34, William Hanna wrote:

>    Super265 
>    compression level 18
>    size = 2.66 GB
>    time = 72 minutes
> 
>    HandBrake
>    compression level 18
>    size = 1.86 GB
>    time = 194 minutes


Did you have a 2 pass option with handbrake? This takes longer but
creates smaller files.

[toc] | [prev] | [next] | [standalone]


#110015

FromWilliam Hanna <bill@invalid.invalid>
Date2017-11-12 21:37 -0800
Message-ID<121120172137477990%bill@invalid.invalid>
In reply to#110006
> Did you have a 2 pass option with handbrake? This takes longer but
> creates smaller files.

i didn't set a 2-pass option 

and looking at it now, 
i don't even see that option

tell me more please

[toc] | [prev] | [next] | [standalone]


#110016

FromYour Name <YourName@YourISP.com>
Date2017-11-13 19:12 +1300
Message-ID<oubd3s$1p2b$1@gioia.aioe.org>
In reply to#110015
On 2017-11-13 05:37:47 +0000, William Hanna said:
>> 
>> Did you have a 2 pass option with handbrake? This takes longer but
>> creates smaller files.
> 
> i didn't set a 2-pass option
> 
> and looking at it now,
> i don't even see that option
> 
> tell me more please

The tick box for the "2-pass encoding" option is under the Video 
Quality settings (Video tab) when using an Average Bitrate. According 
to the Handbrake forums:

    The reason for doing a two-pass encode is (usually) to hit
    a target bit rate. When the bit rate isn't a limiting factor,
    using 1 pass and constant quality would be significantly
    faster than wondering how to save a first pass result.


[toc] | [prev] | [next] | [standalone]


#110030

FromWilliam Hanna <bill@invalid.invalid>
Date2017-11-13 11:57 -0800
Message-ID<131120171157295741%bill@invalid.invalid>
In reply to#110016
thanks

2-pass was selected

i'll try again without it and see what happens





In article <oubd3s$1p2b$1@gioia.aioe.org>, Your Name
<YourName@YourISP.com> wrote:

> On 2017-11-13 05:37:47 +0000, William Hanna said:
> >> 
> >> Did you have a 2 pass option with handbrake? This takes longer but
> >> creates smaller files.
> > 
> > i didn't set a 2-pass option
> > 
> > and looking at it now,
> > i don't even see that option
> > 
> > tell me more please
> 
> The tick box for the "2-pass encoding" option is under the Video 
> Quality settings (Video tab) when using an Average Bitrate. According 
> to the Handbrake forums:
> 
>     The reason for doing a two-pass encode is (usually) to hit
>     a target bit rate. When the bit rate isn't a limiting factor,
>     using 1 pass and constant quality would be significantly
>     faster than wondering how to save a first pass result.
> 
> 
>

[toc] | [prev] | [next] | [standalone]


#110056

Fromheron stone <heron@invalid.invalid>
Date2017-11-14 20:41 -0800
Message-ID<141120172041038713%heron@invalid.invalid>
In reply to#110016
ok...
i reconverted a file without 2-pass checked

HandBrake is still REALLY slow
i was converting a 4.7 GB mkv to h265 at level 18
and i quit it after 3 hours and it was only 67% thru

Super265 finished it in 1 hr and 40 minutes

[toc] | [prev] | [next] | [standalone]


#110060

FromLewis <g.kreme@gmail.com.dontsendmecopies>
Date2017-11-15 17:48 +0000
Message-ID<slrnp0ovfj.1c3b.g.kreme@snow.local>
In reply to#110056
In message <141120172041038713%heron@invalid.invalid> heron stone <heron@invalid.invalid> wrote:
> ok...
> i reconverted a file without 2-pass checked

> HandBrake is still REALLY slow
> i was converting a 4.7 GB mkv to h265 at level 18
> and i quit it after 3 hours and it was only 67% thru

> Super265 finished it in 1 hr and 40 minutes

You changed the level. You previously said you set the level for Super265
at 20.

(I don't care, I'm not using h.265 until I have hardware decoders for it
built-in to my Synology, and I am unlikely to replace my synology in the
next 5 years).

-- 
Q is for QUENTIN who sank in the mire
R is for RHODA consumed by a fire

[toc] | [prev] | [standalone]


Back to top | Article view | comp.sys.mac.system


csiph-web