Squinktronix Arpeggiator discussion thread

But I backed up a level and downloaded Arpeggiator 2.0.5 “pre-release”. Did I grab the wrong one this morning.

I think I’m using the same version as k-chaffin does

My problem may be that rather than using that link, i backed up a level and downloaded the 2.0.5 pre-release which was dated yesterday whereas the link I and Squinky just sent is dated 5 days ago.

Actually , I am confused now, but 2.0.5 is what he announced above last night.

2.0.5 is right, I think github is confused about version, probably because I named them the same thing.

I’m not going to say very much here as things are just confusing. It appears that another plugin that I just subscribed to in the library on Saturday may have been the crash culprit. I’ve sent the log file to Squinky for him to weigh in on whether he thinks it was another plugin.

Having given this caveat, what is the likelihood that a library plugin could cause a crash in a patch in which that plugin is not used? If no one has seen such, the misinterpretation is likely on my end.

Well, the log file does not implicate any plugin in the stack trace. It was probably just coincidental that the last plugin I have added to my Rack was the last to log some autosave info just immediately before the crash. All of the crashes seem in some way related to autosave.

I’ve decided not to submit these new modules to the VCV library, but current/final builds may be found here: Release old Release · squinkylabs/SqHarmony · GitHub. These are built with the “official” rack toolchain.

These should have all reported bugs fixed, “final” documentation, including block diagrams, and panels that are somewhat less ugly than before.

This code is now on the “main” branch, so anyone already building a different branch should switch back.

7 Likes

How come you nuked the repo?

2 Likes

It’s not nuked, it’s private. After the most recent time that Andrew threatened to perma ban me for bad behavior I took down all my educational stuff and that unfinished repo.

1 Like

Totally up to you what you do of course, but that does sound a bit like a retaliation directed towards the wrong people.

Your educational stuff is/was excellent - but if there’s one person who probably wouldn’t learn a great deal from it, it’s Andrew :slight_smile:

5 Likes

Is the Portable sequence document available anywhere, since i now have a broken link for that in my Impromptu manual. If ever it is not, would it be possible for you to send me the .md file so that I can host it on my Impromptu github, if it’s ok with you of course. It would be a shame for the “standard” that we developed with Richie to not be public anymore.

for sure, will do!

Here it is. This is just a zip file that I changed the extension on to try and fool this bbs system: clipboard-format.zip.vcv (3.2 KB)

1 Like

Thanks Bruce!

I think that’s tragic Bruce. Do consider making that valuable resource available somehow.

Marc, if you do publish the Portable Sequence document, please let me know and I’ll link my documentation to it. If you decide against it, also let me know and I’ll publish it in the Entrian Audio repo.

Bruce, thanks for the document. But also, you’re punishing the wrong people (including the Bruce that put a lot of valuable time and effort into all that stuff).

Is there a list anywhere of which sequencers support the portable sequence?

Hi Richie, apologies for not pinging you it slipped my mind :frowning: but here is the link:

Thanks for getting in touch on this!

We had started a list at the end of that document, which you can see here, and if ever others have implemented the format, we can definitely uptate it :slight_smile:

1 Like

Thanks, and no problem! I’ve updated my documentation to point to your repo.

2 Likes