LinuxMusicians

Note, however, there does not seem to be any development of MusE Sequencer in the news section of the website. http://muse-sequencer.org/ Indeed, slow news year ;) Releases of MusE tend to happen a bit too infrequently... but there's been quite some work if you check the forum and github. At the mo...

So, there. I've gone through all the midi scripts and updated them to PyQt5 where applicable. Added to git in the main/master branch.

Apart from the MusE.cfg file I think it should be quite safe having multiple MusE versions installed so I don't believe the problems originate from this. The crash probably originates from one of two sources. 1. jack 2. a plugin that for some reason causes muse to crash To check the first, try runni...

funkmuscle wrote:yep that works. thanx. will you be doing that for the other scripts?

Yes that was my plan.

Ported the script at hand to PyQt5, please find it attached. I'd propose creating the scripts folder here $HOME/.config/MusE/scripts/ and putting the file there. MusE will find it and display it in the menu. The file needs to have the executable bit set. E.g with: chmod +x RandomizeVelocityRelative ...

Alright, cool. Unless you have a clear idea on how to link Awl correctly I think you might aswell ignore deicsonze for the moment. It's a synth plugin and MusE will run fine without it. This goes for all the synths, they are optional for the core application. What happens if you try to run the exe? ...

Looks like you got rid of the muse 2.x version, which is good. It is very old. Sad that we haven't been able to get a more recent version into the repos... Running muse3 in the end looks promising, not sure how far you got, is it working? The GTK errors should be harmless anyway, they should not be ...

Argh, PyQt4 is getting quite old, could be the packages are no longer complete.. The scripts should be ported to PyQt5, actually, didn't I do that already?! Hmm :S I'm not that fluent in Arch packaging, as Tim says it could be a missing package, search for more pyqt packages? It could be a python ve...

Hi Rob, that sounds wierd indeed. The muse built from source will be called muse3, are you sure this is the one you are starting? Possibly there is a 'muse' installed by Ubuntu Studio. If we keep to the console, check: which muse3 to find out which actual binary you are trying to execute If all that...

The last PKGBUILD linked in the post below built just fine here with the commit appended. Not only did it build, but the drum editor was also fully functional :mrgreen:! I believe it is indeed functional in most cases, the question at hand is the drawing of snap lines (unless me and the reporter ar...

I can say this much.

If you limit the checkout to
git checkout 4547301
which is at January 19, it seems ok. Something happened with the checkin after that, on the 20th.

Hey, I'm taking a look but as I'm not sure what I'm looking at yet it might not be quick.
I'll post here if I manage to solve it.

Thanks
Just drop us a line if you get stuck later on!

funkmuscle wrote:build but the same issue, the drum editor is not usable

I can confirm this. The fine grained lines in the midi editors somehow has vanished, it's still working I think but hard to know what you are doing.
Unless Tim checks back I'll hopefully have a look tomorrow night.

Hi Rob,

Did you check the videos on the tutorials page?
http://muse-sequencer.org/index.php/Tutorials

Tutorial 1 for MusE 2.2 hopefully gives you a good start. There has been some changes to how it works but it's mostly the same.