Found bugs of WaveThunder version:

All found bugs in a version are always solved in the next version.

Wavethunder cannot load color palette for displaying energy diagrams.

conditions
  • After opening a Wavefile with a Shadowfile for displaying Wave in the Window.
effects
  • The color palette is not readfrom the Shadowfile which have the extention ".wtw".
  • When displaying a energy diagram, a default black/white is shown.
workaround
  • To save the Colorpalette, you need to save the color palette seperatedly to the color palette file with extension ".cp1":
    • Main menu: View | Volume
    • Press [Edit Palette...]
    • Press in the new dialogbox on the Save button
    • Choose or type the color palette file
    • Press [Save]
  • After opening the Wave with the Shadowfile, open the saved color palette:
    • Main menu: View | Volume
    • Press [Edit Palette...]
    • Press in the new dialogbox on the colored folder button
    • Choose or type the color palette file
    • Press [Open]

Cannot Open a Factory file (.wtf): "Cannot read file ... : unexpected begin of element "ValueSource", expect end of element "NodeInput", at line n, column m

conditions
  • A Node Input has a (constant) value.
  • A connection to that node is made. The (constant) value should be removed, but is not done so, resulting in a illigal state of the Node Input.
  • The factory is saved into a file.
  • This file is opened again.
effects
  • The file cannot be opened and a errormessage appears.
workaround
  • Open the file using a text editor.
  • Go to the line that is given in the errormessage.
  • Remove element "Value" or "ValueSource" at your own choice:

    • <Value>
      <String>inputname</String>
      <ValueType>String</ValueType>
      <UnitKind>EHNone</UnitKind>
    </Value>

    or

    <ValueSource>
      <NameInput>Input 5</NameInput>
    </ValueSource>

  • Try again opening, it is possible that there are more of such errors in the file.

WaveThunder can crash after deleting a Input Operand of a Builtin Node

conditions
  • The deleted Operand has not the highest sequence number.
  • A action such as adding an operand is followed, to trigger the crash.
effects
  • Crashing by a pointer exception, after a action such a adding a new Operand to this Node.
workaround
  • Avoid deleting a not-last Input Operand from a Builtin Node. Move connections, if needed, and delete the last Operand instead.

WaveThunder can crash while drawing a connected flag

conditions
  • A connected flag is drawed horizontally.
  • A stick has a (almost) exact position in the horizontally middle of the flag
effects
  • Crashing by a assertion failure.
workaround
  • Avoid a note stick in the horizontally middle of the connected flag.
  • Changed the properties of the Stave, to draw loose flag instead of connected flags.

A playset-file cannot be opened

conditions
  • Opening a valid playerset-file.
  • Unpredictable conditions
effects
  • An error occured while opening a playerset-file.
workaround
  • Try opening this file in different conditions, repeat two times in every condition.
  • Restarting the Wavethunder can help sometimes.

Tuplets are not played correctly

conditions
  • Every tuplet is played incorectly.
effects
  • Al notes of the Tuplet are played at the same time instead of a correct time.
workaround
  • Convert Tuplets by non-tuplets.

An error occured while opening a music-file

conditions
  • The Music file to be opened containes one or more staves having RoomUp or Room Down with 30 pixels.
effects
  • Errormessage and failure of opening the music-file.
workaround
  • Be sure that Room Up and Room Down of every Stave is at least 31 pixels.
  • Modify values of 30 pixels in Room Up and Room Down in a higher value by hand (using for example notepad): every XML-element "Stave" has two XML-elements "RoomUp" and "RoomDown", modify these values so every element is greater than 30.
  • Next versions of the WaveThunder will accept values of 30.

changing vertical positions of notes after a changed Clef

conditions
  • The octave of a Clef is changed.
  • The User has answered "No" to the question whether correcting the vertical positions of notes to sound a before.
  • There are Notes after the changed clef.
effects
  • The vertical postions of the Notes after the Clef are changed unexpectedly.
workaround
  • Answer "Yes" (or cancel) while changing the octave of a Clef.

Errormessage "Geen lengte" appeared unexpectedly

conditions
  • One or more Music Parts are empty (has no notes).
  • Actions such as Playing triggered these errormessage
effects
  • Message "Geen lengte" appeared. No failure of actions.
workaround
  • Add notes to every Note Part.

WaveThunder can crash when using too high frequencies in Resonant and Notch Filter

conditions
  • Using Resonant or Notch Filter.
  • The Constant Frequency is higher (or same) than the sample Frequency of the wave.
effects
  • Assertion failed when starting the manipulation.
workaround
  • Be sure to use a lower frequench in the Resonant or Notch Filter than the sample frequency of the wave.
WaveThunder can crash when removing a Stave from Music.

