Audyssey One has been replaced with a more sophiosticated version "A1 Evo" and is no longer being maintained. You can find A1 Evo tutorial and download link here: th-cam.com/video/lmZ5yV1-wMI/w-d-xo.html OCA
I'm a software engineer but not in terms of audio. I have been one since the 90s and I can tell that you live and breath this... and I thank you so much for your time and effort... My Denon 3800 is unbelievable and I have the stock Audyssey setting still as a preset and I cannot stand it anymore after hearing what Audyssey One can do. Thank you!
Thanks, and well done sir! My home theatre has never sounded better! My only regret is that I've been missing out on this phenomenal sound for so many years.
I finally found the "contribution button", thus want to say thank you for your great work, patience and motivation to update and improve your script. My results are so great that I already sold my Dirac Licence. Next step is to get a second subwoofer, looking forward how A1 wil handle and integrate it.
Happy Anniversary, Serkan! Audyssey One is two months old today, and I think it's safe to say it has taken the world by storm. Many thanks, again, from all of us. 🥰
Yo...I love you man. I just moved to a new place and over here I was having struggles with Audyssey and the performance of my subs in my new living room. Your tool fixed it. Thank you x1000. This is pure magic.
This is AMAZING. I wasn't expecting such an obvious audible difference after optimizing but holy heck I'm hearing a 3d surround image far beyond anything I heard before. Thank you for this!
Copy/pasting the links in the video description also here as some of you have problems with those: Download Audyssey One v1.3x (Latest - 23 May 2024 11:15 CET) drive.google.com/file/d/1O-yRmbahRFjj0flX_kfgFDj3vrQwvZYq/view?usp=sharing REW Beta 21 (guaranteed to work right with the script!): Windows: drive.google.com/file/d/1g-vX91fC3xjMIrz7KgB_HNhablx2ph36/view?usp=sharing Mac: drive.google.com/file/d/1U2Gxepsm_XzU6i_Q2G-PlQxRnus_8SSF/view?usp=sharing
Awesome! Unfortunately, the link in the main description does not work for me. "No file found" but maybe I missed a download address somewhere else (in the comments or so?) I would really appreciate, if you could count up versions. It is just so confusing to have the third, fourth, fifth, … version with the exact same number 1.3x. I know, no major upgrade, but to my mind every change in the code would justify a 1.31, 1.32, 1.33, … Common Software Convention ;) Have a nice day and a big cheers
Which is not even close and and rather unintuitive. Version numbers were invented for a reason. But hey, your software, your rules. No offense, just a hint to a better user experience. And as i speak about that: your software is awesome - the whole publishing with links (mostly not working) in the description, on youtube, within hundreds of comments is (sorry to say so) a total mess! Unworthy for such a beautiful piece of software and a real pitty. Even though I try to follow changes and comments, I feel more and more totally lost on what changed with what, which version of rew to use, … Crawling through a ton of contradictionary descriptions and comments … Feels just very frustrating and please let me assure you, that I am not alone with these feelings. Again, no offense. By the way: the link in the description to Google Drive is not working. At least for me it is not. Love your work! Hate the way it is published and maintained. Cheers and have a nice day! :)
@@c.o.s.softwaregmbh9247 Thank you for your feedback. I understand your concerns about the versioning and the organization of information regarding the scripts and REW versions. The version of REW used in these scripts has remained consistent as Beta 21 since the very first launch two months ago. Recent beta releases of REW have introduced changes to their API handling, which can cause compatibility issues with older beta versions. As a result, I have been providing links to the specific REW Beta 21 installers for Windows and Mac within the scripts themselves, as older beta versions are no longer available for download from REW's server. I appreciate your point about version numbering being a standard practice for better user experience. However, in this case, I have not changed the version number as the underlying method and functionality of the scripts have remained the same. Regarding the confusion around download links, you're correct that the video descriptions may sometimes link to outdated versions due to browser caching issues. The chaos in the comments section is a result of me personally replying to each and every one of over 2,000 comments, unlike most other channels. As an independent creator managing this channel, I could explore hosting the files elsewhere to improve accessibility, but my primary focus is on providing free tutorials to the audio enthusiast community, with view count being the primary metric for reaching a wider audience. I'm glad to hear that you find the software itself useful. I acknowledge the frustrations caused by the organizational challenges you've highlighted, and I appreciate your constructive feedback. Rest assured, I'm continuously working on improving the user experience while balancing the demands of managing this channel as a solo effort. Thank you for your understanding and for your kind words about the software. I hope this explanation provides some clarity, and I welcome any further suggestions you may have.
'I used to be deaf, but now I can hear.' Thank you so much for this adjustment. It saves me a whole 700€ for Dirac Live. I never imagined that such incredible sound would be possible in my living room, which has extremely poor acoustic properties. Now, listening to music has become downright addictive. I finally understand what 'soundstage' means. Earlier, I actually had to get up from the couch and listen to my center speaker because I wasn't sure anymore if it wasn't playing along, even though I was listening in stereo 😂. Wow, you did just an incredible job on this. Can't thank you enough.
Script updated with some additional info on crossovers. Multiple subwoofer distance problems should have been completely eliminated now. As an added bonus for all the inconvenience, this one is about 25% faster ;)
Perfect timing for this. Just finishing measurements in directional and standard modes. I would be happy to provide those for your review. Certainly trying the script by myself soon.
Already done with the new script and everything is perfect! I don't know what else you will bring us in the future, but this is the best calibration that my system has so far! 😄Cheers!
Going to remove mini dsp and mso and try new script, I’m thinking bass may be better, as of now I run audyssey with script over mso I’m also thinking I may get better sub mains intergration
I run REW measurements after the script. I found out that subwoofers levels were too low almost 10dB. Maybe LFE used on measuring and when lining up with the EQ target overall level stays too low. Easy to fix by raising all subs, but maybe would be better to update the script to take care of this.
Thank you so much for your work so far, looking forward for a way to apply more manual more gentle PEQ above 100 Hz. Can’t shake the feeling that it’s the one thing my system is missing right now.
Denon and Marantz should contact you and hire you as theyr sound engineer . Really awesome sound. In my many years of home cinema at home i didnt get close to these results here with your optimization . Really awesome and remarkable what you achieved . This video sould have millions of views
I have a lot of suck out between 60 and 80hz with dual subs (15" & 12"). Would you recommend buying a minidsp to first align the two subs as 1 before running audussey? Or something else I can do to achieve a better response? Unfortunately, moving the subs isn't an option. Thank you for your work, fantastic results.
I tried the script, it was crazy easy for the great sounded results I got. Maybe the issue is on me. I did 3 positions at MLP. Maybe I can try for 8 all around the MLP. Results sound great. Theoretical graphs look like they could improve. I love numbers and graphs and tend to strive for perfection too much.
8 point measurements would improve things a bit. The best sounding filters will not look the best visually. I have explained in this recent video why you shouldn't correct above 200Hz unless you have really bad speakers: th-cam.com/video/qoFZPlXrTeM/w-d-xo.html @@burtonscustom
@ocaudiophile it's the 60 to 80hz that I'd like to improve. Just wondering ways to possibly improve on it. Thought maybe a minidsp would allow for more calibration before running audyssey. Regardless, this is my new running calibration. Already watched two movies on it. Very happy.
The dip you observe there is a room mode (some bass waves reflected from the walls cancelling each other out), is determined by your room dimensions and will not go away even when you change your subwoofer and LP location, although might improve. Best remedy is adding another (or more) sub. Trying to correct it with a boosting filter will only make things worse (introduce distortion to the SW) since you will also boost the cancelling wave. There's only some much digital filters can do. On the positive side, we don't hear the dips as much as we hear the peaks. Most sharp dips you see in the magnitude response are inaudible to the ear.
Thanks a lot Serko.. My system never sounded this good in years. I tried many things like MultiEQ-X, Spatial toolkit, Magic beans.. Nothing ever worked (and quick) as with A-1.. Thanks so much again.. Keep up the great work
Audyssey One will provide perfect Dr Toole target curve response at 75dB (MutlEQ Editor app measured level, -30dB on the receiver scale) at Audyssey Reference setting with Dynamic EQ, Dynamic volume and LFC all off (default). But if you are somehow not satisfied with the outcome or desire certain changes including the ability to use Dynamic EQ, here are some tips to manipulate the sound. * If you want to take advantage of Dynamic EQ and prefer the higher bass output of Harman Kardon target curve, the settings below will get you the closest system response to Harman curve at 75dB: Audyssey settings¦ MultEQ XT32: Reference, Dynamic EQ: On, -Reference Level Offset: 5dB, Dynamic Volume: Off, Audyssey LFC: On, -Containment Amount: 1 Surround Parameters¦ Cinema EQ: On * You find the sound too bright: "Cinema EQ: On" setting will dim high frequencies gradually from 1kHz onwards by about 4dB at 75dB volume level * You want more bass but not Dynamic EQ or Harmon curve in particular: Increase subwoofer volume level Try inverting subwoofer polarity (there have been cases where Audyssey got it wrong in the first place and A1 doesn't check for that at this time) "Dynamic Volume: Heavy" setting will tilt the sound response to provide relatively more bass PS: The effects of the above parameters have been tested directly from preamp outputs of a Marantz SR6015 and may not fully reflect your speakers' in room response.
Thenks for this. This is a tremendous amount of work. What if I live in an apartment and i listen to movies at a moderately low levels? Around 60-70 dBs with peaks to 85 or so? I like to use Multi EQ as it ups the base at low listening levels. Is it ok to leave it on? P.S. As we are using AVRs mic for measurement, will we get worse results than if we would have used UMIK1 and REW Manual calibration from your previous videos?
I’m surprised at leaving the LFC on with a containment of 1! What’s the benefit there OCA? Just curious. Been using three settings since you posted and sound okay. Tempted to lose the LFC though…
OCA, dont mind saying again, you are truly amazing. Not only with your knowledge/passion on the subject, your willingness to share with others and patiently answer any questions thereafter! Those who are enthusiasts in the field will understand the value here. Thank you!
OCA, I have 2 subwoofers in my setup and in the speaker configuration use 2 subs. My ZIP file that is created with the ady responses shows only SW10 - SW17. Will the algos you have implemented see this as 2 separate subwoofers and still be able to create individual adjustments?
There should be only one sub in the zip, this is ok. Audyssey uses only one filter for the combination of the 2 subs and this cannot be changed. The filter the script creates are in fact for both subs. So, in short, it will do everything correctly for you and it will keep the relative distance and volume settings between the subs intact so as to keep the accuracy of the filter (because the imported sub response is the result of the two subwoofers with these exact settings only)
Thanks for the prompt response. A few more observations. 1. The bass response has been the lowest with 'One' compared to any of your other methods. Same original ADY as input. Any thoughts? 2. There are literally no filters at all between 300hz to 3khz. The Immersive Audio method yielded filters in that range. Target curve differences maybe? 3. The sub distance has to be increased as I have verified with REW in the past. Here it tried to set 7.8m which is limited by the 6m limit. Then it set it to 1.08m!. This is even lower than 4.86ft that Audyssey calculated. What do you make of this? Again, the workflow was a breeze and fun to execute. Thx!
Thank you very much with your generous contribution, OCA. My system never sounded better than now, it's amazing how immersive, precise and clear turns out the sound while watching a movie or listening to music after using A-1, even in a really small and complicated room with a 5.1.2 setup.
Thanks for the hard work, really amazing result's. One question I have up firing Atmos speakers. Your script set them at 80hz but Klipsch recommended 120-140hz, should I change them?
If One calculated 80Hz for them, they must be going down that low in their measured response, you can check that in the graphs produced at the end of the optimization procedure in REW "All SPL" tab. It's quite common for speakers to produce more bass than their spec due to wall gains, your Atmos speakers are probably close to some wall surfaces. Both the speaker and the amp will benefit from raising the crossover frequency higher due to decreased loads so feel free to try. The only concern is that Atmos enabled speakers already have issues completely re-directing sound to the ceiling and XO at 120Hz would increase localization of the signals a bit more towards the floor. I'd listen to both options and decide by ear. The test tracks I supplied have a lot of Atmos height content. They could help with quickly spotting the differences.
Thank you for your incredible work! I exported the .ady file that I currently use on my setup, and AudysseyOne set the crossovers on my LRs and surrounds to full range (they certainly aren't full range speakers). Do I need to take a fresh set of measurements?
Are your speakers at corners and very close to side or rear walls? The crossover calculation algorithm is certainly seeing your speakers produce sound down to 20 Hz levels to decide them to be full range. There's no harm in changing XO frequencies manually btw. Cutting everything at 80Hz is not a bad idea for instance especially for movies. Let me how it unfolds after a new set of measurements.
@@ocaudiophile"certainly seeing your speakers produce sound down to 20 Hz levels". I don't think so, the input graphs show my surrounds struggling below 50 hz. I'll file a bug report so we can determine if there's an issue.
An important update has been made to the Audyssey One script v1.3x today: It's been acknowledged that MultEQ Editor app (and MultEQ-X as well) does not allow for a "soft" change in subwoofer polarity. A1 will now ONLY provide advice if it detects potential benefits from switching subwoofer polarity, indicating it should be done directly on the sub(s). The script remains unchanged and identical in all other aspects, and if you weren't prompted by A1 to invert the subwoofer polarity before, there's no action required on your part. Apologies for any inconvenience this may have caused. OCA
Thanks OCA! My script keeps getting stuck on "Optimization process (version 1.3x dated 14 Jun 24) started... 5:52:36 PM [LOG] Transposing measurements from '3' different microphone positions to the primary listening position..." and eventually says "load failed". Can you help troubleshoot?
This is fantastic!!! Anyone who follows your work knows the importance of this automation. Thank you very much, you don't exist. I can't contribute at the moment, but as soon as possible I won't forget someone who does this work out of pleasure and is so little recognized. THANKS.
I was actually looking into making something like this myself. I'm glad someone did it so I don't have to :). Great work, guys. You are changing the game of calibration 100%!
Attention multiple subwoofer users: I "might" have found a bug that can affect multiple subwoofer relative delays in some models and have updated the script just now (15:15 CET). This "could" change multiple subwoofer performance considerably. Please run the latest version and let me know if you will hear any difference. Single subwoofer systems (including multiple subs through a MiniDSP) have not been affected from this bug and they don't need to do anything.
Was there a rule that custom distance sub 2 + delay adjustment sub 1 should equal the total distance? The new script looks like custom distance fields were removed entirely. Distances are both 5.19 and audyssey app shows distance of sub 1 as 0 and sub 2 as 0.1.
Yes, that's the bug I am talking about. Some models require customDistance setting and channelReport.distance to be 0, some others only take the distance value from channelReport.distance and ignore CcustomDistance setting value so I removed customDistance from subwoofer altogether. WHat do you see in the AVR settings when you transfer the ady? @@burtonscustom
Hi! Thanks a lot for this script. I'm been tinkering with my home cinema for years and recently set up 7.2.4 with a Denon X3600H and external amp for the L+R speakers. Subwoofers with miniDSP and MSO but this time I'm running them bare. Comparing with my previous Audyssey XT32 efforts the new calibration without using your script and correcting to 300 Hz was already an improvement. After some hickups of One Drive corrupting the optimized ady file and my subwoofers measuring 45 dB too loud and with too much delay, I got it working with some hacks. Your optimized filters sound the best, by far, of what I've experienced anywhere so far. I use several movie scenes and opening logos I know intimately and they got significantly more clarity. I can pick up details of things in the background I've never heard at all before. Voices get clear as day (Blade Runner 2029 opening for example). Bass is much more defined, confined and I can feel it right for the first time. I still have comparisons to do with my UMIK-1 for spectrograms but so far this is remarkable. Thank you so much!
I was shocked at the extra detail and clarity, I’m running mini dsp and mso for a nice response over 2 seats and run audyssey and script over that, now I’m wondering it could be even better if I take mini dsp out and just use my 3800h sub outs
Hi!!! I have a problem with the optimized file in the Drive or I have a corrupt file message... How did you go about solving this problem please? I've been struggling since yesterday.... Your help would be invaluable...
The script has been updated today, incorporating the following enhancements: • Introduction of a version number for improved user tracking (line 109 in the code) • Significant revisions to the crossover frequency calculation method, resulting in enhanced consistency. • Elimination of setting any speaker to Full Range, ensuring that bass is exclusively managed by the subwoofer, which is optimally filtered. • Implementation of a warning system for cases where volume adjustment for a subwoofer (or subwoofer combination) exceeds the AV Receiver hardware limit of 12dB. In such instances, volume is adjusted to the maximum permissible level, allowing optimization to proceed. • Introduction of a warning mechanism for cases where volume adjustment for a speaker surpasses the prescribed limit. This is typically indicative of a faulty measurement process, but was seen in rare cases. • Removal of irrelevant data from REW before the optimization process concludes. ***If you're running into memory problems due to too many speakers, install REW with max. memory option of 3GB. In my tests, it only touches above 2GB usage for a short time. Better yet, you can right click on the REW shortcut, select properties and replace Target setting box like below: "C:\Program Files\REW oomeqwizard.exe" -J -Xmx4196m -api" This will ensure REW will always start with 4GB of memory allocation and API server running.
It's quite a bit slower than the previous one, doing a lot of extra work for crossover calculation but never crashed in my pc. Can you share your logs or your ady?
I think I know why, probably REW default memory allocation is insufficient for the number of measurements you have. Did you set it up at the max 3GB during installation?
Audyssey One has been updated to version 1.2 drive.google.com/file/d/1qnFTmS1687dnYYP5nORx3W1CTF3nQgiq/view?usp=sharing today with the following improvements and revisions: * Subwoofer volume alignment frequency range has been modified from 22.3Hz - 178.2Hz to 28.3Hz - 226.3Hz. This change may result in a slight increase in bass response for certain audio systems. However, if desired, the previous frequency range can be reverted by modifying line 625 of the script. * The calculation of crossover frequencies has been optimized for faster performance and reduced memory usage. As a result, there is no longer a need to increase REW's memory settings. Additionally, the calculated crossover frequencies are FINALLY completely accurate to five decimal places for every possible system configuration. * To minimize driver loads and increase clarity, any calculated crossover frequency below 80Hz will be automatically raised to 80Hz. * The logging functionality has been enhanced, providing some additional enthusiast information. * A timer has been implemented to report the total execution time at the end of the optimization process. To do: * Implementing an exhaustive subwoofer alignment process with iterative targeting of minimum total phase delays at the crossover frequencies. Assistance from experienced coders is needed, as my hopeless attempts today have resulted in multiple REW crashes. * Enabling manual optimal relative alignment of multiple subwoofers by taking Audyssey measurements in 'directional mode' and then switching to 'standard mode.' However, it is uncertain whether Audyssey will accept running the calibration in directional mode on older receiver models, even if the mode can be activated through the app."
Hi great channel and very inspiring to me as I've just got the umik-1 also. Just tried yesterday before the update yesterday and now tonight already 2 updates after my first calibration amazing support. Saw some of your other videos and have some questions. I wil totally start over calibration again with my Denon AVR 4400H. Do you recommend me to calibrate the audyssey mic against my umik-1 before starting this software? Should I take 3 Audyssey measurements at the seathing position at the same spot without moving the mic or 8 measurements same spot without moving the mic? Or do you recommend to move the mic and how many measurements to take. Also had former added Curtain to the final audessy XT32 calibration at 300hz are this necessary with your software? Great work 🎉
If you will use REW and Umik, then take just 3 measurements with Audyssey (the bare minimum) all at the same mic position. They will only be used to generate a dummy app for REW filters. When measuring with REW, you can take as many as you want. Repeating measurements at the same mic position also helps increase signal to noise ratio of measurements. The method is detailed in the Audyssey ART video and the Immersive Audio videos. @@dennishlarsen
Strange, line 109 says: // **************************** version 1.1 18 MAR 2024 - 21:25 CET ************************************ Is this msg the same in all Versions? Perhaps reposting the google drive link... @@ocaudiophile
A1 will work with any number of mic positions, so you can stop after the 3rd round if you so wish. You'll have the best sound (but only at a single location) by keeping the mic at the exact central position at ear height and repeat all 8 measurements without moving the mic.
I just tried this method. So far its outstanding. I use Star Wars Battlefront Dolby Atmos demo, more subtle audio all around. Will try regular movies as well.
Simplemente excelente Script, ahora tengo un sistema de audio del cual puedo disfrutar todo su potencial. Voces nítidas, bajos contundentes, sonido sin distorción, feliz con mi nueva configuración. Felicitaciones!
Thanks. Need help. Ran into a problem. 1.3x stops saying subwwofer level is too low. V 1.0 used to work fine. Tried with fresh set of measurements in the audyssey app. If I get to the red band, audyssey doesn't work. Anywhere in the green band, sub level seems too low to audyssey one. Could you please share link to v1.3? Running Denon avr x3600h with SVS SB1000pro. Grateful for your help.
Also, forgot to tell you, I am running audysseyone ver 1.0, and I substituted the Half Witledge Curve from YSR forum for the Toole curve. I am not a purist, and this isthe most awesome my system has sounded yet. A1 v1 delivered a fantastic optimised file. Thanks again.
@@ocaudiophile Oh! OK. Sorry but I didn't think you would reply. Got a fresh set of readings but the sub woofer level is close to the upper end. Will run it all again. Again, great work.
It looks really good, unfortunately it doesn't work without a subwoofer. I don't think it's mentioned anywhere, would it be possible to add this warning stoneware? Really impressive work, not for me unfortunately.
Minor bug fix to Audyssey One v1.3x today. The bug was affecting ONLY SOME MULTIPLE SUBWOOFER systems connected directly to the receiver (i.e. not through a MiniDSP). If you are using A1 with such a system, you will most likely benefit from running the revised script. Download link is unchanged (in the video description): drive.google.com/file/d/1O-yRmbahRFjj0flX_kfgFDj3vrQwvZYq/view?usp=sharing PS: For peace of mind, please keep using REW Beta 21 until REW Beta releases finalize. Some Beta versions may yield different results and/or throw errors.
Got an error "TypeError: customLevel[j].toFixed is not a function - program execution has stopped!" on the new script. Looks like the new code is getting caught on a type conversion on that customLevel array somewhere. This is running an ADY that worked fine on all previous versions of 1.3x.
Hi OCA, thx for the update again. It sounds really good with good bass (Harman Curve), but I noticed one strange thing: previous version said: "[WARNING] Calculated optimal subwoofer distance of 6.68m exceeds AV Receiver's max. speaker spacing limit [5.42m vs 4.02m]!" But your latest version says this: "[INFO] Subwoofer distance is 'optimally' set @ 6.68m and is 'safely' within the AV Receiver's speaker spacing limits." Makes me wonder.... is it a safe distance or not? It is also the first version that tells me to invert my subs. Which makes the bass less good... Rest of the corrections are exactly the same.
Thanks a lot @ocaudiophile for your work ! it really helps my X4800H so much that I don't feel to cash out USD600+ on DL+DLBC 😀Some doubts, Audyssey One got my XOs for my 5.2.1 at 40Hz and sets 80Hz to relieve the stress on the amp which is fine for me, does it means that I'll get a bit more bass between 40-80Hz ? And another finding my X4800H never sends the customDistance parameter so I have to type the Center distance to MLP, my NR1711 does but why I did find in the MultiEQ App is that the Sub distance is set for X4800H and below 6 meters (3.98m vs 3.52m your scripts calculate) do you think MultiEQ App is stripping some info before exporting .ady files ? TIA
Your welcome! A1 confirms that you are safe down to 40Hz XO with these speakers but less or more bass will depend on their phase match with the sub(s), you need to try both 40 and 60Hz and listen (or measure with REW) and compare to be sure. But the lower the XO, the more load on the speaker and the 4800, that's a fact. If center speaker distance is being asked, that means Audyssey during the calibration run maxed out your SW distance and deleted other speaker distances. It will show you distances in the app but they are calculated by the app after fixing SW at max. If A1 could set your SW distance afterwards, there's nothing to worry about. Script calculation is robust (it matches impulse responses). Also, if you edit distances in the app and re-save, then they will also show up in the ady and you will not need to enter anything manually.
@@ocaudiophile Thanks. I'll take some REW sweeps before and after A1. A preliminary sweep of my R channel shows lower bass compared with the O'Toole target at drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link please note that sweeps were taken with a UMIK-1 instead of the MultiEQ Mic
@@ocaudiophile Thanks ! I'll take some REW sweeps before and after A1, preliminary sweep with a UMIK-1 shows a recess on bass compared with O'Toole target at drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link C channel distance was set a 1.77 meters. drive.google.com/file/d/1IuIkxasURtML2cwwFXvmXoTiIYGObipS/view?usp=drive_link
@@ocaudiophile Thanks. I'll run sweeps before and after A1, preliminary sweep on R channel shows a reccess on bass response compared with O'Toole target as in this image: drive.google.com/file/d/1IuIkxasURtML2cwwFXvmXoTiIYGObipS/view?usp=drive_link The whole sweep and .ady files are here, please note that REW sweeps was taken with a UMIK-1 not the MultiEQ mic: drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link BTW I'm having some troubles posting comments, not sure is my Adblock systems or what.
@@ocaudiophile I have problems to post comments they disappear. Trying to post my G Drive with REW measures before and after A1 comparing Reference, Flat, etc
I have an X3600, it is on latest firmware and using the IP lookup it is definitely 300M/S. looking at the script it is not one of the exceptions, can it be added (or is there a way I could add it manually)? Also, the video does not mention taking the audyssey measurements but I guess we need to do an 8 point measure grouped at MLP and then upload the ady?
Yes, you can edit the code in any text editor, i.e. Notepad and save and it will continue working. The receiver list is at line 121. You can take as many measurements as you want (Audyssey will require a minimum 3 to end the process though). If the listening area is small, 3 would suffice but the more the better of course.
Minor updates and enhancements have been implemented in the Audyssey One calibration optimization tool today (v1.3): • The anti-"high frequency roll-off" filter has been recalculated from preamp outputs and now "completely" eliminates the reference curve effect on speaker responses. • A1 v1.3 detects whether the subwoofer polarity determined by Audyssey needs inversion and automatically inverts it using ady file parameters, resulting in potentially improved bass response in certain systems. • Upon completion of the optimization process, a copy of the full optimization log will be saved on your computer as a text file for your reference. • Root causes have been included as informational details in system logs to help with some common errors. Version 1.3 has a distinct link provided in the video description, while the link to v1.2 will remain accessible to prevent browser caching issues when transitioning to the updated link. drive.google.com/file/d/1x3_c_MSwIYymxQbhiY7zvtykV_hwwUX2/view?usp=sharing
Hi OCA, thx so much for this. New version already! I tried it, some different results it seems but the only thing that's get's downloaded as a result is the log file, not an .ady file...
@@ocaudiophile Hello. Thank you for all the work and dedication you've put into this. I do have a question about v1.3. I ran the script using v1.3 and it stated it inverted my sub. Ok. I uploaded that .ady file to the MultEQ app, but I noticed all the graphs in the app look the same as the .ady file I made with v1.2. Would that sub inversion be visible somewhere in a graph, whether it be on the app or REW? Did v1.2 also Invert my sub and that's why both look the same or is that only a v1.3 feature? I just want to know if to leave the .ady file I made with v.1.2 or if to replace it with the 1.3 version. Hope that's clear.
Script updated just now with a fix for multiple sub distance settings transfering incorrectly to certain models. Please give feedback and share your ady file if you are still seeing subwoofer distances as 0 in your AVR setup menu!
Hi and good morning. I answered some minutes ago, but the post is empty. I try it again. You had hard days and you are very very engaged. Thank you. Here are the files with the last three updates from your script. (drive.google.com/drive/folders/1sNJfIeK2LKasAzcml82oTdF2Q33zk8k5?usp=drive_link)
Bitte testen Sie erneut mit dem neuesten Skript, das vor wenigen Sekunden hochgeladen wurde! Lassen Sie mich wissen, wenn das Problem weiterhin besteht.@@777Gurus
I run the script on standard mode measurements. Work's very well and I have better results than before. No problems with sub distances, but unfortunately there's dip on freq response. So alignment is not optimal for that. Timing is much better now than before, but again it's mostly because I have moved subs closer to MLP. I tried directional mode, but script gave me an error. I would like to see how I could use individual measurements from each subs to achieve best combined results. My plan is to run subs always on standard mode. Maybe I could use measurements and manually align+eq them in REW, then upload parameters by using MultEQ-X. Once more. Just great work and thanks!
Dude! This latest version is just fantastic!. I've had to make a few changes since my open floor plan is a mess, acoustically. limited gain to +6db and had it correct all the way out to 20,000. The default toole curve is "ok", but I did swap that out to a older school harman + toole curve under (100hz the bass is increased quite a bit) is the main difference. With these changes, it's a MARKED IMPROVEMENT over anything I could get MultEQ-X to do.
@@ocaudiophile Hi OCA - quick question in your opinion Would using the MultiEQ-X $200 PC version along with A1 make a better difference - rather than the Audessy App $20 & A1 ? Just Curious to know.
Very Important: First off Audyssey One is amazing, and my system sounds even better now! But, make sure to use the same REW version that OCA has set! Don't be like me and make that mistake I was using REW Beta 28 (just downloaded most recent since Mac link wasn't in TH-cam description), and Audyssey One was setting all crossovers to 150hz in the logs. This was odd because I did an initial sweep and separate measurement and it measured my L+R mains down to 30hz flat in my room. After downgrading back to REW Beta 21. Audyssey One put them closer to 40hz crossover. So if you are getting very high crossovers make sure you are on right REW tested version.
It was working fine to up to 26 and then 27 and 28 suddenly changed things. Beta is a work in progress so sticking with 21 until it all settles seems to be a wise decision.
Thanks @bungatown. But where did you find the REW Beta 21? I can only find the latest Beta version (currently 67) for Mac. OCA's googledrive link for Mac is broken...
Minor update for Mac users just now: Some Safari browsers were only saving the logs but not the ady file at the end of the optimization. This must have been fixed with this update. Please notify me if the issue continues (I don't have a Mac to try).
Hi OCA! First of all a massive thank you for this! My sound stage is noticeably larger and there's a clarity in my speakers that sounds amazing! Just wow! :D I do have a Mac and when running v1.2 it creates an ady file ok. However, after just now running v1.3, a log.txt is generated and downloaded but this is still no ady file. Hope this helps! :)
@@ocaudiophile Hey Serkan, I just checked to get you some more input. In V1.3 only the log file gets saved. Version 1.2 works flawlessly on Safari because there's only the .ady file to be downloaded. So I guess Safari has an issue with the second download, which does not make very much sense as at the beginning of the optimization Safari has no issue downloading the extracted measurements and the target curve... TH-cam should allow you to search in the comments or we could start a FAQ, I just searched the comments as after changing the Level on my Arendals to reference level with a new Audyssey calibration the text box regarding the sub delay appeared. I wanted to ask which is better without the text box and alignment on the second attempt or with the text box on the first attempt. Luckily you are so supportive and answer every comment so I already found your answer in an older comment. Very happy with the results! "User input requirement has no effect on the optimization. It only means Audyssey couldn't align your subwoofer. If the optimization completes with success after that, it means A1 could align your sub. FYI, with or without the user input, the most important factor is how many attempts did A1 take to align your sub. If your sub is aligned in the first attempt, that almost always means remarkably better bass performance compared to the next two attempts."
Hi OCA, Yesterday I did try to V1.3. I am only using one subwoofer. Still it inverted my subwoofer. Why it is so? I never feel to invert my subwoofer. And A1 always set trim of my LCR to positive 3 to 5db. In addition, in my LR speaker crossover point there is dip of 18db. Which Ady mobile app corrected in calibration but A1 didn't. Any way to calibrate full spectrum i.e 20hz to 20khz?
I just wanted to say after using this after week it's FREAKING INSANE - when playing halo I now get much more directional feedback on where grenades blow up, the bass kick so hard i can feel it, lol and it scares me sometimes lol in Ready player one i hit 125 db in my MLP lol not only is bass cleaner and hits hard it also doesn't vibrate things like it used too!!! I deffineently think my room treatment is helping ady and your scrim get the best out of the system!!!
Hey OCA! Long time since the last adyssey video! Wanted to ask if this correction technique would work the same if we feed the script rew manual ummik1 measurements, instead of the avr default mic ones, and use the values of the generated ady file to insert in our multq x pc app? I guess it wont work cause of the high frequency rolloff compensation? Is there a way to mitigate that for multeq x users? Thank u in advance for any feedback! We much appreciate your efforts for the Audio Valhalla
Dear John, I cannot decrypt the "mic calibration file" embedded in mqx measurements (they have used SHA 256 encryption) although I can read mqx measurements and import to REW. The response will always be a little off by an unknown mic cal amount. It's possible to decrease its effect by using the standard Audyssey mic cal file as a dummy but this wouldn't make guys like you very happy! Hence the lack of support for mqx in my script. Since the filters are not produced by REW EQ but pure inversion, there's no way to export them as biquads to x, either.
One benefit for you would be using the volume settings found by the script and use them in MQX as base. The volume alignment in the script (including SW volume) is state of the art and cannot be matched manually.
@@ocaudiophileI think we can make the script work all the same, if we replace the exported ady measurements with our rew ones (i guess we need to name them as we saw in the video). The only thing that i need to try this out, is if you can tell me what line of code should we look to change for the high frequency rolloff compensation you are deliberately making, can you tell me where you are making this so i can disable it for me?
As long as you keep the responses data at perfect speaker norm, you can use any filters you want with the script including filters based on REW/Umik measurements. You just should not use mqx measurements. Anti HFR1 is the additionalRows constant at line 822, delete that and it will no longer be applied.@@johnaps
@@ocaudiophileI will not mess with the editor app nor the ady file, so i guess i can just use the script to do the rew corrections to my measurements automatically, and then populate the results inside my multq x app! Perfecto! Will try it out today
I've had some issues with my Audyessey app recently where the connection between the app and receiver has dropped out around measurement 7 or 8. It's been incredibly frustrating, and having to run the calibration up to 4 times to get a reading has left me accepting whatever sound quality I could get from the process. I spent 10 minutes last night using the tool from this video and wow, just wow. It's like I just bought a brand new setup, the clarity is nothing short of incredible, I was a little put off by what I perceived to be lower sub output when trying out some test scenes, but with some more testing I see now that the balance of the sub and speakers is utterly perfect. Cannot recommend this enough, it's a life/game changer. Kudos to you sir!
"Audyssey One" minor compatibility update today (v1.3x) * Updated to address ongoing REW Beta API changes. Please use the provided REW Beta 21 link within A1 until the next update ensures compatibility with the latest REW beta versions. * Revised default Dr. Toole target curve for roll-off filters in your receiver, providing full flat response throughout the audible frequency range. * Optimized subwoofer volume level calculation algorithm for increased compatibility. Link for MultEQ Editor app Android version with no subwoofer volume -12dB bug: drive.google.com/file/d/1--DP4H6SZcIQN1i3pRyXdEY18Aa9v9fO/view
Looks like your amazing work is kinda being hijacked. Been a follower of what you do for some time now, and it is quite astonishing. Not that I understand it all, but fascinating nonetheless. Being older I finally got to assemble my dream music/movie system, and you videos are invaluable. Can't believe you give this info away for free. But, it appears that at least one other youtuber (that I know of) is referencing your hard work to boost their own channel. Not nice in my opinion. But I am older and maybe I am getting it wrong. He does give full credit though. Anyway, huge thanks for this, very much appreciated. J.
He's helping people with questions on A1 and also running a facebook page. I cannot cope with all the requests on my own so I am happy with his engagement ;)
***Important: I have figured the reason behind the rare 0m distance problem thanks to calibration file shared by @matten545. If Audyssey measures your subwoofer's actual required delay (distance) higher than the 6m speaker spacing limit, it will set all speaker distances in the ady file to 0!!!! The app then sets the subwoofer distance to the maximum allowed and fills up the rest of the speakers accordingly. The only work around that was to ask the user for a distance estimate which is now added in the script. So, if the script is asking you to manually enter your center speaker distance, it's ONLY because even Audyssey has found that your subwoofer requires a delay larger than the maximum distance limit.
@ocaudiophile I'm not sure is the only case because in my case the App reports 3.98m but inside the .ady file all delays are set to 0. Linked the .ady file and a screnshot of the MultiEQ file. And many thanks for your great work ! I tried to find where in the files are the distances that the screenshot shows without success. drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link
I saw a comment from you to not use a modified .ady file, so I took a new set of measurements this morning and exported them from the app. This set most of my distances to 0, and my L/R to full range with 20hz X/O. Center channel to 200HZ. This is incredible work you've done, but I'm unsure if I've done it correctly. I've pasted the log from running the script as a reply to this.
eriving optimal speaker distances through cross-correlation analysis... 8:09:53 AM [LOG] C: 0m 8:09:53 AM [LOG] FL: 0.23m 8:09:53 AM [LOG] FR: 0.13m 8:09:53 AM [LOG] SLA: -0.62m 8:09:53 AM [LOG] SRA: -0.74m 8:09:53 AM [LOG] SWMIX: 0.42m 8:09:53 AM [LOG] TML: -0.44m 8:09:53 AM [LOG] TMR: -0.55m 8:09:53 AM [INFO] Subwoofer distance is 'optimally' set @ 0.43m and is within the AV Receiver's speaker spacing limits. 8:09:53 AM [INFO] Crafting custom room correction filters... 8:10:16 AM [LOG] Done! 8:10:16 AM [INFO] Pinpointing optimal crossover frequencies... 8:10:16 AM [INFO] Crossover frequency for C is set @ 200Hz 8:10:16 AM [INFO] Crossover frequency for FL is set @ FULL RANGE
What model AVR and what version of app are you using? These results would only come out if both your distance and custom distance settings are 0 in the original ady file. You can still correctly set up all distances from the figures produced. Measure your C speaker's actual distance to MLP and add/subtract the numbers and fill all others up accordingly. ie if C is @ 3m, FL should be 3.23, and FR should be 3.13. If you can share your ady file, I will check why this is happening.@@Jkrison
@@ocaudiophile 1.11.1 (3.20.0) is the version of MultiEQ I'm using. Denon X3700H with GSG 18" Martys /w Crown amps, Polk R700's. Polk Legend CC, rest of bed layer also Polk. The original measurements taken put the C at 9.7ft in the app. I didn't modity the distance settings at all, I went straight from measurements in the app, and exported to my PC. I can email you my .ady if you want? Not sure how else to share it.
Stopped by to review the tutorial, one of my SVS SB-13 Ultra subwoofer when kaput, and want to calibrate using multi position multiple sweeps per subwoofer at each position (same as audyssey) choosing the best sweep for each sub. I am the only attendee. Best subwoofer calibration tutorial . 🎉
Amazing work brother, I won’t be using it since I just got my system professionally calibrated but I admire your work and when I get brave enough to do it my self I will definitely go with your file. I watch all your videos learning so much Thank you 🙏
Audyssey One has been replaced with a more sophiosticated version "A1 Evo" and is no longer being maintained. You can find A1 Evo tutorial and download link here:
th-cam.com/video/lmZ5yV1-wMI/w-d-xo.html
OCA
Incredible results in my theater! I don't think I need to splurge for a Dirac license anymore. Many thanks! Please keep up the awesome work.😲
Many thanks!
I'm a software engineer but not in terms of audio. I have been one since the 90s and I can tell that you live and breath this... and I thank you so much for your time and effort... My Denon 3800 is unbelievable and I have the stock Audyssey setting still as a preset and I cannot stand it anymore after hearing what Audyssey One can do. Thank you!
🙏
Thanks, and well done sir! My home theatre has never sounded better! My only regret is that I've been missing out on this phenomenal sound for so many years.
Many thanks for your kind gesture.
Thank you for your ongoing hard work on the script and for sharing your knowledge with us in a easy to use way!
So nice of you
I finally found the "contribution button", thus want to say thank you for your great work, patience and motivation to update and improve your script. My results are so great that I already sold my Dirac Licence. Next step is to get a second subwoofer, looking forward how A1 wil handle and integrate it.
Thank you vm.
Happy Anniversary, Serkan! Audyssey One is two months old today, and I think it's safe to say it has taken the world by storm. Many thanks, again, from all of us. 🥰
Thank you and special thanks for your individual support. Least I can do for such amazing community.
@@ocaudiophile thank you so much! I am waiting for the next update to do another measurement :)
@ocaudiophile This is such an amazing tool. Any ideas how many folks are using Audyssey One? Congratulations on your 2 months anniversary.
@@rafacq Thanks. There's a FB group (I am not the admin) of about 1000 members so safe to say thousands :)
i already know countless enthusiastic users from our home cinema forum in Germany. there are probably a few thousand i guess😊
Yo...I love you man. I just moved to a new place and over here I was having struggles with Audyssey and the performance of my subs in my new living room. Your tool fixed it. Thank you x1000. This is pure magic.
You thought I forgot. I really appreciate the work put forth. Cant wait for your Dynamic EQ update 🥴
Cheera mate!
WOW...O.C.A. I cant believe the work that must have went into this! I thank you for the work!
Very welcome
This is AMAZING.
I wasn't expecting such an obvious audible difference after optimizing but holy heck I'm hearing a 3d surround image far beyond anything I heard before. Thank you for this!
Great to hear!
3-dimensional audio-bubble here
@jdhuisen235 Enjoy
Thanks! You made the process so fool-proof that even an old fool like me was able to get great results. 🤩
Glad it helped!
Copy/pasting the links in the video description also here as some of you have problems with those:
Download Audyssey One v1.3x (Latest - 23 May 2024 11:15 CET)
drive.google.com/file/d/1O-yRmbahRFjj0flX_kfgFDj3vrQwvZYq/view?usp=sharing
REW Beta 21 (guaranteed to work right with the script!):
Windows:
drive.google.com/file/d/1g-vX91fC3xjMIrz7KgB_HNhablx2ph36/view?usp=sharing
Mac:
drive.google.com/file/d/1U2Gxepsm_XzU6i_Q2G-PlQxRnus_8SSF/view?usp=sharing
Awesome! Unfortunately, the link in the main description does not work for me. "No file found" but maybe I missed a download address somewhere else (in the comments or so?)
I would really appreciate, if you could count up versions. It is just so confusing to have the third, fourth, fifth, … version with the exact same number 1.3x. I know, no major upgrade, but to my mind every change in the code would justify a 1.31, 1.32, 1.33, … Common Software Convention ;)
Have a nice day and a big cheers
@@c.o.s.softwaregmbh9247 All versions have a release time/date in them which they also print in the logs.
@@c.o.s.softwaregmbh9247 Which link? They all work for me.
Which is not even close and and rather unintuitive. Version numbers were invented for a reason. But hey, your software, your rules. No offense, just a hint to a better user experience. And as i speak about that: your software is awesome - the whole publishing with links (mostly not working) in the description, on youtube, within hundreds of comments is (sorry to say so) a total mess! Unworthy for such a beautiful piece of software and a real pitty. Even though I try to follow changes and comments, I feel more and more totally lost on what changed with what, which version of rew to use, … Crawling through a ton of contradictionary descriptions and comments … Feels just very frustrating and please let me assure you, that I am not alone with these feelings. Again, no offense.
By the way: the link in the description to Google Drive is not working. At least for me it is not.
Love your work! Hate the way it is published and maintained.
Cheers and have a nice day! :)
@@c.o.s.softwaregmbh9247 Thank you for your feedback. I understand your concerns about the versioning and the organization of information regarding the scripts and REW versions.
The version of REW used in these scripts has remained consistent as Beta 21 since the very first launch two months ago. Recent beta releases of REW have introduced changes to their API handling, which can cause compatibility issues with older beta versions. As a result, I have been providing links to the specific REW Beta 21 installers for Windows and Mac within the scripts themselves, as older beta versions are no longer available for download from REW's server.
I appreciate your point about version numbering being a standard practice for better user experience. However, in this case, I have not changed the version number as the underlying method and functionality of the scripts have remained the same.
Regarding the confusion around download links, you're correct that the video descriptions may sometimes link to outdated versions due to browser caching issues. The chaos in the comments section is a result of me personally replying to each and every one of over 2,000 comments, unlike most other channels.
As an independent creator managing this channel, I could explore hosting the files elsewhere to improve accessibility, but my primary focus is on providing free tutorials to the audio enthusiast community, with view count being the primary metric for reaching a wider audience.
I'm glad to hear that you find the software itself useful. I acknowledge the frustrations caused by the organizational challenges you've highlighted, and I appreciate your constructive feedback. Rest assured, I'm continuously working on improving the user experience while balancing the demands of managing this channel as a solo effort.
Thank you for your understanding and for your kind words about the software. I hope this explanation provides some clarity, and I welcome any further suggestions you may have.
Hope you enjoyed it!
Thanks for freely sharing your obsession with us. Looking forward to the upcoming release.
🙏
Thank you for your support and your commitment!
Thank you too!
'I used to be deaf, but now I can hear.'
Thank you so much for this adjustment. It saves me a whole 700€ for Dirac Live. I never imagined that such incredible sound would be possible in my living room, which has extremely poor acoustic properties. Now, listening to music has become downright addictive. I finally understand what 'soundstage' means. Earlier, I actually had to get up from the couch and listen to my center speaker because I wasn't sure anymore if it wasn't playing along, even though I was listening in stereo 😂. Wow, you did just an incredible job on this. Can't thank you enough.
Script updated with some additional info on crossovers. Multiple subwoofer distance problems should have been completely eliminated now. As an added bonus for all the inconvenience, this one is about 25% faster ;)
Perfect timing for this. Just finishing measurements in directional and standard modes. I would be happy to provide those for your review. Certainly trying the script by myself soon.
Already done with the new script and everything is perfect! I don't know what else you will bring us in the future, but this is the best calibration that my system has so far! 😄Cheers!
Going to remove mini dsp and mso and try new script, I’m thinking bass may be better, as of now I run audyssey with script over mso I’m also thinking I may get better sub mains intergration
I run REW measurements after the script. I found out that subwoofers levels were too low almost 10dB. Maybe LFE used on measuring and when lining up with the EQ target overall level stays too low. Easy to fix by raising all subs, but maybe would be better to update the script to take care of this.
Thanks, OCA! Can you publish your updates to the Github repo? That lets me file PRs against the current version.
Really appreciate taking my sound system to the next level!
🙏
Keep up the good work! Looking forward to your next creation!
🙏
Thank you so much for your work so far, looking forward for a way to apply more manual more gentle PEQ above 100 Hz. Can’t shake the feeling that it’s the one thing my system is missing right now.
Noted! and many thanks for the gesture!
Denon and Marantz should contact you and hire you as theyr sound engineer . Really awesome sound. In my many years of home cinema at home i didnt get close to these results here with your optimization . Really awesome and remarkable what you achieved . This video sould have millions of views
I have a lot of suck out between 60 and 80hz with dual subs (15" & 12"). Would you recommend buying a minidsp to first align the two subs as 1 before running audussey? Or something else I can do to achieve a better response? Unfortunately, moving the subs isn't an option. Thank you for your work, fantastic results.
Let's talk after you try the script ;)
I tried the script, it was crazy easy for the great sounded results I got. Maybe the issue is on me. I did 3 positions at MLP. Maybe I can try for 8 all around the MLP. Results sound great. Theoretical graphs look like they could improve. I love numbers and graphs and tend to strive for perfection too much.
8 point measurements would improve things a bit. The best sounding filters will not look the best visually. I have explained in this recent video why you shouldn't correct above 200Hz unless you have really bad speakers:
th-cam.com/video/qoFZPlXrTeM/w-d-xo.html
@@burtonscustom
@ocaudiophile it's the 60 to 80hz that I'd like to improve. Just wondering ways to possibly improve on it. Thought maybe a minidsp would allow for more calibration before running audyssey. Regardless, this is my new running calibration. Already watched two movies on it. Very happy.
The dip you observe there is a room mode (some bass waves reflected from the walls cancelling each other out), is determined by your room dimensions and will not go away even when you change your subwoofer and LP location, although might improve. Best remedy is adding another (or more) sub. Trying to correct it with a boosting filter will only make things worse (introduce distortion to the SW) since you will also boost the cancelling wave. There's only some much digital filters can do.
On the positive side, we don't hear the dips as much as we hear the peaks. Most sharp dips you see in the magnitude response are inaudible to the ear.
Thanks a lot Serko.. My system never sounded this good in years. I tried many things like MultiEQ-X, Spatial toolkit, Magic beans.. Nothing ever worked (and quick) as with A-1.. Thanks so much again.. Keep up the great work
Happy to hear that!
Been watching your videos for a while and this script just took all the tedious work out of the adjustments. Danke!
Thanks for watching!
Thank you OCA! I could hear the improvement and clarity and mid-high end right away.
Thank you.
Audyssey One will provide perfect Dr Toole target curve response at 75dB (MutlEQ Editor app measured level, -30dB on the receiver scale) at Audyssey Reference setting with Dynamic EQ, Dynamic volume and LFC all off (default). But if you are somehow not satisfied with the outcome or desire certain changes including the ability to use Dynamic EQ, here are some tips to manipulate the sound.
* If you want to take advantage of Dynamic EQ and prefer the higher bass output of Harman Kardon target curve, the settings below will get you the closest system response to Harman curve at 75dB:
Audyssey settings¦ MultEQ XT32: Reference, Dynamic EQ: On, -Reference Level Offset: 5dB, Dynamic Volume: Off, Audyssey LFC: On, -Containment Amount: 1
Surround Parameters¦ Cinema EQ: On
* You find the sound too bright:
"Cinema EQ: On" setting will dim high frequencies gradually from 1kHz onwards by about 4dB at 75dB volume level
* You want more bass but not Dynamic EQ or Harmon curve in particular:
Increase subwoofer volume level
Try inverting subwoofer polarity (there have been cases where Audyssey got it wrong in the first place and A1 doesn't check for that at this time)
"Dynamic Volume: Heavy" setting will tilt the sound response to provide relatively more bass
PS: The effects of the above parameters have been tested directly from preamp outputs of a Marantz SR6015 and may not fully reflect your speakers' in room response.
soll ich die einstellungen vor dem durchlauf oder nach dem durchlauf anwählen.
@@69ETO after, these are optional post optimization tweaks
Thenks for this. This is a tremendous amount of work. What if I live in an apartment and i listen to movies at a moderately low levels? Around 60-70 dBs with peaks to 85 or so? I like to use Multi EQ as it ups the base at low listening levels. Is it ok to leave it on?
P.S. As we are using AVRs mic for measurement, will we get worse results than if we would have used UMIK1 and REW Manual calibration from your previous videos?
I pinned a comment about how to use Dynamic EQ with One above.
I’m surprised at leaving the LFC on with a containment of 1! What’s the benefit there OCA? Just curious. Been using three settings since you posted and sound okay. Tempted to lose the LFC though…
OCA, dont mind saying again, you are truly amazing. Not only with your knowledge/passion on the subject, your willingness to share with others and patiently answer any questions thereafter! Those who are enthusiasts in the field will understand the value here. Thank you!
Wow, thank you
OCA, I have 2 subwoofers in my setup and in the speaker configuration use 2 subs. My ZIP file that is created with the ady responses shows only SW10 - SW17. Will the algos you have implemented see this as 2 separate subwoofers and still be able to create individual adjustments?
There should be only one sub in the zip, this is ok. Audyssey uses only one filter for the combination of the 2 subs and this cannot be changed. The filter the script creates are in fact for both subs. So, in short, it will do everything correctly for you and it will keep the relative distance and volume settings between the subs intact so as to keep the accuracy of the filter (because the imported sub response is the result of the two subwoofers with these exact settings only)
Thanks for the prompt response.
A few more observations.
1. The bass response has been the lowest with 'One' compared to any of your other methods. Same original ADY as input. Any thoughts?
2. There are literally no filters at all between 300hz to 3khz. The Immersive Audio method yielded filters in that range. Target curve differences maybe?
3. The sub distance has to be increased as I have verified with REW in the past. Here it tried to set 7.8m which is limited by the 6m limit. Then it set it to 1.08m!. This is even lower than 4.86ft that Audyssey calculated. What do you make of this?
Again, the workflow was a breeze and fun to execute. Thx!
Correction...sorry, I meant to say 4.86m (not ft) as calculated by Audyssey.
Thank you very much with your generous contribution, OCA. My system never sounded better than now, it's amazing how immersive, precise and clear turns out the sound while watching a movie or listening to music after using A-1, even in a really small and complicated room with a 5.1.2 setup.
Thanks, enjoy!
I appreciate you for taking the time in helping and for making this tool :)
Glad it was helpful!
@@ocaudiophile did you send my file somewhere btw?
I never saw a link to your file yet.@@J0ngebv
@@ocaudiophile drive.google.com/file/d/1bcAFqjzG7nsDxv0MFOXYakxNVKSiq_GR/view?usp=drive_link , hope you see it now
drive.google.com/file/d/1UQJ92Fbz1KGta7jfOeFXEbqwh9KtpcXH/view?usp=sharing
Thanks for the hard work, really amazing result's. One question I have up firing Atmos speakers. Your script set them at 80hz but Klipsch recommended 120-140hz, should I change them?
If One calculated 80Hz for them, they must be going down that low in their measured response, you can check that in the graphs produced at the end of the optimization procedure in REW "All SPL" tab. It's quite common for speakers to produce more bass than their spec due to wall gains, your Atmos speakers are probably close to some wall surfaces. Both the speaker and the amp will benefit from raising the crossover frequency higher due to decreased loads so feel free to try. The only concern is that Atmos enabled speakers already have issues completely re-directing sound to the ceiling and XO at 120Hz would increase localization of the signals a bit more towards the floor. I'd listen to both options and decide by ear. The test tracks I supplied have a lot of Atmos height content. They could help with quickly spotting the differences.
Thank you for your incredible work!
I exported the .ady file that I currently use on my setup, and AudysseyOne set the crossovers on my LRs and surrounds to full range (they certainly aren't full range speakers). Do I need to take a fresh set of measurements?
Glad it helped!
Are your speakers at corners and very close to side or rear walls? The crossover calculation algorithm is certainly seeing your speakers produce sound down to 20 Hz levels to decide them to be full range.
There's no harm in changing XO frequencies manually btw. Cutting everything at 80Hz is not a bad idea for instance especially for movies.
Let me how it unfolds after a new set of measurements.
@@ocaudiophile"certainly seeing your speakers produce sound down to 20 Hz levels".
I don't think so, the input graphs show my surrounds struggling below 50 hz. I'll file a bug report so we can determine if there's an issue.
Thanks for making my system sound so much better. Looking forward to the next release!
An important update has been made to the Audyssey One script v1.3x today:
It's been acknowledged that MultEQ Editor app (and MultEQ-X as well) does not allow for a "soft" change in subwoofer polarity. A1 will now ONLY provide advice if it detects potential benefits from switching subwoofer polarity, indicating it should be done directly on the sub(s).
The script remains unchanged and identical in all other aspects, and if you weren't prompted by A1 to invert the subwoofer polarity before, there's no action required on your part.
Apologies for any inconvenience this may have caused.
OCA
Hello,
Thank you so much for your work.
Is it possible to have a link to your last update ?
It's in the video description.
Is it possible to modify the value of the parameter « upperLimit » ?
@ldps-zf3qk It's not easy and you'll not like the audible outcome even if you did.
@@ocaudiophile
Ok, I need to correct from 0 to 300Hz due to my room
Right up to date with OCA target and hockey script. Denon 2700. Thanks for the effort and the education it's been fascinating!
👍🙏
Thanks OCA! My script keeps getting stuck on "Optimization process (version 1.3x dated 14 Jun 24) started...
5:52:36 PM [LOG] Transposing measurements from '3' different microphone positions to the primary listening position..." and eventually says "load failed". Can you help troubleshoot?
First of all thank you very much for your gesture. I've fixed that and many other bugs with A1 Evo v3x. Please use that one and let me know.
This is fantastic!!! Anyone who follows your work knows the importance of this automation. Thank you very much, you don't exist. I can't contribute at the moment, but as soon as possible I won't forget someone who does this work out of pleasure and is so little recognized. THANKS.
Your kind words are more than enough fo me . Enjoy!
So true! You just spoke my heart out A TO Z.
I was actually looking into making something like this myself. I'm glad someone did it so I don't have to :). Great work, guys. You are changing the game of calibration 100%!
Cool, thanks!
Attention multiple subwoofer users: I "might" have found a bug that can affect multiple subwoofer relative delays in some models and have updated the script just now (15:15 CET). This "could" change multiple subwoofer performance considerably. Please run the latest version and let me know if you will hear any difference. Single subwoofer systems (including multiple subs through a MiniDSP) have not been affected from this bug and they don't need to do anything.
Was there a rule that custom distance sub 2 + delay adjustment sub 1 should equal the total distance? The new script looks like custom distance fields were removed entirely. Distances are both 5.19 and audyssey app shows distance of sub 1 as 0 and sub 2 as 0.1.
Yes, that's the bug I am talking about. Some models require customDistance setting and channelReport.distance to be 0, some others only take the distance value from channelReport.distance and ignore CcustomDistance setting value so I removed customDistance from subwoofer altogether. WHat do you see in the AVR settings when you transfer the ady? @@burtonscustom
@@ocaudiophile
Will the script work with the directional operation of two subwoofers?
No!@@TygapbI4
@ocaudiophile Subwoofer 1 is 0 and Subwoofer 2 shows 0.1 for distances in the AVR after transferring it. Denon X3800H
Danke für deine großartige Arbeit!
Gerne geschehen!
Thanks for this great tool! Used this with the harman kardon target curve. And it sound great
Lovely!
Hi! Thanks a lot for this script. I'm been tinkering with my home cinema for years and recently set up 7.2.4 with a Denon X3600H and external amp for the L+R speakers. Subwoofers with miniDSP and MSO but this time I'm running them bare. Comparing with my previous Audyssey XT32 efforts the new calibration without using your script and correcting to 300 Hz was already an improvement. After some hickups of One Drive corrupting the optimized ady file and my subwoofers measuring 45 dB too loud and with too much delay, I got it working with some hacks. Your optimized filters sound the best, by far, of what I've experienced anywhere so far. I use several movie scenes and opening logos I know intimately and they got significantly more clarity. I can pick up details of things in the background I've never heard at all before. Voices get clear as day (Blade Runner 2029 opening for example). Bass is much more defined, confined and I can feel it right for the first time. I still have comparisons to do with my UMIK-1 for spectrograms but so far this is remarkable. Thank you so much!
I was shocked at the extra detail and clarity, I’m running mini dsp and mso for a nice response over 2 seats and run audyssey and script over that, now I’m wondering it could be even better if I take mini dsp out and just use my 3800h sub outs
@@paulsmith3440that's what I want to know, do I EQ with minidsp or not
@@andrew1977au align and eq with minidsp first then run an audyssey cal and give that to A1
Hi!!!
I have a problem with the optimized file in the Drive or I have a corrupt file message...
How did you go about solving this problem please?
I've been struggling since yesterday....
Your help would be invaluable...
@@jeanmichelgaudron9556 how are you transfering it? I use OneDrive to take the file fromy phone to PC
Thanks
Cheers!
Thanks Serkan. Not all heroes wear capes ❤
Thanks! Really great piece of work. Can't wait to see more of your magic here on this channel! 😄👍
Thanks a lot!🙏
The script has been updated today, incorporating the following enhancements:
• Introduction of a version number for improved user tracking (line 109 in the code)
• Significant revisions to the crossover frequency calculation method, resulting in enhanced consistency.
• Elimination of setting any speaker to Full Range, ensuring that bass is exclusively managed by the subwoofer, which is optimally filtered.
• Implementation of a warning system for cases where volume adjustment for a subwoofer (or subwoofer combination) exceeds the AV Receiver hardware limit of 12dB. In such instances, volume is adjusted to the maximum permissible level, allowing optimization to proceed.
• Introduction of a warning mechanism for cases where volume adjustment for a speaker surpasses the prescribed limit. This is typically indicative of a faulty measurement process, but was seen in rare cases.
• Removal of irrelevant data from REW before the optimization process concludes.
***If you're running into memory problems due to too many speakers, install REW with max. memory option of 3GB. In my tests, it only touches above 2GB usage for a short time.
Better yet, you can right click on the REW shortcut, select properties and replace Target setting box like below:
"C:\Program Files\REW
oomeqwizard.exe" -J -Xmx4196m -api"
This will ensure REW will always start with 4GB of memory allocation and API server running.
Something is not right on this one. My ceiling speakers are all the same model. Now got xo 40Hz on other pair and other is correct at 120Hz.
They must be somehow producing bass until below 50Hz. Did you check the final speaker responses?@@hannu.kalkaja
@@hannu.kalkaja this one crashes / stops for me too... cannot get past " Pinpointing crossover frequencies for each speaker..." ...
It's quite a bit slower than the previous one, doing a lot of extra work for crossover calculation but never crashed in my pc. Can you share your logs or your ady?
I think I know why, probably REW default memory allocation is insufficient for the number of measurements you have. Did you set it up at the max 3GB during installation?
Audyssey One has been updated to version 1.2
drive.google.com/file/d/1qnFTmS1687dnYYP5nORx3W1CTF3nQgiq/view?usp=sharing
today with the following improvements and revisions:
* Subwoofer volume alignment frequency range has been modified from 22.3Hz - 178.2Hz to 28.3Hz - 226.3Hz. This change may result in a slight increase in bass response for certain audio systems. However, if desired, the previous frequency range can be reverted by modifying line 625 of the script.
* The calculation of crossover frequencies has been optimized for faster performance and reduced memory usage. As a result, there is no longer a need to increase REW's memory settings. Additionally, the calculated crossover frequencies are FINALLY completely accurate to five decimal places for every possible system configuration.
* To minimize driver loads and increase clarity, any calculated crossover frequency below 80Hz will be automatically raised to 80Hz.
* The logging functionality has been enhanced, providing some additional enthusiast information.
* A timer has been implemented to report the total execution time at the end of the optimization process.
To do:
* Implementing an exhaustive subwoofer alignment process with iterative targeting of minimum total phase delays at the crossover frequencies. Assistance from experienced coders is needed, as my hopeless attempts today have resulted in multiple REW crashes.
* Enabling manual optimal relative alignment of multiple subwoofers by taking Audyssey measurements in 'directional mode' and then switching to 'standard mode.' However, it is uncertain whether Audyssey will accept running the calibration in directional mode on older receiver models, even if the mode can be activated through the app."
Hello OCA, is the google drive linke up to dated? It still shows version 1.1 from 18.03.24 21:25 .Best regards.
Yes, just double checked it. It's v1.2 now!@@miroslavpetkov9895
Hi great channel and very inspiring to me as I've just got the umik-1 also. Just tried yesterday before the update yesterday and now tonight already 2 updates after my first calibration amazing support. Saw some of your other videos and have some questions. I wil totally start over calibration again with my Denon AVR 4400H. Do you recommend me to calibrate the audyssey mic against my umik-1 before starting this software? Should I take 3 Audyssey measurements at the seathing position at the same spot without moving the mic or 8 measurements same spot without moving the mic? Or do you recommend to move the mic and how many measurements to take. Also had former added Curtain to the final audessy XT32 calibration at 300hz are this necessary with your software? Great work 🎉
If you will use REW and Umik, then take just 3 measurements with Audyssey (the bare minimum) all at the same mic position. They will only be used to generate a dummy app for REW filters. When measuring with REW, you can take as many as you want. Repeating measurements at the same mic position also helps increase signal to noise ratio of measurements. The method is detailed in the Audyssey ART video and the Immersive Audio videos. @@dennishlarsen
Strange, line 109 says: // **************************** version 1.1 18 MAR 2024 - 21:25 CET ************************************
Is this msg the same in all Versions? Perhaps reposting the google drive link... @@ocaudiophile
A1 will work with any number of mic positions, so you can stop after the 3rd round if you so wish. You'll have the best sound (but only at a single location) by keeping the mic at the exact central position at ear height and repeat all 8 measurements without moving the mic.
I just tried this method. So far its outstanding. I use Star Wars Battlefront Dolby Atmos demo, more subtle audio all around. Will try regular movies as well.
Intresting
This comment does not get the attention it deserves.
What does exact central position mean, is it the centre of the room or centre of the listening area or the main listening position?
@@oliverheath2000 I think he means ear level. where you sit. Approximately the location, between your heard.
Thanks! For these great videos and superb knowledge shared in order to help your audience experience better sound!!!
Thank you!
Thank you!!! I have been using 1.1 and it is the bomb. Where are the links to 1.3x? I only see 1.2
Thank you very much for your time and work.
Thanks. The link is in the video description. Your browser cache might be taking you to an older link.
@@ocaudiophile The video description only says 1.2? Is that from browser cache?
My system now sounds like a 10k+ system, awsome🎉
Simplemente excelente Script, ahora tengo un sistema de audio del cual puedo disfrutar todo su potencial. Voces nítidas, bajos contundentes, sonido sin distorción, feliz con mi nueva configuración. Felicitaciones!
Muchas gracias.
A1 cannot process directional bass mode, A1 Evo will so keep your ady file and wait just a bit more.
Thanks. Need help. Ran into a problem. 1.3x stops saying subwwofer level is too low. V 1.0 used to work fine. Tried with fresh set of measurements in the audyssey app. If I get to the red band, audyssey doesn't work. Anywhere in the green band, sub level seems too low to audyssey one. Could you please share link to v1.3? Running Denon avr x3600h with SVS SB1000pro. Grateful for your help.
Also, forgot to tell you, I am running audysseyone ver 1.0, and I substituted the Half Witledge Curve from YSR forum for the Toole curve. I am not a purist, and this isthe most awesome my system has sounded yet. A1 v1 delivered a fantastic optimised file. Thanks again.
Try to run REW beta 21 linked in the description. The error could be caused by changes in the latest REW.
@@ocaudiophile Oh! OK. Sorry but I didn't think you would reply. Got a fresh set of readings but the sub woofer level is close to the upper end. Will run it all again. Again, great work.
Danke!👍
🙏
Audyssey One now has its own song :)
th-cam.com/users/shortsQ5r_EZBcmWE?feature=share
Awesome
Excellent
Epic!
It was all done for free by Suno AI (including style, lyrics and all)! @@techm0j0
That's awesome! I'm going to make a new song now!
It looks really good, unfortunately it doesn't work without a subwoofer.
I don't think it's mentioned anywhere, would it be possible to add this warning stoneware?
Really impressive work, not for me unfortunately.
Minor bug fix to Audyssey One v1.3x today. The bug was affecting ONLY SOME MULTIPLE SUBWOOFER systems connected directly to the receiver (i.e. not through a MiniDSP). If you are using A1 with such a system, you will most likely benefit from running the revised script. Download link is unchanged (in the video description):
drive.google.com/file/d/1O-yRmbahRFjj0flX_kfgFDj3vrQwvZYq/view?usp=sharing
PS: For peace of mind, please keep using REW Beta 21 until REW Beta releases finalize. Some Beta versions may yield different results and/or throw errors.
Seems to work perfectly, thank you, never thought my system could sound this good!
Got an error "TypeError: customLevel[j].toFixed is not a function - program execution has stopped!" on the new script. Looks like the new code is getting caught on a type conversion on that customLevel array somewhere. This is running an ADY that worked fine on all previous versions of 1.3x.
It's fixed now. Please download the script again.
Hello. I did with A1 v1.3 again. v1.2 put my SW ´-5,5db but v1.3 puts it -3.5db. Its ok?
Hi OCA, thx for the update again. It sounds really good with good bass (Harman Curve), but I noticed one strange thing: previous version said:
"[WARNING] Calculated optimal subwoofer distance of 6.68m exceeds AV Receiver's max. speaker spacing limit [5.42m vs 4.02m]!"
But your latest version says this:
"[INFO] Subwoofer distance is 'optimally' set @ 6.68m and is 'safely' within the AV Receiver's speaker spacing limits."
Makes me wonder.... is it a safe distance or not?
It is also the first version that tells me to invert my subs. Which makes the bass less good... Rest of the corrections are exactly the same.
Thanks a lot @ocaudiophile for your work ! it really helps my X4800H so much that I don't feel to cash out USD600+ on DL+DLBC 😀Some doubts, Audyssey One got my XOs for my 5.2.1 at 40Hz and sets 80Hz to relieve the stress on the amp which is fine for me, does it means that I'll get a bit more bass between 40-80Hz ? And another finding my X4800H never sends the customDistance parameter so I have to type the Center distance to MLP, my NR1711 does but why I did find in the MultiEQ App is that the Sub distance is set for X4800H and below 6 meters (3.98m vs 3.52m your scripts calculate) do you think MultiEQ App is stripping some info before exporting .ady files ? TIA
Your welcome! A1 confirms that you are safe down to 40Hz XO with these speakers but less or more bass will depend on their phase match with the sub(s), you need to try both 40 and 60Hz and listen (or measure with REW) and compare to be sure. But the lower the XO, the more load on the speaker and the 4800, that's a fact.
If center speaker distance is being asked, that means Audyssey during the calibration run maxed out your SW distance and deleted other speaker distances. It will show you distances in the app but they are calculated by the app after fixing SW at max. If A1 could set your SW distance afterwards, there's nothing to worry about. Script calculation is robust (it matches impulse responses). Also, if you edit distances in the app and re-save, then they will also show up in the ady and you will not need to enter anything manually.
@@ocaudiophile Thanks. I'll take some REW sweeps before and after A1. A preliminary sweep of my R channel shows lower bass compared with the O'Toole target at drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link please note that sweeps were taken with a UMIK-1 instead of the MultiEQ Mic
@@ocaudiophile Thanks ! I'll take some REW sweeps before and after A1, preliminary sweep with a UMIK-1 shows a recess on bass compared with O'Toole target at drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link C channel distance was set a 1.77 meters.
drive.google.com/file/d/1IuIkxasURtML2cwwFXvmXoTiIYGObipS/view?usp=drive_link
@@ocaudiophile Thanks. I'll run sweeps before and after A1, preliminary sweep on R channel shows a reccess on bass response compared with O'Toole target as in this image:
drive.google.com/file/d/1IuIkxasURtML2cwwFXvmXoTiIYGObipS/view?usp=drive_link
The whole sweep and .ady files are here, please note that REW sweeps was taken with a UMIK-1 not the MultiEQ mic:
drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link
BTW I'm having some troubles posting comments, not sure is my Adblock systems or what.
@@ocaudiophile I have problems to post comments they disappear. Trying to post my G Drive with REW measures before and after A1 comparing Reference, Flat, etc
Script updated with "SR6015", "SR7015", "X8500H" for SoS 300 m/s just now! Download again to update your copies!
I have an X3600, it is on latest firmware and using the IP lookup it is definitely 300M/S. looking at the script it is not one of the exceptions, can it be added (or is there a way I could add it manually)?
Also, the video does not mention taking the audyssey measurements but I guess we need to do an 8 point measure grouped at MLP and then upload the ady?
Yes, you can edit the code in any text editor, i.e. Notepad and save and it will continue working. The receiver list is at line 121.
You can take as many measurements as you want (Audyssey will require a minimum 3 to end the process though). If the listening area is small, 3 would suffice but the more the better of course.
Denon X4500H is also at 300 m/s according to my measurements.
I added x3600h just in case 😊, its also 300
My Denon 4800 shows:
3048
but I'm not sure where I have to change SoS value...
You don't have to do anything, 4800 is known to the script@@ampueron
Minor updates and enhancements have been implemented in the Audyssey One calibration optimization tool today (v1.3):
• The anti-"high frequency roll-off" filter has been recalculated from preamp outputs and now "completely" eliminates the reference curve effect on speaker responses.
• A1 v1.3 detects whether the subwoofer polarity determined by Audyssey needs inversion and automatically inverts it using ady file parameters, resulting in potentially improved bass response in certain systems.
• Upon completion of the optimization process, a copy of the full optimization log will be saved on your computer as a text file for your reference.
• Root causes have been included as informational details in system logs to help with some common errors.
Version 1.3 has a distinct link provided in the video description, while the link to v1.2 will remain accessible to prevent browser caching issues when transitioning to the updated link.
drive.google.com/file/d/1x3_c_MSwIYymxQbhiY7zvtykV_hwwUX2/view?usp=sharing
Hi OCA, thx so much for this. New version already! I tried it, some different results it seems but the only thing that's get's downloaded as a result is the log file, not an .ady file...
Correction: it does work in chrome based browser, not in safari.
Safari might be blocking the download because of some security setting that needs to be turned off.
@@ocaudiophile
Hello. Thank you for all the work and dedication you've put into this. I do have a question about v1.3.
I ran the script using v1.3 and it stated it inverted my sub. Ok. I uploaded that .ady file to the MultEQ app, but I noticed all the graphs in the app look the same as the .ady file I made with v1.2.
Would that sub inversion be visible somewhere in a graph, whether it be on the app or REW? Did v1.2 also Invert my sub and that's why both look the same or is that only a v1.3 feature?
I just want to know if to leave the .ady file I made with v.1.2 or if to replace it with the 1.3 version. Hope that's clear.
Im not able to use the new link :-(
No browser works
fantastic video, once again !! your knowledge regarding audyssey is out of this WORLD !!!!
Thanks for this brilliant work! Small token of my appreciation. I have sent you a PM on the forum 😊
Cheers!
Script updated just now with a fix for multiple sub distance settings transfering incorrectly to certain models. Please give feedback and share your ady file if you are still seeing subwoofer distances as 0 in your AVR setup menu!
Hi and good morning. I answered some minutes ago, but the post is empty. I try it again. You had hard days and you are very very engaged. Thank you. Here are the files with the last three updates from your script. (drive.google.com/drive/folders/1sNJfIeK2LKasAzcml82oTdF2Q33zk8k5?usp=drive_link)
Thank you, these will be of great help!@@matten545
habs eben getestet, habe 2 SW und die sind bei 0.00 und 0.01
Bitte testen Sie erneut mit dem neuesten Skript, das vor wenigen Sekunden hochgeladen wurde! Lassen Sie mich wissen, wenn das Problem weiterhin besteht.@@777Gurus
I run the script on standard mode measurements. Work's very well and I have better results than before. No problems with sub distances, but unfortunately there's dip on freq response. So alignment is not optimal for that. Timing is much better now than before, but again it's mostly because I have moved subs closer to MLP.
I tried directional mode, but script gave me an error. I would like to see how I could use individual measurements from each subs to achieve best combined results. My plan is to run subs always on standard mode. Maybe I could use measurements and manually align+eq them in REW, then upload parameters by using MultEQ-X.
Once more. Just great work and thanks!
🎊 🎉❤ I want to thank you 🙏 for creating this amazing script.
My system sounds so much better now.
I am in a cocoon of amazing 🤩 sound
Dude! This latest version is just fantastic!. I've had to make a few changes since my open floor plan is a mess, acoustically. limited gain to +6db and had it correct all the way out to 20,000. The default toole curve is "ok", but I did swap that out to a older school harman + toole curve under (100hz the bass is increased quite a bit) is the main difference. With these changes, it's a MARKED IMPROVEMENT over anything I could get MultEQ-X to do.
You might be able to use a heavy curtain to separate the different spaces?
Thanks So Much OCA !!!! 👊😃👌
Your very welcome!
@@ocaudiophile Hi OCA - quick question in your opinion Would using the MultiEQ-X $200 PC version along with A1 make a better difference - rather than the Audessy App $20 & A1 ? Just Curious to know.
You don't really need MultEQ-X with Editor app and A1.
Very Important: First off Audyssey One is amazing, and my system sounds even better now! But, make sure to use the same REW version that OCA has set! Don't be like me and make that mistake
I was using REW Beta 28 (just downloaded most recent since Mac link wasn't in TH-cam description), and Audyssey One was setting all crossovers to 150hz in the logs.
This was odd because I did an initial sweep and separate measurement and it measured my L+R mains down to 30hz flat in my room.
After downgrading back to REW Beta 21. Audyssey One put them closer to 40hz crossover. So if you are getting very high crossovers make sure you are on right REW tested version.
It was working fine to up to 26 and then 27 and 28 suddenly changed things. Beta is a work in progress so sticking with 21 until it all settles seems to be a wise decision.
Thanks @bungatown. But where did you find the REW Beta 21? I can only find the latest Beta version (currently 67) for Mac. OCA's googledrive link for Mac is broken...
Minor update for Mac users just now:
Some Safari browsers were only saving the logs but not the ady file at the end of the optimization. This must have been fixed with this update. Please notify me if the issue continues (I don't have a Mac to try).
Hi OCA! First of all a massive thank you for this! My sound stage is noticeably larger and there's a clarity in my speakers that sounds amazing! Just wow! :D
I do have a Mac and when running v1.2 it creates an ady file ok. However, after just now running v1.3, a log.txt is generated and downloaded but this is still no ady file. Hope this helps! :)
That means the update didn't fix the issue yet, keep running v1.2 or v1.3 with Chrome or Firefox browser for now. I'll see what I can do.
@@ocaudiophile Hey Serkan, I just checked to get you some more input. In V1.3 only the log file gets saved. Version 1.2 works flawlessly on Safari because there's only the .ady file to be downloaded. So I guess Safari has an issue with the second download, which does not make very much sense as at the beginning of the optimization Safari has no issue downloading the extracted measurements and the target curve...
TH-cam should allow you to search in the comments or we could start a FAQ, I just searched the comments as after changing the Level on my Arendals to reference level with a new Audyssey calibration the text box regarding the sub delay appeared. I wanted to ask which is better without the text box and alignment on the second attempt or with the text box on the first attempt. Luckily you are so supportive and answer every comment so I already found your answer in an older comment. Very happy with the results!
"User input requirement has no effect on the optimization. It only means Audyssey couldn't align your subwoofer. If the optimization completes with success after that, it means A1 could align your sub. FYI, with or without the user input, the most important factor is how many attempts did A1 take to align your sub. If your sub is aligned in the first attempt, that almost always means remarkably better bass performance compared to the next two attempts."
Hi OCA, Yesterday I did try to V1.3. I am only using one subwoofer. Still it inverted my subwoofer. Why it is so? I never feel to invert my subwoofer.
And A1 always set trim of my LCR to positive 3 to 5db.
In addition, in my LR speaker crossover point there is dip of 18db. Which Ady mobile app corrected in calibration but A1 didn't.
Any way to calibrate full spectrum i.e 20hz to 20khz?
A1 aims to create the best sound not the best graphs ;)
I just wanted to say after using this after week it's FREAKING INSANE - when playing halo I now get much more directional feedback on where grenades blow up, the bass kick so hard i can feel it, lol and it scares me sometimes lol
in Ready player one i hit 125 db in my MLP lol
not only is bass cleaner and hits hard it also doesn't vibrate things like it used too!!! I deffineently think my room treatment is helping ady and your scrim get the best out of the system!!!
Are you using DEQ as well?
@@HOTpopcornVideo no it's off
Obrigado!
Many thanks Miguel!
I can't thank you enough! I'm rediscovering my favorite movies! WTF was this?! 😁 👍
Least I can do for audiophile community ;)@@miguelmedinaramos
Thanks OCA !!!
🙏
Hey OCA! Long time since the last adyssey video!
Wanted to ask if this correction technique would work the same if we feed the script rew manual ummik1 measurements, instead of the avr default mic ones, and use the values of the generated ady file to insert in our multq x pc app?
I guess it wont work cause of the high frequency rolloff compensation?
Is there a way to mitigate that for multeq x users?
Thank u in advance for any feedback!
We much appreciate your efforts for the Audio Valhalla
Dear John, I cannot decrypt the "mic calibration file" embedded in mqx measurements (they have used SHA 256 encryption) although I can read mqx measurements and import to REW. The response will always be a little off by an unknown mic cal amount. It's possible to decrease its effect by using the standard Audyssey mic cal file as a dummy but this wouldn't make guys like you very happy! Hence the lack of support for mqx in my script.
Since the filters are not produced by REW EQ but pure inversion, there's no way to export them as biquads to x, either.
One benefit for you would be using the volume settings found by the script and use them in MQX as base. The volume alignment in the script (including SW volume) is state of the art and cannot be matched manually.
@@ocaudiophileI think we can make the script work all the same, if we replace the exported ady measurements with our rew ones (i guess we need to name them as we saw in the video).
The only thing that i need to try this out, is if you can tell me what line of code should we look to change for the high frequency rolloff compensation you are deliberately making, can you tell me where you are making this so i can disable it for me?
As long as you keep the responses data at perfect speaker norm, you can use any filters you want with the script including filters based on REW/Umik measurements. You just should not use mqx measurements.
Anti HFR1 is the additionalRows constant at line 822, delete that and it will no longer be applied.@@johnaps
@@ocaudiophileI will not mess with the editor app nor the ady file, so i guess i can just use the script to do the rew corrections to my measurements automatically, and then populate the results inside my multq x app! Perfecto! Will try it out today
Hello Master ☺️
Is a 1.4 planend? What „feautures“ are you working on? I‘m totally hyped and thankful!
No more versions of A1 but...
@@ocaudiophile you are a tease🤩
@@ocaudiophilecannot wait for the new rocket 🚀
excited for this one! thanks OCA!
Hope you like it!
I've had some issues with my Audyessey app recently where the connection between the app and receiver has dropped out around measurement 7 or 8. It's been incredibly frustrating, and having to run the calibration up to 4 times to get a reading has left me accepting whatever sound quality I could get from the process. I spent 10 minutes last night using the tool from this video and wow, just wow. It's like I just bought a brand new setup, the clarity is nothing short of incredible, I was a little put off by what I perceived to be lower sub output when trying out some test scenes, but with some more testing I see now that the balance of the sub and speakers is utterly perfect. Cannot recommend this enough, it's a life/game changer. Kudos to you sir!
I have this also when i have CEC running. So when I run Audyssey I make sure 0 devices connected to the avr are on.
@@everydayguy3737 Turning the TV on has worked for me thankfully
OMG WOW !!! OCA !! you the man !!
"Audyssey One" minor compatibility update today (v1.3x)
* Updated to address ongoing REW Beta API changes. Please use the provided REW Beta 21 link within A1 until the next update ensures compatibility with the latest REW beta versions.
* Revised default Dr. Toole target curve for roll-off filters in your receiver, providing full flat response throughout the audible frequency range.
* Optimized subwoofer volume level calculation algorithm for increased compatibility.
Link for MultEQ Editor app Android version with no subwoofer volume -12dB bug:
drive.google.com/file/d/1--DP4H6SZcIQN1i3pRyXdEY18Aa9v9fO/view
Sounds fantastic.
OCA, what's the link for 1.3x? Was there a 1.3 before this that I missed?
The Audyssey One v1.3x makes the subwoofer less boomy. I like it better! Thanks again :)
drive.google.com/file/d/1O-yRmbahRFjj0flX_kfgFDj3vrQwvZYq/view?usp=sharing
Thank you for adding the version number in the log file of the script! :)
Thanks for the videos, they are amazing. Learned lot from them. Can you add X3500H to 300 SoS list?
Added thanks.
Thanks!
Welcome!
Thanks!
🙏
Looks like your amazing work is kinda being hijacked.
Been a follower of what you do for some time now, and it is quite astonishing. Not that I understand it all, but fascinating nonetheless.
Being older I finally got to assemble my dream music/movie system, and you videos are invaluable. Can't believe you give this info away for free.
But, it appears that at least one other youtuber (that I know of) is referencing your hard work to boost their own channel. Not nice in my opinion. But I am older and maybe I am getting it wrong.
He does give full credit though.
Anyway, huge thanks for this, very much appreciated. J.
He's helping people with questions on A1 and also running a facebook page. I cannot cope with all the requests on my own so I am happy with his engagement ;)
Hi, why you don't change the version number of a1? Xou bring new Versions, all with the same number?
Thanks. Total legend. Any chance you can script MSO and make it this easy??
No but I'm working on a new version with better bass handling
@@ocaudiophile what are your approx timescales?
@@clunesy I intend to launch it before summer, nearly finished now but final touches taking longer than I anticipated.
Ich bin so gespannt 🙏
Danke!
Finally the wait is over!!!!
Thanks!
You're spoiling me guys!
Unbelievable! Better than Dirac! This is a legit gamechanger!
Cheers!
***Important: I have figured the reason behind the rare 0m distance problem thanks to calibration file shared by @matten545.
If Audyssey measures your subwoofer's actual required delay (distance) higher than the 6m speaker spacing limit, it will set all speaker distances in the ady file to 0!!!!
The app then sets the subwoofer distance to the maximum allowed and fills up the rest of the speakers accordingly. The only work around that was to ask the user for a distance estimate which is now added in the script.
So, if the script is asking you to manually enter your center speaker distance, it's ONLY because even Audyssey has found that your subwoofer requires a delay larger than the maximum distance limit.
@ocaudiophile I'm not sure is the only case because in my case the App reports 3.98m but inside the .ady file all delays are set to 0. Linked the .ady file and a screnshot of the MultiEQ file. And many thanks for your great work ! I tried to find where in the files are the distances that the screenshot shows without success.
drive.google.com/drive/folders/1kSygSPZX4H3KAxfKhmusMlmDB-pEj_Wt?usp=drive_link
Thanks!
Cheers!
I saw a comment from you to not use a modified .ady file, so I took a new set of measurements this morning and exported them from the app. This set most of my distances to 0, and my L/R to full range with 20hz X/O. Center channel to 200HZ. This is incredible work you've done, but I'm unsure if I've done it correctly. I've pasted the log from running the script as a reply to this.
eriving optimal speaker distances through cross-correlation analysis...
8:09:53 AM [LOG] C: 0m
8:09:53 AM [LOG] FL: 0.23m
8:09:53 AM [LOG] FR: 0.13m
8:09:53 AM [LOG] SLA: -0.62m
8:09:53 AM [LOG] SRA: -0.74m
8:09:53 AM [LOG] SWMIX: 0.42m
8:09:53 AM [LOG] TML: -0.44m
8:09:53 AM [LOG] TMR: -0.55m
8:09:53 AM [INFO] Subwoofer distance is 'optimally' set @ 0.43m and is within the AV Receiver's speaker spacing limits.
8:09:53 AM [INFO] Crafting custom room correction filters...
8:10:16 AM [LOG] Done!
8:10:16 AM [INFO] Pinpointing optimal crossover frequencies...
8:10:16 AM [INFO] Crossover frequency for C is set @ 200Hz
8:10:16 AM [INFO] Crossover frequency for FL is set @ FULL RANGE
What model AVR and what version of app are you using? These results would only come out if both your distance and custom distance settings are 0 in the original ady file. You can still correctly set up all distances from the figures produced. Measure your C speaker's actual distance to MLP and add/subtract the numbers and fill all others up accordingly. ie if C is @ 3m, FL should be 3.23, and FR should be 3.13. If you can share your ady file, I will check why this is happening.@@Jkrison
@@ocaudiophile 1.11.1 (3.20.0) is the version of MultiEQ I'm using. Denon X3700H with GSG 18" Martys /w Crown amps, Polk R700's. Polk Legend CC, rest of bed layer also Polk.
The original measurements taken put the C at 9.7ft in the app. I didn't modity the distance settings at all, I went straight from measurements in the app, and exported to my PC. I can email you my .ady if you want? Not sure how else to share it.
I have fixed the problem in the latest version. Pls redownload.
¡Gracias!
🙏
Thanks
Welcome!
Thank you!
You're welcome!
Stopped by to review the tutorial, one of my SVS SB-13 Ultra subwoofer when kaput, and want to calibrate using multi position multiple sweeps per subwoofer at each position (same as audyssey) choosing the best sweep for each sub. I am the only attendee.
Best subwoofer calibration tutorial . 🎉
Amazing work brother,
I won’t be using it since I just got my system professionally calibrated but I admire your work and when I get brave enough to do it my self I will definitely go with your file.
I watch all your videos learning so much Thank you 🙏
Glad I could help
Happy to here that from you!
Ellerine sağlık Serkan. You are simply amazing dude. I am having a hell of fun experimenting with your script👏
Professor OCA!! Your work is greatly appreciated!! Many thanks for this contribution!! 🙏
My pleasure!
Tried this last night. Very impressive results indeed! Thanks!!
Great to hear!