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. |
12th November 2011, 16:55 | #501 | Link |
Registered User
Join Date: Oct 2007
Posts: 42
|
Thanks for letting me know.. I have completely missed that! =)
Ok. I understand.. I have the same feeling like you regarding Quicktime.. But it produce great sounding aac files Meanwhile, I'll try to use the FHG aac encoder |
12th November 2011, 21:41 | #502 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
LameXP v4.03 R2 has been released
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ |
|
12th November 2011, 21:55 | #503 | Link |
Registered User
Join Date: Jul 2007
Location: UK
Posts: 336
|
After installing an update, I always have to set my personal preferences again - the output folder, disable sounds, uncheck .m3u option, disable shell integration etc...
Is it possible that when an update is installed that preferences are remembered? This would be a welcome addition to this great program. Thanks. |
12th November 2011, 22:06 | #504 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Some settings change their range/meaning between different versions and, the way it currently is implemented, a rude surprise is avoided. After all, I should implement an automatic "import" function that will import settings from previous versions - if and only if possible. (Nonetheless, if you only install major updates, then you won't update and thus loose your settings very often. So this isn't high priority)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 13th November 2011 at 20:57. |
|
15th November 2011, 16:27 | #505 | Link |
Registered User
Join Date: Feb 2005
Location: São Paulo, Brazil
Posts: 392
|
The Web Update and instalation windows should not be aways on top of everything... I'm writing it right now with the download window above the textbox...
Besides that, this is my favorite audio encoding tool. Thanks for the update! |
15th November 2011, 16:36 | #506 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
I made the Installer and Web Updater windows "top most", because Windows has the annoying tendency to show the GUI of newly created processes in the background.
Having to minimize all other windows in order to find the Installer (or Updater) window may be very confusing, especially to less experienced users. Therefore I think making those windows "top most", in order to ensure they will be visible right away, is the the lesser of two evils. Also: How often do you install/update LameXP? Unless you use Beta updates, you shouldn't see the updater more often than once every 2 or 3 months. And, while updating, focusing on the Updater isn't the worst thing... (You can minimize the updater at any time, of course. Probably makes sense only, if your internet connection is extremely slow)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 15th November 2011 at 16:46. |
18th November 2011, 22:07 | #507 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Diary of an GUI developer
A small excursion: LameXP uses "background" threads to monitor the encoder/decoder processes (e.g. LAME or OggEnc2) in real-time. A "background" thread will read and parse all text output that its encoder/decoder process writes to the STDOUT or STDERR. And, as soon as the process has written a progress update, the "background" thread emits an update signal. The update signal will then be processed in the "main" (GUI) thread's event loop, causing the progress indicator to be updated. Until now, each "background" thread was emitting update signals as soon as possible and even if the progress hadn't changed at all. It has to be noted that some encoder/decoder processes write a whole lot of status messages to their STDOUT/STDERR, often resulting in the same progress value (percentage) being reported multiple times. This happens, for example, if the progress hasn't changed between two (or more) consecutive status messages. Unfortunately as a result our "background" threads will emit update signals at a high rate! While playing around with the profiler (AMD CodeAnalyst), it came to my attention that the LameXP front-end process was eating a substantial amount of CPU time, in certain cases. It was obvious that this was caused by too many update signals being emitted/processed. For this reason I implemented update signal coalescing today. This means: Now a "background" thread will emit an update signal if and only if the progress has increased by at least 3% - relative to the previous update signal that has been emitted. Depending on the individual encoder/decoder, this significantly reduces the amount of update signals the "main" thread has to process, which clearly reduces the CPU time consumed by the LameXP front-end process. That CPU time is now available to the encoder/decoder processes, which will speed-up the overall process, or to other processes running on the system. It comes at cost of slightly delayed progress indicator updates. This CPU usage graph shows the CPU load produced by the LameXP front-end process for the very same transcoding job, before (left) and after (right) the optimization: And here is a more detailed analysis of the CPU time consumption for all processes running on the computer while transcoding, before (left) and after (right) the optimization: (That's a reduction of LameXP's CPU time consumption to 1/5 in this particular case - using 'mpg123' as decoder and 'OggEnc2' as encoder)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 20th November 2011 at 17:48. |
20th November 2011, 01:34 | #508 | Link | |
typo lover
Join Date: May 2009
Posts: 595
|
Quote:
http://sites.google.com/site/qaacpage/
__________________
my repositories |
|
20th November 2011, 01:53 | #509 | 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; 20th November 2011 at 02:04. |
|
22nd November 2011, 20:17 | #510 | Link |
Registered User
Join Date: Jan 2010
Posts: 9
|
These probably are dumb questions/suggestions:
Every time I open LameXP I have to clear 'Comment' field from Meta Data, it doesn't memorize the blank deleted info, both portable/install versions. Then again when I'm editing tag infos on foobar there is always "LAME 32bits version 3.99.1 (http://lame.sf.net)" written in <encoding settings>. It would be cool if this could be personalized. Regarding 32bits - I'm running under win7 x64 and it works fast without any problem but since there is a LAME 64-bit version available wouldn't make sense that be included/used? I had the last version updated from the manager and today I noticed 'Adjust Bass (dB)' @ -1,00 and I'm positive I didn't change it. It would be cool if it was possible to drag a .cue file instead of using the import tool. Lazy, I know. Thanks for this indispensable app. |
22nd November 2011, 20:46 | #511 | Link | ||||
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Hello, VzK.
Quote:
It's probably a help for the developers. So if somebody sends in a "problematic" file to the LAME developers, they can easily know form which LAME version that file originated. Even if I could, I wouldn't modify LAME to suppress its signature. And I wonder what you want to hide? It doesn't leak any person information! Quote:
Including a 64-Bit build "just because we can" isn't a good idea. It would make LameXP.exe even bigger. And, as the 64-Bit builds of LAME currently can't be build with Assembler-optimizations enabled, they would probably be even slower... (I did a test with various compiler settings a while ago and the 64-Bit build was the slowest on my system) Quote:
(If not, I'll investigate it, as soon as you give me detailed instructions on how to reproduce the issue) Quote:
That's why you can throw a bunch of files onto LameXP and still it will be able to tell the type of each file and select the suitable decoder. That's not possible with Cue Sheets, because these are simple Text files. Well, we could try to guess that a file with extension .cue is a Cue Sheet, but file extensions are not unambiguous and might even be "wrong".
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 22nd November 2011 at 21:20. |
||||
23rd November 2011, 01:02 | #512 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Here is experimental QAAC (Apple QuickTime/iTunes AAC encoder) support
You will need to install the QAAC Add-in for LameXP from this location: http://www.mediafire.com/file/8ifdny...2011-11-22.zip Last but not least, if you do not have an up-to-date QuickTime or iTunes installed yet, you will have to download and install that too (Note: If both, Nero AAC and QAAC, are available, then LameXP will give preference to QAAC for now!)
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 4th December 2011 at 23:38. |
1st December 2011, 23:42 | #513 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
LameXP v4.04 Alpha-6:
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 4th December 2011 at 23:29. |
|
4th December 2011, 11:40 | #514 | Link |
Registered User
Join Date: Aug 2008
Posts: 343
|
Hello Lord Mulder, do you take in account Intel Hyperthreading? When i was compressing on corei3mobile 2cores/4threads with two cores set in lamexp, my cpu wasnt full utilised. When i set to 4 cores, cpu went on 100% and compressing was faster. Not big deal cause we can manualy set this option, but since you automate parallel instance count, You might consider Hyperthreading too. Wonder if same apply to bulldozer.
|
4th December 2011, 14:13 | #515 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Quote:
Hyperthreading simulates two "logical" cores for each "physical" one. But from the operating systems point of view, HT just doubles the number of CPU cores. In "Auto" mode, LameXP will detect the number of CPU cores (using the GetNativeSystemInfo function ) and adjusts the maximum number of parallel instances accordingly. The number of CPU cores reported by GetNativeSystemInfo() should include all CPU cores, e.g. on a Quadcore with HT enabled, it should report eight cores. Consequently on your Dualcore "Core i3 Mobile" with HT - if it really does have HT (isn't that for the i5 M's only?) - LameXP should detect and use four cores/instances. Still this is only a maximum! That maximum number of parallel instanced can only be reached, if the number of files transcoded "at once" is at least as high as the maximum. Moreover: Up to and including LameXP v4.03, the upper bound for the maximum number of instances was four! I implemented a less restrictive formula in LameXP v4.04. (Also note that, if you overwrite LameXP's decision by manually setting the number of instances, it will run exactly the number of instances you have configured!) For details please see: http://lamexp.git.sourceforge.net/gi...=HEAD#89cbd3d0
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 4th December 2011 at 15:15. |
|
4th December 2011, 20:38 | #516 | Link |
Registered User
Join Date: Aug 2008
Posts: 343
|
Yes, it works as u say in stable 4.03 release. My last version i used was beta-6 snapshot and i wasnt sure if my cpu threads was recognized properly. Now i can't verify, beta expired And nice cpu/ram usage indicator addon btw
First mobile hyperthreaded cpu was intel's 1st gen corei3 series if any wanna know. |
4th December 2011, 21:25 | #517 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
Note that you can always run LameXP with "--console" option to check the number of CPU cores that have been detected.
Output should look like this: Code:
CPU vendor id : GenuineIntel (Intel: 1) CPU brand string : Intel(R) Core(TM)2 Quad CPU @ 2.40GHz CPU signature : Family: 6, Model: 15, Stepping: 7 CPU capabilities : MMX: 1, SSE: 1, SSE2: 1, SSE3: 1, SSSE3: 1, x64: 1 Number of CPU's : 4
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 5th December 2011 at 02:14. |
4th December 2011, 23:31 | #518 | Link | |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
LameXP v4.04 Alpha-7:
Quote:
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 9th December 2011 at 01:42. |
|
7th December 2011, 13:28 | #519 | Link | |
Registered User
Join Date: Jul 2008
Posts: 532
|
Quote:
Code:
-t disable INFO/WAV header Disable writing of the INFO Tag on encoding. This tag in embedded in frame 0 of the MP3 file. It includes some information about the encoding options of the file, and in VBR it lets VBR aware players correctly seek and compute playing times of VBR files. When '--decode' is specified (decode to WAV), this flag will disable writing of the WAV header. The output will be raw PCM, native endian format. Use -x to swap bytes. |
|
7th December 2011, 21:39 | #520 | Link |
Software Developer
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,248
|
These are two different things:
The so called "LAME header" is an extension of the good old "Xing/Info header". The format of the extended Xing header is described here: http://gabriel.mp3-tech.org/mp3infotag.html In the LAME tag there are only 9 characters for the version info. The format for the 'VersionString ' field used to be "LAME3.XXr", but there was some confusion about that recently: http://www.hydrogenaudio.org/forums/...dpost&p=775750 At the same time, the "long" version string, such as "LAME 32bits version 3.99.1 (http://lame.sf.net)", is included in a normal id3v2 tag. ID3 (version 2) Tag: http://img202.imageshack.us/img202/2...1402011120.png Xing+LAME Header: http://img248.imageshack.us/img248/2...1402011120.png
__________________
Go to https://standforukraine.com/ to find legitimate Ukrainian Charities 🇺🇦✊ Last edited by LoRd_MuldeR; 7th December 2011 at 23:08. |
Tags |
aac, aotuv, flac, lame, lamexp, mp3, mp4, ogg, oggenc, opus, vorbis |
|
|