Scope and Windows

[Bud Weiser]

You can make the required key and entries

So, you say,- when I create these inside an allready installed Win 11 Pro 21H2,- the machine will automaticly update again and up to 24H2 ???
And from there, it will receive all the upcoming updates ?

Or,- are these workarounds only valid for "fresh install" and once installed, it´s all set in stone again ?

I don´t wanna use the "Tiny11" just because no one really knows who that guy, offering this shrinked software, really is.
He´s a private person, not working for MS and no one knows what´s implemented and possibly hidden in such "builds".



Bud

[Bud Weiser]

You can make the required key and entries

I did now and rebooted.
Doesn´t work w/ Win 11 Pro 21H2 installed already.
Searching for updates comes up w/ the same result and "security updates missing" warning.



Bud

[fra77x2]

come on guys don't say a hardware's asio driver has issues if some
plugins don't run in stand alone mode. The fault is with these apps.

The asio is flawless in my case and my apps that use asio work fine. ( I use rtaudio )

The daws that have issues too bad for them...

[Bud Weiser]

come on guys don't say a hardware's asio driver has issues if some
plugins don't run in stand alone mode. The fault is with these apps.

The asio is flawless in my case and my apps that use asio work fine. ( I use rtaudio )

The daws that have issues too bad for them...

Yes, but I´m sure it´s both,- the driver and the apps/plugins,- and it´s hard to find out why.
I say because they ALL run fine w/ the RME HDSPe RayDat and Babyface drivers and on 2 different machines,- main DAW Win7 Pro 64Bit and laptop Win10 Pro 22H2 x64.

So,- there IS something w/ the ScopeASIO driver since Scope version 7 64Bit,- last but not least because these issues weren´t present in SCOPE v5.1 32Bit.

I´d really, really like to use SCOPE/XITE 7 x64 as the only audio interface w/ Win11 and laptop in future,- ASIO and WAVE drivers.
Can´t wait for the driver updates being announced since 2 years now.
And, it should work w/ Win10 Pro 22H2 x64 already as perfect as RME drivers do !



Bud

[fra77x2]

Ok Bud but please let me add something. You have a dream and that'snice and perhaps it would happen but i am sure you understand the realities of programming.

For an example google is one of the biggest companies and when i go to youtube studio ( a google company) in an android device ( the same)
the interface doesn't fit... I have to use my windows pc.

So if we constantly want stuff to be made and we regard these as issues forgetting the intricancies of programming perhaps this works against our wishes

[fra77x2]

Also if your RME does that well the xite can do something else that RME doesn't. Who cares. Find a system that works and start working and stop changing it. If something doesn't work don't use it. It is very easy I am not sure why you still can't setup your system right.

[Bud Weiser]

Also if your RME does that well the xite can do something else that RME doesn't. Who cares. Find a system that works and start working and stop changing it. If something doesn't work don't use it. It is very easy I am not sure why you still can't setup your system right.

I have working systems because I use SCOPE/XITE v7 64Bit standalone as an application on a different machine.
That´s o.k.,- but WHEN an application comes w/ ASIO driver out-of-the-box, the driver should work flawlessly.
The WAVE driver too.
And assigning MIDI CCs to device parameters should be storeable permanently per device to be 100% total recall.
For every device´s preset list there´s a MIDI controller bank existing,
Whatfor when assignments go south when closing a project ?
It´s cumbersome re-assigning MIDI CCs for every device I re-load into new projects.

YMMV



Bud

[fra77x2]

Ok. I guess you have to find a system that scope works with your daw, I mean like the system i use everyday for the last 15 years.

Too bad really. I feel you or I try to, or just say I imagine it. What a waste...

About the CC's let me give you a tip. Forget it. Stop talking about it. It would never happen. Wake up.

[fra77x2]

Tip. in the sdk the midi controllers work fine... recallable. Everyday every hour.

For the Scope software i believe it would never happen. Don't give a damn personally

[Bud Weiser]

Tip. in the sdk the midi controllers work fine... recallable. Everyday every hour.

For the Scope software i believe it would never happen. Don't give a damn personally

No SDK here.



Bud

[fra77x2]

I rarely use midi assignments. Too complicated to write. I record hands-on. If it is messy complicated or feels like surgery in complexity
i don't do it. I like knobs and audio modulations, lfos etc. I always record.

I have 14 bit midi controllers for scope, I don't use it. I like how it sounds if i turn the knobs while listening and recording.

I consider my roland-se a ruined analog synth with 7 bit midi on the pots ( it also receives cv for the filter for people like me that consider this important). It offers the 8bit midi controllers on the knobs for the people that do not consider it important to have a steppy analog filter. And who are these people really? The jackasses...

Or the 7-bit midi on the delay time.... It is never right

[fra77x2]

Imagine even in planetz it stills logs me out while replying to messages. I always copy the string before submiting... The last 10 years. And you wait for the CCs to be fixed...

[Bud Weiser]

Imagine even in planetz it stills logs me out while replying to messages. I always copy the string before submiting... The last 10 years. And you wait for the CCs to be fixed...

Fra,- I´m not a recording/ mixing engineer in 1st place,- I´m a keyboardplayer like Jimmy was.

