Not signed in (Sign In)

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorkrundt
    • CommentTimeJun 14th 2010 edited
     
    SynthFont 1.420 has sent me a load of error reports I have never seen before. In effect they all claim the same, "Access violation at address 73BA428E in module 'winmm.dll'. Read of address 0032350D." (Numbers vary) and points to a place in my code where SynthFont is sending a program change message to the Midi Output. I find this error rather strange and almost "impossible". I cannot figure out which change since the previous version (1.412) can have resulted in this.

    I have not yet been able to reproduce this error.

    Is there anyone out there that has experienced anything that sounds like what I have described above? That is, a completely unexpected crash when starting to play a song?

    Thanks a lot!
    Kenneth
    • CommentAuthorkeantoken
    • CommentTimeJun 14th 2010
     
    I haven't had any problems. If Synthfont is sending a message to MIDI out, does that mean you have to be playing with your soundcard's MIDI hardware?

    Is it possibly a single corrupted copy of Synthfont sending all the messages?

    Maybe a compiler error?

    - keantoken
    •  
      CommentAuthorkrundt
    • CommentTimeJun 14th 2010
     
    This can only happen if you have selected MIDI Out for a track in your arrangement. And yes, this is what you would do if you wanted to use an external synth - your keyboard or your soundcard. What intrigues me is that there suddenly seems to be a huge number of people wanting to do this. Why?

    In fact - I think this is a bug in the sense that the user is not really wanting to use the MIDI Out function but SynthFont seems to think he is.

    Kenneth
    • CommentAuthornotsevendy
    • CommentTimeJun 15th 2010
     
    I had no problem connecting Synthfont MIDI out through MIDI Yoke to VSTSynthfont running in VSThost.
    • CommentAuthorkeantoken
    • CommentTimeJun 15th 2010
     
    I'm still running 1.42 with no problems...

    - keantoken
    •  
      CommentAuthorkrundt
    • CommentTimeJun 16th 2010
     
    This is all very strange... yesterday morning I got two crashes almost immediately. Then in the afternoon and evening I run it for hours, playing files from a folder, without one single crash. Hadn't I received so many exactly similar error reports I would say that this kind of crash cannot happen.

    I will not rest until I have sorted this out. (And not release a new version either)
    Kenneth
    • CommentAuthorkeantoken
    • CommentTimeJun 16th 2010 edited
     
    Maybe you could add a user feedback box to the exception reporter, so people can tell you what they were doing.

    - keantoken
    •  
      CommentAuthorkrundt
    • CommentTimeJun 16th 2010
     
    I had it once - no one bothered!
    And, it actually looks like people weren't doing anything when it crashed. Only playing.
    Kenneth