MTR 6 ANNOUNCEMENTS - READ FIRST!

[GrizzlyHippo]

GB, I've just read through these 10 pages of your updates. Wow! Thank you for your continued work on this. I am having trouble with John Wick 3 at the moment, so look forward to trying MTR 5410 on the damn disk when it's ready.

Happy Christmas Y'all.

Grizzly.

[GrizzlyHippo]

If so , its $100 for the year ,
Any kind souls want to chip in towards that? seems a lot for two functions personally.

That's great , thank you! I will put this aside now.

$25 - W3ato
$25 - Freaky Dude
$25 - 2Socks
$22 - eahn
$44 - TheSystemhasFailed

Complete.
Many thanks to those who helped:
Development takes time , costs money , so once again Thank you.

Your user names will be in the apps credits.

Just catching up... been a long time since I was here. Let me know how to contribute / donate. I'll chip in for a years worth.

Grizzly.

[geezerbuttz]

If so , its $100 for the year ,
Any kind souls want to chip in towards that? seems a lot for two functions personally.

Just catching up... been a long time since I was here. Let me know how to contribute / donate. I'll chip in for a years worth.

Grizzly.

what does that mean?

[GrizzlyHippo]

Sorry, the first bit of text was a quote of yours, but it wasn't presented as a quote.

Basically, I’m happy to donate $100 to the cause!

Grizzly.

[geezerbuttz]

Ah , ok ... well sorry that was my mistake.

All help is currently very welcome , it helps keep the lights on here.
Its not easy being retired in this climate...

Regarding the App... i just successfully upgraded the cell link code...
Its remarkable simple compared to the original nightmare.

Next i just have to implement the tail_pgc checks. They are similar to the cell link code , should be quick.

In a nutshell around 600 lines of code , spread across three methods , have been reduced to 75 lines of code in one method with an additional 2 processing blocks nested internally...

Not bad ( but it required me to decipher code written by a moron.... )

[geezerbuttz]

well , its the end of the year..
I just completed a last minute addition prior to the release.

The cell table in main feature indicated what cells have cell commands attached to them ( blue flash )
I decided that this was not enough information to help you decide if the correct sequence of cells has been calculated to avoid possible CRC errors.

This meant I had to update the VMDecoder from DVDProbe , wrap it into a framework ,and get it into MTR.
Then capture the cells that have cell commands , decode them , and store them in the cell array.

Those cells can now display the cell command that is attached to them..
For example you can see if it jumps to a different cell , or if it exits before it starts by calling the tail PGC etc...

Thats done , working , and was quite a pain to crowbar in without hacking any existing code..
So it matches cleanly with the existing code base.

Happy New Year to you all.
Keep safe.

[geezerbuttz]

ok , small addition while im cleaning up.

I removed the tableview row coloring scheme in the title view , and replaced it with the "flagView" that i used in the cell view.

This means i can now notify you of not only titles with less than 1 seconds of video , but also titles that have programs
that all reference different program chains.
These normally have thousands of cells in the title.

These can now easily be identified by a yellow flag in the title view.
A red flag indicates zero time in the title.

In the case of a messed up title that has MultiPGC and zero time , the flag adapts to show both conditions.

Back to clean up....
G

[geezerbuttz]

right , the clean up continues:

Just moved all the panel drawing code for all tableviews , into a single class.
Implemented the flag code into that class thus all drawing routines are now centralised.

Removed the ISO view tint code , and enabled a set of flags , thus conforming to the standard in the rest of the UI.
Advantage? you can now represent three states per iso cell , instead of just one.

As the flag colors represent different results depending on the mode of operation , or table selected, I have added tool tips to the views that the flags are in so you can mouse over the view in the table view to refresh your memory.

Thats me for the day... im running out of things to clean up.

G

[Brady]

You are a super beast!

[geezerbuttz]

job for tomorrow:

Even when running DVDSectorProbe , you can end up with some cloned titles:
I plan tomorrow to implement a user driven check ( maybe user driven , still thinking about that )
that can identify the unique titles , and remove exact clones..

The clones must be mirror copies to be removed , any change m, will render them unique.


Now on a side note:
Anybody got a handle on a decent priced 1080Ti ( not paying hyped prices over here )
Let me know!

Good night all!

[geezerbuttz]

no work yesterday due to bad stomach...

So the titles code: its a little more involved.
1)when loading titles , or after adjusting titles with an IMF map we need to:
scan for duplicates , mark with a new flag that the titles is a duplicate, add (construct ) a list to add in addition to the contextual menu items that list those titles:

Its rather important , as it reduces the list clutter , reduces the memory footprint on obfuscated disks.

Im on it today.

More soon.
G

[geezerbuttz]

ok , that is done.
A few changes to make sure we do not trash the backup data for the title table .

Usage:

When disk now loads , it will automatically remove the duplicate titles , and group them together under one title entry.
This also happens when you load the data from an IMF data file.

You can at anytime reset the UI back to its raw condition by choosing to reset the structure by the title table contextual menu.

You can also , ( if you feel the need ) re apply the duplicate removal from the same contextual menu.
The same contextual menu ( when duplicate titles are found) contains a list of the titles that were removed that are identical to this selected title.

Titles that reference duplicates have the green flag set in the UI title Table.

(the nitty gritty)
matching the titles is as follows:
The same cell count - the same cell structure ( time sectors data )
The same root sector address
The same audio attributes
the same subtitle attributes

