Hi, I just bought MuGen today, installed/uninstalled twice to get sure (one time with exe, the other time with msi, win 10), run as admin, always thes same:
- no base key to choose
- no scale/mode to choose
- none of the new songtypes under "Song structure"
Any idea why all this dont work :-( ?
And there does not seem to be any kind of manual/help/tutorial.
Kind regards,
Richard
O.k. I solved the problem with the root key/scale modes, maybe would been better (as long as there is no documentation at all) to not have it set on "randomn scales/signatures" by default......
But still there are no styles, it even is in the description but nothing to choose in the dropdown box and I have not found anything that might activate this in the list on the right:
Ah, I understand. See my attached image for explanation.
I will update the documentation so this is more clear.
The reason is that there are a lot of song types that use the same basic structure. It is the combination of song structure, tempo, keys and chord progressions, the use of 7th notes etc. that determines a song's 'style'.
I was just wondering that I dont get that picture with this song structures directly when I open the program:
Do I have to make some special settings to get this ? Or is the picture just for explanation ? Its just confusing that this picture is different from what I see when I opend the program, there is simply no "POP_BRIDGE" to choose for me like in the picture.
What would be your preferred/expected result in this case?
The program indeed creates songs that land on the 1, and in G Lydian that becomes G (major) which I agree does not always create the best results as the 1 is unstable in Lydian.
It basically uses G major scale with an augmented/sharp 4th.
To improve I guess it could be an idea to focus the chord progression on the 1, 2, 7 then use the 3, #4, 5 a lot in the melody and resolve the progression on the 5.
The song is in G Lydian in the sense that all the notes are from the G Lydian scale (which is actually the exact same notes as in a D major scale).
But the program does not emphasize the G Lydian tonality by hitting that #4th.
But if you create a G Lydian song, use a chord progression with a lot of 1's in it and avoid the 5, and maybe even use chord separation and pads I think you will get quite a few good sounding G Lydian compositions. What I usually do is create 10-50 songs, then click through them to find something I like then build upon that.
I feel that part of the reason for using a program like this is to get inspiration, and a big part of that is going 'outside the box' so to speak. So the flexibility regarding mixing of scales, modes, progressions and structure is an intended feature, not a limitation.
That said, I hear you, and it is actually a good idea to have some kind of 'style templates' that the user could select from. I will put it on my todo list as well.
I have to come back to the scale/mode thing. Are you sure this works at all ? I have tried all kind of different settings, progressions and went threw ALL the modes, no matter which I choose, even MINOR, all songs generated (at least the naming, maybe its only a naming problem, I dont know) where labelled "G major":
Hi. I am glad it works!
So to your suggestions:
I thought about using roman numerals but decided against it as I want the program to be usable by people not too familiar with music theory and notation. Also, If I went from arabic to roman numerals they would change when you switched from major to minor for example. (IV would be iv). Also, if I went that route, I should really add notation for dimished as well, and it would quickly become confusing.
Your other suggestion about being able to use your own progressions are actually exactly what I am working on now for the next release. I am also working on giving the user more direct influence on the different parts of the music, for example, if you find a drum pattern or bass line you like, you should be able to keep that and randomize the rest.
Then it must be both daw that could not read the name properly.
I have just made some quick test in my usual test daw environment mulab and its definitely not on that side. I imported files from cgmusic (dont know if you know, one of the best out there, from a game develloper to who sadly does not find time to devellop further), all with track name (melody, drum.....).
Then I add a screen from a midi editor software I sometimes use for your track, "untitled", this works really good on different midi files, can im-/export different formats.....:
EDIT: Just found out something interesting maybe that could help to solve the problem, it seems that the midi editor HAS the info, but not on the track but on the CHANNEL:
I am afraid the track naming still does not work for me and none of my daw reads the channel info:
I even tried the *.mid.xml but none of my daw could read xml it seems. If at least the track/channel Number was in the track name I could get the info from the text file but its still all only the file name, no number, no instrument, nothing:
It should be "simply" bringing the channel info to the tracks. I tried a bit today and renamed the "untitled" track names in the midi editor after the names of the channel info. Started with the first ones, saved and now it works as you can see in the picture:
It works in my other daw too, so it is really that your app has to output the channel info instead of whatever in the track name to make it work.
Of course this could be kind of workaround, but as the strength of the app is to put out lots of different tracks to compare IN the daw could not be a solution. But it helps for some more testing.
The first good news: velocity randomization works :-)
Yes, I agree, sorry, I should have explained :-).
The chord track is only to be able to use some other generative tools, sequencers, arps and so on on it to make them easiely play in tune with the song from mugen. Or to "recognize" the chordprogression on that track.
Of course it would be bothering to let it play all the time :-)
But if the track is there it will be played :-)
I see what you want and why you want it but that particular use case is a little bit outside the scope of the program at the moment.
However, I could add another 'creator' mode where things like that could be done, where the focus is not so much creating songs to listen to outright, but rather to create building blocks for a DAW do to speak.
Some more problems, I have attached the tracks in my daw and then the settings in case there might be something wrong which I doubt (I think there are some important bugs). Problems:
- I have chosen "pad" but the pad tracks are empty (I have deleted before making the screen so not to be seen but they are empty)
- whats more severe and can be seen in the screen: a lot of tracks dont follow the chord progression but simply stay on ONE note threw all the song, that does not make any sense at all
