.mp4 metadata editor?

"J. P. Gilliver (John)" wrote

| Since VLC on my system seems to have lost the ability to add anything in
| the Comment field of mp4 files (probably other fields too), anyone care
| to suggest something that can?
|

In case you or anyone else is still interested:

https://www.jsware.net/jsware/scrfiles.php5#mded

Pretty simple. You need to download ffmpeg.exe.
The download here is an HTA utility that uses ffmpeg.
On 32-bit Windows there's also an option to drop
files into the window. It calls ffmpeg to extract tags
and loads up to 9 that ffmpeg writes to a file. Then
the utility can be used to add/edit/remove any of the
tags. It rewrites the file and tells ffmpeg to load it.

That's it. Most of it is ffmpeg. The utility is just an
HTA that makes the job simple, automating the
command line and the parsing/editing of the tags
file. There are links included to get ffmpeg for
XP/32-bit or Win64.

I actually stopped using VLC on my WinXP system.
It supposedly supports XP but later versions started
acting funky. I found Media Player Classic and find
that's very solid, even though the last version wwas more
than 3 years ago.

On Wed, 17 Feb 2021 at 17:21:59, Mayayana
wrote (my responses usually follow points raised):
"J. P. Gilliver (John)" wrote

| Since VLC on my system seems to have lost the ability to add anything in
| the Comment field of mp4 files (probably other fields too), anyone care
| to suggest something that can?
|

In case you or anyone else is still interested:

Well, going back to VLC version ....11 (from ....12) solved the problem,
but ...

https://www.jsware.net/jsware/scrfiles.php5#mded

Pretty simple. You need to download ffmpeg.exe.
The download here is an HTA utility that uses ffmpeg.
On 32-bit Windows there's also an option to drop
files into the window. It calls ffmpeg to extract tags
and loads up to 9 that ffmpeg writes to a file. Then
the utility can be used to add/edit/remove any of the
tags. It rewrites the file and tells ffmpeg to load it.

That's it. Most of it is ffmpeg. The utility is just an
HTA that makes the job simple, automating the
command line and the parsing/editing of the tags
file. There are links included to get ffmpeg for
XP/32-bit or Win64.

.... looks the usual workmanlike jsware product. I might try it on the
small number of video files VLC can't edit the metadata on (the ones
where the playing _doesn't_ freeze after I've tried editing metadata [if
it _does_ freeze, I usually know the editing has succeeded]).

I actually stopped using VLC on my WinXP system.
It supposedly supports XP but later versions started
acting funky. I found Media Player Classic and find
that's very solid, even though the last version wwas more
than 3 years ago.


I fear I'm probably stuck on 7 now - I suspect I've made enough little
tweaks that I'd find it a little tedious to go back to XP now. Though I
expect to stay with 7 even longer than I did with XP, because of the
sea-change involved with 10 (and the suspicion that 32-bit 10 will be
hard to find and cease support soon [why did they do a 10-32 initially?
And why are they still supporting it?]). So - touch wood - I'm not
having any problems with VLC (other than the one that prompted this and
an earlier thread).
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Of course, this show - like every other cop show on earth - massively
overstates the prevalence of violent crime: last year, in the whole of the UK,
police fired their weapons just three times. And there were precisely zero
fatalities. - Vincent Graff in RT, 2014/11/8-14

"J. P. Gilliver (John)" wrote

| because of the
| sea-change involved with 10 (and the suspicion that 32-bit 10 will be
| hard to find and cease support soon

? 32-bit software is supported under Win64, so it's
not really an issue. The only limitation I know of is
with in-process software. Shell extension DLLs can only
run under a matching Explorer. DLLs in general are
in-process. But I've circumvented that for most things
by making COM EXEs. It's the same thing as the DLL, but
it runs in its own process so it can be used with 64-bit
software.

..... All of which is to say that 32 vs 64 is mostly invisible
now.

On Thu, 18 Feb 2021 at 12:23:18, Mayayana
wrote (my responses usually follow points raised):
"J. P. Gilliver (John)" wrote

| because of the
| sea-change involved with 10 (and the suspicion that 32-bit 10 will be
| hard to find and cease support soon

? 32-bit software is supported under Win64, so it's
not really an issue. The only limitation I know of is
with in-process software. Shell extension DLLs can only

Don't know what "in-process" means, but Turnpike is (I think) indeed a
shell extension. It worked right up to the last pre-release version of
7-64 - which still contained whatever was needed, and switched to it
when required - but under the first official release (and all since), it
doesn't.

run under a matching Explorer. DLLs in general are
in-process. But I've circumvented that for most things
by making COM EXEs. It's the same thing as the DLL, but
it runs in its own process so it can be used with 64-bit
software.

(I doubt you'd be able to with Turnpike. [If you could, I think there'd
be lots who would give you Real Money!])

.... All of which is to say that 32 vs 64 is mostly invisible
now.

mostly (-:

--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

[What's your guilty pleasure?] Why should you feel guilty about pleasure? -
Michel Roux Jr in Radio Times 2-8 February 2013

"J. P. Gilliver (John)" wrote

| Don't know what "in-process" means, but Turnpike is (I think) indeed a
| shell extension. It worked right up to the last pre-release version of
| 7-64 - which still contained whatever was needed, and switched to it
| when required - but under the first official release (and all since), it
| doesn't.
|

In-process means that a library is loaded into the
same process, which means shared memory addresses.
It's sort of like talking to someone in your house vs
someone next door. The conversation is in the context
of your own house.
A sheel extension is a component that provides functionality
in Explorer, like an Explorer Bar or Property Page. If the
Turnpike software worked at first on Win64 then the problem
probably has nothing to do with 32/64.

On Thu, 18 Feb 2021 at 16:40:35, Mayayana
wrote (my responses usually follow points raised):
"J. P. Gilliver (John)" wrote

| Don't know what "in-process" means, but Turnpike is (I think) indeed a
| shell extension. It worked right up to the last pre-release version of
| 7-64 - which still contained whatever was needed, and switched to it
| when required - but under the first official release (and all since), it
| doesn't.
|

In-process means that a library is loaded into the
same process, which means shared memory addresses.
It's sort of like talking to someone in your house vs
someone next door. The conversation is in the context
of your own house.

Like the old paged, extended, expanded, and so on memory in DOS days.

A sheel extension is a component that provides functionality
in Explorer, like an Explorer Bar or Property Page. If the

Well, Turnpike makes a (pseudo?) folder appear on the desktop called
Turnpike, below which - when looked at in explorer - has apparent
folders called Newsgroups and Mail - with folders for newsgroups; in
other words, posts and emails look as if they're files in folders. (Not
identical - some different symbols.)

Turnpike software worked at first on Win64 then the problem
probably has nothing to do with 32/64.

Those who know a lot more than I say that up until, but not including,
the final release of 7-64, the 64-bit OS included a 32-bit shell (I
think shell was the word), which was "switched in" (?) when software
needed it.


3
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Know what happens when you don't pay your exorcist?
You get repossessed!
- Randle Brashear, 2015-8-9