New Version 1.0.4

#1

Thanks :wink: for

Had to "rebuid" start.bin inside SD card, would not load patch;

Have been following changes so… only Preferences - Controller Object - have to try ( but Mark explains it here https://sebiik.github.io/community.axoloti.com.backup/t/patch-load-object/628/22)

Keep up the good work.

#2

thank johannes and technobear for.1.0.4 aswell .......to me it looks like win 8.1

one little bug...
Object name comment not found
attempt to create object from subpatch file : objects/comment.axs

#3

oops the (git missing) notification was not intended...
I am assuming this is the windows version?

#4

boolean true win 8.1....just cosmetically

#5

oh, good in macosx

#6

on the "cosmetically" typo topic:

Has MIDI channel -- attibute--

#7

What is the best way to update?

Do I uninstall 1.03 first, and then install 1.04?

#8

no need to uninstall ..also wont overwrite ur axos :yum:

#9

hmz, trying to build from the src package:

[javac] /home/dreamer/Sources/axolotis/axoloti-1.0.4/src/main/java/axoloti/Version.java:1: error: unclosed string literal
[javac] package axoloti;public class Version {public final static String AXOLOTI_VERSION ="fatal: Not a git repository (or any parent up to mount point /home)

Checking out the 1.0.4 tagged release directly does compile.
However I have a lot of issues connecting to the board:

Nov 14, 2015 1:33:15 AM axoloti.USBBulkConnection OpenDeviceHandle
INFO: USB device found
Nov 14, 2015 1:33:17 AM axoloti.USBBulkConnection writeBytes
SEVERE: Control transfer failed: -7
Nov 14, 2015 1:33:18 AM axoloti.USBBulkConnection writeBytes
SEVERE: Control transfer failed: -7
Nov 14, 2015 1:33:18 AM axoloti.USBBulkConnection writeBytes
SEVERE: Control transfer failed: -7
Nov 14, 2015 1:33:19 AM qcmds.QCmdPing Do
SEVERE: Ping: WaitSync Timeout, disconnecting now
#10

Linux? Do you have /etc/udev/rules.d/49-axoloti.rules installed?
The USB handling did not change from 1.0.3 to 1.0.4

#11

Yes, what I've noticed however is that after flashing the new firmware it is best to disconnect the board, then reattach before use.
Otherwise I get the afforementioned errors.

I guess it needs a 'clean startup' before it works properly.

#12

After flashing the microcontroller resets itself, should be equivalent of disconnect/reattach.

#13

You'd think, but apparently not.
Hard reset seems the best method to not get these usb errors.