@ongo wrote:
I mean obviously the tempo info is simple , but sending Start/Stop remotly is my question 😳
START Timeline:
STOP Timeline:
START Individual cursor:
STOP Individual cursor:
REWIND the Timeline:
N.B. Some of these are not documented, which means the Iannix Lords, like any authors with not-yet-documented APIs, could change the syntax at some point in the future.
hth,
–Bob
No, there are no inputs with those names in my Ableton preferences. they are greayedf out in the track strip.
I have a device that seems to be expecting OSC messages, that does not work either.
Nice one AvantGuy
feel slightly silly now seeing how simple it is really !!!
I have midi yoke installed and noticed that on startup Iannix states that midi in was found at midi yoke 1. How can I check the midi ports that Iannix chooses? Does midi yoke interfere with it?
Hello, sorry for possibly stupid question but I searched through documentation and I didn’t find an answer.
How do I change the background, or import an image to inside iannix?
I also would like to thank you for creating such an amazing tool, I am a graphic design student and I am researching how grids and typography can be turned into sound, and your app is very useful for that!
Cool, thanks for the info! Already had a look yesterday night on those LObjects. I think though I have figured out a solution. Will try and see! 😉
Thanks again!
Sorry I can’t help very much because I don’t have M4L. I only have a freebie copy of Live Lite I got bundled with an interface I bought a few years ago. Even though I cannot run M4L devices I’m a curious sort, so I loaded up Iannix’s Live-set with my copy of Live Lite 8 and this is what my channels look like:
I see that “Iannix_out” is instantiated as the MIDI-In for both channels, so if you have M4L, I would expect it to be receiving MIDI messages from Iannix running “Simple MIDI example.nxscript“. I know for sure that score generates MIDI messages. However, unlike the example screen shots provided by Iannix, I found no way to get those ports to appear in the MIDI Preferences. I do not know why — maybe that’s a function of M4L. Hopefully one of the Live-8/M4L users will see this thread and help.
No, MIDI Yoke should not interfere, and if I were you and I had no luck instantiating ports via those Live channels, I would experiment using Yoke as the buss. But first I’d try to get one of the M4L users here to help out because none of them mentioned using a MIDI inter-process buss like MIDI Yoke or NTONYX, so I’m guessing Ableton Live can instantiate MIDI ports via its own virtual devices.
–Bob
One or two of the sample scores has a background image. Just have a look at their scripts and you’ll see how it’s done. Also note that you’ll find the matching image files, such as Xenakis-Metastaseis.png, in the distro folders.
Cheers,
–Bob
Hi/bonjour,
I am interest by your sequenceur and the osc protocole to synchronise animation and sound.
I ‘d like to run iannix to send osc to processing and to usine (in a single pc). It seem that only one can see messages, not both in same time.
I know the question is more about osc than iannix, but if someone have knowledge in this erea?
A suggestion on tranport fonctions: it would be nice to make smaller loops to isolate parts of whole motion, when only a small patern is interesting. So loopBegin, loopEnd points, and few memories. Or a way to adress the head player position, (in osc? to control that from Usine).
Have a nice day, Cyrille.
I tried working with the midi yoke ports to no avail, maybe there is a max4rlive dewvice that needs to loaf for those 2 ports to be recognized. Have not madew much progress.
Hey Team. Having unexpected quits on launch on 10.6.6 as well. Looks like a Qt problem? Not sure whats going on here – have un- and re- installed Qt, Dev tools, everything. No dice. Here’s the crashlog:
Process: IanniX [33417]
Path: /Applications/IanniX/IanniX.app/Contents/MacOS/IanniX
Identifier: IanniX
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [167]
Date/Time: 2011-07-02 16:04:02.093 -0400
OS Version: Mac OS X 10.6.6 (10J567)
Report Version: 6
...
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 000000000000000000 0 + 0
1 QtCore 0x00000001013cf566 QFontLaoCodec::convertFromUnicode(QChar const*, int, QTextCodec::ConverterState*) const + 3702
2 QtCore 0x00000001012d1550 QTextCodec::fromUnicode(QString const&) const + 32
3 QtCore 0x00000001012aa923 QString::toLocal8Bit() const + 51
4 QtCore 0x0000000101378247 QFSFileEngine::open(QFlags) + 1207
5 QtCore 0x000000010137fae9 QFSFileEngine::fileName(QAbstractFileEngine::FileName) const + 1833
6 QtCore 0x00000001012b2533 QDir::canonicalPath() const + 51
7 QtCore 0x00000001012c9d74 QCoreApplication::libraryPaths() + 372
8 QtCore 0x00000001013a4aec QCoreApplication::init() + 204
9 QtCore 0x00000001013a4c01 QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) + 49
10 QtGui 0x00000001006147a3 QApplication::QApplication(int&, char**, int) + 83
11 IanniX 0x00000001000680a0 IanniXApp::IanniXApp(int&, char**) + 48
12 IanniX 0x00000001000689bc main + 28
13 IanniX 0x0000000100005524 start + 52
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff806d216a kevent + 10
1 libSystem.B.dylib 0x00007fff806d403d _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff806d3d14 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff806d383e _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff806d3168 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff806d3005 start_wqthread + 13
Thread 2:
0 libSystem.B.dylib 0x00007fff806d2f8a __workq_kernreturn + 10
1 libSystem.B.dylib 0x00007fff806d339c _pthread_wqthread + 917
2 libSystem.B.dylib 0x00007fff806d3005 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x000000010162de80 rcx: 0x0000000101630638 rdx: 0x00000000ffffffff
rdi: 0x0000000101406090 rsi: 0x00000001014022ec rbp: 0x00007fff5fbfeea0 rsp: 0x00007fff5fbfee28
r8: 0x00000001015064e8 r9: 0x00000001016fc0a4 r10: 0x0000000000000005 r11: 0x0000000101630630
r12: 0x00000001014022ec r13: 0x0000000000000000 r14: 0x00000001016155d0 r15: 0x0000000000000030
rip: 0x0000000000000000 rfl: 0x0000000000010246 cr2: 0x0000000000000000
Iannix worked great before I upgraded to Snow Leopard and then blammo… unexpected quits. I thought I might try compiling from the source, but the Qt opensource SDK installer ALSO quits on launch. 😡
Any ideas?
@mrgosh wrote:
Hey Team. Having unexpected quits on launch on 10.6.6 as well. Looks like a Qt problem? Not sure whats going on here – have un- and re- installed Qt, Dev tools, everything. No dice. Here’s the crashlog:
[…]
Any ideas?
Just to double-check: Is this your own build, or did you install from iannix_mac__0_8_21.dmg ?
–Bob
If I understand you correctly, this should be no problem, so long as you can set Processing and Usine to different receive socket ports. Except: You did not say whether you must have OSC messages from the same Iannix cursor to send to both programs. I think that’s not possible with Iannix’s current features, but it is definitely possible if you had a Max or Pd patch in between to receive messages on a single port, then regenerate two separate OSC messages on different ports for Processing and Usine (assuming perfect time-synchronization is not required). If you can use separate Iannix cursors, you’re golden. Also I think you could instantiate two Iannix cursors on the same curve at the same position and assign one to transmit to Processing, and the other to transmit to Usine (a sort of jury-rigged solution to the single cursor requirement, so long as Iannix keeps them in sync).
Example, for a single cursor…
setmessage current 150, osc://127.0.0.1:2001/cursor cursor_id cursor_value_x cursor_value_y
…where “2001” is the port number.
I hope that helps.
Cheers,
–Bob
I’m trying to run from an install of the latest release, yeah. Not building from source.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |