Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 01 2019 13:42
    chrsbats starred Buzztrax/buzztrax
  • Oct 27 2018 19:12
    lb90 starred Buzztrax/buzztrax
  • Oct 21 2018 11:14
    spheenik starred Buzztrax/buzztrax
  • Oct 18 2018 07:42
    ensonic commented #77
  • Oct 17 2018 16:26
    panoptic starred Buzztrax/buzztrax
  • Oct 13 2018 13:43
    trebmuh synchronize #77
  • Oct 13 2018 13:41
    trebmuh opened #77
  • Oct 13 2018 12:48
  • Oct 02 2018 22:22
    trebmuh opened #76
  • Oct 02 2018 22:19
    trebmuh closed #75
  • Oct 02 2018 22:19
    trebmuh commented #75
  • Oct 02 2018 19:43
    ensonic assigned #74
  • Oct 02 2018 19:43
    ensonic commented #74
  • Oct 02 2018 19:42
    ensonic commented #75
  • Sep 27 2018 10:54
    plater commented #74
  • Sep 27 2018 10:13
    plater commented #74
  • Sep 25 2018 23:54
    trebmuh commented #75
  • Sep 20 2018 18:11
    sonejostudios starred Buzztrax/buzztrax
  • Aug 30 2018 10:58
    trebmuh commented #75
  • Aug 28 2018 21:35
    trebmuh commented #75
Stefan Sauer
@ensonic
Yeah, need to take a look. Its kind of weird that one changes such a fundamental macro
Joe Pea
@trusktr
@ensonic Any luck? Would love to run Buzztrax again!
Stefan Sauer
@ensonic
let me rebuild and install and see if I can repro this here
Joe Pea
@trusktr
I found my old bzt files! Would love to get them back up and running!
Joe Pea
@trusktr
ping :)
Stefan Sauer
@ensonic
The bug is weird - as usual for me it builds and runs fine :/
Joe Pea
@trusktr
Hmmmmm
Joe Pea
@trusktr
There is this patch that is applied during install for Arch Linux. May it have anything to do with it? https://aur.archlinux.org/cgit/aur.git/tree/0001-tests-prefer-AM_TESTS_ENVIRONMENT-to-make-automake-h.patch?h=buzztrax
Doesn't seem like it would.
Joe Pea
@trusktr
I'm currently not getting the glib error like in the GitHub issue, but I do get a couple errors like this before it quits with error state:
tests/bt-check.h:153:5: error: too many arguments to function ‘_tcase_add_test’
  153 |     _tcase_add_test (tc, tf, fname, signal, allowed_exit_value, start, end);
      |     ^~~~~~~~~~~~~~~
Joe Pea
@trusktr
Any thoughts?
dlbeswick
@dlbeswick

Hey there Stefan, I'm still poking around Buzztrax from time to time. I was using "pulsesrc" in a song, I think that's a regular gstreamer plugin, and I found that it only worked if I created it straight away in the song. If I save and then load again, the pulsesrc plugin fails to start:

ERROR: Failed to connect: Invalid argument (GStreamer encountered a general resource error.)

Finally, I found that if I removed the saved pulsesrc properties "server" and "device" from the saved file then that solved the problem. What do you think might be going on here?

Also, would you mind if we saved the songs pretty-printed? It makes debugging a lot easier. It's an easy change in song-io-native-xml.c: from xmlSaveFile to xmlSaveFormatFile (file_name, song_doc, 1)

"pulsesrc" is in the "Direct Input" category
dlbeswick
@dlbeswick

Hello, I think there might be an issue with the UI interactions for the boolean parameter types. Both button-release-event and toggled events are connected on the checkbox, and it seems button release is fired before the toggle one. It's in on_button_release_eventthat update_param_after_interaction is called, but at that stage the value of the property hasn't been updated because on_checkbox_property_toggled hasn't been called. The effect is for the parameter to take on the value of the checkbox at the last click, not the current click.

For now I've just commented out button-release-event for the checkbox and restored the call to update_param_after_interaction in on_checkbox_property_toggled, but please let me know if there's a better fix.

dlbeswick
@dlbeswick
BTW the "pulsesrc" issue was because these properties seem to be NULL in the GstElement, but serialization writes them out as empty string. The element seems to treat these two cases differently -- I guess it's trying to open a device/server with an empty string name, which it can't do. I have some fixes for this I'll post a request for shortly. Thanks!
Stefan Sauer
@ensonic
hi, apparently I lost the chat tab a while ago and did not got any of the message. If in doubt please file an issue on github :)
@dlbeswick let me know if there is anything not address with your merged PRs
Bernhard M. Wiedemann
@bmwiedemann_gitlab
Hello
Bernhard M. Wiedemann
@bmwiedemann_gitlab
@ensonic I was trying the single-threaded make docs after unpacking the tarball. In front of the parallel make https://code.opensuse.org/package/buzztrax/blob/master/f/buzztrax.spec#_243
Stefan Sauer
@ensonic
Ahh, good idea
When I do this, it goes like this:
make -j1 docs
  GEN      src/lib/core/marshal.h
