Unable to open audio playback device.

Page: < 12 Showing page 2 of 2
Author
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 09:20:40 (permalink)
The device manager is in one of the first posts (Enheder til lyd, video og spil)


And a bonus (Ingen Lyd(ændret) = No Sounds (changed)):
post edited by RigPa - 2009/05/15 09:26:30
#31
WDI
Max Output Level: -54.5 dBFS
  • Total Posts : 2069
  • Joined: 2007/08/28 02:31:11
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 09:53:53 (permalink)
Sorry, not Device Manager. I meant Control Panel/Sounds and Audio Devices.

Like this...


post edited by WDI - 2009/05/15 09:54:27

Sonar 7 PE
Windows XP Pofessional (SP3)
MSI K8N Neo4-F
AMD Athlon 64 3500+
2 GB PC 3200 Ram
RME Fireface 800
Edirol FA-66
CM Labs MotorMix

Old stuff: ARJO
#32
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 10:05:50 (permalink)
I am afraid that is all I got. Vista is a little different than XP. It is actually Control Panel/Sounds.
post edited by RigPa - 2009/05/15 10:08:16
#33
WDI
Max Output Level: -54.5 dBFS
  • Total Posts : 2069
  • Joined: 2007/08/28 02:31:11
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 10:27:06 (permalink)
Oh, yeah, I don't know Vista or 64bit.

Could be Sonar, could be the plugs. I'm out of ideas. From what I've seen the Fireface looked synced correctly and configured correctly in Sonar. Wish I could of been more help.

EDIT:

ORIGINAL: Rigpa

The error does not show when only playing MIDI, but playing andiofiles with no plugins at 24/96 will also cause this error some times.


Well, looks like Sonar. Unfortunately, computers can be very difficult to trouble shoot. I had a mother board one time I couldn't get to work for the life of me.
post edited by WDI - 2009/05/15 10:30:25

Sonar 7 PE
Windows XP Pofessional (SP3)
MSI K8N Neo4-F
AMD Athlon 64 3500+
2 GB PC 3200 Ram
RME Fireface 800
Edirol FA-66
CM Labs MotorMix

Old stuff: ARJO
#34
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 11:05:36 (permalink)
Thanks all of you for the help. At this point it seems like every thing points to Sonar. I am also out of ideas and the only people who can debug deeper into this is Sonar. So I will make (yet another) error report and hope they will look into this, so I can get back in business again...
#35
Resonant Order
Max Output Level: -78 dBFS
  • Total Posts : 647
  • Joined: 2003/12/02 13:45:33
  • Location: Austin, Texas
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 11:20:09 (permalink)
The c0000005 buffer overrun error has nothing to do with Sonar. It's common in the new Play Engine for this to happen, and one of the reasons why Eastwest routinely deletes posts off the forum. The Play engine is buggy as hell. You should definitely stick to the NI engine if you want to use those samples.

Also, get a new midi interface. It's completely outdated. The Edirol UM series runs much better.
post edited by Resonant Order - 2009/05/15 11:29:44

"After silence, that which comes nearest to expressing the inexpressible is music." Music at Night, 1931- Aldous Huxley
#36
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/05/15 12:40:56 (permalink)
The C0000005 error is caused by the CPU trying to access memory in no where land. It is also called an Access Violation. The tricky job is to find the program that was using the cpu when it happened. Fortunately the eventlogger is very detailed. Here is a list with the exact programs that caused that violation on my DAW these few days:




Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, module error VPSoloDec.dll_unloaded, version 0.0.0.0, timestamp 0x44213591, exception error 0xc0000005, offset error 0x00000000392ae865, proces-id 0xe58, program start time 0x01c9d55b68a4e17e.

Program error iexplore.exe, version 7.0.6000.16830, timestamp 0x49ac913e, module error mshtml.dll, version 7.0.6000.16830, timestamp 0x49acafc4, exception error 0xc0000005, offset error 0x000a5277, proces-id 0x97c, program start time 0x01c9d4bf660cca25.

Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, module error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, exception error 0xc0000005, offset error 0x0000000000b4bc11, proces-id 0xa1c, program start time 0x01c9d4b33d2c8cd6.

Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, module error VPSoloDec.dll_unloaded, version 0.0.0.0, timestamp 0x44213591, exception error 0xc0000005, offset error 0x000000001000e865, proces-id 0x690, program start time 0x01c9d410acdd381f.

