Page 28 of 28

Re: new pvst beta (updated 25-Oct-2021)

Posted: Wed Oct 27, 2021 6:20 pm
by wde
Thanks!

Re: new pvst beta (updated 25-Oct-2021)

Posted: Thu Oct 28, 2021 10:08 am
by polac
I really hope the save bug is sorted out, fingers crossed.

Re: new pvst beta (updated 25-Oct-2021)

Posted: Tue Nov 02, 2021 2:20 pm
by skizzo
@polac: You know my story - all things work perfectly, no more probs here!

Re: new pvst beta (updated 25-Oct-2021)

Posted: Tue Nov 02, 2021 11:01 pm
by mcbpete
Never knew about the application until last year when I got a new (and rather troublesome to initially diagnose the fault) laptop, and got tech support to aid my repair via this tool - but since have got rather 'obsessed' with Window's built in app Reliability Monitor (more specifically getting a run of days without any kind of warning or critical events so the graph heads towards a fabled 10/10 score :D ). I notice that if I load Buzz with any new VST (or VSTi) installed since last loading (specifically new, rather than updates to older existing versions of the VST/i) that Reliability Monitor will always complain of a critical event claiming that scan.x64.exe has 'stopped working'.

There doesn't actually seem to be any visible problem, Polac will successfully scan that plugin and add it to my machine index, just wondering quite why Windows itself seems to kick up a fuss regarding what seems to be a non-issue. Does anyone else get this critical event logged in Reliability Monitor ?

Here's an example error log (Had just installed Black Rooster Audio - VPRE-73HE before launching Buzz). The plugin itself works perfectly and appears in the gear list:
Faulting application name: scan.x64.exe, version: 0.0.0.0, time stamp: 0x5ca48c8e
Faulting module name: VPRE-73HE.dll, version: 2.5.8.0, time stamp: 0x617175b7
Exception code: 0xc0000005
Fault offset: 0x00000000000f4655
Faulting process id: 0x88c
Faulting application start time: 0x01d7cf75de5ab6df
Faulting application path: C:\Program Files (x86)\Jeskola\Buzz\bin64\scan.x64.exe
Faulting module path: C:\Program Files\Vstplugins\Black Rooster Audio\VPRE-73HE.dll
Report Id: c22f0dce-d293-4a95-a783-550e7b661226
Faulting package full name:
Faulting package-relative application ID:
(apologies to those that have now also fallen for the compulsion of getting a 10/10 score run in Reliability Monitor!)

Re: new pvst beta (updated 25-Oct-2021)

Posted: Sun Nov 07, 2021 1:13 pm
by wde
polac wrote:
Thu Oct 28, 2021 10:08 am
I really hope the save bug is sorted out, fingers crossed.
I haven't had time to really stress test the new version but at least I haven't encountered issues with some of the bigger plugins. Looking good so far :)

One issue I noticed that might be easier to reproduce.
  1. Start Buzz 32, create a more complex song including many big VSTs.
  2. Add 64bit version of Ozone 8 Standard before Master and select some preset.
  3. Save song
  4. Load song.
  5. If problem occurred, then Ozone crashes when loading and I actually need to rename ozone dll/remove it so that I can load the song again. You might need to play around with the song machines to find correct combination.
Other things:
  • If you are able to create this reproducible setup then saving the song with Ozone 8 64bit and closing Buzz will not close vst.x64.dll process (hinting that something went wrong when saving).
  • Interestingly 32bit version of Ozone 8 will not reproduce this issue in the song where 64bit Ozone does.
Maybe this is Ozone issue and I'm fine using the 32 bit version just in case.

Re: new pvst beta (updated 25-Oct-2021)

Posted: Tue Nov 16, 2021 11:02 am
by polac
One issue I noticed that might be easier to reproduce.

Start Buzz 32, create a more complex song including many big VSTs.
Add 64bit version of Ozone 8 Standard before Master and select some preset.
Save song
Load song.
If problem occurred, then Ozone crashes when loading and I actually need to rename ozone dll/remove it so that I can load the song again. You might need to play around with the song machines to find correct combination.
I was not able to reproduce it here yet, but i only have Ozone 8 Elements installed here. I did save a project with 10 x64 plugins(both vst2 and vst3) and Ozone, all did load just fine here. However I did not edit/insert patterns in this scenario.

Re: new pvst beta (updated 25-Oct-2021)

Posted: Tue Nov 16, 2021 11:05 am
by polac
mcbpete wrote:
Tue Nov 02, 2021 11:01 pm
Never knew about the application until last year when I got a new (and rather troublesome to initially diagnose the fault) laptop, and got tech support to aid my repair via this tool - but since have got rather 'obsessed' with Window's built in app Reliability Monitor (more specifically getting a run of days without any kind of warning or critical events so the graph heads towards a fabled 10/10 score :D ). I notice that if I load Buzz with any new VST (or VSTi) installed since last loading (specifically new, rather than updates to older existing versions of the VST/i) that Reliability Monitor will always complain of a critical event claiming that scan.x64.exe has 'stopped working'.

There doesn't actually seem to be any visible problem, Polac will successfully scan that plugin and add it to my machine index, just wondering quite why Windows itself seems to kick up a fuss regarding what seems to be a non-issue. Does anyone else get this critical event logged in Reliability Monitor ?

Here's an example error log (Had just installed Black Rooster Audio - VPRE-73HE before launching Buzz). The plugin itself works perfectly and appears in the gear list:
Faulting application name: scan.x64.exe, version: 0.0.0.0, time stamp: 0x5ca48c8e
Faulting module name: VPRE-73HE.dll, version: 2.5.8.0, time stamp: 0x617175b7
Exception code: 0xc0000005
Fault offset: 0x00000000000f4655
Faulting process id: 0x88c
Faulting application start time: 0x01d7cf75de5ab6df
Faulting application path: C:\Program Files (x86)\Jeskola\Buzz\bin64\scan.x64.exe
Faulting module path: C:\Program Files\Vstplugins\Black Rooster Audio\VPRE-73HE.dll
Report Id: c22f0dce-d293-4a95-a783-550e7b661226
Faulting package full name:
Faulting package-relative application ID:
(apologies to those that have now also fallen for the compulsion of getting a 10/10 score run in Reliability Monitor!)
It's odd it only happens with scan.x64.exe and not with the scan.exe, they are both the same codewise.