INFO: Reading src/lib/core/marshal.list...
  CC       src/lib/core/libbuzztrax_core_la-core.lo
maybe you can put more of the output on a github gist
(or some other pastebin)
Bernhard M. Wiedemann
@bmwiedemann_gitlab
I uploaded the full log to my server: https://rb.zq1.de/temp/buzztrax-make-docs.log.txt
Bernhard M. Wiedemann
@bmwiedemann_gitlab
maybe it is because of ./configure --disable-dependency-tracking
Bernhard M. Wiedemann
@bmwiedemann_gitlab
docs say, it should not matter for a single compile
Bernhard M. Wiedemann
@bmwiedemann_gitlab
btw: we build using make-4.3 automake-1.16.3
Stefan Sauer
@ensonic
Thanks. I'll have a look tonight
dlbeswick
@dlbeswick

Hello again! On the question of looping, I did track down some of the discussions you had with the gstreamer team around audiomixer. Really, this project is very bold in the way that it makes use of the gstreamer framework, I think that's impressive as I learn more about it.

In thinking about this naively, I would approach the problem by treating the gstreamer pipeline as a "live stream" scenario and just having Buzztrax keep the timing. For example, if a loop was defined, then "bt_pattern_control_source_get_value" would take the stream elapsed time and calculate the real song position by an offset and modulo with the loop length. If you have some time to go into it, what are some of the technical issues or some of the other design goals you have that would make this approach unsuitable?

Stefan Sauer
@ensonic
Yep, that'd be an options as well. Btw. which TZ are you ? Maybe I can be onlien when you are awake to do a little more interactive chat on taht (I am in CET)
David Meyer
@meyertime
hello. i'm trying to build on arch linux. never built buzztrax before. trying to follow the instructions in the readme. (./autogen.sh and make) i am running into an error. i'm wondering if it's related to #91?
  CC       src/lib/core/libbuzztrax_core_la-song-io-native-bzt.lo
src/lib/core/song-io-native-bzt.c: In function ‘bt_song_io_native_bzt_save’:
src/lib/core/song-io-native-bzt.c:399:13: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations]
  399 |             gpointer data = g_memdup (mem, (guint) len);
      |             ^~~~~~~~
In file included from /usr/include/glib-2.0/glib.h:82,
                 from src/lib/core/core.h:22,
                 from src/lib/core/core_private.h:56,
                 from src/lib/core/song-io-native-bzt.c:34:
/usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here
  257 | gpointer              g_memdup         (gconstpointer mem,
      |                       ^~~~~~~~
cc1: all warnings being treated as errors
make: *** [Makefile:6536: src/lib/core/libbuzztrax_core_la-song-io-native-bzt.lo] Error 1
David Meyer
@meyertime
i've gotten past most of the build errors by removing -Werror so that warnings are not treated as errors. it appears to build now, but i can't find the executable to run. i tried make install, but get this error:
libtool: install: /usr/bin/install -c .libs/libbuzztrax-ic.lai /home/david/buzztrax/lib/libbuzztrax-ic.la
libtool: warning: relinking 'libbuzztrax-core.la'
libtool: install: (cd /home/david/code/buzztrax; /bin/sh "/home/david/code/buzztrax/libtool"  --silent --tag CC --mode=relink gcc -g -O2 -export-symbols-regex "^_?(bt_|Bt|BT_).*" -version-info 2:0:1 -o libbuzztrax-core.la -rpath /home/david/buzztrax/lib src/lib/core/libbuzztrax_core_la-core.lo src/lib/core/libbuzztrax_core_la-tools.lo src/lib/core/libbuzztrax_core_la-buzzcallbacks.lo src/lib/core/libbuzztrax_core_la-application.lo src/lib/core/libbuzztrax_core_la-audio-session.lo src/lib/core/libbuzztrax_core_la-childproxy.lo src/lib/core/libbuzztrax_core_la-cmd-pattern.lo src/lib/core/libbuzztrax_core_la-cmd-pattern-control-source.lo src/lib/core/libbuzztrax_core_la-experiments.lo src/lib/core/libbuzztrax_core_la-machine.lo src/lib/core/libbuzztrax_core_la-parameter-group.lo src/lib/core/libbuzztrax_core_la-pattern.lo src/lib/core/libbuzztrax_core_la-pattern-control-source.lo src/lib/core/libbuzztrax_core_la-persistence.lo src/lib/core/libbuzztrax_core_la-processor-machine.lo src/lib/core/libbuzztrax_core_la-sequence.lo src/lib/core/libbuzztrax_core_la-settings.lo src/lib/core/libbuzztrax_core_la-setup.lo src/lib/core/libbuzztrax_core_la-sink-bin.lo src/lib/core/libbuzztrax_core_la-sink-machine.lo src/lib/core/libbuzztrax_core_la-song.lo src/lib/core/libbuzztrax_core_la-song-info.lo src/lib/core/libbuzztrax_core_la-song-io.lo src/lib/core/libbuzztrax_core_la-song-io-native.lo src/lib/core/libbuzztrax_core_la-song-io-native-bzt.lo src/lib/core/libbuzztrax_core_la-song-io-native-xml.lo src/lib/core/libbuzztrax_core_la-source-machine.lo src/lib/core/libbuzztrax_core_la-value-group.lo src/lib/core/libbuzztrax_core_la-wavetable.lo src/lib/core/libbuzztrax_core_la-wave.lo src/lib/core/libbuzztrax_core_la-wavelevel.lo src/lib/core/libbuzztrax_core_la-wire.lo src/lib/core/libbuzztrax_core_la-marshal.lo libbuzztrax-ic.la libbuzztrax-gst.la -lgthread-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 -lgio-2.0 -lxml2 -lgstcontroller-1.0 -lgstaudio-1.0 -lgstbase-1.0 -lgsttag-1.0 -lgstfft-1.0 -lm -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lasound -lgudev-1.0 -lgobject-2.0 -lglib-2.0 -lgsf-1 -lgobject-2.0 -lglib-2.0 -lxml2 -lm -lgstaudio-1.0 -lgstpbutils-1.0 -lrt )
/usr/bin/ld: cannot find -lbuzztrax-ic
/usr/bin/ld: cannot find -lbuzztrax-gst
collect2: error: ld returned 1 exit status
libtool:   error: error: relink 'libbuzztrax-core.la' with the above command before installing it
make[3]: *** [Makefile:3419: install-libLTLIBRARIES] Error 1
make[3]: Leaving directory '/home/david/code/buzztrax'
make[2]: *** [Makefile:8337: install-am] Error 2
make[2]: Leaving directory '/home/david/code/buzztrax'
make[1]: *** [Makefile:7771: install-recursive] Error 1
make[1]: Leaving directory '/home/david/code/buzztrax'
make: *** [Makefile:8330: install] Error 2
David Meyer
@meyertime

ok, i actually got it to run and start, though i haven't played around with the program yet to see if it works. got past the above error by running make clean install. but then i got this error when trying to run buzztrax-edit:

(buzztrax-edit:50838): GLib-GIO-ERROR **: 10:17:13.754: Settings schema 'org.gnome.desktop.interface' is not installed
Trace/breakpoint trap (core dumped)

to get past that, i had to set an environment variable:

XDG_DATA_DIRS=/usr/local/share/:/usr/share/ ./buzztrax-edit
David Meyer
@meyertime
image.png
everything appears to work... except the machine view looks a little wonky, as you see above. though i'm not sure how it's supposed to look, since i've never used buzztrax before. but the tiny text may be due to it not handling scaling well.
dlbeswick
@dlbeswick
Hi David, there are quite a few deprecation warnings in the codebase currently. Usually I build by just disabling those errors. IMO we should probably set that compiler option by default until we can sort those out.
Interesting about the xdg_datat_dirs issue; that wasn't something I remember having to do.
The UI shouldn't look like that, I guess you're using a high DPI display, is that what you meant by scaling? Does it still happen if you use a lower res?
Stefan Sauer
@ensonic
@meyertime sorry for late reply (vacation time) - I'll fix some of the deprecation warnings in the next week (make it conditional on the available libs) - Imho the flag is off for release build (tar balls).
Stefan Sauer
@ensonic
The required env-vars are printed at the end of the configure run. We could also print the warnings when starting the app. The schema related one is per design in glib and I don't like that either. The missing images are also path related. See the info here:
https://github.com/Buzztrax/buzztrax/blob/master/README.md#installing-locally
David Meyer
@meyertime
thanks for the response. i tried setting all the environment variables mentioned in that section. i'm not sure if it made a difference, but some kind of graphic does show up if i run it from the repository directory instead of the bin directory, but they look garbled:
Screenshot_20210821_004123.bmp
and yes, high dpi display. i normally have scaling set to 150% system-wide. also, if it makes a difference, i'm using kde plasma. i tried reverting everything to 100%, but i don't know if this is normal sized text or not:
Screenshot_20210821_005705.bmp
David Meyer
@meyertime
i played around with it a bit, trying to get some kind of instrument to play with my midi controller, but it would crash with the output Segmentation fault randomly. it didn't do that while i was running without scaling, though, but i wasn't using it very long.
Joe Pea
@trusktr
I can't wait to get this running again!
jobf
@jobf
awwwwww hell yeah buzztrax is still alive!
Stefan Sauer
@ensonic
I know my response time is terrible, sorry) - if you get segfaults, try running via gdb and report the backtraces to us. Know issue is reconnecting wires while playback runs and there is no easy fix (and no time to fix it properly :/ on my side)
according to the screenshots something weird is going on with the icon theme & SVGs
I wonder if running from a terminal shows some warnings that could help