Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows|macOS|Linux|BSD] - Exporting to WAV/VGM/S98 no longer works reliably. #258

Closed
Zexxerd opened this issue Sep 5, 2020 · 6 comments
Labels
bug Something isn't working

Comments

@Zexxerd
Copy link

Zexxerd commented Sep 5, 2020

Checklist

  • I am reporting exactly 1 bug with this issue.
  • This bug hasn't already been reported.
  • [?] This bug hasn't already been fixed in the latest development build.

Bug Description

(Tested on Mac)
In v0.4.4, after confirming any export, the program will often keep trying to export the module to a WAV/VGM/S98 file without actually saving anything. Sometimes, this causes the program to freeze when trying to quit.

How to reproduce

  1. Open a module.
  2. Try to export it.
  3. Watch.

System Information

  • Operating System: MacOS Mojave Version 10.14.6
  • BambooTracker Version: v0.4.4
  • Build Type: Official

#Edit: some wording

@Zexxerd Zexxerd added the bug Something isn't working label Sep 5, 2020
@Zexxerd Zexxerd changed the title [Windows|macOS|Linux|BSD] - Exporting to WAV/VGM/S98 no longer works [Windows|macOS|Linux|BSD] - Exporting to WAV/VGM/S98 no longer works outside of program folder Sep 5, 2020
@Zexxerd Zexxerd changed the title [Windows|macOS|Linux|BSD] - Exporting to WAV/VGM/S98 no longer works outside of program folder [Windows|macOS|Linux|BSD] - Exporting to WAV/VGM/S98 no longer works reliably. Sep 5, 2020
@rerrahkr
Copy link
Member

rerrahkr commented Sep 6, 2020

Thanks for your report. I tested these file export on Windows and macOS, and found that this was happened on only macOS.
It was not synchronized between the export progressbar and the wave view.
I don't know what the cause is yet, so I'll check it out a little more closely.

@rerrahkr
Copy link
Member

rerrahkr commented Sep 6, 2020

I fixed 0Dxx detection in exporting at 0a5f883. Does the bugfixed dev-build work well on your workspace?

@Zexxerd
Copy link
Author

Zexxerd commented Sep 7, 2020

how do I get or make the dev-build?

@OPNA2608
Copy link
Member

OPNA2608 commented Sep 7, 2020

Check the project page, section Downloads -> macOS -> GitHub Builds -> Development builds:. You'll want to pick the option labeled Environment: APPVEYOR_JOB_NAME=for macOS (Modern), then click on the Artifacts 1 tab.

@Zexxerd
Copy link
Author

Zexxerd commented Sep 7, 2020

Yes, the bug-fixed build works perfectly. It seems a bit slow, though.

@Zexxerd Zexxerd closed this as completed Sep 7, 2020
@OPNA2608
Copy link
Member

OPNA2608 commented Sep 7, 2020

That's normal, development/debug builds are expected to be slower than release builds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants