• RetroMaximus

    Yes it was me using delays but I made it a point not to anymore I removed all that I come across. There might be something remaining. Ill take a look

    posted in technical issues read more
  • RetroMaximus

    I made one changes to the pattern and sequencer selector to use banks so instead of having 64 buttons visible there will be only 16 trying to make Overblast less expensive as a whole.

    While testing i was able to disconnect [pd OBSendSteps] and the index value for the sequence and pattern can be seen changing instantly as it should.

    But now that I have made those revisions and reconnected [pd OBSendSteps] I am getting a bunch of "lag". So I'm not sure why this is happening but when [r checkedpadnum] changes the sequence toggles should update with whatever is in the txt doc. But its not and the process of unpacking 32 values seams to take a long time. Is there a more efficient way of unpacking these values?

    I thought this might be a case of disconnecting and reconnecting the highlighted portion of the screenshot but that did not help I'm still getting a long delay after a new pattern or sequence is selected.

    If you feel the need to see more I provided a link to the whole patch via github
    https://github.com/RetroMaximus/OverBlast-Alpha/blob/master/OverBlast-Alpha.zip

    image.png

    posted in technical issues read more
  • RetroMaximus

    I just updated the repository with the latest version of the patch it is still a little broken but I feel like im making progress and getting a lot done now. :)

    https://github.com/RetroMaximus/OverBlast-Alpha

    posted in technical issues read more
  • RetroMaximus

    sweet baby jesus i had the [f] connections swapped. The trigger: can only convert 's' to b or 'a' errors are gone. thats one bug off the list. wheeew!

    Thank you once again

    posted in technical issues read more
  • RetroMaximus

    First i just noticed i should have removed the underscore from the [get_ind< [get_patt< [get_reps< and [get_state< messages in OBsPattItem.pd im still getting errors but things are changing.

    image.png

    posted in technical issues read more
  • RetroMaximus

    I was stumbled on to where the errors stems from. Im not sure what im doing wrong tho.

    image.png

    I do have a github with the project currently but i do have to update it with the most recent fixes other then what im dealing with now. Im going to play around with this a bit more for a few hours see if i can figure it out and ill update the repository either way and post the link.

    posted in technical issues read more
  • RetroMaximus

    So if i was to give the [tmppatch] all the correct test data and no red errors appear i can eliminate that pd patch move on to whatever it is connected to (if it might be a subpatch) to look at its value and see if its the correct obj type.

    posted in technical issues read more
  • RetroMaximus

    Ive been doing exactly that and i can seam to find the inlet that wants a float.

    So in the original post i ran into the error "inlet expected float but got list" that gets overwritten some so i cant seam to cntrl + mouse to go to the last error. It says the error cant be found tho the screenshot does not.

    So i was thinking if i could print out whatever is coming from any obj i could see the its contents and have a better idea of which inlet to look for in the overall patch. The problem is I have no idea where the inlet is.

    In theory I was hoping this would breakup the string of errors with printed obj contents. Or maybe if the last thing was a triggered bang or the value of a floatatom ect.

    posted in technical issues read more
  • RetroMaximus

    I have a understanding of whats going on now with your patch and I was able to mash this together. I can see a connection being made. Now i cant seam to figure out how to get rid of the [tmppatch] object and use the highlighted portion instead.

    The purpose of this is to get the latest temp file that was created. At the moment the PrintDebugger.pd patch has to be reopened to view the [tmppatch] file.

    I tried to connect [obj 10 10 tmppatch] to the right outlet of [textfile] but pure data seams to lock up. Also If clicked [obj 10 10 tmppatch] manually I do see it added to PrintDebugger.pd I need it to be automatic as soon as a new temp file is created.

    Any idea where to connect it?

    image.png

    posted in technical issues read more

Internal error.

Oops! Looks like something went wrong!