Synthmaster One?

[Amram]

Try running Synthmaster One in standalone mode and see if it loads the skin that way, at least you can rule out it being a Reason-induced issue vs. a Synthmaster one. BTW, I would NOT set anything as a preset skin in the Settings tab, I got a crash that way, not with my skins, but the other day, and I don't trust that, it seems there is a bug there. I always just change the global skin via right click on the plugin.

Also try enabling and re-scanning Synthmaster in Reason (however you do that), see if that resolves it. I downloaded and tested the satYatunesWood.rar archive and it is fine here. I'm going to bed but will check back with you in the morning.

i am thinking i just put satYatunes the the one that comes with sm1 instllation to deafult when i close sm1.

[kv331]

I have problem here with the wood skin and reason 10 , after i screenshot the plugin in reason 10 and sm1 save this skin for deafult , i close reason and open again than sm1 and i get this message:
https://imgur.com/a/AZdCt

I have no insight into Reason issues, so I'm sorry, I can't help with that.

Try deleting the config file documents/synthmasterone/synthmasteroneconfig.txt

to reset the skin.

If that doesnt help, try deleting the skin folder from Resources/Skins/ subfolder

[Amram]

I have problem here with the wood skin and reason 10 , after i screenshot the plugin in reason 10 and sm1 save this skin for deafult , i close reason and open again than sm1 and i get this message:
https://imgur.com/a/AZdCt

I have no insight into Reason issues, so I'm sorry, I can't help with that.

Try deleting the config file documents/synthmasterone/synthmasteroneconfig.txt

to reset the skin.

If that doesnt help, try deleting the skin folder from Resources/Skins/ subfolder

I installed again and deleted the config file from the instllation but it dodnt help , its seems this problem just in reason 10 because in studio on 3.5 its working well.
Ill try to move the new skins folders.
Thx kv311 and braj for the great skins.

[kv331]

You can always send me the crash report (for OSX at least)

[braj]

I had SMO crashing Reaper repeatedly this morning, every time I tried to load the plugin. I had put my computer to sleep without shutting down Reaper, I have no idea if that had anything to do with it, but I deleted the SMO Config file as suggested and that fixed it for me, I checked the skins and they work fine. But it does make me wonder if there is some bug related to skinning. I'm only changing a few image files, keeping the dimensions the same, and changing the name of the skins in the xml file.

[braj]

Actually, I just tracked it down, the dark skin with new knobs causes SMO to crash, so I deleted the link. If anyone has any skin that causes SMO to crash after using, delete the skin file, then delete the config file and relaunch.

Are there detailed requirements available for skinning? Obviously the skin works, but if SMO gets launched with the skin or closed with the skin enabled, it crashes.

[braj]

There is definitely a bug somewhere in SMO regarding skins. I was now just getting Reaper crashing no matter what when I launch. It should have some error handling in case it can't launch a skin, and load the default skin if some issue with the preferred skin is encountered.

If you run into this issue, this is what resolved it for me:

1. Close your host, make sure it isn't running as a background process.
2. Delete the config file from Documents\Synthmaster One\Config
3. Move all custom skins out of the Skins directory.
4. Launch SMO in your host, it should give you the message 'do you want to automatically check for updates' which confirms basically that the config is being initialized.
5. Move your skin folder you wish to use back into the Skins directory.
6. Remove the plugin completely from your host track, and reload.
7. You should now be able to safely change skins.

I don't know if this is some issue with my skins particularly, or a general bug in SMO that gets triggered when changing skins, but hopefully the steps above work for anyone having issues. And again, I would say this is a more global issue with error handling when a skin can't be loaded for whatever reason, especially as skins are allowed to be uploaded directly in the app soon by any user, it could make the plugin very unstable.

[kv331]

Actually, I just tracked it down, the dark skin with new knobs causes SMO to crash, so I deleted the link. If anyone has any skin that causes SMO to crash after using, delete the skin file, then delete the config file and relaunch.

Are there detailed requirements available for skinning? Obviously the skin works, but if SMO gets launched with the skin or closed with the skin enabled, it crashes.

If you could email me the skin, I can test it and figure out what's crashing.

[braj]

Actually, I just tracked it down, the dark skin with new knobs causes SMO to crash, so I deleted the link. If anyone has any skin that causes SMO to crash after using, delete the skin file, then delete the config file and relaunch.

Are there detailed requirements available for skinning? Obviously the skin works, but if SMO gets launched with the skin or closed with the skin enabled, it crashes.

If you could email me the skin, I can test it and figure out what's crashing.

I sent the link to you in PM a little while ago

[VELLTONE MUSIC]

want to ask something - can something like this be implemented in sm3 :

[Amram]

want to ask something - can something like this be implemented in sm3 :

Fantastic

[Amram]

for the skins:
if i sweatching to original satYatune after i finishing using sm1 with wood skin there is no problem.
its seems the problem is to make wood skin default.

[braj]

for the skins:
if i sweatching to original satYatune after i finishing using sm1 with wood skin there is no problem.
its seems the problem is to make wood skin default.

Are you talking about the wood or the Divine one? Try Divine if you want wood, I have no issues with it.

[Amram]

for the skins:
if i sweatching to original satYatune after i finishing using sm1 with wood skin there is no problem.
its seems the problem is to make wood skin default.

Are you talking about the wood or the Divine one? Try Divine if you want wood, I have no issues with it.

i prefer the wood , but in reason 10 i have problem to keep this skin after i close sm1 .
because if i close reason 10 than open it and than open sm1 i get error message , like i upload here , so i am switching it back to factory skin untill bulent fix it.
edit:
the dark skin looks like gorlla skin.
edit:
u are right wih the devine skin there is no problem at all .

[zzz00m]

want to ask something - can something like this be implemented in sm3 :

I would really like to see something like that at the oscillator level. Drag in a sample, and then experiment with which part of it plays back. Something different from wavetables, but with potentially just as much creativity.

Not actually suggesting full blown sampler features, but it would be nice to just be able to limit the sample playback in a non-destructive way to certain time based ranges of the sample, like in this video.