conditions
  • A symbol of a Stave is selected.
  • That Stave is removed using the Music Dialogbox.
effects
  • Access violation immediately after deleting the Stave.
  • Assertion failed at a later time.
workaround
  • Before deleting the Stave, select a symbol of another Stave.
WaveThunder can crash when removing a Note Group from Music.

conditions
  • A note of a Note Group is selected.
  • That Note Group is removed using the Music Dialogbox.
effects
  • Access violation immediately after deleting the Note Group.
  • Assertion failed at a later time.
workaround
  • Before deleting the Note Group, select a note of another Note Group, or select another kind of symbol (not a note).
WaveThunder can crash after closing a project or application, when music dialogboxes are open.

conditions
  • A Music dialogbox or Music Parts dialogbox selected.
  • Close project or application.
effects
  • Access violation immediately after closing.
  • Access violation when altering the dialogboxes, after closing.
workaround
  • Before closing the project or application, close the Music(Part) dialogboxes.
WaveThunder can crash while running a Factory with nonexisting wave names.

conditions
  • Running the Factory.
  • A name of a Wave is used at Input of Nodes.
  • There is no Wave Window with that name.
effects
  • Access violation while running the Factory.
  • Assertion failed.
workaround
  • Before running the Factory, be sure all the names of the wave used in the factory, exists.
WaveThunder can crash while opening a Node Input Values Dialogbox, with wave names.

conditions
  • Opening a Node Input Values Dialogbox.
  • One or more Node Inputs have name of waves.
effects
  • Access violation while opening dialogbox.
workaround
  • Before opening the dialogbox, erase the value of the Wave Node Inputs, by making a connection to the Node Inputs containing the name of Wave.
WaveThunder can crash while adding, editing en deleting music symbols in Music window containing invisible Music Parts.

conditions
  • The Music Window has one or more Invisible Music Parts (Music Parts that are disabled for drawing and playing).
  • Adding, editing and deleting symbols to the Music Window.
effects
  • Crash by an assertion failed.
  • Selecting invisible Music Symbol.
  • Unpredictable result, as mis-clicking symbols, scrolling music etc.
workaround
  • Before adding, editing and deleting Music Symbol, be sure all Music Parts are enabled for drawing and playing.
WaveThunder can crash while running Factory with Buildin Node Sine, Cosine and Tangent.

conditions
  • The running Factory has Buildin node Sine, Cosine and/or Tangent
  • The Input Node "Factor" of this Node is not used (is not nonnected and has no value).
effects
  • Crash by an assertion failed.
workaround
  • Add an dummy Value of 1, with Type Factor, to unused Input of Nodes Sine, cosine and Tangent.
While opening a project, an errormessage occured about duplicate names for the Windows.

conditions
  • Open a project
  • Standard names for windows like "Wave 1" in the project
effects
  • Errormessage.
  • A window without a name.
workaround
  • Avoid standard names for windows, by changing the names, then save or close the project.
Factory Node "Divide": Factor Value divide by a Time Value gives wrong answer.

conditions
  • Using a mathematical Divide Node in a Factory.
  • Operand 1 is a Factor Value
  • Operand 2 is a Time Value
effects
  • Answer is a Boolean Value, but it must be of course a Frequency Value.
workaround
  • None.
Errormessages while opening a Music Parts dialogbox for the first time after starting the application.

conditions
  • Open a Music Parts dialogbox
  • for the first time after starting the application
effects
  • Errormessages.
workaround
  • None.
Errormessages while opening a Music Parts dialogbox for the first time after starting the application.

conditions
  • Open a Music Parts dialogbox
  • for the first time after starting the application
effects
  • Errormessages about the Pitch.
workaround
  • None.
Wrong version Help for WaveThunder 8.0 displayed in the Help dialogbox. It is still the correct Help file for version 9.0

  • After manipulation of Wave Window with Cursor and no part selected, the whole wave was selected and drawed inverted.
  • There was a conflict between the actions Play and PlayMax when activating them successively.
  • Closing or Manipulating a Wave Window which is busy drawing a Volume diagram, a serious error occurred.
  • Wave function Blocking a Wave: Two times lesser count of vertical steps than expected.
  • Block filter a stereo wave using an envelope: error message: assertion failed.
  • Make Block wave using an envelope: the wave contained old mess from memory.
  • Merge Waves Horizontally: change Bytes of Sample did not work.

  • Expand Wave: A tick at the end of the result
  • Notch Filter without envelope: The part outside the selected part of the wave becomes silence.
  • Conversion from Stereo to Mono: Only one of the two channels is used for the mono channel!
  • When dialogbox Selecting and Zooming is open: Setting cursor in a zoomed wave: In dialogbox is field Cursor empty.
  • On some Windows O.S. the toolbars and toolbuttons of the application were black.