PlanetZ forums - scopeusers.com

But still in SDK you are restricted to what the current set of DSP programs offers. On other open systems, you can add your own DSP algos freely, without being restricted by a Dongle or whatever.

faxinadu wrote: ↑Fri Mar 09, 2018 2:11 am no idea about windows 10 since i never used it. on windows 7 and xp and 98 all good.

Obviously: ASIo is loaded in 32-bit memory on Win7 and below. No problem there.

If any of them are 64-bit and loaded into 64-bit space (other than 0), running under Win10 and using ASIO: they 100% can't work.

I think it's more a matter of ownership. If Franks still owns scope 4 (or is a co-owner), he can do what he likes to do with it. If he wants to modify scope 5 or higher, he needs permission to do so.

I using the Teensy 3.6 platform for building extraordinary sound-modules. With 170Mhz DSP floating-point power, it&s good enough for a 8-voice polyphonic harmonic synthesizer. The SW is ope-source and easily expandable.

What drivers are you talking about? Low level like system device driver or something between ASIO and that?

I have a master degree in computer science and electrical engineering. I learned making things and solder from my father, who was a teacher at a school for that. I actually wanted to study music, but job outlook was disappointing. I'm building my own electronics since I was 14. Mostly guitar effects...

My studio/office/workshop is not as tidy, but I got everything, I need:

I have no problem with the guy himself or his equipment. But I think, as introduction into modular synthesis, it was a bit lame. If I had to do something like this, I would start from a nice sound and explain, what the parameters are and how to achieve that. No fancy fm or pm at the beginning and al...

I watched the video for about 20min. Yes, the hardware is impressive, but what he calls interesting is actually quite boring... And yes, I like modular synths, but they can do much more, if used with more creativity. My Teensy synth sound as well (see my example) and doesn't need as much space (just...

Congrats too. Did you actually pay 349（=$420) Euro instead of $299? That's a ripoff of 25%.

Has anyone successfully used either of these systems: Hydrogen Drum, Nyquist, Audacity or Faust? Does PD work?
I can't get none of them running on Win 7 or 10. If someone could to it, please teach me, how to. I tried Jack and Portaudio drivers to no avail.

Thanks for all the compliments, it was a long, but interesting journey. I also learned a lot. Regarding the fix: there are 2 possibilities: Either change the one spot, where the error happened, so that 64-bit addresses can be passed, or change the structure for every parameter, which contains 64-bit...

Just to confirm: under Windows 7, the ASIO driver is loaded into 32-bit space. Therefore no problem.

I asked me myself the same question. I'll take a look at that later. Maybe in Win 7 all process are running in 32-bit space.
And Voicemeeter is working, because it's a 32-bit application.

My suspicion was confirmed: ASIOScope uses 32-bit Address pointers when it should use 64-bit pointers. As Ableton runs in 32-bit memory space, there is no issue in that case. I informed Holger about my findings and I hope I could help. I can't do anything further atm, because not only the ASIOScope ...

After some in depths debug session, my conclusion is (sad as it might be): there is nothing wrong with the ASIO driver. The problem occurs deep in the scopexite.sys driver and is an access violation exception at this code: mov dword ptr [rax+rcx*4],0FFFFFFFFh with rax=00000000ee97f8b0 and rcx=000000...

First findings: (as expected) Ableton Live survives the same syscall, which ASIO SDK host doesn't. I.e. I can reproduce the problem, but still have no idea, how to fix it. I have to dig deaper into that specific call (it's actually not the first call which creates the BSOD, but other call have diffe...

Good News: I got the source from Holger and now I can find found, what's really happening.

Got my Win 7 working again. Tested in both x86 and x64 mode. As expected, nothing weird happened. In x64 the final syscall is #4 (status of the device) which returned the correct value.