Ok. I will do the same. Thanks!I've had this segmentation 11 fault as well when updating using a Mac. I just did it again and it went away.
Ok. I will do the same. Thanks!I've had this segmentation 11 fault as well when updating using a Mac. I just did it again and it went away.
Hi Steven, ive got a bit lost on the thread, have you got your upgraded MDAC back yet and tried it against/with and without your grounded grid preamp yet?
Cheers
I am using a Mac. When updating the software once again the process was faultless.Are you using a MAC or PC? Never seen or heard of the message (sounds like your using a MAC)... But if the MDAC updated OK then your OK
At first, I wanted to hear glorious reports of how good the upgrades were. Well I got my wish, and now I'm suffering a bad bout of impatience It's only going to get worse once Fusion posts his reactions to his unit.
The only thing that can cure me is a dispatch email from Hifi collective
For my part, I'm really interested to find out whether the fusioned MDAC will drive my HD800 headphones as well as my Violectric V200 does (which is better than the stock MDAC to my ears).
The L2/Toy/Fusion has a totally reworked output stage - greater ClassA operating area, greater output current and lower output impedance so it will be interesting indeed
MDAC will drive 30 ohms no problem but is current limited to +/-150mA or so..[/QUOTE said:Busy weighing up which model to buy.
Any news on the Jiri suggestion in regards to front balanced headphone socket ?
And also confirmation that the Mamp/Mimp will do av bypass.
As per previous posts a few pages back.
Many thanks.
With this in mind when you get the chance can you update the specs off the headphone output balanced mod please.
Busy weighing up which model to buy.
Any news on the Jiri suggestion in regards to front balanced headphone socket ?
And also confirmation that the Mamp/Mimp will do av bypass.
As per previous posts a few pages back.
Many thanks.
...exept that I have now only the left channel...I am using a Mac. When updating the software once again the process was faultless.
There are some miniXLR PCB-mountable male sockets available on the Internet, the problem is that there's again no "standard" for pin placement - you can easily come across 3 different versions of ie. 4-pin minixlr socket/plug.Any news on the Jiri suggestion in regards to front balanced headphone socket ?
Segmentation fault is normally a program (app) error. It occurs when an application tries to access a (virtual) memory region that has not been allocated (or has been freed). Long story short - it's an unhandled program state, bug in the program itself, probably caused by some unexpected state of things (well, unexpected to the creators of the program).Restarting M-DAC
Segmentation fault: 11
logout
Ok. Everything worked perfectly until I reinstalled the newest software. It went through without any problems. However, after that I have had only the left channel. Frustrating. I try to go back to the 0.90 (with my wifes laptop-pc). Let's see, what happens... Hopefully it helps.Segmentation fault is normally a program (app) error. It occurs when an application tries to access a (virtual) memory region that has not been allocated (or has been freed). Long story short - it's an unhandled program state, bug in the program itself, probably caused by some unexpected state of things (well, unexpected to the creators of the program).
Ok. Everything worked perfectly until I reinstalled the newest software. It went through without any problems. However, after that I have had only the left channel. Frustrating. I try to go back to the 0.90 (with my wifes laptop-pc). Let's see, what happens... Hopefully it helps.
Edit: it didn't help.
To be more specific - the message is printed by the default handler (list of instructions) of the SIGSEGV signal, which kernel sends to a userspace program. The handler also causes the program to exit right after printing that message, likely with an exit code of 137 (IIRC).Ok. Everything worked perfectly until I reinstalled the newest software. It went through without any problems. However, after that I have had only the left channel. Frustrating. I try to go back to the 0.90 (with my wifes laptop-pc). Let's see, what happens... Hopefully it helps.
Edit: it didn't help.
It worked a while until I updated to the last software version. Then the right channel was again away.I don't think it's a software problem. In that case both headphone out and rear outputs should be affected.
Either it's a problem with the left channel relay or a problem with the left channel output at the rear panel or your cables, amp, ...
Have you tried connecting your amps right channel to the left channel output?
The software warning was only once there, when I updated to the latest software version - it gave the warning in the end of the update.To be more specific - the message is printed by the default handler (list of instructions) of the SIGSEGV signal, which kernel sends to a userspace program. The handler also causes the program to exit right after printing that message, likely with an exit code of 137 (IIRC).
Where are you getting it? .. I presume it's either the fault of the music player itself, some library or perhaps even a driver part that's running in an x86 protected mode. Most likely the player/library though as the error is considered a *very* serious one and often leads to security issues, so I don't expect such thing in the kernel.
edit: That said, the left channel problem is probably of different nature, try exercising the relay(s).
...exept that I have now only the left channel...
Power cycle the unit - or thump the top!
I might even start replacing the relays by default!
Try headphones, should work on both channels (ifs its a bad relay).