Old 01-13-2017, 04:02 PM   #1
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default Lots of freezing and crashing

I'm currently on the latest build and that last few releases as well.

Here's my crash dump, preferences and problem session:

LINK: https://www.dropbox.com/sh/yf5kphdk2...Sg2JU1JVa?dl=0

Can someone please help me resolve the crash dumps. I'm not finding much in the event viewer but I did find these crash dump files in my user folder.

Some of the crash dumps are forced dumps, which means it dumps everything that's in the memory at the time. That's why a couple of these are super large files.

The crashes almost always occur while moving the edit cursor. I have smooth seek on. Could that affect it. I've changed a few of my buffer and playback settings as you can see in my preference file. If there is anything in there that needs adjusting please let me know.

SYSTEM SPECS

Window 10 Pro (latest Build)
Reaper Pre Release 5.32 RC2
Kontakt 5.6.5
2 x 12core 3GHz Intel Xeon
128GB Ram
14 x 500GB SSDs
srdmusic is offline   Reply With Quote
Old 01-13-2017, 04:13 PM   #2
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default Crash log

Faulting application name: reaper.exe, version: 5.3.1.62, time stamp: 0x5877cdb3
Faulting module name: ucrtbase.dll, version: 10.0.14393.0, time stamp: 0x578997b5
Exception code: 0xc0000409
Fault offset: 0x000000000006ea1e
Faulting process id: 0x3e3c
Faulting application start time: 0x01d26defc7bf9d93
Faulting application path: C:\Program Files\REAPER\reaper.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: ac482e70-9e22-4332-ab99-f190afc93716
Faulting package full name:
Faulting package-relative application ID:

System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2017-01-13T22:54:47.534579100Z

EventRecordID 96124

Channel Application

Computer SRD-MASTER

Security


- EventData

reaper.exe
5.3.1.62
5877cdb3
ucrtbase.dll
10.0.14393.0
578997b5
c0000409
000000000006ea1e
3e3c
01d26defc7bf9d93
C:\Program Files\REAPER\reaper.exe
C:\Windows\System32\ucrtbase.dll
ac482e70-9e22-4332-ab99-f190afc93716
srdmusic is offline   Reply With Quote
Old 01-13-2017, 04:14 PM   #3
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default Crash 2

The program reaper.exe version 5.3.1.62 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 37cc
Start Time: 01d26de11286f064
Termination Time: 60000
Application Path: C:\Program Files\REAPER\reaper.exe
Report Id: dd11ad83-d9e2-11e6-8db5-001086800144
Faulting package full name:
Faulting package-relative application ID:

- EventData

reaper.exe
5.3.1.62
37cc
01d26de11286f064
60000
C:\Program Files\REAPER\reaper.exe
dd11ad83-d9e2-11e6-8db5-001086800144


55006E006B006E006F0077006E0000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 006E0055 006E006B 0077006F 0000006E
0010: 0000


In Bytes

0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00
srdmusic is offline   Reply With Quote
Old 01-13-2017, 04:20 PM   #4
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

The program reaper.exe version 5.3.1.62 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 37cc
Start Time: 01d26de11286f064
Termination Time: 60000
Application Path: C:\Program Files\REAPER\reaper.exe
Report Id: dd11ad83-d9e2-11e6-8db5-001086800144
Faulting package full name:
Faulting package-relative application ID:

- EventData

reaper.exe
5.3.1.62
37cc
01d26de11286f064
60000
C:\Program Files\REAPER\reaper.exe
dd11ad83-d9e2-11e6-8db5-001086800144


55006E006B006E006F0077006E0000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 006E0055 006E006B 0077006F 0000006E
0010: 0000


In Bytes

0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00 ..
srdmusic is offline   Reply With Quote
Old 01-13-2017, 04:21 PM   #5
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

Faulting application name: reaper.exe, version: 5.3.1.62, time stamp: 0x5877cdb3
Faulting module name: ucrtbase.dll, version: 10.0.14393.0, time stamp: 0x578997b5
Exception code: 0xc0000409
Fault offset: 0x000000000006ea1e
Faulting process id: 0x3e3c
Faulting application start time: 0x01d26defc7bf9d93
Faulting application path: C:\Program Files\REAPER\reaper.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: ac482e70-9e22-4332-ab99-f190afc93716
Faulting package full name:
Faulting package-relative application ID:

reaper.exe
5.3.1.62
5877cdb3
ucrtbase.dll
10.0.14393.0
578997b5
c0000409
000000000006ea1e
3e3c
01d26defc7bf9d93
C:\Program Files\REAPER\reaper.exe
C:\Windows\System32\ucrtbase.dll
ac482e70-9e22-4332-ab99-f190afc93716
srdmusic is offline   Reply With Quote
Old 01-13-2017, 05:24 PM   #6
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

Those crashes all indicate ucrtbase.dll, which is a run-time library that is not used by REAPER. It is most likely a plugin crashing, or the system simply running out of resources.

The usual thing to do in this case is offline all the plugins and bring them back one at a time to isolate the offending plugin. However, your project contains 833 tracks and 754 plug-ins, so it may be difficult to figure out.
schwa is offline   Reply With Quote
Old 01-14-2017, 01:29 PM   #7
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default Plugin Crash

I saw in the event viewer that Zebra VST3 crashed at one point.

My assistant had place VST3 Zebra patches in my template which are known to crash.

I've gone through and replaced all the patches with VST2.

I'm testing the new template today and I'll let you guys know if that solved it.

FYI I was seeing very similar crashes in Cubase and thus switch to Reaper hopping to sovlve that. I was a part of Steinberg's BETA team and one of the things we found was a crash in FabFilter when it tried to access Open GL.

Is there a way to have reaper disable Open GL for testing. Contrastly, is there a way to force more GUI or plugin visual resources to be processed on my W7100 AMD card?
srdmusic is offline   Reply With Quote
Old 01-14-2017, 01:40 PM   #8
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

REAPER doesn't really have any control over how plugins interact with the system graphics. Disabling hardware acceleration on the machine might just make things worse as it may force plugins that are trying to use openGL to instead use a software implementation.

I'm sure you have reasons for wanting such a massive project, but you are likely to get better performance and stability overall if you could find a way to break the project into smaller parts. Perhaps you could use subprojects?

Last edited by schwa; 01-14-2017 at 01:52 PM.
schwa is offline   Reply With Quote
Old 01-14-2017, 01:50 PM   #9
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,721
Default

Quote:
Originally Posted by schwa View Post
Perhaps you could use subprojects
Or freeze some tracks.
Justin is offline   Reply With Quote
Old 01-14-2017, 02:57 PM   #10
snooks
Banned
 
Join Date: Sep 2015
Posts: 1,650
Default

Quote:
Originally Posted by srdmusic View Post
I saw in the event viewer that Zebra VST3 crashed at one point.

My assistant had place VST3 Zebra patches in my template which are known to crash.

I've gone through and replaced all the patches with VST2.

I'm testing the new template today and I'll let you guys know if that solved it.

FYI I was seeing very similar crashes in Cubase and thus switch to Reaper hopping to sovlve that. I was a part of Steinberg's BETA team and one of the things we found was a crash in FabFilter when it tried to access Open GL.

Is there a way to have reaper disable Open GL for testing. Contrastly, is there a way to force more GUI or plugin visual resources to be processed on my W7100 AMD card?
Remember in REAPER that you can firewall suspect plugins by running them in a separate or a dedicated process.

Right-click the FX/instrument in question in the FX browser and select "Run as". Then either choose "Separate process" to run all the plugins with this option in one additional shared process, or "Dedicated process" for an exclusive one for that plugin instance.

