Gustin Johnson wrote: > Adding Ubuntu and Debian sources and then doing some sort of tar backup > and restore (seemingly at random) is not my idea of a level headed > approach to software testing. >
I'm only using repositories for Hardy and I just made some, not a lot changes, it's not me you are thinking off. My 3.0-beta nearly is a vanilla install and as Daniel has mentioned before, they do know that there is something bad because of the package 64studio. > The corollary to this is that one then takes responsibility for the > changes one makes. This is the key to Free Libre Open Source Software. > That's what I do, I only made bug reports, btw. Fmit isn't fine on my 3.0-beta3. I didn't reported that. spinymouse-s...@64studio:~$ fmit fmit: symbol lookup error: fmit: undefined symbol: jack_error_callback >> 2. For a beta there could be bugs and those bugs should be reported. >> >> > The only problem I have with your bug reports is that your system tends > to not reflect the actual released beta which makes it difficult to sort > out exactly where the bugs are. There are not many changes for my 64 Studio that have impact to the vanilla version, e.g. I add Qtractor, but don't change dependencies, even if this would be better for Qtractor. I'm able to change everything back I made, excepted of behaviours because of e.g. the broken package 64studio. Btw. nothing gets broken because I installed from third party packages. I did install less apps this way, e.g. Shutter is one of them and non of them ever caused trouble. The only trouble I've got is the 64studio package, resp. what ever depends to this package. > I can say that I have yet to reproduce > any of the bugs that you have reported, though I have not had the time > to test every single "report" that you have made. That is not to say > that you may not be finding legitimate bugs, but they will get buried by > the noise of your spurious reports. > You better don't remove the package 64studio and than install it again, I guess this was and is a useful report, because if you like to test some newer versions of libs you need to do this. I tried such things, but always noted all changes to make it 100% possible to change things back ... it's not my fault if a package in the repository gets broken, this could happen for a beta, it's also not the fault of anyone else. I guess that very often people aren't talking about my troubles, but mails I replied too, e.g. because of the kernel. I never used another kernel than the standard-vanilla-default kernel and I absolutely have no Debian repository added. >> Disgusting! I only speak well about 64 Studio, I'm not from Windows or >> MacOS. >> > > Actually you have made many comparisons to Windows with respect to > "professional" audio. Having said that, I don't care where you "came > from". I applaud your enthusiasm and I look forward to your future > contributions. Yes and I also installed Windows to my computer, but I don't use it, anyway I was an audio equipment developer and need to work with other OSs. I know the audio apps very well and stopped those comparisons some time ago. 1. I don't have many third party or svn etc. apps installed 2. I'm not using another kernel 3. I noted every step I made by Synaptic's history and by a bundle of DIN A 5 notebooks 4. I made regular, error-free tar backups Replies to people using other kernels doesn't mean that I use other kernels too, even if I did it for one 2.1 install. Btw. there's nothing bad with having more than one kernel, this don't break a system, like no third party package will do, if you will make changes change back if needed. Some people might not like my personality or the style of writing, but the facts about my 64 Studio install are not those some people and you think. Sometimes I only reply to other users and sometimes I'm able to help other users. Actually on my system there are 4½ things broken: 1. MIDI jitter, but this is for any vanilla install of any distro the same 2. Trouble because the 64studio package tries to do something that it isn't able to do and because of this I need to restore some files from a backup. This is because of a bug not caused by me, but by the 64 Studio developers, because it's a beta. 3. Auto-mount isn't fine for DVD and hard disks. This might be because of the chroot, if so, this won't be hard to fix. 4. Fmit doesn't open 4½. Qtractor might have a loss for the sound quality Ooops, pardon 5. Hydrogen very often crashs And I always said it's okay and I recommend to use the beta on several mailing lists, because it's stable and I also added that for 64 Studio there is a kind community. I guess there were two people, Kevin and Rich on deadly dullness not correctly reading my reports ... and by the way, you seem to think of my 64 Studio Lenny which I don't use any more. I won't reply on anything because of this issue any more. Btw. how many of you did use Synfig and how many just launched it and played 60 minutes with it? Okay, in this case I couldn't launch it, but not seldom I've got the impression that people don't really use applications, while I do use them for days. I've got this impression when I'm able to help people who made music for days and then run into trouble and nobody but me replies. I do reply and I'm sometimes able to help, because I had similar troubles too. There are problems that only appears when there's some load, after producing several days, while just starting an app and making some recordings for 12 hours is something complete different. Where are reports from other people? What I read from other people who do work a lot is something like ... "I guess I need to pay a master studio" etc. ... search the archive ;). There a some people Dave, Quentin, you who do work a lot without having trouble, this doesn't mean that other people don't have trouble, hey and even Dave has got his MIDIsport. If people like Kevin and Rich are fine with everything they might distribute howtos, e.g. how to use Swami and other apps that are needed and come without a manual. Or just answer people who ask how to make soundfonts and GIGs with Linux etc. ... stupid flames aren't a better help than what I do. And again, I don't know any place where I have to discuss such issues like this one, even if a lot of people don't like me, they simply don't stay in touch with me and that doesn't mean that there aren't other people who do like me. Kevin and Rich should block mails from me and they don't need to worry, Bill doesn't pay me to infiltrate 64 Studio. EXIT LAST MAIL BECAUSE OF THIS anything else is for /dev/null Ralf _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
