In my experience, that 0.8.21 Iannix build runs perfectly on OSX 10.6.7, so there might be something anomalous in your installation.
Did Iannix crash on its very first invocation following your upgrade from 10.5, or were you able to open a score or do some edits before it began crashing on launch? I’m wondering if it is attempting to load a file that is corrupted (sometimes apps in early beta don’t have all the input validation in place, and bad data might cause an out-of-bounds access). To eliminate the possibility of a bad startup file, you might try temporarily relocating your data out of the “Project” subfolder so Iannix will not find anything to open upon launching.
When you upgraded to 10.6, did you do a clean install or an upgrade install? I don’t have any particular issue in mind, but if you did an upgrade, I wonder if some kind of corruption of your app occurred. If you haven’t already done so, it might be worth your time to reinstall Iannix.
Yes, from your stack trace, it does look like it was in a QT call before vectoring through address zero, but 90% of the time an app built on QT will be inside a library call. The invalid access comes out of the Unicode conversion call, and that might be while parsing the name of the default score file. It is unlikely to be a “QT problem”, per sé, because all of the QT runtime support required by Iannix is inside of iannix.app — your QT dev tool installation should have no bearing on this.
@mrgosh wrote:
I’m trying to run from an install of the latest release, yeah. Not building from source.
Cheers,
–Bob
Ok guys Im very happy to present and share with you the final version.
Download link and info:
http://www.softcore.net.gr/IannixSequencer/
No reason to feel silly. I looked at the source code to get one or two of those :–)
Cheers,
–Bob
@ongo wrote:
Nice one AvantGuy
feel slightly silly now seeing how simple it is really !!!
Hmmm, Ok. So the plot thickens!
After double and triple checking that all my other software would still work, I updated to 10.6.7 and I’m still getting crashes. My update from 10.5 to 10.6 was a clean install; all subsequent updates have been combo updates (the ones recommended by Digi since I use ProTools all day for work).
The crashing was instantaneous on my upgrade to 10.6. There was no period where I would work and Iannix would crash. And actually I remember teaching a MaxMSP class in which my machine running 10.5 ran Iannix fine and none of the student computers running 10.6 could run it. Didn’t check the crashlogs! Wish I had now.
Anyway, after updating 10.6.7 I also tried running every Mac release of Iannix. No dice. It’s a crash party, and everyone is invited. Removing default project files had no effect.
Now get THIS: Nothing Qt works anywhere on my system. The Online Qt SDK installer quits on launch (downloaded this in an attempt to build Iannix from source). All the Qt Tools (creator, assistant, etc) all quit on launch (and they all cite converttoUnicode in their crashlogs). This has not always been the case, but I can’t say when exactly this began happening since I do not regularly use Qt anything. Anyway… THIS problem seems to be all over the net (http://bit.ly/ms2C0T, http://bit.ly/lokjNl). Seems more and more like these might be related?
This might no longer be a “Mac OS X compatibility” issue, but a my-machine-specifically issue. I’m gonna set about deactivating large groups of fonts just for fun? See if I can’t track something down, hopefully save someone this headache in the future.
…related? I think you might be teasing us with an understatement :–) It sure does look related. A comparison of your crash dump with that QT bug report crash dump is more like twins than kissing cousins. Both crashes occur very early in the app startup sequence. I mean, when you can see the entry to main() less than a dozen stack frames before the crash, you *know* the app is still cranking its engine when it dies. Plus, they both croak from that Unicode call (well, you got one more stack frame before death than did this other event, but that might just be a difference in QT versions and some kind of function re-factoring QT might have done).
It’s looking to me like this issue results from a combination of a particular hardware configuration and OSX 10.6, based on the problem-free experience I’ve had with Snow Leopard. Just what is your hardware? Mine is a first generation Macbook with RAM maxed out.
Have you applied all CMOS patches to your hardware? You might want to ensure you’re totally up to date with system patches.
–Bob.
If I had M4L I’d be running this right now! But just through taking in the video, I’d say this project is an enticing way to indicate the potential of Iannix in combination with other software. You must have solved your OSC denial-of-service message cloud problem :–)
Cheers,
–Bob
Understatement be my curse!
I’m on a 2.8Ghz MBPro5,1 4G ram (max).
Found some troublesome fonts and killed them but that didn’t make any difference (it was a longshot anyway, I know). My SMC and bootrom are both up-to-date. The only thing I’m not up to date on is OS because digi hasn’t qualified 10.6.8 yet (of course).
This is one hell of a mystery – on both the Iannix and Qt-in-general fronts.
EDIT: I wonder if its possible that this is a 32-bit v 64-bit problem. That might set off all these flags… Bob, is your machine Core2Duo or no? Mine has 1x 64-bit core.
One more forum in ‘inglish’ for french musiciens.
You help!
That you say confirm things i observed. I’m not in Max and Pd, but i think it’s possible to do a relai patch in Usine to resend message in another adress. If not, double iannix objects is a solution.
Thanks.
Salutations, Cyrille.
I hope I don’t have to start reading the IanniX source code to answer the following:
I would like my IanniX score(s) to send nb_curves or nb_cursors to my Supercollider patch(es). This would be preferred to matching the number synths by hand every time I run or modify a score.
Where’s a good place to encode this info. Certainly, don’t want to carry it around in every /cursor, /trigger, etc., right?
So IanniX also SENDS “play” when user presses the play button. That seems like a sensible spot in which to indicate how many synths to play. Is there a way to append arguments to “play”?
thanks,
–dick
Hi!
Do you download the last version of IanniX? Because in the last version, we included a transport message that sends
osc://127.0.0.1:57120/transport status nb_triggers nb_cursors nb_curves
on Play and Fastrewind. For example, on play, it sends :
osc://127.0.0.1:57120/transport play 50 50 50
.
You can customize this message in the inspector>network tab.
@Guillaume wrote:
Do you download the last version of IanniX? Because in the last version, we included a transport message …
I must have looked at that ten times; didn’t even realize it was there 😳 !
@Guillaume wrote:
Hi!
Do you download the last version of IanniX? Because in the last version, we included a transport message …
Hi Guillaume,
Yes! I had downloaded that. I noticed that the transport message carried some numbers in it, but hadn’t figured out what they were. That’s great, exactly what I wanted to do. Will this feature find its way into the documentation, do you think?
–dick
Hi Guillaume,
In another thread you mentioned:
@Guillaume wrote:
… in the last version, we included a transport message that sends
osc://127.0.0.1:57120/transport status nb_triggers nb_cursors nb_curves
on Play and Fastrewind.
This is so great. For those of us using SC, it means we can have the OSCresponder listening on play figure out how many synths to activate, rather than coding the number in the SC patch as the ones you provided do. As I mentioned in the other thread, we could tumble to these features quicker if they were documented.
By the way, I think there is a bug in your “gendy” patch. the responder for cursors assigns an ordinate (X-axis) value to a variable that seems to think it’s an abscissa (“Y”). If you use that to assign frequency, it won’t do the expected. Perhaps you intended to supply us a friendly puzzle?
thanks for your support!
–Dick
The Ardour DAW responds to OSC messages, so I tried to set it up to receive this message from a IanniX trigger :
osc://127.0.0.1:3819/ardour/add_marker
The message is sent when the cursor passes the trigger, I checked it in the Monitor, but Ardour isn’t getting it. Do I have the correct message format or have I left out something ? It’s supposed to drop a location marker into Ardour as it plays.
The Ardour address and message code are correct, AFAICT.
Suggestions ?
Best,
dp
Reply to self: IanniX is now working with Ardour3, thanks to some help from Paul Davis at #ardour on Freenode IRC. The correct message format requires my non-local IP address and the access_action command, like so:
osc://192.168.1.103:3819/ardour/access_action Transport/Forward
A Trigger with this message will start playback in Ardour. I’ve just started to experiment with IanniX + Ardour, the combination looks exciting. 🙂
Best,
dp
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. |