Forum Replies Created
-
AuthorPosts
-
Thanks for the hint, I had seen and played with the getSize() but I have no idea how I overlooked getByte(), I will examine it now.
the JV1010 method actually works, I tested it on a component with controller for delay up to 5000ms, by setting the modulator in Ctrlr to max 5000 and by using r1, r2, r3 and r4 it maps the entire range 1 unit on the modullator gives one millisecond on the mixer, beautiful! Thanks once again Atom for prompt reply!
Good idea, the MIDI monitor is such an useful tool when working on a panel.
Thank you Atom!
“C:\Documents and Settings\%USERNAME\Application Data\Ctrlr” folder..
…there it was, I just did as you said and renamed the folder, now my midi monitor is working again. Probably some settings data got damaged when the program crashed.
Now I am back in the fight!It sure is a strange error, I wonder if it was triggered by me, shutting Ctrlr down while the midi monitor window running on my second video monitor, because I remember that Ctrlr crashed on me a couple of times last night when I was shutting it down, but I can not be 100% sure that the midi monitor problem arose just after that, since I did not try to use it immediately after. It this was the case, I would expect that clean re-install would fix it.
Try the vst versions : they keep the midi monitor .the only solution i’ve found to get it
thanks for the suggestion zeoka, I tried to export an instance of a panel, and when I run the instance I can open the midi monitor from it, but still it is broken on the main Ctrlr program.
Of course, OS is XP 32 bit with SP3, I was running ctrlr 1579 when this happened, I have uninstalled that version and installed the latest, ctrlr 1583, but it does exactly the same thing. Thanks for your reply, Gunni K
-
AuthorPosts