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_vumeter (Read 45694 times) previous topic - next topic
0 Members and 18 Guests are viewing this topic.

Re: foo_vis_vumeter

Reply #300 –
^The point you are repeatedly missing is that no one else is doing this in DirectX. :/

Other solutions are GDI based.

edit: my component uses Direct2D but I can get the HDC required using this technique.

https://learn.microsoft.com/en-us/windows/win32/direct2d/direct2d-and-gdi-interoperation-overview#draw-gdi-content-to-a-direct2d-gdi-compatible-render-target

edit2: with that I use this...

https://github.com/reupen/columns_ui-sdk/blob/6191409f4f18049781b66161fc232d21bb52f468/win32_helpers.h#L79

Re: foo_vis_vumeter

Reply #301 –
Quote from: marc2k3 on
^The point you are repeatedly missing is that no one else is doing this in DirectX. :/

Other solutions are GDI based.

edit: my component uses Direct2D but I can get the HDC required using this technique.

https://learn.microsoft.com/en-us/windows/win32/direct2d/direct2d-and-gdi-interoperation-overview#draw-gdi-content-to-a-direct2d-gdi-compatible-render-target

edit2: with that I use this...

https://github.com/reupen/columns_ui-sdk/blob/6191409f4f18049781b66161fc232d21bb52f468/win32_helpers.h#L79
Thx for your help. I hope @oops can use it.

BTW. I don't have a clue what @Case is using in Wavebar Mini mod. The changelog and prefrences say nothing about the used rendering technique.

Re: foo_vis_vumeter

Reply #302 –
Uploaded 0.8.5 with the "Disallow Fullscreen" option.

Re: foo_vis_vumeter

Reply #304 –
What may be the cause of foobar crash at the moment, when I click "VU Meter (DirectX 12)" in the "Add New UI Element"?
Foobar 2.24.1 x64, freshly installed. Running on Windows 10 x64. dxdiag shows system supprts DX12.

Re: foo_vis_vumeter

Reply #305 –
Quote from: p.h. on
What may be the cause of foobar crash at the moment, when I click "VU Meter (DirectX 12)" in the "Add New UI Element"?
Foobar 2.24.1 x64, freshly installed. Running on Windows 10 x64. dxdiag shows system supprts DX12.

I personally don't setup VU Meter using this method but I tried it and I can confirm it crashes. Once you add it using Add New UI Element, you get a blank element. When you right click on it the crash will occur.

EDIT...Versions before 0.8.0 don't have this issue.

EDIT#2...The crash does not occur if it has VU Meter files in the vumeter folder.

Re: foo_vis_vumeter

Reply #306 –
Quote from: Majestyk on
EDIT#2...The crash does not occur if it has VU Meter files in the vumeter folder.

I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar: "c:\Users\my_username\AppData\Roaming\foobar2000-v2\vumeter\"
but it doesn't change anything. Foobar still crashes.

Re: foo_vis_vumeter

Reply #307 –
Quote from: p.h. on
Quote from: Majestyk on
EDIT#2...The crash does not occur if it has VU Meter files in the vumeter folder.

I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar: "c:\Users\my_username\AppData\Roaming\foobar2000-v2\vumeter\"
but it doesn't change anything. Foobar still crashes.
The default folder for vumeter's skins is in the Profile folder, as in ..foobar2000-v2\profile\vumeter.
If you would rather have it elsewhere you can change the location in Foobar/Preferences/Advanced:

Re: foo_vis_vumeter

Reply #308 –
Quote from: p.h. on
Quote from: Majestyk on
EDIT#2...The crash does not occur if it has VU Meter files in the vumeter folder.

I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar: "c:\Users\my_username\AppData\Roaming\foobar2000-v2\vumeter\"
but it doesn't change anything. Foobar still crashes.


That is the correct folder location. I do not get any crash as long as there are 'proper' bin files inside.

Quote from: sveakul on

The default folder for vumeter's skins is in the Profile folder, as in ..foobar2000-v2\profile\vumeter.


That's also the correct folder location, if you're using a portable build.

Re: foo_vis_vumeter

Reply #309 –
Quote from: sveakul on
The default folder for vumeter's skins is in the Profile folder, as in ..foobar2000-v2\profile\vumeter.
If you would rather have it elsewhere you can change the location in Foobar/Preferences/Advanced:


In my case the "Panels directory" setting was empty. I've entered "c:\Users\my_username\AppData\Roaming\foobar2000-v2\vumeter\", but it didn't change anything.

I ticked "Debug output" checkbox, but I cannot find any log after the crash.

Quote from: Majestyk on
That is the correct folder location. I do not get any crash as long as there are 'proper' bin files inside.

At the moment I have there a few freshly downloaded BINs. Each skin in its own folder.

Re: foo_vis_vumeter

