WIndows 7! Are there any issues?

[bboy_jon]

So I just purchased windows 7 (using my college email) but I am still a little weary on whether to use it yet or not. Is anyone having any driver issues with their recording hardware? Does reaper run well? I have a tascam us1641 and a line 6 toneport. Anyone using these with windows 7?

Thanks

[setvice]

I have it on a seperat partition using reaper with a tascam 1804. Almost everytime I use it it gives me the blue screen of death. It's not just with reaper tho. It does it in iTunes, vlc etc. It's listed as a legacy product on tascam website so they probably won't fix it.

[wallace]

I upgraded to home premium.
Not having any issues.

[bboy_jon]

What drivers do I use? Standard xp drivers or vista drivers?

[d.bop]

I'm using Win7 Professional x64 with ZERO issues whatsoever. I can't comment on support for your TASCAM though, but the Vista drivers should work fine.

[bullshark]

Window 7 pro x64 here and no issues to report. The hardware I'm using with it, Audiophile 2496 and FA-101, don't have drivers for it yet, but the Vista x64 work fine when installed in compatibility mode. Audio performance is actually better overall here than it was on XP.

I did have BSOD initially, but I've narrowed it down to virtual drive software(alcohol 52%, clone drive etc), once those(and my graphic card HDMI driver) were removed it was smooth sailing.

[SiKo]

Originally Posted by setvice

I have it on a seperat partition using reaper with a tascam 1804. Almost everytime I use it it gives me the blue screen of death. It's not just with reaper tho. It does it in iTunes, vlc etc. It's listed as a legacy product on tascam website so they probably won't fix it.

sorry to hear that.
maybe it is time for another sound card?

[pbk]

Originally Posted by setvice

I have it on a seperat partition using reaper with a tascam 1804. Almost everytime I use it it gives me the blue screen of death. It's not just with reaper tho. It does it in iTunes, vlc etc. It's listed as a legacy product on tascam website so they probably won't fix it.

Ha. Thanks for the laugh. That is so typical of Tascam. It should take them a while to spin-off a new Win7 driver for the 1804. I had to get rid of my 1641 since I never could use it reliably. Good luck!

[funkster1]

I just installed it 2 days ago (Ultimate x64). Since I skipped Vista, there's still a lot of getting used to. So far my drivers all seem to work OK (M-Audio Delta 1010LT, x64 beta driver from the M-Audio forum). Unfortunately I have already seen my first BSOD this morning (DRIVER_POWER_STAE_FAILURE) so I'll have to check from which driver this comes. I dn't really have time to test Reaper or any other music software yet.

Cheers,

Raphael

[Document02]

Running 7x64 Home premium, the only issue worth mentioning is the absence of official x64 drivers for my soundcard (TC Electronic), which are still in beta phase.

I believe most vista drivers work in 7, you might have to decompress the installer & tell seven to find the driver in the uncompressed files by itself.

Additionally on firewire interfaces, some problems may occur with the firewire drivers, which you have to switch to legacy mode.

[LCipher]

I have Win7 x64 oem sitting in a box, but am getting ready to give it a spin. Keep putting it off because I can't get info on what happens if I have to re-install.

With Win 7 - if you install on a HD to try, then authorize, then blow it away to install it again (same system of coursse, maybe *different* HD) do they make you jump thru hoops or is it easy re-authorization?

[bullshark]

Originally Posted by LCipher

I have Win7 x64 oem sitting in a box, but am getting ready to give it a spin. Keep putting it off because I can't get info on what happens if I have to re-install.

With Win 7 - if you install on a HD to try, then authorize, then blow it away to install it again (same system of coursse, maybe *different* HD) do they make you jump thru hoops or is it easy re-authorization?

last time I did this, I had to call to get the software authorized if I installed again within a three month period. That was XP thought, but 7 should be the same.

But don't you have ghosting software? That's what those programs are for, install Window, authorize it, then ghost it to any drive you want. I only install Window when I change OS nowadays, or there if there was a major service pack released.

[zappa]

No real problems for me runnin Win7 x64. Reaper itself runs fine, 32 or 64 bit versions. The only real issues so far as I know are:

1. Obtaining stable Win7 drivers for your audio hardware. Shouldn't prove too difficult with anything that isn't rare or legacy.

