Forum Rule: Always post complete source code & details to reproduce any issue!

Search:

Type: Posts; User: h4yn0nnym0u5e

Page 1 of 5 1 2 3 4

Search: Search took 0.01 seconds.

  1. Great. Today has mostly been about tidying up:...

    Great. Today has mostly been about tidying up: I've removed almost all the horrible "50 byte temporary string buffer - should be enough" code, with a side effect that the initial / can be omitted by...
  2. I have faith you'll figure it out! I just...

    I have faith you'll figure it out! I just realised that there could be problem with "mutual nesting": if you have Tab A and Tab B, each can import [an array of] the other. I imagine this could cause...
  3. Just pushed an update to OSCAudio, should be more...

    Just pushed an update to OSCAudio, should be more tolerant of some variations we've used on the dynamic engine addressing. It'll also be less efficient, but we can tweak the rules later... I'm...
  4. This and the above all sound great. Input order...

    This and the above all sound great. Input order isn't massively important, though I guess it means the user having to know how wide the mixer is ... ah, right ... now I remember ... I implemented...
  5. You're right of course. But looking at the latest...

    You're right of course. But looking at the latest code on github there seems to be some sort of intent to provide (limited) wildcards in both. Here's a fragment of code from OSCMatch.c:
    ...
  6. Nothing weird in the design at all. I think it's...

    Nothing weird in the design at all. I think it's the OSC library's bizarre "pattern matching", which sort of works some of the time. Looking at the code it's allowed to have a * wildcard in both...
  7. No, the update interrupt is called 44100/128...

    No, the update interrupt is called 44100/128 times a second, and processes 128 samples (or technically AUDIO_BLOCK_SAMPLES, which is usually set to 128), so about every 2.9ms.

    At the moment I'm...
  8. Eliminate code bloat with SD.h - how?

    This could be the shortest piece of code posted under the Forum Rule ever:

    #include "Audio.h"
    //#include "SD.h"
    void setup() {}
    void loop() {}I could have made it shorter, but that would have...
  9. Quite so :D. Funny how one always assumes the OP...

    Quite so :D. Funny how one always assumes the OP will have properly checked the Really Obvious Possibilities before posting.... But then again, I've been know to fall down a similar hole, e.g. "did...
  10. Had hoped that someone who fully knows what...

    Had hoped that someone who fully knows what they're talking abut would weigh in, but ... apparently not... I'm pretty familiar with the Audio library, not so much (at all) with OctoWS2811. However.
    ...
  11. I've just pushed the repos with the latest Audio ...

    I've just pushed the repos with the latest Audio and cores, using the tag v0.7-alpha. These are my first try to get Teensy 3.x supported, and haven't had much testing apart from a quick go on a...
  12. ...long pause... I meant the WT11. But yes, the...

    ...long pause... I meant the WT11. But yes, the WX11 is pretty cool. Wish I could play it properly.
  13. That's fine as far as it goes, but it's going to...

    That's fine as far as it goes, but it's going to suffer from "zipper noise" at some fade rates because the multiplier is only changed once per audio update cycle. It really needs updating more often...
  14. Replies
    6
    Views
    945

    I've tried following the instructions, and have...

    I've tried following the instructions, and have had success on a Teensy 4.1 by using the fragment posted in https://forum.pjrc.com/threads/66330-Dual-SerialUSB-and-MIDI-config-possible, but for the...
  15. I agree it would be possible to make the Teensy...

    I agree it would be possible to make the Teensy an OSC client, and equally possible to use Ethernet as the transport stream. I've not touched Ethernet on the Teensy as yet, though I do have an...
  16. No, I don't have /subscribe even started yet! It...

    No, I don't have /subscribe even started yet! It just occurred to me that it's present in some implementations of OSC, and would probably be useful. However, like /fs it may not directly be part of...
  17. While I think, and back on topic a bit more (!),...

    While I think, and back on topic a bit more (!), do we want to think about some sort of /subscribe capability? Could the GUI++ be set up to generate those (as defined by the user, of course), and...
  18. I think the grouping is possibly best left to the...

    I think the grouping is possibly best left to the application writer ... though maybe could do it with gain(level,bitmap) for up to 32 or 64 channels, similarly pan() and balance()? Not quite the...
  19. Not at all sure that's better / easier to grasp,...

    Not at all sure that's better / easier to grasp, and certainly harder to implement. It means two extra function names (SetPair and gainP) and an extra array to store the pairNr->chL+chR mapping. The...
  20. Ah yes, I recall a separate conversation about...

    Ah yes, I recall a separate conversation about problems with AudioWaveformModulated - must look into that, since the audio modules seem to be getting added to anyway in this library! Sounds very...
  21. Sounds good, means we can stick with AudioMixer...

    Sounds good, means we can stick with AudioMixer and AudioMixerStereo. I've started updating my AudioMixerStereo (as yet not tested), with the following scheme (very similar to yours):

    pan(ch,...
  22. I've just re-read this, and it's already...

    I've just re-read this, and it's already confusing me ... and I wrote it! I think we could do MtoM, MtoS and StoS (manicksan's three variants) with just two classes, by making AudioMixerStereo do...
  23. Good, that means you should be able to import my...

    Good, that means you should be able to import my JSON! One thing I couldn't find was a way (if there is one) to set the number of inputs shown for a specific instance of a variable-input-width...
  24. Here's a simpler (?) way of doing the same thing:...

    Here's a simpler (?) way of doing the same thing:
    27130
    mixerS now has to expand internally to 11 inputs...
  25. I've called it AudioMixerStereo. Not sure if...

    I've called it AudioMixerStereo.

    Not sure if you'll be able to import this, as I made a couple of custom nodes to allow me to put something like an AudioMixerStereo into the design:
    ...
  26. Excellent news - glad it's working for you. Hope...

    Excellent news - glad it's working for you. Hope you can post in the future about what you've done, and why the dynamic library was useful to you.
  27. Currently it's M0 M1 ... Mn, with the mono inputs...

    Currently it's M0 M1 ... Mn, with the mono inputs being panned across the two outputs using pan(channel, position): position is -1.0 (fully left) through 0.0 (centred) to +1.0 (fully right). At...
  28. I'm just experimenting with a slightly simpler...

    I'm just experimenting with a slightly simpler grouped design:
    ...
  29. No. I'm not 100% sure what the "correct" response...

    No. I'm not 100% sure what the "correct" response is in such cases, though if we're that short of memory I suspect the system would be likely to crash anyway. I did implement getChannels() which...
  30. New suite of stuff pushed to github: please...

    New suite of stuff pushed to github: please update your cores, Audio and OSCAudio to get everything in all its wonderfulness... Note the documentation in #176 is now superseded, the object is now...
  31. OK, I'll change the class name from AudioMixerX...

    OK, I'll change the class name from AudioMixerX to AudioMixer, for now. I'm not 100% happy with that as the name, because it doesn't really tell the user much about the functionality, i.e. that it's...
  32. @manicksan, are you OK with my adding my edits of...

    @manicksan, are you OK with my adding my edits of your your DynMixer code into my Dynamic Audio library?

    I've got it working here, along with a rather kludgy implementation added to...
  33. Understood, but I believe it's preferable to hide...

    Understood, but I believe it's preferable to hide the grim details of the input queue memory allocation from the user, where possible! It's a simple enough fix in the AudioStream library, and it's...
  34. I've very quickly pulled this into my audio...

    I've very quickly pulled this into my audio library, and made some changes to the DynMixer.h file only:


    <license removed for brevity>
    #ifndef DYNMIXER_H_
    #define DYNMIXER_H_

    #include...
  35. I've just pushed to the repos with the latest...

    I've just pushed to the repos with the latest Audio and cores, using the tag v0.5-alpha, and recommend anyone who's trying this out to update. There were some pretty massive problems with deleting...
  36. Added commit 92e164f...

    Added commit 92e164f to the repo just now. You will need the latest Audio and cores for this to be useful, as there were some pretty massive problems with deleting objects that I think I've now dealt...
  37. Just realised, for anyone out there playing with...

    Just realised, for anyone out there playing with this at the moment, that renaming and deleting objects will be broken for the time being...
  38. Easily done!

    Easily done!
  39. Sorry - which design? I quoted from part of the...

    Sorry - which design? I quoted from part of the export of the JSON from post#163... I'm not really using JSON at the moment, though it would probably be good to work up a Python example that can take...
  40. Just took a look at the non-working export - one...

    Just took a look at the non-working export - one thing you need to do for the group paths is include the / separators, as these are valid within group path parameters, and needed for the OSC dynamic...
  41. Turns out, not as hard as I feared... see latest...

    Turns out, not as hard as I feared... see latest commit at https://github.com/h4yn0nnym0u5e/OSCAudio/tree/features/groups. To use it, send /dynamic/crCo,ss<name><path>, e.g....
  42. Thank you! Not sure if it'll be hard, it's...

    Thank you! Not sure if it'll be hard, it's certainly a good suggestion - I just wanted to get the bare bones out as soon as I could, as it's fundamental to being able to make a structured design in...
  43. Phew ... finally. I think I have audio groups...

    Phew ... finally. I think I have audio groups working, please see https://github.com/h4yn0nnym0u5e/OSCAudio/tree/features/groups. For now I've not merged it into trunk as there are probably bugs and...
  44. There’s nothing in there that refers to the audio...

    There’s nothing in there that refers to the audio shield, and because the Teensy 4.x models don’t have a DAC your audio system doesn’t have an object with “update responsibility”. So the audio...
  45. Away visiting family at the moment, so canít test...

    Away visiting family at the moment, so canít test Ö but Ö that looks close to working. malloc() allocates bytes so the external version should have malloc(ninputs * sizeof(audio_block_t**)) - similar...
  46. Glad you found it. The latest commit of...

    Glad you found it.

    The latest commit of OSCAudio (70e49da) should fix the delete crash, as well as allowing use with the old static Audio library - I'm not regression testing that often, as it's...
  47. This looks useful. You may want to start from the...

    This looks useful. You may want to start from the OSCAudioUseMIDI example (where I've started to split out the various functions into separate .ino files within the sketch), and add the file listing...
  48. I'm looking into this ... very similar ideas to...

    I'm looking into this ... very similar ideas to yours, but introducing an OSCAudioGroup object to do a nested linkage to arbitrary depth. Getting my linked lists very tangled, and have to go out now...
  49. @adrianfreed, when you're able to give this some...

    @adrianfreed, when you're able to give this some bandwidth, it'd be good to discuss OSC stuff (maybe start another thread, or on github). Just looked at the outstanding PRs, and have agreed with...
  50. “Should” is definitely too strong a word! It...

    “Should” is definitely too strong a word! It might be useful, though as yet it’s all a bit fluid. It is like advanced MIDI, but much more flexible, and you can use it internal to your application.
    ...
Results 1 to 50 of 248
Page 1 of 5 1 2 3 4