Bug reports

[tonedef71]

Hello Attila:

I am running on Windows 8.1 x64. It appears that all of the issues (audio and drag/drop MIDI) seem to be related. I ran an earlier version of RC, and the same problems happened; the issues are also now happening with my Sonar X3 as well.

I did perform a "SFC /SCANNOW" and found some corruption on the windows system image, so I ran the DISM utility ("Dism /Online /Cleanup-Image /RestoreHealth") to repair the corruption. The last time I had corruption like that, it was related to faulty Windows update patches. Whether or not the image corruption is responsible for the problems I am having now, I do not know.

The audio problems are a result of the JackAudio server failing to connect to the named pipe that gets created to link the audio between the JackAudio server and the ASIO drivers of the audio applications. As is the case with drag & drop, named pipes require that all involved applications are running with a compatible Windows "Mandatory Integrity Level" in order for system messages to propagate between applications.

For some reason on my system, RapidComposer and Sonar are now running with an integrity level that requires the JackAudio server to be run with elevated privileges in order to interoperate with these two applications.

I noticed that if I ran the RC installer and left the "Run RapidComposer Now" checkbox checked before exiting the installer, RC would run with a suitable integrity level (TrustedInstaller): drag & drop of MIDI files from Windows explorer and the JackAudio ASIO driver work fine for that session.

I checked the RC installation folder and for some reason it, along with all of its contents, was owned by the Adminstrator user instead of my own user. Ditto for Sonar. After fixing this (by changing the owner of the files and folders), I am now able to run RC and Sonar with suitable integrity. However, RC and Sonar still do not run with suitable integrity from the shortcuts pinned to the start menu.

[musicdevelopments]

Hi Tony,

this is wonderful! I have learned a lot from your solution. I'll save your post, maybe someone will face the same issues.
Please ignore the e-mail that I sent, there is no need to run any logging.

Thanks!
Attila

[Mrposull]

Hi Attila, I'm not sure if this has already been reported. I'm running 2.82b3 on Win7 x64. I created a simple 4-bar chord progression using the default guitar sound font and 'FingerPicking07' phrase. When I hit 'play' with looping enabled the 4-bar loop plays continuously and all is well. I stop the playback, hit F2 to go into note editing mode and the Note On Velocity graph pops up showing the note velocities. I then hit play and the first time through all is well. The second time through all the velocities are messed up - being much quieter at the beginning of the loop and increasing a little in velocity about two thirds of the way through. Doesn't matter if it's 32 or 64 bit version of RC. Also, it does the same if I use midi out connected to a sampler. Attached is the rcCOMP file in question.

Cheers
Paul

[tonedef71]

Hi Tony,

this is wonderful! I have learned a lot from your solution. I'll save your post, maybe someone will face the same issues.
Please ignore the e-mail that I sent, there is no need to run any logging.

Thanks!
Attila

Thanks Attila. I am not sure if what I ended up doing was more of a workaround than a solution.

I apologize in advance if I have asked you the following question before: is it possible to have debugging logic in RC that is disabled until RC is invoked with a special command line parameter to dynamically enable trace logging to a file? Or if the logging is not too invasive, then have RC logging always enabled; the startup and initialization phase of RC could be logged every time to the file and then further logging could hold off until warning conditions and/or crashes occur. You would then be able to request that a user send you the rc-run.log file as the first step in reporting an issue.

[tonedef71]

I then hit play and the first time through all is well. The second time through all the velocities are messed up - being much quieter at the beginning of the loop and increasing a little in velocity about two thirds of the way through.

I, too, am hearing the same sort of phenomena with playback in the latest beta. I loaded up a 4-bar song snippet that I created in a previous version of RC; it is configured to play back through the MIDI rendering engine. I enabled looped playback mode and pressed the play button. On the first play through, the song volume is steady, although it sounds a bit on the quiet side to me. Then, on the first loop (i.e. the second play through), the volume jumps up on the second beat of the first bar.

[musicdevelopments]

Thanks Paul and Tony, for reporting this weird issue. The fix is under way but it is not an easy one. It is both a bug and a theoretical problem when dealing with optimizations in multiple rendered layers

[musicdevelopments]

then have RC logging always enabled; the startup and initialization phase of RC could be logged every time to the file and then further logging could hold off until warning conditions and/or crashes occur. You would then be able to request that a user send you the rc-run.log file as the first step in reporting an issue.

