Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[6233638]

Still getting that "format not supported by your hardware" error with ASIO playback at random.
I doubt anything has changed, but it's been a lot more frequent for me this last week, often happening several times a day now.

[6233638]

Very strange - I just got this error for the first time with WASAPI now, while playing audio to another device via ASIO.
 
Audio sent to that device worked perfectly fine in Windows, but it refused to play anything in Media Center.
When I stopped playback to the ASIO device, the WASAPI one worked.
When I tried to play anything to the ASIO device after that, it gave me the "format not supported" error every time.
 
 
Restarted Media Center, and both devices work just fine. (for now)
Media Center is the only program this happens with.

[6233638]

Idle for another couple of hours, had to restart MC.
 

Code: [Select]

0003562: 7108: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
0003562: 7108: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using input format
0003562: 7108: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Applying output format settings
0003562: 7108: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 96kHz 32bit 6ch
0003562: 7108: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
0003562: 5792: Playback: CASIOPlugin::Open: Start
0003562: 5792: Playback: CASIOPlugin::Open: Starting ASIO
0003562: 5792: Playback: CASIOPlugin::StartASIO: Start
0003562: 5792: Playback: CASIOPlugin::CreateASIO: Start
0003562: 5792: Playback: CASIOPlugin::CreateASIO: Creating ASIO wrapper
0003594: 5792: Playback: CASIOPlugin::CreateASIO: Finish (32 ms)
0003594: 5792: Playback: CASIOPlugin::StartASIO: Starting ASIO for device: {B2D4D5A2-1B17-4AB6-8A6D-667095C480B2}
0003594: 5792: Playback: CASIOPlugin::StartASIO: ASIOInit(...) failed with code -1000
0003594: 5792: Playback: CASIOPlugin::StartASIO: Finish (result: 0) (32 ms)
0003594: 5792: Playback: CASIOPlugin::Open: Failed to start ASIO
0003594: 5792: Playback: CASIOPlugin::Open: ASIO result (0 is success): -1
0003594: 5792: Playback: CASIOPlugin::Open: Finish (32 ms)
0003594: 5792: Playback: CASIOPlugin::~CASIOPlugin: Start
0003594: 5792: Playback: CASIOPlugin::~CASIOPlugin: Updating plugins
0003594: 5792: Playback: CASIOPlugin::~CASIOPlugin: Deleting buffers
0003594: 5792: Playback: CASIOPlugin::~CASIOPlugin: Finish (0 ms)
0003594: 7108: Playback: CDXPlayerWindow::PrePlay: Finish (47 ms)
0003594: 7108: Playback: CDXPlayerWindow::ProcessMainThreadMessage: Finish (47 ms)
0003594: 872: Playback: CDXPlayerWindow::CPlayThread::Thread: Start
0003594: 872: Playback: CDXPlayerWindow::CPlayThread::Thread: Running graph
0003594: 872: Playback: CDShowFilterGraph::Run: Start
0003594: 872: Playback: CDShowFilterGraph::Run: Running graph
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 33024 (0x8100), 0, 2095938516.  Callback 0x7dae2ab0
0003594: 7108: Playback: CDShowFilterGraph::SetVolume: Start
0003594: 7108: Playback: CDShowFilterGraph::SetVolume: Finish (0 ms)
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
0003594: 872: Playback: CDShowFilterGraph::Run: Graph succeeded
0003594: 872: Playback: CDShowFilterGraph::Run: Finish (0 ms)
0003594: 872: Playback: CDXPlayerWindow::CPlayThread::Thread: RunGraph returned 0
0003594: 872: Playback: CDXPlayerWindow::CPlayThread::Thread: Finish (0 ms)
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 64023 (0xfa17), 0, 0.  Callback 0x7dae2ab0
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Unhandled DX event: 0xfa17
0003594: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
0003594: 7108: Playback: CDXPlayerWindow::ProcessMainThreadMessage: Start
0003594: 7108: Playback: CDXPlayerWindow::PostPlay: Start
0003594: 7108: Playback: CDXPlayerWindow::PostPlay: Updating play state
0003594: 7108: Playback: CDShowFilterGraph::SetVolume: Start
0003594: 7108: Playback: CDShowFilterGraph::SetVolume: Finish (0 ms)
0003609: 7108: Playback: CDXPlayerWindow::PostPlay: Updating status
0003609: 7108: Playback: CDXPlayerWindow::PostPlay: Finish (15 ms)
0003609: 7108: Playback: CDXPlayerWindow::ProcessMainThreadMessage: Finish (15 ms)
0003625: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
0003625: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 10 (0x0a), 70780800, 0.  Callback 0x7dae2ab0
0003625: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
0003641: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
0003641: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 14 (0x0e), 0, 0.  Callback 0x7dae2ab0
0003641: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Unhandled DX event: 0x0e
0003641: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
0003687: 7108: Database: CDataHolder::Load: Field: Date; Files: 54075; Pointer bytes: 216448; Data bytes: 49208; Elapsed ms: 2.446
0003687: 7108: Database: CDataHolder::Load: Field: Access Rating; Files: 54075; Pointer bytes: 26012; Data bytes: 16440; Elapsed ms: 0.794
0003687: 7108: Database: CDataHolder::Load: Field: Screenwriter; Files: 54075; Pointer bytes: 26012; Data bytes: 16440; Elapsed ms: 0.552
0003687: 7108: Database: CDataHolder::Load: Field: Budget; Files: 54075; Pointer bytes: 23708; Data bytes: 16440; Elapsed ms: 0.677
0004125: 7108: Playback: CDXPlayerWindow::LayoutWindow: Start
0004125: 7108: Playback: CDXPlayerWindow::LayoutWindow: Getting rectangles
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Start
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Native video size (1920, 1080)
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Window client rect (l=0, t=0, r=953, b=542)
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Original target rect (l=0, t=3, r=953, b=539)
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Deflate 0
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Target rect after zooming (l=0, t=3, r=953, b=539)
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Target rect after shifting (l=0, t=3, r=953, b=539)
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Source rect after cropping (l=0, t=0, r=1920, b=1080)
0004125: 7108: Playback: CVideoZoomControl::GetVideoRectangles: Finish (0 ms)
0004125: 7108: Playback: CDXPlayerWindow::LayoutWindow: Source: 0,0,1920,1080; Target: 0,3,953,539)
0004125: 7108: Playback: CDXPlayerWindow::LayoutWindow: Positioning video
0004125: 7108: Playback: CDXPlayerWindow::LayoutWindow: Success
0004125: 7108: Playback: CDXPlayerWindow::LayoutWindow: Finish (0 ms)
0004719: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
0004719: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 6 (0x06), -3, 2095938516.  Callback 0x7dae2ab0
0004719: 7108: Playback: CPlayerZone::JRPlaybackEngine_PlaybackError: Start
0004719: 7108: Playback: CPlayerZone::JRPlaybackEngine_PlaybackError: Error: Playback could not be started on the selected audio output.