Programmet SONARPDR.exe version 17.3.1.372 afbrød kommunikationen med Windows og blev afsluttet. Hvis du vil se, om der findes yderligere oplysninger om problemet, kan du læse om problemets historik via kontrolpanelet Problemrapporter og -løsninger. Proces-id: 9f0 Starttidspunkt: 01c9d3ad5e4959a5 Sluttidspunkt: 29

Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, module error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, exception error 0xc0000005, offset error 0x0000000000b4bc11, proces-id 0xaf4, program start time 0x01c9d3a7c2d2be24.

Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, module error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, exception error 0xc0000005, offset error 0x00000000007fac94, proces-id 0xc4c, program start time 0x01c9d03e4cc37058.

Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, module error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b69bf7, exception error 0xc0000005, offset error 0x0000000000b4bc11, proces-id 0x6e0, program start time 0x01c9d03e01e15d48.

Program error SONARPDR.exe, version 17.3.1.372, timestamp 0x49b693f4, module error play_VST.dll, version 1.2.0.0, timestamp 0x49adf332, exception error 0xc0000005, offset error 0x0005d63c, proces-id 0x9dc, program start time 0x01c9cf69c1c6753b.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error play_VST_x64.dll, version 1.2.0.0, timestamp 0x49adf390, exception error 0xc0000005, offset error 0x000000000008446c, proces-id 0xee0, program start time 0x01c9cab350e62b78.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error play_VST_x64.dll, version 1.2.0.0, timestamp 0x49adf390, exception error 0xc0000005, offset error 0x000000000008446c, proces-id 0x2b0, program start time 0x01c9cab229607bb8.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error play_VST_x64.dll, version 1.2.0.0, timestamp 0x49adf390, exception error 0xc0000005, offset error 0x000000000008446c, proces-id 0xf50, program start time 0x01c9cab00363f978.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, exception error 0xc0000005, offset error 0x0000000000b4b601, proces-id 0x7c4, program start time 0x01c9c91259aec56b.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, exception error 0xc0000005, offset error 0x0000000000b4b601, proces-id 0xa8c, program start time 0x01c9c8fe39df9d3e.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, exception error 0xc0000005, offset error 0x0000000000b4b601, proces-id 0xf80, program start time 0x01c9c8fa408329ec.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a434cb, module error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a434cb, exception error 0xc0000005, offset error 0x00793f06, proces-id 0x87c, program start time 0x01c9c848d7315275.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, exception error 0xc0000005, offset error 0x0000000000b4b601, proces-id 0xca4, program start time 0x01c9c84837b5d685.

Program error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, module error SONARPDR.exe, version 17.3.0.367, timestamp 0x49a43b42, exception error 0xc0000005, offset error 0x0000000000b4b601, proces-id 0xbb8, program start time 0x01c9c847ddf882a5.



4 x PLAY

1 x Iexplorer

2 x VPSoloDec.dll (Vvocal)
1 x Sonar unspecified halt error
10 x Sonar Exception errors


That makes 13 out of 18 errors Sonar related

But strictly speaking it could be the OS kernel running tasks on behalf of the program that is running at that specific time. And dont mistake the timestamp for actual time, it is part of the version no.
post edited by RigPa - 2009/05/15 15:01:47
#37
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/05/16 09:06:00 (permalink)
So I tried just one last thing before going MAC - sorry MAD. I have 2 computers. A Dual Core running XP and XPx64 and Delta1010, and a Quad Core running Vista x64 and 2 x FireFace800.

I have this project that includes a PLAY instance and it will not play. On both computers it will not run and procduce this error: Unable to open audio playback device. I tried on the Dual Core to go back to Sonar 800 from 831 but still same error. A funny thing I noticed was that the CPU meter was jumping between 50 & 250% - how is it possible to perform 250% without OC'ing?

So I tried on the Dual Core to load the project in Sonar 7. THIS WORKED. The project plays beautifully. I went back to the Quad Core and installed Sonar 7 here. I loaded the project. And guess what. No problems. No bloody "Unable to open audio playback device error". Sonar 7 works....!!!!!

This fits pretty well into my earlier experiences with this error. I have had it for years, but upgrading to Sonar 8 made this error visible a lot more. After all it is an error that can be produced from a number of different situations.

I think that I have produced evidence enough now. I have been doing what CW should have done a year ago and after this I find it impossible to believe anything else than Sonar 8 is guilty as h...

If I bought a car that couldnt start I could get another or get it repaired or get my money back. But this is software and they just blame it on EW and third party plugs and maybe they even believe that they themselves are perfect and doesnt make mistakes... Now I will go back to Sonar 7 and and cry 5 minutes for all those wasted hours, days, weeks and months that I havent been able to make a decent income and then I will take it out on my punch bag for an hour or two... And after that I an going to work - making music to the world


Good Day to all of you.
post edited by RigPa - 2009/05/16 10:44:49
#38
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/05/16 14:43:22 (permalink)
Now I have been using Sonar 7 for ½ a day and the error does not show up any more.
I havent been able to work so long time without an error for a very long time.
In the beginning of this thread I mentioned that Sonar does not redraw.
This problem has also vanished completely with Sonar 7.
Guess that CW upgraded Visual Studio and .net since Sonar 7.