You are reading my mind (again)
There is logging built in, but it is not enabled in the release build. A less detailed log file could always be created, with an option to make it more detailed, but slower to create. It would be cool to automatically add the log file to the e-mail when the user presses 'Send Bug Report' but AFAIK this is not possible with the mailto: URI scheme.

Thanks,
Attila

[JohnBullFrog]

sometimes when I view a phrase in the main composition window it looks and sounds correct but when I double-click it and enter the phrase editor, parts of it are now the wrong notes! here is an example in the composition window,



but when I double-click the phrase to enter the phrase editor this is what I get,



I am really confused as to why the phrase does not stay consistent between these two views.

[musicdevelopments]

These look different because all the notes are chord-relative (except the 1st, 3rd and 4th note from the left) and these notes adhere to the current chord. E.g. the notes in the red rectangle will be relative to E Major, but neighboring notes use different chords in the composition, while in the phrase editor the whole phrase is shown as rendered with one chord (B Major).

If you convert all notes to scale-relative notes, you will see the same in the phrase editor, and in the composition, unless the scale changes in the middle of the phrase. To do this
- in the phrase editor: select all notes, then choose "Scale Notes [+semitones]" in the Note Mapping menu
- in the composition, select the phrase, right-click to open the inspector, and first choose "Convert to Absolute Notes", then select "Scale Notes [+semitones]" in the Mapping menu, then click on "Convert To Relative Form".

[musicdevelopments]

Paul, Tony, will you please try the new update (beta4, last beta version built for Windows only).
I think I managed to fix the issues with the note velocity.

I was playing with the composition in VelocityProblem.zip; available a few posts above. Interesting rhythm patterns can be achieved when adding 'Double Note' and/or 'Remove Note' to the track... Die-hard users can add 2 Double Note's Try this: "Double Note" set to "Before Time 4", and another "Double Note" set to "Note At Index 1". As you move the sliders, the rhythm changes. I enjoyed this composition, thank you Paul! (Please note the Piano track and the Steel String Guitar track uses the same channel, therefore you will hear piano sound instead of guitar).

Thanks,
Attila

[tonedef71]

Paul, Tony, will you please try the new update (beta4, last beta version built for Windows only).
I think I managed to fix the issues with the note velocity.

Sorry Attila. I still hear volume problems with my composition. I will PM you with a link to the 4-bar composition. The volume problem is easier to notice if you turn on looped playback and use the MIDI playback engine.

[Mrposull]

Hi Attila, I tried beta version 4 and like Tony I'm still having velocity issues. Attached is a simple phrase that gradually increases in velocity. When playing in looped mode everything behaves as expected *until* you press F2 to bring up Note Editing mode (I did while the phrase was playing). After pressing F2, everything plays correctly the *first full* time through. The second time through the phrase (remember we're in loop mode) the velocity envelope seems to be ignored and the phrase is played at a constant velocity. Now, if I press F1 to go from Note Editing mode to Phrase Editing mode (or if I press F3 or F4) the phrase immediately starts to play back as expected. If I then press F2 again, it starts to misbehave the *second* full time through. And if I exit Note Editing mode (F1, F3 or F4) it immediately behaves normal again.

Version 2.81 behaves very similarly except in my case the *wrong* velocities are different than with the latest beta.

Hopefully, this makes sense but let me know if you need any more info or clarification.

Cheers
Paul

[musicdevelopments]

Hi Paul,

thank you, I managed to reproduce this, I'll investigate and fix it. This is a different issue from the one reported by Tony.

Best,
Attila

EDIT: this bug is fixed now, and it was most probably the same issue that Tony experienced.

[Mrposull]

Hi Paul,

thank you, I managed to reproduce this, I'll investigate and fix it. This is a different issue from the one reported by Tony.

Best,
Attila

EDIT: this bug is fixed now, and it was most probably the same issue that Tony experienced.

That's great Attila. Excellent support. I hope RC becomes hugely successful for you.

Cheers
Paul

[amiracam]

Issue: Screen will freeze but playback works

Mac OX 10.10.1. latest Mac Mini model, 16gb ram
Resolution : 28.5-inch (2560 x 1080)

Pressing on tabs, left clicks, right clicks etc anything that seems related to mouse input fails to respond.

Pressing on the space bar will trigger playback.

Mac's "Force Quit" dialog does not show RC as "Not responding"

Its happened several times , yet I can't discern a pattern that leads to this state.