Topic: 23.0.17 - High Pitched Tone bug back (Read 6937 times)

CallMeSteven · « **on:** July 09, 2017, 07:50:42 am »

Unable to use this build. This reintroduced an issue I had with Version 21...NOT 22, or build 23.013 - results in a loud high pitched tone randomly
starting with my Xonar Essence soundcard. I was so happy Version 22 solved this issue and 23.0.13, but for some reason 23.01.17 brought it back

JimH · « **Reply #1 on:** July 09, 2017, 08:01:15 am »

I don't think there are any changes that could have caused that. Try adjusting buffer sizes. Search for other Xonar posts here and on the Internet.

CallMeSteven · « **Reply #2 on:** July 09, 2017, 08:05:19 am »

Well that's not possible. Nothing changed my end other than a change from 0.13-0.17. Something must have been introduced. NB: I have used
Version 21 of MC and suffered with this issue for over a year, but as soon as I upgraded to version 23 in May it completed vanished...I use MC extensively,
so as I said the new version MUST have changed the audio coding somehow, otherwise I cannot explain my findings.

Awesome Donkey · « **Reply #3 on:** July 09, 2017, 08:13:17 am »

Quote from: CallMeSteven on July 09, 2017, 08:05:19 am

as I said the new version MUST have changed the audio coding somehow, otherwise I cannot explain my findings.

Looking at the changelogs between .13 to .17, I see no audio related changes.

CallMeSteven · « **Reply #4 on:** July 09, 2017, 08:26:25 am »

Well that does not mean my 'bug' is not a 'bug' - I'm looking for a solution, maybe the next version will not have this issue. The thread is for bugs
found, as I said it was NOT present on the previous version, so it IS a bug.

JimH · « **Reply #5 on:** July 09, 2017, 08:28:06 am »

JimH · « **Reply #6 on:** July 09, 2017, 09:03:08 am »

Try the Weird and Wonderful thread in my signature for ideas.

Here's just one example of what you may find:
https://yabb.jriver.com/interact/index.php?topic=81054.0

JimH · « **Reply #7 on:** July 09, 2017, 09:05:30 am »

and another:
https://yabb.jriver.com/interact/index.php?topic=86383.msg591334#msg591334

CallMeSteven · « **Reply #8 on:** July 09, 2017, 10:40:57 am »

Thanks...I have read about the 'high pitched tone issue' with my sound card over several years, but as I said above it was solved by the two versions
mentioned above, but the lastest build brought it back...very odd. I'll try the next build and see if it disappears again & update this thread for other users.

blgentry · « **Reply #9 on:** July 09, 2017, 04:11:54 pm »

Searching google for the words: Xonar Essence high pitched

...results in many many forum threads discussing this problem. I only read through a page or two and decided it wasn't worth my time, since the threads can be 10+ pages long, each.

This is clearly a problem with this series of sound cards and the various drivers used with it. Because these problems exist independently of JRiver MC, it would seem that it's not related to MC.

If you were able to reproduce the problem with one build, then switch to another build and have the behavior STOP, then it would be a more compelling case that JRiver MC was at fault. If you could do that, the JRiver staff might want to look more deeply into the problem.

If not, it seems this issue is outside of MC and will require a different solution.

Good luck to you.

Brian.

~OHM~ · « **Reply #10 on:** July 10, 2017, 01:21:06 am »

does the OP have windows 10....we all know w10 will update drivers at will and could be the culprit here...don't ya just love free stuff!

CallMeSteven · « **Reply #11 on:** July 10, 2017, 01:49:25 am »

Thanks for the thoughts guys....but you must read my posts before trying to help.

MC 21 caused the high pitched tone with my sound card

MC 22 all versions NO issue whatsoever

MC 23 .13 build No issue whatsoever

MC 23.17 High Pitched tone back

Going back to .13 build again all fine.

NB: I am on the latest build of Windows 10 - last update 28th June, that was BEFORE I tried .17......13 was working fine.

Conclusion The lastest MC 23.0.17 is the culprit.

JimH · « **Reply #12 on:** July 10, 2017, 06:56:33 am »

As long as you have your mind made up, you're unlikely to find a solution.

Did you try increasing buffers?

CallMeSteven · « **Reply #13 on:** July 10, 2017, 07:48:19 am »

No reason to.....and you cannot accept that it's a bug!!

I've gone back to 23.0.13 and the the issue is resolved.

Hendrik · « **Reply #14 on:** July 10, 2017, 07:53:21 am »

Quote from: CallMeSteven on July 10, 2017, 07:48:19 am

No reason to.....and you cannot accept that it's a bug!!

We do actually know what changed in MC between .13 and .17, and absolutely nothing whatsoever was changed regarding audio output.

What you cannot accept is that this particular hardware appears to just have this issue, and it happening randomly is out of the control of any software.

CallMeSteven · « **Reply #15 on:** July 10, 2017, 08:45:03 am »

Well if that is the case, I just wonder why it should return immediately after changing from version 23.0.13 - 23.0.17.

