Martin Klang

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 437 total)
  • Author
    Posts
  • in reply to: Faust problems #2967

    Martin Klang
    Keymaster

    yes you are of course right, sorry, my mistake!

    @stas I get the same errors as you when compiling your generated FaustPatch.hpp (but not for some reason when generating it myself).

    The errors are cleared if I add #include <string> to the top of Source/PatchProgram.cpp.

    Can you try that pls? If it works for you I’ll update the repo.

    in reply to: Faust problems #2964

    Martin Klang
    Keymaster

    faust2 doesn’t have the new memory management option. Is there a reason why you want to use faust2 over master-dev?

    I’m having a hard time reproducing your error. With faust2 tip, OwlProgram master tip, and gcc-arm-none-eabi-5_4-2016q2 I still get no compilation errors.

    in reply to: Faust problems #2961

    Martin Klang
    Keymaster

    #including it before should work because the headers are only included once.

    What branch of faust are you using?

    in reply to: Faust problems #2959

    Martin Klang
    Keymaster

    I thought changing the include order would fix it. You can try putting #include "Patch.h" last in the includes.
    Or you can try adding #undef min, #undef max, #undef abs after the Patch.h include.

    in reply to: Faust problems #2957

    Martin Klang
    Keymaster

    I think it’s just a clash with the include order. We define max() and min() macros for patches to use – we probably shouldn’t.

    in reply to: Faust problems #2952

    Martin Klang
    Keymaster

    The FAUST poly midi code looks great, but I think we will have to roll our own. The FAUST version uses STL (std::map, std::vector et c) which is a bit too heavy for embedded use.

    FAUST poly-dsp.h uses a method of processing in slices which is a really nice way to get sample accurate parameter changes e.g. for note onsets.

    in reply to: powering the modular over USB #2950

    Martin Klang
    Keymaster

    hello!

    On the back of the OWL Modular, on the main board, there is a 3-pin header which selects boot mode, and another 2-pin header. If you connect a jumper across the 2-pin header you will be able to power the digital board over USB.

    However, bad news: this doesn’t power the analogue circuitry, which runs from the +/-12v supply. This means that the audio inputs and outputs, CV and ADC won’t work. You can talk to the OWL over USB MIDI, but you won’t get sound out of it and the parameters will be stuck in the max position.

    What you need is really +12v and -12v going into the OWL.

    in reply to: New FAUST Release #2946

    Martin Klang
    Keymaster

    Here’s a teaser from Romain Michon’s work-in-progress DX7 emulator: https://hoxtonowl.com/patch-library/patch/DX7_Brass_Orchestra/

    It uses dx7.lib from the current FAUST development branch. Not only does it emulate a DX7, Romain has also created tools to convert existing DX7 sysex presets to FAUST patches, which will then run on the OWL. Really looking forward to see this develop further!

    in reply to: Faust problems #2943

    Martin Klang
    Keymaster

    That’s odd, I’m not seeing the same error.

    I’ve just updated to latest faust2 branch, Version 2.1.1

    What version of the gcc toolchain are you compiling with?

    I’ve pushed a small change to OwlProgram which might help, try pulling and recompiling (changed the include file order).

    in reply to: Faust problems #2939

    Martin Klang
    Keymaster

    So to receive midi note messages in faust it seems you make a slider or button for each note.
    The only use of midi:key{on,off,press} I can find in the examples is in midiTester.dsp and it only seems to display the
    value pressed.
    Am I right in assuming that to handle all MIDI notes you would need 128 voices running in parallel, unless you use the experimental mute branch of Faust?

    The CC handling is nice. Control change messages are already mapped to OWL parameters so not sure we need [midi:ctrl]. Could add support for all 40 MIDI-enabled OWL parameters though.

    Regarding push output: yes, synchronising outgoing button/gate changes to the audio stream is on the firmware todo list.

    in reply to: Faust problems #2938

    Martin Klang
    Keymaster

    ok great – I’ve just pushed some changes I’ve done to OwlPatches/Faust, so make sure you pull.

    in reply to: Faust problems #2935

    Martin Klang
    Keymaster

    gate/button output ->
    I’ve pushed an update with a foreign function that you can use like this:

    
    push = ffunction(int owl_pushbutton(int), <owl.h>,"");
    process = hslider("Frequency[OWL:PARAMETER_A]",0,0,1,0.01) : int : push;
    

    (idiot patch, sorry!)

    The return value is simply the current state: 0 or 1. Any non-zero value turns the LED red and gate on.
    The function is called every sample, but registers changes which are propagated to the firmware along with the current sample count. Should be very efficient and accurate.

    I’ve done a bit of testing with the latest faust2 and it seems pretty solid.
    @stas if you are using faust2 let me know if you come across any problems.

    If there are no obvious issues I’d like to push the latest faust2 to the live server, and update our sample patches. Help with the latter would be much appreciated!

    in reply to: OWL pedal v2 ?? #2927

    Martin Klang
    Keymaster

    Good to hear your feedback on this.
    We’ve been doing some prototyping with a newer processor, bit more ram and flash, and a better performing codec with more dynamic range. Early days still, and these things take time, but it’s really good to hear what is important to you.

    Changing patches was always a tricky subject, and true bypass is one of these things that people have strong opinions on.

    If/when we make another pedal I’d love to add a momentary, soft touch foot switch and maybe relay bypass too, but it is difficult to find reliable, affordable components that will fit our build.

    in reply to: [Sharing is fun] – Gen code #2926

    Martin Klang
    Keymaster

    Great stuff, thanks jayrope!

    in reply to: Faust problems #2924

    Martin Klang
    Keymaster

    Edit: I was wrong about tables being generated for sin or other math calls. Certain oscillators e.g. osci will generate tables. But the default osc will not.

    Incidentally sin and cos calls are very efficient on the OWL, as we have implementations optimised for the hardware.

    Foreign functions – I didn’t know about these. Looks interesting, we can probably use them to set output parameters.

Viewing 15 posts - 16 through 30 (of 437 total)

Latest News

Links

Follow us on Twitter