The audio format may not be supported by your hardware.  You can use DSP Studio to change the output to a compatible format.

Also, make sure that your system has a valid sound playback device and that it is properly configured in playback options.
0004719: 7108: Playback: CPlayerZone::JRPlaybackEngine_PlaybackError: Finish (0 ms)
0004719: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 64023 (0xfa17), 1, 0.  Callback 0x7dae2ab0
0004719: 7108: Playback: CPlayerZone::JRPlaybackEngine_EndOfFile: Start
0004719: 7108: Playback: CPlayerZone::PlayNextFile: bCanPlayNext=0, m_bPlaybackError=1
0004719: 7108: Playback: CPlayerZone::PlayNextFile: Starting playback error thread
0004719: 7108: Playback: CPlayerZone::JRPlaybackEngine_EndOfFile: Finish (0 ms)
0004719: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
0004719: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
0004719: 7108: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
0004734: 7108: Playback: CPlayerZone::HandlePlaybackError: Start
0004734: 7108: Playback: CPlayerZone::HandlePlaybackError: Finish (0 ms)
0004734: 7108: Playback: CPlayerZone::Stop: Start
0004734: 6332: Playback: CPlayerZoneDisplayInfoUpdateThread::Thread: Finish (1359 ms)
0004750: 7108: Playback: CPlayerZone::Stop: Checking for not loaded playback engine
0004750: 7108: Playback: CPlayerZone::Stop: Firing stop to playback engine
0004750: 7108: Playback: CDXPlayerWindow::StopVideo: Start
0004766: 7108: Playback: CDXPlayerWindow::StopVideo: Finish (16 ms)
0004766: 6280: Playback: CDXPlayerWindow::Thread: Worker thread exiting
0004766: 6280: Playback: CDXPlayerWindow::Thread: Finish (1391 ms)
Other programs have no problem using ASIO at all.
In this state, I can play audio via ASIO to another device - at least until it happens with that one too.
 