2. Plugins. Some plugins are designed for XP, and don't handle UAC too well. Usual workarounds are modifying a few file permissions, reg-key permissions, or if all else fails running reaper as admin temporarily to allow plugin registration at scan time. If all else fails you could turn UAC off, although I've not needed to do this, preferring to find a solution that works within 7's security model. I've only seen issues with a few plugins, including Waves (older waveshells), Kjaerhus (registry permissions) and Trilogy (file permissions). A good start is to add Users:Full Control to your vstplugins folder and contents.

3. Oddball issues. For example if running firewire audio hardware, you may need the Win7 Firewire fix to make your audiocard work properly (depending on FW chipset etc.)

z.

[Zacchino]

Windows 7 is a snappy and rock solid OS like Windows XP used to be (until my need for more CPU / Memory became an urge).

I first partitionned my HDD in half, made the new second partition Primary and Active, and I downloaded the Windows 7 Enterprise RTM (x64) 90 days Evaluation version just to try it out.

After a couple of weeks of testing, I decided to switch completely to Windows 7, so I bought the x64 Ultimate version, and upgraded it.

How did I upgrade a Beta ? Simple, In the registry, there's a fix explained here, then insert the DVD, right clic on the Setup.exe and in the Compatibility tab, specify to use the "Windows Vista SP2" compatibility mode. Run Setup.exe, and voila!

Now you can Upgrade your Beta to your Full working Windows 7 Ultimate. This trick might also work with just the "upgrade" cheaper) version of Windows 7... Not tested but I'm just assuming here.

BTW you guys will only need the Professional version. No use for the Ultimate version, I just bought that one because I thought the black color was cooler ^^.

After the installation, I just got my Windows 7 Ultimate full version running with NO issues, NO file duplicates, NO Registry messed up, just a clean, lean Windows 7 Ultimate.

So I went ahead and installed AAaaalll my plugins... Guess what ? Out of about 200, only 3 didn't work. Hopefuly I wasn't using them that much.

Reaper x86 has never been so happy on this new OS. Even Acid Pro runs smoother on Windows 7. But I can't say the same for x64 (it doesn't detect ANY of my Dx / VST effects, not even the Waves). But this is an issue exposed in another post.

[EvilDragon]

Yeah, I also figured that Professional is perfectly fine for DAW usage.

[shakey.oberon]

ultimate has the bit locker security thing, thats about it really

does everyone know that the student version of 7 pro is £30 at the moment, go find yourself a student mac user and use his college email to get yourself a copy!

[LCipher]

Originally Posted by bullshark

But don't you have ghosting software? That's what those programs are for, install Window, authorize it, then ghost it to any drive you want. I only install Window when I change OS nowadays, or there if there was a major service pack released.

Does that work? (why would they let it work? seems like a loophole). I would thing it would fail since you have a new machine ID.

Does this work for programs with challenge response?

My stuff is all legit - but I HATE having to find all the crap serials, etc each time I re-setup.

What ghosting software are you using? There are about 15 versions of Acronis, what else? Plus what to use for X64? What to avoid/watch out for?

[Zacchino]

Originally Posted by LCipher

Does that work? (why would they let it work? seems like a loophole). I would thing it would fail since you have a new machine ID.

Does this work for programs with challenge response?

My stuff is all legit - but I HATE having to find all the crap serials, etc each time I re-setup.

What ghosting software are you using? There are about 15 versions of Acronis, what else? Plus what to use for X64? What to avoid/watch out for?

It works, but some plugins have to be re-challenged/responded. If you have ACPI Enabled in your bios (which is nowdays always enabled), you can ghost to another machin with different hardware. Driver wise it will re-detect all the chipset, ethernet, etc automatically.

I've done this once when changing my Motherboard. It worked like a charm.

[winbe]

Hello there,

I upgraded to Win7 x64 from a XP SP3.
This is just excellent! More responsive, and the interface is efficient.
Only problem: no 64bits drivers for the 2x2 MIDIport from MAudio !!

I use the Window7 beta drivers for my Delte66, no problems.

The only problem I have.. is with EpicVerb from Bootsy. I don't know why, this is the only VST that now does not work any longer. Oh, it does work, but after two seconds it enters a feedback loop and reaches ultra high levels above +400DB. Too bad, so I switched to MoVerb.

Apart from that, I could not go back to XP SP3 !!

