Jump to content

MediaInfo For Emby Plugin(HDR, Vision, Atmos, DTS:X)


Cheesegeezer

Recommended Posts

FrostByte
11 minutes ago, Cheesegeezer said:

 

Sure i can do that nae bother, can you gimme an example where in your log please 

 

What I'm seeing

2022-06-15 20:54:54.644 Info Media Info: Zombieland: Double Tap is in the excluded list and will not be processed

maybe something like the below if it isn't a bother.  

2022-06-15 20:54:54.644 Info Media Info: Zombieland: Double Tap (####) is in the excluded list and will not be processed

 

  • Thanks 1
Link to comment
Share on other sites

@Cheesegeezer

I need to apologize. I wasn't aware that this was "your" plugin topic. I never considered or looked for that, because I had never subscribed to this topic (and I don't read "everything").

Actually I was under the assumption that we would still be talking in the topic where we had discussed MediaInfo options originally (https://emby.media/community/index.php?/topic/72953-add-dv-atmos-dtsx-hdr10plus-hlg-to-mediainfo-and-track-name/page/5/).

From all Emby staff, probably nobody dislikes unrelated conversations more than I do, and not even the posts I made regarding ffprobe dovi output belong into this topic.

I have split out all unrelated posts into a separate topic now:

 

This topic should really be about your plugin - only!

Sorry for the confusion.

softworkz

Edited by softworkz
  • Thanks 1
Link to comment
Share on other sites

Cheesegeezer
1 hour ago, softworkz said:

@Cheesegeezer

I need to apologize. I wasn't aware that this was "your" plugin topic. I never considered or looked for that, because I never subscribed to this topic (and I don't read "everything").

