Regarding Obsidian toolbox not working.
In newer versions of creamware software panels are designated either "circuit" or "surface", the panels from older versions of scope are designated as circuit. I believe that Obsidian used some of the original panels that came with the various atoms, and that is why they will no longer show.
The SFP bug list.
Ok, now we´ve collected some bugs around SFP...
First of all, my S/PDif input doesn´t work anymore, same problem on 3.1 AND 3.1a, same problem on Chris´ machine next to mine, although the setups are completely different from each other. Only the OS is the same, Win98SE on both of them.
(edit: it doesn´t work as loop in 44.1, but it does at 48k, or even at 44.1 as one-way connection)
mine: Intel Celeron 1200 on Asus TUSL2-c, Ati Radeon 8500, Powerpulsar+Pulsar2
Chris´: Athlon 1800XP on Abit KG7raid333, GForce4 Ti4200, Pulsar1+SRB1
Then I have invisible cables in my project when I connect one AUX out to ADAT-A dest twice... then save and reload the project. The cables are there and functional, I just don´t see them anymore.
Chris found a problem that the preset lists don´t keep what was selected last; whenever windows are switched forth and back again, the highlit preset will be the first of the list, not the one that is active. Old-style lists work fine though...
I got another problem about downwards compatibility to useful but no longer delivered devices like the stereo Aux-rack. They will load, but working with them like I did with 2.xx will cause errors when I want to save the project. Trying to save the presets of the FX used in it will crash SFP...
Next, the directsound source doesn´t work as it should. Many games or other Direct-X related programs stutter, don´t give sound at all or even crash the whole system. Examples: Shiny Entertainment´s "Sacrifice", Mad Onion´s "3D-Mark2000", Fishtank´s "Aquanox", and some more...
btw, I DO KNOW about the hardware-accelleration set to "None".
Why the &*#^$!@ can´t CW just deliver a working and correctly implemented DX-sound driver? If everyone can, why not CW?
Next: bidirectional ADAT connection works fine for my old A16, but not for connecting two computers. Tried with even a third PC with SFP, nothing worked really fine, not when working in more than one direction, and sometimes even unidirectional link wouldn´t do fine. (I also DO KNOW about correct master/slave settings and so on, as they SHOULD work.)
What´s so different if I connect an A16 via ADAT, or another PC? One works, the other doesn´t... *grumblmumblgrrrRRRrrr*
All bugs confirmed as we´re three people here using three CW-based DAW´s in the same room.
We´ll go on bug-collecting over here and keep you guys posted.
JoeKa, ChrisWerner and FreiFlug
<font size=-1>[ This Message was edited by: JoeKa on 2002-08-08 16:33 ]</font>
First of all, my S/PDif input doesn´t work anymore, same problem on 3.1 AND 3.1a, same problem on Chris´ machine next to mine, although the setups are completely different from each other. Only the OS is the same, Win98SE on both of them.
(edit: it doesn´t work as loop in 44.1, but it does at 48k, or even at 44.1 as one-way connection)
mine: Intel Celeron 1200 on Asus TUSL2-c, Ati Radeon 8500, Powerpulsar+Pulsar2
Chris´: Athlon 1800XP on Abit KG7raid333, GForce4 Ti4200, Pulsar1+SRB1
Then I have invisible cables in my project when I connect one AUX out to ADAT-A dest twice... then save and reload the project. The cables are there and functional, I just don´t see them anymore.
Chris found a problem that the preset lists don´t keep what was selected last; whenever windows are switched forth and back again, the highlit preset will be the first of the list, not the one that is active. Old-style lists work fine though...
I got another problem about downwards compatibility to useful but no longer delivered devices like the stereo Aux-rack. They will load, but working with them like I did with 2.xx will cause errors when I want to save the project. Trying to save the presets of the FX used in it will crash SFP...
Next, the directsound source doesn´t work as it should. Many games or other Direct-X related programs stutter, don´t give sound at all or even crash the whole system. Examples: Shiny Entertainment´s "Sacrifice", Mad Onion´s "3D-Mark2000", Fishtank´s "Aquanox", and some more...
btw, I DO KNOW about the hardware-accelleration set to "None".
Why the &*#^$!@ can´t CW just deliver a working and correctly implemented DX-sound driver? If everyone can, why not CW?
Next: bidirectional ADAT connection works fine for my old A16, but not for connecting two computers. Tried with even a third PC with SFP, nothing worked really fine, not when working in more than one direction, and sometimes even unidirectional link wouldn´t do fine. (I also DO KNOW about correct master/slave settings and so on, as they SHOULD work.)
What´s so different if I connect an A16 via ADAT, or another PC? One works, the other doesn´t... *grumblmumblgrrrRRRrrr*
All bugs confirmed as we´re three people here using three CW-based DAW´s in the same room.
We´ll go on bug-collecting over here and keep you guys posted.
JoeKa, ChrisWerner and FreiFlug
<font size=-1>[ This Message was edited by: JoeKa on 2002-08-08 16:33 ]</font>
STM1632 mixer unmutes channels after switching between 3/6dB panning law. Green Mix buttons remain grey. After manual reset, they behave normal.
more has been done with less
https://soundcloud.com/at0m-studio
https://soundcloud.com/at0m-studio
Better implementation of the midi presets, reloading of a midi preset don't fully work and devices have to be re-told what midi CC# they have.
Is there some way of having a fader or knob remember it's last CC# so while using a external midi fader box the device fader or knob doesn't move until the hardware fader CC# match
That would be 
Is there some way of having a fader or knob remember it's last CC# so while using a external midi fader box the device fader or knob doesn't move until the hardware fader CC# match
That would be Re: Yer right davo, mid implementation is still not 100%. Although these CC# preset lists are super c o o l. But it's not hm bug free yet. Let's hope they make some work of it.
Other bug: In many projects, the STM1632 starts to 'forget' it's channel label. Ie. the name is gone and invisible, there's just an empty background-coloured space instead of the channel name. The longer STM1632 is in the project, the more channel names start disappearing. Anyone else experiences the same?
Other bug: In many projects, the STM1632 starts to 'forget' it's channel label. Ie. the name is gone and invisible, there's just an empty background-coloured space instead of the channel name. The longer STM1632 is in the project, the more channel names start disappearing. Anyone else experiences the same?
Yip, I can confirm the channel labels that disappear, this time in the STM4896. I've had a 32 channel live mix sitting around for about 3 months, and so far I've lost the labels for Bass, VOX and Sax and they can't be re-entered... it's probably a good thing my ears don't forget what a sax sounds like...
First let me say I just noticed "Mouse wheels" are now semi-supported in SFP3.1a. Hurray! As far as I can tell though, they only work in the Routing window so far. <b>I would really like to see the wheel also work in the file browser and Live bar...</b>
I've got a really minor bug here with the mouse wheel:
It works great while wiring up devices, however if you have a synth or device surface up and bump the mouse button you get a strange little thing where the routing window will jump out of it's frame a tiny bit. Not show stopping, but would be nice to tighten up if it hasn't already (I know a new version is coming .. maybe something to test in the newest betas)
Background: SFP3.1a, MS Explorer mouse, WinXP, Standard mode (not classic).
I've got a really minor bug here with the mouse wheel:
It works great while wiring up devices, however if you have a synth or device surface up and bump the mouse button you get a strange little thing where the routing window will jump out of it's frame a tiny bit. Not show stopping, but would be nice to tighten up if it hasn't already (I know a new version is coming .. maybe something to test in the newest betas)
Background: SFP3.1a, MS Explorer mouse, WinXP, Standard mode (not classic).