Bug reports

[dsan@mail.com]

Here are some screen shots of the RC beta installer properties window. Since the pics are large you will need to scroll them to see completely.

To open the properties window, right click the RC installer ".exe"

Select the last item "Properties"

Then follow the pictures to unblock the file.

Now, it should install completely and hopefully stop the crashing you have experienced.

HTH and Good luck!

Happy Musiking!
dsan

[tolstoevsky]

Dear dsan (sorry for using your cryptic nickname in the absence of alternative ),
now I grasped your 1st step, but, as I checked, there are no blocking notifications in installer's properties (everything looks initially as on your last picture), so there is nothing to unblock inherently.
Concerning possible virus protection mechanisms interferences - my BitDefender is tight as a clam during installations of any RC updates.
So...I am still left wondering what "may be standing in my way of a successful installation"
May be the problem after all is not there?
However that may be, grand merci for your help and time spent for clarification!
P.S. In fact, I must specify that many (but not all) of my latest crashes occure after I try to open some tricky midi-files (and only multi-channeled). So I am not claiming that RC has begun to work very inconsistantly: it just looks (and feels) like it crashes more often than before

[dsan@mail.com]

I have noticed in previous versions I get a crash when trying to open a midi file that has program changes imbedded in a track. Perhaps this is the issue.

I just opened several midi files that I know have multiple program changes within the track and had no crashes.

However, I notice the playback position indicator is moving along the timeline in a choppy fashion. It does not seem to affect the playback of the track though.

I am perplexed why you do not recieve the message "Blocked" in the properties window. I run XP, Vista and W7 and always get this message on a downloaded file. Strange that you do not.

Do you have UAC enabled? This could be the reason for that. UAC is enabled here on the Vista and W7 machines, for safety reasons.

And lastly, you are welcome to call me Dennis if you prefer I'll answer to just about any name. You should hear some of the names my partner calls me.

Let me know if I can be of any additional assistance. Hope you get it sorted.

Best regards,

Happy Musiking!
dsan

[como baila]

I'm away from my studio for the weekend. I have run one of the 2.5 versions in Cubase 7.5 without problems ... but I never tried to setup the embedding.

I'll try to remember to take a look on Monday using the latest version.

Yes, please, can you check if the latest beta works with Cubase 7.5? I don't know what happened because several people used the v2.5 plug-in in Cubase 7.5 successfully.

Thanks,
Attila

I've opened, saved, closed and reopened a Cubase 7.5 project with RapidComposer2.56b4x64 problem free. Everything worked as expected.

This is on Win7 x64 with 16GB Ram and a dual dualcore 3.0Ghz Xeon machine.

I have had 'hang' problems on reopen in the past and I'm still unable to open those earlier versions (I think RC is looking for the file it was hosting at the time and cannot find it?).

I did not think (occurs to me at the moment) to open a second 7.5 project with RC VSTi, save and close it and check to see if the earlier one reopens. Will try to do that today.

However, no crashes of either RC VSTi when instantiated or of Cubase itself.

One of the great things about running the VSTi in Cubase is that you can copy i.e., manually insert) your RC progression into Cubase's new Chord Tracks. You cannot only sync everything in time between RC and Cubase, you can also sync all in Key ... including audio tracks in Cubase. That plus being able to use all of Cubase's great midi tools on the midi input from RC and auditioning everything in real time and context makes this pairing a total winner.

[dsan@mail.com]

@ tolstoevsky - Another thought - are you downloading the file (SAVE, SAVE AS) or allowing the installation from your browser (RUN)?

I recommend downloading and then install (after going through the processes I have outlined).

A direct install from your browser may not be allowing complete installation.

HTH

Happy Musiking!
dsan

EDIT: Como - good to hear all is working well for you! Based on your report I may have to upgrade my Cubase

[musicdevelopments]

Thank you Dennis for the replies and tolstoevsky for the feedback!

If you happen to find a problematic MIDI file that will crash the program during or after importing, please let me know. It can be fixed usually quickly.

Thanks!
Attila

[musicdevelopments]

I've opened, saved, closed and reopened a Cubase 7.5 project with RapidComposer2.56b4x64 problem free. Everything worked as expected.

This is on Win7 x64 with 16GB Ram and a dual dualcore 3.0Ghz Xeon machine.

Hi como baila,
thank you for trying the plug-in in Cubase!

Today two nasty bugs were fixed, one of them caused the application hanging during start-up, when loading the last composition, the other made the chord progression library corrupted. A new beta version will be uploaded shortly.

Since so many issues were fixed since v2.55, a bug-fix update will be released next week. There is still a race condition which may crash VST plug-ins on OS X, this will also be eliminated.

Attila

[tolstoevsky]

