Problems with"DSK instruments"...

alex-almotaz wrote on 9/10/2018, 6:40 AM

Hey everyone,

So, today, i decided to look for some free VSTs online and looking at my last post, i remembered johnebaker telling me about some instruments long ago that i should look at or at least try. (thankfully, they were free.)

I first downloaded two DSK instruments (DSK synthopia 2 and DSK ethereal padz 2). Then, i ended up with two rar files one for each instrument, respectively. By extracting the files, two files were extracted, again, one for each instrument and inside these files were one .DLL file and a standard “readme” file...that is it.

Now i did download and installed a VST before (drum pro) and i followed the same exact steps for how to install a VST. however, it says that a bunch of .sem files are missing or couldn’t be found.

It is worth noting that magix music maker reads the VSTs but for some reason couldn’t open them. Also, everytime this message pops up i have to force close magix music maker from the task manager because i couldn’t interact with any thing.

 

If you know the how to solve this problems, please let me know.

 

A list of things i tried:

 

- see if the missing files are hidden.

- create a separate file for these instruments.

- put the VSTs outside the VSTs plug-ins file in program files (x86).

- take the files out of there original file.

Here is a question, are the .sem files missing or cannot be read somehow? if missing, how could i get them?

Comments

johnebaker wrote on 9/10/2018, 9:42 AM

@alex-almotaz

Hi

All the required files should be in the download, however folder structure and placement in the VST folder is critical.

In my case I have a custom VST folder called VST, in this folder is placed the dll file, eg DSK Synthopia 2.dll, a sub folder also needs creating with the same name as the dll ie DSK Synthopia 2.

IIRC, once this is done the SEM files are generated and placed in this folder on first run, below is the contents for Synthopia 2.

HTH

John EB

 

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

browj2 wrote on 9/10/2018, 5:30 PM

@alex-almotaz @johnebaker

With Version 27.0.0.16, I get the same problem. The 2 (and there are more) DSK files only have a dll and a txt file. The same files on my desktop (not updated) with 25.1.3.84, no problem.

If you try DSK Saxophones from the Top Content menu, a choice of 32 bit or 64 bit comes up. I used the 32 bit and it somes with a subfolder with .mse files. This works on version 27... If you download the other one from under free content, SaxophoneZ, there are no other files, only the dll and txt. This one does not work on version 27, but works fine on 25.

Something has gone wrong with version 27, I think.

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

magicianman wrote on 9/10/2018, 9:47 PM

Hi. I installed and have tested about a half dozen DSK VSTs into 27.0.0.16 and did not notice any problems of any kind with any of them. Nothing unusual that has caught my attention. I only remember unzipping the various folders (32 bit) and placing them within my dedicated VST folder. If anyone wants to me to check anything for comparison I will be glad to do so. Regards, CEC

browj2 wrote on 9/10/2018, 11:55 PM

@magicianman

Hi,

