PlanetZ forums - scopeusers.com

But why cant I import standard AKAI files to the STS samplers any more, without crashes?
Does it have something to do with 64 bit?

Same problem here.
Any solutions?

Not that I'm an expert of the Akai 'format', but afaik that applies to a specific disk format ('volumes' etc)...
low level reading of rather obscure stuff, errors to be 'fatal' by default.
One thing to keep in mind is that CDs unless 'pressed' commercially are an extremely unreliable source of data.
There are probably tons of disks that look 'professional' but have simply been burned by the manufacturer just the way anybody did his backup or copy at home.
The 'old' 32bit environment might be more tolerant in that context or recompling/modifying stuff has put up new conditions.
It's difficult to judge, as the software spans quite some range from reading the drive to moving the data into the Scope environment.
At least I wouldn't expect Sonic Core to have a major amount of effort invested into this aspect.
It's probably not libraries for a 32 MEGA-byte sampler that people who demand a 64bit adress space are after...
to be honest... I'd frankly call you (well, maybe not...) if you insisted on flawless operation in that domain, too

cheers, Tom

I'm experiencing some random pops with the wave drivers. On XP 32bit the wave drivers worked fine.

Miniscope and MK II in v5.1

JL wrote:I'm experiencing some random pops with the wave drivers. On XP 32bit the wave drivers worked fine.

Random pops with the wave driver here, too...

katano wrote:

JL wrote:I'm experiencing some random pops with the wave drivers. On XP 32bit the wave drivers worked fine.

Random pops with the wave driver here, too...

same here

[quote="Cochise"]Miniscope and MK II in v5.1
-same here on miniscope and mkii-.. but miniscope wavelength edition works fine
-aso problems with sts sampler ... after loading 3-5 sts files ..bsod
and sometimes the sts sounds like a 8 bit sampler .... i gave up on sts ..but i miss the sounds from my akai xxl pad collection

hi,you are very lucky because my scope64 don't want run.
It fail the start. ,
i think that we can stay here to wait so many time before the software 64bit run well!!!

You guys posting these to SC?
I doubt that they're reading this thread.

I will also try to ask them about these at NAMM.

Greg

widy wrote:

Cochise wrote:Miniscope and MK II in v5.1
-same here on miniscope and mkii-.. but miniscope wavelength edition works fine
-aso problems with sts sampler ... after loading 3-5 sts files ..bsod
and sometimes the sts sounds like a 8 bit sampler .... i gave up on sts ..but i miss the sounds from my akai xxl pad collection

Just tried the Wavelenght Miniscope and it works; Didn't tried Sts x64 yet... The 32 bit version looks working at a first try.

siriusbliss wrote:You guys posting these to SC?
I doubt that they're reading this thread.

I will also try to ask them about these at NAMM.

Greg

Even though I am sure they read here, yeah, I emailed them as well.

Here are some of my problems

Error
1.) Today I've tried STS5000 (which was included in the 5.1 Upgrade) to find out that Win7 also has a BSOD IRQ_NOT_LESS_OR_EQUAL. As soon as I send the first midi notes to STS I get the BSOD.
2.) Miniscope MKII opens without background, only control elements show on screen. So I can confirm a previous post in this thread.

Minor nuisance
1.) I use a dual screen setup with scope routing window on the second screen but Popups always open on main screen.

Anyone with solutions to this?

The answer I got was to deactivate the following settings
in BIOS :

Intel EIST
Intel C State
C1E Support
Overspeed Protection
Hyperthreading
Execute Bit Support
Set Limit CPUID MaxVal to 3 (maybe not so important)
Intel Virtual Tech
Intel VT-d Tech

Will do it tonight, expecting your answers as well.

Throttler wrote:The answer I got was to deactivate the following settings
in BIOS :

Intel EIST
Intel C State
C1E Support
Overspeed Protection
Hyperthreading
Execute Bit Support
Set Limit CPUID MaxVal to 3 (maybe not so important)
Intel Virtual Tech
Intel VT-d Tech

Will do it tonight, expecting your answers as well.

I dont even have those in my BIOS!
I got to old computer i guess.

Hi all

I just want to share a short test I did yesterday.

I tried the BIOS optimization, or at least the ones i've got available in my Dell Optiplex 780 BIOS. I noticed no difference with occasional clicks/pops at all, except for the hyperthreading. When I disable hyperthreading, my large mixing projects in Cubase 5 with about 36 channels and just a few vst effects doesn't play well at all. I got nonstop crackling and the cpu usage is peaking every second. When i enable hyperthreading both in bios and cubase, it works well! Except for the wave driver, which still got occasional clicks and pops... oh, and the Set Limit CPUID MaxVal to 3 parameter doesn't seem to have any effect at all...

Conclusion for my setup: With or without bios tweaks, the result is the same...

Cheers
Roman

what do you mean by pops with the wave driver?

i am currently using xp (planning to upgrade to 64 bits soon) and i use the wave driver to playback windows multimedia (winamp and internet).

i will not use wave for recording with sonar, which works with asio.

is wave (out) driver working in win7 64 bit for normal apps??

I have enormous trouble with Scope 5.1 win7 64 bit. With Cubase 4.
Running with Scope ASIO it crackles a lot even with only one Halion One playing some chords.

But when I run Cubase alone with Creative ASIO I can have tried 6 VST synths playing massive chords at the same time and not a crackle at all.

CPUID Max Val To 3 is disabled on my rig.
PCI Latency Timer is set to 64 also.

i am as close to realtime as one can get.
64 samples @ 1.4msec/44.1k Duplexed ASIO in Kontakt 4.2 Standalone.
Scope is definately not the culprit.

I also use 4 x Instrument banks and 8.1GB's of RAM.
Each Instrument Bank loads a kick butt instrument instantly as if I had a hardware Rompler.
I only use 68 sampled sounds, but each sound has been developed using NCW lossless audio.
This current template would have required 16GB's of RAM w/o NCW.

This is the most awesome live performance rig I ever owned.
I am sure this is unnecessary for most cats here, but if my rig can have unlimited poly in realtime and change presets instantly, I would look to to the overbloated hosts that seem to never optimize their software/coding quite enough.

NI is way ahead of the curve and even Reaper is able to do 2.9 ASIO duplex @ 64 samples/44.1k.

Perhaps Tragic, Spubase, Cakeland, Blonar and BlownTools are just too big for their britches these days......................

no, they work as well.

Roman, have you played with the wav buffer settings in the app using the wav driver? you're not using wav drivers with Cubase, right?