Page 1 of 2
					
				the Sdk v4.5 is not Working with Scope 5
				Posted: Sun May 31, 2009 7:36 am
				by fmpsycho
				installation the Driver a Hardware version conflict 
so not working .....
			 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Sun May 31, 2009 8:03 am
				by erminardi
				
			 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Sun May 31, 2009 8:51 am
				by fmpsycho
				Fixble:   go to device manager and change the driver when using Sdk 
but still no v5 Sdk 
hope there will be soon  

 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Sun May 31, 2009 9:00 am
				by Shroomz~>
				We're back to 4.5 here for now. Switching between the drivers regularly isn't something I want to do.
			 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Sun May 31, 2009 7:14 pm
				by eric
				Even though I don't have SDK yet (it's lost in postal system somewhere between Germany and Australia  

 ), I am ready and have two platforms on same computer.
I cloned the C drive to another disk and then cloned it again to the same disk in a different location. I tweaked the Partition Record (sector 0) to boot from the second clone and installed Scope5. Now I can just tweak the Partition Record to switch between clones 4.5 or 5. In each case the other clone is visible as a "data" drive so I can copy stuff between clones. This works very well. No messing with drivers and registry entries. Complete fallback position.  
 
 
Ralf said SDk for 5 isn't public or available yet.
Eric.
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Mon Jun 01, 2009 3:43 am
				by Shroomz~>
				eric wrote:Even though I don't have SDK yet (it's lost in postal system somewhere between Germany and Australia  

 ), I am ready and have two platforms on same computer.
I cloned the C drive to another disk and then cloned it again to the same disk in a different location. I tweaked the Partition Record (sector 0) to boot from the second clone and installed Scope5. Now I can just tweak the Partition Record to switch between clones 4.5 or 5. In each case the other clone is visible as a "data" drive so I can copy stuff between clones. This works very well. No messing with drivers and registry entries. Complete fallback position.  
 
  
Tweaking the Partition Record to switch between clones is practically as messy as switching drivers constantly. When you're working with sdk, there's times when you need to shut down sdk, load Scope to test something, shut down Scope & start sdk again. You'll experience times when you need to do that several times within 5-10 mins, so it needs to be a streamlined transition.
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Mon Jun 01, 2009 4:11 am
				by erminardi
				Hei, take it easy... now Scope 5.0 final version, then SDK and synths (& ASB) bug fix 

Sonic|Core is a little (big) brand, leave them work!
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Mon Jun 01, 2009 4:29 am
				by Shroomz~>
				I think you picked the wrong thread for a 'give 'em a break' post because nobody here is complaining.
			 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Mon Jun 01, 2009 5:17 am
				by erminardi
				Shroomz~> wrote:I think you picked the wrong thread for a 'give 'em a break' post because nobody here is complaining.
Yes, You're right Shroomz  
 
 
I've solved this problem with using 2 separate computers. 
Actually I think that the benefit of new devices from Scope 5.0 not worth tha lacks of SDK, XTC and some big known and announced issues.
Too much compromises, for now, for a good professional use IMO.
I prefer to wait a final relase or use a secondary DAW for 5.0 testing.
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Tue Jun 02, 2009 9:13 am
				by MCCY
				Me too 

 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Tue Jun 02, 2009 11:53 am
				by fmpsycho
				
  i have to agree with shroom it's a hastle but it pays to progress to v5
        with my experience Xcite won't get you to the Sdk and my thing is really 
        to develope the synths so i won't give that up 
        by switching drivers i can also use the Sdk 
       ( btw v5 Sdk is really a mith ) 
        so in this hard times this is a choise cause no Sdk5
        
        we are the developers !!
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Tue Jun 02, 2009 12:31 pm
				by Shroomz~>
				erminardi wrote:Shroomz~> wrote:I've solved this problem with using 2 separate computers. 
 
That's the best solution at the moment & it's a good solution for Scope sdk users in any case. 2 computers networked - one running sdk & one running Scope.  

 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Tue Jun 02, 2009 12:35 pm
				by Shroomz~>
				fmpsycho wrote:( btw v5 Sdk is really a mith) 
What makes you think that?
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Wed Jun 03, 2009 1:36 am
				by fmpsycho
				they say it exist . .  but no one has seen it working fully 
hehe     
 
 
i want to say sorry to shroom cause v5 and v4 together causes conflicys in asio 
So I am Sfp 4.5 
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Wed Jun 03, 2009 4:19 am
				by katano
				fmpsycho wrote:
       ( btw v5 Sdk is really a mith ) 
i don't think it's a myth, because i've got a sdk 5.0 key in my new keyfile  

 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Wed Jun 03, 2009 4:24 am
				by netguyjoel
				I'm confident there will be SDK for 5.0
			 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Wed Jun 03, 2009 11:23 am
				by kylie
				but it's not likely to arrive "soon"...
			 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Thu Jun 04, 2009 12:01 am
				by eric
				Shroomz~> wrote:erminardi wrote:Shroomz~> wrote:I've solved this problem with using 2 separate computers. 
 
That's the best solution at the moment & it's a good solution for Scope sdk users in any case. 2 computers networked - one running sdk & one running Scope.  

 
"2 computers networked - one running sdk & one running Scope."
Doesn't that mean 2 Scope or similar cards, one in each computer?
I am effectively running 2 computers. Two separate operating systems - same hardware. All I have to do is reboot to switch between XP with 4.5 and XP with 5.0 installed. I could create a 3rd clone for SDK. That would be like running 3 computers. Each partition I boot from can see the other partition(s) as other drive letters so I can point the Scope settings/folders to any drive which contains my projects etc. or copy/move files around. Same end - different solution. Rebooting is no big deal. 
 
 
I don't expect to be trying anything I create with the SDK on 5.0 yet so I will develop and learn in 4.5 only. I'm a total beginner, in fact I'm not even a beginner yet!  
Eric.
 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Fri Jun 05, 2009 4:43 am
				by kylie
				eric wrote:I don't expect to be trying anything I create with the SDK on 5.0 yet so I will develop and learn in 4.5 only. I'm a total beginner, in fact I'm not even a beginner yet!
after finishing wayne's tutorial you still feel like a beginner, but at least you should have a first impression of what's it all about... 

 
			
					
				Re: the Sdk v4.5 is not Working with Scope 5
				Posted: Fri Jun 05, 2009 10:32 pm
				by hifiboom
				an sdk will come for sure....
thats the base for 3rd parties....
even Klaus Piehl @Messe 2008 told me that they wanna bring an updated sdk in the future.
other sources confirm this statement. 
 
 
But its a small team, now they have managed to bring out xite-1 and scope v5, i guess next will be Solaris HW and SDK5.
I guess they already have an updated internal sdk or do you think SC do switching drivers in their house....?
i see no point why they should not release an sdk. Thats the base of the platform and makes it open and alive and attracts new 3rd party-devs for future commercial devices. And the past has shown very awesome free devices also.