Trying to create a new version of an object

#3

what happens if you use int32 instead of int128 (which i don't think exists)

also you put in "frac128" which doesnt exists either. use frac32 instead i think.

#4

Just made a new version with 32 inserted instead of 128, but still not working(comes up as red in talkback window, with no info about what the error might be):

sel fp 128 2.axo (23.5 KB)

#5

maybe some prob with patcher not knowing how to draw so many slots.
also changed your last line to ..-128 but that didnt help.

#6

hmm i deleted a bunch of entries to make it like sel 32 but it is still giving errors.

#7

i think your SHA and UUID are fnurked. gonna take a look

#8

I just made a new version with 64 steps. I think better to start with smaller. Easier to check for errors.... But stil not working. I think values and everything is right, but it still doesnt work. I basicly compared the sel/sel i 16 to the sel/sel i 32 .... and changed all values that was different in the two objects to 64.

Must be some steps I am missing in the process....

New attempt with sel/sel i 64

sel i 64.axo (11.5 KB)

Wishlist of objects
#9

bleh, even if i remove the fp 32.axo and copy paste the fp 32 contents into the 128.axo i get an error.

#10

maybe something wrong with that text file format...

#11

well 31 steps worked. lets try 33

#12

Yes it might be that.

I just tried changing only the name in the first line and saving the .axo object to that name.... And now the object doesnt work. Any change makes the patch not work, so I think I need to try another text editor... I am on Mac...

Any suggestions to what to use instead of TextEdit?

#13

please throw textedit into the well and get notepad+ !

33 steps works here too.
still not sure why i couldn't just copy paste your text into the file and get 64 steps. maybe it breaks at some value.

#14

oh..a mac. throw it away also!

#15

Haha,.. :smile: just bought this one, so it is going to be a while befor that happens.... :smile: Pc might be good for some things.. But when I used to play live a lot I wouldnt trust a pc. On Mac I had both Logic and Ableton running and if Logic crashed Ableton would keep playing and I could just reopen Logic and continue playing.... That would never happen on a pc with out Blue screen of death.. Anyway.. Both have their advantages :smile:

There must be a solution for coding on Mac.. going to look around a bit. Maybe code. Apples own app for coding.

#17

yeah im joking of course. shouldnt matter what you use. not really sure what happened with those files anyway.

im sure there is one or two super awesome text editors that don't introduce weird formatting into files. everyone pretty much uses notepad++ on windows.

#18

https://itunes.apple.com/gb/app/textwrangler/id404010395?mt=12 maybe

#19

Hell yeah :smile:

Really excited about this. Got 33 steps working :smile: going to see if I can make 64 :smile: I looked in the 7bar 64 object and there is not anything different from the 32 steps version to 64 steps versions.. except the step amount off course....

#20

Aaaaannnnd... Here is 64 step version :smile:

Axoloti warns about a few SHA are identical, but it works. At first it opened the 64 step version in every patch i opened that has 32 step version. But then I changed the uuid and the SHA and now it works :smile:

Sooooo happy bout this. Going to make some changes.. Thanks guys for helping me... Using Textwrangler did the trick :smile:

Here you go :smile:

sel i 64.png832x190 8.19 KB

sel i 64.axo (11.5 KB)

#21

Now next issue is making a disp/ibar64 in one lane, so it fits with the 64 steps sequencers. The one that comes with Axoloti has the 64 steps in 4 lanes so you cant put it above the 64 step sequencers to see on which step of the sequencer is being triggered.

I tried using same method as with the sel/sel i 64 version, I changed the values and the name and the uuid tag and the SHA tag, but it doesnt work.

I used the disp/ibar32 at starting point(cause it has only one lane).

Any ideas?

@johannes Is there a reason for the ibar 64 to be in 4 lanes and not one long? Maybe it has something to do with why it doesnt work here?

#22

The code looks like this. A short one:

bar1.png1222x362 53.6 KB

I think I need to change these 3 lines(Sorry cant paste code so I will only paste line number):
Line 2 : change name This works
Line 15: change "bar32" to "bar64" Don't work
Line 20: change "in-32" to "in-64" Don't work

As soon as I change the values in line 15 and 20 the object is not recognised by Axo editor. But changing name is ok.

#23

In src/main/java/axoloti/object/AxoObject.java you can find the legal types of inlets, outlets, parameters, displays and attributes.

The display components int32.bar16 and int32.bar32 show the bits of an 32 bit integer. int32.bar64 does not exist. The object disp/ibar 64 uses 4 int32.bar16 display components.