On March 14, 2016 09:29:15 AM Robert Jonsson wrote: > Here's another one that I think I'll call finished. ;) > > https://soundcloud.com/cdee/robert-jonsson-help-myself
Nice. I like the unexpected sort of short bridge chord change which also appears at the end. Sounds like kind of G to inverted A7 or dim. Heartbreak. The scars. Here's hoping you're not too blue. You know there was a certain blues player by almost the same name? > Biggest issue is that I had two crashes during audio recording, this hasn't > happened to me in a very long time so I'm a bit anxious to find the reason > but sadly core creation wasn't turned on.. duh. OK Keep me posted, I might be to blame. > I also had very wierd issues with opening LV2 native guis. For a long time > muse crashed completely when I tried to open the guis. I did a commit the other day making it easier to recompile the pre-built lvGtk2Helper library, if that helps. Just run the 32 or 64 bit makefile and it will create the library in a subdirectory called 'build' and cmake will use /your/ version while leaving the pre-built one intact. That is important because... Before, if a MusE dev happened to recompile the library it would replace the existing one and the dev might unwittingly push /his/ compiled version. Am I Right? I want to help packagers by providing a cmake option to recompile the library. I think it should be ON by default. I'm the one who suggested not requiring Gtk just to use LV2 features, but really anyone compiling MusE is installing several dev packages anyway, why not go ahead and require (actually recommend) Gtk2 - but /only/ if LV2 support is enabled. There's a safety aspect too, sometimes packagers or project hosts don't like binaries in the tree. Also it's weird having binaries in the git tree. My KDevelop won't show them in the project tree so it's hard to work with them, I have to use a filemanager. > A complete recompile and reinstall seemed to remedy the problem but then > after a few hours it came back. At this point I rebooted and the problem > vanished again. > At another point my wifi vanished on the same computer and I could do > nothing but reboot to get it back. This should not be related to MusE so I > wonder if my hardware is getting tired. > Either that or the gui issues is due to some nasty memory corruption/leak. Ghostbusters. Who you gonna call... The trouble I had getting this new distro running. Weird hardware problems, then Plasma crashing and so on. It seems to have mostly settled now, even before any major updates. Compare with a damped sinewave - it's working, it's not working, over and over again until it gradually settles. >From your snapshot it looks like you are running something similar, with recent KDE. That 'K' symbol. That little red "application crashed" tray icon. He he... > Anyway, I had fun recording it and a lot of things work very well, not the > least with Tim's latest fixes :) Thanks. Hope it makes things less cumbersome. That's our new tag line: " MusE3 - Now less cumbersome ! " T. > > Regards, > Robert ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
