Answers For All your Questions About Xfer Records Serum :

(1) - Xfer Records Serum Will Crash If you have PC With 2GB RAM Or LOWER
(2) - Xfer Records Serum Will Crash if You try to open Serum.dll x64 version inside x86 DAW
(3) - Xfer Records Serum Will Crash If your Presets Folder is a Subfolder (folder inside folder)
(4) - Xfer Records Serum Will Not Work If your Presets Folder Is Not inside C:\Users\*******\Documents
(5) - Xfer Records Serum when you install an update go to Program files < Serum folder < Copy Serum.dll & Serum_x64.dll & Do Paste inside your VST folder & Replace the Old Serum.dll & Serum_x64.dll With the New Serum.dll & Serum_x64.dll cause if you don't do that you will not get the updated version of serum just the old version before the update
(6) - Xfer Records Serum If you don't have Serum presets folder just install the demo from Serum Website

NOTE : If you have any other question, don't hesitate to ask , if I know the answer, I will give you an answer.

EDIT Updated Info : This Beta Build (Xfer.Records.Serum.v1.06.beta5.Update) has a major issue when you click on the red button to close Serum, it make the DAW Crash.
This issue is only happened with v1.06b5
The previous update 1.05b9 work pretty well with no problem

 

Last edited by a moderator: Aug 2, 2015

What about say the case of x32 inside x64 DAW. Assuming it can be bridged fine & run ok.

Also when you say an x86 DAW which parts exactly do you mean or do you mean say x32 OS?

For example if u take say Bitwig even with with the X64 the GUI is hosted in a x32 bit process. However the plugins etc are hosted on a separate x64 bit process. Therefore theoretically shouldn't it be possible to run X64 .dll on a separate process even if other elements such as GUI hosted by a x32?

Possibly this would also apply to other DAW's?

Also I assume that when running x32 RAM is gonna be limited say with 256MB graphics to at most 3.5 GB so u gonna be pushing all the way with an x32 bit OS? Does changing the folder permissions or structure have any effect also on possible crashing issues?

Thanks for the info

 

x64 DAW Can Run 32bit Plugins
x86 DAW Means 32bit DAW Cause 32bit OS Can't Run 64bit Application

Presets folder Location By Default is C:\Users\*******\Documents
but yes you can place the Presets folder in any place you want
as along as The Presets folder isn't inside another folder (Means Subfolder) Cause it will crush serum Plugin

 

Last edited: Aug 2, 2015

I've grown to love this synth... especially since it's making me money!!!!!

 

Thanks, That's what I wanted to Clarify Mr Amine

For example if I have a X64 OS. I can then install say Reaper x86 (for whatever reason) and then install Serum or other X64 .dll & run it from within x86 Reaper as again Reaper will simply Bridge it as it would x32 in x64.

It just gives it a 64 Bit process & the Plugin works perfectly fine, no problems.

Therefore x32 OS will NOT run X64 .dll

However it is perfectly viable to run X64 .dll briged from within x86 Reaper on x64 OS if u so wish as it simply gets given a x64 process.

BTW not sure about the subfolders or whether that is something to do with a specific version or a DAW issue or something else making it crash.

For myself I have run x64 Serum.dll through x86 Reaper on X64 system no problems at all from a subfolder called Serum Presets, within a folder, within another folder on desktop.

For me personally it doesn't matter how many subfolders there are as long as you locate the folder serum presets upon opening the plugin

Think that could be maybe a DAW issue or something else completely.

Maybe other users might be able to verify this

 

I DID The test on FL Studio 12 & Cubase 8 Pro
i don't know about reaper cause i never test it. maybe i will in the near future when they release Reaper v5
by the way i use x64 AAX plugins only with Avid Pro Tools HD 11 in my studio
& when I get home I Use MY Home Laptop to test other version of plugins VST2 & VST3


I'm Talking about using x64 plugins inside x86 DAW without jBridge (I Mean Directly)

 

Last edited: Aug 2, 2015

No. It's in C:\Users\*******\Documents\Xfer.

But even if i'll put Serum presets in the "Documents" it will crash anyway.
Whatever you do, it's still crashing ableton, cubase pro, studio one. On the win7, win 8.1, win10 (all x64 ofc)

 

Try to put the presets folder in C:\Users\*******\Documents\ , without xfer folder just Serum Presets folder only.
put the folder like this C:\Users\*******\Documents\Serum Presets
and open your daw & Let me know if it works or not

 

Last edited: Aug 2, 2015

Already. Crashing.

 

can you tell details of your pc

OS
RAM
CPU

 

It's crashing on every pc with amd and intel cpu.

Current: Amd fx8350
32gb corsair vengeance blue revision
r9 280x (win 10 x64)

Also crashed on intel i74790k with same ram modules and gtx 980. (win 8.1 x64)

And on i5 with 8gb ram (goodram) and gtx 770. (win 7 x64)

It's just bad build. No matter what system you're using. You're closing plugin window and it's crashing daw.

 

I Didn't notice cause when i save a project in any daw i click on new project and it didn't crash since last month but Yes ,I Confirm it's A BAD Build & There's A Bug that make any daw crush if you click on red button to close Serum ; Since i don't use serum that much cause i use kontakt a lot anyway ,Tomorrow i will go to studio to test my legit copy and tell you if this is the developer's Build who's causing this problem or the update on AZ it may be altered somehow.

 

Last edited: Aug 2, 2015

Thank you for this thread Mr Anime, it's very educative

 

Couldn't tell you about that build MR Amine as not tested extensively

Will be interesting to see what happens with the official build and see whether it doing the same thing as opposed to say any modification to the plugin itself or a DAW or OS issue.

Nice one

 

So far mine is having no issues with a custom presets location, haven't given it a massive hammering yet but it doesn't seem to crash or give me any issues! Using Live 9 x64

 

try to exit serum by click on X mark on the right side above and see what will happend

 

Does Serum use a Registry key to point to the folder containing presets ?
- set to default as "C:\Users\..... "
Maybe it can be modified to point to wherever you want it to be ?

 

if you already have the presets folder just open Xfer Serum & when it will ask you about presets folder just locate The presets folder and serum will accept it

 

Win 8.1 64x with Reaper, S1, Maschine2
Update v1.06b5 works fine here (after rescanning Preset folder).

 

Serum (v106b5) was crashing and this worked for me.

After register Serum:
1. Copy %APPDATA%/xfer/Serum/user.dat to
Documents/Xfer/Serum Presets/System
2. Set this file to read only.

If you save any preset you need restore user.dat in %APPDATA%/xfer/Serum.