Try downloading and using the 2 instruments that were mentioned above, the ones with only a dll file (txt file doesn't count) in the latest MM.

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

alex-almotaz wrote on 9/11/2018, 5:23 AM

Hi everyone. (sorry i took too long to respond, i was busy.)

 

So, i tried john’s instructions and they still didn’t work or like usual i’m missing something.

Here is some screenshots:

(Note: Don't worry, i tried removing the .zip files...still didn't work)

As for @browj2 suggestion, there was no 32-bit or 64-bit choice with both of these instruments.

I feel like i’m missing something or i’m doing it all wrong with the placements and selection. Here is what i do to install a VST and tell me if it’s wrong or not:

 

Press the “p” button after opening the MMM software.

Go to the “folders” tab.

Below, there are two buttons, “add VST plug-ins path” and “reset VST plug-ins information”.

Click the “add…” button.

A window will pop-up, then select the path to the file that contains the VSTs.

Press “okay”.

 

Things to note:

You can’t select the files made for the VST because they are empty...so it won’t be of any use. (and i tried it.)

The .dll files don’t appear in the path selection and they shouldn’t...technically.

At first, it seems like there is a problem with the program but @magicianman says it works just fine.

Is there a problem with the formating?

This problem started to frustrate me. So, please, let’s find a solution to this. (i’m also glad that you guys are actually digging into this...thanks for your attention.)

johnebaker wrote on 9/11/2018, 8:04 AM

@alex-almotaz

Hi

I suspect the problem is caused by the third party VST folder being located in the C:\Program Files folder and does not have the correct permissiions for the VST dll to generate the SEM files.

Mine are located in C:\ProgramData\MAGIX\Common\VST - VST being the new folder I created, which does have the correct permissions for the program to access.

I would suggest you move your VST's folder to the same location ie C:\ProgramData\MAGIX\Common.

As you can see below I have removed the SEM files from my installation and then on running the VST they are recreated

HTH

John EB

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

alex-almotaz wrote on 9/11/2018, 9:07 AM

@alex-almotaz

Hi

I suspect the problem is caused by the third party VST folder being located in the C:\Program Files folder and does not have the correct permissiions for the VST dll to generate the SEM files.

Mine are located in C:\ProgramData\MAGIX\Common\VST - VST being the new folder I created, which does have the correct permissions for the program to access.

I would suggest you move your VST's folder to the same location ie C:\ProgramData\MAGIX\Common.

As you can see below I have removed the SEM files from my installation and then on running the VST they are recreated

HTH

John EB

Oh my god. After some struggle, i did it and it finally works (doesn't display the pictures for the insturments, but it works.). It turned out that my "ProgramData" file was hidden and i had to go to the control panal to fix this.

thanks, johne. i was really frustrated.

shgrude wrote on 9/11/2018, 9:43 AM

In Windows10 You can simply click the Windows Start button and type %ProgramData% followed by <enter> and it will open file explorer inside the C:\ProgramData directory. It will even open correctly if the directory has been relocated to another disk drive (not recommended by Microsoft). This will work with any language used on the OS (ie non-english language)

This works in Windows 7 too, and you do not need to make the ProgramData visible prior to this. It just works

Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Operating system: Microsoft Windows 10 Home (64-bits) OS 18363.475 (1909)
Memory: 16GB
Sound Card: NVIDIA High Definition Audio
Realtek High Definition Audio
NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
Graphics Card: NVIDIA GeForce GTX 1060 1920x1080

browj2 wrote on 9/11/2018, 10:23 AM

@johnebaker

I did as you suggested, moved the dll files to ProgramData/vstplugin (I created the folder) and the sem files were created. I then copied the folder with the sem files back to the C:\Program Files (x86)\Vstplugins\DSK and that worked.

I wonder if opening MM as Admin would have solved the problem. I'll give it a try.

In the meantime, I see that there is a patch and I'm downloading it.

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

browj2 wrote on 9/11/2018, 10:53 AM

I tried opening MMM in Admin mode, closed it, updated to new patch, started MMM normally, and added in one of the other instruments that had only a dll, to the normal path:

C:\Program Files (x86)\Vstplugins\DSK\DSK Ethereal PadZ 2

This worked and the sem files and folder were created. I recalled that this was a problem in Samplitude.

Perhaps someone else could test this to see if the solution is running once in Admin mode.

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

johnebaker wrote on 9/11/2018, 11:06 AM

@alex-almotaz

Hi

Good to know that it got fixed.

. . . . doesn't display the pictures for the instruments, but it works. . . . .

It won't, there are no pictures with the VST to use - however I created 2 and dropped them into the same folder as the dll's.

You can download the images from these 2 links : Synthopia 2 EtherealPadz

Check that the file names match that of the dll's and drop them in the folder as above.

HTH

John EB.

 

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

johnebaker wrote on 9/11/2018, 11:12 AM

@browj2

Hi John

I would not advise, and it is not recommended, putting anything other than 'installed' programs in the the Program Files (x86) or Program Files folders .

Permissions issues arise and it is too easy to mess up the program installations by changing or adding permissions.

The ProgramData\Program installed folder however has all the correct permissions, for System, Software and User, set when the program is installed.

HTH

John EB

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

browj2 wrote on 9/11/2018, 11:39 AM

@johnebaker

Hi John,

The folders created by Magix for plugins are:

C:\Program Files\VSTPlugins

C:\Program Files (x86)\Vstplugins

These folders are scanned, usually automatically, by Magix programs, like MEP, VPX, AML, MMM and Samplitude. Samplitude users do as I do, create subfolders for various VST and VSTi plugins. It was my understanding that these are the correct locations to put these files. ProgramData is normally a hidden folder which is why it is not normally used. Of course, I have others that have gone to their own folders during installation under program files, like Steinberg, but most are simply like the DSK files.

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

johnebaker wrote on 9/11/2018, 1:31 PM

@browj2

Hi John

. . . . The folders created by Magix for plugins are:

C:\Program Files\VSTPlugins

C:\Program Files (x86)\Vstplugins . . . .

Agreed, however I would qualify that to say the folders created by Magix for Magix installed plugins.

Many third party VST's do not have an installer to set up the correct permissions. In practice they should inherit the containing folders permissions when they are copied into the folder, however, from experience, this is not always guaranteed.

Other VST's which have an installer either ask for an installation path or install into there own or the Steinberg folder and set up the correct permissions for access, the best ones being those that are aware of the program they are going to be used with.

. . . . It was my understanding that these are the correct locations to put these files. . . .

IMHO there is no specific place to VST's must be placed in, if there was, then the Add VST file path option would be unnecessary.

In my experience, the advantage of using the ProgramData folder, or any other folder that is not located in the program installation folders, is that they do not get cleared when a major update occurs.

John EB

 

 

Last changed by johnebaker on 9/11/2018, 1:32 PM, changed a total of 1 times.

Lateral thinking can get things done!

VPX, MEP Premium, MEP 2016, and earlier versions, Music Maker Premium, Music Maker 2016, 2015.

Running Windows 10 64bit on Intel i7-8700K 3.2 GHz, 16Gb RAM, 1Tb + 2 x 2Tb internal HDD + 60Gb internal SSD, + 6 x 2Tb ext HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.