Sonar 5 and Win 7 - WaveProfiler doesn't work...

Hello everyone,
 
I'm back :p I've got Sonar 5 Producer Edition, and I have Windows 7 (64-bit). And I did install the 64-bit Sonar first, I was so delighted it had that! But it was a nightmare. It couldn't read its own template files, the menues were empty, it didn't let me enter the activation code, and yeah... so I uninstalled it and am using the 32-bit program, and yay, that works.
It's activated, it can read its templates, it has all menu options, it's great. Yeah. Only... I can't get the Wave Profiler to work, so it doesn't recognize my audio.
 
Basically what happens is that I click the Wave Profiler button, and I get the popup about changes only coming into effect after I exit and come back, and I click OK, and then a popup asking if I want to go through a few tests now. And I click Yes. And then nothing happens.
 
Then I usually exit, and try to open the program again and it does nothing. Well, I've now figured out that after exiting Sonar, it still hangs around the task manager, at slightly less memory usage (maybe 20% less). But I've left it for +10min and it has not closed itself down. Is that normal?
 
Anyway, so if I force-close it from there, then I can open it again. But then the same problem prevents me from making a test recording.
 
Stuff I've tried:
1.) The program is set to run in compatibility mode. At first it was XP (first 3SP, then 2SP), but now it's down to 98. That seems fine.
2.) I ran the compatibilty wizard in Windows, but that just asked me to set it to XP-2SP when I had it on XP-3SP and had no other info
3.) I set the SONARPDR to run Privilege level "Run this program as an administrator"
4.) I set the whole Cakewalk folder to Shared, with full rights, although I may have done that stupidly, as I also limited it to my own useraccount... :S not sure on this one.
5.) Oh, and I've tried this about 10-20 times in a row.
 
Now... I have an audio chip, I haven't even started with the USB Soundcard yet. I still think it should find a chip though.
 
Note: The PC and Windows are brand new, and I've already scan-disked and defraged and all that, it's all fine. And I still feel bad about upgrading Sonar from 5, because I like the older versions of stuff (hence I just got win 7, not 8, too).
 
Well, it IS an old product and I don't know if it's a very very long shot, but any ideas would be appreciated.
And if you think a chip would not be recognized, then alright, I'll wait until I've got the USB card set up.
 
Cheers!!! x

It's usually recommended you use a USB-soundcard with its native ASIO drivers, assuming such exist. And Wave Profiler does not work/isn't needed when ASIO drivers are used. MME drivers are the oldest and poorest there is, and seldom work properly in DAW work.
Anyway, good to hear you got things running!

@Kalle: Kiitos! I'll keep that in mind. But right now I am so very happy :) so I'll see how far I get with this. I have the C1 and I have an Audiophile, and some stuff. But I never loved anything as much as tiny soundcards that you can plug crappy mics and direct guitar cables into, and the lo-fi, nervy sound that comes out of them. It takes all sorts :)
 
@Cactus: Thanks for the warning, that may well turn out to be the case, but so far it's fine. And it's alright, as I said I have the bigger cards and stuff, but I didn't like using them at all.
And... sorry, but you don't know me. I know you're trying to be helpful, but if anything kept me from recording then it was me - my health issues and my financial issues. It's not the fault of software that was good enough ten years ago. I was good enough ten years ago, too. If it works, it works. I don't need new stuff, when I am still such a n00b at the old stuff. I never used more than 10% of what Sonar 3 could do, and am the same on 5. But those things I use, I love so much I want to stay with Sonar, and not move to any other DAW. Audacity is free. There are options. If I don't use them, it's MY fault, ultimately. Not the software. I haven't been trying this for 4 years. If I had got my stuff together, I could have had it working much sooner. TBH, I thought my post clearly showed the issue was 80% an ID10T mistake on my part.
A nice error message would have helped, but mainly I was wrong for assuming stuff was default and should work. Sonar 5 can't be blamed very much.

@Rbh: Thank you!! I'm glad you still like it, too, and that it's stable for you!! :)
 