What does not matter are the titles call commands , as the cells can be the same , but the cell commands can differ.
For this , the commands do not matter as we are only interested in the cell data.


I feel a simple user guide ( addendum ) would suffice for this.

What do you think?
I will run over the source one last time, then if all is well, get ready to package.

G

[geezerbuttz]

optimised some memory routines , better usage of resources.
Changed the title/cell table view to display the cells hosting title.

This helps when you have a multi PGC title , as we now append the cells group PTT to the title number.
This then looks like this..

71.1
71.2
71.n

And so on , this helps you isolate cells groups from the PGC that are mashed in these titles.
(remember you can also right click to get other information such as the actual PGC number of the cell too)

A few more optimisations of some older code will be happening.

Now, something has arisen and I have to think carefully about the release date.
I have to travel home this coming weekend , and while I can get this out the door before that , there is no way I can issue the upgraded licenses for that week.

So , I am thinking to postpone the release until I get back here to ensure a smooth upgrade experience.
Thoughts....

G

[Brady]

I would for sure wait until you are back so you can deal with any unexpected issues.

[w3ato]

my thoughts are...
...I can wait...

[TheSystemHasFailed]

Now, something has arisen and I have to think carefully about the release date.
I have to travel home this coming weekend , and while I can get this out the door before that , there is no way I can issue the upgraded licenses for that week.

So , I am thinking to postpone the release until I get back here to ensure a smooth upgrade experience.
Thoughts....

G

Wait to do it until you're home.. we'll all be good until then..

Hope all is well...

[geezerbuttz]

yes , that will give me time to update the whole title reader.
Currently its a 2 pass system... a throwback to version 4.

I need to move it into a single process...

G

[geezerbuttz]

change of plan , left both in place as the initial gather does more than the secondary pass for title.
I have however optimised the sh*t out of it.

G

[geezerbuttz]

https://www.dropbox.com/scl/fi/vq47wn9h ... uizy0&dl=0

A quick and dirty video with all the new changes ( well , those that I can remember anyway ) on display.
Sorry about the ramblings and the bad audio... i was rushed and had no plan or direction.

CU all soon when I get back.

[geezerbuttz]

quick follow up , between packing and getting ripped of with extra flight costs , I managed to add a new function.

You can now access the subtitle color for each title , and change the colors...
Now we can fix the god awfull yellow subtitles!

CU soon.

[geezerbuttz]

im packed and waiting , but that gave me enough time to solve the dropped responder in the tableviews..

The solution?
Drop in a dummy backing view in the cellView.. regains focus every time , scrolling is back.

Cured.

[wngmst]

GB,

Really getting excited to view the new 6.x version! Keep up the good work!

Let us know how we can help.


WM

[geezerbuttz]

well im back...

I spent today reviewing the tableview code to solve the issue of the focus getting lost.

My fast solution was to drop a dummy view in there , and all was well...
well , that did not translate across all tables , and some it caused horrendous issues.

Instead , i have implemented tracking zones on the tableviews , and to automatically select the view as the current keyView and release it when the mouse leaves the view.


This makes sure that any and all mouse events are focused on that tableView , thus scrolling , dragging etc work without having to click first in the table.

I did some reading on the subtitle colours.
While i present all subtitle colors , it seems that a title can use multiple combinations of them.
You have a "per title" color group , a "per subtitle" color group...
I may add a 'probe' on the subtitle panel to allow you to read up untill the first encountered subtitle , to get the actual first 4 colours used for that subtitle , that way you can get an idea when 4 colours in the group of 16 are actually being used.

More on that when I look into this a little bit more.

G

[geezerbuttz]

just completed a small update in DVDSP to improve the display layout:

It now matches more closely the display of MTR in ISO mode.
This should help you to navigate between the two apps.

The exported file structure has not changed.

[geezerbuttz]

Added a couple of new features:

Due to preferences becoming cluttered , i redesigned the layout with tabs to ease the screen layout.

Added the ability to smooth subtitles in MKV.
Added the ability to display only forced subtitles in MKV.

In Process:
The ability to globally override the MKV subtitle colors via a four color choice in preferences.

That will be completed tomorrow.

Left todo , is the addendum video...

More soon.

[geezerbuttz]

i have completed the subtitle global color code and UI additions.
Only one issue , the custom colors set in the IDX ( internal in the MKV file ) do not effect the output in VLC.

Changing the titles referenced color pallete does work , but i need to get a better way to identify the actual color layers used ( background , border , stroke , fill etc )

Thoughts....

[geezerbuttz]

ok , i have an idea that i can implement.

I will be able to remove the individual title / subtitle control .

I need to read each subtitle packet , assertain the colours used ( indexed relative to the IFO )
Store this data , then at the end , manipulate the MKV pallete to reflect the replaced colours that we calculated.

Going to have to write code to parse the subpic control header to get those color indexes...
Already started that.

More soon.
G

[geezerbuttz]

This is complicated.
The subData is split across multiple packs , and I need to build the full frame before I can navigate its structure.
This needs some fresh eyes...

Tomorrow after sleep.

[geezerbuttz]

ok , we are reading and assembling the subpic data in memory as we extract...
Now to read the data in the subpic frame that we need.....

G

[geezerbuttz]

right that the subpic data disassembled in memory....
now we have the info , i just need to decide best how to hand the color tables i need to create.

More soon.