Dear Dennis ,
thank you again for your new comments/ideas
and more specifically this one: "I have noticed in previous versions I get a crash when trying to open a midi file that has program changes imbedded in a track. Perhaps this is the issue" - I strongly suspect that multiple PCs are the main problem in such crashes.
But I would like to attach here two particular examples illustrating my crashes:
1st one is just an image showing the main window after bad opening of single-track file (with multiple program changes ) and
2nd one is midi-file which causes immediate crash without any comments and attempts to open it
I hope that Attila could explain why it happens.
My best wishes,
T.

[dsan@mail.com]

My results; RC crashed before opening the file.

Here is my screenshot. The midi in the load area is not tolstoevsky's midi. It was another I had previously opened.

Attila's turn

By the way T, you mention multiple PC's. If you move or copy a file from one PC to another you will not get the "Blocked" message on the moved file. This is because you previously set up trust levels between computers. The orignal file though (on the computer downloaded to) is still blocked and the move may have resulted in an incomplete file.

I cannot ascertain if this is what you meant by "multiple PC's" but wanted to mention this in case you are transferring files between computers.

Also attached is a screen shot of the midi file properties you deposited.

Happy Musiking!
dsan

RC crash.jpg

[tolstoevsky]

Very nice to see that I'm not alone experiencing such crashes, Dennis
And concerning your comments on "multiple PCs" - sorry for confusing you, I just meant "multiple program changes" not computers
P.S. I know indeed that some files have such additional feature (blocking/unblocking below their properties) and e.g. my archived file doesn't have it
P.P.S. BTW, I opened and played that offending (attached) midi-file in standard midi-player without any problems.

[dsan@mail.com]

I successfully opened the midi in Live 9. This is a very complex midi file and I'm not sure if RC is up to the task. Attila will be able to answer that.

I exported the file from Live and tried again to open in RC, thinking maybe something was amiss in the midi and a fresh export may resolve the issue.

Unfortunately RC crashed immediately.

You are right, T, hopefully Attila will be able to determine the problem.


Happy Musiking!
dsan

[tolstoevsky]

Well, may be I want far too many from this nice program )
Certainly, there must be some limits even for RC!

[dsan@mail.com]

So I did some experiments with this file:
First, I deleted all notes below C4. Exported midi (....violins 1), attempted to open in RC. Result, immediate crash.

Next, I deleted all measures beyond measure 23. Exported as a new midi file (...violins 2) attempted to open in RC. Result, immediate crash.

Next, I deleted all but 2 notes, creating a 1 measure midi file (....violins 3). Same result; RC immediately crashed when I attempted to open the midi.

There is definitely something in the files RC just does not like.

I have attached the 3 midi files (as an .rar) in hopes Attila will be able to determine the cause of the crashes.

Midi.rar

HTH

Happy Musiking!
dsan

[thebutler]

I'm away from my studio for the weekend. I have run one of the 2.5 versions in Cubase 7.5 without problems ... but I never tried to setup the embedding.

I'll try to remember to take a look on Monday using the latest version.

Yes, please, can you check if the latest beta works with Cubase 7.5? I don't know what happened because several people used the v2.5 plug-in in Cubase 7.5 successfully.

Thanks,
Attila

I've opened, saved, closed and reopened a Cubase 7.5 project with RapidComposer2.56b4x64 problem free. Everything worked as expected.

This is on Win7 x64 with 16GB Ram and a dual dualcore 3.0Ghz Xeon machine.

...

However, no crashes of either RC VSTi when instantiated or of Cubase itself.

One of the great things about running the VSTi in Cubase is that you can copy i.e., manually insert) your RC progression into Cubase's new Chord Tracks. You cannot only sync everything in time between RC and Cubase, you can also sync all in Key ... including audio tracks in Cubase. That plus being able to use all of Cubase's great midi tools on the midi input from RC and auditioning everything in real time and context makes this pairing a total winner.

Well, my thanks to you for checking this como baila; very thorough.

So, my issue of crash/freeze on attempting to instantiate RC in C7.5 must be an issue with my system and not inherently bad with RC (probably as I suspect, a low memory situation on a 32bit OS).

And, your second points about close integration of RC as VSTi with Cubase Chord Track/MIDI, was exactly what I was looking forward to trying out...

Ah well...!

Still enjoying the program standalone mind; will play more this weekend.

Cheers,
thebutler

[tolstoevsky]

So I did some experiments with this file:
First, I deleted all notes below C4. Exported midi (....violins 1), attempted to open in RC. Result, immediate crash.

Next, I deleted all measures beyond measure 23. Exported as a new midi file (...violins 2) attempted to open in RC. Result, immediate crash.

Next, I deleted all but 2 notes, creating a 1 measure midi file (....violins 3). Same result; RC immediately crashed when I attempted to open the midi.

There is definitely something in the files RC just does not like.

- Dennis, you are a magician
Same triple crash, sure, on my comp
Now I definitely want to examine in detail your "deconstructed midi-tracks", especially the last mighty tune with two notes!
Cheers,
T.