From: Christian S. <sch...@li...> - 2025-09-20 11:40:18
|
On Wednesday, September 17, 2025 11:49:17 AM CEST David Schornsheim via Linuxsampler-devel wrote: > > Considered fixed in Gigedit 1.2.2.svn2. > > Thanks a lot for fixing this so quickly! > > I tried the latest snapshot (2.4.0.svn1_20250914) and noticed two things > with gigaedit when saving a giga studio file: > 1. Saving any file under a new name brings up a warning dialog saying > something along the lines of "Could not import the following sample(s): > libgig error: could no (re)open the file "C:\path\to\newly saved > file.gig" in read-write mode Is that a Windows specific issue? I just made a quick test here and couldn't reproduce it, not on Windows though. > 2. Opening this ~70MB file (original gig file from the SI Symphonic > Brass Collection) and just saving it under a new name produces a huge > 10GB gig file: https://owncloud.gwdg.de/index.php/s/KbngKGggApKN8Zt To bring that specific issue forward, I fear you would need to debug it or find somebody to debug it for you. > Let me know if this mailing list is still the appropriate channel for > reporting bugs. Right now it is. Keep in mind though that currently it's basically two and a half people working on this stuff at all. So the more actively people are participating to investigate and resolve their encountered issues, the higher the chance they get fixed, and vice versa. /Christian |