PlanetZ@scopeusers.com

the wave driver inputs have NEVER worked in 64bit. they don't work in your computer either.

ASIO drivers DO work, so the cards are far from useless, unless you want to use them for something they weren't designed for, like Skype.

the next release of Scope should have this issue fixed.

in 64bit, wave drivers suffer random pops. in 64bit, wave driver inputs don't work. for Skype, use the built-in audio's mic input. these are known issues. wavelab needs a patch. this is pretty well-known as well. steinberg made the patch years ago. it is attached. ASIO should be clean. if it's not, ...

that should be ok.

system information is easier to read...(how to get there is in the link).

most importantly, is EIST and Hyperthreading turned off?

i can never figure out what some people do to mess up installations, but it happens. you can usually update win7 to win10 without problems. your mileage may vary. yes, you can take the win10 installation and move it to another mb, but that can be tricky. there are steps or apps that will help. the X...

hopefully it's just setup stuff.
the most important points in that posting are also in the .pdf letter that accompanies v7.

the only time mono is important is in club mixes. that's what the mono button is for, to be sure that a mono mix doesn't exhibit strange behavior(phase anomalies). otherwise, everything that involves panning and left or right is stereo. mono means one channel, period.

oh, that's easy to do with the STM2448. you can use a bus for that. you can use direct outs, too. you need to study hardware mixer design.

stereo is dual mono. there aren't any middle tracks. mid/side middle is equally in both left and right. everything else is more or less left and right. there is no 3rd track. i'm not sure what the purpose is...

true mono would not leave things left and right.

except that when you open projects made in PCI with the XITE, or vice versa, or if you open a project made in a different version of Scope, then you will be asked to locate files. that's how it works.

resaving the project once should end all that. optimasterx is an XITE device. optimaster is a PCI device. you must be loading a PCI project to your XITE. that will certainly make the system ask for device locations, since the project is saved with PCI file locations. needing to constantly save proje...

just use browse to find the proper location.

it's because you are loading an old project that had a different directory.

the main benefit to windows 10 is that it's current and it supports the current software. in addition, the latest motherboards require it to function fully. i haven't had any issues from the lan connection. it hasn't significantly affected performance. it's not like XP. if you have a working machine...

it doesn't HAVE to be, but it might as well be.

computers are heading into a very iffy direction, but that's progress, right?

win 10 MUST update.
there should be a connection or things don't work correctly.

sometimes when a graphics card dies, the system still works. the only problem is that graphics are not offloaded to the GPU, but instead are handled by the CPU.

you can make your own...

http://www.hitfoundry.com/issue_15/dsub_mst.htm

no win10 issues here....

a compressor basically does that. a VCA would be the same as just normalizing the part. there is not anything that can think for you, and there is no getting something for nothing....or i probably misunderstand the request...