Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
7th December 2019, 08:26 | #1061 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
I don't know exactly how MeGUI's File Indexer tells Lsmash to index a source, as it does that "behind the scenes", but the log file indicates it creates a script to open the source file which it runs, causing Lsmash to index. The initial script created by MeGUI's Script Creator after indexing would look like this: LWLibavVideoSource("D:\Episode 4.mkv.lwi") It's always worked much the same way as indexing with DGIndex, where the index file becomes the source. DGDecode_mpeg2source("D:\Episode 4.d2v") For ffms2, I assume MeGUI uses the cachefile argument to create the index file in the working directory. I checked and if you open a source file directly using the script creator and an lwi index file exists in the same directory, MeGUI appears to verify it's valid and uses the source file as the source in the script, rather than the index file. At least for MKVs. I haven't checked other file types, but for file types where it'd normally index with a different indexer by default, it'd probably insist on indexing again, so being able to open an index file directly would prevent that. There's no way to bypass the File Indexer completely if MeGUI thinks a source needs indexing though. A way around the problem when using a newer version of Lsmash would be to manually create a script to open the source file, and to use that script as the source for MeGUI. When it's opened, Lsmash would automatically index the source file and MeGUI will patiently wait for the indexing to finish. Scripts can also be used as source files for the One Click encoder and batch encoding, but because MeGUI isn't seeing the source directly it can't know if it's anamorphic, and bypassing the File Indexer that way would mean the user would have to extract the audio themselves if they don't wish to re-encode it. Not including the path to the source in the index file probably isn't the end of the world, but MeGUI will have to be changed for Lsmash so it doesn't use the index file as the source, and I assume the index file is always going to have to live in the source directory. Last edited by hello_hello; 8th December 2019 at 18:57. |
|
9th December 2019, 20:14 | #1062 | Link | |
Registered User
Join Date: Jan 2019
Location: Antarctica
Posts: 74
|
Quote:
Was this .lwi taken out of the code or something? Is it possible to put whatever got it working to the latest lsmash? Perhaps then would the MeGUI author be willing to finally update. |
|
9th December 2019, 21:59 | #1063 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
http://avisynth.nl/index.php/LSMASHS...ived_Downloads Remove InputFilePath field from the index file. It's unnecessary and troublesome when users rename or move the source file. Given it doesn't seem to be common practice to use the index file as the source in scripts, I'm not sure how including the source path could be much of a problem. If you moved or renamed the source file and opened it in a script, wouldn't lsmash just index it again anyway? And if you are using the index file as the source... don't move or rename the source file. The ffms2-like cachefile argument is a welcome addition, although I've still found it a bit of an annoyance because you can't re-open the index file directly (with MeGUI) unless it's in the same directory as the source. DGIndex has worked that way forever. The path to the source is stored in the index file and it becomes the source for DGDecode. Maybe a new argument to make including the source path optional might be a compromise? Obviously LWLibavVideoSource has the ability to open an index file, so it seems a pity to lose that completely when it'd often be useful. Last edited by hello_hello; 9th December 2019 at 22:25. |
|
10th December 2019, 23:37 | #1065 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Index file should not contain hardcoded Path to a file. End of the story.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
11th December 2019, 00:42 | #1066 | Link | ||
Registered User
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 3,078
|
Quote:
LSmash is just following the good old DGIndex example, and I never heard any complaints about the d2v file format. I just rechecked with the latest DGIndex version: Quote:
|
||
11th December 2019, 02:37 | #1067 | Link | |
SuperVirus
Join Date: Jun 2012
Location: Antarctic Japan
Posts: 1,351
|
Quote:
Last edited by filler56789; 11th December 2019 at 02:39. Reason: disambiguation |
|
11th December 2019, 02:59 | #1068 | Link |
Useful n00b
Join Date: Jul 2014
Posts: 1,667
|
You can omit full paths too with DGIndex, leaving just the bare filename, which makes things relative to the current directory, and such that the files can be moved together to a new location without needing re-indexing.
|
11th December 2019, 08:13 | #1069 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
The cachefile argument is nice to have, but from the perspective of someone who uses a GUI, the ability to specify it's location isn't as useful when the index file doesn't know where the source is, as it can't be opened directly later on unless it's in the source folder. Could we have a show of hands from those who often use the cachefile argument without specifying a location other than the source folder? Does anyone regularly give index files fun names while still writing them to the same folders as the source? What about something like this? If the cachefile argument isn't used, or of the index file is written to the source folder, by default LSmash would not save the full path to the index file. If the index file is not written to the same folder as the source, then by default LSmash would write the full path. A FilePath argument would allow the user to over-ride those defaults. Just a thought... Last edited by hello_hello; 11th December 2019 at 08:53. |
|
11th December 2019, 10:09 | #1070 | Link |
HeartlessS Usurer
Join Date: Dec 2009
Location: Over the rainbow
Posts: 10,980
|
Embedding the filename in the index may or may not have been a good idea to begin with, but breaking things without good reason is also not a good idea.
EDIT: Is/was also a lousy (and lazy) idea for MeGUI to use embedded filename to load source, I was a bit shocked to discover that it did that.
__________________
I sometimes post sober. StainlessS@MediaFire ::: AND/OR ::: StainlessS@SendSpace "Some infinities are bigger than other infinities", but how many of them are infinitely bigger ??? Last edited by StainlessS; 11th December 2019 at 10:14. |
11th December 2019, 12:44 | #1071 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
While I'm defending MeGUI.... If I remember correctly adding Lsmash as an indexer wasn't completely straightforward. I don't think older versions report the indexing progress because I recall Zathor saying he had to find a way to let MeGUI know when it finished, and MeGUI had to be taught to move the index files to the working directory so lsmash wouldn't be embarrassed in the company of cachefile enabled indexers. So.... the index files are in the working directory and it's time to create a new script from scratch. MeGUI can open d2v index files and until recently it worked the same way for lsmash, but not so much for ffms2 because the index file has no idea where the source file is. You can work around it by manually moving/copying the index file to the source directory and open it as the source in MeGUI's script creator. MeGUI will create a new script with the index file specified for the cachefile argument. I assume the index file must be named correctly for MeGUI to get the source name right. Last edited by hello_hello; 11th December 2019 at 13:31. |
|
11th December 2019, 13:33 | #1072 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Mr. Common sense my friend... No guidelines needed.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 11th December 2019 at 13:37. |
11th December 2019, 16:08 | #1073 | Link |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Does the source path saved to the index file play any part in determining if the source and index file are a match? I assume not, given it's no longer written to the index file, so would it be logical to assume it only tells Lsmash where to find the source that's expected to match?
My questions are.... well they're not actually my questions, but Mr. Common Sense will hassle me relentlessly until I ask on his behalf..... Mr. Common Sense is keen to understand why the source/path info in the index file couldn't be ignored when LWLibavVideoSource is opening a video file directly, and why it wouldn't function exactly as it does without it. He's quite adamant the freedom to rename or move files won't change whether the source/path info in the index file is ignored or it's not written-in the first place. Mr. Common Sense is insisting if the source info written to the index file is only used when an index file becomes the source for LWLibavVideoSource it's so obviously common sense that the index file should include the video file's location, not including it becomes borderline mental. There's no cachefile-equivalent argument for specifying the video file's location when opening index files. Mr. Common Sense wants me to emphasise his/my entire post is purely a common sense view of how the world should work, with possibly no basis in reality, due to common sense being so uncommon. Last edited by hello_hello; 11th December 2019 at 16:28. |
11th December 2019, 16:42 | #1074 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,806
|
Quote:
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
|
11th December 2019, 21:00 | #1075 | Link | |
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
Mr. Common Sense is beginning to suspect if there's a good argument for never writing the source path to the index file, someone would've offered it by now, or maybe explained why I'm wrong for thinking it should at least be optional, or something.... On a completely different subject, the usual expression is "barking up the wrong tree", in case you weren't aware. Unless that's an alternative version I've not heard before. Last edited by hello_hello; 11th December 2019 at 21:06. |
|
11th December 2019, 21:40 | #1076 | Link |
Registered User
Join Date: Jun 2012
Location: Ibiza, Spain
Posts: 321
|
Nothing is broken in lsmash, only something is broken in megui if you try to use an unsupported fork of that plugin on that gui. Is as simple as using another fork, or asking the megui author for an update.
|
12th December 2019, 08:32 | #1077 | Link | ||
Registered User
Join Date: Mar 2011
Posts: 4,823
|
There's no insisting taking place. I'm just waiting for someone to answer a single question I've asked or to explain what problems were fixed by the change. I'm starting to accept that's not realistic, as even beginning my last post with "it's not about MeGUI" didn't help.
Quote:
Quote:
Last edited by hello_hello; 12th December 2019 at 09:31. |
||
13th December 2019, 11:13 | #1078 | Link | ||||
Registered User
Join Date: Mar 2011
Posts: 4,823
|
Quote:
Quote:
Quote:
Are you mistaking calmly answering questions for yelling or are you being childish? Quote:
I use AVISynthesizer quite a bit for creating scripts. In case you're not aware of it, you create templates to use via Explorer's right click menu and AVISynthesizer adds the path/source details and creates the script. When the index file wasn't in the source folder you could previously use it instead of the source, or even create a new script manually without requiring any tedious typing for the cachefile argument, and even when doing so to open it in avspmod. Admittedly, that sort of thing only qualifies as a minor annoyance, but we all do things differently. Not everyone creates a script to open and index a source in avspmod before moving or renaming the source file. I honestly don't care that much if lsmash remains the way it is, but the refusal to acknowledge there might have been a better way to solve the source renaming/moving problem does baffle me a little, as does attempting to blame a GUI or label it as badly designed, especially if the change was made without knowing index files could be used as the source. Last edited by hello_hello; 13th December 2019 at 18:20. |
||||
13th December 2019, 11:39 | #1079 | Link |
Registered User
Join Date: Jun 2012
Location: Ibiza, Spain
Posts: 321
|
I know I already bit the bait but, shouldn't we ignore the obvious troll? He doesn't use the plugin but he's just wasting others time with ridiculous questions nobody cares just because he's probably bored and all. In the last post he even retorted to mild insulting, sad view.
|
Thread Tools | Search this Thread |
Display Modes | |
|
|