Axoloti TEST release 1.0.8

#124

I think there may be a bug related to the Glide object in 1.0.8.

Does the following patch loop like it should work, from the attached screenshot?

Screen Shot 2016-03-25 at 17.12.54.png1530x867 74.4 KB

I managed to get it to work once, but there seems to be a problem with the smoothing amount- a value of 0 seems still to produce a pitch glide (where I assume it shouldn't).

After that one time, it appears to compile and upload (log below), but produces no audio, and there's no activity on the two scopes, either.

I've tried connecting a cntrl/button object to the 'en' input of the Glide object, too, with the same result- no output. With nothing connected to 'en', it works, but no glide, obviously.

Generate code complete
Start creating directory on sdcard : /nmpgen3
creating dir: /nmpgen3
Done creating directory
Changing working directory on sdcard : /nmpgen3
Change working directory: /nmpgen3
Axoloti says: file error: FR_NOT_ENABLED, filename:"/nmpgen3"
Done changing working directory
Start compiling patch
Axoloti says: file error: FR_NOT_ENABLED, filename:"/nmpgen3"
Compiling patch... with /Applications/Axoloti.app/Contents/Java/firmware
BDIR = /Users/alx/Documents/axoloti/build
FIRMWARE = .
RM
rm -f /Users/alx/Documents/axoloti/build/xpatch.o /Users/alx/Documents/axoloti/build/xpatch.elf /Users/alx/Documents/axoloti/build/xpatch.bin /Users/alx/Documents/axoloti/build/xpatch.d /Users/alx/Documents/axoloti/build/xpatch.map /Users/alx/Documents/axoloti/build/xpatch.lst
APP
arm-none-eabi-g++ -nostdlib -fno-exceptions -fno-rtti -mcpu=cortex-m4 -O3 -fomit-frame-pointer -falign-functions=16 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -fsingle-precision-constant -Wunused-parameter -DCORTEX_USE_FPU=TRUE -DTHUMB_PRESENT -mno-thumb-interwork -DTHUMB_NO_INTERWORKING -mthumb -DTHUMB -std=c++11 -DARM_MATH_CM4 -D__FPU_PRESENT -H -I/Applications/Axoloti.app/Contents/Java/CMSIS/Include -I/Applications/Axoloti.app/Contents/Java/chibios/os/ports/common/ARMCMx/CMSIS/include -I/Applications/Axoloti.app/Contents/Java/chibios/os/ports/common/ARMCMx -I/Applications/Axoloti.app/Contents/Java/chibios/os/ports/GCC/ARMCMx -I/Applications/Axoloti.app/Contents/Java/chibios/os/ports/GCC/ARMCMx/STM32F4xx -I/Applications/Axoloti.app/Contents/Java/chibios/os/kernel/include -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/include -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32F4xx -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/GPIOv2 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/I2Cv1 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/OTGv1 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/RTCv2 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/SPIv1 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/TIMv1 -I/Applications/Axoloti.app/Contents/Java/chibios/os/hal/platforms/STM32/USARTv1 -I/Applications/Axoloti.app/Contents/Java/chibios/boards/ST_STM32F4_DISCOVERY -I/Applications/Axoloti.app/Contents/Java/chibios/ext/fatfs/src -I. -I/Applications/Axoloti.app/Contents/Java/chibios -Winvalid-pch -MD -MP --include /Users/alx/Documents/axoloti/build/xpatch.h -c /Users/alx/Documents/axoloti/build/xpatch.cpp -o /Users/alx/Documents/axoloti/build/xpatch.o 
! /Users/alx/Documents/axoloti/build/xpatch.h.gch
LINK
arm-none-eabi-gcc -nostartfiles -Tramlink.ld -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16 -mthumb  -mno-thumb-interwork /Users/alx/Documents/axoloti/build/xpatch.o -Wl,-Map=/Users/alx/Documents/axoloti/build/xpatch.map,--cref,--just-symbols=./build/axoloti.elf -o /Users/alx/Documents/axoloti/build/xpatch.elf
BIN
arm-none-eabi-objcopy -O binary /Users/alx/Documents/axoloti/build/xpatch.elf /Users/alx/Documents/axoloti/build/xpatch.bin
Done compiling patch
Start uploading patch
bin path: /Users/alx/Documents/axoloti/build/xpatch.bin
block uploaded @ 0x20011000 length 7564
Done uploading patch
Start starting patch
Done starting patch
Start locking
Done locking
Disconnect request

Here's the patch in question:
nmpgen3.axp (5.6 KB) (requires my nmpgen3 object, which is in the contrib library).

a|x

#125

UPDATE:

I've tried with the math/smooth object in place of the Glide.

In this case, I get the same behaviour I saw before- with smooth at 0, I still get smoothing.

If I try to add a multiplexer to switch between the smoothed and unsmoothed pitch (see screenshot), again it fails to make a sound.

I'm just trying to achieve a switched glide effect, based on a boolean output from the nmpgen3 object. I'd have thought this should be possible. Is it something to do with execution order, perhaps, and not a bug after all?

Screen Shot 2016-03-25 at 18.25.09.png1530x867 75.6 KB

a|x

#126

Seems to work if I swap the 'osc/pwm' oscillator for an 'osc/square cheap'. Dunno why...
Could be a bug with the pwm oscillator, then...

nmpgen3 Cheap Sqr.axp (5.6 KB)

a|x

#127

I'm sorry, i really did not notice the error after the init, and i thought you were referring to the axoloti patcher startup. I apologize for wasting your time, next time i'll be more careful.

#128

no problem @Sputnki .. I recognise its hard on both sides.

just every now and then, Id like to remind everyone, I also prefer making music with axoloti (and my other gear), Im just another community member helping here, its not my job, I'm not paid etc (like it would be for a Native Instrument support guy) , so I kind of appreciate it when others help reduce the amount I have to do to chase these things down.... I view its as a team effort, where end-users are a vital part of that team.

but as I said, I do recognise its not always easy for those reporting issues to know what is important and not... even on my side sometimes I miss the more obvious causes initially :wink:

@toneburst, id guest this is not 1.0.8 specific i.e. probably same in 1.0.6, so I suspect not high priority on 1.0.8 for fixing. (1.0.8 does mean we can update objects between software releases, so not vital its fixed before 1.0.9 is out) - not saying not important, just may not get priority at the moment.

#129

I see. Were you able to confirm it's a bug, just out of interest?

I'm a newb when it comes to using the Patcher, but I think my patch should work, conceptually, at least. The fact it Does work, with a different oscillator object suggests Bug pretty strongly to me.

a|x

#130

By looking a little bit more into it, axoloti changed The names of The objects. Actually i didnt use The : sign, i used the / sign. But axoloti changed The : to /. But Will avoid using Those special characters at all. Just letters & numbers?

#131

I'd avoid both.

The forward-slash '/' character is the path delimiter on UNIX-based systems (including OS X). It can't be used in OS X filenames, but I guess the system replaces them with ':' characters, behind the schenes, while displaying the original forward slash you typed in Finder (but not in other apps like the Axoloti patcher).

a|x

#132

the substituting rule for : / is SLASH, as axoloti substitutes with words, e.g. * becomes STAR.
anyway, I just pushed a change for 1.0.9 that means : becomes COLON.

but yeah best avoid special characters, as there are quite a few that could cause issues.

in 1.0.9 when you use 'add to library' it shows you the filename that is going to be used, so if its still has odd characters, best not to use it ... and if its a useful one, let us know and we can ensure its gets substituted.

#133

Well, me an Axoloti object editor have never been friends. Never worked for me. I make som changes and changes are gone when I close the editor.....I am probably doing something wrong..... So I am still doing custom objects in Text Wrangler and name them there cause that worked everytime. But if it works in new version i will definatly give it a go :smile:

#134

I noticed a little error into the subpatch object dist/hardclip.axs: it does not work, since the +c_2 object inside should be s-rate when instead is k-rate.

#135

@thetechnobear

So, today I had time to change the names of the objects in Finder in OSX. Do I have to change the name of the objects in textwrangler also(the name that is shown in the editor)? Or is it enough to just change the name in Finder?

I dont have any Windows machine so cant really test if they would work on Windows now.

What do you say? :smile:

sel sel.png999x599 97.5 KB

#136

sure, any is fine as long as you stick to numbers/letter for the filename (as factory objects do)
really the filename is not that important, as users don't see it, only the object name which can have other characters.

#137

just a small question :
Is anyone having problemes with the dist/hardclip object in version 1.0.8? Mine seems to emit no sound, so neither does the stomp/distortion subpatch. I don't know if it's this version or before, I was just wondering before going back to 1.0.6 and testing it out

#138

I remember seing someone mention it here somewhere taht they had problems with one of the distortion drive objects.

#139

Also does the Keyboard work in 1.0.8? I load the 11_subtractive_simple.axp and call the Keyboard but it shows the greyed keys. Can't play anything. :confused:

#140

Yes, the keyboard works on my setup (1.0.8 on windows10)

#141

Thanks, I am on linux.

#142

2 posts were merged into an existing topic: Nord Stage 2 midi not working

#143

It does emit no sound because of a k-rate math/+ object put in place of a s-rate object.