PlanetZ forums - scopeusers.com

Thanks Berny
The tweeter loss was all my fault.
I was not paying enough attention to levels
Hope the plug is useful for you
maus

Hi There, I blew a tweeter in one of my Event ASP8 Studio monitors testing this device (Not the device's fault!!) Anyway, here is a small offering you might have some fun with. If you feed a mono source (e.g. a synth) into both left and right there might be a few presets that don't work as you might...

Reason 12 and SCOPE 7 work fine here on windows 11 64bit.
If you continue to have issues you might try running Reason asio into Reaper and then Reaper asio to Scope.
That usually fixes the asio incompatibilities I have come across.
Its the only time I use Reaper at all LOL.
regards
maus

What did you tweak in BIOS (UEFI) for Win10 ? Which mobo ? Bud Hi Bud, It was a long time back but I followed a tweaking post here on the Planet. From memory it was disabling EIST, Hyper Threading and Turbo Mode. My old MOBO was MSI X58A-GD65. BTW, I was curious whether Win 10 in the new build woul...

I don't think I was getting any clicks and pops on Studio One before and I used it regularly.
Win 10 was BIOS tweaked though
Thanks for the info
regards
maus

Just a quick update to set the record straight.
The problem with iLok had nothing to do with the hardware or windows upgrades.
I had forgotten that iLok is not compatible with Bitdefender which I installed sometime back.
Sorry for any confusion, just an old brain not remembering right.
regards
maus

How much bloatware is Win11 compared to Win10 ? Does "WinPrivacy" work w/ Win11 already,- or any of the other apps which can be used to shrink Windows and stop spy traffic ? Hey Bud, I have not run any windows shrink software to date, so can't advise on that area. Windows 11 looks a littl...

Hi there, Not sure if anyone else has posted on this subject, but I have just finished upgrading my PC to be win 11 compatible and installed win 11. Scope 7/XITE worked straight up with no BIOS tweaking (no audio crackles). There were some issues with some software, tools and plugs with regards lice...

This is my latest midi device which you might find useful. It has: - 3 midi ins - 6 midi outs (each with their own midi filers) - Individual midi filter pages (Click one of the Mid Filter button to display its filter page) for each of the 6 midi outs for detailed filtering of port midi data - Midi f...

Hopefully this will help I managed to get Giada working into scope asio by feeding it thru Reaper first. The image below shows the Reaper setup and the Giada Config that makes use of Reaper's asio IO. Reaper has for me solved a number of incompatibilities between scope and other apps by using this t...

Watching your posts closely
It is likely I will build a new system some time soon to bring a new PC into line with win 11
Thanks for the updates
maus

you could load a poti, and load the skins as an animation (attributes = bottom, not selectable ) then connect another poti that will control which skin is displayed (val to val connection) with both animations having min val = 0 and max val = 2 , steps = 3 or -1, so you can get all your skins insid...

Thanks guys
maus

I released a version of this device before, but this is a complete redesign and adds a couple of new elements. I have included 3 versions with only skins being the difference between them all. They all share the same presets. Features: - 2 bands (Bass and Stereo) with widths controlled by the xover ...

Looking good Dante
I use MixBus32 exactly as you describe, not the main sequencer but great for stems.
Good to see Hitfoundry is alive and well.
maus

Good news

Hey Dante,
Mixbus32C-6 works on all 3 samplerates here.
I load SCOPE at 48KHz (Default Project) and then set the samplerate to either 44.1K or 96K and run Mixbus with Buffered I/O.
It all works as expected.
maus

petehalo wrote: ↑Tue Aug 24, 2021 1:47 am Unfortunately with my main DAW Harrison Mixbus there's problems while trying to get the DAW started with Scope ASIO drivers.

I seem to remember I had to select 'buffered I/O' in the setup to get mixbus to work with scope.
Anyway it definately works with scope
Hang in there
regards
maus

in sdk, you could probably add a lot more connections using the "on same dsp" attributes of the device/module (val=1) when building. but you must desactivate it for scope/xite users, before saving the device 'val=0 or -1 can't remember right now, it must show "not set" once relo...

I can see this becoming a real problem down the track. I checked my 2 DAWs and neither are compatible with win 11, 'secure boot unsupported'. We may be able to live with win 10 for some time to come but eventually we will need to upgrade, you can bet on it. I see Win 10 is somewhat capable of a moth...