Bug reports

[spassbeisaite]

Crash in Idea Tool

When I work with little ideas, i don't need the "Parts". So, in the Timeline Inspector "Display Structure" is off to save space on my display.

Today I briefly entered the Idea Tool. I noticed that the display of some windows was not as expected (e.g. illegible headings). After a short time the program crashed. I tried that a few times with the same result.

I know, the Idea Tool needs "Parts" to work correct. Perhaps an alert window is necessary, when Display Structure is not checked.

If "Display Structure" is active in the Timeline, the Idea Tool can be entered. However, I soon notice that the processor is running at full load and the fans are turning up. It can also be observed in the activity monitor that the CPU load increases significantly as soon as the Idea Tool is entered. By leaving back to the Phrase Edit Mode, the processor load for RC is normal again.

So, something is unfortunately wrong.

RC 3.81 Mac OS 10.11.6

[musicdevelopments]

Yes, I can see the chopped off headings which I will fix soon. I could not make it crash though.
Will you send me crash report(s) in e-mail? That would help a lot.
Thanks in advance!
Attila

[spassbeisaite]

...today I couldn't crash it. But if I click for example on the hamburger symbol in the idea tool window below right, it takes up to 10 sec, until the menu opens. The other controls also react very slowly. At the same time the processor load increases. I will send the report if RC crashes again.

[spassbeisaite]

ok, now i have some crash reports.
To which email address should i send it?
And in the consoloe there was this message:
RAPID COMPOSER [7834] thread 1571543 caught burning CPU!; EXC_RESOURCE supressed due to audio playback

[musicdevelopments]

Please send them to info at musicdevelopments Punkt com

[tanislas]

Hi Attila,
I m using the latest update (osx 10)
1- I have a random crash when I throw a phrase in the track.
2-when I use ghost (shift F) and I use split phrases at chord boundaries only the first phrase makes it and the rest of the phrases diappear.
3- using snap for chord positions to insert a chord for example in the 3rd beat of the bar, the phrase (generator) is not changing where I expect it to change but only in the bar...but maybe this is normal?

Thanks

[tanislas]

3- using snap for chord positions to insert a chord for example in the 3rd beat of the bar, the phrase (generator) is not changing where I expect it to change but only in the bar...but maybe this is normal?

This is really a bug because when I use the V3.81 on my other mac (10.13.6) every thing works ok

[BluGenes]

go to the support tab and check for new update, 3.82.. If this is the version that you are using, there was a "silent" release of a newer 3.82, since the original was released. Re-install 3.81, then check for the update via the support tab, then get the newer 3.82. This version fixes the ghost issues..

[musicdevelopments]

Hi tanislas,

Thank you for the bug reports.
It would make the fixes faster if you send me crash logs. Actually I would be happy to study all RC crash logs that you find in /Applications/Utilities/Console.app.

Yes, splitting does not work with ghost phrases. Until this is fixed please use normal phrases for splitting. It is a bit tricky with ghosts, but I want to fix this for the next update.

Please note that chords are checked and used at the note beginning position. If the master track chord changes after the note started, it won't have an effect on the note.
Please send me a screenshot or a rcCOMP file so that I can check this.

Thanks,
Attila

Hi Attila,
I m using the latest update (osx 10)
1- I have a random crash when I throw a phrase in the track.
2-when I use ghost (shift F) and I use split phrases at chord boundaries only the first phrase makes it and the rest of the phrases diappear.
3- using snap for chord positions to insert a chord for example in the 3rd beat of the bar, the phrase (generator) is not changing where I expect it to change but only in the bar...but maybe this is normal?

Thanks

[tanislas]

This is a screenshot of the phrase not following the chord change time
https://i.postimg.cc/zDRTRcKW/Not-Following.png

Hi tanislas,

Thank you for the bug reports.
It would make the fixes faster if you send me crash logs. Actually I would be happy to study all RC crash logs that you find in /Applications/Utilities/Console.app.

Yes, splitting does not work with ghost phrases. Until this is fixed please use normal phrases for splitting. It is a bit tricky with ghosts, but I want to fix this for the next update.

Please note that chords are checked and used at the note beginning position. If the master track chord changes after the note started, it won't have an effect on the note.
Please send me a screenshot or a rcCOMP file so that I can check this.

Thanks,
Attila

[tanislas]

thank you BluGenes !
Do you mean a beta version? because what you suggested is exactly what I did to update to 3.82...

go to the support tab and check for new update, 3.82.. If this is the version that you are using, there was a "silent" release of a newer 3.82, since the original was released. Re-install 3.81, then check for the update via the support tab, then get the newer 3.82. This version fixes the ghost issues..

[BluGenes]

no, the official version..

[yellukhan]

This is a screenshot of the phrase not following the chord change time
https://i.postimg.cc/zDRTRcKW/Not-Following.png

its because of Timeline Snap vs Generator Division,
in your pic. chord changes smaller than the note lengths:

[tanislas]

its because of Timeline Snap vs Generator Division,
in your pic. chord changes smaller than the note lengths:

Thank you Yellukan!!! I got it )

[musicdevelopments]

I fixed the bug when splitting ghost phrases in the latest beta version (v3.9b1).
If you need the download links, please send me an e-mail or PM.

Unfortunately this is possible only by "unghosting" the ghost phrases, because ghost phrases inherit the size and scaling of the original phrase. I tried implementing splitting so that 2 ghosts are made from one, and added a setting for the ghosts to override size settings, but everything became very complicated and resulted in more questions, and more issues than it solved.

Thanks,
Attila