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. |
24th May 2020, 10:55 | #1681 | Link | |||
Registered User
Join Date: May 2007
Location: Wisconsin
Posts: 2,132
|
Quote:
Quote:
Quote:
__________________
My Total Eclipse 2017 Photos My Nov 2019 Game of Thrones Tour My NEOWISE Comet Photos 2020 Last edited by MrVideo; 24th May 2020 at 10:57. |
|||
24th May 2020, 12:48 | #1682 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Of course, we cannot simply delete the source files (after conversion), just because they are WAV files, because WAV files can very well be added to the source file list in other ways - CUE import is not they only way. So, yeah, to implement what you want, it would be necessary to carry some kind of additional "tag" along with each source file on the list which indicates how the particular source files was added to the list. But, even then, it would be anything but clear whether the average user wants their source files to be deleted (after conversion), just because these files have been added to the source list via the CUE Sheet importer...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 24th May 2020 at 12:58. |
|
27th May 2020, 20:52 | #1684 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
It's not done with the flag alone. If some files on the source files list do have a "self-destruct" flag set, while others don't, this needs to be indicated to the user in the GUI in some suitable way – because we don't want to have a "hidden" state in the application that will take the user by surprise. And, if so, then you'd probably want to also give the user a way to set or clear the "self-destruct" flag as needed...
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 27th May 2020 at 20:56. |
|
29th May 2020, 09:39 | #1686 | Link |
Life's clearer in 4K UHD
Join Date: Jun 2003
Location: Notts, UK
Posts: 12,227
|
Remove them... Of-course
__________________
| I've been testing hardware media playback devices and software A/V encoders and decoders since 2001 | My Network Layout & A/V Gear |
|
11th June 2020, 16:12 | #1689 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Sorry, did not have time to look into this yet.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
12th June 2020, 06:54 | #1690 | Link |
Registered User
Join Date: May 2007
Location: Wisconsin
Posts: 2,132
|
When encoding files, the status for filtering and encoding is not accurate. I've never seen them go above 20%. It varies as to what the peak percentage is. The only one that goes to 100% is decoding. Is there an issue as to why those two aren't displaying percentage correctly?
|
13th June 2020, 17:08 | #1691 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
So, every time the decoder, filter or encoder process prints a progress update to the stdout, the corresponding "worker" thread will parse the new progress value and send a signal the "main" (GUI) thread. GUI will then be updated accordingly. If you think that, for a particular encoder or decoder, the progress is not parsed properly by LameXP, you will have to tell us which exact encoder or decoder is affected. In that case, you should first check the progress updates that are actually printed to the stdout by the affected encoder or decoder (e.g. by running the affected encoder or decoder in the terminal) and compare that to the progress that is displayed in LameXP. If and only if LameXP is "missing" progress updates that actually have been printed by the encoder or decoder process, we might by able to fix something on the LameXP side. Having said that, progress updates generally work smoothly for me: http://www.mediafire.com/file/6vbmv2...gress.mkv/file Last but not least: Be aware that, for short files, the process will complete quickly. So there simply may not be a large number of progress update before the process completes – in which case it may seem like the progress just "jumps" to 100%.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 13th June 2020 at 17:24. |
|
13th June 2020, 20:30 | #1692 | Link | ||
Registered User
Join Date: May 2007
Location: Wisconsin
Posts: 2,132
|
Quote:
The decoder does show all the way to 100%. The filter and encoder barely get above 0%. At most I've seen the encoder get to is 22% and these were files that took minutes to filter/encode. I'd run them on the command line, but in order to compare apples to apples, I'd have to know what the command line options are that you use. The console output doesn't supply that information. Quote:
|
||
13th June 2020, 23:10 | #1693 | Link | |||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
File copy does not invoke a separate process. We use CopyFileExW() to copy the WAV file. And we install a LPPROGRESS_ROUTINE callback to monitor the progress of the copy operation. It is very possible that copying the file finishes so quickly that there is not much time to actually see any "intermediate" progress updates. So, in that case, it would effectively just "jump" to 100% very quickly. Anyway, we can only update the progress displayed in the GUI when Windows actually invokes the supplied LPPROGRESS_ROUTINE callback. There is nothing else we could do on our side, I think. Quote:
As explained before, the one and only case in which things could possibly be improved on the LameXP side would be if any progress updates actually written out by the filter process (e.g. SoX) were "missed" or parsed wrongly by LameXP. You can see the full command-line that LameXP invokes in the log, as always (just double-click an item after it has finished). Either that, or just use a tool like Process Monitor. Quote:
If you look at the video more carefully, you will see that the "filter" progress smoothly goes up from 0% to 100%. You can best see this with Track #1, which is the longest – it still completes pretty fast, so may want to step frame-by-frame.
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 13th June 2020 at 23:20. |
|||
14th June 2020, 11:39 | #1694 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Here is new TEST build with some additional debug outputs in WAV decoder and Normalization filter:
http://www.mediafire.com/file/ax0bcn...06-14.zip/file Looks all good to me, though, when converting a WAV file with the Normalization filter (SoX) enabled: https://pastebin.com/tinPicAd (Only "anomaly" we can see here is that SoX reports 100% several times in a row, after reaching 100% for the first time. That is probably because SoX only reports the percentage of the input file that has been read thus far, not the percentage of the output file that has been written. So there probably will be some extra delay at the end of the normalization process, when flushing that pending data that is still buffered inside SoX)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 24th June 2020 at 22:10. |
24th June 2020, 20:01 | #1695 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
LameXP v4.19 Alpha-5
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 21st August 2020 at 21:40. |
|
12th July 2020, 15:23 | #1696 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
LameXP v4.19 Alpha-6
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 21st August 2020 at 21:39. |
|
19th August 2020, 15:14 | #1697 | Link |
Registered User
Join Date: Mar 2005
Posts: 34
|
I installed the latest version this morning from the link above. It says:
"This demo (pre-release) version of LameXP has expired at 2020-08-11" When I do "check for updates" I get a windows which says: "No new updates. Currently installed Build 2274. Latest available: Build 2274". Thank you for this great software and I look forward to trying the latest version! |
19th August 2020, 23:40 | #1698 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 21st August 2020 at 21:40. |
|
21st August 2020, 21:39 | #1699 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
LameXP v4.19 Alpha-7
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 5th September 2020 at 21:07. |
|
Tags |
aac, aotuv, flac, lame, lamexp, mp3, mp4, ogg, oggenc, opus, vorbis |
Thread Tools | Search this Thread |
Display Modes | |
|
|