A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » General XP issues or comments
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

.mp4 metadata editor?



 
 
Thread Tools Display Modes
  #1  
Old February 17th 21, 11:21 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .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.


Ads
  #2  
Old February 18th 21, 05:12 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default .mp4 metadata editor?

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
  #3  
Old February 18th 21, 06:23 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .mp4 metadata editor?

"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.


  #4  
Old February 18th 21, 06:29 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .mp4 metadata editor?

"Paul" wrote

| Reinserting edited metadata information from the FFMETADATAFILE file
can
| be done as:
| @example
| ffmpeg -i INPUT -i FFMETADATAFILE -map_metadata 1 -codec copy OUTPUT
| @end example
|

That looks fine. I ended up with something slightly different:

ffmpeg -y -i "C:\windows\desktop\SNL2.mp4" -f ffmetadata -map_metadata g
metadata.txt

Without the map_metadata it doesn't extract creation time.


| Their suggestion of "-codec copy" should be slightly better than
| my "-c:v copy -c:a copy" suggestion, as their method might copy
| more of the streams. There might even be a need to copy subtitles
| with some other trick.
|

I've tried it with a number of MP4 and MP3, resulting in
identical file sizes and nearly identical metadata. I looked
in their docs at -codec but I can't say I understand the
difference.


  #5  
Old February 18th 21, 06:49 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default .mp4 metadata editor?

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
  #6  
Old February 18th 21, 10:40 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .mp4 metadata editor?

"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.



  #7  
Old February 18th 21, 11:04 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default .mp4 metadata editor?

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
  #8  
Old February 19th 21, 02:01 AM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .mp4 metadata editor?

"J. P. Gilliver (John)" wrote

| 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.

There are 2 things. One is a "stub" that allows 32-bit
to run on Win64. They're not actually very different. So
32-bit can run on all Win64, including Win10.

The other thing, that people might have been talking
about, was that, if I remember correctly, Explorer/IE/32 was
the default at first because they hadn't finished the 64-bit
version. Then for some time (maybe still?) you could choose
to use the 32-bit version. Eventually I think it was removed.
So thast could explain how a shell extension worked and
then didn't.


  #9  
Old February 19th 21, 02:15 AM posted to alt.windows7.general,microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default .mp4 metadata editor?

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

| 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.

There are 2 things. One is a "stub" that allows 32-bit
to run on Win64. They're not actually very different. So
32-bit can run on all Win64, including Win10.

The other thing, that people might have been talking
about, was that, if I remember correctly, Explorer/IE/32 was
the default at first because they hadn't finished the 64-bit
version. Then for some time (maybe still?) you could choose
to use the 32-bit version. Eventually I think it was removed.
So thast could explain how a shell extension worked and
then didn't.

I suppose it _could_ use IE - I've heard that Explorer itself does.

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

It costs more to send someone to prison than it does to send a child to Eton.
- Dan Snow (RT 2014/11/1-7)
  #10  
Old February 19th 21, 04:16 AM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .mp4 metadata editor?

"J. P. Gilliver (John)" wrote

| I suppose it _could_ use IE - I've heard that Explorer itself does.

They're interconnected, or at least they were. I wrote
my own Explorer Bar and had to make extra effort to stop
it loading in IE. And it works in Win7. But it's 32-bit so I
can't use it in Win10.

The coupling dates back to Active Desktop in 98+. The strategy
to beat Netscape by embedding IE so deeply that no
court could make them remove it. The desktop was a browser
window. Folders were browser windows. Literally,
IE browser windows. It was so much fun to work with. But
then security happened. Nevertheless, both Explorer and IE
stayed linked at least through Win7. I assume much of it
exists in Win10 for backward compatibility.

All of that was marketed as Bill Gates brilliantly forseeing
the role of the Internet, but it really had nothing to do with
the Internet. It was about killing Netscape and finding a way
to sell ad space on Windows. The first worked out well, the
latter, not so much.


  #11  
Old February 19th 21, 06:58 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default .mp4 metadata editor?

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

| I suppose it _could_ use IE - I've heard that Explorer itself does.

They're interconnected, or at least they were. I wrote
my own Explorer Bar and had to make extra effort to stop
it loading in IE. And it works in Win7. But it's 32-bit so I
can't use it in Win10.


Win10-64, I presume you mean. (It's always puzzled me why they made -
and still support - a 10-32. I'd have thought they'd take the
opportunity to end 32; surely the saving in support/development costs
would outweigh the tiny market for 10-32 [presumably those with old
hardware or software - but surely most of them are going to stay on 7/8
anyway!]. But what do I know!)

The coupling dates back to Active Desktop in 98+. The strategy
to beat Netscape by embedding IE so deeply that no
court could make them remove it. The desktop was a browser
window. Folders were browser windows. Literally,
IE browser windows. It was so much fun to work with. But
then security happened. Nevertheless, both Explorer and IE
stayed linked at least through Win7. I assume much of it
exists in Win10 for backward compatibility.

All of that was marketed as Bill Gates brilliantly forseeing
the role of the Internet, but it really had nothing to do with


No; Microsoft were quite noticeable, to me anyway, for ignoring the
internet until they had to.

the Internet. It was about killing Netscape and finding a way


Yes, they seemed determined to do that, which seemed odd given their
lack of interest in the internet. Maybe they foresaw that it offered a
UI that people would like, so everything would be done via a browser,
and they weren't going to let anyone else develop one of those.

to sell ad space on Windows. The first worked out well, the
latter, not so much.

Indeed!

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

Practicall every British actor with a bus pass is in there ...
Barry Norman (on "The Best Exotic Marigold Hotel" [2011]), RT 2015/12/12-18
  #12  
