|
|
A bit more information would be helpful in resolving this issue. Can you try this again with SVN head? Can you provide a screenshot of the session in question? Uploading a whole ardour session is generally too big for mantis, but if you could upload your *.ardour and *.history files from the session's directory that would be good. |
|
2007-04-15 17:45
|
snapshot2.png (151,410 bytes) |
|
2007-04-15 17:45
|
snapshot3.png (152,897 bytes) |
|
2007-04-15 17:46
|
|
|
|
I uploaded a clean session's .history and .ardour, where I tried to do range->export. Also two screenshots two minutes apart, so you could appreciate the slowness of the export. This time I could cancel OK. I will try the SVN head soon as I have the time. Hope this helps. |
|
|
So... it's not crashing, just hanging... According to the rightmost portion of the screenshot, you are completely out of disk space. That would explain a lot about it stopping the export! |
|
|
Although it would be better to detect out of disk conditions more robustly doing so has a bit of runtime cost. Perhaps we could change the color of the disk message(s) to better alert the user in the next release. |
|
|
Don't be hasty. I quess you are guessing my "disk space problems" from the icon of RSIbreak, which is an app that reminds about keeping typing breaks and enforces them too. Nothing to do with my disk space, which is low-ish, but surely not the point. /dev/hdi2 12G 9,3G 1,2G 90% / udev 506M 668K 505M 1% /dev /dev/hda2 30G 28G 947M 97% /home /dev/hdi1 137G 121G 17G 89% /mnt/hdi1 /dev/hda1 157G 112G 45G 72% /mnt/hda1 shm 506M 0 506M 0% /dev/shm /dev/hdb1 58G 50G 7,7G 87% /mnt/hdb So let's not close this bug yet. Furthermore, I never said it's a crash, but a hang. Please read the reports more carefully. Thank you for your work etc, but we poor users report bugs a bit more if we're not pooh-poohed away... If there is a more appropriate bug severity class than crash for this, by any means move it there. Mantis isn't what I work with. Ardour could be. |
|
|
And I do apologize, I was too eager to close this bug as the march towards 2.0 continues. The screenshot of ardour itself shows you have no disk space left. Ardour thinks you have no disk space. I note that even though you may show disk space with df, that it is possible that you cannot write enough to do the export due to being out of inodes or due to quotas on your particular user. as the user (not as root), try copying the ardour directory or at least a sizeable file around in that dir. Other things to try - assuming the above works - turn off dithering - not needed for a 44.1khz export from a 44.1khz export. Otherwise, 44.1khz is working for me (rc1+surfaces branch), and I'm low on ideas to try at the moment. |
|
|
or, startup ardour in a different directory (not home), like, for example, where you are trying to export to... then open the file... |
|
|
Ok, seems it really is a strange diskspace issue. When starting from /home/jussi and exporting to /home/jussi/Desktop it exported ok, but showed 24h+ one second and 00:00:00:00 the next, and again 24h+ the next... but exported ok. When I started ardour in the session dir, everything worked OK. So, no bug, just slightly odd behavior (from my point of view). Close away. Thanks for your help. |
|
|
Aside from making space checking more robust in the future and looking into how the algorithm checks for space across multiple filesystems, this is issue is resolved for this tester. Thank you for the feedback! |
- Anonymous
