Forum Replies Created
-
Posts
-
Knobman is a phenomenal app, been using it for some time now together with Max/MSP. You won’t be disappointed!
Yes, the property panel. I understand the rationale for potentially wanting to have scroll functionality in the panel, but for me, I’d give it up if it meant not inadvertently changing properties I didn’t want to… BTW, I should clarify that I’m not talking about the turning off the ability to scroll the entire property panel up and down – just the ability to scroll an individual property’s value.
Can you just disable response to mouse scroll for the elements in the right hand pane?
Yup – just tried with VST, and it works correctly ("test" plugin is named appropriately, and can co-exist with regular ctrlr.vst). So just seems to be an issue on the AU side. No rush, thanks again for all your efforts!!
OK, understood.
Followup – it seems that there is a conflict if one has the main Ctrlr.component, as well as a "Player" component in the plugins folder at the same time. In other words, if I have
Ctrlr.component
Test.component
Test.playerAll in my AU plugins folder, apps only seem to "see" the Ctrlr.component. Furthermore, if remove the Ctrlr.component from that folder, then apps do see and properly open the Test plugin, but it is incorrectly still named "Ctrlr" – will we have to manually modify the file’s resources to change that, or will that be automated in the future?
Thanks!
Ah, I see, I was putting the .panel file in there too, instead of the .player file. Now it’s working, thanks!
Question though – is there any way that the two files could be bundled together into one, so that the plugin is like others with just one file? On OS X, perhaps you could put the .player file within the .component file’s app bundle? Not sure how it would work on Windows…
First – this is all AWESOME! I didn’t check the forums for a few weeks, only to come back to see all this great development. Thanks atom!!
Second – having trouble figuring out how to make an AU (or VST) that includes just the one panel, with no ability to edit, etc.. I loaded up the regular Ctrlr.component in Ableton, then opened up a panel I was working on, then saved as a Player. That created a new .component file for me, which I put into my AU plugins folder (I tried both with and without the original .panel file), but I don’t see that "custom" ctrlr AU plugin in my apps when I try and load it up? Am I doing something wrong?
Really looking forward to this! I think if you’re successful with the "no programming" thing, you will see an explosion of ctrlr devices….
Not sure why you are posting about my Klee software here TonE, but feel free to email me directly at dan@defectiverecords.com if you’re having trouble with it!
OK, here it is, "Ensoniq_DP4_Sysex_Spec.pdf", 8.1 MB.
http://hotfile.com/dl/85782499/9fa5990/ … c.pdf.html
Hopefully Atom (or someone) can tackle this baby! I would try myself, but I’m still at the "Hello World" stage with ctrlr development I’m afraid…
I have the full DP4 MIDI/Sysex Implementation Specification. It’s "Appendix A" to the original manual. It’s 40 pages long,and very complete. This is a pretty complex Sysex implementation – I believe it will be challenging! I’ll scan it at work on Monday, and post….
I’m also the person behind the Peavey PC1600x pages at http://defectiverecords.com/pc1600/pc1600.html – the DP4/DP2 implementation that comes with the stock patch that comes with the device is basic – it only controls volume/mix status of the 4 effects units in the DP4, and some generic controls with each effect. It’s nowhere near as complete as Rob Martin’s old OS9 editor….
OK, no problem, now I know!
One question re: the video. I presume where we modify what various CC controller numbers are being sent is in the template.xml file – in the video, starting at time 17:13, I presume the number listed after each modulator name is the number of the desired CC controller, correct?
Thanks.
Excellent, thanks atom!
BTW, one more headache for you: I don’t think the forum "subscriptions" to topics is working – I didn’t get a notification that there was another post as I was expecting, I just happened to check back….
Thanks atom – I know what you mean about the time problem! If you do find some though, I and I’m sure many others would greatly appreciate the screencast or whatever.
Having looked at some of the source files, it seems like building out plugins for additional devices is probably well within the grasp of people with basic coding skills; we just need a little help getting over the initial hump getting started.
@atom – kudos from me too, just getting started, but really cool and helpful project!
As the Digital White Byte mentioned, would be really helpful if you fixed the 2 missing images from the HowTo guide! Thanks in advance….
