Open GoogleCodeExporter opened 9 years ago
Forgot to add, same result when opening from the File menu as well.
Original comment by sir.shan...@gmail.com
on 7 Oct 2010 at 1:30
Please attach the problematic .cue file here.
Original comment by tmkkmac
on 31 Oct 2010 at 3:24
shoot, I since reverted back to previous version, successfully converted and
deleted it. If it happens again (now on the latest build) I'll come back to
post it.
Original comment by sir.shan...@gmail.com
on 31 Oct 2010 at 11:12
hello. This is to report that the newest version 20130601
and the previous one, 20130407, do crash when loading a .cue sheet
that was typed manually, for a 24/96 Vinyl Rip,
no matter how method you use to load the .cue.
Tried erasing the .plist file, nothing.
Erased then also it and jp.tmkk.XLD.LSSharedFileList.plist, to no avail.
Then I read the REM initial line issue, which these .cues had,
and tried that as well, and once again after a .plist deletion.
Lastly, I messed a bit between Mac OS Roman and UTF-8. No again.
I had to revert to 20130127, which hasn't had any similar issue during the past
three to four years.
Not before, nor after today, had I installed in ANY the checksum pluguin.
That is all. BTW, normal .cues (of an already splitted rip), opened flawlessly
in both late versions.
I have attached the .cue for the REM unedited Vinyl B Side
(also here, http://cl.ly/102R2Z1Q303e), just in case you'd need it.
Regards.
Original comment by deo...@gmail.com
on 2 Jun 2013 at 2:40
Attachments:
The cue sheet itself has no problem. As far as I've tested the latest XLD loads
.cue without crash.
Uploading a crash report may help.
P.S. you should create a new topic for it.
Original comment by tmkkmac
on 2 Jun 2013 at 5:50
I will naturally do that. Tenks, tmkkmac...
Will research into this web's interface to learn how to post my first. I take
there is no incompatibilty between two different versions installed at the same
time on the same system, in my case, ML.
Original comment by deo...@gmail.com
on 2 Jun 2013 at 12:00
Original issue reported on code.google.com by
sir.shan...@gmail.com
on 7 Oct 2010 at 1:29