From Resound-wiki
- Loading an rpf file into a different size matrix - predictably causes problems if you save an rpf, restart GUI with a larger matrix and load the file.
- Node Locks: Nonsense audio if lock is removed while audio is playing. Doesn't cause crash but seems to loop buffer.
- Presets: Same buffer skipping problem if a null preset is selected. Presets need to be tested further.
- Removing a behaviour whose parameters have been assigned to a fader causes crash. -- fixed in rev 155 pending testing
- Note: crash doesn't happen straight away; only when you return to the Performance view. Suspect something to do with graphics...? Backtrace suggests Resound::ParameterVUMeterWidget::OnPaint
- Suspect this is because when a behaviour is destroyed its parameters are not removed from collectives (could this be a red herring?)
- Crash seems to occur at src/resound_gui/vumeterwidget.cpp line 150-153
- Console output as follows:
---- Resound Client Running ----
Remove Parameter: /bm/mp_crossfade_0/amp
Address has been removed: /bm/mp_crossfade_0/amp
Address has been removed: /bm/mp_crossfade_0/amp
Address has been removed: /bm/mp_crossfade_0/amp
Remove Parameter: /bm/mp_crossfade_0/pos
Address has been removed: default
Address has been removed: /bm/mp_crossfade_0/pos
Address has been removed: default
Address has been removed: default
Address has been removed: /bm/mp_crossfade_0/pos
Address has been removed: /bm/mp_crossfade_0/pos
Behaviour 0~BehaviourViewItem
Behaviour~ mp_crossfade_0
resound_gui: /usr/include/boost/shared_ptr.hpp:315: T* boost::shared_ptr<T>::operator->() const [with T = \
Resound::Parameter]: Assertion `px != 0' failed.
Aborted (core dumped)
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7515875 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7517201 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb750eb6e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#4 0x081491f5 in boost::shared_ptr<Resound::Parameter>::operator-> (this=0xbfd6c894)
at /usr/include/boost/shared_ptr.hpp:315
#5 0x0818e56b in Resound::ParameterVUMeterWidget::OnPaint (this=0x8677810,
event=@0xbfd6cae4)
at /home/james/sandbox/resound-0.1.104/src/resound_gui/vumeterwidget.cpp:151
#6 0xb77bd905 in wxAppConsole::HandleEvent () from /usr/lib/libwx_baseu-2.6.so.0
#7 0xb784cfb2 in wxEvtHandler::ProcessEventIfMatches () from /usr/lib/libwx_baseu-2.6.so.0
#8 0xb784d0fd in wxEventHashTable::HandleEvent () from /usr/lib/libwx_baseu-2.6.so.0
#9 0xb784d27f in wxEvtHandler::ProcessEvent () from /usr/lib/libwx_baseu-2.6.so.0
#10 0xb7a140b9 in wxWindow::GtkSendPaintEvents () from /usr/lib/libwx_gtk2u_core-2.6.so.0
#11 0xb7a143f9 in ?? () from /usr/lib/libwx_gtk2u_core-2.6.so.0
#12 0xb72a61de in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0
#13 0xb6ecb772 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#14 0xb6edc323 in ?? () from /usr/lib/libgobject-2.0.so.0
#15 0x086805e8 in ?? ()
#16 0xbfd6ccd0 in ?? ()
#17 0x00000002 in ?? ()
#18 0xbfd6cdac in ?? ()
#19 0xbfd6ccbc in ?? ()
- Cancelling Store Preset dialog causes seg fault. -- fixed
- Presets when saving performances. The currently selected present always gets copied into preset 0 when saving files, overwriting the contents of preset 0. All other presets appear to be saved correctly. (Workaround is to always select preset 0 before saving). -- fixed
- Behaviours stop working after a certain length of time. It doesn't cause a crash; the behaviour simply stops working. Suspect this may be to do with the way angles are calculated viz. wrap-around. -- fixed rev 157
- Compiler flags for debug or build have to be set manually in cmake scripts.
- Command line flag to show version. We need one: --version and -V (-v already used for verbose) -- added rev 156
- Compatibility viz. node locks. Not sure about compatibility with rpf files saved from earlier revisions, especially viz. node locks. I think some weird things happened when I loaded an rpf saved from an earlier version. Either needs to be patched or declared 'officially' incompatible.
- Saved file names. .rpf could automatically be appended to saved file name if not explicitly stated by user.
- Matrix node locks - initialisation / refreshing. Saved a performance file with some matrix parameters locked. Close GUI, re-open and load saved performance file. Matrix locks *appear* to be correct (graphically, the locked parameters are visible) but they aren't really locked. You have to toggle the lock manually. Fixed in rev 160
- Closing the Server while client is still running. If you close the server but leave the Client open, then re-start the server, OSC messages are still sent and received but audio connections do not appear to be re-made Fixed in rev 161 - added Force Update option in GUI
- After loading a saved rpf file, creating a Multipoint Crossfade behaviour consistently caused a seg fault. This may have been because one had previously been deleted before the patch was saved as it doesn't seem to happen with every loaded rpf file.
- Removing an element from a collective caused a seg fault. (Try to replicate: I think this might have been due to the wx2.8 problem). assume fixed
- Wireless: Using a wireless connection between separate server and GUI machines tends to cause the system to hang. I've only tried wireless on the GUI machine side. This may be related to unreliable wireless networking in Ubuntu.
- Node Locks: cannot be unlocked with right-click when at maximum or minimum value. This is actually just a display update issue.
- Bug with libwx-2.8 -- need to force cmake to link to libwx-2.6 only.
- Potential changes to cmake files so it will only link with 2.8 libraries
- After loading a saved rpf file, creating a behaviour consistently caused a seg fault if any behaviour has previously been deleted before the patch was saved.
- Clicky interpolation with fast parameter changes
- Esp. noticeable with automated behaviours, e.g. Mexican Wave
- Running GUI with large number of inputs
- Causes Matrix tab to get larger and larger, eventually causing GUI cock-up. Esp. noticeable with e.g. 24 inputs. Outputs do not cause a problem as these expand horizontally with a scroll bar.
- Assigning the same input to multiple outputs within multiple collective elements
- Hard to explain, but I think the assignment failed in some way, or maybe I failed in some way.
- Load this .rpf file into the GUI. It consists of one Multipoint Crossfade behaviour. The position is assigned to Fader 17, the amplitude is assigned to Fader 25. The 'wave' should appear across all input-to-output busses (see the collective: assignments from input 6 are made) but input6-to-anything doesn't show any parameter mapping in the Matrix window.
- File compatibility viz. scalable node locks?
- Control of matrix node locks is inverted - fixed in branches/resound-0.1.104 rev.122
- Unlocking matrix nodes -- wasn't really a bug - use right click
- zipper noise - improved, pending further testing
- Matrix node locks - initialisation / refreshing
- Closing the Server while client is still running