Sonar 8:

Look at the transport control bar:




Trying to open a project with only one button:




Just pressed Help:


post edited by RigPa - 2009/05/16 14:57:59
#39
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/06/03 18:00:53 (permalink)
I just got this mail from CW 2 days ago:

Thank you for contacting Cakewalk Technical Support. Thanks for the
files. Sometimes GUI problems like this can be caused by decimal
issues with international versions of Windows. A machine running on a
German or French version of Windows would expect a "," as a decimal
separator character. This can cause problems in SONAR and certain
plugins.

Here are 2 workarounds.

[1] Run the Windows Control Panel, and go to the "Regional and
Language Options" panel. Under the "Standards and formats" setting,
choose "English (United States)". This will cause numbers to formatted
and scanned in the way these plugins expect, but will
also cause times and dates to formatted for US English, which may not
be desirable. So you might want to try [2] instead...

[2] Again bring up the "Regional and Language Options" panel, but
click on the [Customize...] button, and make the following changes:

Decimal symbol: .
Digit grouping symbol: ,
List separator: ,


I made the changes and have been running for some time now

and it seems to work !!!!!!
#40
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
RE: Unable to open audio playback device. 2009/06/04 09:20:07 (permalink)
Well - sort of. To day im back in the old groove with crashes and errormessage. At least it worked for a day and it was relly nice having just one day with no crashes and I got a lot of work done....
#41
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re:Unable to open audio playback device. 2009/08/06 09:49:19 (permalink)
I have had these error for nearly a year now. Does CW have some kind of Tech Support any more? I havent heard from them in 2 months. Do they care at all? Or did I just waste my money on Sonar 8?
 
Am I the only one with this error on 4 different computers with 4 different operating systems and 4 different soundcards???
 
#42
CJaysMusic
Max Output Level: 0 dBFS
  • Total Posts : 30423
  • Joined: 2006/10/28 01:51:41
  • Location: Miami - Fort Lauderdale - Davie
  • Status: offline
Re:Unable to open audio playback device. 2009/08/06 11:20:16 (permalink)
Are they the same errors you listed about 10 post ago?? most of those errors looks like its due to a VSt plugin that does not like 64bit and or 64bit vista..
Cj

www.audio-mastering-mixing.com - A Professional Worldwide Audio Mixing & Mastering Studio, Providing Online And Attended Sessions. We also do TV commercials, Radio spots & spoken word books
Audio Blog
#43
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re:Unable to open audio playback device. 2009/08/07 05:10:57 (permalink)
I get this error in projects with no VST's at all and only a few tracks of audio, but the bigger projects are the more likely the error will come.  Using PLAY or True Pianos will make the error present sooner.

Sonar7 does not do this at all. It is only Sonar8. Projects 'damaged' by Sonar 8 will present the "Unable to open audio device..." error just by loading them (in Sonar 8). Sonar 7 loads and plays these projects with no problems at all and saving them with a new name from Sonar 7 and loading them in Sonar 8 makes S8 play them for a while - until the Exception error suddenly shows up - and it will show up eventually. Then the show starts all over...
#44
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re:Unable to open audio playback device. 2009/08/08 07:19:29 (permalink)
ok - 96 minidumps so far..... Just sent them to CW.
#45
Jeff Evans
Max Output Level: -24 dBFS
  • Total Posts : 5139
  • Joined: 2009/04/13 18:20:16
  • Location: Ballarat, Australia
  • Status: offline
Re:Unable to open audio playback device. 2009/08/08 08:28:14 (permalink)
Seeing as Cakewalk have mentioned language, was the good day running with Windows in English and the following day were you still in English.  Also I got this message a few times with the EMU 1212M. Have you got Patchmix installed and is everything set OK in there as well.
post edited by Jeff Evans - 2009/08/08 08:53:25

Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
 
Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
#46
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re:Unable to open audio playback device. 2009/08/10 07:37:51 (permalink)
Jeff Evans


Seeing as Cakewalk have mentioned language, was the good day running with Windows in English and the following day were you still in English.  Also I got this message a few times with the EMU 1212M. Have you got Patchmix installed and is everything set OK in there as well.

The language (Locale Setting) was a brilliant idea from Steve Cox. It didnt work though but I have seen other applications and setups (on SQL Server) with an exception error that got cured by switching the Country settings from DK to US ("." &",").  I still think that there could be something here. We are only 2 hand full of people in DK using Sonar so what are the chances that people in other countries run in to the same thing...
 
Yes I have Patchmix running OK (On DAW 3). In the beginning I had trouble understanding and using it, but now its a piece of Cake. Im actually very happy with 1212m - it sounds great
#47
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re: RE: Unable to open audio playback device. 2009/11/22 16:00:15 (permalink)
If you always run the same samplerate you will never experience this:

