Page 1 of 1

Vocodizer fixed device

Posted: Mon Jun 11, 2012 4:32 pm
by djmicron
Not used the vocodizer in the past, so i didn't know about the bug described here:

http://forums.planetz.com/viewtopic.php?f=1&t=29070


after some test, i have found a workaround described in the above link, then i have done some fix to the device using scope sdk and at least on my system it works.

I have done nothing of illegal and the device needs a valid key to work.

Re: Vocodizer fixed device

Posted: Mon Jun 11, 2012 5:47 pm
by dawman
DJM is back like a storm.
Thanks, I will try this and the Celmo Talk Box tonight.
I am thinking Solaris has everything else except a mic, so I shall give it a whirl.

CiaoMein.


Ankyu

Re: Vocodizer fixed device

Posted: Tue Jun 12, 2012 9:22 pm
by tomylee
this is great! how much do you get paid for doing SC´s work?

cheers
tomylee

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 4:49 am
by rhythmaster
Hi djmicron!

Very good job, thanks!!!!!

I have another task for you if you'd like to take a look at it:

http://forums.planetz.com/viewtopic.php?f=1&t=30156

SB404 issues ....

The behaviour exists for 1,5 years now - and no reply from S|C :(

Thank you so much
Harry

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 5:31 am
by djmicron
ok, i'll look into it :)

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 6:37 am
by jksuperstar
I wonder if the releases/updates John Bowen made for his synths might fix this issue. He made win x64 updates for scope to fix sequencer issues in his synths.

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 7:10 am
by djmicron
i have done a test inside sdk, all i can say is that it's not related to presets management, but it is more like the controls on the surface are not connected with the device, so i can't fix it.

The sb 404 version that comes from scope v4.5 works fine, so my workaround is:
  1. download the old sb404 version
  2. open the device inside scope v5.1
  3. copy the request string
  4. ask sonic-core support for a valid key
  5. use the v4.5 device

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 8:09 am
by jksuperstar
So it is possible to work in 5.1, is that on x64 or 32-bit windows? windows XP or win7?

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 11:50 am
by djmicron
i have scope v5.1 only on win7 64 bit, so if someone with the 32 bit version of scope v5.1 can confirm the sb404 bug, then using the sb404 version from scope v4.5 should be a workaround.
Else it's related to 64 bit os and need a fix as the solaris.

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 1:15 pm
by rhythmaster
I have win 7 32 bit scope 5.1 -> bug

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 1:35 pm
by Mr Arkadin
XP with bug. I think it's not directly related to SB404 as the sequencer modules in Modular are also broken.

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 1:41 pm
by djmicron
i asked SC for a new serial to run sb404 old version on 5.1, let's see...

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 9:33 pm
by rhythmaster
I also asked for a new serial!
I addressed this problem in July 2011 to S|C. They confirmed the misbehaviour in August 2011 with SB404 ...
And even if there are more problems als with Modular ... What treatment of error handling is this?

So hopefully in SCOPE 6 the errors are gone - but when will it be?????????????????

Re: Vocodizer fixed device

Posted: Wed Jun 27, 2012 10:20 pm
by garyb
err...

Re: Vocodizer fixed device

Posted: Fri Jun 29, 2012 3:46 am
by rhythmaster
September?

December 2012 - then we had two years since the last new version.

And if SB404 will be fixed then and hanging notes in XTC Mode Cubase 6.5 Win7 32 bit several synthies including Minimax - it would be great.

Re: Vocodizer fixed device

Posted: Fri Jun 29, 2012 10:39 am
by garyb
with only a couple of people coding it takes YEARS to make a new version.

win7 64bit took 2 1/2 years. this is not something that just anyone can do....

Re: Vocodizer fixed device

Posted: Fri Jun 29, 2012 4:17 pm
by dante
So my prediction of a NAMM 2013 release could be realistic - assuming they started late 2010 ealry 2011.. 8)