Actually I was under the assumption that we would still be talking in the topic where we originally discussed MediaInfo options (https://emby.media/community/index.php?/topic/72953-add-dv-atmos-dtsx-hdr10plus-hlg-to-mediainfo-and-track-name/page/5/).

From all Emby staff, probably nobody dislikes unrelated conversations more than I do, and not even those posts I made regarding ffprobe dovi output belong into this topic.

I have split out all unrelated posts into a separate topic:

 

 

This topic should really be about your plugin - only!

Sorry for the confusion.

softworkz

Thanks fella, and we all on the same side here, seriously we are!! 
 

my code might look a piece of novice crap to you guys, but i try to fill a gap where i can. 
 

understand also I’m about challenges, i managed to keep pilots in the air for 12 years as a helicopter engineer with a release to fly signature, i fixed trains for Siemens in London and fluid dynamics for Formula 1 teams and also Moto GP all over the globe! 
 

yeah… planes trains and automobiles lol 😆 

Now in the oil gas and renewables for well over 16 yrs and have written papers on new technologies accepted by the American petroleum institute. 
 

coding is a hobby and another challenge and at a tender age of 45 i love it.
 

  • Like 1
Link to comment
Share on other sites

A good software developer is not necessarily someone who knows a lot (about a specific area of development). Such knowledge allows allows you to work faster and more efficiently on a certain subject, but it's not that much important. Of course, general experience in sw development plays an important role and allows you to write code of higher quality and with low bug rates. That part can only be gained over time, and only when you pay attention to it. It's a matter of character I think: like people moving to a foreign country and having to learn a different language: some are permanently improving and after few years it's impossible to even notice that one isn't a native speaker. And there are others who stop learning after a minimum is achieved and keep making the same grammatical mistakes for the rest of their life, even though they've heard a zillion times how it would be right.

First of all, software development is about learning. Being able to learn quickly, being flexible to adopt gained knowledge, make correct deductions and valid abstractions of problems and - not to forget - constant self-reflection are key factors. Unlike most other professions, there is no point where you have learned "it" and you just keep doing your work. In that case, you might be a coder, programmer, or sw engineer, but should you ever come to that point, your career as a developer would have ended (or never existed).

So, learning is the key, "not knowing" is not a reason for embarrassment (while "knowing" but not acting accordingly is).
When you have questions regarding plugin development, you can always PM me!

softworkz

  • Like 2
Link to comment
Share on other sites

Cheesegeezer

Hey guys, so i wanna thank everyone for helping with developing this plugin. 
 

are were ready for a catalog release? After I implement frosty’s extra logging. 
 

huge thanks to @rbjtechfor taking out a lot of r&d time using his scripts to convert from.

huge thanks to @FrostByte for his wierd and wonderful formats and improving on what was already there.

and for everyone else that had the passion for this plugin to make to daylight.

Link to comment
Share on other sites

Cheesegeezer
12 minutes ago, FrostByte said:

I'm good here.  Works perfect on my NAS.  Thanks

Is RTM working good for you?

Link to comment
Share on other sites

Cheesegeezer

It's released

Thanks again everyone

image.thumb.png.dc7b6f8b51d486b79f03759d250afa39.png

  • Like 4
  • Thanks 2
Link to comment
Share on other sites

MagicDoubleM

Congratulations!

I swear I just discovered this one while adding something new. PCM-audiotracks, from DVDs, aren't invited to the party yet, right?

And I have to report, that I seem to have problems with real time monitoring, since I yesterday removed the scheduled task. There is a HDR-SDR-task running, which takes a whiiiiiiiiile, so could it be that mediainfo doesn't get triggered because of that?

 

image.png.52d39012dc485f0b439efe07680a178e.png

image.png.7dbfd9d4f3f7a4b0233ecb9fe0a0d896.png

Edited by MagicDoubleM
Link to comment
Share on other sites

Cheesegeezer
7 minutes ago, MagicDoubleM said:

Congratulations!

I swear I just discovered this one while adding something new. PCM-audiotracks, from DVDs, aren't invited to the party yet, right?

And I have to report, that I seem to have problems with real time monitoring, since I yesterday removed the scheduled task. There is a HDR-SDR-task running, which takes a whiiiiiiiiile, so could it be that mediainfo doesn't get triggered because of that?

 

image.png.52d39012dc485f0b439efe07680a178e.png

image.png.7dbfd9d4f3f7a4b0233ecb9fe0a0d896.png

Both tasks can run side by side, so that shouldn’t be the issue. I ran both purposely on my main system to see if there were issues. I do feel that i may have got over excited about the exit codes and this may be the issue here. 
 

on the point of PCM’s can you share your json?

are we looking at an aac pcm… because if its not adding anything to the mix then probably not worth it.

  • Like 1
Link to comment
Share on other sites

MagicDoubleM
12 minutes ago, Cheesegeezer said:

Both tasks can run side by side, so that shouldn’t be the issue. I ran both purposely on my main system to see if there were issues. I do feel that i may have got over excited about the exit codes and this may be the issue here. 
 

on the point of PCM’s can you share your json?

are we looking at an aac pcm… because if its not adding anything to the mix then probably not worth it.

Audiotracks look like this in the json, I would "expect" (not really, but you know what I mean) that they show up as "PCM 2.0 (48khz) [16-bit]", but that's really just wondering and nitpicking.
 

{
"@type": "Audio",
"@typeorder": "1",
"StreamOrder": "1",
"ID": "2",
"OriginalSourceMedium_ID": "4352",
"UniqueID": "16611185997022130693",
"Format": "PCM",
"Format_Settings_Endianness": "Little",
"Format_Settings_Sign": "Signed",
"CodecID": "A_PCM/INT/LIT",
"Duration": "5546.540000000",
"BitRate_Mode": "CBR",
"BitRate": "1536000",
"Channels": "2",
"SamplesPerFrame": "240",
"SamplingRate": "48000",
"SamplingCount": "266233920",
"FrameRate": "200.000",
"FrameCount": "1109308",
"BitDepth": "16",
"Delay": "0.000",
"Delay_Source": "Container",
"StreamSize": "1064935680",
"StreamSize_Proportion": "0.03842",
"Title": " (48Khz) [16-Bit]",
"Language": "de",
"Default": "Yes",
"Forced": "No",
"extra": {
"OriginalSourceMedium": "Blu-ray"
}
},
{
"@type": "Audio",
"@typeorder": "2",
"StreamOrder": "2",
"ID": "3",
"OriginalSourceMedium_ID": "4353",
"UniqueID": "6190127296791851607",
"Format": "PCM",
"Format_Settings_Endianness": "Little",
"Format_Settings_Sign": "Signed",
"CodecID": "A_PCM/INT/LIT",
"Duration": "5546.540000000",
"BitRate_Mode": "CBR",
"BitRate": "1536000",
"Channels": "2",
"SamplesPerFrame": "240",
"SamplingRate": "48000",
"SamplingCount": "266233920",
"FrameRate": "200.000",
"FrameCount": "1109308",
"BitDepth": "16",
"Delay": "0.000",
"Delay_Source": "Container",
"StreamSize": "1064935680",
"StreamSize_Proportion": "0.03842",
"Title": " (48Khz) [16-Bit]",
"Language": "fr",
"Default": "No",
"Forced": "No",
"extra": {
"OriginalSourceMedium": "Blu-ray"
}

 

Link to comment
Share on other sites

Cheesegeezer
9 minutes ago, MagicDoubleM said:

Audiotracks look like this in the json, I would "expect" (not really, but you know what I mean) that they show up as "PCM 2.0 (48khz) [16-bit]", but that's really just wondering and nitpicking.
 

{
"@type": "Audio",
"@typeorder": "1",
"StreamOrder": "1",
"ID": "2",
"OriginalSourceMedium_ID": "4352",
"UniqueID": "16611185997022130693",
"Format": "PCM",
"Format_Settings_Endianness": "Little",
"Format_Settings_Sign": "Signed",
"CodecID": "A_PCM/INT/LIT",
"Duration": "5546.540000000",
"BitRate_Mode": "CBR",
"BitRate": "1536000",
"Channels": "2",
"SamplesPerFrame": "240",
"SamplingRate": "48000",
"SamplingCount": "266233920",
"FrameRate": "200.000",
"FrameCount": "1109308",
"BitDepth": "16",
"Delay": "0.000",
"Delay_Source": "Container",
"StreamSize": "1064935680",
"StreamSize_Proportion": "0.03842",
"Title": " (48Khz) [16-Bit]",
"Language": "de",
"Default": "Yes",
"Forced": "No",
"extra": {
"OriginalSourceMedium": "Blu-ray"
}
},
{
"@type": "Audio",
"@typeorder": "2",
"StreamOrder": "2",
"ID": "3",
"OriginalSourceMedium_ID": "4353",
"UniqueID": "6190127296791851607",
"Format": "PCM",
"Format_Settings_Endianness": "Little",
"Format_Settings_Sign": "Signed",
"CodecID": "A_PCM/INT/LIT",
"Duration": "5546.540000000",
"BitRate_Mode": "CBR",
"BitRate": "1536000",
"Channels": "2",
"SamplesPerFrame": "240",
"SamplingRate": "48000",
"SamplingCount": "266233920",
"FrameRate": "200.000",
"FrameCount": "1109308",
"BitDepth": "16",
"Delay": "0.000",
"Delay_Source": "Container",
"StreamSize": "1064935680",
"StreamSize_Proportion": "0.03842",
"Title": " (48Khz) [16-Bit]",
"Language": "fr",
"Default": "No",
"Forced": "No",
"extra": {
"OriginalSourceMedium": "Blu-ray"
}

 

Fair point!! Don’t look great at all so we need to cater for this. Gimme a a couple of days.. work is mental so if I can grab 15mins, ill get this in the gene pool lol 😂 

Edited by Cheesegeezer
  • Like 1
Link to comment
Share on other sites

neik

Hello Cheese, I just got a couple of minutes to test the catalog release and now I am seeing some sort of error for every file that is being processed.
Here an example:

2022-06-21 21:31:56.695 Info Media Info: PERFORMING MEDIAINFO EXTRACTION ON MOVIES
2022-06-21 21:31:56.695 Info Media Info: PROCESSING OF  GX010060 - tv  HAS STARTED
2022-06-21 21:31:56.695 Info Media Info: Item FilePath = /var/lib/emby/gopro/GX010060 - tv.mkv 
2022-06-21 21:31:56.700 Debug Media Info: Starting MediaInfo.exe process
2022-06-21 21:31:58.329 Debug Media Info: ************** Reset Embedded Titles = False
2022-06-21 21:31:58.423 Debug Media Info: Ref Item = /var/lib/emby/gopro/GX010060 - tv.mkv
2022-06-21 21:31:58.424 Debug Media Info: GENERAL INFO
2022-06-21 21:31:58.424 Debug Media Info: Video Tracks = 1
2022-06-21 21:31:58.424 Debug Media Info: Audio Tracks = 1
2022-06-21 21:31:58.424 Debug Media Info: Subtitle Tracks = 
2022-06-21 21:31:58.424 Debug Media Info: Overall Bitrate = 51857126
2022-06-21 21:31:58.424 Debug Media Info: *********************
2022-06-21 21:31:58.424 Debug Media Info: VIDEO INFO
2022-06-21 21:31:58.424 Debug Media Info: Track Format = AVC
2022-06-21 21:31:58.424 Debug Media Info: BitRate = 
2022-06-21 21:31:58.424 Debug Media Info: Height =2704
2022-06-21 21:31:58.424 Debug Media Info: Width =1520
2022-06-21 21:31:58.424 Debug Media Info: Aspect Ration =0.562
2022-06-21 21:31:58.424 Debug Media Info: HDR Format =
2022-06-21 21:31:58.424 Debug Media Info: HDR Format Profile =
2022-06-21 21:31:58.424 Debug Media Info: HDR Compatibility =
2022-06-21 21:31:58.424 Debug Media Info: *********************
2022-06-21 21:31:58.437 Warn Media Info: Replace Video Track Failed to update Track Title & Exited with Code 1
2022-06-21 21:31:58.451 Debug App: Saving nfo metadata for /var/lib/emby/gopro/GX010060 - tv.mkv to /var/lib/emby/gopro/GX010060 - tv.nfo.
2022-06-21 21:31:58.457 Debug Media Info: AUDIO INFO
2022-06-21 21:31:58.457 Debug Media Info: Track Format = AAC
2022-06-21 21:31:58.457 Debug Media Info: No of Channels = 2
2022-06-21 21:31:58.457 Debug Media Info: Track Index = 1
2022-06-21 21:31:58.457 Debug Media Info: Track Additional Features = LC
2022-06-21 21:31:58.457 Debug Media Info: *********************
2022-06-21 21:31:58.463 Warn Media Info: Replace Audio Track Failed to update Track Title & Exited with Code 1
2022-06-21 21:31:58.466 Debug App: Saving nfo metadata for /var/lib/emby/gopro/GX010060 - tv.mkv to /var/lib/emby/gopro/GX010060 - tv.nfo.
2022-06-21 21:31:58.467 Info Media Info: Item Tags found =  
2022-06-21 21:31:58.468 Info Media Info: PROCESSING OF GX010060 - tv HAS COMPLETED
2022-06-21 21:31:58.469 Debug Media Info: MediaInfo processing for GX010060 - tv and took 1773 milliseconds

Edit: The NFO was somehow changed as the timestamp changed to now.
Server version 4.7.3.0

Edited by neik
Link to comment
Share on other sites

Cheesegeezer
48 minutes ago, neik said:

Hello Cheese, I just got a couple of minutes to test the catalog release and now I am seeing some sort of error for every file that is being processed.
Here an example:

2022-06-21 21:31:56.695 Info Media Info: PERFORMING MEDIAINFO EXTRACTION ON MOVIES
2022-06-21 21:31:56.695 Info Media Info: PROCESSING OF  GX010060 - tv  HAS STARTED
2022-06-21 21:31:56.695 Info Media Info: Item FilePath = /var/lib/emby/gopro/GX010060 - tv.mkv 
2022-06-21 21:31:56.700 Debug Media Info: Starting MediaInfo.exe process
2022-06-21 21:31:58.329 Debug Media Info: ************** Reset Embedded Titles = False
2022-06-21 21:31:58.423 Debug Media Info: Ref Item = /var/lib/emby/gopro/GX010060 - tv.mkv
2022-06-21 21:31:58.424 Debug Media Info: GENERAL INFO
2022-06-21 21:31:58.424 Debug Media Info: Video Tracks = 1
2022-06-21 21:31:58.424 Debug Media Info: Audio Tracks = 1
2022-06-21 21:31:58.424 Debug Media Info: Subtitle Tracks = 
2022-06-21 21:31:58.424 Debug Media Info: Overall Bitrate = 51857126
2022-06-21 21:31:58.424 Debug Media Info: *********************
2022-06-21 21:31:58.424 Debug Media Info: VIDEO INFO
2022-06-21 21:31:58.424 Debug Media Info: Track Format = AVC
2022-06-21 21:31:58.424 Debug Media Info: BitRate = 
2022-06-21 21:31:58.424 Debug Media Info: Height =2704
2022-06-21 21:31:58.424 Debug Media Info: Width =1520
2022-06-21 21:31:58.424 Debug Media Info: Aspect Ration =0.562
2022-06-21 21:31:58.424 Debug Media Info: HDR Format =
2022-06-21 21:31:58.424 Debug Media Info: HDR Format Profile =
2022-06-21 21:31:58.424 Debug Media Info: HDR Compatibility =
2022-06-21 21:31:58.424 Debug Media Info: *********************
2022-06-21 21:31:58.437 Warn Media Info: Replace Video Track Failed to update Track Title & Exited with Code 1
2022-06-21 21:31:58.451 Debug App: Saving nfo metadata for /var/lib/emby/gopro/GX010060 - tv.mkv to /var/lib/emby/gopro/GX010060 - tv.nfo.
2022-06-21 21:31:58.457 Debug Media Info: AUDIO INFO
2022-06-21 21:31:58.457 Debug Media Info: Track Format = AAC
2022-06-21 21:31:58.457 Debug Media Info: No of Channels = 2
2022-06-21 21:31:58.457 Debug Media Info: Track Index = 1
2022-06-21 21:31:58.457 Debug Media Info: Track Additional Features = LC
2022-06-21 21:31:58.457 Debug Media Info: *********************
2022-06-21 21:31:58.463 Warn Media Info: Replace Audio Track Failed to update Track Title & Exited with Code 1
2022-06-21 21:31:58.466 Debug App: Saving nfo metadata for /var/lib/emby/gopro/GX010060 - tv.mkv to /var/lib/emby/gopro/GX010060 - tv.nfo.
2022-06-21 21:31:58.467 Info Media Info: Item Tags found =  
2022-06-21 21:31:58.468 Info Media Info: PROCESSING OF GX010060 - tv HAS COMPLETED
2022-06-21 21:31:58.469 Debug Media Info: MediaInfo processing for GX010060 - tv and took 1773 milliseconds

Edit: The NFO was somehow changed as the timestamp changed to now.
Server version 4.7.3.0

Hey bud, so the file should still get processed. It’s just a warning that there is something up with the file. But I couldn’t see the track title being written to the file. 
The nfo will be updated from Emby side because the file refresher is started. Have a look in the log for Emby starting some refresher

if you can provide the mediaInfo Json for this particular file it will help us figure something out

Link to comment
Share on other sites

neik
10 hours ago, Cheesegeezer said:

Hey bud, so the file should still get processed. It’s just a warning that there is something up with the file.

It is not happening for that file only, apparently all files are exiting with error 1.

10 hours ago, Cheesegeezer said:

But I couldn’t see the track title being written to the file. 

The only change I can see in between my testing is that I updated MKVToolNix from iirc V45 to V68 due to V45 not supporting Dolby Vision and therefore the layer going lost.
Might this update be related?

10 hours ago, Cheesegeezer said:

if you can provide the mediaInfo Json for this particular file it will help us figure something out

Do you mean the attached file?

mediainfo.log

Link to comment
Share on other sites

neik

@Cheesegeezer, I had a deeper look at the logs and went through the processed movies one by one and it seems like all those movies exiting with "error 1" have already been processed previously in earlier testing.

Might be related?

I will let it run a bit longer and see how it behaves.
I'll let you know how it goes on.

Edit: Just let it run a little while longer and apparently there really is some sort of issue as it is not updating the tittles for me.
So, it was more of a coincidence that it was processing the already processed files.
Example: 

2022-06-22 11:38:58.069 Info Media Info: PROCESSING OF  Footloose  HAS STARTED
2022-06-22 11:38:58.069 Info Media Info: Item FilePath = /path/to/movies/Footloose (2011)/Footloose (2011).mkv 
2022-06-22 11:38:58.069 Debug Media Info: Starting MediaInfo.exe process
2022-06-22 11:39:00.901 Debug Media Info: ************** Reset Embedded Titles = False
2022-06-22 11:39:00.901 Debug Media Info: Ref Item = /path/to/movies/Footloose (2011)/Footloose (2011).mkv
2022-06-22 11:39:00.901 Debug Media Info: GENERAL INFO
2022-06-22 11:39:00.901 Debug Media Info: Video Tracks = 1
2022-06-22 11:39:00.901 Debug Media Info: Audio Tracks = 2
2022-06-22 11:39:00.901 Debug Media Info: Subtitle Tracks = 
2022-06-22 11:39:00.901 Debug Media Info: Overall Bitrate = 10169927
2022-06-22 11:39:00.901 Debug Media Info: *********************
2022-06-22 11:39:00.901 Debug Media Info: VIDEO INFO
2022-06-22 11:39:00.901 Debug Media Info: Track Format = AVC
2022-06-22 11:39:00.901 Debug Media Info: BitRate = 8020088
2022-06-22 11:39:00.901 Debug Media Info: Height =816
2022-06-22 11:39:00.901 Debug Media Info: Width =1920
2022-06-22 11:39:00.901 Debug Media Info: Aspect Ration =2.353
2022-06-22 11:39:00.901 Debug Media Info: HDR Format =
2022-06-22 11:39:00.901 Debug Media Info: HDR Format Profile =
2022-06-22 11:39:00.901 Debug Media Info: HDR Compatibility =
2022-06-22 11:39:00.901 Debug Media Info: *********************
2022-06-22 11:39:00.904 Warn Media Info: Replace Video Track Failed to update Track Title & Exited with Code 1
2022-06-22 11:39:00.909 Debug App: Saving nfo metadata for /path/to/movies/Footloose (2011)/Footloose (2011).mkv to /path/to/movies/Footloose (2011)/Footloose (2011).nfo.
2022-06-22 11:39:01.721 Debug Media Info: AUDIO INFO
2022-06-22 11:39:01.721 Debug Media Info: Track Format = AC-3
2022-06-22 11:39:01.721 Debug Media Info: No of Channels = 6
2022-06-22 11:39:01.721 Debug Media Info: Track Index = 1
2022-06-22 11:39:01.721 Debug Media Info: Track Additional Features = 
2022-06-22 11:39:01.721 Debug Media Info: *********************
2022-06-22 11:39:01.724 Warn Media Info: Replace Audio Track Failed to update Track Title & Exited with Code 1
2022-06-22 11:39:01.726 Debug App: Saving nfo metadata for /path/to/movies/Footloose (2011)/Footloose (2011).mkv to /path/to/movies/Footloose (2011)/Footloose (2011).nfo.
2022-06-22 11:39:01.743 Debug Media Info: AUDIO INFO
2022-06-22 11:39:01.743 Debug Media Info: Track Format = DTS
2022-06-22 11:39:01.743 Debug Media Info: No of Channels = 6
2022-06-22 11:39:01.743 Debug Media Info: Track Index = 2
2022-06-22 11:39:01.743 Debug Media Info: Track Additional Features = 
2022-06-22 11:39:01.743 Debug Media Info: *********************
2022-06-22 11:39:01.747 Warn Media Info: Replace Audio Track Failed to update Track Title & Exited with Code 1
2022-06-22 11:39:01.749 Debug App: Saving nfo metadata for /path/to/movies/Footloose (2011)/Footloose (2011).mkv to /path/to/movies/Footloose (2011)/Footloose (2011).nfo.
2022-06-22 11:39:01.756 Info Media Info: Item Tags found =  
2022-06-22 11:39:01.756 Info Media Info: PROCESSING OF Footloose HAS COMPLETED
2022-06-22 11:39:01.757 Debug Media Info: MediaInfo processing for Footloose and took 3687 milliseconds

Mediainfo output is attached.

mediainfo.log

Edited by neik
Link to comment
Share on other sites

rbjtech

So the emby error log is just passed from mkvpropedit - the 3rd party app that does all the changes.

See below.

I suspect it's permissions based (on your files) - so check those first.

Maybe do a manual edit to check the titles can be changed.

---

 

from https://mkvtoolnix.download/doc/mkvpropedit.html

mkvpropedit(1) exits with one of three exit codes:

  • 0 -- This exit code means that the modification has completed successfully.

  • 1 -- In this case mkvpropedit(1) has output at least one warning, but the modification did continue. A warning is prefixed with the text 'Warning:'. Depending on the issues involved the resulting files might be ok or not. The user is urged to check both the warning and the resulting files.

  • 2 -- This exit code is used after an error occurred. mkvpropedit(1) aborts right after outputting the error message. Error messages range from wrong command line arguments over read/write errors to broken files.

 

Link to comment
Share on other sites

rbjtech
2 hours ago, neik said:

The only change I can see in between my testing is that I updated MKVToolNix from iirc V45 to V68 due to V45 not supporting Dolby Vision and therefore the layer going lost.

This is likely the issue - does the new version of mkvpropedit have the necessary permissions to update(write) to the MKV files ?

Link to comment
Share on other sites

neik
2 minutes ago, rbjtech said:

Maybe do a manual edit to check the titles can be changed.

Any chance you can provide an example?

Just now, rbjtech said:

This is likely the issue - does the new version of mkvpropedit have the necessary permissions to update(write) to the MKV files ?

It should have, I guess, as it has the exact same permissions as the mediainfo binary.

Link to comment
Share on other sites

rbjtech
5 minutes ago, neik said:

Any chance you can provide an example?

It should have, I guess, as it has the exact same permissions as the mediainfo binary.

mkvpropedit "mediafile.mkv" --edit track:v1 --set "name=TEST_VIDEO_TITLE"

Edited by rbjtech
Link to comment
Share on other sites

Cheesegeezer

Just use mkvtoolnix GUI and see if you can do it thru that. Will be much easier than getting involved in command line interfaces if you are not used to it.

you can also check the file properties to see if it has a read only attribute associated with it. I don’t know linux but google might be your friend.

cheers

Link to comment
Share on other sites

rbjtech

If it worked before and now after changing mkvpropedit it no longer works, then logic would suggest it's something to do with changing mkvpropedit .. ;)

Link to comment
Share on other sites

neik
49 minutes ago, rbjtech said:

mkvpropedit "mediafile.mkv" --edit track:v1 --set "name=TEST_VIDEO_TITLE"

That does work just fine on both local files and the mount I am using.
Really strange...

Link to comment
Share on other sites

neik
47 minutes ago, Cheesegeezer said:

you can also check the file properties to see if it has a read only attribute associated with it. I don’t know linux but google might be your friend.

Thought the same but the binaries mkvpropedit & mediainfo both have the exact same permissions and same group.

Edit:
Any chance you can provide me an older version than the available 1.0, just for me to test?
Or maybe some more logging could be added?

Edited by neik
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...