My wife bought a Blu-ray disk at a library sale, and now I need to
transcode
its contents and stick them on the media server so we can watch it. So, I did the naïve thing and tried to read it using Handbrake 1.6.1. It read titles 23 (5:00) and 25 (0:47). Obviously something's not right. DVDs work
properly, but this is the first BD I've tried. What do I need to add to make it work? Thanks.
Hi,
Am 16.11.2024 um 18:36 schrieb Eben King:
My wife bought a Blu-ray disk at a library sale, and now I need to
transcode its contents and stick them on the media server so we can
watch it. So, I did the naïve thing and tried to read it using
Handbrake 1.6.1. It read titles 23 (5:00) and 25 (0:47). Obviously
something's not right. DVDs work properly, but this is the first BD
I've tried. What do I need to add to make it work? Thanks.
Digital Restrictions Management is bad.
Plan to spens ome time, and start at https://forum.makemkv.com/forum/viewforum.php?f=3 if you like!
On Sat, Nov 16, 2024 at 5:07 PM Arno Lehmann <[email protected]> wrote:
Hi,
Am 16.11.2024 um 18:36 schrieb Eben King:
My wife bought a Blu-ray disk at a library sale, and now I need to
transcode its contents and stick them on the media server so we can
watch it. So, I did the naïve thing and tried to read it using
Handbrake 1.6.1. It read titles 23 (5:00) and 25 (0:47). Obviously
something's not right. DVDs work properly, but this is the first BD
I've tried. What do I need to add to make it work? Thanks.
Did you try playing the BD with VLC?
eben@cerberus:~$ vlc /dev/sr0
VLC media player 3.0.21 Vetinari (revision 3.0.21-0-gdd8bfdbabe8) keydbcfg.c:701: No valid AACS configuration files found
aacs.c:121: No usable AACS libraries found!
dec.c:197: aacs_open() failed: -2!
bdj.c:614: libbluray-j2se-1.3.4.jar not found.
bdj.c:801: BD-J check: Failed to load libbluray.jar
bdj.c:614: libbluray-j2se-1.3.4.jar not found.
bdj.c:801: BD-J check: Failed to load libbluray.jar
keydbcfg.c:701: No valid AACS configuration files found
aacs.c:121: No usable AACS libraries found!
dec.c:197: aacs_open() failed: -2!
bdj.c:614: libbluray-j2se-1.3.4.jar not found.
bdj.c:801: BD-J check: Failed to load libbluray.jar
bdj.c:614: libbluray-j2se-1.3.4.jar not found.
bdj.c:801: BD-J check: Failed to load libbluray.jar
You may have to install libbluray2 and gstreamer1.0-plugins-ugly.
Hi,sure !
Am 16.11.2024 um 18:36 schrieb Eben King:
My wife bought a Blu-ray disk at a library sale, and now I need to
transcode
its contents and stick them on the media server so we can watch it.
So, I
did the naïve thing and tried to read it using Handbrake 1.6.1. It read >> titles 23 (5:00) and 25 (0:47). Obviously something's not right.
DVDs work
properly, but this is the first BD I've tried. What do I need to add to
make it work? Thanks.
Digital Restrictions Management is bad.
I know of no real Open Source solution to that problem, but have very
good results using MakeMKV under Windows. It should be possible to build
that for Linux, but I never tried.
Plan to spens ome time, and start at https://forum.makemkv.com/forum/ viewforum.php?f=3 if you like!
note that vlc on debian reads and play BlueRay disks just fine :) (just be sure sure that libluray is installed)
--
Hi,
On Sun Nov 17, 2024 at 7:05 PM GMT, eben wrote:
--
Just to point out that the mail signature separator is '-- ', i.e. with
a suffixed ' ' character. Without it, Mail User Agent programs may not recognise your signature as such.
(original email sent 19 Nov 2024 at 10:02)
That is what I see in the message to which you replied. See the <1k attachment. This message also has a space. Is that not what you see?
On 11/19/24 05:19, Jonathan Dowland wrote:No. This is how the separator line looks like in your message's (quoted printable) source:
Hi,
On Sun Nov 17, 2024 at 7:05 PM GMT, eben wrote:
--
Just to point out that the mail signature separator is '-- ', i.e. with
a suffixed ' ' character. Without it, Mail User Agent programs may not
recognise your signature as such.
That is what I see in the message to which you replied. See the <1k attachment. This message also has a space. Is that not what you see?
That is what I see in the message to which you replied. See the <1k attachment. This message also has a space. Is that not what you see?
On Tue, 19 Nov 2024 10:02:59 -0500
[email protected] wrote:
Hello [email protected],
That is what I see in the message to which you replied. See the <1k
attachment. This message also has a space. Is that not what you see?
I see what Jonathan sees.
Your sig separator arrives here as "--". If it leaves you as "-- ",
which it seems to be based on your attached image, I'm not sure what's happening.
On 11/19/24 10:31, Brad Rogers wrote:
On Tue, 19 Nov 2024 10:02:59 -0500
[email protected] wrote:
Hello [email protected],
That is what I see in the message to which you replied. See the <1k attachment. This message also has a space. Is that not what you see?
I see what Jonathan sees.
Your sig separator arrives here as "--". If it leaves you as "-- ",
which it seems to be based on your attached image, I'm not sure what's happening.
I guess until I find a smoking gun I'll just delete the signature and its separator when sending to this list.
On Tue, Nov 19, 2024 at 07:41:25PM -0500, [email protected] wrote:
On 11/19/24 10:31, Brad Rogers wrote:
On Tue, 19 Nov 2024 10:02:59 -0500
[email protected] wrote:
Hello [email protected],
That is what I see in the message to which you replied. See the <1k
attachment. This message also has a space. Is that not what you see?
I see what Jonathan sees.
Your sig separator arrives here as "--". If it leaves you as "-- ",
which it seems to be based on your attached image, I'm not sure what's
happening.
I guess until I find a smoking gun I'll just delete the signature and its
separator when sending to this list.
How do you add tyour sig? "By hand"?
Note that Thunderbird seems to have a
way to add the signature itself, and then it adds the separator (by default).
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
On Wed, Nov 20, 2024 at 10:13:20 -0500, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
In the message I received, none of these lines have any trailing
spaces.
If I had to guess, I would guess that Thunderbird is composing HTML
email, and then translating it to plain text, with trailing spaces
being lost during that translation. Including the trailing space on
the signature separator.
Just to double-check,
On Tue 19 Nov 2024 at 19:41:25 (-0500), eben@… wrote:
On 11/19/24 10:31, Brad Rogers wrote:
Your sig separator arrives here as "--". If it leaves you as "-- ",
which it seems to be based on your attached image, I'm not sure what's
happening.
I guess until I find a smoking gun I'll just delete the signature and its
separator when sending to this list.
So, naturally you use an editor to compose your posts.
On Tue 19 Nov 2024 at 19:41:25 (-0500), eben@… wrote:
On 11/19/24 10:31, Brad Rogers wrote:
On Tue, 19 Nov 2024 10:02:59 -0500 eben@… wrote:
That is what I see in the message to which you replied. See the <1k attachment. This message also has a space. Is that not what you see?
I see what Jonathan sees.
Your sig separator arrives here as "--". If it leaves you as "-- ", which it seems to be based on your attached image, I'm not sure what's happening.
I guess until I find a smoking gun I'll just delete the signature and its separator when sending to this list.
So, naturally you use an editor to compose your posts. Have you
set it up to remove trailing spaces from files when it saves them?
On 11/20/24 10:20, Greg Wooledge wrote:
If I had to guess, I would guess that Thunderbird is composing
HTML email, and then translating it to plain text, with trailing
spaces being lost during that translation. Including the trailing
space on the signature separator.
Makes sense. Does anyone using Thunderbird _not_ get trailing
spaces stripped, or is it just me?
On 2024-11-20 at 11:24, [email protected] wrote:
On 11/20/24 10:20, Greg Wooledge wrote:
If I had to guess, I would guess that Thunderbird is composing
HTML email, and then translating it to plain text, with trailing
spaces being lost during that translation. Including the trailing
space on the signature separator.
Makes sense. Does anyone using Thunderbird _not_ get trailing
spaces stripped, or is it just me?
I don't (see signature below), but it may be worth noting that I am
using an *ancient* version of Thunderbird, because of UI/UX changes in
the meanwhile which I'm not willing to tolerate. It's far from
impossible that changes in more recent Thunderbird versions might have
broken this.
Anyone know how to
get a pure text version, if such a thing exists?
On 11/20/24 11:37, The Wanderer wrote:
On 2024-11-20 at 11:24, [email protected] wrote:
On 11/20/24 10:20, Greg Wooledge wrote:
If I had to guess, I would guess that Thunderbird is composing
HTML email, and then translating it to plain text, with trailing
spaces being lost during that translation. Including the trailing space on the signature separator.
Makes sense. Does anyone using Thunderbird _not_ get trailing
spaces stripped, or is it just me?
I don't (see signature below), but it may be worth noting that I am
using an *ancient* version of Thunderbird, because of UI/UX changes in
the meanwhile which I'm not willing to tolerate. It's far from
impossible that changes in more recent Thunderbird versions might have broken this.
This is true. What version?
BTW I received your separator as "--=20". But that's once saved as eml.
Onscreen it looks fine, and the signature is greyed out. Anyone know how to get a pure text version, if such a thing exists?
On 11/20/24 10:20, Greg Wooledge wrote:
On Wed, Nov 20, 2024 at 10:13:20 -0500, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
In the message I received, none of these lines have any trailing
spaces.
Dangit.
On 11/20/24 11:24, [email protected] wrote:
On 11/20/24 10:20, Greg Wooledge wrote:
On Wed, Nov 20, 2024 at 10:13:20 -0500, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
In the message I received, none of these lines have any trailing
spaces.
Dangit.
What folks don't seem to get, is that the character preceding the "-- "
needs to be a line feed, as does the character /after/ the space, IOW,
on a line by itself.
[...]
Cheers, Gene Heskett, CET.
Which is what I am sending from latest t-bird in what I think is plain text, as below, and it works, my too long comment is not greyed out in the incoming echo from the listserver. You should see it incoming but not in a reply you make that quotes mymsg for context. Your agent is supposed to throw it away, not retransmitting it again and again.
Cheers, Gene Heskett, CET.
On 21/11/2024 05:31, gene heskett wrote:
Which is what I am sending from latest t-bird in what I think is plain
text, as below, and it works, my too long comment is not greyed out in
the incoming echo from the listserver. You should see it incoming but
not in a reply you make that quotes my msg for context. Your agent is
supposed to throw it away, not retransmitting it again and again.
Cheers, Gene Heskett, CET.
My TB is behaving exactly like yours in this respect. Your sig is shown greyed-out and is automatically removed when I reply to your post (like this).
Meanwhile my sig is correctly added and (I've just checked) sent to
another account's inbox with the trailing space after -- intact.
So nothing here to blame on TB, at least for mail being sent between Thunderbirds.
On 11/20/24 23:46, John Crawley wrote:And that one above did nothing because it was mid-line, w/o the /r-- /r
On 21/11/2024 05:31, gene heskett wrote:Which is how it should be.
Which is what I am sending from latest t-bird in what I think is
plain text, as below, and it works, my too long comment is not greyed
out in the incoming echo from the listserver. You should see it
incoming but not in a reply you make that quotes my msg for context.
Your agent is supposed to throw it away, not retransmitting it again
and again.
Cheers, Gene Heskett, CET.
My TB is behaving exactly like yours in this respect. Your sig is
shown greyed-out and is automatically removed when I reply to your
post (like this).
Meanwhile my sig is correctly added and (I've just checked) sent to
another account's inbox with the trailing space after -- intact.
So nothing here to blame on TB, at least for mail being sent betweenThat (sigh) was my point. That doesn't affect the dozens of miss-
Thunderbirds.
configured email agents here that violate those SOP's for text emails.
<y list of groups I sort email into is about 2 screens tall but tirds
filters for debian-user still miss-sorts them, a lot. Some sent to debian-user, some send to the full fqdn, And it still leaves about 10-20
an hour in the inbox or in junk with a perfectly good address. Which
filter rule is miss-firing is a puzzle w/o enough clues to solve.
Cheers, Gene Heskett, CET.
That doesn't affect the dozens of miss-configured email agents here that violate those SOP's for text emails. <y list of groups I sort email into is about 2 screens tall but tirds filters for debian-user still miss-sorts them, a lot. Some sent todebian-user, some send to the full fqdn, And it still leaves about 10-20 an hour in the inbox or in junk with a perfectly good address. Which filter rule is miss-firing is a puzzle w/o enough clues to solve.
On 11/20/24 15:16, gene heskett wrote:
On 11/20/24 11:24, [email protected] wrote:
On 11/20/24 10:20, Greg Wooledge wrote:
On Wed, Nov 20, 2024 at 10:13:20 -0500, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
In the message I received, none of these lines have any trailing
spaces.
Dangit.
What folks don't seem to get, is that the character preceding the "-- "
needs to be a line feed, as does the character /after/ the space, IOW, on
a line by itself.
Which is what I am sending from latest t-bird in what I think is plain text, as below, and it works, my too long comment is not greyed out in the
incoming echo from the listserver. You should see it incoming but not in a reply you make that quotes my msg for context. Your agent is supposed to throw it away, not retransmitting it again and again.
On 11/20/24 15:31, gene heskett wrote:
On 11/20/24 15:16, gene heskett wrote:
On 11/20/24 11:24, [email protected] wrote:
On 11/20/24 10:20, Greg Wooledge wrote:
On Wed, Nov 20, 2024 at 10:13:20 -0500, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
In the message I received, none of these lines have any trailing spaces.
Dangit.
What folks don't seem to get, is that the character preceding the "-- " needs to be a line feed, as does the character /after/ the space, IOW, on a line by itself.
Which is what I am sending from latest t-bird in what I think is plain text,
as below, and it works, my too long comment is not greyed out in the incoming echo from the listserver. You should see it incoming but not in a reply you make that quotes my msg for context. Your agent is supposed to throw it away, not retransmitting it again and again.
Your sig separator arrived as "-- " not "--=20". Why the difference?
Also, yours works and mine doesn't, and we're both using a recent Tbird.
What could we be doing differently?
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
On 11/20/24 10:13, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
OK, I changed "mail.html_compose" from true to false. Now to see if it makes a difference:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
OK, I changed "mail.html_compose" from true to false. Now to see if it makes a difference:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
On 11/21/24 11:07, [email protected] wrote:
On 11/20/24 10:13, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
OK, I changed "mail.html_compose" from true to false. Now to see if it
makes a difference:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
Now I changed "mailnews.send_plaintext_flowed" from true to false.
This is a long line that is more than seventy-two characters that should end with a space. It is wrapped on my end.
This is a long line that is more than seventy-two characters that should end with two spaces. It is also wrapped on my end.
The =20 tells me its been converted to html style encoding some where.
On 11/20/24 15:31, gene heskett wrote:
On 11/20/24 15:16, gene heskett wrote:
On 11/20/24 11:24, [email protected] wrote:
On 11/20/24 10:20, Greg Wooledge wrote:
On Wed, Nov 20, 2024 at 10:13:20 -0500, [email protected] wrote:
Just for kicks:
This line has no trailing spaces.
This line has one trailing space.
This line has two trailing spaces.
In the message I received, none of these lines have any trailing
spaces.
Dangit.
What folks don't seem to get, is that the character preceding the "-- "
needs to be a line feed, as does the character /after/ the space,
IOW, on
a line by itself.
Which is what I am sending from latest t-bird in what I think is plain
text,
as below, and it works, my too long comment is not greyed out in the
incoming echo from the listserver. You should see it incoming but not
in a
reply you make that quotes my msg for context. Your agent is supposed to
throw it away, not retransmitting it again and again.
Your sig separator arrived as "-- " not "--=20". Why the difference?
Also, yours works and mine doesn't, and we're both using a recent Tbird.
What could we be doing differently?
.
On Thu, Nov 21, 2024 at 18:32:38 -0500, gene heskett wrote:And I learn something Greg, thanks. Now all I have to do is remember it,
The =20 tells me its been converted to html style encoding some where.
No, =20 is "quoted printable" encoding. It's extremely common for
email; it can be used whenever the source content is HTML or plain text
or a calendar invitation or any other textual material which might
not fit within the 7-bit ASCII encoding.
If the message were HTML encoded, you would have seen %20, not =20.
.
But can I ask you why you stopped using f=f when you changed address.
Was it because you're now using quoted-printable for some reason,
rather than 8bit.
And perhaps I ought not to ask why the paragraph above is right-justified.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 164:26:24 |
| Calls: | 12,095 |
| Calls today: | 3 |
| Files: | 15,000 |
| Messages: | 6,517,797 |