Windows 10 Is A Free Upgrade For 7 And 8 Users

[TapperMike]

I never use it.  I haven't bothered to even turn on my laptop in the last month.  Right now I'm content running vista on my desktop. 

[starise]

I had typed a much longer response to the porn sites David...but decided to try and keep this on topic. Might be a good topic to discuss over in the lounge area. I don't think it's harmless and I know this from experience...but as I say, I won't go there right now.  

I'm loving my Win 10 64 bit! The computer will be loaded with Acronis and other than as a recording DAW, only used for  basic stuff on the web. Hopefully I'll be good for a long time to come.

I had a lot of software to re register and I had a few minor issues with audio drivers. Using WASAPI drivers the computer only seen 8 ( not 8 stereo channels) of my 16 channel sound card. The only thing that worked was using  ASIO drivers which I was already comfortable using from my last build. My old Win 7 computer would sometimes reboot on it's own when I used Sonar and switched to Studio One if I was set for 24/48 on Sonar and 16/44.1 on Studio One. I think this computer has a similar issue. I had to make sure that all devices and drivers were set to the same bit rates. I also disabled all of the audio to my motherboard sound so there would be no conflicts with my sound card. Since Firewire is used less for audio I needed to make sure that I bought a PCIe to firewire 400 card with the Texas Instruments chipset. I sometimes get an alert that the audio engine stopped in Sonar, but it always works when I record, so I think there may still be a conflict somewhere but it isn't affecting the audio or the recording. Another thing I did was disable all windows sounds. You can go into control panel and select to disable that.

It seems that Microsoft really did their homework with respect to drivers. Early reports I'm getting are that even older drivers written for Win xp work in Windows 10. My interface was made in 2009 and the older control panel and drivers still work. 

With all 16 channels of my Presonus Firetube Studio set to be active my latency is a little high, but I can't tell it when I play a soft synth. I seldom use input monitoring anyway.

All in all working with Win 10 has been a pleasant surprise

 

 

 

Edited December 2, 2015 by starise

[TapperMike]

Have you checked with presonus for driver updates?

Firewire like thunderbolt has security risks.  In Microsoft's attempts to patch those risks it may be gumming up the works.

Some programs allow you to allocate which cores to use for certain things.  This is important as it can be used to bypass the interrupt process.  Midi operates on interrupt.  Which means if your computer is checking something in the background you have to interrupt the process first.  If the operating system says "no you can't interrupt what I'm doing" then the signal has to wait.  Sure it's all small stuff today compared at what windows used to run before but it still can lead to inconsistencies.  Sort of like using external plugins with ableton live.  The sample rate doubles for each non included AL plugin you are using It gets downright stupid after awhile which is why I no longer use AL.

[starise]

Yes I checked the Presonus site for updates and since my hardware is considered to be "legacy" and was discontinued, Presonus no longer continues to update it. I am using the latest drivers that were said to work with Win 7 and 8.1. FWIW most anything that works with 7 seems to work with Win 10. The last update on my hardware was fairly recent though, even though they stopped making these interfaces.

The default drivers for my onboard sound were WASAPI drivers, so I  disabled those drivers in my control panel. A bios update may cause problems though.

Like Focusrite and several others Presonus interfaces (sound cards) have a go between software program that lets you set up bit rates and  has a mixer that lets me control my outputs and inputs fed to my DAW software. Since this program is tied to the drivers it runs in the background all the time and it this is where I set my bit rates and resolution . When using Studio One it immediately recognizes everything...one benefit of buying a sound card made by the same people who made your software. Not too much more trouble to use Sonar though...just a few adjustments in the audio preferences.

On another forum someone said that Win 10 was changing their audio settings when it runs updates...this is what I'm thinking might be happening. If true, Win 10 could be trying to make changes and my audio software might be locking it back causing the audio engine warning. What ever it is, it only lasts for a second and the engine goes right back online. Never happens while recording. Only when I initially start a project. Once I record it goes away and I never hear any sound when it happens. Never has affected playback yet.

I should check that Sonar is using all my cores. I believe that it is. With hyperthreading it shows 12 cores on my Sonar cpu indicator. My OS recognizes all 6 cores but it only posts 3.3 ghz , so this is apparently  just a posted stat since I have it overclocked to 4.4ghz. My bios shows 4.4ghz.Using Intel turbo boost my cpu might idle at 1ghz until I need it. I don't have it set to max all the time. 

 

 

Edited December 3, 2015 by starise