PlanetZ forums - scopeusers.com

Posted: **Fri Mar 21, 2008 12:29 am**

I completely agree with this one.

If this thread should have any effect we should use the bug report below - oh and the bug should be reproducable and actual (nothing we have heard about etc)

pollux wrote:By experience, bug reports should contain at least the following information so that they are actually helpful for the dev teams:

* severity
* nature of the bug
* circunstances under which it appears
* frequency it appears
* blocking or not (workaround possible)
* workarounds (if any)
* detailed instructions to reproduce it
* OS Version
* SFP Version
* Plugin / Module Version (if corresponding)
* any other information you find useful

Let's try to stick to a certain structure in order to make it easier for everyone
We should also check if a bug we found is already listed prior to posting it, to avoid dupplicates, and in that case simply reference it so that the new occurrence is counted.

Feel free to add any other "fields" (bug submitters and dev teams)

(please, let's stay focused and be objective in this thread as this can be of big benefit for all of us)

Cheers!

Raul

Posted: **Fri Mar 21, 2008 12:42 am**

I thought this thread was going to be bug reports?

Now it's become a discussion about STS and feature wishlists?

I've not seen a single actual bug report posted (including detailed reproduction steps etc as posted in the second post in the thread).

Not trying to be a bitch here

but I'm not sure it would be of any help to SC if everyone is just gonna post randomly.

Posted: **Fri Mar 21, 2008 1:36 am**

King of Snake wrote:I thought this thread was going to be bug reports?

Now it's become a discussion about STS and feature wishlists?

I've not seen a single actual bug report posted (including detailed reproduction steps etc as posted in the second post in the thread).

Not trying to be a bitch here but I'm not sure it would be of any help to SC if everyone is just gonna post randomly.

Then dont bitch! I dont see can it be more simple then that? Reread all post again. You will find some obvious bugs. There are people in this thread which dont post randomly ya know. To guy with STS "advice", please make your own thread regarding STS in "STS Talk" area!

Can we go back to main subject? You know, bugs in current version...Good! Thank you! (John Cleese and Fawlty Towers comes to my mind...i wonder why?)

Posted: **Fri Mar 21, 2008 2:02 am**

test on stm16/32 i load and remove optimaster in insertslots 30 times without any trouble!
sfp 4_5 win xp sp2;

without reproducable scenarios this thread is useless!

the i think misterious vibes going on sometimes somewhere i dont know . .
was it sfp4 or 4_5 i cant remember right now but . . you know for sure
posts are very funny thats all;

bug vibes from vienna
or was it wishes ?
who knows _ who cares?

Posted: **Fri Mar 21, 2008 2:16 am**

Guys, lets continue this AFTER SFP5 is released

Posted: **Fri Mar 21, 2008 3:52 am**

yeah, this way this thread is useless (which was predictable anyway

).
reporting bugs is an art, people not even mention platform and OS.
bugs? hardly seen one in this thread...

Posted: **Fri Mar 21, 2008 4:50 am**

I have altered the first post to make this thread more relevant.
I don't think the thread is useless, we have to accept there will be some reports that aren't of much use and some straying off the subject at hand,

Posted: **Fri Mar 21, 2008 4:53 am**

sdk crashes a lot when being heavily thrashed with a large stick. Sorry if that's OT

Posted: **Fri Mar 21, 2008 6:44 am**

I aggree a normal fix list don`t look like this, but at the end Scope 4.5 is really old and I think SC are aware of these little problems.

So a collection of the little problems is just fine. ( I mean all in one thread)

I have another one:

If you build a modular patch, you sometimes come to the point, where you cannont cable connect to modular pads of one module.

Workaround is to disconnect the problematic mod_module by right clicking it choose "disconnect" and reconnect it from scratch.

happens randomly....

Posted: **Fri Mar 21, 2008 7:37 am**

- cd access and akai dlls fix
- support for command line (double-clicking) project opening, this should be easy since once it worked.

cheers
Fede

Posted: **Fri Mar 21, 2008 10:36 am**

BUG-3rd party plugins are not saved in screensets.

I am using the SFP 24/48 mixer

If you save a screenset with just the plugins showing for instance, the 3rd party plugins aren't saved and they "hang over" if you select a different screenset.

Also if you have a screenset with the main out mixer panel showing it won't save the selected channel, selected, in that screenset only the one you've currently selected.

Found a great use for screensets now but this bug hinders my flow.

Posted: **Sat Mar 22, 2008 8:31 am**

another thing that annoys me a bit is the dsp allocation error with minimax.

Don`t know why but it only happens when loading minimax. Prodyssey and all the other stuff works fine....

sometimes relocation on dsp works sometimes not....

here is an example: i got a standard setup (44,1 khz, ... )

when loading the first minimax the error appears but when i click retry, it is solved. But when I try to load the second minimax, the error appears but retry doesn`solve the problem.

but i still got round 8 unused dsp....

I would be happy if that could be fixed as well.

I cannot say exactly when this appears, but I think I did not have this error when I had 2xPulsar2(6dsp) installed.
So a reason may be the ScopePro(14dsp) and ScopeProject(6dsp) combination.

Posted: **Sat Mar 22, 2008 8:56 am**

Using an external sequencer (in my Yamaha RS 7000) that sends clock out MIDI signal freezes the whole computer. Typically in the Scope 4 project I have a synth (like Vectron) that receives MIDI signals.

Posted: **Sat Mar 22, 2008 2:41 pm**

Hifiboom, at the background of your screenshot I can see a word-document called "Diplomarbeit"!
Do you write your Diplomarbeit about Scope?

Sorry for OT.

Posted: **Sat Mar 22, 2008 4:08 pm**

well noted

Posted: **Sat Mar 22, 2008 4:33 pm**

the reallocation bug isn't a bug.
depending on what devices get loaded, there may not be multiple dsps right next to each other, which is what a big device like minimax requires(latency issues between dsps). at least scope will reshuffle the project and load the dsps in a way that will fit, even if it's eventually. Pro Tools HD will just refuse to load, period, until you make a new project or buy more dsps......

Posted: **Sat Mar 22, 2008 4:47 pm**

garyb wrote:at least scope will reshuffle the project and load the dsps in a way that will fit, even if it's eventually. Pro Tools HD will just refuse to load, period, until you make a new project or buy more dsps......

bingo.

Posted: **Sat Mar 22, 2008 7:06 pm**

Herr Voigt wrote:Hifiboom, at the background of your screenshot I can see a word-document called "Diplomarbeit"!
Do you write your Diplomarbeit about Scope?
Sorry for OT.

no, my Diplomarbeit is about coding a software for heuritsic price calculation in Yield and Revenue Management.

thats why I have less time doing sdk projects the next 1,5 months. currently everything is on hold.

but how does A.S. said in T. : I`ll be back !

Posted: **Sat Mar 22, 2008 9:09 pm**

garyb wrote:the reallocation bug isn't a bug.
depending on what devices get loaded, there may not be multiple dsps right next to each other, which is what a big device like minimax requires(latency issues between dsps). at least scope will reshuffle the project and load the dsps in a way that will fit, even if it's eventually. Pro Tools HD will just refuse to load, period, until you make a new project or buy more dsps......

What!? Pro Tools has bugs? But everyone keeps telling me that Pro Tools is perfect....

I think the version of MiniMax that was updated for "MidiMax" fixed the DSP errors, didn't it? I don't remember the link to it....

I also occasionally get the Mod3 connection bug, and the loading bug...so you all were right about that.

Here's another bug I sometimes run into: when shifting around DSP resources, sometimes the velocity of a synth suddenly doesn't work properly -- the velocity value for a note gets tacked onto the next note, like a velocity delay. Worst with MiniMax especially. It gets fixed if I disconnect the MIDI connection in Scope and reconnect it. Has anybody else had that?

Shayne

Posted: **Sun Mar 23, 2008 1:51 am**

it's not a bug on PTHD either, although you can believe even PT has bugs(all complex software has bugs, hence all the hotfixes). PTHD just doesn't allow partially loaded dsps to be used for other purposes. Scope tries to squeeze all the use possible out of the dsps the system has.

the problem, when you get that message, is that there isn't enough contiguous dsp space for the plugin(minimax takes a couple of dsps), so the system asks if you want to reshuffle to make room(giving you a chance to protect your work before trying). it's a GOOD message, in a sense...

PlanetZ forums - scopeusers.com

Bug reports for Scope 4.5 hopefully to be fixed for Scope 5!