The SFP bug list.

at0m · Post by **at0m** » Fri May 10, 2002 6:14 am

For Voices problem:

Does assigning # voices to preset, then selecting preset, bypass the problem? Instead of directly changing # voices on the device?

sandrob · Post by **sandrob** » Fri May 10, 2002 6:18 am

my bug list with images and tarzan's english

_________________
"got my mojo working, but it just won't work on you"

[ This Message was edited by: sandrob on 2002-05-10 07:19 ]

darolek · Post by **darolek** » Fri May 10, 2002 7:05 am

Bug or not bug ?

?
-
In STS-2000P I can set 16 voices max.
(under 3.01 I can set 64 voices)
-
On CW forum Ingo answer to me:
"A fixed bug (64 voices were displayed, but 16 stereo (!!)
voices were always the maximum). For more voices, load another STS 2000P
Ingo,
CreamWare"
What do you think about ?

caleb · Post by **caleb** » Fri May 10, 2002 7:11 am

I think Ingo was right there.

It was only 32 voices (16 stereo) for STS2000P wasn't it?

Wow! I've never really thought about it that way, but technically speaking a mono left and a mono right is 2 voices not one. Sometimes the most obvious things just don't pop into your head - happens with me a lot.

darolek · Post by **darolek** » Fri May 10, 2002 7:44 am

Hey Caleb !
It's obvious for you ??? Look at the SFP manual:
-----------
Foreword
The STS 2000 is a 16-part multitimbral
sample player capable of generating up
to 64 voices. Its voicing structure features
two-pole low-pass filters. Otherwise, its
playback architecture is the same as that
of the other members of the STS family.
p.s.
In fact - STS family was many problems in ver. 3.01b under XP. But STS-2000P (either 3.01b) under 98SE gets up to 64 voices, eats DSP power and plays

Strange ...

[ This Message was edited by: darolek on 2002-05-10 08:49 ]

AudioIrony · Post by **AudioIrony** » Fri May 10, 2002 11:57 pm

1. Scope Fusion Platform BG application crashes with Error 12 on Mac
http://www.planetz.com/forums/viewtopic ... &forum=1&5

2. Using a Midi Merger module in your project causes Auto Routing to not connect properly - ie to the Midi Merger (there is only the option to connect to the Midi source or the sequencer source.)

caleb · Post by **caleb** » Sat May 11, 2002 2:52 am

"Hey Caleb !
It's obvious for you ??? Look at the SFP manual"

That's not what I was talking about when I said "obvious", I was referring to left mono and right mono being two voices instead of one. I'd never thought of it like that before.

Unfortunately as can be seen in another thread, I'm hopeless at reading manuals. Maybe I was deducing out of thin air. It's quite possible with me you know.

I always think I've read something - somewhere, only to realise that for some reason my mind just invented a new fact.

Happens all the time.

samplaire · Post by **samplaire** » Sat May 11, 2002 3:28 am

On 2002-05-11 00:57, blgrace wrote:
1. Scope Fusion Platform BG application crashes with Error 12 on Mac
http://www.planetz.com/forums/viewtopic ... &forum=1&5

2. Using a Midi Merger module in your project causes Auto Routing to not connect properly - ie to the Midi Merger (there is only the option to connect to the Midi source or the sequencer source.)

in addition to the above:
1. It happens in MacOS 9.2.2. in 9.1 the BG project doesn't launch with any explanation (clicking on it exectutes nothing)

new observations:
SFP 3.1 + MacOS 9.2.2 + Cubase 4.1r2 - 'active sensing' (i.e. if there is any external midi controller connected to Pulsar/Luna Midi in) crashes cubase with #1 error (hope this one doesn't take place with Cub 5.x but I don't know). The situation doesn't occur in 9.1 so SFP 3.1 + MacOS 9.1 + Cubase 4.1r2 - > OK

topaz · Post by **topaz** » Sat May 11, 2002 4:31 am

spdif in wont work at 44.1k
every samplerate but, as soon as I change to 44.1 the signal vanishes.

fine in all version prior to 3.1 and I still have 3.01 installed and it,s working.

On 2002-05-08 14:15, remixme wrote:
Ok right now I don't want to spoil everyones fun, but no one expects a release to be bug free, although I think creamware have done a GOOD JOB on scope. If we compile a list of common confirmed bugs creamware can fix it quicker.
Also people thinking about moving to sfp can look and make an informed decision

So if you have any problems, post here keeping this format.

First List the problem:

System setup (cpu/chipset/os/cards):

State whether this has been confirmed by a different user/or different setup:

darolek · Post by **darolek** » Sat May 11, 2002 8:09 am

On 2002-05-11 05:31, topaz wrote:
spdif in wont work at 44.1k
every samplerate but, as soon as I change to 44.1 the signal vanishes.

