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 59400 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: New VST adapter for foobar2000

Reply #175 –
"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.

Re: New VST adapter for foobar2000

Reply #176 –
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 #178 –
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 #179 –
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 #180 –
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 #181 –
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 #182 –
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.