As I said at the start (of this topic) version 22 also was absolutely fine. I used version 21 for over a year with this issue which occurred yes randomly, but at least
once a day and yet with both version 22 & 23.0.13 never occurred once. That's the thing that I find quite odd. I thought I'd let you know my
experiences with the software....I know you are trying to help, thank you.

JimH · « **Reply #16 on:** July 10, 2017, 09:00:02 am »

If there is a bug in a driver or any software, it is possible that is triggered by something very specific. For example, antivirus software might slow something down enough that timing is different.

I'm guessing that your device is running out of data, and when it does, it isn't well behaved.

Please contact the device manufacturer or do a little Internet investigation. This isn't an MC problem.

A.K. · « **Reply #17 on:** July 10, 2017, 09:06:58 am »

Had the same issue (version 23.0.13) with one album (vinyl rip low quality mp3), but only when vst plugin (TB Isone) was enabled. Switched it off and sound was Ok.

23.0.17 seems to be OK with vst plugin enabled.

CallMeSteven · « **Reply #18 on:** July 10, 2017, 09:13:43 am »

Quote from: A.K. on July 10, 2017, 09:06:58 am

Had the same issue (version 23.0.13) with one album (vinyl rip low quality mp3), but only when vst plugin (TB Isone) was enabled. Switched it off and sound was Ok.

23.0.17 seems to be OK with vst plugin enabled.

Did Version 22 cause any of these issues? (It is odd as 23.0.13 caused no issues and yet the audio coding appears not have changed between the versions!!)

A.K. · « **Reply #19 on:** July 10, 2017, 09:31:16 am »

22.0.110 sounds ok vst plugin on and off. In my case it could be some setting in plugin causing the high pitch noise. Maybe something in the mp3 file + vst setting... ?

CallMeSteven · « **Reply #20 on:** July 10, 2017, 09:36:30 am »

Thanks....the mystery continues. I'll try the next version when it comes out & see if it's back or not.

A.K. · « **Reply #21 on:** July 10, 2017, 09:37:55 am »

Bingo! Yes it was indeed the vst setting causing the noise.

blgentry · « **Reply #22 on:** July 10, 2017, 09:51:07 am »

Buggy hardware and drivers just suck. I *personally* would be shopping for a new DAC/sound card.

Brian.

CallMeSteven · « **Reply #23 on:** July 10, 2017, 10:04:34 am »

Awesome Donkey · « **Reply #24 on:** July 10, 2017, 10:05:12 am »

Quote from: blgentry on July 10, 2017, 09:51:07 am

Buggy hardware and drivers just suck. I *personally* would be shopping for a new DAC/sound card.

I agree, especially with the ASUS Xonar Essence sound cards. I own the ASUS Xonar Essence STX sound card and it was by far the worst sound card I ever owned - even worse than Creative cards! It had terrible, buggy drivers, high DPC latency, couldn't use ASIO due to it having popping issues along with latency issues no matter what it was set at, etc. Even the third-party UNi Xonar Drivers package (which are better than the drivers ASUS provide) didn't help too much that I ended up replacing it with my first USB DAC (which was a major upgrade!). In addition I've only heard terrible things from people who owned other Xonar products.

~OHM~ · « **Reply #25 on:** July 10, 2017, 05:46:14 pm »

Quote from: Awesome Donkey on July 10, 2017, 10:05:12 am

I agree, especially with the ASUS Xonar Essence sound cards. I own the ASUS Xonar Essence STX sound card and it was by far the worst sound card I ever owned - even worse than Creative cards! It had terrible, buggy drivers, high DPC latency, couldn't use ASIO due to it having popping issues along with latency issues no matter what it was set at, etc. Even the third-party UNi Xonar Drivers package (which are better than the drivers ASUS provide) didn't help too much that I ended up replacing it with my first USB DAC (which was a major upgrade!). In addition I've only heard terrible things from people who owned other Xonar products.

Gee why am I the last to hear this stuff. I'm using ASUS Xonar DGX Audio, asio, toslink out to 7.1 yamaha and it sounds great!

mwillems · « **Reply #26 on:** July 10, 2017, 06:27:20 pm »

I've had very good expereinces with the old Xonar ST (still in use) and the Xonar U7 (ditto)). Less good with the Xonar DX. It's hit or miss.

blgentry · « **Reply #27 on:** July 10, 2017, 06:45:46 pm »

Quote from: ~OM~ on July 10, 2017, 05:46:14 pm

I'm using ASUS Xonar DGX Audio, asio, toslink out to 7.1 yamaha and it sounds great!

Your use is different than a lot of people's would be. If you're using optical digital out, that probably means that are you re-encoding everything to Dolby Digital. Otherwise the connection wouldn't be able to handle multi-channel signals. This means the sound card is being used in a fundamentally different way.

But it's definitely good to hear that it works well for you.

Brian.

INTERACT FORUM

Author Topic: 23.0.17 - High Pitched Tone bug back (Read 6937 times)