It almost seems like Media Center has completely lost the ASIO device. If I click the "open driver control panel" button, I get an error saying: "The selected ASIO driver does not have a control panel."

[glynor]

That's frustrating.

When it is in one of these states, can you test the audio device in another application?  Even if it is just to open the ASIO driver control panel to see if it is there (and make sure it still shows as enabled/working in the Device Manager).

Assuming it isn't a more generic Hardware/Windows problem, I wonder if it has something to do with your Zone Switching rules?

[6233638]

When it is in one of these states, can you test the audio device in another application?  Even if it is just to open the ASIO driver control panel to see if it is there (and make sure it still shows as enabled/working in the Device Manager).

Works perfectly in another application when MC is in this state.

It's not possible that another application is taking control over the device either, since this ASIO driver appears to be non-exclusive, and when MC is in a working state, it is able to play while another application is sending audio to it.

Assuming it isn't a more generic Hardware/Windows problem, I wonder if it has something to do with your Zone Switching rules?

Next time it happens, I'll try disabling Zone Switch, though the zone it would have switched to was currently active.
 
I doubt it's a general hardware issue since I just added a new PCIe soundcard from another vendor and it's happening with that too. (actually, I tried two different cards from different vendors, and it happened with both)

[mwillems]

Works perfectly in another application when MC is in this state.

It's not possible that another application is taking control over the device either, since this ASIO driver appears to be non-exclusive, and when MC is in a working state, it is able to play while another application is sending audio to it.

I wouldn't make that assumption just because it sometimes works;  I've had a couple of ASIO soundcards that would only sometimes allow for non-exclusive playback.  The problem (for me) seemed most acute when the soundcard was the windows default (hence the destination for all system audio), but MC was also trying to engage with it.  Depending on the order of engagement it would work fine, but eventually I'd need to quit one or the other program outputting to the device.

So two suggestions:

1) If you haven't already tried it, can you try to prevent any other programs from outputting to the device (by making it non default, and also not using the WDM driver as the default temporarily) and see if it still errors? 

2) The two biggest offenders for non-exclusive access grief (for me) were browsers (flash plugins especially), and measurement software (Holm Impulse, REW, etc.).  So next time it happens, see if either closing your browser or blowing away the browsers plugin container in task manager helps at all.

I may be barking up the wrong tree, but thought I'd offer my own experience of similar errors.

[Hendrik]

Sounds to me like a driver problem, or a rather exotic configuration. I use ASIO every day without ever seeing such a message, and so do many more people I imagine.

In any case, the next version of MC will log the error string as returned by the ASIO driver when the init failed, maybe it'll tell us something more.
The -1000 error just means device not present, which could be all sorts of things.

[6233638]

Sounds to me like a driver problem

On three separate devices, from different vendors?

or a rather exotic configuration.

Connected DAC/Soundcard. Installed driver. Tried to play music/video in MC.

In any case, the next version of MC will log the error string as returned by the ASIO driver when the init failed, maybe it'll tell us something more.
The -1000 error just means device not present, which could be all sorts of things.

