Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_vis_milk2 (Read 22065 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_vis_milk2

Reply #125 –
You've reported multiple crashes already, right?

--------
OS: Windows 10
Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz 3.50 GHz
RAM: 16.0 GB
GPU processor: NVIDIA GeForce GTX 980 Ti
--------
Are your CPU, GPU and drives in good condition?

Is the problem with using these components at the same time?

foo_vis_spectrum_analyzer
foo_vis_vumeter
foo_wave_minibar_mod
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: foo_vis_milk2

Reply #126 –
Quote from: Mekoz on
I'm at a loss though as to why I'm crashing when trying to run other components at same time. I've tried updating Graphics drivers, reinstalling foobar2000, etc. On its own its absolutely fine, any insight would be greatly appreciated.
Visual Studio is not bringing up the crash stack with the dump (this is a problem on my end). So, looking at it with WinDbg (I'm a bit more limited there), it seems something is nuking your render target view pointer. I have not seen this before. I do not know what can cause this other than something else you have running on your machine. Aside from other foobar2000 components that might be hacking at the window directly one standout is the RivaTuner hook DLL. Can you try running without that loaded? Why do you even need to have that loaded into foobar2000?

Re: foo_vis_milk2

Reply #127 –
Quote from: Air KEN on
You've reported multiple crashes already, right?

--------
OS: Windows 10
Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz 3.50 GHz
RAM: 16.0 GB
GPU processor: NVIDIA GeForce GTX 980 Ti
--------
Are your CPU, GPU and drives in good condition?

Is the problem with using these components at the same time?

foo_vis_spectrum_analyzer
foo_vis_vumeter
foo_wave_minibar_mod

foo_vis_spectrum_analyzer
foo_vis_vumeter

When using these two components along with "fo_vis_milk2" i crash

Re: foo_vis_milk2

Reply #128 –
Quote from: oops on
Quote from: Mekoz on
I'm at a loss though as to why I'm crashing when trying to run other components at same time. I've tried updating Graphics drivers, reinstalling foobar2000, etc. On its own its absolutely fine, any insight would be greatly appreciated.
Visual Studio is not bringing up the crash stack with the dump (this is a problem on my end). So, looking at it with WinDbg (I'm a bit more limited there), it seems something is nuking your render target view pointer. I have not seen this before. I do not know what can cause this other than something else you have running on your machine. Aside from other foobar2000 components that might be hacking at the window directly one standout is the RivaTuner hook DLL. Can you try running without that loaded? Why do you even need to have that loaded into foobar2000?

RivaTuner hook DLL comes from using ATI afterburner, i wasn't aware it was affecting Foobar2000. It displays statistics, FPS etc. It could be the culprit i was looking for, currently testing now. Thanks for the heads up, will report back.

Re: foo_vis_milk2

Reply #129 –
I'm not experiencing any more crashes since closing ATI Afterburner/RivaTuner.

Thank you so much for the infomation. This has been driving me crazy for a long time. Everything is working perfectly now.

Kind regards

Re: foo_vis_milk2

Reply #130 –
@Mekoz
That's really good.
I'm not doing anything useful but it's been bothering me for so long.
Wow, you've been reporting crashes for a long time now. Hahaha.  :))
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: foo_vis_milk2

Reply #131 –
Quote from: Mekoz on
I'm not experiencing any more crashes since closing ATI Afterburner/RivaTuner.
Quote
Update on this problem, turns out these issues are likely due to MSI Afterburner and RivaTunerStatisticsServer trying to hook into the the program- so users of MSI Afterburner and RivaTuner, to fix this, you need to open RivaTuner's GUI and add foobar2000.exe to the application profile list, and set detection for it to "None" to prevent it from trying to hook into foobar2000s video buffers, which is what was leading to all of the crashes for whatever reason.
~ https://hydrogenaud.io/index.php/topic,122847.msg1015337.html#msg1015337
Quis custodiet ipsos custodes?

Re: foo_vis_milk2

Reply #133 –
It was you who provided the clue.  :)
Quis custodiet ipsos custodes?

Re: foo_vis_milk2

Reply #134 –
I'm trying foo_vis_milk2 in foobar2000 for the first time, and I'm having one fairly prominent bug:  When the song changes, the new song's title fades onto the screen as expected, but a moment later when that text should be added into the mix and smeared away with the rest of the visualization, instead a giant white rectangle is added to the mix in its place.

Actually, as I was writing that, I went back to test it some more, and now, not even the initial "floating" version of the title works; I'm just seeing a white rectangle fade onto the screen the way the title usually does (and then that same rectangle gets smeared into the mix).  Is this a known issue?