Reply #310 –
Try moving the custom path statement out of the Windows permissions hierarchy and be sure it end with a single backslash, like:

c:\vumeter\

Also, try taking the BIN files out of the bracketed folders first.

Re: foo_vis_vumeter

Reply #311 –
Quote from: p.h. on
What may be the cause of foobar crash at the moment, when I click "VU Meter (DirectX 12)" in the "Add New UI Element"?
Foobar 2.24.1 x64, freshly installed. Running on Windows 10 x64. dxdiag shows system supprts DX12.
Sorry it has taken me long to reproduce this crash, I've been finishing up a different feature. It happens when you have one or more empty folders in the skins/panels directory AND there is not at least one bin/zip/rar file in the entire "vumeter" directory hierarchy. I have implemented fixes and I'm testing them. In the meantime, I thought it would be helpful to know what set up combination to avoid.

I also fixed the failure to load the RAR archive contents in the other thread. My initial analysis was wrong. The issue is the naming of the files inside the archive, not the missing INI file.

Re: foo_vis_vumeter

Reply #312 –
I have installed fresh foobar2000 and foo_vis_meter on another computer. Dropped just a 3 BIN files in the vumeter folder. And it works there.
So I get back to my computer, made an extra, fresh, installation, portable one, copied just the same set of BIN files in the vumeter folder. There are no empty folders inside the vumeter folder. Unfortunately it crashes.

Re: foo_vis_vumeter

Reply #313 –
Quote from: p.h. on
I have installed fresh foobar2000 and foo_vis_meter on another computer. Dropped just a 3 BIN files in the vumeter folder. And it works there.
So I get back to my computer, made an extra, fresh, installation, portable one, copied just the same set of BIN files in the vumeter folder. There are no empty folders inside the vumeter folder. Unfortunately it crashes.
Are you talking about fresh portable installations on BOTH computers?  What exactly is the path statement to the meter folders in the Advanced entries on both installs (screenshots)?

Re: foo_vis_vumeter

Reply #314 –
Quote from: p.h. on

I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar: "c:\Users\my_username\AppData\Roaming\foobar2000-v2\vumeter\"
but it doesn't change anything. Foobar still crashes.

> I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar
What are you talking about?

Please delete the component first.
Also delete the vumeter folder.
Please download the latest component from below.
Download vumeter.7z and unzip it.
Place the vumeter folder in \profile\vumeter

Analog VU Meter Visualisation
https://www.foobar2000.org/components/view/foo_vis_vumeter

vumeter.7z
https://mega.nz/file/NSc2VbDY#vQRW19-1YtKXsSbhYnlCm7OVjKTEUa2Xq_cdsLTkt44
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_vumeter

Reply #315 –
Quote from: sveakul on
Quote from: p.h. on
I have installed fresh foobar2000 and foo_vis_meter on another computer. Dropped just a 3 BIN files in the vumeter folder. And it works there.
So I get back to my computer, made an extra, fresh, installation, portable one, copied just the same set of BIN files in the vumeter folder. There are no empty folders inside the vumeter folder. Unfortunately it crashes.
Are you talking about fresh portable installations on BOTH computers?  What exactly is the path statement to the meter folders in the Advanced entries on both installs (screenshots)?

Sorry for not putting myself clear.

I have foobar installed on two computers: 1. my home computer and 2. at work on my laptop. On both of them, standalone, 64-bit versions. Additionally, a portable one on my home PC. The portable installed just for a test if this will behave the same as standalone (which it indeed does).

