10 Nov
2012
10 Nov
'12
8:12 p.m.
Radium is an open source music editor with a novel interface.
It's inspired by trackers, but has fewer limitations and uses graphics
to show musical data.
Screenshot:
===========
http://dl.dropbox.com/u/4814054/radium-1.9.1.png
Source code:
============
http://dl.dropbox.com/u/4814054/radium-1.9.1.tar.gz
64 bit binary:
===============
http://dl.dropbox.com/u/4814054/radium-1.9.1_linux64.tar.gz
(Requires GNU libc 2.14 or newer. It should work with Ubuntu 12,
Fedora 17 or Mint 13)
Homepage:
=========
http://users.notam02.no/~kjetism/radium/
(It's not quite updated, I can't seem to login to the web server right
now.)
Source code repository:
=======================
https://github.com/kmatheussen/radium
Most important changes 0.67.1 -> 1.9.1:
=======================================
* Audio.
* A quick-to-use modular mixer. Jack ports can be inserted anywhere.
* VST plugins and instruments (native, not via wine)
* LADSPA
* Fluidsynth instrument
* 20 STK instruments. (Physical modelling)
* Sampler instrument (soundfiles, xi instruments, soundfonts)
* Multiband compressor
(http://users.notam02.no/~kjetism/radium/pictures/screenshot-multiband.png)
* Built-in filters and equalizers.
* Simple arpeggiator
* Drunk input velocity
* Various GUI improvements
* Pitch expand made available in the menues.
* Tapiir plugin
* Zita reverb plugin
* Demo song
* Reconfigured keybindings
* Various bug fixes
Acknowledgment:
===============
Full list: http://users.notam02.no/~kjetism/radium/development.php
Especially thanks to Yann Orlarey for Faust, Julius O. Smith III for
the Faust filter and compressor code and more, Romain Michon for the
Faust
STK instruments, Fons Adriaensen for the amazing Zita reverb sound
(and Julius O. Smith III for the Faust implemention of it),
and Rui Nuno Capela for QTractor. (Plugin GUI code are based on code
taken from QTractor.)
11 Nov
11 Nov
3:37 p.m.
On 11/10/2012 08:12 PM, Kjetil Matheussen wrote:
Source code:
============
http://dl.dropbox.com/u/4814054/radium-1.9.1.tar.gz
Hi, building from source sadly fails, too. make packages runs through
fine, then during build:
g++ Qt/Qt_MainWindow.cpp -c `cat buildtype.opt` -DNOPAUSEPLAY
-Ibin/packages/gc-7.2/include -IQt/ -I/usr/include/python2.7 -DGUIISQT
-Imidi/rtmidi -DUSE_GFX_OP_QUEUE -Werror=array-bounds -DUSE_QT_VISUAL=1
-DUSE_GTK_VISUAL=0 -DUSE_QT_REQTYPE=1 -DUSE_GTK_REQTYPE=0
-DUSE_QT_MENU=1 -DUSE_GTK_MENU=0 -DUSE_VESTIGE=0 -DUSE_QT4
-DUSE_QIMAGE_BUFFER=1 -DQT_SHARED -DQT3_SUPPORT -I/usr/include/qt4
-I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork
-I/usr/include/qt4/QtSql -DQT_NO_OPENGL
g++ windows.o window_config.o list.o vector.o hashmap.o song.o blocks.o
block_insert.o block_split.o block_delete.o block_properties.o tracks.o
localzooms.o control.o lines.o font.o track_insert.o track_onoff.o
settings.o notes.o notes_legalize.o wblocks.o wtracks.o sliders.o
gfx_wblocks.o gfx_wblocks_reltempo.o gfx_statusbar.o
gfx_tempotrackheader.o gfx_upperleft.o common.o gfx_wtracks.o
gfx_wtrackborder.o gfx_wtext.o gfx_text.o gfx_lines.o gfx_point.o
gfx_op_queue.o eventreciever.o reallines.o notestext.o trackreallines.o
clipboard_range.o clipboard_range_calc.o clipboard_range_copy.o
clipboard_range_paste.o clipboard_range_cut.o transpose.o backwards.o
invert.o glissando.o pitchexpand.o clipboard_track_copy.o
clipboard_track_paste.o clipboard_track_cut.o clipboard_tempos_copy.o
clipboard_localzooms.o clipboard_block_copy.o clipboard_block_paste.o
quantitize.o mouse.o mouse_wtrack.o mouse_wtrackheader.o
mouse_tempoheader.o mouse_wtrackborder.o mouse_temponodeborder.o
mouse_fxarea.o mouse_vellinenode.o mouse_vellineend.o
mouse_vellinestart.o mouse_fxnode.o mouse_quantitize.o
mouse_reltemposlider.o tbox.o area.o range.o debug.o memory.o
placement.o t_gc.o cursor.o cursor_updown.o subtrack.o velocities.o
pixmap.o scroll.o blts.o realline_calc.o gfx_subtrack.o LPB.o
gfx_wtrackheaders.o gfx_wtrackheader_volpan.o gfx_slider.o
reallines_insert.o gfx_shrink.o gfx_shrink_t.o gfx_request.o nodelines.o
nodeboxes.o instruments.o patch.o fxlines.o fxlines_legalize.o
blocklist.o scroll_play.o gfx_tempocolor.o reltempo.o temponodes.o
tempos.o time.o time2place.o mouse_temponodes.o temponodes_legalize.o
Ptask2Mtask.o player.o scheduler.o PEQrealline.o PEQmempool.o PEQblock.o
PEQnotes.o PEQcommon.o playerclass.o player_startstop.o PEQvelocities.o
PEQ_calc.o PEQfxs.o player_pause.o PEQ_type.o PEQ_calc_64bit.o
PEQ_clock.o disk.o disk_fxs.o disk_wblock.o disk_localzooms.o
disk_track.o disk_fx.o disk_fxnodelines.o disk_wtrack.o
disk_temponodes.o disk_tempos.o disk_song.o disk_velocities.o
disk_block.o disk_placement.o disk_stops.o disk_playlist.o disk_root.o
disk_notes.o disk_lpbs.o disk_windows.o disk_warea.o disk_save.o
disk_load.o disk_instrument.o disk_patches.o disk_slider.o undo.o
undo_notes.o undo_fxs.o undo_temponodes.o undo_tempos.o undo_lpbs.o
undo_notesandfxs.o undo_reallines.o undo_tracks.o undo_range.o
undo_blocks.o undo_trackheader.o undo_reltempomax.o undo_maintempos.o
undo_block_insertdelete.o undo_block_mergesplit.o undo_reltemposlider.o
undo_playlist.o undo_patch.o undo_patchvoice.o undo_patchname.o
undo_chip_position.o Qt_visual.o GTK_visual.o Qt_Main.o Qt_endprogram.o
Qt_EventReceiver.o Qt_colors.o Qt_Menues.o Qt_Fonts.o Qt_ReqType.o
Qt_PopupMenu.o qcolordialog.o Qt_Bs_edit.o Qt_instruments.o
Qt_PluginWidget.o Qt_MyQSlider.o Qt_SliderPainter.o Qt_memory.o
Qt_path_resolver.o Qt_settings.o Qt_MainWindow.o GTK_ReqType.o
GTK_PopupMenu.o Qt_soundfilesaver_widget_callbacks.o Qt_Semaphores.o
radium_wrap.o api_common.o api_keyplay.o api_keyplayedit.o
api_navigate.o api_noteedit.o api_support.o ad_noteadd.o wrapfunclist.o
api_trackonoff.o api_zoom.o api_notemanipulate.o api_play.o
api_clipboard.o api_undo.o api_various.o api_instruments.o
api_requesters.o posix_settings.o posix_Player.o X11_keyboard.o
X11_error.o X11_disk.o X11_Qtstuff.o disk_midi_fx.o
disk_midi_i_plugin.o midi_fx.o midi_i_plugin.o midi_playfromstart.o
midi_rtmidi.o RtMidi.o midi_i_input.o midi_menues.o zita_rev.o
stk_flute.o stk_bowed.o stk_blow_bottle.o stk_bass.o stk_blow_hole.o
stk_brass.o stk_clarinet.o stk_flute_stk.o stk_glass_harmonica.o
stk_harpsi.o stk_modal_bar.o stk_NLF_eks.o stk_NLF_fm.o stk_piano.o
stk_saxophony.o stk_sitar.o stk_tibetan_bowl.o stk_tuned_bar.o
stk_uni_bar.o stk_voice_form.o faust_tapiir.o faust_system_eq.o
faust_system_lowpass.o faust_system_lowshelf.o faust_system_highshelf.o
faust_system_delay.o faust_multibandcomp.o audio_instrument.o
SoundProducer.o Jack_plugin.o Bus_plugins.o VST_plugins.o
Ladspa_plugins.o Sampler_plugin.o FluidSynth_plugin.o
SoundPluginRegistry.o SoundPlugin.o Mixer.o get_windows_commandlines.o
Envelope.o Resampler.o SoundFonts.o Smooth.o undo_audio_effect.o
SoundfileSaver.o QM_view.o QM_chip.o QM_MixerWidget.o undo_mixer.o
undo_mixer_connections.o undo_chip_addremove.o -o bin/radium -g -lm
-lQt3Support -lQtGui -lQtNetwork -lQtSql -lQtCore -lpthread -lasound
-ljack -llrdf -pthread -lrt -lX11 bin/packages/gc-7.2/.libs/libgc.a
-L/usr/lib -lpython2.7 bin/packages/libgig/src/.libs/libgig.a
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a `pkg-config
--libs sndfile` `pkg-config --libs samplerate` `pkg-config --libs glib-2.0`
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_sys.o):
In function `fluid_istream_readline':
fluid_sys.c:(.text+0x10fc): undefined reference to `readline'
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_cmd.o):
In function `fluid_shell_run':
fluid_cmd.c:(.text+0x1b06): undefined reference to `add_history'
collect2: ld returned 1 exit status
make: *** [bin/radium] Error 1
Flo
3:59 p.m.
Le Sun, 11 Nov 2012 15:37:13 +0100,
Florian Paul Schmidt <mista.tapas(a)gmx.net> a écrit :
On 11/10/2012 08:12 PM, Kjetil Matheussen wrote:
Same error, here on gentoo:
Source code:
============
http://dl.dropbox.com/u/4814054/radium-1.9.1.tar.gz
Hi, building from source sadly fails, too. make packages runs through
fine, then during build:
g++ Qt/Qt_MainWindow.cpp -c `cat buildtype.opt` -DNOPAUSEPLAY
-Ibin/packages/gc-7.2/include -IQt/ -I/usr/include/python2.7
-DGUIISQT -Imidi/rtmidi -DUSE_GFX_OP_QUEUE -Werror=array-bounds
-DUSE_QT_VISUAL=1 -DUSE_GTK_VISUAL=0 -DUSE_QT_REQTYPE=1
-DUSE_GTK_REQTYPE=0 -DUSE_QT_MENU=1 -DUSE_GTK_MENU=0 -DUSE_VESTIGE=0
-DUSE_QT4 -DUSE_QIMAGE_BUFFER=1 -DQT_SHARED -DQT3_SUPPORT
-I/usr/include/qt4 -I/usr/include/qt4/Qt3Support
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui
-I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtSql -DQT_NO_OPENGL
g++ windows.o window_config.o list.o vector.o hashmap.o song.o
blocks.o block_insert.o block_split.o block_delete.o
block_properties.o tracks.o localzooms.o control.o lines.o font.o
track_insert.o track_onoff.o settings.o notes.o notes_legalize.o
wblocks.o wtracks.o sliders.o gfx_wblocks.o gfx_wblocks_reltempo.o
gfx_statusbar.o gfx_tempotrackheader.o gfx_upperleft.o common.o
gfx_wtracks.o gfx_wtrackborder.o gfx_wtext.o gfx_text.o gfx_lines.o
gfx_point.o gfx_op_queue.o eventreciever.o reallines.o notestext.o
trackreallines.o clipboard_range.o clipboard_range_calc.o
clipboard_range_copy.o clipboard_range_paste.o clipboard_range_cut.o
transpose.o backwards.o invert.o glissando.o pitchexpand.o
clipboard_track_copy.o clipboard_track_paste.o clipboard_track_cut.o
clipboard_tempos_copy.o clipboard_localzooms.o clipboard_block_copy.o
clipboard_block_paste.o quantitize.o mouse.o mouse_wtrack.o
mouse_wtrackheader.o mouse_tempoheader.o mouse_wtrackborder.o
mouse_temponodeborder.o mouse_fxarea.o mouse_vellinenode.o
mouse_vellineend.o mouse_vellinestart.o mouse_fxnode.o
mouse_quantitize.o mouse_reltemposlider.o tbox.o area.o range.o
debug.o memory.o placement.o t_gc.o cursor.o cursor_updown.o
subtrack.o velocities.o pixmap.o scroll.o blts.o realline_calc.o
gfx_subtrack.o LPB.o gfx_wtrackheaders.o gfx_wtrackheader_volpan.o
gfx_slider.o reallines_insert.o gfx_shrink.o gfx_shrink_t.o
gfx_request.o nodelines.o nodeboxes.o instruments.o patch.o fxlines.o
fxlines_legalize.o blocklist.o scroll_play.o gfx_tempocolor.o
reltempo.o temponodes.o tempos.o time.o time2place.o
mouse_temponodes.o temponodes_legalize.o Ptask2Mtask.o player.o
scheduler.o PEQrealline.o PEQmempool.o PEQblock.o PEQnotes.o
PEQcommon.o playerclass.o player_startstop.o PEQvelocities.o
PEQ_calc.o PEQfxs.o player_pause.o PEQ_type.o PEQ_calc_64bit.o
PEQ_clock.o disk.o disk_fxs.o disk_wblock.o disk_localzooms.o
disk_track.o disk_fx.o disk_fxnodelines.o disk_wtrack.o
disk_temponodes.o disk_tempos.o disk_song.o disk_velocities.o
disk_block.o disk_placement.o disk_stops.o disk_playlist.o
disk_root.o disk_notes.o disk_lpbs.o disk_windows.o disk_warea.o
disk_save.o disk_load.o disk_instrument.o disk_patches.o
disk_slider.o undo.o undo_notes.o undo_fxs.o undo_temponodes.o
undo_tempos.o undo_lpbs.o undo_notesandfxs.o undo_reallines.o
undo_tracks.o undo_range.o undo_blocks.o undo_trackheader.o
undo_reltempomax.o undo_maintempos.o undo_block_insertdelete.o
undo_block_mergesplit.o undo_reltemposlider.o undo_playlist.o
undo_patch.o undo_patchvoice.o undo_patchname.o undo_chip_position.o
Qt_visual.o GTK_visual.o Qt_Main.o Qt_endprogram.o Qt_EventReceiver.o
Qt_colors.o Qt_Menues.o Qt_Fonts.o Qt_ReqType.o Qt_PopupMenu.o
qcolordialog.o Qt_Bs_edit.o Qt_instruments.o Qt_PluginWidget.o
Qt_MyQSlider.o Qt_SliderPainter.o Qt_memory.o Qt_path_resolver.o
Qt_settings.o Qt_MainWindow.o GTK_ReqType.o GTK_PopupMenu.o
Qt_soundfilesaver_widget_callbacks.o Qt_Semaphores.o radium_wrap.o
api_common.o api_keyplay.o api_keyplayedit.o api_navigate.o
api_noteedit.o api_support.o ad_noteadd.o wrapfunclist.o
api_trackonoff.o api_zoom.o api_notemanipulate.o api_play.o
api_clipboard.o api_undo.o api_various.o api_instruments.o
api_requesters.o posix_settings.o posix_Player.o X11_keyboard.o
X11_error.o X11_disk.o X11_Qtstuff.o disk_midi_fx.o
disk_midi_i_plugin.o midi_fx.o midi_i_plugin.o midi_playfromstart.o
midi_rtmidi.o RtMidi.o midi_i_input.o midi_menues.o zita_rev.o
stk_flute.o stk_bowed.o stk_blow_bottle.o stk_bass.o stk_blow_hole.o
stk_brass.o stk_clarinet.o stk_flute_stk.o stk_glass_harmonica.o
stk_harpsi.o stk_modal_bar.o stk_NLF_eks.o stk_NLF_fm.o stk_piano.o
stk_saxophony.o stk_sitar.o stk_tibetan_bowl.o stk_tuned_bar.o
stk_uni_bar.o stk_voice_form.o faust_tapiir.o faust_system_eq.o
faust_system_lowpass.o faust_system_lowshelf.o
faust_system_highshelf.o faust_system_delay.o faust_multibandcomp.o
audio_instrument.o SoundProducer.o Jack_plugin.o Bus_plugins.o
VST_plugins.o Ladspa_plugins.o Sampler_plugin.o FluidSynth_plugin.o
SoundPluginRegistry.o SoundPlugin.o Mixer.o
get_windows_commandlines.o Envelope.o Resampler.o SoundFonts.o
Smooth.o undo_audio_effect.o SoundfileSaver.o QM_view.o QM_chip.o
QM_MixerWidget.o undo_mixer.o undo_mixer_connections.o
undo_chip_addremove.o -o bin/radium -g -lm -lQt3Support -lQtGui
-lQtNetwork -lQtSql -lQtCore -lpthread -lasound -ljack -llrdf
-pthread -lrt -lX11 bin/packages/gc-7.2/.libs/libgc.a -L/usr/lib
-lpython2.7 bin/packages/libgig/src/.libs/libgig.a
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a `pkg-config
--libs sndfile` `pkg-config --libs samplerate` `pkg-config --libs
glib-2.0`
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_sys.o):
In function `fluid_istream_readline': fluid_sys.c:(.text+0x10fc):
undefined reference to `readline'
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_cmd.o):
In function `fluid_shell_run': fluid_cmd.c:(.text+0x1b06): undefined
reference to `add_history' collect2: ld returned 1 exit status make:
*** [bin/radium] Error 1
Flo
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
"We have the heroes we deserve."
4:30 p.m.
Florian Paul Schmidt mista.tapas at gmx.net
fluid_sys.c:(.text+0x10fc): undefined reference to
`readline'
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_cmd.o):
In function `fluid_shell_run':
fluid_cmd.c:(.text+0x1b06): undefined reference to `add_history'
Thanks, fixed in git:
https://github.com/kmatheussen/radium/archive/master.zip
4:56 p.m.
On 11/11/2012 04:30 PM, Kjetil Matheussen wrote:
Florian Paul Schmidt mista.tapas at gmx.net
Thanks a bunch man.. Now it builds and runs.. :D
Looking forward to getting the hang of it.. This looks pretty much like
it could replace my current toy of choice Renoise, which sadly is closed
source..
Flo
fluid_sys.c:(.text+0x10fc): undefined reference
to `readline'
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_cmd.o):
In function `fluid_shell_run':
fluid_cmd.c:(.text+0x1b06): undefined reference to `add_history'
Thanks, fixed in git:
https://github.com/kmatheussen/radium/archive/master.zip
5:02 p.m.
On 11.11.2012 16:56, Florian Paul Schmidt wrote:
On 11/11/2012 04:30 PM, Kjetil Matheussen wrote:
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
Florian Paul Schmidt mista.tapas at gmx.net
Thanks a bunch man.. Now it builds and runs.. :D
Looking forward to getting the hang of it.. This looks pretty much
like it could replace my current toy of choice Renoise, which sadly
is
closed source..
fluid_sys.c:(.text+0x10fc): undefined reference
to `readline'
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_cmd.o):
In function `fluid_shell_run':
fluid_cmd.c:(.text+0x1b06): undefined reference to `add_history'
Thanks, fixed in git:
https://github.com/kmatheussen/radium/archive/master.zip
5:40 p.m.
On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
Another small bugreport: Seemingly parsing of LADSPA_PATH is broken.. I
had this in my environment:
LADSPA_PATH=/usr/lib/ladspa:/usr/local/lib/ladspa
Then it doesn't find the CALF plugin.. Using only /usr/lib/ladspa fixed
that..
Flo
6:13 p.m.
On 11.11.2012 17:40, Florian Paul Schmidt wrote:
On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
Didn't think about having several paths separated by colons.
Fixed in git now.
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
Another small bugreport: Seemingly parsing of LADSPA_PATH is broken..
I had this in my environment:
LADSPA_PATH=/usr/lib/ladspa:/usr/local/lib/ladspa
Then it doesn't find the CALF plugin.. Using only /usr/lib/ladspa
fixed that..
6:21 p.m.
On 11/11/2012 06:13 PM, Kjetil Matheussen wrote:
On 11.11.2012 17:40, Florian Paul Schmidt wrote:
Cool, another small thing (if I get on your nerves, let me know):
Going through my sample collection in the sample player makes radium
hang after the third or fourth sample.. Let's see if I can get a trace.
I did, but it doesn't tell me too much..
file: Pressed "Kick06.flac............2ch, 20kB"
Header id says it is not an xi instrument: "fLaC".
Num channels: 2
[Here it hangs]
^CYou pressed Ctrl+C. Sending SIGINT signal to radium.
Program received signal SIGINT, Interrupt.
0x00007ffff516434e in sf_readf_float () from
/usr/lib/x86_64-linux-gnu/libsndfile.so.1
(gdb) bt
#0 0x00007ffff516434e in sf_readf_float () from
/usr/lib/x86_64-linux-gnu/libsndfile.so.1
#1 0x000000000059af8e in load_sample_with_libsndfile (data=0x264b120,
filename=0x25c63e8
"/media/cbc5904f-b879-4bd4-937a-439cccb0f70c/Samples and
Instruments/Renoise-Samples/Kicks/Kick06.flac")
at audio/Sampler_plugin.c:775
#2 0x000000000059c754 in load_sample (data=0x264b120,
filename=0x25c63e8
"/media/cbc5904f-b879-4bd4-937a-439cccb0f70c/Samples and
Instruments/Renoise-Samples/Kicks/Kick06.flac",
instrument_number=12) at audio/Sampler_plugin.c:827
#3 0x000000000059cd60 in set_new_sample (plugin=<optimized out>,
filename=0x25c63e8
"/media/cbc5904f-b879-4bd4-937a-439cccb0f70c/Samples and
Instruments/Renoise-Samples/Kicks/Kick06.flac",
instrument_number=<optimized out>, resampler_type=2) at
audio/Sampler_plugin.c:934
#4 0x000000000048ab4d in Sample_requester_widget::handle_file_pressed
(this=0x256f0d0, item_text=...)
at Qt/Qt_sample_requester_widget_callbacks.h:346
#5 0x000000000048b37b in Sample_requester_widget::handle_item_pressed
(this=0x256f0d0, item_text=...)
at Qt/Qt_sample_requester_widget_callbacks.h:404
#6 0x000000000048bbe7 in
Sample_requester_widget::on_file_list_itemPressed (this=0x256f0d0,
item=0x217e440)
at Qt/Qt_sample_requester_widget_callbacks.h:464
#7 0x000000000048bb6b in
Sample_requester_widget::on_file_list_currentItemChanged
(this=0x256f0d0, current=0x217e440,
previous=0x2208d50) at Qt/Qt_sample_requester_widget_callbacks.h:460
#8 0x0000000000472770 in Sample_requester_widget::qt_static_metacall
(_o=0x256f0d0, _c=QMetaObject::InvokeMetaMethod, _id=5,
_a=0x7fffffffbd80) at Qt/mQt_sample_requester_widget_callbacks.h:69
#9 0x00000000004728ac in Sample_requester_widget::qt_metacall
(this=0x256f0d0, _c=QMetaObject::InvokeMetaMethod, _id=5,
_a=0x7fffffffbd80) at Qt/mQt_sample_requester_widget_callbacks.h:112
#10 0x00007ffff68ee489 in QMetaObject::activate (sender=0x236e6b0,
m=<optimized out>, local_signal_index=<optimized out>,
argv=0x7fffffffbd80) at kernel/qobject.cpp:3566
#11 0x00007ffff738bcdf in QListWidget::currentItemChanged
(this=<optimized out>, _t1=0x217e440, _t2=0x2208d50)
at .moc/release-shared/moc_qlistwidget.cpp:247
#12 0x00007ffff738be0e in QListWidgetPrivate::_q_emitCurrentItemChanged
(this=0x25bcda0, current=..., previous=...)
at itemviews/qlistwidget.cpp:1112
#13 0x00007ffff68ee281 in QMetaObject::activate (sender=0x22ede60,
m=<optimized out>, local_signal_index=<optimized out>,
argv=0x7fffffffbf40) at kernel/qobject.cpp:3547
#14 0x00007ffff73798ea in QItemSelectionModel::currentChanged
(this=<optimized out>, _t1=..., _t2=...)
at .moc/release-shared/moc_qitemselectionmodel.cpp:173
#15 0x00007ffff73799e0 in QItemSelectionModel::setCurrentIndex
(this=0x22ede60, index=..., command=...)
at itemviews/qitemselectionmodel.cpp:1175
#16 0x00007ffff7328084 in QAbstractItemView::mousePressEvent
(this=0x236e6b0, event=<optimized out>)
at itemviews/qabstractitemview.cpp:1682
#17 0x00007ffff6e4d429 in QWidget::event (this=0x236e6b0,
event=0x7fffffffcd90) at kernel/qwidget.cpp:8358
#18 0x00007ffff720d3b6 in QFrame::event (this=0x236e6b0,
e=0x7fffffffcd90) at widgets/qframe.cpp:557
#19 0x00007ffff732189b in QAbstractItemView::viewportEvent
(this=0x236e6b0, event=0x7fffffffcd90)
at itemviews/qabstractitemview.cpp:1644
#20 0x00007ffff68da028 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized
out>, receiver=0x237c020,
event=0x7fffffffcd90) at kernel/qcoreapplication.cpp:986
#21 0x00007ffff6dfc85f in notify_helper (e=0x7fffffffcd90,
receiver=0x237c020, this=0xf2dd10) at kernel/qapplication.cpp:4555
#22 QApplicationPrivate::notify_helper (this=0xf2dd10,
receiver=0x237c020, e=0x7fffffffcd90) at kernel/qapplication.cpp:4531
#23 0x00007ffff6e020bf in QApplication::notify (this=<optimized out>,
receiver=0x237c020, e=0x7fffffffcd90)
at kernel/qapplication.cpp:4102
#24 0x00007ffff68d9e9c in QCoreApplication::notifyInternal
(this=0xf00280, receiver=0x237c020, event=0x7fffffffcd90)
at kernel/qcoreapplication.cpp:876
#25 0x00007ffff6dfd862 in sendEvent (event=<optimized out>,
receiver=<optimized out>)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#26 QApplicationPrivate::sendMouseEvent (receiver=0x237c020,
event=0x7fffffffcd90, alienWidget=0x237c020, nativeWidget=0xfd0430,
buttonDown=0x237c020, lastMouseReceiver=..., spontaneous=true) at
kernel/qapplication.cpp:3170
#27 0x00007ffff6e7cbf5 in QETWidget::translateMouseEvent (this=0xfd0430,
event=<optimized out>) at kernel/qapplication_x11.cpp:4617
#28 0x00007ffff6e7bbae in QApplication::x11ProcessEvent (this=0xf00280,
event=0x7fffffffd660) at kernel/qapplication_x11.cpp:3732
#29 0x00007ffff6ea50d2 in x11EventSourceDispatch (s=0xea6170,
callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#30 0x00007ffff4b41d53 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007ffff4b420a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007ffff4b42164 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007ffff69093bf in QEventDispatcherGlib::processEvents
(this=0xf2e0c0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#34 0x00007ffff6ea4d5e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...)
at kernel/qguieventdispatcher_glib.cpp:204
#35 0x00007ffff68d8c82 in QEventLoop::processEvents (this=<optimized
out>, flags=...) at kernel/qeventloop.cpp:149
#36 0x00007ffff68d8ed7 in QEventLoop::exec (this=0x7fffffffda00,
flags=...) at kernel/qeventloop.cpp:204
#37 0x00007ffff68ddf67 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1148
#38 0x000000000046064b in radium_main (arg=0x7ffff7f6e52c "") at
Qt/Qt_Main.cpp:466
#39 0x00000000004ad968 in init_radium (arg=0x7ffff7f6e52c "",
gkf=0x104c848) at api/api_common.c:61
#40 0x00000000004a8bc5 in _wrap_init_radium (self=0x0, args=0x10e8290)
at api/radium_wrap.c:572
#41 0x00007ffff5453845 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.7.so.1.0
#42 0x00007ffff541e605 in PyEval_EvalCodeEx () from
/usr/lib/libpython2.7.so.1.0
#43 0x00007ffff541e932 in PyEval_EvalCode () from
/usr/lib/libpython2.7.so.1.0
#44 0x00007ffff541f740 in PyRun_FileExFlags () from
/usr/lib/libpython2.7.so.1.0
#45 0x00007ffff541f958 in ?? () from /usr/lib/libpython2.7.so.1.0
#46 0x00007ffff5453845 in PyEval_EvalFrameEx () from
/usr/lib/libpython2.7.so.1.0
#47 0x00007ffff541e605 in PyEval_EvalCodeEx () from
/usr/lib/libpython2.7.so.1.0
#48 0x00007ffff541e932 in PyEval_EvalCode () from
/usr/lib/libpython2.7.so.1.0
---Type <return> to continue, or q <return> to quit---
#49 0x00007ffff541e9cc in PyRun_StringFlags () from
/usr/lib/libpython2.7.so.1.0
#50 0x00007ffff541f61b in PyRun_SimpleStringFlags () from
/usr/lib/libpython2.7.so.1.0
#51 0x0000000000460a58 in main (argc=1, argv=0x7fffffffe528) at
Qt/Qt_Main.cpp:601
Flo
On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
Didn't think about having several paths separated by colons.
Fixed in git now.
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
Another small bugreport: Seemingly parsing of LADSPA_PATH is broken..
I had this in my environment:
LADSPA_PATH=/usr/lib/ladspa:/usr/local/lib/ladspa
Then it doesn't find the CALF plugin.. Using only /usr/lib/ladspa
fixed that..
6:35 p.m.
On 11/11/2012 06:21 PM, Florian Paul Schmidt wrote:
On 11/11/2012 06:13 PM, Kjetil Matheussen wrote:
This seems to happen only with flac samples. They sound a bit weird in
the playback, too..
Flo
On 11.11.2012 17:40, Florian Paul Schmidt wrote:
Cool, another small thing (if I get on your nerves, let me know):
Going through my sample collection in the sample player makes radium
hang after the third or fourth sample.. Let's see if I can get a
trace. I did, but it doesn't tell me too much..
file: Pressed "Kick06.flac............2ch, 20kB"
Header id says it is not an xi instrument: "fLaC".
Num channels: 2
[Here it hangs] On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
Didn't think about having several paths separated by colons.
Fixed in git now.
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
Another small bugreport: Seemingly parsing of LADSPA_PATH is broken..
I had this in my environment:
LADSPA_PATH=/usr/lib/ladspa:/usr/local/lib/ladspa
Then it doesn't find the CALF plugin.. Using only /usr/lib/ladspa
fixed that..
6:55 p.m.
On 11.11.2012 18:21, Florian Paul Schmidt wrote:
On 11/11/2012 06:13 PM, Kjetil Matheussen wrote:
Absolutely not! It's very important to get rid of bugs like this.
On 11.11.2012 17:40, Florian Paul Schmidt wrote:
Cool, another small thing (if I get on your nerves, let me know):
On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
Didn't think about having several paths separated by colons.
Fixed in git now.
Great to hear! It would also be great if you let me know of
features
you miss from Renoise in Radium.
Another small bugreport: Seemingly parsing of LADSPA_PATH is
broken..
I had this in my environment:
LADSPA_PATH=/usr/lib/ladspa:/usr/local/lib/ladspa
Then it doesn't find the CALF plugin.. Using only /usr/lib/ladspa
fixed that..
Going through my sample collection in the sample
player makes radium
hang after the third or fourth sample..
What exactly do you do? Does pressing the down key 3-4 times in a
folder
of flac sound files cause the program to hang?
Let's see if I can get a
trace. I did, but it doesn't tell me too much..
file: Pressed "Kick06.flac............2ch, 20kB"
Header id says it is not an xi instrument: "fLaC".
Num channels: 2
[Here it hangs]
Maybe you could send your samples privately. I've tried
to reproduce by browsing some flac files, but it doesn't hang
here.
6:57 p.m.
On 11/11/2012 06:55 PM, Kjetil Matheussen wrote:
Click on track header -> Create new sample player. Navigate to folder,
single click a few to audition them. On the third auditioning it hangs..
These samples are included in the renoise demo download..
http://files.renoise.com/demo/Renoise_2_8_1_Demo_x86_64.tar.bz2
in the Kicks folder..
Flo
P.S.: How to disconnect two nodes in the audio routing window? :D
Going through my sample collection in the sample
player makes radium
hang after the third or fourth sample..
What exactly do you do? Does pressing the down key 3-4 times in a folder
of flac sound files cause the program to hang?
Let's see if I can get a
trace. I did, but it doesn't tell me too much..
file: Pressed "Kick06.flac............2ch, 20kB"
Header id says it is not an xi instrument: "fLaC".
Num channels: 2
[Here it hangs]
Maybe you could send your samples privately. I've tried
to reproduce by browsing some flac files, but it doesn't hang
here.
7:31 p.m.
On 11.11.2012 18:57, Florian Paul Schmidt wrote:
On 11/11/2012 06:55 PM, Kjetil Matheussen wrote:
Click on track header -> Create new sample player. Navigate to
folder, single click a few to audition them. On the third auditioning
it hangs..
These samples are included in the renoise demo download..
http://files.renoise.com/demo/Renoise_2_8_1_Demo_x86_64.tar.bz2
in the Kicks folder..
Thank you. I can reproduce that. But it's only happen for certain
samples,
and it doesn't matter how many you have already played before. Try to
open
Kick06.flac directly, and it will freeze. As far as I can see, it's
either something wrong with Kick06.flac, or something wrong with
libsndfile,
or I've misunderstood how libsndfile works.
sf_readf_float returns 0 before the file is fully read, which it should
not.
I've cc-ed Erik de Castro Lopo. Hopefully he can shed some light on
this.
It's simple to workaround this though. I'll push a new version now.
Going through my sample collection in the sample
player makes
radium
hang after the third or fourth sample..
What exactly do you do? Does pressing the down key 3-4 times in a
folder
of flac sound files cause the program to hang?
Let's see if I can get a
trace. I did, but it doesn't tell me too much..
file: Pressed "Kick06.flac............2ch, 20kB"
Header id says it is not an xi instrument: "fLaC".
Num channels: 2
[Here it hangs]
Maybe you could send your samples privately. I've tried
to reproduce by browsing some flac files, but it doesn't hang
here. Flo
P.S.: How to disconnect two nodes in the audio routing window? :D
There is a "Help" button in the upper right corner. It says that you
can
either shift+click a connection, or middle-click a connection.
7:57 p.m.
On 11/11/2012 07:31 PM, Kjetil Matheussen wrote:
OK, cool. Thanks :D Another tiny issue: It seems to me that the sample
auditioning seems to play the sample twice the first time one clicks it.
The second time one clicks it it gets played only once.. Maybe it's just
the first buffer of it repeated. I use a large period size in jack and
maybe that's why it's audible (2048 frames).
To reproduce:
Create a new sample player
Navigate to some folder containing .wavs with a sharp attach (to make it
audible)
Single click a sample (attack gets played twice - a slight "stutter" is
audible)
Single click the same sample again (it plays fine now)
Flo
P.S.: Another question: Is there a way to loop a pattern?
http://files.renoise.com/demo/Renoise_2_8_1_Demo_x86_64.tar.bz2
in the Kicks folder..
These samples are included in the renoise demo download..
Thank you. I can reproduce that. But it's only happen for certain
samples,
and it doesn't matter how many you have already played before. Try to
open
Kick06.flac directly, and it will freeze. As far as I can see, it's
either something wrong with Kick06.flac, or something wrong with
libsndfile,
or I've misunderstood how libsndfile works.
sf_readf_float returns 0 before the file is fully read, which it
should not.
I've cc-ed Erik de Castro Lopo. Hopefully he can shed some light on this.
It's simple to workaround this though. I'll push a new version now.
8:08 p.m.
On 11.11.2012 19:57, Florian Paul Schmidt wrote:
On 11/11/2012 07:31 PM, Kjetil Matheussen wrote:
OK, cool. Thanks :D Another tiny issue: It seems to me that the
sample auditioning seems to play the sample twice the first time one
clicks it. The second time one clicks it it gets played only once..
Maybe it's just the first buffer of it repeated. I use a large period
size in jack and maybe that's why it's audible (2048 frames).
To reproduce:
Create a new sample player
Navigate to some folder containing .wavs with a sharp attach (to make
it audible)
Single click a sample (attack gets played twice - a slight "stutter"
is audible)
Single click the same sample again (it plays fine now)
Good catch! I hadn't noticed that before. Will fix, hopefully.
http://files.renoise.com/demo/Renoise_2_8_1_Demo_x86_64.tar.bz2
in the Kicks folder..
These samples are included in the renoise demo download..
Thank you. I can reproduce that. But it's only happen for certain
samples,
and it doesn't matter how many you have already played before. Try
to open
Kick06.flac directly, and it will freeze. As far as I can see, it's
either something wrong with Kick06.flac, or something wrong with
libsndfile,
or I've misunderstood how libsndfile works.
sf_readf_float returns 0 before the file is fully read, which it
should not.
I've cc-ed Erik de Castro Lopo. Hopefully he can shed some light on
this.
It's simple to workaround this though. I'll push a new version now. Flo
P.S.: Another question: Is there a way to loop a pattern?
You mean, for instance, loop between line 10 and 20? No, there isn't.
Do you need it as part of a song (for instance, look an area 5 times),
or just as a way to conveniently listen to a specific part of a block
(pattern)?
If the latter, you can mark the playing start line by pressing Left
Meta + B.
Then you can press Left Meta + Space to start playing from that line.
8:15 p.m.
On 11/11/2012 08:08 PM, Kjetil Matheussen wrote:
Just simply looping a block (to e.g. fiddle with automation, effects
parameters, etc.), without having to press right meta - space all over
again. :D Looping a range of lines in a block would be useful, too, I
guess...
Just a quick heads up: This program looks really promising. I stumbled
over it earlier, but it seems only with this release it has crossed the
boarder of being really, really useful for me (Effects, instruments,
samples, etc.)... Thanks for hacking it up :D
Flo
Flo
P.S.: Another question: Is there a way to loop a pattern?
You mean, for instance, loop between line 10 and 20? No, there isn't.
Do you need it as part of a song (for instance, look an area 5 times),
or just as a way to conveniently listen to a specific part of a block
(pattern)?
If the latter, you can mark the playing start line by pressing Left
Meta + B.
Then you can press Left Meta + Space to start playing from that line.
8:44 p.m.
On 11.11.2012 20:15, Florian Paul Schmidt wrote:
On 11/11/2012 08:08 PM, Kjetil Matheussen wrote:
Just simply looping a block (to e.g. fiddle with automation, effects
parameters, etc.), without having to press right meta - space all
over
again. :D Looping a range of lines in a block would be useful, too, I
guess...
You mean loop the whole block? It's actually impossible not to loop the
block... Doesn't it loop?
Flo
P.S.: Another question: Is there a way to loop a pattern?
You mean, for instance, loop between line 10 and 20? No, there
isn't.
Do you need it as part of a song (for instance, look an area 5
times),
or just as a way to conveniently listen to a specific part of a
block (pattern)?
If the latter, you can mark the playing start line by pressing Left
Meta + B.
Then you can press Left Meta + Space to start playing from that
line.
9:19 p.m.
On 11/11/2012 08:44 PM, Kjetil Matheussen wrote:
For me it doesn't. But just to be totally clear:
- open radium
- enter some notes
- hit right meta + space
The block plays once and then playback ends at the end of the block
Flo
Just simply looping a block (to e.g. fiddle with
automation, effects
parameters, etc.), without having to press right meta - space all over
again. :D Looping a range of lines in a block would be useful, too, I
guess...
You mean loop the whole block? It's actually impossible not to loop the
block... Doesn't it loop?
9:35 p.m.
On 11.11.2012 21:19, Florian Paul Schmidt wrote:
On 11/11/2012 08:44 PM, Kjetil Matheussen wrote:
For me it doesn't. But just to be totally clear:
- open radium
- enter some notes
- hit right meta + space
The block plays once and then playback ends at the end of the block
That's very strange. Does the same happen if you select "Play Block"
from the menues?
How about Continue Block (Right Shift + Space) ? Does it loop?
And what if you have a song with more than one block in the playlist
(for instance the
demo song), does it play more than one block?
Just simply looping a block (to e.g. fiddle with
automation,
effects
parameters, etc.), without having to press right meta - space all
over
again. :D Looping a range of lines in a block would be useful, too,
I
guess...
You mean loop the whole block? It's actually impossible not to loop
the
block... Doesn't it loop?
10:18 p.m.
For me it doesn't. But just to be totally clear:
Actually false alarm. I thought right meta was Alt-Gr on german
keyboards. But Alt-Gr + Space is mapped to Play Song from top. It seems
I don't have a right meta..
Flo
- open radium
- enter some notes
- hit right meta + space
The block plays once and then playback ends at the end of the block
That's very strange. Does the same happen if you select "Play Block"
from the menues?
How about Continue Block (Right Shift + Space) ? Does it loop?
And what if you have a song with more than one block in the playlist
(for instance the
demo song), does it play more than one block? 
9:04 p.m.
Kjetil Matheussen wrote:
Thank you. I can reproduce that. But it's only
happen for certain
samples,
and it doesn't matter how many you have already played before. Try to
open
Kick06.flac directly, and it will freeze. As far as I can see, it's
either something wrong with Kick06.flac, or something wrong with
libsndfile,
or I've misunderstood how libsndfile works.
sf_readf_float returns 0 before the file is fully read, which it should
not.
I've cc-ed Erik de Castro Lopo. Hopefully he can shed some light on
this.
I would be somewhat surprised by that. Is there a reproducable test case
using something like sndfile-info or a small standalone C program?
If so, please raise a ticket on github:
https://github.com/erikd/libsndfile/
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
12 Nov
12 Nov
8:30 a.m.
On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
OK, since you asked: :D some of these might also be the result of me
misunderstanding radium..
- I really dig the ability to have a graph of nodes for audio
processing. But an often needed use case is just a linear chain of
effects which in radium involves lots of clicking and shifting nodes
around to keep the graph in an orderly state. In renoise you have a
linear DSP chain per track.
http://tutorials.renoise.com/wiki/Track_DSPs
This is really useful and allows for quick exploring of sounds. In an
ideal world we could have the cake and eat it, too. I.e. have a full
graph for complex situations and a per Instrument linear effects chain
which facilitates easy adding/removing/reordering of effects..
- Renoise also has the notion of Meta Devices of which some
functionality can be replaced by having a full graph of nodes, but again
it's just very usable to just throw an LFO device into the effects chain
which modulates some effect parameter..
http://tutorials.renoise.com/wiki/Meta_Devices
- Renoise also has this nice edit step feature which I haven't found in
radium yet. Press, for example, Ctrl-4, and after you enter a note the
cursor jumps to the 4th line below it. This allows for super easy
filling e.g. a Bassdrum/Hihat pattern. Go to the first line of the
pattern on the Bass drum track and just hold Y (C note) and it fills the
pattern. Then go to line 3 on the Hihat track and hold down Y to fill
hihats on the off beats..
- On my laptop screen estate is precious. While I like the ability to
use F7, F8, F9, F10 to toggle the different sections of the GUI I'd
really prefer to have these shortcuts to show the section exclusively. E.g.
F7, F8, F9. F10 - switch to the respective Part of the GUI and show it
only. Pressing it again will toggle back to showing the selection of
views as by the point below...
Shift + F7, F8, ... - Toggle the respective part of the GUI
- It would be nice to have tooltips over each element of the GUI. What
are these sliders at the top of each track, etc? How do the lanes right
of the note lanes work? It would make the GUI more discoverable
- Sometimes focus is in e.g. the sample selection dialog of a sample
player and it's not really obvious how to get focus back to the note
track. Or at least I was sitting here confused for a bit. Maybe allowing
explicit clicking to control focus would meet some people's expectations
more?
- It would be super nice if one could double click a slider in an
Effect/Instrument control to enter a value per Text. This way one could
e.g. enter 750 precisely for a delay time.
And finally I also have another question:
Whenever I enter a note in a block playback stops. Is that intended? Is
there a way to keep playback going while editing a block?
Thanks and Regards,
Flo
9:52 a.m.
On 12.11.2012 08:30, Florian Paul Schmidt wrote:
On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
I've tried to have one's cake and eat it too. :-)
* If you right click on a connection between two object, the new object
is inserted in between those two objects.
* If you drop an object on a connection, the object will insert itself
in between those two objects.
* If you delete an object in between two other objects, the connections
on both sides will connect.
These tricks should make the number of operations needed to edit a
linear
chain of effects similar to Renoise.
Great to hear! It would also be great if you let me know of features
you miss from Renoise in Radium.
OK, since you asked: :D some of these might also be the result of me
misunderstanding radium..
- I really dig the ability to have a graph of nodes for audio
processing. But an often needed use case is just a linear chain of
effects which in radium involves lots of clicking and shifting nodes
around to keep the graph in an orderly state. In renoise you have a
linear DSP chain per track.
http://tutorials.renoise.com/wiki/Track_DSPs
This is really useful and allows for quick exploring of sounds. In an
ideal world we could have the cake and eat it, too. I.e. have a full
graph for complex situations and a per Instrument linear effects
chain
which facilitates easy adding/removing/reordering of effects..
- Renoise also has the notion of Meta Devices of which
some
functionality can be replaced by having a full graph of nodes, but
again it's just very usable to just throw an LFO device into the
effects chain which modulates some effect parameter..
http://tutorials.renoise.com/wiki/Meta_Devices
Thanks, that's interesting.
- Renoise also has this nice edit step feature which I
haven't found
in radium yet. Press, for example, Ctrl-4, and after you enter a note
the cursor jumps to the 4th line below it. This allows for super easy
filling e.g. a Bassdrum/Hihat pattern. Go to the first line of the
pattern on the Bass drum track and just hold Y (C note) and it fills
the pattern. Then go to line 3 on the Hihat track and hold down Y to
fill hihats on the off beats..
Great tip. Shouldn't be too hard to implement.
- On my laptop screen estate is precious. While I like
the ability to
use F7, F8, F9, F10 to toggle the different sections of the GUI I'd
really prefer to have these shortcuts to show the section
exclusively.
E.g.
F7, F8, F9. F10 - switch to the respective Part of the GUI and show
it only. Pressing it again will toggle back to showing the selection
of views as by the point below...
Shift + F7, F8, ... - Toggle the respective part of the GUI
That sounds simple. I'll try that.
You can also define your own keyboard configuration by editing
bin/keybindings.conf.
There are no functions available to show a section exclusively yet
though, but I'll
add it.
- It would be nice to have tooltips over each element
of the GUI.
What are these sliders at the top of each track, etc? How do the
lanes
right of the note lanes work? It would make the GUI more discoverable
Sometimes, you get help in the text at the bottom left of the screen.
It will tell you that those two sliders are for volume and panning.
It also tells you what lines right to the note track are.
- Sometimes focus is in e.g. the sample selection
dialog of a sample
player and it's not really obvious how to get focus back to the note
track. Or at least I was sitting here confused for a bit. Maybe
allowing explicit clicking to control focus would meet some people's
expectations more?
Agreed.
- It would be super nice if one could double click a
slider in an
Effect/Instrument control to enter a value per Text. This way one
could e.g. enter 750 precisely for a delay time.
Ok.
And finally I also have another question:
Whenever I enter a note in a block playback stops. Is that intended?
Is there a way to keep playback going while editing a block?
Yes, unfortunately. The player thread doesn't support having a note
list and so fort changing while playing. Doing so requires quite a bit
of work,
which is probably better done by rewriting the player, which should be
done anyway
for other reasons. Earlier, there were a hack implemented which stopped
the player right before editing, and then continued playing right after
editing.
Maybe I can reintroduce that hack again.
10:09 a.m.
Hi Kjetil, thanks for your response :D
On 11/12/2012 09:52 AM, Kjetil Matheussen wrote:
Yes, it makes editing the graph a bit easier, but it doesn't rival the
ease of operation that a linear view provides for the often needed
usecase of linear effect chains, since I find myself reordering the
nodes of the graph quite often to keep the graph tidy. I urge you to try
this out in Renoise and compare the workflow with radium for that usecase.
BTW: Having these operations as you outlined above is similar to how
Blender does its node graph, which is very useful and a feature which I
would like to see in Ingen, too :D
Once I discovered that in Renoise it made adding some variation to a
track very simple :D Also triggering/modifying effects parameters on
track events like note on/off, etc. is very useful, too..
Cool :D
Cool, thanks for that :D Also it's good to hear that the key bindings
are configurable. So I will twiddle those a bit..
Ah OK, I must have just missed that..
Maybe take a look at the RCU pattern, which also was recently discussed
here on LAD which makes this relatively painless given some assumptions
about the playback thread..
Have fun,
Flo
processing.
But an often needed use case is just a linear chain of
effects which in radium involves lots of clicking and shifting nodes
around to keep the graph in an orderly state. In renoise you have a
linear DSP chain per track.
http://tutorials.renoise.com/wiki/Track_DSPs
This is really useful and allows for quick exploring of sounds. In an
ideal world we could have the cake and eat it, too. I.e. have a full
graph for complex situations and a per Instrument linear effects chain
which facilitates easy adding/removing/reordering of effects..
- I really dig the ability to have a graph of nodes for audio
I've tried to have one's cake and eat it too. :-)
* If you right click on a connection between two object, the new object
is inserted in between those two objects.
* If you drop an object on a connection, the object will insert itself
in between those two objects.
* If you delete an object in between two other objects, the connections
on both sides will connect.
These tricks should make the number of operations needed to edit a linear
chain of effects similar to Renoise.
- Renoise also has the notion of Meta Devices of
which some
functionality can be replaced by having a full graph of nodes, but
again it's just very usable to just throw an LFO device into the
effects chain which modulates some effect parameter..
http://tutorials.renoise.com/wiki/Meta_Devices
Thanks, that's interesting. - Renoise also has this nice edit step feature
which I haven't found
in radium yet. Press, for example, Ctrl-4, and after you enter a note
the cursor jumps to the 4th line below it. This allows for super easy
filling e.g. a Bassdrum/Hihat pattern. Go to the first line of the
pattern on the Bass drum track and just hold Y (C note) and it fills
the pattern. Then go to line 3 on the Hihat track and hold down Y to
fill hihats on the off beats..
Great tip. Shouldn't be too hard to implement. - On my laptop
screen estate is precious. While I like the ability to
use F7, F8, F9, F10 to toggle the different sections of the GUI I'd
really prefer to have these shortcuts to show the section exclusively.
E.g.
F7, F8, F9. F10 - switch to the respective Part of the GUI and show
it only. Pressing it again will toggle back to showing the selection
of views as by the point below...
Shift + F7, F8, ... - Toggle the respective part of the GUI
That sounds simple. I'll try that.
You can also define your own keyboard configuration by editing
bin/keybindings.conf.
There are no functions available to show a section exclusively yet
though, but I'll
add it.
- It would be nice to have tooltips over each
element of the GUI.
What are these sliders at the top of each track, etc? How do the lanes
right of the note lanes work? It would make the GUI more discoverable
Sometimes, you get help in the text at the bottom left of the screen.
It will tell you that those two sliders are for volume and panning.
It also tells you what lines right to the note track are. - Sometimes focus is in e.g. the sample selection
dialog of a sample
player and it's not really obvious how to get focus back to the note
track. Or at least I was sitting here confused for a bit. Maybe
allowing explicit clicking to control focus would meet some people's
expectations more?
Agreed.
- It would be super nice if one could double
click a slider in an
Effect/Instrument control to enter a value per Text. This way one
could e.g. enter 750 precisely for a delay time.
Ok.
And finally I also have another question:
Whenever I enter a note in a block playback stops. Is that intended?
Is there a way to keep playback going while editing a block?
Yes, unfortunately. The player thread doesn't support having a note
list and so fort changing while playing. Doing so requires quite a bit
of work,
which is probably better done by rewriting the player, which should be
done anyway
for other reasons. Earlier, there were a hack implemented which stopped
the player right before editing, and then continued playing right
after editing.
Maybe I can reintroduce that hack again.
6:54 p.m.
Le Mon, 12 Nov 2012 09:52:45 +0100,
Kjetil Matheussen <k.s.matheussen(a)notam02.no> a écrit :
I will be very interested by that. Radium is a great program, but it
scale very badly on my 4:3 screen. The main problem for me is to be
able to read the fonts, they look too small. If I make the font bigger,
the radium window goes over the screen boundaries, and overlap on the
next screen of the wm. So, I use a lot Ctrl-Alt-+ and Ctrl-Alt-- for
now.
If I compare radium with another music editor I liked very much (back
to my time with the Amiga), Music-X, the different parts of the
program was on different superposed screens in the same window. I
don't like tabs, they just eat vertical space. Bindings are better, or
a small button somewhere in a corner.
To have separated windows can be an alternative, but they are
less efficient than key bindings.
Dominique
--
"We have the heroes we deserve."
On 12.11.2012 08:30, Florian Paul Schmidt wrote:
> On 11/11/2012 05:02 PM, Kjetil Matheussen wrote:
>>
- On my laptop
screen estate is precious. While I like the ability
to use F7, F8, F9, F10 to toggle the different sections of the GUI
I'd really prefer to have these shortcuts to show the section
exclusively.
E.g.
F7, F8, F9. F10 - switch to the respective Part of the GUI and show
it only. Pressing it again will toggle back to showing the selection
of views as by the point below...
Shift + F7, F8, ... - Toggle the respective part of the GUI
That sounds simple. I'll try that.
You can also define your own keyboard configuration by editing
bin/keybindings.conf.
There are no functions available to show a section exclusively yet
though, but I'll
add it.
11 Nov
11 Nov
8:02 p.m.
Le Sun, 11 Nov 2012 16:30:43 +0100,
Kjetil Matheussen <k.s.matheussen(a)notam02.no> a écrit :
Florian Paul Schmidt mista.tapas at gmx.net
Thank you, it work fine now.
However, I found 2 minor issues. I am making an ebuild to install it,
and found 2 minor issues. At the beginning of Makefile.Qt, it is
libdir = $(prefix)/lib
but on my multilib system, ${libdir} is /usr/lib64
libdir ?= $(prefix)/lib
must be right to be able to manage $libdir in a multilib system.
The second issue is, after installing radium with portage, I get an
executable in /usr/bin/radium, and when I run it, I get:
/usr/bin/radium: ligne 2 :
cd: /var/tmp/portage/media-sound/radium-1.9.1/image//usr/lib64/radium:
Aucun fichier ou dossier de ce type
/usr/bin/radium: ligne3: ./radium: Aucun fichier ou dossier de ce type
In English: No file or directory of this type.
After changing this line into
cd /usr/lib64/radium
radium is working fine.
In the ebuild, the make packages line look like:
emake DESTDIR="${D}" PREFIX="/usr"
libdir="/usr/$(get_libdir)"
BUILDTYPE="RELEASE" OPTIMIZE="${CXXFLAGS}" packages
${D} is the root of the sandbox where portage will build radium.
$(get_libdir) will echo lib64 in my case.
${CXXFLAGS} are the main CXXFLAGS for the system as defined
in /etc/make.conf on gentoo. They are safe flags that should work in
any cases.
The make install line look the same:
emake libdir="/usr/$(get_libdir)" DESTDIR="${D}"
PREFIX="/usr" install
Dominique
fluid_sys.c:(.text+0x10fc): undefined reference
to `readline'
bin/packages/fluidsynth-1.1.6/src/.libs/libfluidsynth.a(libfluidsynth_la-fluid_cmd.o):
In function `fluid_shell_run':
fluid_cmd.c:(.text+0x1b06): undefined reference to `add_history'
Thanks, fixed in git:
https://github.com/kmatheussen/radium/archive/master.zip
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
--
"We have the heroes we deserve."
8:09 p.m.
Le Sun, 11 Nov 2012 21:00:41 +0100,
Dominique Michel <dominique.michel(a)vtxnet.ch> a écrit :
${D} is the root of the sandbox where portage will
build radium.
${D} is the root of the sandbox where portage will install radium
before to copy the files in their final location.
Dominique
--
"We have the heroes we deserve."
8:56 p.m.
Dominique Michel:
However, I found 2 minor issues. I am making an ebuild
to install it,
and found 2 minor issues. At the beginning of Makefile.Qt, it is
libdir = $(prefix)/lib
but on my multilib system, ${libdir} is /usr/lib64
libdir ?= $(prefix)/lib
must be right to be able to manage $libdir in a multilib system.
I've changed = to ?= for both bindir and libdir.
The second issue is, after installing radium with
portage, I get an
executable in /usr/bin/radium, and when I run it, I get:
I didn't get what this was about. Should anything in Radium's build
system
be changed to make making ebuilds simpler?
9:21 p.m.
Erik de Castro Lopo:
Done:
https://github.com/erikd/libsndfile/issues/25
I've linked to a reproducable test case there.
Thank you. I
can reproduce that. But it's only happen for certain
samples,
and it doesn't matter how many you have already played before. Try
to
open
Kick06.flac directly, and it will freeze. As far as I can see, it's
either something wrong with Kick06.flac, or something wrong with
libsndfile,
or I've misunderstood how libsndfile works.
sf_readf_float returns 0 before the file is fully read, which it
should
not.
I've cc-ed Erik de Castro Lopo. Hopefully he can shed some light on
this.
I would be somewhat surprised by that. Is there a reproducable test
case
using something like sndfile-info or a small standalone C program?
If so, please raise a ticket on github:
https://github.com/erikd/libsndfile/
11 p.m.
Kjetil Matheussen wrote:
Done:
https://github.com/erikd/libsndfile/issues/25
I've linked to a reproducable test case there.
Please don't CC email on this mail list. I am subscribed.
Also, to post code in a github ticket you need to make sure whole
block is indented by 4 spaces or more.
My update from github:
Sorry, this code:
while(frames_read < sf_info.frames){
float samples[1024*sf_info.channels];
int read_now = sf_readf_float(sndfile, samples, 1024);
printf("read_now: %d. frames_read: %d. num_frames: %d.\n",read_now,
frames_read,(int)sf_info.frames);
frames_read += read_now;
}
should be considered broken.
The value in sf_info.frames can be incorrect (some validation and
correction is done, but it is not foolproof). The correct usage is
something like:
float samples[1024*sf_info.channels];
while((read_now = sf_readf_float(sndfile, samples, 1024)) > 0){
printf("read_now: %d. frames_read: %d. num_frames: %d.\n",read_now,
frames_read,(int)sf_info.frames);
frames_read += read_now;
}
PS : The only way to ensure that sf_info.frames is correct is to read
in the whole file and that would be slow for anything other than the
shortest of files.
Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/
4177
days inactive
4179
days old
linux-audio-dev@lists.linuxaudio.org
31 comments
4 participants
participants (4)
-
Dominique Michel -
Erik de Castro Lopo -
Florian Paul Schmidt -
Kjetil Matheussen