• SONAR
  • Sonar 5 and Win 7 - WaveProfiler doesn't work...
2014/02/28 11:36:42
Spacecat
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
2014/03/01 03:21:29
Spacecat
YAY!!!!!
It works :)
 
So, under Options - Audio, I clicked onto the "Advanced" tab, and selected Driver Mode "MME (32bit)".
 
The Wave Profiler ran successfuly. Then I exited as told, and Sonar also closed properly and didn't hang around in task manager like unfinished business :)
On next startup, Wave Profiler ran tests again (not sure why, but hey...) successfully, and recording is FINE now! Whee!! ♥
 
One small hiccup on the first attempt to record, but only graphically (waveform stopped dead) the recording continued well. That didn't happen again, so no biggie.
 
Anyway, it seems like the issue was just that I expected the options that programs start up to work - maybe not perfectly, but reasonably anyway. I kinda see them as default. And this isn't helped by the absence of error messages when things go wrong. An error message / status indicator would *really* have helped here, instead of operations just dissipating into the void :D
 
In Audacity, I had an error saying it could not find the input, but I was told to check the devices in specific sections of the program, which eventually did it (Edit - Preferences -> "Devices" selecting own stuff for Playback and Recording). I did have to find that are first, so that could have been much clearer, but at least there was an error, and not just... Mind you, Windows 7 is partially to blame I suppose, and really this is more of a philosophical issue now. Moving away from error messages that can be used for something is ever more unfashionable I suppose. Someone somewhere thought it was more "polite" to hide all that mess from the poor end-users, and I guess it caught on... ;)
 
Anyway, for what it's worth. I also checked these items under the "Advanced tab" in Sonar's Options - Audio:
- Share Drivers with other programs
- Use Multiprocessing Engine
- Always Open All Devices
 
and under Synchronisation: Trigger & Freewheel.
 
I have no real idea if these help, but I thought it could not hurt, and just wanna mention them, in case they were important. (I have no idea what a word clock is, but I don't have MIDI devices at present, so the default option "Full Chase Lock" seemed to not matter...)
 
Anyway, there you go. I'm EXTREMELY happy now. I know this entry hasn't got any replies yet, but I've had a bunch of help in other threads before, so wanna say THANKYOU to you guys again!! Have a Good Weekend!!! ♥
2014/03/01 08:55:08
Kalle Rantaaho
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!
2014/03/01 12:18:57
Cactus Music
Look at all the time you just wasted when you could have been recording.
 
You first posted this I see in 2010 and 4 years later you still having issues..
For a little bit of money or free when you buy an audio interface you'll get a proper version of a DAW software that was made to run on W7 64 bit. You really are wasting your time trying to use 10 year old software and an on board sound card. It will be full of glitches and I even doubt the sync will be very good, your recordings will not line up etc. MME mode is not at all that good for multi track work. It works fine for 2 track work like with Audacity or Windows Media Player. 
 
 
Not to mention how far Sonar has progressed. I opened Sonar 7 the other day and I could not believe how much was not included back then. No way I could work like that anymore. 
2014/03/01 13:30:10
Spacecat
@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.
2014/03/02 22:21:35
Rbh
Try selecting WMD drivers instead of MME. They are capable of nearly the same performance as ASIO drivers and are very stable compared to MME.
 
I'm still using sonar 5 with an XP system, rock solid.
2014/03/03 09:49:32
Spacecat
@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. :)
2014/03/06 18:56:38
spacealf
WDM/KS are the Windows drivers and if you had the inputs and outputs marked in Sonar, I never had a problem with the Wave Profiler starting up, in fact it would do it automatically to test the sound card before being able to record.
MME is poor excuse for drivers but also can be used, but if the drivers for the soundcard are any good, then all of that should work with the Windows WDM/KS whatever drivers with no problem.
 
2014/03/07 12:18:58
Spacecat
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...)
2014/03/07 15:11:41
scook
There are two issues with MME drivers. The extreme latency needed for them to work properly and usually the drivers are restricted to 16bit audio.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account