WMD was the "default" / original setting that Sonar 5 opened with and that's where the WaveProfiler messed up when I tried to run it to pick up my audio device. After exiting the program, Sonar would still sit in the task manager as a running process, and it would block for opening the program again, until it was manually deleted from task list. So something went wrong there, and I don't know what, but I am not changing anything now, as long as things go this well. :) But thanks for the advice!! I'll keep that in mind, in case anything goes wrong. :)

Thanks spacealf!
 
Right, so I would like to know, since all of you always say you don't like MME, what exactly are the kinds of problems you can expect with drivers like this? Because any issues I do see, I blame fair and square on Windows 7, 64-bit Windows, Sonar and Sonar 64-bit. Issues such as on first install, Sonar 64 could not see / find its own templates, later Sonar 32 could not see / find some of its own audio files. Or the access violations in the Sonitus Reverb dll, on 32 bit.
 
But when I search for these issues online, I see people grappling with it for other versions, too, and I just think if 5 treats projects from 3 so badly, I don't know if I trust X3 as far as I could throw it to read projects from 3 properly.
 
I've been recording in Reaper and Audacity instead, and they just work. But then I miss the clear layout in Sonar, some nice effects and capabilities, and today I had the odd idea to install 64 bit as well as 32 bit, and today for some reason that works. I can open all my old songs again, no crashes, whether they have Sonitus effects on them or not. No matter that the dll is the same date in both version. IDK. But I don't think these are driver issues. Maybe I'm wrong...?
 
Every time I want to resign myself to reclaim my data from my old tracks (ah yes, back in the day when I didn't write s¤#t down and so I have no option but to listen and relearn, then note them down, now that I sorta can. I tend to just write write write.) and be done with it, I stumble over a nice, convenient thing in Sonar.
 
To be fair, if I've learned anything it's that I should definitely grab and run right NOW while stuff is working. Because next week some other setting has done something, and then it's all broken again. But I'm just messy. I just want to unload and then leave, with a free and simple mind :D and leave the noting down, sorting out, editing, producing, exporting, etc to another "day"...
 
/ramble
 
Very sorry. just been one of those days... (= _ . _ =)
 
P.S. WaveProfiler just run by itself *that* time :p when I installed 64bit version "on top" of 32bit (not literally on top, in it's own folder in the proper Program Files, not the x86 thingie which is much bigger btw... I def feel like I have the wrong computer for the stuff I want to do most.... ah, why can't everything old run as well as Tomb Raider...)

@sook: many thanks! I've got the MME 32bit setting, and so far it seems and sounds fine to me. Not sure if that is what you mean though. I'm still a bit of a n00b at all this. I do know how bad mp3s sounds compared to wav's but that's about it so far...
 
Regarding the other issue, when you say the high latency is needed to work for them, you mean that basically there is a lot of delay in recording? And stuff may get corrupted and so on, or just not time correctly? Because I have had issues like that on a different system, and I don't have them now at all - not with Sonar, nor with Audacity, nor with Reaper. Sonar though does on occasion mess up a little graphically, but fixes itself soon, and never affects the audio. Stuff I'm talking about is waveform was once missing but audio recorded fine and waveform returned once done; a row of copied clips once had a few holes in it, but played fine and the clips came back later, and dragging audio may appear in the wrong track, but if I don't fix it myself, Sonar fixes it soon. At the very least on next startup.
 
So far 64bit Sonar has only crashed once, and that was when I was adding, previewing, changing, deleting, and adding new effects while listening to a track. I think that's kinda stressful for a small DAW, but I've usually never had this issue with Sonar. Altogether it seems quite fragile and buggy, but this setup here seems to work best of all so far: 32bit installed but not used, 64bit installed and always used.
Only sucks to have fewer effects than 32bit...

@scook: Thank you so much for clarifying. That makes a lot of sense. To me that's a "nice to have" for now, but I know from video that bad drivers can cause crashes and bad behaviour, so I was wondering.
Good audio quality is obviously very nice. But I'm taking everything babysteps at a time, so it's fine for now.
 
Thanks again!!