Also an old, 32-bit, 1.6 version with foo_vis_vumeter (foobar shows the vumeter component's version is "2013-02-16"). The one works flawlessly.

The issue manifests only on my home PC, for foobar 2.24.1 x64 with foo_vis_vumeter 0.8.5.0. Both standalone and portable versions are affected.

Below screenshots for both standalone and portable versions installed on my home PC.
- portable version, vumeter folder location and its contents:

- portable's version settings:

- standalone version, vumeter folder location and its contents:

- standalone's version settings:


As you can see, each of the vumeter folders has the same set of BIN files. Those proved to work fine on my work laptop, hence I test using them.

Quote from: Air KEN on
Quote from: p.h. on

I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar: "c:\Users\my_username\AppData\Roaming\foobar2000-v2\vumeter\"
but it doesn't change anything. Foobar still crashes.

> I've copied all BIN files that worked with version 2013-02-16 to the folder created by the foobar
What are you talking about?
I've meant, that at first I've copied BIN files, that I have used with the old 1.6 foobar. Now I test with those few you can see at the screenshots above. All proved to be fine.
Quote from: Air KEN on
Please delete the component first.
Also delete the vumeter folder.
Please download the latest component from below.
Download vumeter.7z and unzip it.
Place the vumeter folder in \profile\vumeter

Thank you for your set of skins. I will definitely give them a try once I will make the vumeter work. As I have the most recent version of both the foo_vis_vumeter and foobar and proved BIN files, I assume I have already performed the test you've described.

Re: foo_vis_vumeter

Reply #316 –
Please temporarily move the old vumeter to your desktop. Then place the downloaded vumeter and test it.
That's what testing is all about.
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_vumeter

Reply #317 –
Quote from: Air KEN on
Please temporarily move the old vumeter to your desktop. Then place the downloaded vumeter and test it.
That's what testing is all about.

I did this for both standalone and portable versions on my home computer. Crashes just the same.

Maybe I am missing something here, but I don't understand how could it help and what it could prove?
I have already tested my set of 3 BIN files and proved they work just fine on my work laptop. The contents of the vumeter folder is exactly the same. No extra files, no extra nor empty subfolders. They shall not cause any issues on any other foobar 2.24.1 + foo_vis_vumeter 0.8.5 installation.

Re: foo_vis_vumeter

Reply #318 –
> They shall not cause any issues on any other foobar 2.24.1 + foo_vis_vumeter 0.8.5 installation.

If it were me, I would copy these to Portable and use them. This is the end.
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_vumeter

Reply #319 –
Quote from: Air KEN on
> They shall not cause any issues on any other foobar 2.24.1 + foo_vis_vumeter 0.8.5 installation.

If it were me, I would copy these to Portable and use them. This is the end.

As I wrote in a few earlier posts, portable version crashes as well. No matter if I use your BIN files or mine.
The BIN files work fine on another computers, like yours and my work laptop. Hence, they must be ok. We can rule them out beyond any doubt.

Re: foo_vis_vumeter

Reply #320 –
If you can't add any crash reports from profile/crash reports there's no where to go from here.  You must just have a "knackered" computer--bad RAM, drive shot, corrupted drivers, mystery services, who knows.  As KEN put it, "this is the end."

Re: foo_vis_vumeter

Reply #321 –
Long shot: have you checked if your home pc supports dx12?

run dxdiag to check


if possible update your graphics driver to the latest


iirc the new vu meter requires dx12, the old one doesn’t need dx12

Re: foo_vis_vumeter

Reply #322 –
Is foobar2000 really not offering to produce a minidump file when it crashes? A minidump would make it straightforward to find the crash point.

Things I can think of that you should ensure:
  • A version of Windows 10 or 11 that supports DirectX 12; check your version reported by "winver". The API versions for each of the subcomponents are as follows:
    Direct3D 12 (Feature Level 11_0), DXGI 1.6, Direct2D 1.3, DirectWrite 1.3
  • If some component or your video adapter does not support DirectX 12 (see "dxdiag" suggestion above) the component falls back on WARP. To make the fallback work, you need to use the x64 version and place the WARP DLL (d3d10warp.dll) next to foo_vis_vumeter.dll.
  • Check that your processor supports more modern x86 extensions. If your CPU ISA support is lower than Intel's Haswell generation then the component might take exception at unknown instructions.
  • Ensure that the user launching foobar2000 has access permissions to read the folders and files where you're placing the BIN files. Also it might help to unblock the files (mark the files as trusted if you brought them over from an external computer or the internet).
  • Further back we found that other software running on the machine was interfering with the video adapter. In that case it was RivaTuner. If you have any services/apps running on the crashing computer such as OBS, overclocking utilities, frame counters or custom profiles/tweaks on your video card drivers, try turning those off. Process Explorer and Process Monitor can help narrow down what foobar2000 is doing and what it is loading just before it crashes.

The only other thing I can provide is an updated version. The downside of the updated version is that it has lots of additional stuff in the initialization path (relative to 0.8.5) that can cause you additional problems.

Re: foo_vis_vumeter

Reply #323 –
Yes, foobar2000 offers minidumps, when it crashes. So far I've sent them using its "Send" button. Here you have a few attached.

Seems my old i5-4570 (Haswell) has DirectX 12 drivers:

Maybe feature level too low?:


For the purpose of a test, I copied "c:\Windows\System32\d3d10warp.dll" next to "foo_vis_vumeter.dll". See minidump attached. Does the fact, that foobar2000 crashes in the scenario mean, the issue is not caused by DirectX?

The user launching foobar2000 has administrative privileges. Furthermore, I have tested foobar2000 being run as an administrator.

Indeed, the BIN files were blocked, but unblocking them didn't help.

See another minidump - after unblocking, with the WARP and foobar2000 run as admin.

I have none of the kind of software, you've mentioned, that could interfere.

Re: foo_vis_vumeter

Reply #324 –
PGGB-RT 5.6.5 (foo_pggb_rt)
The CPU is not supported.
Do you use it regularly?

https://hydrogenaud.io/index.php/topic,123924.msg1056871.html#msg1056871

Before deleting, you have to right-click on the Playlist view and select Undelete.
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)