Bug reports

Official support for: musicdevelopments.com
dougj7
KVRer
6 posts since 15 Jun, 2018

Post Fri Jul 06, 2018 7:55 am

In the Idea tool is there a way to prevent the first instrument text from being cut off? I'm using the windows 7 64bit version. See attached image:
You do not have the required permissions to view the files attached to this post.

dougj7
KVRer
6 posts since 15 Jun, 2018

Re: Bug reports

Post Fri Jul 06, 2018 3:12 pm

Please disregard my last post. After installing a user interface theme that I downloaded on this forum, the text went back to fully visible.

PeteInNeedOfABeat
KVRer
29 posts since 28 Jun, 2016 from Germany

Re: Bug reports

Post Sat Jul 07, 2018 3:45 am

Ctrl+Q doesn't work anymore to quit RC. Keyboard Shortcut is still set correctly.

3.51 on Win7, 64-bit.

NTO
KVRist
98 posts since 8 Feb, 2011

Re: Bug reports

Post Sun Jul 08, 2018 7:04 am

Why can't/How do - I get phrase detect to break/size in sync w/chord changes for midi import?
2018-07-08_RC_PhraseDetectSizeQuestion.png
Tried a lot of combinations for settings...
You do not have the required permissions to view the files attached to this post.

musicdevelopments
KVRAF
2794 posts since 9 Jan, 2010

Re: Bug reports

Post Mon Jul 09, 2018 3:39 am

dougj7 wrote:In the Idea tool is there a way to prevent the first instrument text from being cut off? I'm using the windows 7 64bit version. See attached image:
Hi dougj7,
I see this too sometimes, I do not know yet why it happens :(
Thanks,
Attila
http://www.musicdevelopments.com
Music Prototyping And Automated Composition Solutions

musicdevelopments
KVRAF
2794 posts since 9 Jan, 2010

Re: Bug reports

Post Mon Jul 09, 2018 3:41 am

PeteInNeedOfABeat wrote:Ctrl+Q doesn't work anymore to quit RC. Keyboard Shortcut is still set correctly.

3.51 on Win7, 64-bit.
Right! I did not realize that! I will fix this shortly.
Thanks for reporting it!
Attila
http://www.musicdevelopments.com
Music Prototyping And Automated Composition Solutions

musicdevelopments
KVRAF
2794 posts since 9 Jan, 2010

Re: Bug reports

Post Mon Jul 09, 2018 3:48 am

NTO wrote:Why can't/How do - I get phrase detect to break/size in sync w/chord changes for midi import?
2018-07-08_RC_PhraseDetectSizeQuestion.png
Tried a lot of combinations for settings...
There is no MIDI Import option for that.
Phrase detection does not (have to) know about chords. The algorithm finds similar pieces by matching notes, and these notes are already chord-relative.

You can still split phrases in the timeline inspector, though logically this should be in the master track inspector:

Image
http://www.musicdevelopments.com
Music Prototyping And Automated Composition Solutions

NTO
KVRist
98 posts since 8 Feb, 2011

Re: Bug reports

Post Mon Jul 09, 2018 7:03 am

What are these options
under Midi Import to be used for?

They have some effect, though :?:
Size 2 = Size 1, Size None = 2 Bars
2018-07-08_RC_PhraseSplitQuestionTwo.png
2018-07-08_RC_PhraseSplitQuestionOne.png
2018-07-08_RC_PhraseSplitQuestionNone.png
You do not have the required permissions to view the files attached to this post.

musicdevelopments
KVRAF
2794 posts since 9 Jan, 2010

Re: Bug reports

Post Tue Jul 10, 2018 11:59 pm

BluGenes wrote: LoopBe30 mutes ports if accidentally looped back.. It isn't that.. I didn't narrate this one, so, watch the steps carefully..
Hello BluGenes,

thank you for your patience.
The crash occurs because of a bug in RC when you duplicate a track with '*' (BTW I liked that you used this shortcut) when the track contained a VST which is 'multitimbral' so one instance is created.

So it is not because using LoopBe30 or routing MIDI events to an external host. If you create the second track using any other method, there won't be a crash. I am still investigating this situation and will have a fix later today.

Thanks,
Attila

EDIT: this bug is fixed now, beta version is expected in the next 3-4 days.
http://www.musicdevelopments.com
Music Prototyping And Automated Composition Solutions

musicdevelopments
KVRAF
2794 posts since 9 Jan, 2010

Re: Bug reports

Post Wed Jul 11, 2018 2:33 am

NTO wrote:What are these options
under Midi Import to be used for?

They have some effect, though :?:
Size 2 = Size 1, Size None = 2 Bars
I have checked the source code but that is so complicated I do not understand it anymore :cry:
Basically these are just hints for trying to make 1 or 2 bar phrases initially, but the size is not guaranteed.

Thanks,
Attila
http://www.musicdevelopments.com
Music Prototyping And Automated Composition Solutions

BluGenes
KVRist
311 posts since 15 May, 2017

Re: Bug reports

Post Wed Jul 11, 2018 3:34 am

musicdevelopments wrote:
BluGenes wrote: LoopBe30 mutes ports if accidentally looped back.. It isn't that.. I didn't narrate this one, so, watch the steps carefully..
Hello BluGenes,

thank you for your patience.
The crash occurs because of a bug in RC when you duplicate a track with '*' (BTW I liked that you used this shortcut) when the track contained a VST which is 'multitimbral' so one instance is created.

So it is not because using LoopBe30 or routing MIDI events to an external host. If you create the second track using any other method, there won't be a crash. I am still investigating this situation and will have a fix later today.

Thanks,
Attila

EDIT: this bug is fixed now, beta version is expected in the next 3-4 days.

Awesome! Ummm, I see no other way of duplicating a track?

NTO
KVRist
98 posts since 8 Feb, 2011

Re: Bug reports

Post Wed Jul 11, 2018 8:14 am

FWIW (not in the app today)
Recently working w/ 'multitimbral', I did not see the channel number increment when I was selecting the same instance on new tracks.
Also
"You can still split phrases in the timeline inspector, though logically this should be in the master track inspector:"
This should be action for individual tracks. (Sorry if already true, not checking today...)

Return to “MusicDevelopments”