Thanks. I could maybe understand it if my USB DAC was doing this (though it's never given me problems before, and nothing has changed) but it's happening with both of the PCIe soundcards I've tried as well.

I wouldn't make that assumption just because it sometimes works;  I've had a couple of ASIO soundcards that would only sometimes allow for non-exclusive playback.

To be clear, nothing is normally sending audio to these devices, and this is happening when I don't have any other ASIO-capable programs running.
 
I only tried running another ASIO application to check whether the ASIO drivers were exclusive or not, and if that was maybe what was causing this. (it's not)

The problem (for me) seemed most acute when the soundcard was the windows default (hence the destination for all system audio), but MC was also trying to engage with it.

Windows audio gets sent over the NVIDIA HDMI connection, not to any of these devices.

1) If you haven't already tried it, can you try to prevent any other programs from outputting to the device (by making it non default, and also not using the WDM driver as the default temporarily) and see if it still errors?

It happens even if I disable the WDM drivers for the devices.
Thanks for the suggestions though.

[Hendrik]

On three separate devices, from different vendors?

Then a screwed up system?
You seem to be alone with this afterall. A fundamentl underlying problem would show up more often.

[6233638]

Then a screwed up system?
You seem to be alone with this afterall. A fundamentl underlying problem would show up more often.

I think a couple of people have reported similar things, but certainly not with this frequency. It's only been recently that it's become such a problem now.
Hopefully the additional logging will help find the cause.

Considering that ASIO is supposed to bypass Windows' audio engine, I'm not sure what could be interfering. I don't normally run anything that uses ASIO other than Media Center.

[mwillems]

Considering that ASIO is supposed to bypass Windows' audio engine, I'm not sure what could be interfering. I don't normally run anything that uses ASIO other than Media Center.

It may be a long shot, but I used to have an ASIO device disappearance problem with an M-Audio PCI card I had three years ago; the card as a whole would lock up occasionally such that the windows audio service needed to be restarted to get playback working again.  I followed a troubleshooting guide on M-Audio's website, and the root cause turned out to be (I am not making this up) that it shared an IRQ with some other peripherals and the card would flake out.  The solution was (again not making it up) to turn off the onboard audio in the BIOS, and seat the M-Audio card in a different PCI slot, because windows wouldn't allow for manual IRQ reassignment (unlike the old days).  I thought the era of hardware caring about sharing IRQs was long gone, but I guess not (or at least it was still going strong in 2011).

That's probably not your exact issue, but it does sound like you recently added some new hardware to the system which may be contributing to your increased rate of failure (you mention a USB device and two new PCI-E devices).  If that's the case, it might be worth:

1) trying some of the hardware in a different PC;
2) trying the existing PC with fewer sound devices; or
3) trying the existing hardware in the same PC but in different PCI-E slots.

[6233638]

Does 20.0.27 contain the additional logging features? I didn't notice anything different when looking over another log for this.
However, I did find something strange.
 
It has happened twice again tonight, and both times I was able to start playback again without restarting Media Center... by unlocking the split view.
 
 
Normally I use a split view where the left pane contains all of my zones, and the right pane contains all of my library views. And more recently since I've added a few more devices/zones, I locked that left pane, because it made things a lot easier to manage.
 
I did also test whether Zone Switch rules played any part of this, and they don't appear to.
I disabled Zone Switch and the errors persisted until I unlocked the view - even though I was already viewing the zone where the files were being sent anyway.
 
What I can't explain is why locking the view would cause an ASIO-related error, why the problem is intermittent, or how to reproduce it other than simply using MC for at least a few hours.
 
 
It's currently in state right now where I can play the currently selected item (a Blu-ray disc) when the view is unlocked, but I immediately get an ASIO error if I lock the view.
 
I don't know if it's related, or just a strange coincidence.

[glynor]

I don't know if it's related, or just a strange coincidence.

Sure sounds like a smoking gun.

Can you give us a run-down on what tabs you have open in the Locked view?  I know you run with a ton of tabs.  I don't think I've ever had more than 3 tabs open.  I suspect you're way outside the norm here, so a problem there may have never been exposed before (not that it shouldn't work as designed, just saying you're the guinea pig).

[6233638]

Sure sounds like a smoking gun.

