Forum Replies Created
-
Posts
-
Yes, 3 libraries actually sound reasonable, but there are still plenty source files in (to me) a somewhat chaotic folder structure. “Bloated” was referring to that and the impression I got from compiling. If you could simply state what each folder is there, that could be helpful to possible contributors. E.g. there seem to be more than one folder called “luabind” which can be a little confusing.
That’s why I suggested a wiki, to explain how to get your code, how to compile it in a way that allows for automation and maybe even how Ctrlr works internally. And of course how to set it up properly, how to create panels etc. And keep it up to date! No more crawling through forum posts. 😉
It’s a shame nobody used the wiki last time, but be assured you would have at least one regular user this time.Also I can offer you to test Ctrlr on linux more regularly, if that helps.
By the way, have you considered releasing stable versions again?
If you just freeze the code of a “good” revision from time to time and apply bugfixes only, that wouldn’t hinder developement too much, would it?
Maybe I can help you there as well, at least by testing.And thanks for your promise to look into the luabind stuff.
What Audio/MIDI hardware are you using, MOTU? 😉EDIT: I just had a closer look in your Documentation. “Getting started” seems a little understated. Nice 🙂
Success! rev 1234 just compiled without a single error/warning! The problem seems to have been my fault. Introjucer changed some includes and probably other stuff and the changes consequently went into my patches. After switching to a different approach using “sed”, everything went fine. I attached the little script I will use to build a new executables in the future.
Btw, the offer still stands: it takes about 2 minutes to build Ctrlr here, so it won’t be a problem to supply the flourishing linux ctrlr community (still countable with one hand I guess) with the occasionally nightly build.
Thx for your help, where none should have been needed 😉
Alright, boost 1.49 also won’t compile on my system (Arch just went for 1.52)
Is it likely that you will make Ctrlr compatible with boost 1.50 or 1.52 soon or should I setup a less cutting edge system if I want to use the latest ctrlr in the next few weeks?The source structure should be taken care of by a few patches I created.
(will be switching to a sed based solution probably)As of today the nightly still doesn’t compile, due to errors with luabind.
I attached the commandline output in a textfile.Well… I “solved” the include thing. I suspected deeply dark magic there, but it was actually just a few folders.
Now I’m hitting the problem with boost and luabind.
I tried working around by using boost 1.48, but that version doesn’t compile on my system anymore…So this is probably where I can stop, until you remember your workaround or find another solution to make Ctrlr work with newer versions of boost…
I’d be glad if you did 😉Good Night!
If you want to do this, great, I’ll look forward to it! 😉
You might have noticed the TX7.xml file(s) (e.g. in “Yamaha – TX7.app/Contents/Resources”). All sysex commands are listed there, so you don’t even have to look in the implementation chart!
I might do the Kawai K1 and Lexicon LXP1/5 instead 😉As I see there is a folder structure like ctrlr[/…]/Source/{Core,MIDI, … } and these folders contain various header files and the related c++ files.
The headers are included e.g. like#include “CtrlrIDs.h”
so for gcc to find it I have to specify the path like “gcc […] -I “…/ctrlr/Source/Core” “. In the same way for …/Source/MIDI, …/Source/Lua etc.
Has this any benefit over including like e.g.#include “Core/CtrlrIDs.h”
#include “MIDI/CtrlrMidiDevice.h”
etc. etc.and specifying only “gcc […] -I “…/ctrlr/Source” “?
How do you handle this with the other compilers?I’d like to automate the compile process so I can easily rebuild the newest version of Ctrlr. I already made a patch to change the Juce Directory from within a script, which seems to work.
By the way, I have access to a rather powerful workstation (dual Opteron 6274).
If this works I can build you some Linux nightlies on a semi regular base, if you want.Best Regards,
RomanGreat! Now it would be good to know if (and how) you can extract the ressources (images) from the executable…
Sounds good, newcomers would feel more comfortable, too
” title=”Wink” />Hi hooya,
as you already figured out, the version in the AUR does not work because it’s an old build. Building from SVN is the way to go.
If you want to modify your patches, i.e. load them into ctrlr you usually need a lua function that parses a sysex dump of your patch and assignes the corresponding parameters to modulators (= buttons, sliders etc). Unless the author of the panel you are using has already done this job for you, you have to grab the midi documentation of your device and start experimenting a little.
If you are new to lua: I have done this for the TX81z panel without ever having to do with lua before. There are some good examples how to do this in other panels.If you can get me the ressources of that panel I can look into this, once I have some spare time.
Maybe earlier” title=”Wink” />
I have a TX7 as well.
Regards, RomanA few weeks ago I found a document on creating "panels" with SoundDiver nad tthe examples they used were the K1 and the LXP5 (which I am going to do a panel for in good time
” title=”Razz” /> ). There were some interesting notes about how these devices behave that might be of interest when creating a panel, e.g. that the K1 has no patch cache and you directly modify (i.e. overwrite!) the patches in your K1’s memory.
If anyone is interested I can dig through my internet cache and look for that pdf.
BTW I, too, would really appreciate a K1 panel but I don’t think I will have the time to do one soon, so if anyone still wants to try it out, go ahead!” title=”Wink” />EDIT: Sorry for the Spam!
” title=”Wink” />Has anyone noticed the two invisible buttons I added?
” title=”Wink” />
One sends a dump request, the other restores some sane starting values to create your own sounds.
I also implemented a function to filter the sysex dumps and assign the values to the corresponding modulators. That way you can tweak your existing patches.From the vast amounts of posts here since the updates I figure that either everything is working just fine (which I doubt) or that nobody using this panel ever visits the forum (again).
I have, however, some "known issues" for the users/testers.
1. Does the dump request work for you? – I used a sysex message that works for my YS200 but is not documented in the TX81 docs, so I figure it won’t work, but i can’t test that.
2. Do the "Reset Values" make sense? – These settings were found by trial&error so there lies potential improvement. E.g. someone could post a dump of an "empty" TX81 patch (one that was newly created)And finally: I’d like to make this panel universal for all 4OP Yahaha synths of that era. But without some people who can test the different devices this makes little sense and I only have my YS200 which I figure is quite obscure.
@atom: is there going to be some sort of changelog function for panels? Or is there already and I was again just to blind/dumb to stumple upon it?” title=”Wink” />I also had this exact problem and found no way to solve it. I suspected that my version of gcc might have been to new at that moment, but no guarantee on that!
For me the problem was solved, when I fetched the latest svn version of ctrlr a few days later. Everything went fine then.That’s what I did. Only after about 10% I got an error message: "Failed to post item to DDB:" without further information.
I was going to try the Windows version as there don’t seem to many Linux users and so there might be something broken here.
EDIT: Also I’m not able to refresh the database. Is that normal behaviour?EDIT2: Using the Windows Binary with Wine I was able to upload, but didn’t have the "permission to change the item". I already used a modified name.
Alright, I’ll do that.
I have the hardware at hand and can test most features, so I’ll do what I can maintaining this one.” title=”Wink” />[url:1hw6tk8u]http://lua-users.org/wiki/StringLibraryTutorial[/url:1hw6tk8u]
also if you still need this:
[code:1hw6tk8u]text = text1 .. text2[/code:1hw6tk8u]
…not that hard to google…
Good Night
” title=”Wink” />I wrote a methode to parse the SysEx dumps from the TX81z/YS200 and so make this panel even more useful.
It’s not quite finished (untested with real hardware, yet unimmune to crippled sysex messages, probably a little messy, some minor stuff missing) but it should work more or less. I’m posting it here so you can include it, if you want.
I used the YS200 references, so there may be some differences (probably not).
Also I noticed some un- or misnamed modulators, see the commens in the attached file.
Regards, Roman
