crash at impact
crash at impact
Ever since newest patch to date (9/19/12) I get this with every rip I attempt
Re: crash at impact
i think this is fixed now, please try r4
Re: crash at impact
Still getting same result
Re: crash at impact
try the rogue (r4+ which will become r5)
https://karaoke.kjams.com/wiki/Downloads/Rogues
https://karaoke.kjams.com/wiki/Downloads/Rogues
Re: crash at impact
This is happening again now with the new patch download
Re: crash at impact
there is a new NEW new rogue. did you use that? if so, then cause the crash and send the crash report. THEN send me a regular email explaining the situation.
Re: crash at impact
I will try the rogue tomorrow and let you know, thanks!
Re: crash at impact
just sent you a crash report. let me know if you more info
Re: crash at impact
I just downloaded the latest version r7 and I got the same message when I right clicked a track and then clicked Export quicktime. kJams didn't crash when I clicked Continue but did crash when I did it a second time and clicked Crash
Re: crash at impact
the latest release "r7" is not the rogue. as i said, please try the rogue.
Re: crash at impact
Tried it, same outcome. e-mailed you report
Re: crash at impact
well, i looked at your report, but it seems to have come from the release, and NOT from the rogue. i checked the code too, and i can assure you this is fixed in the rogue version. did you delete ALL copies of kJams from your computer BEFORE downloading the Rogue? because what i find that people do is they download the rogue, but then they just run the previously installed release version (leaving the rogue still zipped in the Downloads folder)
Re: crash at impact
Just tried it with the rogue and it worked OK when exporting Quicktime. I then closed the rogue and opened the r7 and when I tried the export Quicktime I got the "about to crash message" so the rogue fixed it
Re: crash at impact
please don't have more than one copy of kJams on your computer at a time. otherwise you may run the wrong version. which, i believe, is why this took so long to resolve.