Ralf Mardorf schrieb:
> we are fine with Windows XP pro for multimedia.
>   
MS is not an option for me.
> The only thing I can imagine, that might solve the trouble for you, is
> to take a look if there was a problem by your BIOS for your new CPU.
> Maybe there is an update for your BIOS that solved this.
>   
It's already the latest (stable) BIOS for my motherboard.
> The Mozilla applications, OOo, GIMP and lots of other stuff is fine for
> me too, I "only" get this killall jackd too. I wasn't able to solve this
> from April 2008 to December 2008 and before I had other Linux multimedia
> troubles from November 2003 to April 2008 with another mobo and another CPU.
>   
I don't know, if we're talking about the same problem. You talk about
the "killall jackd" issue. Well, killing jackd is not my problem. My
problem is, that jackd is not stable with a 64bit-Dualcore-CPU. It
doesn't really matter, if I can't restart jackd after it crashed. But it
DOES matter, that I can't work in a stable environment as I used to with
my old CPU.

I guess you mean, that you read "killall jackd" in the messages of
qjackctl. But that only means, that after jackd crashed the "killall
jackd" command is executed, like it is configured in the
"setup"->"options"-menu in qjackctl. If you did, I'm glad to hear, that
my hardware is working alright. The software will be fixed someday, I'll
just have to wait...
> Anything else is fine and also the quality of Reverbs and
> Synth is much better, latencies are smaller etc. ... and no crashes.
>   
I'm working with some xruns at 2,5 ms and with nearly or exactly NO xrun
at 10 ms (with the old CPU). That's alright for me, you know. If the
quality of any OS-Reverb doesn't fit to my needs, I'm using my
T.C.Electronic M300 - guess there's no reverb "for free" on windows that
can reach that. I don't care about synths, but I guess zynaddsubfx and
AMS was more than perfect if I would.
I'm fed up with that licence nonsens and other bullshit on
non-OpenSource platforms. I once tried to make music with Windows and
MacOS. But I can surely say, that I had never such a complete and
reliable DAW than now - for free.
> I guess you should use your old CPU again, if you like to go on with
> Linux for multimedia. If you were fine with it, why did you changed it?
>   
Are you kidding?
Well, if not: Because I can use more tracks and plugins in ardour...?
I'm looking forward to use my machine as a digital mixer. The CPU I've
bought should give me the power I need.

By the way: Yesterday I tried the 32bit 64Studio-2.0 live without any
problems with my new CPU! Because I have another recording tomorrow, I'm
using the "old" CPU, again. When the weekends over, I'll switch to a
32bit installation. But I'll switch back to 64bit, when it's getting
stable, again. In case, we're talking about the same problem and there
is no defective motherboard or cpu, of course.

Have you tried 32bit?

I know, this is an unsatisfactory situation not using the full power of
your hardware. On the other hand, it's so easy to switch to 32bit and
back if you're using a seperate /home partition... :)

Mitsch

_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to