Then if one of those plugins crash the chances of it taking down REAPER are greatly reduced. You can embed the GUI of the bridged plugins in the option at the bottom of the menu for a more integrated feel.

It has to be mentioned that managing all of those additional processes consumes more resources, but the options are more tools in the box to be used as and when required.
snooks is offline   Reply With Quote
Old 01-14-2017, 04:11 PM   #11
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

Thanks for the info about the separate processes snooks.

Justin and Schwa, I'm very impressed with Reaper's CPU consumption and customization abilities.

I've been a film composer for sometime now and worked my way through almost every DAW. IMHO no one gives the user more options that Reaper. Thank you for your dedication to opening up the software and your involvement listening to your user base.

There are a few workflow snags I've run into that I'd love to discuss. I've been told by others on the forum that some of these requests are beyond being able to implement via user script.

You have convinced a couple of my composer friends to switch and I'd like to help in any way I can to bring more users over to Reaper.

If the Pre-Release forum is the best place to post feature requests please let me know. Otherwise, I can direct message you my email address.

Last edited by srdmusic; 01-16-2017 at 11:17 AM.
srdmusic is offline   Reply With Quote
Old 01-14-2017, 04:16 PM   #12
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

So I converted the Zebra's over to VST2 today and I'm still having the crashes while seeking to a new location in sequence with no instruments online. I only have my BUSS and reverb plugins turned on. Here's the list:

Slate Digital - Virtual Buss Compressor
Slate Digital - Virtual Mix Rack
Soft Tubes - Focusing EQ
DMG Audio - Limitless
Relab - LEX 480L
Valhalla - Shimmer
Lowender

Valhalla Shimmer has a know bug that seems to crash Reaper and Cubase when loading the plugin on a track. Going back a version to 1.0.2 fixes this issue. If you guys have seen problems with any of the other plugins listed above please let me know so that I can inform the manufacturer.
srdmusic is offline   Reply With Quote
Old 01-14-2017, 04:24 PM   #13
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default Smooth Seek Crash

I can confirm that when 'Smooth Seek' is turned, Reaper freezes/ crashes when locating with the mouse on the ruler, arrange page or the midi editor. The problem is exacerbated when I click to seek to a new location multiple times.

With Smooth Seek 'uncheck' in the Reaper preferences, I can click anywhere in the timeline as fast as I want and it won't crash. I have a feeling this has something to do with buffering the plugins. When locating reaper has to rebuffer and when smooth seek is on I would imagine that's what's complicating things. Can you guys confirm this or have you seen this issue before?

Here's my latest template if you guys want to test with it.

LINK: https://www.dropbox.com/s/noahafaffd...0VST2.rpp?dl=0
srdmusic is offline   Reply With Quote
Old 01-14-2017, 07:44 PM   #14
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

I'm not able to make the project crash here, but we don't have all of your plugins.

The ideal way for you to isolate which plugin is causing the problem would be to offline all of them, try to reproduce the issue, then bring the plugins back online one at a time until you are able to reproduce it. If you can isolate which plugin it is, we can probably figure out specifically what the cause is.

For convenience, you can check the box marked "open with FX offline (recovery mode)" in the open project dialog, to start the process.
schwa is offline   Reply With Quote
Old 01-14-2017, 08:12 PM   #15
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

Actually, I can reproduce the crash with the Slate virtual mix rack plugin (which I can confirm uses the run-time DLL that is reported in all of your crash logs above).

Unfortunately, this plugin won't run under the debugger because of anti-piracy components, so I can't be more specific about exactly why it's crashing.
schwa is offline   Reply With Quote
Old 01-14-2017, 10:04 PM   #16
moliere
Human being with feelings
 
moliere's Avatar
 
Join Date: Mar 2007
Location: Wellington, New Zealand
Posts: 2,261
Default

