[resolved] On XP running Scope 5.0.2617? I need your ASIO modules

[at0m]

Hi,

I dun goofed on my ASIO2 24 Bit Source and ASIO2 Dest modules. Not sure what happened, I think it has to do with my tidying up $scope\App\Application\IOs too much. Backed up my Scope dir, reinstalled, then that gave me keys issues. Restored my backup Scope dir, but that also returned my borked drivers.
Then copied over from my Scope SDK dir, but double-clicking ASIO there gives me the old Scope blue options panel. Think I restored backup again, and now ASIO2 Dest gets me Dest 64. What the...

So if anyone running XP and Scope 5.0.2617 could zip me up their ASIO2 24 Bit Source and ASIO2 Dest modules, or even the full IOs\Software directory, that would be the easiest quick fix before I spend days on this.

Thanks in advance,
at0m.

[valis]

Can't you extract them from the installer?

[at0m]

Haven't tried. Getting late and I've powered down the studio for today, but will give that a try tomorrow. Launch the installer and search the temp files.

[garyb]

something like this?
https://sourceforge.net/projects/setupextractor/

[valis]

That, or many are even able to be opened with 7Zip or Winrar etc. It depends on the options chosen by the developer when they compile installshield (or etc) all-in-one exe installers.

For instance my 5.1.2790 installer for instance seems to be CRC packed and then a binary CAB file inside that is not able to be seen by extraction tools. Sadly I don't have 5.0.2617 on hand to try.

Curious though, are you too time limited to get 5.1 running stably?

[at0m]

That, or many are even able to be opened with 7Zip or Winrar etc. It depends on the options chosen by the developer when they compile installshield (or etc) all-in-one exe installers.

For instance my 5.1.2790 installer for instance seems to be CRC packed and then a binary CAB file inside that is not able to be seen by extraction tools. Sadly I don't have 5.0.2617 on hand to try.

Curious though, are you too time limited to get 5.1 running stably?

* Winrar doesn't cut it.
* I noticed I was using the wrong installer, 5.1.2790. Refuses to start most of the time. And if it does, doesn't take any of my keys.
* The version I use, 5.0.2617, installs and runs just nicely. But here I do not find any Asio2 24bit Source - only the "ASIO2 32bit Source 64". Meh.
* I had used an old project that did have the 24bit driver somehow , and made a godzillion Externel Effect aliases for the "ASIO as VDAT patch" that use that 24bit ASIO2 driver. I guess I'll have to settle with those 32bit 64ports drivers, and redo all my patches before another week is lost trying to resolve this.

Thanks for your ideas, folks. Too bad that didn't work out :/

[garyb]

use the 32bit source. it will run at 24bit, if your sequencer is running 24bit.
the modules were simplified in v5.

this should not affect your old projects.

[at0m]

this should not affect your old projects.

Except for IO Aliases that I use rather extensively - the External Source/Dest/Effect devices.. Those saved devices load blank since they do not find any "ASIO 24bit Source" anymore. I need to figure out their port numbers, then re-save them.

I love how these devices unclutter the project: neat aliases not generic "source/dest this or that", much less spaghettification, plus <3 can be inserted in modular patches where connections are saved with presets within the patches. The latter means very DSP efficient changing connections on the fly using MIDI program changes, without the routers that cause so much overhead since these are all hardwired switches.

I do understand the design decision for how to switch, where different DAW would no longer require different drivers to be loaded for example., or where it would cause less overhead. Seems I'm one of the edge cases where it isn't At least for now.. In time, when historical (I opened a 2004 project today!) presets are re-saved, that will sure be an improvement.