No, no, no !
It's work. You must to have some individual problems with your gear setup. If you don't belive then do once test yet:
Connect (physical) Pulsar SPDIF-coax OUT to Pulsar SPDIF-coax IN
Rest instructions and connections on the picture below - it's work because must works

darolek · Post by **darolek** » Sat May 11, 2002 8:17 am

Problem:
1632 Mixer don't work at samleprate 96 kHz.
My setup:
TUSL2-C/PIII-1GHz/WinXP Pro
Matrox G-450/Pulsar 2
SFP 3.1 (upgrade in separate folder)
-
Problem has noticed by some users from CW forum.

bassdude · Post by **bassdude** » Sat May 11, 2002 3:47 pm

On 2002-05-09 12:35, remixme wrote:
Ok guys try this in the new standard mixer stm1632 go to the aux page, unclick the button that says 'Int.' And in the routing box in one of the aux send channels on that page right click and try to route something. Like me you should an exception.

Just wanted to confirm this one as I get it too. But it works fine if you make connections in the router window.

sandrob · Post by **sandrob** » Sat May 11, 2002 8:31 pm

On 2002-05-08 21:51, EarlyFirst wrote:
LiveBar is only ontop if the _ontop_ button is pressed

livebar is always ontop anyway in sfp environment and i think is normal because livebar is "master window".
if is the "ontop" pressed that's livebar is ontop other programs. and i think is normal too and very nice specialy in standard mode when is livebar ontop cubase

Post by **garyb** » Sat May 11, 2002 9:51 pm

sp/dif works at 44.1

valis · Post by **valis** » Sun May 12, 2002 3:16 am

My most annoying bug:

Can't find DSP file Multi VU-Meter 6 - Please check installation
When i load STM 2448 under SFP 3.1

[ This Message was edited by: valis on 2002-05-12 04:16 ]

Grok · Post by **Grok** » Sun May 12, 2002 8:46 am

And what about RECORDING?

My first constatations are:

1) recording audio with ASIO drivers works perfectly, even at 32 bit 48 kHz

2) recording at 24 bit 48 kHz and above with the WDM wave is impossible: it's a war between crackles and music. It could be a major bug, making professional work with Scope Fusion and Cakewalk or Samplitude or Acid or Vegas or Sound Forge and others impossible since you can only record without problems at 16 bit and not above

3) XTC mode fails. In Xtc mode, native plugins works well but Creamware's plugins can't make music. Crackles, and so on.

BIT01 · Post by **BIT01** » Mon May 13, 2002 2:02 am

On my 98SE setup SFP keep on crashing each time i manually enter number of asio channel anybody else find this ?

gedas · Post by **gedas** » Mon May 13, 2002 9:31 am

These are little bugs I've found so far while mixing a track in a newly made sfp project:
STW Reverb won't work. At least not in the aux rack, simply no signal.
Aux sends from STM2448 running into aux rack - after reopening project stereo connection is lost (connections shown in the live bar are intact, just the right-side wires are missing), but maybe it's just graphical bug, had no time to check that, simply reconnected.
Eq curves on certain channels are displayed incorrectly. Try setting Q to, say 10, and change the channel view to another channel, then go back to the previous one - the curve looks like the Q is somewhere like 1, but the numerical display is correct as well as the sonic impact of the eq. So far so good. A fully loaded Project (8 DSP), win98lite.

dbmac · Post by **dbmac** » Mon May 13, 2002 10:00 am

I've got the STW Reverb (4080L) working fine in SFP, but as externally routed device (STM16/32 aux send - STW4080 - STM IN 1&2). The Timeworks device graphic is sometimes screwed up, but removing and re-placing in the project usually fixes that.

I've seen a lot of devices not working properly with SFP. Mostly older third party stuff, like Grenfreq. Synchrotron doesn't work at all - loads fine but the presets and knobs are unresponsive. The Sfera device from Orbitone's PsyFi - loads but presets won't open. SpaceF's (free) txt mdls will load but not open.
Zarg's Dark Star loads with no connectors (audio or midi) and no presets. Loading the Ambient causes many notices to pop up with arcane messages about routing exceptions (and the old lost communications with board0).

I wonder if a lot of older plugins will have to be updated (rewritten?) to work in SFP3.1 or if a CW patch will fix things.
/dave

[ This Message was edited by: dbmac on 2002-05-13 11:31 ]

King of Snake · Post by **King of Snake** » Wed May 15, 2002 6:57 am

Hmmm, seems there's still a fair amount of big bugs in there. I just dl'd SFP but Im now still unsure if I should install it o just wait for another bugfix...

Ah well, I don't think I can resist the urge anyway...