Possibly not related, but funny you refer to the Slate plugins. I get lockups and crashes with the Slate VMR and VTM (VST2) when trying to add to large projects. My workaround in that particular case is to open the plugins in a separate tab first, then they add to the large project fine. Feels like something to do with the iLok communication tbh.
moliere is offline   Reply With Quote
Old 01-14-2017, 10:45 PM   #17
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

Thanks for the info moliere. I'm using the Slate stuff as VST3 so that they don't use any processing when nothing is playing through them. Traditionally I've had better luck with their VST3's.

Have you let Slate know about the freezing? If not I have a contact at Slate that I can forward your findings to.
srdmusic is offline   Reply With Quote
Old 01-14-2017, 11:03 PM   #18
moliere
Human being with feelings
 
moliere's Avatar
 
Join Date: Mar 2007
Location: Wellington, New Zealand
Posts: 2,261
Default

Quote:
Originally Posted by srdmusic View Post
Thanks for the info moliere. I'm using the Slate stuff as VST3 so that they don't use any processing when nothing is playing through them. Traditionally I've had better luck with their VST3's.

Have you let Slate know about the freezing? If not I have a contact at Slate that I can forward your findings to.
They had some clicking and dropouts with VST3 a little while back in Reaper (which I'm pretty sure was fixed), but I never ended up going back to them. Might be worth me giving VST3 another go.

No, I haven't let them know, I'd love a contact to have a chat to about it, thanks. While my workaround allows me to do stuff, it's a bit annoying.
moliere is offline   Reply With Quote
Old 01-14-2017, 11:14 PM   #19
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

I loaded my template with all the fx off and was able to replicate the freezing problem with 'smooth seek' turned on. Since all the plugins were offline could it be a problem with the number of tracks or some sort of plugin authorization that's happening every time Reaper seeks to a new location?

I was not able to replicate the error in a blank session. I was also not able to cause the freeze in a blank session with each one of the above single plugins loaded and turned on. Once I turned off 'smooth seek' off, the problem also seemed to not be reproducible.

One thing to note is that I do have some of the auto save functions turned on and saving every 3 mins. This usually causes the gui to freeze up for a second or 2 but comes back after the backup is complete. When seeking/ rebuffering could auto-save cause a longer freeze since it's trying to process two things at once?


During the freezes I forced a couple of crash dumps in task manager. Below is a link to the crash dumps:

https://www.dropbox.com/sh/2yq04buaa...f9u1eWHwa?dl=0



Below is the event viewer log when Reaper came out of the freeze and crashed. If there is any more information you need please don't hesitate to ask.

The program reaper.exe version 5.3.1.62 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 306c
Start Time: 01d26ef143103b0b
Termination Time: 27
Application Path: C:\Program Files\REAPER\reaper.exe
Report Id: 440bc900-dae5-11e6-8db9-001086800144
Faulting package full name:
Faulting package-relative application ID:

reaper.exe
5.3.1.62
306c
01d26ef143103b0b
27
C:\Program Files\REAPER\reaper.exe
440bc900-dae5-11e6-8db9-001086800144


55006E006B006E006F0077006E0000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 006E0055 006E006B 0077006F 0000006E
0010: 0000


In Bytes

0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00 ..
srdmusic is offline   Reply With Quote
Old 01-14-2017, 11:21 PM   #20
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

Quote:
Originally Posted by schwa View Post
Actually, I can reproduce the crash with the Slate virtual mix rack plugin (which I can confirm uses the run-time DLL that is reported in all of your crash logs above).

Unfortunately, this plugin won't run under the debugger because of anti-piracy components, so I can't be more specific about exactly why it's crashing.
If it wasn't already clear in my previous messages, I'm very grateful for you taking the time Schwa in tracking down the issue. Especially on your weekend evening.

I have a good relationship with Slate Digital and their support team. If there is any further info that I can provide them, I'll gladly forward it and report back. If it is better to be in contact directly with them I can provide you my Slate contact info via a direct message.
srdmusic is offline   Reply With Quote
Old 01-14-2017, 11:40 PM   #21
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

Quote:
Originally Posted by moliere View Post
They had some clicking and dropouts with VST3 a little while back in Reaper (which I'm pretty sure was fixed), but I never ended up going back to them. Might be worth me giving VST3 another go.

No, I haven't let them know, I'd love a contact to have a chat to about it, thanks. While my workaround allows me to do stuff, it's a bit annoying.
I'm not sure going to VST3 is a good idea if it is in fact causing the crashing I'm seeing.

I've come from Cubase land recently and switched to Reaper so I'm not entirely sure how the VST implementation carries over. I believe in the Steinberg formatting of VST3 they allow the plugins processing power to be shut off if not audio is being process within the plugin. This does not work well for reverbs as it monitors input audio instead of the output of the plugin. Thus a VST3 reverb would cut off the processing before the tail rang out. Most synth and reverb companies have stayed on VST2 for this reason.

It looks like in the buffer settings there is some options for shutting off processing on plugins that are not processing audio. This may be a work around to achieve the same VST3 advantage on the older VST2 format. If anyone else knows the answer to that one I'd much appreciate knowing. If it is the case I may want to just convert all the slate VST3's over to VST2 until they sort out any potential crashing issues.
srdmusic is offline   Reply With Quote
Old 01-15-2017, 01:59 AM   #22
MikComposer
Human being with feelings
 
MikComposer's Avatar
 
Join Date: May 2012
Location: Brighton
Posts: 1,989
Default

I had Zebra 2 vst3 crashes too, so i stopped trying to use it.
__________________
My Royalty Free Music library
MikComposer is offline   Reply With Quote
Old 01-15-2017, 07:10 AM   #23
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

Quote:
Originally Posted by srdmusic View Post
I loaded my template with all the fx off and was able to replicate the freezing problem with 'smooth seek' turned on.
Well, that's interesting. I'm not able to make it crash or freeze, except for once with the Slate plugin online, and I can't even reproduce that now. I can't make it freeze with all of the plugins offline, seeking around and saving the project, with smooth seek enabled.

If you can manage to get a real crash (not a freeze) with all of the plugins offlined, the only two pieces of information we can use from the crash dump are the faulting module and offset, so if that does happen and you can report those two things here that would be great.
schwa is offline   Reply With Quote
Old 01-15-2017, 07:25 AM   #24
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,750
Default

As a performance note, your project file is over 100 MB regardless of whether the FX are offlined, since the FX state is preserved in the RPP. If you are autosaving the project frequently, that is 100MB written to disk frequently in the middle of audio processing. You would likely see better performance if you can get some of the 700+ plugins out of the RPP some way or another, through a different work flow, using multiple project tabs, or subprojects.
schwa is offline   Reply With Quote
Old 01-15-2017, 05:56 PM   #25
Xenakios
Human being with feelings
 
Xenakios's Avatar
 
Join Date: Feb 2007
Location: Oulu, Finland
Posts: 8,062
Default

Quote:
Originally Posted by schwa View Post
Actually, I can reproduce the crash with the Slate virtual mix rack plugin (which I can confirm uses the run-time DLL that is reported in all of your crash logs above).

Unfortunately, this plugin won't run under the debugger because of anti-piracy components, so I can't be more specific about exactly why it's crashing.
So, Slate is probably using some protections even on top of iLok. :-/ I am able to run some other iLok protected plugins fine under the debugger. (OTOH those plugins themselves haven't crashed inside their own code, so maybe if that happens, the copy protection stuff becomes problematic...?)
__________________
I am no longer part of the REAPER community. Please don't contact me with any REAPER-related issues.

Last edited by Xenakios; 01-15-2017 at 06:10 PM.
Xenakios is offline   Reply With Quote
Old 01-16-2017, 06:08 PM   #26
FnA
Human being with feelings
 
FnA's Avatar
 
Join Date: Jun 2012
Posts: 2,173
Default

This is probably worthless, but I guess it won't hurt.

Reading this made me think of a crash/hang I had about a month ago. I clicked a preset in the Zebra HZ browser.

Zebra. Mouse click. Coincidence probably. This is only crash/hang I can find in event viewer and action center in the time frame. ZebraHZ was 2.6.1. vst2. There was lots of other plugins in the project but it wasn't struggling hard or anything. Tried to click the hell out of it today (REAPER 5.31x64) but could not reproduce. Pretty sure I have autosave shut off.

Code:
The program reaper.exe version 5.2.8.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: ad0
 Start Time: 01d25acf2f115b84
 Termination Time: 20
 Application Path: C:\Program Files\REAPER (x64)\reaper.exe
 Report Id: 253a3e7d-c705-11e6-8f9e-94de80a6a869
Code:
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:	C:\Program Files\REAPER (x64)\reaper.exe

Problem signature
Problem Event Name:	AppHangB1
Application Name:	reaper.exe
Application Version:	5.2.8.0
Application Timestamp:	581fe20a
Hang Signature:	609b
Hang Type:	1
OS Version:	6.1.7601.2.1.0.256.48
Locale ID:	1033
Additional Hang Signature 1:	609bff1e5f92deb6a25d9ba5f4a8ea09
Additional Hang Signature 2:	a754
Additional Hang Signature 3:	a754607a860787e71ed12b026ade69ee
Additional Hang Signature 4:	202d
Additional Hang Signature 5:	202d1731462570bf3438271a174380b7
Additional Hang Signature 6:	8f51
Additional Hang Signature 7:	8f511410c35dc9fa5d4cf5363ce5313a
FnA is offline   Reply With Quote
Old 01-17-2017, 10:20 AM   #27
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default

Quote:
Originally Posted by FnA View Post
This is probably worthless, but I guess it won't hurt.

Reading this made me think of a crash/hang I had about a month ago. I clicked a preset in the Zebra HZ browser.

Zebra. Mouse click. Coincidence probably. This is only crash/hang I can find in event viewer and action center in the time frame. ZebraHZ was 2.6.1. vst2.
[/code]
So you were having a problem with ZebraHZ VST2 not VST3?
srdmusic is offline   Reply With Quote
Old 01-17-2017, 10:25 AM   #28
MikComposer
Human being with feelings
 
MikComposer's Avatar
 
Join Date: May 2012
Location: Brighton
Posts: 1,989
Default

I'm having crash on startup because of RCompressor vst3. It doesn't crash on first start, but when i'm loading the project when have any other project opened.
__________________
My Royalty Free Music library
MikComposer is offline   Reply With Quote
Old 01-17-2017, 05:01 PM   #29
FnA
Human being with feelings
 
FnA's Avatar
 
Join Date: Jun 2012
Posts: 2,173
Default

Quote:
Originally Posted by srdmusic View Post
So you were having a problem with ZebraHZ VST2 not VST3?
Yes. Ordinarily it works fine. Once in a blue moon something weird like this happens.

Like I said, I don't expect it to be surely helpful. Slim chance maybe? I don't know what they see in all those numbers.
FnA is offline   Reply With Quote
Old 01-18-2017, 12:55 AM   #30
srdmusic
Human being with feelings
 
Join Date: Dec 2016
Posts: 876
Default Crash free for two days

I've been crash free for the past two days.

Here's what I've changed:

- Revered to version 1.0.2 of Valhalla Shimmer per Valhalla's suggestion.
- Changed over all U-he synths to VST2
- Changed over all Slate Digital Plugins to VST2
- Turned of Smooth seek in preferences.

I'm not sure if it was a combination of a buggy plugins and smooth seek having to re-buffer, or it was simply buggy plugins but so far so good.

Thank you everyone involved for helping to sort this out.
srdmusic is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 02:49 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.