The simple reason is that the Revo 7.1 is not supported.

@Raziel
That subvendor ID is in because I just copied the header file of the driver source code to the Mixer source code when I created Mixer.

Note that vendor and device ID is not the same as subvendor ID. There are many Envy24HT chips out there which have a vendor ID of 0x1412 and a device ID of 0x1724, but that's just designating the audio controller chip used, in this case the Envy24HT. The subvendor ID's define which particular model the card is (M-Audio Revo 5.1, 7.1, Julia etc.).

@mechanic

A hd-audio chip.

I assume/remember that AHI drivers set their PCM volumes to 0dB. If not, they should have done so at least.

Reading values from Mixer.prefs in an AHI driver would be even better and would be a first bridge between AHI and Mixer.

Good job! Everytime I read about Mixer improvements I'm so happy I released the source code! It might not be much, but I'll be releasing Audio Evolution 3 source code soon as well.

Don't know what you need to fix in the drivers btw, but ask ssolie for them.

Even if I would be willing, the non-Amiga projects take up all of my time currently and in the coming months that it is unlikely to happen.

The problem that one needs to care about PCI voltage these days is just silly of course, but I'm afraid that's how it is.

@328gts

Mixer does not use AHI, so it looks for devices itself. Since cs4281 is probably earlier in the list than the Revo, it comes up with that.
This is the explanation at least, there is no fix right now unfortunately.

Just a short note: when I wrote the driver, I had the same controller chip on a PCI card and am quite sure that recording was working with line-in and mic-in then.
I haven't had the ability to test it on my SAM by absence of the audio break-out board that was planned.

@DaveP

I'm with you when A-Eon contacted the press themselves, but did they? Or were they just around for the vintage computer fair anyway?

@DaveP

Ok, still they can either
A) release it as fast as they can and people can buy a faster machine with PCI-express (and hopefully less buggy than the A1!) and enjoy that now while they wait for all functionality to become unleashed or
B) wait for a long period (years?) until they have everything in place to make full use out of the system (64-bit, SMP, XMOS, whatever)

I'm sure there will be more people who prefer A over B in this niche world.

@djrikki

I guess you're missing my point, but I'm not good at explaining.

What I meant was this: let's say you have a choice between:
A) processor at 800 MHz / 32-bit
B) processor at 1.2 GHz / 32-bit
C) processor at 2.0 GHz / 32- and 64-bit

And basically want the fastest processor, then you would go for option C and hey, if at any time in future there will be 64-bit, great! But for now it doesn't matter. Which is why I didn't understand DaveP's 'OS4 must have 64-bit in December or otherwise...'.

If there was a:
D) processor at 2.0 GHz / 32-bit and cheaper

Then I could imagine that people think option C is a bad choice for now.

Quote:
I don't think comparing AmigaOS to Windows or OSX is relevant. It's almost like you are saying that AmigaOS would be competition and that AmigaOS lost potential users when not going 64-bit anytime soon because other systems have it.

@DaveP

I kindof agree on the SMP part, but why should one care if the 64-bit is used? It's not like anyone is currently reaching the memory limits of 32-bit anyway on OS4.
Besides that, are there dual-core PPC processors available (!) that are equally fast, 32-bit and cheaper? If so, you have a point, otherwise they just went with the fastest one and got 64-bit capability as a 'bonus' which may or may not be used in future.

Quote:

I might be mistaken, but I have the feeling you are not familiar with wxWidgets. At least it has nothing to do with the 'widgets' you see on Vista and Windows7. wxWidgets is a multi-platform C++ toolkit for GUI, gfx, and a lot more.


@abalaban
Good to see you will be up and running again! :)

@328gts

Mixer works independantly of AHI, which causes lots of problems or at least can cause situations which cause confusion. Whether you install any AHI driver, Mixer searches for sound cards itself, so cs4281 will always show up and does not interfere with your M-Audio card.

What causes confusion is that Mixer, AHI prefs and audio apps can all change the output volume (usually the master output) independently and they will not notify each other.
When you start Mixer in user-startup, this will initialize AHI (which will set up some volumes according to the AHI prefs), then the Mixer.prefs will be read and executed (if not, it will fall back to defaults) and after that any app can change volumes.

If you think "what a mess!", then, yes, it is!

@RIBDEVIL

When you have installed the emu10kx drivers and the EMU10KX modes do not show up in AHI prefs, then your model is not supported. Please tell me what PCI vendor and device ID are shown in PCIView.

@Rigo

Mission critical or not, you can only write good software if you got the tools to do it, and one of those is an OS that helps you point out nasty things.
Even expert software developers make bugs hourly/daily. How do you know if you write good software if nothing is saying that you are? For example, before OS4, you could happily write to address 0 and not be notified and you would think you wrote good software. Now with OS4 you are immediately reminded that you didn't write good software at all.

@Rigo

Quote:

Sorry to disagree here Rigo, but that's just nonsense. If your OS stops you from doing bad stuff outside your memory range etc., the developer will see it immediately during debugging/development. If the OS does not have such feature, the developer won't always notice and the bug appears only for other users, making it hard to track down.
The OS should do everything and I mean everything to prevent taking down the system.

@JosDuchIt

If you don't have sound at all, it's best to start without Mixer running. First thing we need to know if the CS4281 audio mode shows up in AHI prefs at all.

If that is the case, make sure that the frequency is 44100 Hz and the volume is 0dB for all units (music unit and unit 0-3). Make sure the CS4281 HiFi Stereo++ mode is actually selected for every unit too. Press the 'test sound' button to see if anything happens. Save the settings in either case.

If still no sound is coming out of it, I'd like to know if you connected your (amplified) speakers to the rear outputs of the motherboard directly, or if you use another output, like for instance a front case output.

@tonyw

Exactly. People forget the difference between an employee and a contractor. With this supposed scheme you'd need a contractor since otherwise you need to employ someone and arrange for his medical, pension (dunno if this is what's called in English!) etc. A contractor would need to have an hourly rate of 3 to 4 times an employee rate, so you'd need about 10 to 16000 euro a month and that translates to even more in USD.

Forget this idea, just use plain bounties.

This is a recurring subject it seems. It's my opinion that applications shouldn't use AHIC_OutputVolume for changing volumes. I've talked to the Tunenet author some time ago, and he said Tunenet wasn't using this at all. So I don't really know what can cause this.

@freddix

if ( ObjectID >> 0 ){

should be >= 0 I think.