|
Post by JohnnyBlue on Nov 1, 2011 21:51:23 GMT
Erm, seems like I was a bit premature with thinking it was all sorted. Just started up my PC again and the afore-mentioned error message has come back.
It only takes a click to get rid of it (and the blue M is still in the status window, despite it saying that MICyMon.exe isn't working, and the Monitor 02 is working properly), but I'd still like to find out what's causing the error...
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 2, 2011 21:06:02 GMT
Hi John, Javier.
Took the plunge and installed 026, nice to report that it is working fine.
Finally realised why my previous upgrades from 727 have all produced problems with clipping.
On the control panel, bottom right hand corner is the system volume control and mute button. On 727 the volume is set at around 5 o`clock on the volume dial, which gives maximum volume available, and if turned anti- clockwise gives a linear reduction in volume, down to zero.
This is not the case with 026.
To achieve maximum volume without clipping the dial needs to be set at 11 o`clock, any higher and the clipping becomes evident, something i am sure must have been the case with my previous upgrade problems, as i wrongly assumed the volume would be the same setting as 727.
So set at 11 o`clock on control panel, then using Amp to adjust listen levels of volume, this latest software works perfectly and sounds great.
Takes me a while, but i get there at some point in time.
Mick.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 2, 2011 21:21:31 GMT
Takes me a while, but i get there at some point in time. ;D ;D Well done Mick!!! Though I don't get why you need to have the volume on the control panel at 11 o'clock to avoid clipping, are you using ASIO?. My vol is at 5 o'clock in the Musiland control panel and Foobar's vol is also at max and I get no clipping whatsoever. Reducing volume in digital domain can mean loss of resolution unless very well implemented. I use the analogue vol pot of the HP amp exclusively.
|
|
|
Post by JohnnyBlue on Nov 3, 2011 7:15:40 GMT
Now I'm envious that I'm the only one who can't get a proper install of 1026! When I ran the 1026 exe file (after uninstalling the previous version and rebooting), then plugged in the 02, I got the (for me, now dreaded) message that the 02 firmware was installing, and not the USB/bus drivers. This is the same issue I had with the previous incarnations, except 0727. By manually installing the USB and bus drivers, in device manager, I can get the 1026 version to work, but I get the error message below every time I turn on my PC, which suggests that something is not right. Attachments:
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 3, 2011 8:22:04 GMT
John, as you are using Vista.. are you installing the drivers with administrator permissions?
|
|
|
Post by JohnnyBlue on Nov 3, 2011 10:12:50 GMT
Do I need to do this if I am already logged in as administrator? I didn't have this issue with 0727, but if you think it'll help with 1026, I'll give it a go.
(I presume this would mean uninstalling the existing 1026, then right-clicking the 1026.exe file and selecting run as administrator?)
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 3, 2011 10:57:19 GMT
If you are logged as an administrator there should be no need to do that but make sure you really have administrator rights. You can check it by opening a command prompt and typing:
control userpasswords2
That way you'll get the "good" account administrator window instead of the limited default one.
|
|
|
Post by JohnnyBlue on Nov 3, 2011 12:20:17 GMT
Doing that just confirms I'm an administrator: I couldn't find anything else there that I could mess with.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 3, 2011 12:35:24 GMT
Have you checked the Windows event viewer to see if it says anything about the error's cause?
|
|
|
Post by JohnnyBlue on Nov 3, 2011 13:24:44 GMT
Never heard of such a thing, but playing around with it, I found this about the MyCon (as well as about 200 about Google Update, which I have blocked by my firewall!):
Faulting application MlCyMon.exe, version 0.0.0.0, time stamp 0x4ea806a3, faulting module audioses.dll, version 6.0.6002.18005, time stamp 0x49e03703, exception code 0xc00000fd, fault offset 0x00009ef3, process id 0x430, application start time 0x01cc99f2351dcfae.
Or, in XML view:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-11-03T06:40:34.000Z" /> <EventRecordID>139794</EventRecordID> <Channel>Application</Channel> <Computer>John-PC</Computer> <Security /> </System> - <EventData> <Data>MlCyMon.exe</Data> <Data>0.0.0.0</Data> <Data>4ea806a3</Data> <Data>audioses.dll</Data> <Data>6.0.6002.18005</Data> <Data>49e03703</Data> <Data>c00000fd</Data> <Data>00009ef3</Data> <Data>430</Data> <Data>01cc99f2351dcfae</Data> </EventData> </Event>
Haven't a clue about any of the above. Event Viewer will keep me amused for hours. No wonder Vista is so bloated with all that info getting stored...
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 3, 2011 13:57:45 GMT
Oh! event logging has been going at least since Windows 3.1, Vista is crap but because of many other things. W7 is way better, in fact I have many 7 year old P4 PCs with only 1GB of RAM at work running it fine but with Vista it was mission impossible they became too slow. When I get home I'll check the versons you have against mine and see what I find.
|
|
|
Post by JohnnyBlue on Nov 4, 2011 11:04:53 GMT
Might have to go back to 0727: I've also just realised that the 1026 error also causes my 02 panel to reset itself to its install defaults every time I switch on the PC. Drat!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 4, 2011 11:32:38 GMT
Hi Javier, just bought Musiland Monitor 02 US. usb sound card for my elder son's Christmas. I know he will be well pleased with it and as it's a few weeks away till then I'll get to play around with it first. Although I'm working with Will's PK and not the 02 I've been following your thread with great interest......very informative over and above it's prime target. Regards, Alan
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 4, 2011 11:41:52 GMT
Hi Alan,
Needless to say that should you need any help with the drivers...
Will you be using XP, Vista or 7?
As good as the 02 is, I think a well powered PK with a USB->I2S adapter like Shaun's WaveIO will easily better it.
BTW, the 02 has a nice SPDIF output you can connect to the PK. Something else to play with and for free!.
Take care
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 4, 2011 11:47:35 GMT
Might have to go back to 0727: I've also just realised that the 1026 error also causes my 02 panel to reset itself to its install defaults every time I switch on the PC. Drat! One silly question John, after uninstalling the drivers, have you checked if there are any leftovers? I'd check in both the c:\program files\musiland and c:\windows\system32. Also check in taskmanager none of the MyMon... services are still running. Panel reseting was fixed in 1013.
|
|
|
Post by JohnnyBlue on Nov 4, 2011 14:58:01 GMT
Well, I'll be jiggered! Fixed! I checked for residual files after the uninstall: all cleared up, so no problem there. One last roll of the dice: I followed Javier's uninstall/install procedure, as opposed to the one on the HiFiDuino website and I also right-clicked the 1026.exe file "run as admin". Yeh! It has now installed the drivers properly (with no firmware driver, and no messing around in device manager). The only difference between Javier's and HiFiDuino's is the point at which one unplugs the 02, i.e., steps 2 & 3 are reversed. If I didn't want a life outside HPs/USBs/PC music I could easily try to see if it's that change or the "run as admin" that did the trick. I do, so I won't.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 4, 2011 17:41:09 GMT
Well, all is well when it ends well. Happy you fixed it John, congratulations! Now time to enjoy the 02. After the time it has taken Musiland to get this version right I think they will take a long rest before changing them again.
|
|
|
Post by JohnnyBlue on Nov 4, 2011 18:52:42 GMT
Hmmm, still getting the error message "MICyMon.exe stopped working and was closed" on re-booting the PC. (Foolishly, I assumed because the install had gone OK that now the drivers were loading properly.)
It's as if the Monitor Series (USB) Control Panel ("MICyMon.exe") is trying to run twice. Even though it says it's not working, it clearly is, because I'm getting the blue M in the system tray, a click upon which brings up the panel, and in any case it performs properly through Foobar...
EDIT: Discovered a work-around for the problem: I went into Services, right-clicked MUSILAND Monitor Series(USB) CPL Daemon, > Properties > General and selected Automatic (Delayed start). This now means that the 02 control panel is about the last thing to load on boot-up, rather than almost the first: seems to have done the trick (but don't hold your breath)!
EDIT 2: Having checked it last night, I've now found that the work-around I came up with [Automatic (Delayed start) for the MICyMon.exe service] hasn't worked this morning: although still selected as delayed start, it's loading early on PC boot-up, so I'm still getting the error message!
Very irritating: every time I think I've won, the b*st*rd combination of my PC and the 1026 software combines to thwart me!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 6, 2011 0:48:39 GMT
Have you searched the registry for more than one MlCyMon.exe? is not probable but maybe the program is being started twice with the second conflicting with the first already running when trying to access the hardware and finfing the patch blocked.
|
|
|
Post by JohnnyBlue on Nov 6, 2011 7:58:58 GMT
OK, MlCyMon crops up under HKEY_LOCAL_MACHINE/SYSTEM three times: ControlSet001, ControlSet003 and CurrentControlSet.
I'm guessing, probably wrongly, that it should only be in one ControlSet (001 or 003) as well as the CurrentControlSet, but really I haven't a clue!
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 6, 2011 9:00:08 GMT
John,
I've checked mine and MlCyMon.exe doesn not appear in any of those sections. In them you should only have MlCyMonS.exe (Notice the additional S that stands for "service") and it is OK to have in CurrentControlSet and the ControlSet00x's. How many 00x do you have? it is unusual to jump from 001 to 003 or was it a typo and you meant 002?
|
|
|
Post by JohnnyBlue on Nov 6, 2011 12:08:36 GMT
Nope, it is definitely 001 and 003 (see below). Interestingly, (well I'm interested, anyway) when I booted up the PC just now, in a hurry, the MICyMon didn't start up until after all the other systray programs, and I didn't get any error message. It's as if sometimes the MICyMon starts early (ignoring the 'delayed start'?) and then tries to load twice. Attachments:
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 6, 2011 12:29:15 GMT
I don't have any Vista PCs to verify that so lets accept it as correct.
Another trick to get rid of the error would be to start the PC with 02 unplugged as the drivers only load upon connection. Once the computer is stable you could connect the 02.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 6, 2011 22:17:05 GMT
BTW, this weekend I had the Asus Xonar D2X in the PC to compare it to 02 once more and I prefer the 02, the difference is not night and day in fact it is quite sublte but it is there. Maybe the 02's output is a tad hotter, no idea but everytime I listened to both for a while I ended using the Musiland even though it is supposed to be an inferior and cheaper sound card.
|
|
|
Post by JohnnyBlue on Nov 6, 2011 22:22:41 GMT
It's all very odd. I've just booted up the PC and it's done the same as it did earlier today: the MlCyMon seemed to obey its 'automatic/delayed start' command and loaded up well after all the network, firewall, antivirus, etc., gubbins had run. This again avoided the error message. The two controlsets seem identical, by the way: Attachments:
|
|