Topic: 1.65

Viewing 5 posts - 1 through 5 (of 5 total)
  • August 5, 2006 at 18:40 #894
    Zynewave
    Keymaster
    • Fix: Optimizations in 1.64 caused MIDI interface output not to work on Windows 2000 or older Windows versions.

    • Fix: Profiling waveforms of imported sounds in 1.64 was not working correctly.

    • Fix: Crash could occur when using the project wizard ‘create tracks’ command on a large number of mappings.
    August 5, 2006 at 20:05 #7253
    Conquistador
    Participant

    @Zynewave wrote:

    • Fix: Optimizations in 1.64 caused MIDI interface output not to work on Windows 2000 or older Windows versions.

    • Fix: Profiling waveforms of imported sounds in 1.64 was not working correctly.

    • Fix: Crash could occur when using the project wizard ‘create tracks’ command on a large number of mappings.

    Very quick fixes! Thanks. 8)

    August 7, 2006 at 12:43 #7257
    francois
    Participant

    Seems to work fine now Frits 😀

    August 15, 2006 at 06:56 #7273
    francois
    Participant

    Hi Frits , i had crashes when i press Alt+crtl+shift+s while podium is playing.Last time before it saved my last audio recording 🙁

    August 22, 2006 at 20:58 #7313
    Zynewave
    Keymaster

    i had crashes when i press Alt+crtl+shift+s while podium is playing

    Saving a sound will lock the data for the duration of the save, so if the sound file is big the engine goes silent after a second or so while the ‘saving sound’ progress dialog is being displayed. I just tried this with a simple arrangement and a single 140 MB sound file. The engine goes silent during the save and then plays again after the save. I could not provoke a crash. To reduce the risk of this sort of crash, Podium could stop playback before saving any sounds, but I’d rather avoid having to put in that restriction. Let me know if it happens again.

Viewing 5 posts - 1 through 5 (of 5 total)
  • The topic ‘1.65’ is closed to new replies.
© 2021 Zynewave