I love using NoahEX and I´d wish SCOPE synths on XIte-1 worked perfect w/ MIDI CCs.
That´s it.
The Scope synths sound very good and I don´t have to think about latency.
I know there are workarounds,- but in my age, I have to think about usage of my lifetime too.
Tinkering w/ all kind of workarounds, not only in Scope, is wasted lifetime too.

B.t.w., I too get logged out often when typing posts here and I copy all the text to clipboard before clicking the "review" or "submit" buttons.
Happens randomly and out of the blue,- so saving the stuff before is essential for me.



Bud

[fra77x2]

I think if you assign the controllers to a device in the sdk and save it, it keeps the controllers fixed in the scope software too. perhaps some sdk user can check this.

Playing the keyboards is great. I will upload a synth for Xite at christmas with some fixed midi assignments to give it a play. 16 voices and my band limited sawtooth. I will wait for your impression

Does your midi keyboard offer 14 bit midi controllers?

I will put 14 bit if you like. Its night and day compared to 7bit

[Bud Weiser]

Playing the keyboards is great. I will upload a synth for Xite at christmas with some fixed midi assignments to give it a play. 16 voices and my band limited sawtooth. I will wait for your impression

Interesting !

Usually I need:

1.)
pitchbend w/ range control in GUI (1 semitone up to 7 semitone steps and 1 octave up/down)
2.)
Modwheel and/or (!) AT to global LFO for pitch- and/or filter cutoff modulation.
3.)
MIDI CC#4 to filter cutoff or,- when there´s OSC sync available,- modulating the slave OSC´s pitch to get these harmonic sweeps via foot-control.
4.)
MIDI CC#64 (sustain)
5.)
A freely assignable MIDI CC for filter resonance control is welcome.
6.)
Pulse width modulation w/ assigable MIDI CC is welcome too,- if there are PWM-OSCs at all.
7.)
If there´s a ringmodulator in the ballpark,- freely assignable MIDI CCs for pitch and amount were essential too.

2.) and 3.) require some routing options since it makes no sense modulating filter cutoff by wheel and foot at the same time,- and I prefer wheel for vibrato and foot for filter.
But I also like wheel and AT together for vibrato ´cause this is how I use my Kurzweil very often and w/ it´s local stored patches.
The wheel assigned to vibrato-LFO depth and also slightly affecting the filter cutoff frequency at the same time and on demand is also very nice.

I know,- that´s already a bit complex and possibly not to achieve w/ fixed MIDI CC numbers.
A small mod-matrix w/ multiple entries for mod-sources and destinations and freely assignable MIDI CCs were perfect.

VST/AU can do,- SCOPE cannot,- that´s the problem.

Does your midi keyboard offer 14 bit midi controllers?
I will put 14 bit if you like. Its night and day compared to 7bit

I don´t think so.
I have several keyboards from the past where only PB is 14Bit.
My most up to date keyboard instrument is still a Kurzweil PC361,- and as much as I appreciate it´s MIDI features, I was disappointed to read that it´s pitchbend resolution is also 7-bit only. What a pity.

But,- IIRC, the Kurzweil manual says there´s the option to create 14bit resolution by combining 2 controllers,- but I never tried up to now.

Finally the most important:

My XITE-1 is currently disconnected from my main DAW machine since it became a RME HDSPe Raydat machine.
The XITE´s PCIe card is not inserted anymore.

To use the XITE-1 again, I´ll have to setup my Lenovo W540 laptop all new from ground up and w/ Win10 Pro 22H, then install SCOPE v7 and all my setup again.
My Win10 on this laptop got ruined by NI´s damn buggy Native Access and a fresh install is faster than finding and fixing all the damage.
I already bought a new and larger SSD and when I find enough time, I´ll do this over the holidays.

When all goes well, I´ll be happy checking out your new synth.

best,-



Bud

[fra77x2]

I will make you one with fix controllers and not many stuff inside so to get 16 voices.

Tell me when youu ll have your xite back working. updating is a very difficult procedure for complicated systems and can lead to a nonworking system. I avoid like the plague.

yesterday i updated a single dependancy in my android code and then i couldn't compile the project anymore. I had my backup of course

wishes for the holidays

[Bud Weiser]

I will make you one with fix controllers and not many stuff inside so to get 16 voices.

Tell me when youu ll have your xite back working. updating is a very difficult procedure for complicated systems and can lead to a nonworking system. I avoid like the plague.

Thx a lot for your generous offer !

It´s not matter of updating.
It´s about setting up Win10 Pro again incl. all the drivers etc. necessary for the Lenovo W540,- then tweak w/ W10Privacy.
And I hope the OEM product key will work since I don´t have a MS account.

I cannot use a backup by different reasons,- and NI ruined the system and setup anyway w/ their buggy Native Access software.
I also expect many VSTplugin activations would be invalid w/ laptop hardware changes.
The laptop got more RAM and will get a new and larger system SSD too.
I´m still waiting for the drive and maybe it will be in the post today, but not sure.

A fresh OS install and installing SCOPE/XITE as the main application is the best option.

I´ll use the other laptop for more native VST stuff then,- but that´s another story.
I also hate this computer tinkering s##t,- it´s all so boring tasks.

wishes for the holidays

Thank you,- best wishes and nice holidays too !



Bud