[bullshark]

Originally Posted by LCipher

Does that work? (why would they let it work? seems like a loophole). I would thing it would fail since you have a new machine ID.

Does this work for programs with challenge response?

My stuff is all legit - but I HATE having to find all the crap serials, etc each time I re-setup.

What ghosting software are you using? There are about 15 versions of Acronis, what else? Plus what to use for X64? What to avoid/watch out for?

If it's on the same machine, it will be the same machine ID; ghosting software make a bit for bit copy of your HD...

The only software that gave me problems was an Adobe program which had to be reauthorized after ghosting, but that's because I ghosted to a new hard drive; Window itself, Office, VSTs, Vegas etc had no problem with that, and the same Adobe software give me no grief when I ghost back to the same hard drive. I believe Adobe product use some kind of malignant rootkit, but for regular product from respectable companies there will be no such trouble.

I personally use Norton Ghost, a very old copy; There's probably better nowadays, but I have no trouble with it.

[setvice]

Originally Posted by SiKo

sorry to hear that.
maybe it is time for another sound card?

HAHA! Rent and food are a priority at the moment. Besides i actually quite like the 1804. I dont care too much about win7 as i have a very streamlined xp and i havent even come close to pushing the limits of my new(ish) quad core machine. Im just testing win 7 at the moment so its not a biggie.

I just tried the legacy firewire fix posted above so hopefully that will work.

[ThePulse]

I'm using it just fine without any issues what-so-ever. Check my specs.

[Broman]

Originally Posted by ThePulse

I'm using it just fine without any issues what-so-ever. Check my specs.

Have you ever had problems with crackling when recording? When I was testing the RC version it didn't seem to work too well with my Emu drivers.

[Cableaddict]

Broman,

I've gotten similar warnings from Lynx and Apogee. Definitely driver / buffer / DPC issues.
Upper-tier techs at both Asus and Intel have also advised me to stay with XP for the time being.

There are definitely unresolved issues that can affect SOME audio rigs.

Since I run two pc's, one only as a backup with exactly the same hardware, I plan on testing Win7 on my 2nd machine. Most folks probably don't have that luxury.

If you are a hobbyist, then go for it. If you are a pro, it might not be a wise move right now.
Unless you are desperate to allocate more than 3.25 GB of ram to your audio (as I am) then what exactly is the reason to switch?

[Deltones]

None so far. However, my Firestudio interface had dodgy drivers even in XP and of course, the situation is worse in Win 7. Had to do some gymnastics to make it work.

Oh and yeah, had to buy another midi interface because the great makers of the Midisport 1x1 don't want to update their driver for Win 7.

[musicbynumbers]

not ready to give my final verdict yet on performance with win7 64bit but have had some annoying compatibility stuff with wacom, lynx, behringer (bcf2000's working with bcfview) and my touchscreens.

Apart from this though it is a beast on a i7 with smooth graphic updates even at 90% usage at 64 buffer size. I think aero actually makes a big difference now and works as I can do all the fancy window hiding and tiling with no major cpu usage.

One thing though is that at that amount of usage I'm finding that it can take a sec or 2 for the song to actually respond again BUT ONLY after I press stop, before I press stop I can seek fast, zoom, scroll, switch screensets fine.

The delay seems to be tied into the "behavior" parameter on the buffering page in prefs.

anyone else seeing this or is this caused by a dodgy lynx l22 driver?

[DBMusic]

Running W7 Pro 32-bit here on a new i7 920 system I got from Jim Roseberry. Not a single issue so far...and I'm overclocking this baby to 3.20 GHz!

My interface is an RME AES-32 along with a couple of UAD cards (1 UAD-1 and a UAD-2). So far, things couldn't be better.

Regards,

DB

[jonathonbarton]

Originally Posted by bboy_jon

So I just purchased windows 7 (using my college email) but I am still a little weary on whether to use it yet or not. Is anyone having any driver issues with their recording hardware? Does reaper run well? I have a tascam us1641 and a line 6 toneport. Anyone using these with windows 7?

Thanks

I've been running 7 x64 since January 12, 2009 (3 days after the initial Beta was available from MS).
I haven't had a single issue with it in almost a year - with the sole exception being my installing the x64 version of Reaper, then wondering where all my 32-bit plugins were. *facepalm*