Can you give us a run-down on what tabs you have open in the Locked view?  I know you run with a ton of tabs.  I don't think I've ever had more than 3 tabs open.  I suspect you're way outside the norm here, so a problem there may have never been exposed before (not that it shouldn't work as designed, just saying you're the guinea pig).

Currently: 7 zones (all playing to local devices), a "recently played" playlist, and Media Center's "downloads" view. (from services & plug-ins)
 
I closed all other tabs so that only the current video zone was open in the left pane when creating the log though.

[6233638]

Well I'm thinking that may have been a very strange coincidence earlier - even though it happened three times, and the third time toggling the option repeatedly caused playback to work or not.
 
It's happened again and this time I had to restart MC.
Rather than being after a couple of hours idle, it was after an hour-long TV show, trying to start the next episode. (two-parter in a playlist)

[glynor]

Okay.  I still think the fact that you could "bring it back to life" with the Lock toggling (and re-break it) is really suspicious that it has something to do with your multiple tabs.  And I wonder if something in the tabs system is keeping some zone active that shouldn't be (or maybe partially) and it is borking the whole thing up.  Maybe you only got into that place where you could "save it" the one time randomly, but it still could be related that it breaks when using MC with all sorts of Playing Now views open at once.

So...  As a test, can you try running MC for a while with no split views and no tabs (like an animal) and see if the problem goes away?

I'm willing to try recreating your setup a bit, but I don't have any machines with that many zones, so I'm going to have to fake things, and it might not work the same (and I might not replicate your setup anyway).  But, if you can definitively link the weird behavior to the split view and/or tabs setup you got going there, then that would be a huge clue.

[6233638]

It couldn't hurt.

[glynor]

It couldn't hurt.

Well, it could. 

with no split views and no tabs (like an animal)

[Hendrik]

Does 20.0.27 contain the additional logging features? I didn't notice anything different when looking over another log for this

It does, but the driver only has an empty error message, so no luck there.

[6233638]

Well, it could.  

Haha, very true.


Well keeping Media Center restricted to a single tab, rather than a split view with a lot of tabs open, has just let about 9 hours of video (25 minutes each) play back-to-back without interruption which is the longest it's worked for weeks now.
 
Usually I'm lucky to get two hour-long TV episodes to play back-to-back.

[6233638]

Well maybe ZoneSwitch also plays a part?
 
Started playback of a Blu-ray in the wrong zone by mistake (my stereo one rather than multichannel) and immediately received the "format not supported" error when ZoneSwitch kicked in.
Started playback in the correct zone (again, with only a single tab open) and it worked correctly.
 
 
So it's probably a combination of the above:

• Multiple zones open in tabs
• Zones open in a locked split view, preventing the view from changing
• ZoneSwitch trying to change the currently open tab when a video starts playing

I don't know why it's resulting in an ASIO error, but it doesn't actually seem that the ASIO driver is at fault?

[6233638]

Well two days of using Media Center in a single pane, single tab way, with it automatically switching to Playing Now when I start video playback has not given me a single error yet.
Though Glynor was right, and I am hating using MC like this.
 
So I'm now fairly convinced that it is related to having a lot of zones open in tabs, rather than anything to do with the ASIO drivers for three separate audio devices.
 
I'm not sure where we go from here though, as the logs apparently don't show anything helpful (the previous log showed behavior with an error the first time, and then no error when I unlocked the split view) and it's intermittent rather than 100% reproducible - though it does seem to be happening several times a day now.

[6233638]

Another day, another 10 hours of video (25 files) played back with zero errors when set to a single view/tab, playing to a different ASIO device than the last one.
 
So it's clearly not the device or the driver at fault here.
  
What's interesting today is that rather than receiving an ASIO error, I received a general "something went wrong with playback" error the first time I tried to play anything after setting up the split views as before. Unfortunately, logging was not enabled at the time.
 
And after that error, any time I tried to play anything I received the "format not supported by your hardware" error, despite 10 hours of uninterrupted playback when it was confined to a single pane/tab.

[6233638]

Any suggestions for what I can do about this?
 
