Help with seq (recording midi). Not working properly in standalone.
mistabu
Nov 20 2023 | 11:37 am
Hi,
Im getting abit crazy with seq when trying to record midi. It does not matter is I use "seq" or "seq seq_sc.midi" objects.
When Im trying to record midi to specific name/location via message, it works properly but only within max msp patcher. After exporting standalone version of the patch it does not work and max console shows a "can`t create" message. But if I click on a "write" message connected to seq it opens a window where I can set the midi file name & destination. I cannot understand why is it happening, I couldn`t find an explication/solution to work with specific file name/location sent to seq in standalone version.
Any ideas? Find attached a patcher to show the issue.
Thanks in advance.
- Source AudioNov 20 2023 | 1:32 pmwhat path is that ???
to target user's desktop path, you use: ~/Deskop/ for that file : write "~/Desktop/singe_Midi 1.mid" if you place standalone object into your patch, then give it unique bundle and Preferences file names ! - mistabuNov 20 2023 | 1:49 pmThanks Source Audio!But the problem still there. It does not create the midi file at my desktop using write "~/Desktop/singe_Midi 1.mid" and I`ve got the same message within Max console ("can`t create")."MacOS :/Users/a/Desktop/single_Midi 1.mid" is the destination and file name sent from an open dialog object.The weird thing is that from within max patcher it works properly creating the midi file using selected file name and destination, but when testing in the standalone app version it does not work.
- Source AudioNov 20 2023 | 2:18 pmI never saw such path, it could be so in new MacOS systems ? Even if your Boot Volume is named MacOS that space before colon and the rest of the path is suspicious ! You could also have privileges problem, your standalone maybe has no rights to write anywhere. why do you use opendialog for saving ? rather use write message to seq an check if it writes the file. otherwise, I'd suggest to report to cycle support. I don't use any MacOS system higher than 10.13, and so can't help you....
- mistabuNov 20 2023 | 2:52 pmIm on Mac OS12.5.I use open dialog because Im recording the audio output from a vst object (loaded with vst instrument), so I want to have the same name and location used to save the audio recording for the midi file. I need to save audio and midi used for the vst object in one-click, so the filepath used to save the audio using record object is used via message to save the midi recorded using seq automatically, without having to do it twice, one for audio and one for midi.The standalone has the needed privileges, it saves the audio files but not the midi files. If I use write message to seq (independently, so I have to introduce the file name for audio and later for midi file again in differnet windows), it opens a destination window to save the midi file and it writes the file correctly. It`s what get me crazy, it works using write message and destination window but not if I use "prepend write" or "write $1" and the file path as a message.
- Source AudioNov 20 2023 | 3:10 pmwhy don't you post your opendialog and following objects that form the path for both audio recording and SEQ storage ?It could be simply that you have nothing recorded into SEQ, which throws error like what you mention, if it is empty and you tell it to write ?
