seq won't load .mid in standalone - though file is included / Max 7
Hi there at all, my problem seems to be rather simple, yet i could not find any answers in the forums, at least concerning max 7 - so forgive any redundancies please. I have have a patcher which I want to make a standalone of. Inside the patcher, there's a seq object that loads a .mid every time the patcher gets launched - works with a loadbang as long as the .mid is in the same folder as the max patcher.
Yet, building an application seems to be a little more complicated than just adding the filepath of the .mid via the "include file" function. So far, my hands on research had the following results:
If I DO NOT include the .mid file in the standalone at all, the max console (after launching the standalone) reads: "xxxx.mid : no such file in collective" (more or less exact wording) - makes sense, as I did not include it.
Now:
If i DO include the .mid file in the standalone, the max console reads: "seq: cant open xxxx.mid" - this makes me assume - as the "no such file in collective" message is no longer appearing in the max window - that the file has been found, but seq was not able to load it due to any other circumstances.
What am I missing here? Is it more comlicated than just including the .mid? Is it a question of format? (seq loads and plays the .mid flawless within pathcer though) Any hint would be very welcome, as i'm running out of ideas... except of building a sequencer within the patch that uses fixed values (rebuilding the .mid and making it obsolete therefore)....
Anyways, thank you so much for any help!!!
Cheers,
M
FYI, in the meantime found another way using a relative file path / ;max send apppath / receive / combine obj. combination. Thing is that the .mid has to be existent on the harddrive of the user now. I was assuming that including the file in the standalone would make that obsolete. Any input on that would be appreciated (is it even possible?)
Cheers,
M
Any luck with your seq object loading .mid in a standalone? I'm having the same issue.
JB
i dont hav experience with including media files inside the app (and i wouldnt do it anyway) but it should always work to have files inside the search path of the runtime/app you are going to build.
(and, like he found out, by default that is restricted to paths relative to the runtime.)
unlike for vst~ there should also not be any bugs with seq reading files at init (loadbang).
the only thing what could happen is that several attempts to open files (esp the same file, but also different ones) might not work on init because loading files is not thread safe. but that wont work in the patch during programming, too then...
Here it is 2022, anyone solved this? I'm having the same issues.
midi files can not be included into mxf file.
Use absolute path to file you want to read.
You might have luck placing it into search path of standalone
and use read mesage.
support folder works mostly.
thank you, I'll try absolute path.
I have .mid files working inside an exported project but only with [detonate]
[seq] based device won't load the included .mid files for some reason.
the error is also not that it can't find the file, but that it can't load it. So something is off here