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: New VST adapter for foobar2000 (Read 85096 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

Re: New VST adapter for foobar2000

Reply #175 –
I am afraid there is something wrong with FB2.24 as stated in other topic - my VST visualisations also are very (realy very) choppy. Up til 2.1.16 it was OK.

Re: New VST adapter for foobar2000

Reply #177 –
Quote from: Case on
"VST worker terminated" could be caused by a crash in a VST plugin hosted in the sandbox. There might be further evidence of that in Windows event viewer's application logs.

Thanks Case. Here is the Event Viewer detail:

Version=1
EventType=APPCRASH
EventTime=133774854150037027
ReportType=2
Consent=1
UploadTime=133774854158599568
ReportStatus=268435456
ReportIdentifier=5e63ef7b-aa17-4e41-bc87-5c5bb59cccb6
IntegratorReportIdentifier=dc975b60-4abd-483b-b07e-011ef7301e0a
Wow64Host=34404
NsAppName=fooVSTHost64.exe
AppSessionGuid=00002c18-0004-00d4-961a-dc618543db01
TargetAppId=W:0006f3ed06ee5b4faf5a91060295d89031010000ffff!000044910417e1f766636afac75786a17c2dc2e78087!fooVSTHost64.exe
TargetAppVer=2023//05//30:09:58:37!0!fooVSTHost64.exe
BootId=4294967295
TargetAsId=36164
UserImpactVector=808452912
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=f99f118e2506dfa127ae1c8c5f2f9a0c
Response.BucketTable=4
Response.LegacyBucketId=1706332698037950988
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fooVSTHost64.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=6475c8cd
Sig[3].Name=Fault Module Name
Sig[3].Value=igxelpicd64.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=31.0.101.5333
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=65d59ac6
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0000000000262a4e

Re: New VST adapter for foobar2000

Reply #178 –
Quote from: Basilderat on
[...]
Sig[3].Name=Fault Module Name
Sig[3].Value=igxelpicd64.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=31.0.101.5333
The VST crashes inside Intel graphics drivers. It's not foobar's fault. The VST in question may do something wrong, but this is most likely a driver bug.

Re: New VST adapter for foobar2000

Reply #179 –
Quote from: Case on
Quote from: Basilderat on
[...]
Sig[3].Name=Fault Module Name
Sig[3].Value=igxelpicd64.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=31.0.101.5333
The VST crashes inside Intel graphics drivers. It's not foobar's fault. The VST in question may do something wrong, but this is most likely a driver bug.

Hi Case, that's what I had figured too, so I updated the Intel® Iris® Xe Graphics driver to version 32.0.101.6314 dated 2024-11-26 and it has fixed the problem, Thank you so much for your help with this, hugely appreciated mate!

Cheers, Peter
 

Re: New VST adapter for foobar2000

Reply #180 –
Quote from: wojak on
I am afraid there is something wrong with FB2.24 as stated in other topic - my VST visualisations also are very (realy very) choppy. Up til 2.1.16 it was OK.
Problem confirmed, thanks for reporting. There will be a 2.24.1 with a fix for this before the end of the year.
Microsoft Windows: We can't script here, this is bat country.

Re: New VST adapter for foobar2000

Reply #181 –
Quote from: Peter on
Quote from: wojak on
I am afraid there is something wrong with FB2.24 as stated in other topic - my VST visualisations also are very (realy very) choppy. Up til 2.1.16 it was OK.
Problem confirmed, thanks for reporting. There will be a 2.24.1 with a fix for this before the end of the year.

I am not sure if it is related to the above problem but lately I found out that when playing .m2ts files in FB (with ffmpeg decoder wrapper) and watching video part of the file with either mpv or youtube plugin the video gets desynchronized from the audio (but not always, rather the later the more or get desynchronized at some point and stay like that to the end). It is not choppy like vst, it looks ok but is just out of sync which is very annoying especially when you see someone talking or playing drums and the moves are "in wrong time". WIN10/64, FB2.24/64. All plugins at newest versions. It didn't happen with previous FB versions.

Re: New VST adapter for foobar2000

Reply #182 –
The component does not work properly with Dirac processor VST3 plugin.
Initially I experiencied this problem in a benchmark listening with another player (Jriver), of course with same plugin and same Digital Room Correction filter, so i decided to take some measurements to show the problem.
I used the RTA function of REW with a minidsp-UMIK-1 microphone and a wav file, generated by REW, containing random pink noise at -20 db 48 khz 32 bit floating point.

I use foobar from about 15 years with any type of file PCM or DSD at any FS (from 44.100 to 192 khz, from DSD64 to DSD256) and bit deepth (16, 24, 32) without any problem, click, scratch, noise...

All the parameters of the measures (Smoothing of the curve, seconds of average...) are described inside figures.

The figure '1 rew alone' shows the pink noise directly streamed from REW to the DAC.
The figure '2 jriver no dirac' shows the file reproduced by Jriver player, in this case the plugin is selected in the preferencies of the player but the DRC filter is not activated in the VST control panel of Dirac plugin
The figure '3 foobar no dsp' shows the file reproduced by Foobar player, in this case the component VST adapter is not loaded in the DSP Manager Active list.

Still now it is all OK and the three measures above are very similar.

The first problem there is when i load the component VST Adapter in the DSP Manager and I select the DIRAC plugin.
The figure '4 foobar no dirac' shows the file reproduced by Foobar player, the DRC filter is not activated in the VST control panel of Dirac plugin, so the curve should be the same of the three above measures (1, 2, 3)
Instead the misure is very different and moreover foo_vis_spectrum_analyzer 0.7.6.2 shows an hole in the range between 500-900 hz (see figure '5 foobar no dirac spectro'), the hole is clearly present in the listening where there is a big change of the tone of the pink noise.

When I activate the DRC filter in the VST Control Panel of Dirac I obtain the following behaviors.

In Jriver there is a new curve (see figure '6 jriver dirac') with a clear intervention of the DRC filter (the hole at 40 hz is reduced and the curve is smoothed)
In Foobar i obtain (see figure '7 foobar dirac')  quite the same curve of figures 1,2,3, a reproduction of the pink noise without filtering. This strange situation is confirmed by the spectrum analizer where the hole at 500-900 hz disappear (see figure '8 foobar dirac spectro').

All the misures has been take with one player active at the moment of the detection and to be more sure i did the Foobar set, i restarted the PC and then i did the Jriver set, to avoid any strange interferences in the Dirac plugin.

I perfectly know that Dirac is a licensed software and I don't know if the developper (Peter) can riproduce this problem obtaining support from Dirac company.
If I can joke I say that it was very funny to listen pink noise for a whole day at 75-80 db, so I hope that Peter can solve this problem.

Of course I am available to supply any other information, log, trace and whatever he needs to fix it.

Leonardo

Re: New VST adapter for foobar2000

Reply #183 –
I'm trying to setup multi channel to binaural (with head tracking) plugins and I'm not finding anything working. These take 11 or 12 channels in (7.0.4 or 7.1.4, in the configuration I need) and 2 channels out. APL Virtuoso crashes when you set it for Atmos 7.1.4A speaker config, and Sparta Binauraliser isn't passing audio correctly (mostly silence).

Can this component be made to support 12 channel in/or or 12 ch in 2 ch out VST3?

Referenced plugins:
https://apl-hud.com/product/virtuoso-plugins/
https://leomccormack.github.io/sparta-site/docs/plugins/sparta-suite/#binauraliser


 

Re: New VST adapter for foobar2000

Reply #184 –
There is no way to directly edit numeric values in the Q-4 FabFilter. I double click and the edit box opens, but the keyboard does not work. At the same time I can cut and paste with the mouse through the context menu.