I usually get some new DEV's that come with empty presets. Lately Poltec, and RMX160.
No problemo, just save them, and give them a name right? Well this ain't working very well. Not only do I get a pop up, but it will halt the start up project until I say yes,......5 TIMES !! I have never seen this so does anyone have a fix, as even though I saved with the names of the devices, I still must load the saved, renamed one. This is a minor PITA, but since it happens upon start up, so eventually it must be resolved.
Thank You My Brotha's,
Empty Preset Pop Ups...They're Killing Me
I don't know those devices , but the procedure in such case is generally the following.
1. copy the suspect preset list somewhere else, you will need it in a minute, and you must not delete it.
2. load the device, open the preset list, in the "file" menu, press "new". any existing preset lis that was loaded is deleted. that's what we want.
3. in File menu again, load the preset list that you copied somewhere (point 1 )
4. In the file menu, press "SAVE AS" (not "save") and MAKE SURE you are saving it in the /Scope/Presets menu. . Do not change the name: when you press "save as" the name should be automatically selected.
5. delete the device from your project and reload it to see if it loads the list automatically (it should now).
The problem you have comes from one of the following cause (in general):
- a difference in the preset list name
- the preset list is not saved in the scope's preset directory.
- may be the preset flder is wrong in the scope settings or cset ini, but that's probably not the case if your other list load fine.
It should work now anyway (otherwise contact the device maker, only he can help if there is something wrong with preset list (but normally, the loading of lists is a function of scope, not something developpers can mess with easily, as far as i know).
general advice to anyone: scope remembers the location where you saved a preset list: if you do not always save in the preset directory, you expose yourself to loosing your presets easily by overwriting them unwillingly, or a very messy organisation in case you think it is better to save a list in your songs/project folder: in a month, you will have forgotten where that great preset is. by experience, i'd recommend to always save in the same preset list and in the scope's preset folder. Your preset list will grow and all your sounds will always be at your disposal each time you load that device.
make a backup every now and then to protect yourself from future disk problems, crashes etc...
1. copy the suspect preset list somewhere else, you will need it in a minute, and you must not delete it.
2. load the device, open the preset list, in the "file" menu, press "new". any existing preset lis that was loaded is deleted. that's what we want.
3. in File menu again, load the preset list that you copied somewhere (point 1 )
4. In the file menu, press "SAVE AS" (not "save") and MAKE SURE you are saving it in the /Scope/Presets menu. . Do not change the name: when you press "save as" the name should be automatically selected.
5. delete the device from your project and reload it to see if it loads the list automatically (it should now).
The problem you have comes from one of the following cause (in general):
- a difference in the preset list name
- the preset list is not saved in the scope's preset directory.
- may be the preset flder is wrong in the scope settings or cset ini, but that's probably not the case if your other list load fine.
It should work now anyway (otherwise contact the device maker, only he can help if there is something wrong with preset list (but normally, the loading of lists is a function of scope, not something developpers can mess with easily, as far as i know).
general advice to anyone: scope remembers the location where you saved a preset list: if you do not always save in the preset directory, you expose yourself to loosing your presets easily by overwriting them unwillingly, or a very messy organisation in case you think it is better to save a list in your songs/project folder: in a month, you will have forgotten where that great preset is. by experience, i'd recommend to always save in the same preset list and in the scope's preset folder. Your preset list will grow and all your sounds will always be at your disposal each time you load that device.
make a backup every now and then to protect yourself from future disk problems, crashes etc...
Ladies And Gentlemen,.......Mehdi.
I finally figured it out, and with your help of course. It was a little deeper than the both of us thought. It was digging into a file from the modular presets also. I eventually went to the SpaceF back-up preset list, Modulars preset, and the SFP preset as well and delete all empty preset.pres.
Many modular, and SDK devices are released with the empty pres. Some save well, others don't. Your advice helped me figure out the problems I have been having. It's no big deal, as I usually just load after start up. But I have become a perfectionist lately, and want a flawless DAW, even though these are all human errors from somewhere.
I finally figured it out, and with your help of course. It was a little deeper than the both of us thought. It was digging into a file from the modular presets also. I eventually went to the SpaceF back-up preset list, Modulars preset, and the SFP preset as well and delete all empty preset.pres.
Many modular, and SDK devices are released with the empty pres. Some save well, others don't. Your advice helped me figure out the problems I have been having. It's no big deal, as I usually just load after start up. But I have become a perfectionist lately, and want a flawless DAW, even though these are all human errors from somewhere.
If a preset list has the name "Empty Effect.pre", the device creator didn't give the preset list a name. If you have more than one device, where this did not happen, you of course will get into trouble because completely different devices want to load the very same preset list and/or overwrite the one from another device due to the same name. This can only be fixed by the device creator in the long run (giving the preset list a name that is).
hi jimmy,
ftp://cwaudio.de/Software/Scope_family/nokeys_OXE/
http://www.digitalaudiosoft.com/plugins ... audiosoft/
cheers
olive
here are the links for the good oxe (or zip) files with well labelled preset filesI usually get some new DEV's that come with empty presets. Lately Poltec, and RMX160.
ftp://cwaudio.de/Software/Scope_family/nokeys_OXE/
http://www.digitalaudiosoft.com/plugins ... audiosoft/
cheers
olive
Thank You My Brotha's,
I could fuck up a steel ball sometimes, I am so illiterate, but everytime I ask for help, I not only get the fix, but explanations that help me understand the way Scope software functions.
I am especially honored to have my 3 favorite developers respond.
Thank You Everyone, The pics were also helpful Brotha' Man Manu, I have the DAS DynaPara storing everything, but I managed to fuck the others up.
It's so nice when pop ups stop rearing their annoying heads.
I could fuck up a steel ball sometimes, I am so illiterate, but everytime I ask for help, I not only get the fix, but explanations that help me understand the way Scope software functions.
I am especially honored to have my 3 favorite developers respond.
Thank You Everyone, The pics were also helpful Brotha' Man Manu, I have the DAS DynaPara storing everything, but I managed to fuck the others up.
It's so nice when pop ups stop rearing their annoying heads.