Nth logik

i realize it's been a while since i've been here but,.... i have a few

ideas about some kind of autosaving feature i'd like to create. i've built various projects over the years using max/msp though, there is stil a few things i havn't been able to figure out. i realized i might have asked this type of question some time ago but i don't think i received a str8 forward answer. i was wondering if anyone could tell me how i could load a wave file from a certain folder then with the patch, save its location inside the patch as a config file/thispatcher obj/preset obj/etc. i want to be able to load a wave file inside a patch to act as a user defined sound with however i'll use it, and then when the patch loads next time, to have it still be resident and ready to use.

i realize it's been a while since i've been here but,.... i have a few
ideas about some kind of autosaving feature i'd like to create. i've built various projects over the years using max/msp though, there is stil a few things i havn't been able to figure out. i realized i might have asked this type of question some time ago but i don't think i received a str8 forward answer. i was wondering if anyone could tell me how i could load a wave file from a certain folder then with the patch, save its location inside the patch as a config file/thispatcher obj/preset obj/etc. i want to be able to load a wave file inside a patch to act as a user defined sound with however i'll use it, and then when the patch loads next time, to have it still be resident and ready to use.


question-about-patches-w-autosaving-feature-loading-wav-files

A simple way of doing it might be to save the path in a coll with "save data with patcher" enabled. then use loadmess to retrieve the info and straight into your sfplay~ or whatever you are using. if there is no data present in the coll, there is no output and your patch won't blow up on you.

does this make sense? did I understand the question correctly?

yes that makes very good sense. i could try that out and see how well it works,though, i don't know if i could load that long mesh of code you have there underneath your message as a patch, i'm using an older version (4.55)

any chance you could provide a backward compatible translation of it ? i'd

yes that makes very good sense. i could try that out and see how well it works,though, i don't know if i could load that long mesh of code you have there underneath your message as a patch, i'm using an older version (4.55)
any chance you could provide a backward compatible translation of it ? i'd
be ever so thankful.


i tried using the coll idea w/ loadmess & tried saving it as a plugin then

i tried loading the plugin in my sequencer,.... it does not work properly.

actually i have a patch that's all set up with loading a file path to a message box. it reloads the new sound file when the patch is saved in the max environment but when i render the patch to a plugin it only loads the last patch/max environment saved sound file. i really wish i could find a way to get around/fix this. because i have a really serious idea for a custom drum machine i want to build with max, but this problem is annoying.

i tried using the coll idea w/ loadmess & tried saving it as a plugin then
i tried loading the plugin in my sequencer,.... it does not work properly.
actually i have a patch that's all set up with loading a file path to a message box. it reloads the new sound file when the patch is saved in the max environment but when i render the patch to a plugin it only loads the last patch/max environment saved sound file. i really wish i could find a way to get around/fix this. because i have a really serious idea for a custom drum machine i want to build with max, but this problem is annoying.


here is a max 4 version of what I had above. I have never gone the plugin route so I am not sure what happens there. but in theory this should work, though it might need some tweaking.

i had to add the following code for it to even load properly into my max/msp:

___________________________________________

i compared the code you have there with a saved *.pat

that i had in my files & found out those lines were

what was needed to complete it/load it successfully.

upon rendering it as a plugin, it still didnt work.

thank you for your effort in helping me trying to

solve this problem, i guess i'll have to think it

through more carefully or think of some other way to

accomplish it. i'm not sure how thats going to happen.

thanks again for helping me, though if you can think of

anything else/another way this could possibly work,

max v2;
#N vpatcher 0 0 1024 702;
___________________________________________
the code up above inbetween these lines:
___________________________________________
and the last line of code 

#P pop;
___________________________________________
i compared the code you have there with a saved *.pat
that i had in my files & found out those lines were
what was needed to complete it/load it successfully.

upon rendering it as a plugin, it still didnt work.
thank you for your effort in helping me trying to
solve this problem, i guess i'll have to think it
through more carefully or think of some other way to
accomplish it. i'm not sure how thats going to happen.
thanks again for helping me, though if you can think of
anything else/another way this could possibly work,
please let me know.  

i'm guessing creating plugins is similar to creating standalones, in which case i don't think it's possible to have colls save data with the patcher.

the solution would be to write to and read from a file on disk, instead of embedding in the patcher.

robthrich: the solution would be to write to and read from a file on disk, instead of embedding in the patcher....... i would think it would have to be something like a group of componentry that could internally record the loaded file path & while in plugin form upon being loaded into a VST host, the sound will instantly be there when the patch as a plugin loads into the sequencer & is ready to use without having to manually reload the sound. if i could get it to work with a PluginParam object, that would prolly work a whole lot better. however that could happen, i can't seem to load/save a determined file path while its within my VST host before/after saving it with a song file. i have a verson of this type of idea built recently, it does work right within the max environment, however, it does not work correctly within my VST host which is where i want it to work.

hi i realize it's been a while since i've been in here to respond to

most/any msg's,... i think i recently figured the save loadSND file thing out that i was trying to accomlish. a big thanx goes out to all who lent a hand, thank you very much. holy moley,.... i just realized this topic is 4 months old. oops.

hi i realize it's been a while since i've been in here to respond to
most/any msg's,... i think i recently figured the save loadSND file thing out that i was trying to accomlish. a big thanx goes out to all who lent a hand, thank you very much. holy moley,.... i just realized this topic is 4 months old. oops.


question about patches w/ autosaving feature loading *.wav files ???