I haven't figured out a way to make it any more reproducible, other than having a split view where one is all Zones and the view is locked, with the other being Library Views.
Logs don't seem to show anything useful, so I haven't tried creating any more.
 
It seems that Media Center is not properly releasing, or somehow "losing track" of the devices, rather than it being the device driver at fault—especially since it's happening on three different devices, and three different drivers. (rather than separate devices which share the same driver and just rebrand it)
 
I would also add that I have all of the "Jump on play…" options disabled if that makes any difference.
Zone Switch did not seem to be the cause, but having Media Center switch zones did seem like it makes this occur more frequently.
 
Unfortunately, it sometimes happens within 30 minutes of launching the program, and sometimes it only starts happening after several hours.

[6233638]

A lot of the time I'm just getting silent errors now (file icon turns blue) and only on the third or fourth attempt to play something does Media Center present the "format not supported" error.

[glynor]

It might be useful to know exactly what the "tipping point" is where it goes from: MC handles split views/tabs fine to MC is broken with this number/configuration of split views.

Which will probably require some systematic testing on your part.

Basically, I think you're one of the only people on the planet who is using it in this way... I use split views and tabs occasionally, usually with one or two Playing Now windows open in tabs on one side, and views on the other, but never to the degree you do, and even then, only here and there when I'm DJ-ing.

