Forum Replies Created
-
Posts
-
MidiOX puts a configurable amount of waiting time after each 0xF7. Sending 116622 bytes without breaks might be a problem for some instruments.
Because the function of sendMidiMessageNow is to send a single message, that starts with f0 and ends with f7. I don’t see any problem with it.
I don’t have any problem with it, I just don’t understand what problem sendMidiMessageNow could have if it was not restricted to one single SysEx block, and if would let me decide what to put in the data to be sent.
Yesterday I noticed this too working on my current RefaceDX panel project.
A dump with one single patch already contains 7 little sysex blocks with lengths of respectively 13, 51, 41, 41, 41, 41, 13 bytes = 241 bytes in total.
I first tried to use SendMidiMessageNow() on the complete dump but soon discovered that only the first 13 bytes were sent.
So I now call SendMidiMessageNow() seven times in row. In this case with such a small dump no extra intervaltime was needed. Just extra lines of code and extra work for me.I think this is a strange limitation of SendMidiMessageNow. Why not let me decide if I want to send my dump as a whole, or in separate packets?
Yes I am on Linux. In this case the the dump is 241 bytes in size, so that should not be a problem except if the 0xFE and 0xF8 bytes keep filling that buffer. You are right that from the moment the first 0xF0 arrives the dump continues uninterrupted until the last 0xf7 has passed.
I should do some testing on my Windows machine to be sure I am not doing something wrong that has nothing to do with this.
Maybe you can recommend one of the existing panels to study how handling MIDI SysEx in/out dumps can work in Ctrlr panels?This is a linux issue not Ctrlr, there is a special option in ctrlr to use JUCE own file selector dialogs, use that to go around the problem
If you read again my first message: I know that, and I tried that: in Edit->Preferences (Ctrlr/Settings) I already disabled “Use OS native file open/save dialogs (disable for Linux). If I load or save a panel I see indeed a fileselector that differs from my Gnome/GTK+ fileselector.
But if I try to open a fileselector from within LUA code for a panel – my panel can save/load a patchdump to/from a *.syx file – Ctrlr freezes. If I now, while Ctrlr is in frozen condition – open a terminal and try the “ps x” command I can see that Ctrlr has tried to use zenity to open a native fileselector:
12461 pts/0 Sl+ 0:00 ctrlr
12477 pts/0 Sl+ 0:00 zenity –file-selection –title=Load Patch 2>/dev/nullIs there a separate option to force the use of JUCE dialogs instead of native (zenity) dialogs also for inside panels? I could not find it?
1. Just use something like MIDIOX and its midi monitor instead of Ctrlr one, there you can filter those messages.
2. Where do you want to filter them? In “Called when the panel receives a MIDI message” method?
1. Yes, sure I know that. But still it would be nice if I could filter it in Ctrlr’s MIDI monitortool.
2. Yes that’s the idea. I have created a button that sends a SysEx dump request message. The RefaceDX will react by sending a SysEx dump. And in my Lua method I want to first check the size of the incoming SysEx, from the first 0xF0 to the last 0xF7, and if the size is the expected value, extract the correct values to set in my Panel’ s parameter values. For this to work all 0xf8 and 0xfe bytes should be ignored.
To make things more complicated (I hope it isn’t a problem for Ctrlr) the SysEx the Reface DX is sending consists of 7 SysEx blocks (seven times 0xf0…0xf7).
I just tried the same panels in a Windows machine: no problem.
The problem is on Linux only.Thanks for working on this document.
But I agree with lcchan that open source development, which includes not only software but also documentation, should be done in an open source version control system like git. And I would expect to find stable versions of such documentation easily in the ctrlr website below the “Documentation” and/or the “Downloads”, not hidden inside a forum thread.Having said that: Keep up the good work! Good documentation is essential for the usability, power, and future of ctrlr!
BTW:
I couldn’t figure out how to highlight this line:CPUS=`cat /proc/cpuinfo | grep processor | wc -l`
as codeblock in this message editor. The backquotes that are important for this code seem to confuse the
codesyntax?I guess these kind of fixes and bugreports would be much faster and easier if I knew how to use GIT properly. Sorry for the inconvenience, I hope my reports will reach the right person(s) using this forum also.
What do you mean by “not the standard MIDI device”?
You must select the correct MIDI input and output devices to be used from the Ctrlr MIDI menu. It shouldn’t matter if it’s a “real” MIDI device or a USB connection I guess.Hi,
Thanks for reporting the wrong file in the download section!
I uploaded the latest and greatest version 20150223b.I have started some nice bankmanager support. Not completely functional yet though.
Great, another Korg DS-8 owner! 🙂
When posting bugreports:
1. please download and test latest released version of the panel from the download section (currently: 20150115). Several bus have been fixed since 20150101). BTW: I am working on a newer version with save/load/put/get support for the 100-voice banks.2. Please download and test latest version of Ctrlr from the download section (currently: 5.3.85)
3. If you are using “older” version, please specify which version
4. If it “doesn’t work”, please specify what exactly doesn’t work, what error messages do you see? If you know how to use a terminal and commandline: Try to start Ctrlr from a commandline and redirect (error)messages to a textfile.
Good bugreports can be a tremendous help to fix bugs and improve panels and/or Ctrlr.
And I have more questions around Licences. I see Steinberg VST sdk2.x public source code is part of the distribution. I think the Steinberg Licence does not allow this:
I quote from Steinberg VST PlugIns SDK Licensing Agreement, version 2.4:
2. The Licensee has no permission to sell, licence, give-away and/or distribute the VST PlugIn Interface technology or parts of it in anyway, on any medium, including the Internet, to any other person, including sub-licensors of the Licensee or companies where the Licensee has any involvement. This includes re-working this specification, or reverse-engineering any products based upon this specification.
If the Ctrlr code will be distributed without the Steinberg vst sdk components, it can also not be distributed under the GPL licence anymore. And it would be rather unfriendly to people who want to compile their own Ctrlr binaries.
The conflict between GPL and Steinberg licences is a known problem and probably the reason why the main Linux distributions don’t support VST technology by default. Even free software like Ctrlr and many free VST plugins are not and cannot be part of the distribution’s download repositories.
OK, I see.
One thing I don’t understand: How can Ctrlr use two different Licenses simultaneously? It seems to me that the GPL and BSD licences are not compatible.
If I can freely choose to agree with only the BSD licence this makes the GPL licence useless.
Or am I misunderstanding something?I just tried to load the Linux VST plugin version (Ctrlr version 5.3.71 64 bits) using Qtractor 0.6.4 as host on Fedora 21.
The plugin shows up in the list of available VST plugins, but when I try to start it Qtractor crashes
I just tried to load the Linux VST plugin version (Ctrlr version 5.3.71 64 bits) using Qtractor 0.6.4 as host on Fedora 21.
The plugin shows up in the list of available VST plugins, but when I try to start it Qtractor crashes.
I don’t know if what you ask is possible, but I personally would NOT prefer such behaviour. If I want a a smooth transition, I move the slider smoothly in the speed of my choice. If I want a quick and direct change I tap/click on one new position. How else should the panel know how slow or fast you want the transition from A to B to be?
I don’t know how git works. How long will it take before we see those fixed in the git sources?
