I did some serious research these last few weeks, trying to obtain information as accurate as possible for the dates displayed for each file (that information will come handy for some site improvements I've been planning).
I researched release notes, readmes, zip file timestamps, and even PE timestamps; and hopefully the pages now portray as accurately as possible what was released when.
Also, I decided to upload/update several MP3 encoders this time around:
If you have LAME versions not featured at the LAME page, please submit them!
rjamorim, rc55, 2017? I think I will go back to sleep, something seems very off.
How modern to use github. Soon you will use github pages, markdown and github LFS for the files...
LFS sounds interesting, but RW burns way more bandwidth than what they provide... (and I'm way too old to learn markdown now that I kinda grasped html)
Last post by jsdyson -
Got another example -- I have partially retuned the restoration processor -- most got rid of the surging. it was mostly due to the depth of linear expansion being allowed to be too deep in the time/dB axis. I made the dB expander sections more solid (longer averaging times). The dB expander sections use an atypical attack/release structure -- because it isn't one. It basically doesn't understand attack/release but rather chases the signal around for reasonable dB bounds. If I had used a traditional attack/release structure, the surging and expansion artifacts would be MUCH worse. Unfortunately, there was a small loss in noise reduction -- because the gain control for low levels is less quick. This whole thing is a tradeoff. Even though it is not scientific, I have a sample of another song off the same album. The same song gets boring over and over again -- also the original example '14.pais*' wasn't really the 'best' quality recording, but REALLY SHOWED the general capability of the restoration processor. In that previous example, there was even some pre-limiting and limiting and super-fast dynamic limiting in the result -- but I'll bet that you cannot tell when it was happening!!! (very good limiter design -- doesn't distort or intermod unless desperate.) So, attached is the example with the retuned result. (One reason why I sometimes have troubles with the examples is that my ears are so darned variable -- so at night I'll think that the sound is okay -- then in the morning, I'll hear a defect.) The only defect that I can tell this morning in this example would normally be inaudible (might be able to see the noise floor, however with careful digital analysis.)
How can I find those 4 track pairs in that huge text log ?
What do you find at the end of the log?
For text files this big, Notepad++ is your friend.
Ok i reinstall my realtek audio driver to latest version it fixed for me the problem please close thread. thx for the help.
Last post by jazzthieve -
These forums are for the desktop version only.
You need to be here.
Scientific Discussion / Re: Have a working 'expander' based on DolbyA (not same design) -- works well.Last post by jsdyson -
One more example -- slightly less processing. There might be too much processing for some ears on the original 'restored' version, so I backed off about 30% of the processing in this example. Note that I still don't have 100% of the surging fixed again -- I have retuned for NR a bit better, and so getting the higher level dynamics tuned to the 'ear' is important. Need to decide if I need to make the depth of fast (and linear) expansion faster, make the slow (dB/dB) expansion slower or faster or what other combination. It sounds to me like the hold time is a little too long -- but the tradeoff is LF distortion. There are so darned many tradeoffs that it can be very UNFUN to work on this stuff!!! So, below is a version of the demo with less expansion. (I dropped the expansion from 1:1.60 to 1:1.40 to give an idea as to the difference.) I didn't change any timeconstants (which are pretty much fixed anyway -- but appear to need to be retuned because of the vast amount of NR enabled.)
Last post by jsdyson -
I have put the 4 band aside for now -- pretty much latest sources reside on the repository. I found out (by some experiments) that the 'large scale' processor can usually do 90% of what the 4 band can do -- but also MUCH MUCH MORE. Frankly, in some of my experiments, the noise reduction capability (due to some uncommon algorithms) SEEMS TO GO far beyond a normal expander. In the same way the 'large scale' APPEARS to do a pretty good (if not amazing) job of dynamic range expansion for transients. I did learn some limitations of the transient expansion mechanism -- should have realized from the math -- so I had to only allow enable/disable rather than tuning it. (The transient expansion tends to fit hand-in-glove with the original compression that damaged the music and the normal expansion mechanisms in the expander section of the processor.) I still plan to give out binaries and a little later source code -- but there is A LOT more work than the simple 4 band. Because this new processor is so very aggressive -- it even has the ability to recompress and relimit if too much expansion is requested. The tunables are too numerous right now, and I need to do some work on that. Here are some short examples (before/after.) The original version is converted directly from the source copy used to produce the 'after' version. There was no special tuning in this case, but the expander was set to a more aggressive mode. The most recent work on the expander has been to further refine the NR capabilites, which I estimate at approx 10-12dB (with an 18dB maximum NR.) This is NOT your average audio processor!!! Attached are the shortened examples...
Last post by zilexa -
Thanks for your tip unfortunately that one is continued.
I looked at other products on their site, but none of them mention the cable type so there is no way to know.
I don't really need a workout solution, I have the JLab Epic2 (wireless) for that, which is the absolute best in its class. Perhaps only beaten by JLab Air (fully wireless).
Eventually I have decided to give up and focused on other things like weight, comfort, cable material, microphone, remote with buttons to take/end calls and skip tracks + volume and play/pause.
My search (spending hours and multiple days) lead me to:
1. BeyerDynamic Byron (€47) - for every day use and work (making phone calls) and short business trips. Heavy use means risk of loosing or damaging them. These ones are not that expensive so I can take risks with them.
2. 1More Triple Driver - more expensive (€88) but amazing built and sound quality. Still lightweight. I will use them to enjoy music or a movie. But I won't use them often, keeping it exclusive.
I do not regret my choices, the BeyerDynamic Byron has its mic/remote on the left side, exactly what I was used to with Y cable inears. The fit is perfect and sound quality very good. The 1More clearly a step up, you hear it immediately.