I'd guess the most tabs/splits I've ever had open before was 4-6 total.  Maybe 5 (three tabs on one side, two on the other sounds like something I've used).

So... You're out in undiscovered country.  If you can show exactly where it breaks, I bet they'll fix it.  Otherwise, though... You're out in undiscovered country.  

[6233638]

Unfortunately I've had it happen with a 2-pane split with only one tab open in each, so it's not something as easy as saying "once you go over 10 total tabs, things start to behave unpredictably".
I've been doing a lot of testing, but I can't find anything which can reproduce this with any consistency.

[6233638]

Well I've been running without Zone Switch for a week (which was awful) and I seemed to encounter significantly fewer playback errors - though it did still happen a few times.
 
I re-enabled Zone Switch with some very basic rules (based on the Media Type and number of channels) and almost immediately started seeing "format not supported" errors with a much higher frequency.
 
 
I'm finding that MC doesn't seem to be creating logs for me at all once I have reset the log now, unless I restart the program - I just get zip files that contain nothing but "System Info.txt" which is no help.
 
And since restarting MC often seems to prevent this from occurring, it means I have to sort through log files which are absolutely massive in size. Off-topic, if anyone has any recommendations for editors that can handle text files which are hundreds of megs, if not a gig or two in size, I'd appreciate it. I've been using Sublime Text and it's okay once it loads in, but it seems like there must be something better for it.
 
The logs seem to be a little more detailed now, though I'm not sure that they're any more useful than before:

Code: [Select]

20431047: 5440: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
20431047: 5440: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using input format
20431047: 5440: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Applying output format settings
20431047: 5440: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 192kHz 32bit 2ch
20431047: 5440: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
20431063: 2508: Playback: CASIOPlugin::Open: Start
20431063: 2508: Playback: CASIOPlugin::Open: Starting ASIO
20431063: 2508: Playback: CASIOPlugin::StartASIO: Start
20431063: 2508: Playback: CASIOPlugin::CreateASIO: Start
20431063: 2508: Playback: CASIOPlugin::CreateASIO: Creating ASIO wrapper
20431078: 2508: Playback: CASIOPlugin::CreateASIO: Finish (15 ms)
20431078: 2508: Playback: CASIOPlugin::StartASIO: Starting ASIO for device: {786D9225-743E-4ABB-8FB7-1462B2758205}
20431078: 2508: Playback: CASIOPlugin::StartASIO: ASIOInit(...) failed with code -1000 and message "No device is connected to the PC."
20431078: 2508: Playback: CASIOPlugin::StartASIO: Finish (result: 0) (15 ms)
20431078: 2508: Playback: CASIOPlugin::Open: Failed to start ASIO
20431078: 2508: Playback: CASIOPlugin::Open: ASIO result (0 is success): -1
20431078: 2508: Playback: CASIOPlugin::Open: Finish (15 ms)
20431078: 2508: Playback: CASIOPlugin::~CASIOPlugin: Start
20431078: 2508: Playback: CASIOPlugin::~CASIOPlugin: Updating plugins
20431078: 2508: Playback: CASIOPlugin::~CASIOPlugin: Deleting buffers
20431078: 2508: Playback: CASIOPlugin::~CASIOPlugin: Finish (0 ms)

[JimH]

vi is always a good choice.

[glynor]

Notepad++ is always a good choice.

T,FTFY.

For OSX, TextWrangler.

[6233638]

Slightly different error when playing to another device:

Code: [Select]

16282234: 8164: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
16282234: 8164: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using input format
16282234: 8164: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Applying output format settings
16282234: 8164: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 96kHz 32bit 6ch
16282234: 8164: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
16282250: 8676: Playback: CASIOPlugin::Open: Start
16282250: 8676: Playback: CASIOPlugin::Open: Starting ASIO
16282250: 8676: Playback: CASIOPlugin::StartASIO: Start
16282250: 8676: Playback: CASIOPlugin::CreateASIO: Start
16282250: 8676: Playback: CASIOPlugin::CreateASIO: Creating ASIO wrapper
16282266: 8676: Playback: CASIOPlugin::CreateASIO: Finish (16 ms)
16282266: 8676: Playback: CASIOPlugin::StartASIO: Starting ASIO for device: {B2D4D5A2-1B17-4AB6-8A6D-667095C480B2}
16282266: 8676: Playback: CASIOPlugin::StartASIO: ASIOInit(...) failed with code -1000 and message ""
16282266: 8676: Playback: CASIOPlugin::StartASIO: Finish (result: 0) (16 ms)
16282266: 8676: Playback: CASIOPlugin::Open: Failed to start ASIO
16282266: 8676: Playback: CASIOPlugin::Open: ASIO result (0 is success): -1
16282266: 8676: Playback: CASIOPlugin::Open: Finish (16 ms)
16282266: 8676: Playback: CASIOPlugin::~CASIOPlugin: Start
16282266: 8676: Playback: CASIOPlugin::~CASIOPlugin: Updating plugins
16282266: 8676: Playback: CASIOPlugin::~CASIOPlugin: Deleting buffers
16282266: 8676: Playback: CASIOPlugin::~CASIOPlugin: Finish (0 ms)
16282266: 8164: Playback: CDXPlayerWindow::PrePlay: Finish (63 ms)
16282266: 8164: Playback: CDXPlayerWindow::ProcessMainThreadMessage: Finish (63 ms)
16282266: 5212: Playback: CDXPlayerWindow::CPlayThread::Thread: Start
16282266: 5212: Playback: CDXPlayerWindow::CPlayThread::Thread: Running graph
16282266: 5212: Playback: CDShowFilterGraph::Run: Start
16282266: 5212: Playback: CDShowFilterGraph::Run: Running graph
16282266: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
16282266: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 33024 (0x8100), 0, 2078769268.  Callback 0x5c019258
16282266: 8164: Playback: CDShowFilterGraph::SetVolume: Start
16282266: 8164: Playback: CDShowFilterGraph::SetVolume: Finish (0 ms)
16282266: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
16282266: 5212: Playback: CDShowFilterGraph::Run: Graph succeeded
16282266: 5212: Playback: CDShowFilterGraph::Run: Finish (0 ms)
16282266: 5212: Playback: CDXPlayerWindow::CPlayThread::Thread: RunGraph returned 1
16282266: 5212: Playback: CDXPlayerWindow::CPlayThread::Thread: Finish (0 ms)
16282266: 8164: Playback: CDXPlayerWindow::ProcessMainThreadMessage: Start
16282266: 8164: Playback: CDXPlayerWindow::PostPlay: Start
16282266: 8164: Playback: CDXPlayerWindow::PostPlay: Updating play state
16282266: 8164: Playback: CDShowFilterGraph::SetVolume: Start
16282266: 8164: Playback: CDShowFilterGraph::SetVolume: Finish (0 ms)
16282266: 8164: Playback: CDXPlayerWindow::PostPlay: Updating status
16282266: 8164: Playback: CDXPlayerWindow::PostPlay: Finish (0 ms)
16282266: 8164: Playback: CDXPlayerWindow::ProcessMainThreadMessage: Finish (0 ms)
16282281: 4004: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Start
16282281: 4004: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Using input format
16282281: 4004: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Applying output format settings
16282281: 4004: Playback: CAutoConfigureAudioOutput::GetOutputFormat: 96kHz 16bit 6ch
16282281: 4004: Playback: CAutoConfigureAudioOutput::GetOutputFormat: Finish (0 ms)
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 10 (0x0a), 70780800, 0.  Callback 0x5c019258
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 10 (0x0a), 70780800, 0.  Callback 0x5c019258
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 10 (0x0a), 70780800, 0.  Callback 0x5c019258
16282297: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
16282297: 8444: Playback: CASIOPlugin::Open: Start
16282297: 8444: Playback: CASIOPlugin::Open: Starting ASIO
16282297: 8444: Playback: CASIOPlugin::StartASIO: Start
16282297: 8444: Playback: CASIOPlugin::CreateASIO: Start
16282297: 8444: Playback: CASIOPlugin::CreateASIO: Creating ASIO wrapper
16282313: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
16282313: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 14 (0x0e), 0, 0.  Callback 0x5c019258
16282313: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Unhandled DX event: 0x0e
16282313: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Finish (0 ms)
16282328: 8444: Playback: CASIOPlugin::CreateASIO: Finish (31 ms)
16282328: 8444: Playback: CASIOPlugin::StartASIO: Starting ASIO for device: {B2D4D5A2-1B17-4AB6-8A6D-667095C480B2}
16282328: 8444: Playback: CASIOPlugin::StartASIO: ASIOInit(...) failed with code -1000 and message ""
16282328: 8444: Playback: CASIOPlugin::StartASIO: Finish (result: 0) (31 ms)
16282328: 8444: Playback: CASIOPlugin::Open: Failed to start ASIO
16282328: 8444: Playback: CASIOPlugin::Open: ASIO result (0 is success): -1
16282328: 8444: Playback: CASIOPlugin::Open: Finish (31 ms)
16282328: 8444: Playback: CASIOPlugin::~CASIOPlugin: Start
16282328: 8444: Playback: CASIOPlugin::~CASIOPlugin: Updating plugins
16282328: 8444: Playback: CASIOPlugin::~CASIOPlugin: Deleting buffers
16282328: 8444: Playback: CASIOPlugin::~CASIOPlugin: Finish (0 ms)
16282328: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Start
16282328: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 33024 (0x8100), 0, 2078769268.  Callback 0x5c019258
16282328: 8164: Playback: CDShowFilterGraph::SetVolume: Start
16282328: 8164: Playback: CDShowFilterGraph::SetVolume: Finish (0 ms)
16282328: 8164: Playback: CDShowFilterGraphNotifyWindow::OnDXEvent: Event: 6 (0x06), -3, 2078769268.  Callback 0x5c019258
16282328: 8164: Playback: CPlayerZone::JRPlaybackEngine_PlaybackError: Start
16282328: 8164: Playback: CPlayerZone::JRPlaybackEngine_PlaybackError: Error: Playback could not be started on the selected audio output.

The audio format may not be supported by your hardware.  You can use DSP Studio to change the output to a compatible format.

Also, make sure that your system has a valid sound playback device and that it is properly configured in playback options.

[6233638]

Well now I'm fairly sure that this is not an issue with ASIO, but something due to the fact that I use a split view with multiple zones open in tabs and Zone Switch.
 
Because ever since I got the WDM Driver working - and have set it as my default sound device - I've been getting similar "format not supported" errors for WASAPI sound devices as well.
 
More specifically, the device that the IPC Playback outputs to.
I occasionally have playback fail to start (silently) in my Video Zone which plays to that device even though there is a Zone Switch rule that should stop playback in my IPC Zone, and other times I get the "format not supported" error in the Video Zone.
 
This never happened until I started using the WDM Driver frequently.