Old February 20th 21, 01:55 AM posted to alt.windows7.general,microsoft.public.windowsxp.general
Stan Brown
external usenet poster
 
Posts: 2,904
Default .mp4 metadata editor?

On Thu, 18 Feb 2021 22:04:39 +0000, J. P. Gilliver (John) wrote:
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.


Sounds like you're talking about WOW6432. If I'm not mistaken, it
involved a whole set of duplicate libraries and some duplicate
utilities. C:\Windows\System contained only the 64-bit versions; C:
\Windows\System32 contained 32-bit versions.

This is analogous to "C:\Program Files" and "C:\Program Files (x86)"
for user-installed programs in 64-bit Windows, though of course there
would generally be no duplication of programs. It's possible to
install 32-bit _and_ 64-bit Firefox if you want to, but I imagine
that's pretty rare. (In my case, I found out it was possible by
carelessly downloading and installing the wrong update.)



--
Stan Brown, Tehachapi, California, USA https://BrownMath.com/
https://OakRoadSystems.com/
Shikata ga nai...
  #13  
Old February 20th 21, 01:56 AM posted to alt.windows7.general,microsoft.public.windowsxp.general
Stan Brown
external usenet poster
 
Posts: 2,904
Default .mp4 metadata editor?

On Fri, 19 Feb 2021 17:58:17 +0000, J. P. Gilliver (John) wrote:
Win10-64, I presume you mean. (It's always puzzled me why they made -
and still support - a 10-32. I'd have thought they'd take the
opportunity to end 32; surely the saving in support/development costs
would outweigh the tiny market for 10-32 [presumably those with old
hardware or software - but surely most of them are going to stay on 7/8
anyway!]. But what do I know!)


Remember that Microsoft can gather and sell your data much more
easily from Windows 10. They therefore want to make sure that as many
computers as possible can be "upgraded" to Windows 10.

--
Stan Brown, Tehachapi, California, USA https://BrownMath.com/
https://OakRoadSystems.com/
Shikata ga nai...
  #14  
Old February 20th 21, 03:14 AM posted to alt.windows7.general,microsoft.public.windowsxp.general
J. P. Gilliver (John)[_7_]
external usenet poster
 
Posts: 603
Default .mp4 metadata editor?

On Fri, 19 Feb 2021 at 16:55:08, Stan Brown
wrote (my responses usually follow points raised):
On Thu, 18 Feb 2021 22:04:39 +0000, J. P. Gilliver (John) wrote:
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.


Sounds like you're talking about WOW6432. If I'm not mistaken, it


Sounds vaguely familiar.

involved a whole set of duplicate libraries and some duplicate
utilities. C:\Windows\System contained only the 64-bit versions; C:
\Windows\System32 contained 32-bit versions.

This is analogous to "C:\Program Files" and "C:\Program Files (x86)"
for user-installed programs in 64-bit Windows, though of course there
would generally be no duplication of programs. It's possible to
install 32-bit _and_ 64-bit Firefox if you want to, but I imagine
that's pretty rare. (In my case, I found out it was possible by
carelessly downloading and installing the wrong update.)

Whatever it was, they apparently pulled it at the last moment (so they
told me in the Turnpike 'group).


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

Intelligence isn't complete without the full picture and the full picture is
all about doubt. Otherwise, you go the way of George Bush. - baroness Eliza
Manningham-Buller (former head of MI5), Radio Times 3-9 September 2011.
  #15  
Old February 20th 21, 02:43 PM posted to alt.windows7.general,microsoft.public.windowsxp.general
Mayayana
external usenet poster
 
Posts: 6,438
Default .mp4 metadata editor?

"Stan Brown" wrote

| Sounds like you're talking about WOW6432. If I'm not mistaken, it
| involved a whole set of duplicate libraries and some duplicate
| utilities. C:\Windows\System contained only the 64-bit versions; C:
| \Windows\System32 contained 32-bit versions.
|
That's not past tense. 32-bit still runs on Win64
via a global "shim" that redirects it to those libraries.
System32 is the 64-bit and SysWOW64 is the
32-bit. (Typical Microsoft confusion.)

But that's not the issue here. The issue is that 32
bit can't run in a 64-bit process and vice versa. The
addressing is different and pointers are different. Shell
extensions such as Explorer Bars, Property Sheets, and
so on, run in the Explorer process. They're loaded by
Explorer as DLLs. So they have to match the bitness.
Note that a shell extension is not "shell" in the sense of
a commandline program or GUI program. It specifically
refers to addons for Explorer, that are run by Explorer.

When Win64 first came out I think it was possible to switch
the default Explorer to 32-bit. So 32-bit shell extensions
could work. Eventually 32-bit Explorer was removed, as far
as I know. But the whole transition was very gradual because
no one was making 64-bit software at the time.

| This is analogous to "C:\Program Files" and "C:\Program Files (x86)"
| for user-installed programs in 64-bit Windows, though of course there
| would generally be no duplication of programs. It's possible to
| install 32-bit _and_ 64-bit Firefox if you want to, but I imagine
| that's pretty rare. (In my case, I found out it was possible by
| carelessly downloading and installing the wrong update.)
|

There's no problem at all running 32-bit software. Many
programs are still only 32-bit. If you look in your 32-bit
Program Files folder you'll probably see at least a few.
There's not much real difference between them. Win64
just defaults to 64-bit numbers for values such as memory
pointers, to allow for a future where such values are typical.
And if a 32-bit program wants to handle a file over
4 GB it will need to be designed for that. 4 GB+ will be
outside the normal data type range of a 4-byte integer.
No biggie, as the kids say. I write in VB6 and still use all of
my own software on Win7/Win10-64. I just can't install my
shell extensions.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 11:04 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.