RapidComposer v5 beta feedback and discussion

[BluGenes]

XML export loads and plays well in MuseScore 4.4.2, but, crashes Guitar Pro 8.. probably a problem in GP 8..

[BluGenes]

And, if you take the xml exported by RC and load it into MuseScore, then export THAT as MXL, it loads into GP 8.

Also noticed the file extension is just .MXL from MuseScore.. Win 10 even see's it as a GP file with that extension.

Thinking the MXL struct needs some tweaking in RC still..

Just repeat the same steps and open both files to compare..

[musicdevelopments]

XML export loads and plays well in MuseScore 4.4.2, but, crashes Guitar Pro 8.. probably a problem in GP 8..

When my GP8 trial worked (not anymore) I successfully imported RC-created musicXML into GP8. Can I ask you to send me the XML file that crashes GP8 when importing? I'll check the file and if I don't see anything wrong, I'll contact Arobas Music.

And, if you take the xml exported by RC and load it into MuseScore, then export THAT as MXL, it loads into GP 8.

MXL contains the zipped format of MusicXML so basically it is the same format but zipped.

Thanks,
Attila

[BluGenes]

Ok, so, I may be in-correct here.. I just re-tested, but, used a different midi file and now it works.

I suppose I had a bad file for what ever reason..

[musicdevelopments]

No, I think you did find a bug and there is indeed a rare problem with the musicXML file. If you happen to find a bad XML file, please save it for further inspection

[BluGenes]

No, I think you did find a bug and there is indeed a rare problem with the musicXML file. If you happen to find a bad XML file, please save it for further inspection

I tried, but, I can't get GP to crash now. I used the same file and it worked this time. The only thing is, it loads into GP but with multiple voices. I think it should have only been a single voice.

It may have been my PC was under a load at the time, running back ground stuff, so, that is probably the best answer.

[sj1]

When my GP8 trial worked (not anymore) ...

As a GP8 user, and someone always concerned with interoperability, I'd be happy to put up $10-15 towards a permanent GP8 license for Attila. Anyone else with me?

[sj1]

Hi.

Importing the attached MIDI file (originated in BIAB) into RC, I notice that the presence of a 2-measure Count-In area causes all the Parts and Lines to be offset by that amount from where I would logically like them to be.

RC - Blank Count-In Would Like to Ignore.jpg

Above is without Trim Silence selected but I also tried with Trim Silence selected and that did not produce the desired result either.

Perhaps we could have a new option in the import configuration area

RC - MIDI FIle Import Options 01.jpg

to the effect of 'Start Part/Line repetition at Measure N'.

The idea would be that the area prior to Measure N would be considered one single leading Part (an Intro, as it were), after which the normal Part/Line segmentation would commence.

All of Me (RVB) - 120 BPM - x5.zip

[lulukom]

+1

[musicdevelopments]

When my GP8 trial worked (not anymore) ...

As a GP8 user, and someone always concerned with interoperability, I'd be happy to put up $10-15 towards a permanent GP8 license for Attila. Anyone else with me?

That is very nice, but first I'll contact them for an NFR license. Most software companies are happy to help fellow developers with licenses, which is nice.

Thanks!
Attila

[lulukom]

Crash

[musicdevelopments]

Crash

Thanks, lulukom, I am checking this. It crashed when rendering a MIDI CC curve but the exact reason is not known yet.

Thanks,
Attila

[musicdevelopments]

Crash

Hi lulukom!

Do you remember what was on the screen when this crash occurred? Was the Phrase Editor open with the MIDI CC lane? Was the main composition page open? Or maybe you edited a rhythm in the Rhythm Lab?

Thanks,
Attila

[lulukom]

Hi Attila. At that moment I was cutting phrases in the composition window and switched to the notes editor. (there was CC midi open) I can't say more precisely)

[musicdevelopments]

Thanks, lulukom, that is very helpful!