October 15, 2019  -  PowerTracks Pro Audio 2019 Build 2 Update Available!

PowerTracks Pro Audio 2019 users can download the FREE Build 2 patch update here

Summary of Changes in Build 2:
Fixed: Sometimes the position of the VST/DX plugs window (even if not visible) would prevent a drop, such as into the drop station, from occurring.
Fixed: When batch converting files, the volume of some file types such as wav/mp3/wma/mp4, etc. would be too low.
Fixed: In Chords Window, you could not enter held chords on Piano track.
Fixed: LeadSheet might not display tied notes on the last bar of a track.
Fixed: Pressing "M" key in Editable Notation to insert a new note at the current time location on the Staff was inserting a duplicate note rather than inserting it above an existing note.
Fixed: Loading in a MusicXML file could result in MIDI notes of zero instead of the currect MIDI notes.
Fixed: Dragging a file into the tracks window didn't always result in the effects slot for the track being setup properly for the file type dragged in.
Fixed: When inserting hard rest, and answering Yes to question about removing notes for the peg, it would remove notes from both clefs instead of the clef that the rest was inserted on.
Fixed: Potential access violation when deleting a note in staff window.
Fixed: Potential jukebox access violation if there were songs with the entire path of the filename being 256 characters or greater loaded into jukebox.
Fixed: Jukebox not playing the playlist in correct order in certain situations involving stopping/restarting, etc.
Fixed: When loading in a MusicXML file that has a specific guitar fretboard defined that matches one of our fretboards, the guitar tablature type will now be set for the notation.
Fixed: Ability to load in .MXL (compresssed musicXML file) as well as ability to load normal noncompressed musicXML file with the new .musicxml extension instead of just .XML.
Fixed: Hammer ons, pull offs, and slides are now being saved to MusicXML files.
Fixed: Exceptionally jittery timing indicator in the notation window during playback compared to older versions of RealBand.
Fixed: If the start of a generated section of a song didn't have a chord entered at the beginning of the section, then it could default to a C major chord instead of the most recent chord prior to the section.
Fixed: Potential access violation if song has micro-pegs and multiple notes on a peg.
Fixed: Accidental element that specified whether a note was displayed as sharp/flat wasn't eing saved to XML, even though the correct pitch of the note itself was saved.

Posted on October 15, 2019 11:50 AM