darcyb62.
darcyb62Podium audio manager status report
Log period: 12/17/2006 3:37:42 PM – 12/17/2006 3:37:54 PM
ASIO device: Inspire 1394 ASIO Driver
– Supported clock sources: 000A9200E5091083 – MSU Synch Ou
– Current clock source: 000A9200E5091083 – MSU Synch Ou
– Supported sample rates: 44100, 48000, 88200, 96000
– Current sample rate: 44100
– Input channels: 4 (1111)
– Output channels: 2 (11)
– Input/Output latency, buffer size: 513/595, 441
– PerformanceCounter: 3579545 Hz
– ASIO sample types: 18, 18
End of report
ZynewaveDoes it crash if you switch to Wave drivers instead of ASIO?
Try to set up a track with a sound event, without audio inputs and plugins. Does it crash on playback?
darcyb62Wave drivers work…
If I go back to asio and drop in a sound event it crashes…
By the way… I might have a deeper problem with my system as suddenly I can’t get a network connection on my music machine…
I’ll have to spend a bit more time with it…
Darcy
ZynewaveBy the way… I might have a deeper problem with my system as suddenly I can’t get a network connection on my music machine…
I recommend you use a diagnostics tool to check your system. I once had a PC with a periodically faulty RAM block which caused me a lot of aggravation before I figured out it was a hardware problem.
darcyb62@Zynewave wrote:
By the way… I might have a deeper problem with my system as suddenly I can’t get a network connection on my music machine…
I recommend you use a diagnostics tool to check your system. I once had a PC with a periodically faulty RAM block which caused me a lot of aggravation before I figured out it was a hardware problem.
The system checked out okay so I have done a complete windows xp reinstall. I tried a repair 1st but that didn’t do anything.
So with a fresh windows install and with the only additions outside of windows being the Presonus Inspire drivers and Podium, Podium still crashes when I turn on monitoring.
I don’t understand this.
It worked before (but had an occasional problem starting podium), but now there is no chance.
I am going to continue loading the windows updates to see if that changes anything (need to get sp2 anyways).
If that doesn’t do anything I’ll see if I can find my firewire card for this notebook and try it on here.
Later…
Darcy
ZynewaveSo with a fresh windows install and with the only additions outside of windows being the Presonus Inspire drivers and Podium, Podium still crashes when I turn on monitoring.
Did you install the older driver that used to work with Podium?
Your report stated that you are using a buffer size of 441, which is kind of odd. If possible, try changing this to 256, 512, 1024 etc.
You could also try the ASIO4All driver, to check if you can use an ASIO driver at all with Podium on your PC.
ZynewaveOk, I’m pretty sure I found the problem. I made a temporary hack in the code to simulate a buffer size of 441 on my RME card (which normally only allows power of 2 buffer sizes). I got a crash in the SSE optimized code that calculates the meters, due to the buffer size being uneven. You must have used a different buffer size before you upgraded the driver?
I have inserted a check that skips the SSE optimizations on uneven buffer sizes. I’m about to send a 1.76 beta to you. Please report if this fixes your crash problem.
darcyb62I will give the beta a try when I get off work this evening, however I did see your response before I came into work and tried a few things.
The Presonus drivers don’t actually let you set the buffer size, you set the latency which I guess internally determines buffer size.
The default buffer size after an install is 10 ms which I had left in place when I tried the upgraded driver. When I reinstalled the old drivers the latency was left at the default 10 ms. When I rebuilt the system and reinstalled the original drivers the latency was left at the default 10 ms.
I remembered that I typically use a 3 ms latency setting and when I tried that, presto… it worked.
So I have gone through each setting on the card and checked to see what happened… Here are the results:
1.5 ms works
2.0 ms works
2.5 ms works
3.0 ms works
4.0 ms works
6.0 ms works
8.0 ms works
10.0 ms crashes
12.0 ms crashes
18.0 ms crashes
24.0 ms crashes
I’m not exactly sure what buffer size each latency setting translates to but if you want that I can run the report for each setting and post later today.
So I thin installed the newer driver and I get exactly the same results.
The good thing about this is that even though it was probably still working before, I have a very clean system now.
😉
darcyb62@Zynewave wrote:
Ok, I’m pretty sure I found the problem. I made a temporary hack in the code to simulate a buffer size of 441 on my RME card (which normally only allows power of 2 buffer sizes). I got a crash in the SSE optimized code that calculates the meters, due to the buffer size being uneven. You must have used a different buffer size before you upgraded the driver?
I have inserted a check that skips the SSE optimizations on uneven buffer sizes. I’m about to send a 1.76 beta to you. Please report if this fixes your crash problem.
This resolved the problem.
ZynewaveThis resolved the problem.
Excellent 🙂 . Sorry for the troubles it caused you.
darcyb62hey… no apologies required… just keep on developing this fine product… 😀
ConquistadorWow…glad to see a solution to this one. I had been following it closely but from a safe distance 😆
As usual a solution is found…keep it up Frits! 8)
darcyb62The side benefit to this is that by rebuilding the system, the performance of my system has improved dramatically.
It’s probably been a year since I built the system I was using and a lot of crap had accumulated on it.
I try a lot of different software/plugins and although a lot of them get deleted, they still leave fragments and they build up over time.
So what kind of improvement did I see? I cut about 1/3 off the time it takes to do an offline bounce.
I just have to clean up some of the plugin pointers and then I’m going to take an image and recovery should be easier next time.
Should probably dod something like this a couple of times a year.
ConquistadorI might do a clean install of Windows XP soon but with Vista on the horizon and Podium consistently performing so well ‘as is’ I might wait a bit longer. 😉
But yes a clean wipe can be a huge help. 🙂
darcyb62@Conquistador wrote:
I might do a clean install of Windows XP soon but with Vista on the horizon and Podium consistently performing so well ‘as is’ I might wait a bit longer. 😉
But yes a clean wipe can be a huge help. 🙂
I was thinking of giving Vista a test drive when I rebuilt but decided to hold off on it for awhile. There are some things I want to get done and I don’t really want to worry about any potential stability issues.