Zynewave.
duncanparsonsHi
I have an Alesis MultiMix 16 Firewire which is in good working order with the latest drivers.
Podium was working OK with it (after a fashion), but now I get the “could not initialize audio interface at 44100 Hz sample rate” box.
Because I always have a number of projects on the go, I don’t update my main machine terribly often, only when there’s something I NEED. So I’ve been running v1.80. I’ve updated and now running 2.38 (for some reason 2.39 wouldn’t download).
I’m still getting the same error. I’ve completely uninstalled the Alesis drivers & reinstalled. Same thing.
As I said, it was working, and the only thing that has happened in between is buying & attaching a new USB harddrive, something not generally known for upsetting audio.
Any ideas? I’ve tried using the Alesis Asio driver & Asio4All which both do the same thing; also the WDM driver which sucks – but this is more to do with WDM on this laptop than anything else.
I notice that this error has come up a couple of times in the forum, mostly referring to devices with fixed samplerates. The Multimix will work at 44100 and 48000. I have it set to use 44100 out of habit, but it happens whatever I use.
I’ve got the report Podium generates:
Podium audio manager status report
Log period: 16/11/2010 23:32:47 - 16/11/2010 23:33:58
ASIO device: Alesis Firewire
- Supported clock sources: Firewire
- Current clock source: Firewire
- Supported sample rates: 44100, 48000
- Current sample rate: 44100
- Input channels: 18 (111111111111111111)
- Output channels: 2 (11)
- Input/Output latency, buffer size: 340/328, 256
- PerformanceCounter: 3579545 Hz
- ASIO sample types: 18, 18
ASIO driver status:
- ASIOStart error: -1000
- ASIO reset requests: 9
- ASIO sample position gaps: 7 (256)
Audio stream buffer errors:
- Output buffer skip count: 7
End of reportWould it be an admissible thing to query the device and if it is using the samplerate that is desired, then don’t send that s/rate initialise call? It’s kinda annoying when my project is at 44100, the device is at 44100, and yet every 8-10 seconds or so I get this error as Podium keeps banging it’s head against a brick wall. I was using an Audigy PCMCIA card for a few years, which worked fine; but I am going to be needing the 16inputs of the MultiMix for some upcoming projects, and a resolution to this would be grand!
I have a demo of FL studio on this box, and it works flawlessly with any of the drivers. So far as I can tell, they query the device, and use that internally; when you choose a different samplerate for your project they internally resample. I’m not totally convinced this is a great idea, but it circumvents having to instruct the device what speed to run at – especially if it is already going at the desired rate.
🙂
DSP
LiquidProj3ctI’ve related problems with sample rate. If I save a project with my driver at 44.1kHz I cannot open it at 48kHz or viceversa (they’re MIDI projects!).
If I have my driver at 48kHz when I run Podium and I try to open a 44.1kHz project i get the “could not initialize audio interface at 44100 Hz sample rate” box. Then I change the driver and Podium samplerate to 44100Hz, I try to play the project and I cannot 😯
Once they’ve changed I must restart Podium and it works with 44.1kHz. If I want to open another samplerate project I must change the driver&Podium samplerate and restart Podium.
Zynewave@duncanparsons wrote:
Because I always have a number of projects on the go, I don’t update my main machine terribly often, only when there’s something I NEED. So I’ve been running v1.80. I’ve updated and now running 2.38 (for some reason 2.39 wouldn’t download).
1.80 is almost 4 years old :shock:. A lot of things have happened since then. I’d prefer not to backtrack my code changes for 4 years, to try to determine which update may have changed this behaviour.
I just tried downloading 2.39 and had no problems. Maybe just try again?
Does it show the error dialog also when using ASIO4ALL and Wave drivers?
duncanparsonsSorry for the delay in getting back – had to ahve my developer hat on for the last week.
@Zynewave wrote:
@duncanparsons wrote:
Because I always have a number of projects on the go, I don’t update my main machine terribly often, only when there’s something I NEED. So I’ve been running v1.80. I’ve updated and now running 2.38 (for some reason 2.39 wouldn’t download).
1.80 is almost 4 years old :shock:. A lot of things have happened since then. I’d prefer not to backtrack my code changes for 4 years, to try to determine which update may have changed this behaviour.
yeaaahhh… I have been using more recent versions for tinkering on other machines, but I just had a number of incomplete projects, and long times spent between doing music.. and a whole load of excuses, really!
@Zynewave wrote:
I just tried downloading 2.39 and had no problems. Maybe just try again?
Thank you, yes, I have it now. Must just have been some problem in the ether at the time I was trying to get it.
@Zynewave wrote:
Does it show the error dialog also when using ASIO4ALL and Wave drivers?
Using raw WDM is a nightmare, but that’s just my laptop.
ASIO4ALL performs better, I don’t get the samplerate error. There’s glitches (even with larger buffers), but of the 16 inputs the MultiMix has, only 8 are exposed by ASIO4ALL.
I’d really like to be able to use Alesis’ driver since it gives me all that the device has to offer.
I have a band session tomorrow, for tracking I’m going to revert to nTrack just to get the wavs and mix later. But I’d like to have everything in Podium. Is there anything I can do to help with this? Debug version, etc?
Thanks
Duncan
Zynewave@duncanparsons wrote:
Is there anything I can do to help with this? Debug version, etc?
I imagine I could spend several days trying to figure out what the problem is with the MultiMix device. I’d rather spend that time implementing support for the new Windows Vista/7 WASAPI audio driver model. Which Windows version are you using?
If I can avoid it, I prefer not to mess with the ASIO driver handling, as there is a real chance that changing the behaviour to suit MultiMix would break compatibility with other devices.
duncanparsonsthat’s fair enough 🙂
I’m using XPSP3 in general, but for my work with GForce I have VMs of W7 x86 & x64 for testing [the Steinberg VSTBridge for running x86 plugins in x64 Cubase is a nightmare, esp on W7!]
I know what the problem is with the MultiMix – the samplerate is ‘fixed’ by the driver either at 44100 or 48000; there is an Alesis control panel applet that sends the control signal to the device/driver to set it. I’ve never needed to look at the initialisation procedures of ASIO, so can’t speak for certain, but can it be initialised passively, as in accept the samplerate it is set at, rather than informing it what to be set at?
I’ll have a poke about with the SDK.. I might write an intermediary driver
🙂
DSP
ZynewaveFrom your report: ASIOStart error: -1000
-1000 is an error code for “hardware input or output is not present or available”.
So it’s not certain that the problem can be fixed by simply not setting the sample rate. Since your report does not show errors for “ASIOSetSampleRate” or “ASIOGetSampleRate”, it would appear that the driver did not report problems when setting up the sample rate.