-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ralf Mardorf wrote: > Kevin Donnelly wrote: >> You've certainly spent a lot of time writing posts instead of >> making music. >> > > Because I can't make music with Linux.
Obviously. >> Random crashes are in my experience more often due to flaky >> hardware (ie hardware that is not broken, but is about to break). >> Even if everything works OK in Windows, that is no guarantee - >> Windows isn't as picky as Linux. Use memcheck, or try a new hard >> disk, or swap in another PSU. > I changed my complete hardware, everything is new, only the soundcard > isn't new, I can check it by a Hameg oscilloscope with a components > tester, but I'm sure the soundcard is fine. What sound card again? I have been using an RME PCI for a couple of years, and I don't plan to change. It was an expensive card but it has certainly been worth it. > I'm using Rosegarden 1.7.1, because 1.7.0 isn't fine. My 64 Studio > default install is a default install. Then use the downgrade mentioned earlier. Going newer is not usually the best choice. >> 64Studio was put together specifically in order to avoid your >> having to do that sort of thing. Get the basic, default distro >> working solidly first, and *then* (in a few months) start >> experimenting. >> > It's the default install. We, not only I, had troubles with > Rosegarden 1.7.0, that's why 1.7.1 is in the backport since > yesterday. There are no troubles with dependencies and nothing > changed to 1.7.0, problems are the same. That happens sometimes. >> One of the big problems with new Linux users is that they have >> itchy fingers - just because you can upgrade from different repos >> or compile the latest point release of something doesn't mean you >> should. > > I'm not really a full noob ;), more a semi-noob, but anyway, 64 > Studio is default. For a lot of your posts this was not the case. Do not lump those self imposed problems in with the default install of 64Studio. >> My main machine runs openSUSE, and the JAD distro worked fine on >> that, > > JAD comes with enlightenment 17 by default and enlightenment 17 isn't > stable. Or is there a new JAD released, not using enlightenment? I have never used these, but I am pretty sure you are not limited to E17. I would be more than surprised to find out that E17 was the _only_ choice. >> but there were intermittent problems that turned out to be a bad >> disk. My music machine (much lower spec) runs 64Studio, and it has >> worked fine so far. >> > By the way, some problems even must be there for you, e.g. Suse's > Hydrogen has a patch, so that it is in better sync than the 64 Studio > version is, when using Jack transport to sync Hydrogen and Ardour. I > don't use Jack transport, so I don't have to compile the stable svn > version of Hydrogen, but for some users this should be an argument to > compile an application instead of using the default version of 64 > Studio. > This is always the case. If you are building a new version then make a .deb package out of it. It will supersede your installed version. Of course if there are a lot of dependencies that need updating, this may not be an option. > I'll change the RAM, check the soundcard and PSU and look for a new > BIOS update. But if there will be such broken hardware, I must have > crashes, also when using non-audio applications. RT apps are really demanding, and can often expose bugs in the BIOS or in the drivers themselves. I personally experienced this with my laptop. > It might be interesting if somebody else has an ASUS M2A-VM HDMI, I > especially bought the ASUS, because my old mobo is an ASRock, and I > won't by an ASRock again. > I have this board and it sucks. It plays DVDs and and xvids for the TV, running a vanilla install of Windows XP. Quite simply, I gave up trying to make it work properly. It is the reason I now avoid AMD/ATI. Soon I can ditch my HP laptop from hell (nVidia chipset, AMD CPU, and two years of pain that I will not get back). In the face off all this, my 939 based AMD machines run flawlessly. If buying new there can be only Intel :) It is almost stable under windows too. Low latency work blue screens it, (memtest came up clean btw). > It seems to be, that my hardware isn't broken and I'm using the > default Yes it is. It is broken by design. > install, excepted Rosegarden. I can reinstall the default version > 1.7.0. Maybe this will help. > > Thank you again :). I still frustrated, because I don't think that my > hardware is broken and the reinstall to 1.7.0 will be a help, but > maybe I'm wrong. > Best of luck. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIu4EkwRXgH3rKGfMRAh6wAJ9VjF/Ew0f8AORQAJegor84j0x0vwCePB6K LsakcUjGrXXUEJ4eEsd575w= =OaZO -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
