#10

This is great!
I got it working without any problems on my 256.
I’ll let you know if i run into any bugs or anything unusual or unexpected.
Thank you very much for your effort, it’s nice to finally get a bit extra out of having 256 instead of a 128 with the modules.

1 Like
#11

This. Is. Awesome.

Thank you so much for the time and effort you have poured into this and Orca.

Dusted off my 256:

b

1 Like
#12

That’s awesome! is there a 256 mod for white whale? Might be on the look out for a Meadowphysics.

#13

yep, was going to look into modding ww next.

1 Like
#14

Would it be possible to see your sourcecode?
I’m trying to learn and it would be very helpful!

#15

of course, just like the original firmware it’s open source.

here is the branch:

and here is the diff so you can easily see the mod itself:

it’s a pretty straight forward mod, the implementation was intended to be done in the way that would have minimal impact on the original code. will be happy to help with any questions!

#16

one thing i realized i didn’t add was a proper support for non vb 256. is that something that would have enough interest? adding that would result in a lot of duplicated code [or refactoring some of the original code, which i’m trying to avoid].

#17

I have a non vb walnut 256. I’d definitely make use of this, but I’m not sure just me would justify a bunch of your valuable time.

#18

it’s actually not as bad as i thought, should be able to add it easily!

#19

looks like i don’t need to do anything extra for meadowphysics - it calls the same function for both VB and non VB, so you should be able to use this version. for white whale it does have a separate function for non VB, i’ll make sure the 256 mod will support both.

#20

Cool! I give the meadowphysics a try when i’m back to my studio next week.

1 Like
#21

Amazing

I almost sold my 256 so it’s staying for now

@scanner_darkly

I have a DIY 512 and I’m certain it would detect two 256 ?

I’ll check this later and post

super excited to try this with a simmons sds and akai S900 and disting :slight_smile:

should be mucho sample triggering fun :slight_smile:

s

#22

not sure how it will work with a 512, in theory if it reports itself as a grid with 32 columns and 16 rows it should work. i’ll be curious to hear if it does!

#23

Hi,

I think i found a bug… After running a while it detects button presses in the rightmost column in the upper 8 rows of my 256… I recorded a small video. I experienced it sometimes now, and always after my meadowphysics being on for a little while, approx 15-20 minutes or so(not completely sure about how long, but never on startup)
https://vimeo.com/180151871

#24

i’ll take a look (likely won’t be able to do that until sunday).

once it starts happening do any of the subsequent resets of this nature happen faster? in the video it looks like it did it twice within a short amount of time. also, once it happens and if you don’t press any buttons, does it happen again or does it just continue running normally?

#25

yes when it starts happening, it happens quite often.
If it happens and i don’t touch anything, and just keeps running normally i think.
I’ll do some more testing.
I wondered if it was my 256, but haven’t had any other problems with it

1 Like
#26

had it running for hour and a half today, could not reproduce it. tried different rules / button presses / running on max speed. also looked at the code but don’t see anything suspicious.

are you able to test it with the original firmware and see if you’re still getting the issue?

#27

Quite weird here :
the bottom half also reflects the top one (half bright). Is it intended ?

#28

you mean it shows the current playing positions? that’s what the top half does when you’re on one of the 2 control pages (probably so that you can visualize the effect of your changes), and i used the same visualization code for the bottom part. but yeah, i’ve been thinking it’s not necessary on a 256 since you can just use the top half for that. i’ll change it.

anybody else experience the issue @AndersSkibsted reported?

#29

This. On @AndersSkibsted 's video, it doesn’t seem to be the case, that’s why i got even more confused.