Strange Solaris 4.1 error messages
I'm getting these error messages when loading some of the new banks patches in Solaris 4.1 (e.g. Donehr from bank 2). Usually dismissing the error boxes results in SFP crashing as well. Solaris was working fine up until the new build and banks and none of my other Scope synths give me problems - on the whole my setup is stable (still not upgraded to 4.5). I've sent this info to John Bowen too and he is looking into it but I thought maybe someone here might know what these error messages stand for? The first one is particularly weird as I have no software on my D drive - I use it exclusively for sample libraries - Scope is in the default c:/SFP folder.
D:Xsourcesrcsimscopebrd.cpp (1745): from != NULL
pepAddRouting: Pads sync sw EX. In2 and sync sw EX2 are incompatible cannot route
D:Xsourcesrcsimscopebrd.cpp (1745): from != NULL
pepAddRouting: Pads sync sw EX. In2 and sync sw EX2 are incompatible cannot route
I just upgraded to 4.0 and now have a whole new palette. Some presets sound different so I will tweak 'em back to normal. But now when I import samples into the WAV oscillators, they randomly change pitch. I tried to reset root key,etc. nothing seems to work right.But I just started getting into this so I don't have a lot of experience yet. I hope we can continue this thread though, for I will be in Solaris land for quite some time. It is my new star synth, for it has replaced so much. Also noticed my presets take more time to load, and use more DSP. I had Solaris loading very fast after doing the 0 voices save approach. I recently upgraded GS3, and Solaris. Kind of wished I didn't, for it was rocking solid. Now I struggle at the gig w/ load times, and such. This is not fun. Next time there is an upgrade for anything, I think I will pass. You just get going in the right direction, and bada-bing, bada-boom.
Damn spoke too soon - it's still crashing using presets from the 2 new banks but what I'm finding is that its not any particular preset and that's what made me think it was fixed at first - its hard to tell because every crash causes a system freeze and I have to restart but sometimes I can play the same patch and it works fine, other times it crashes. Crashes usually occur after I've changed patches a few times but definately not with any of the older patches so it must be connected somehow to the new functionality.
be sure that in your cset.ini file there are the search optiuons enabled.
You should check the " [ReferenceResolver] " line and this is how it looks on mine :
[ReferenceResolver]
MainSetting=
All files_AutoUse=1
All files_Paths=g:/scope45/;
i'm sure this works, because i've done tests with and without it.
I'm on scope 4.5 @ 44.1 sampling rate.
You should check the " [ReferenceResolver] " line and this is how it looks on mine :
[ReferenceResolver]
MainSetting=
All files_AutoUse=1
All files_Paths=g:/scope45/;
i'm sure this works, because i've done tests with and without it.
I'm on scope 4.5 @ 44.1 sampling rate.
Jimmy,On 2006-04-14 18:35, scope4live wrote:
I just upgraded to 4.0 and now have a whole new palette. Some presets sound different so I will tweak 'em back to normal. But now when I import samples into the WAV oscillators, they randomly change pitch. I tried to reset root key,etc. nothing seems to work right.
Could you please check if the Wav Oscs have the Fixed (tuning) switch on? If so, the root key will be ignored, and the sample will play back at the original sampled pitch (and will not track the keyboard). Also, make sure the first Frequency Mod path is NOT set to 'KeyTrk', as this disconnects the normal keyboard tracking and routes it through the modulation path.
Also, I'm not sure why your presets are not sounding the same as before, since I did not change the preset data....however, the signal path has been revised (as I stated in the v4.1 update notice), so if you used Overdive FX in your presets, you will have to make some adjustments...otherwise, things should be the same.
re: preset change times are longer - if you are talking v3 to v4, then yes, v4 added quite a few new parameters to the preset list structure, and these will tend to make things slightly longer to load in sometimes. (Of course, you can always go back to v3 anytime you need...).
regards,
John B.
Well 4.1 seems to have fixed everything that was bothering my rig. But I am pretty sure I installed it wrong. Some nights when I don't drive, I find it hard to pass up all the comps, so I was probably being a little too festive when I did this. BTW Solaris 4.1 loads faster now, i.e. like a preset synth almost. I thought maybe I left on the 0 voice approach, but they just load 3 x as fast as before. This is the vision I had when I bought into this platform. Funny, now GS3 Orchestra is a pain in my ass. Last year Giga 160 w/ Scope was solid. I aim to make GS3 / Scope the same. BTW, if Giga is working well for you, don't upgrade. It was the biggest musical mistake of my career, what was once stable is now so bad, I only use it as a sample playback device. All that VST shit was just to get people to buy into it again, and fix it as they go along.
I Came, I Saw, I Conquered, VINIVIDIVICI,
I Came, I Saw, I Conquered, VINIVIDIVICI,