When loading a project Sonar 8 does NOT set the samplerate on the soundcard from the project sample rate. Sonar set the samplerate from Options/Audio/Default Settings for NEW!!! Projects.
If the Default Settings for New Projects doesnt match the loaded project Sonar produce 'Unable to open Audio Playback device...'
Sonar 7 does this correct from the project samplerate. Not from Default Settings for NEW Projects. Which is the correct way to do it.

Has anybody else experienced this?
#48
root
Max Output Level: -88 dBFS
  • Total Posts : 109
  • Joined: 2009/02/16 11:29:19
  • Status: offline
Same: "unable to open audio playback device" message 2010/01/16 16:33:28 (permalink)
RigPa...I'm getting the same message "Unable to open Audio Playback Device". Device may not support the projects audio format or may be in use.) then it diects me to support/hardwaresteup/ and it doesn't solve the problem.
Any luck with the problem? I'm running a .mov file with audio and was editing okay last nite (first time I've tried this) but today I can't get the audio to play.
root aka Bob G


Intel i7 920   6 Gigs triple channel Ram   Win 7 64   Sonar X1c  Layla 3G 


#49
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re:Same: "unable to open audio playback device" message 2010/04/02 14:03:34 (permalink)
Well sort of... I have this other thread that seems to be the same thing: http://forum.cakewalk.com/tm.aspx?high=&m=1812323&mpage=1#1909495

Be aware that there are multiple reasons for this error message. I think it all comes down to controlling the samplerate.

My first error report on this problem was Dec 5. 2008. I dont know how many times I have contacted TS, but it is a high number.

At last one year later Dec. 02 2008 I get a mail from CW admitting that they had been able to reproduce the problem and the status then changed to SUBMITTED TO DEVELOPMENT. It 'only' took me 1 year to convince CW. Nice.

That is 5 months ago so 6 days ago I wrote tech support asking if something happened. The answer was that they would look into the problem when they get the time (I guess that means never)...

I hope you found a work around. Mine is to use Sonar 7 - which has its issues too, and my old Tascam 38.


#50
Mark D.
Max Output Level: -88 dBFS
  • Total Posts : 122
  • Joined: 2007/10/23 23:19:37
  • Location: Massachusetts
  • Status: offline
Re:Same: "unable to open audio playback device" message 2010/04/02 14:38:15 (permalink)
I've seen this error before, rarely, and I know why every time. Sometimes I have Windows Media Player open playing a song & don't realize it when I open Sonar. Media Player playing a 16 bit 44.1 khz .wav will do that to the drivers. So will having iTunes open. But get this. Sometimes you close iTunes and it still has some way of keeping it at that rate since it runs other services.

Another cause is having the Internet open with a page that has ANY KIND of audio or video playing. Be it YouTube, or some site that's got a shockwave player going. Even if the song finishes playing, that player may be 'first in line' and keep Sonar from not only playing, but cause Sonar to do that 'reset' to a lower bit and sample rate.  It's often a matter of 'who gets there first' here.

Like we say in the world of IT I've worked in for years before, reboot. Open Sonar first (no Internet or Media Player or iTunes). If this fails, go into WDM mode and run our friend the good old audio configuration thing (who's exact name escapes me, that's not needed or clickable for AISO, but is for WDM) and that'll hopefully find the higher sample rates and let you run with it, from there.

Try this and see if it works. You may have to re-run that app every time you get this error. It's not perfect but it is a work-around. I'm not surprised at audio conflicts with so many things able to access audio. So I just roll with it. As far as projects or bundles not opening, those just might be ones you have that above 16 bit 44.1. See if those at 16 bit 44.1 open, while others (higher) do not.
 
www.westernmastering.com
#51
RigPa
Max Output Level: -82 dBFS
  • Total Posts : 437
  • Joined: 2006/06/15 16:27:47
  • Location: Denmark
  • Status: offline
Re:Same: "unable to open audio playback device" message 2010/04/02 19:42:29 (permalink)
Exactly. And only 1 type of soundcard with 1 driver. Disable onboard soundcard and ANY kind of mediaplayer.

And one last thing: Fix the samplerate bug.
#52
Mark D.
Max Output Level: -88 dBFS
  • Total Posts : 122
  • Joined: 2007/10/23 23:19:37
  • Location: Massachusetts
  • Status: offline
Re:Same: "unable to open audio playback device" message 2010/04/05 13:38:27 (permalink)
Just realized. You may want to be sure the 'share audio drivers' check box is checked off on page two of the audio options. That may allow it to run more friendly with other such audio programs. Though again, I have mine checked off and its only one at a time. Not a bother for me, usually that's fine, I don't need or want more than one thing playing.
#53
Page: < 12 Showing page 2 of 2
Jump to:
© 2024 APG vNext Commercial Version 5.1