picorims / wav2bar Goto Github PK

Describe the bug
When running Wav2Bar from the CLI, the export process also tries to evaluate it, causing the export to fail.

To Reproduce
Steps to reproduce the behavior:

1. run start \wait Wav2Bar.exe -- export -i "path" -o "path".
2. Look at the end of the logs.

Expected behavior
The video is successfully exported.

Desktop (please complete the following information):

• OS: Windows 10
• Version 0.2.2

Additional context
The export only fails from the CLI, because the code causing the issue isn't ran when not using the CLI.

Describe the bug
FPS, screen size and JPEG export inputs are completely broken. Labels do not show up correctly, and inputs have no effect.

To Reproduce
Steps to reproduce the behavior:

1. Open the application
2. Observe incorrect labels
3. Test the inputs in front of incorrect labels.

Expected behavior
FPS, screen size and JPEG export values should be visible and editable, inputs should have an effect, and labels should be correct.

Desktop (please complete the following information):

• OS: Windows 10
• Version 0.3.2-beta
• MSI installation (no impact on ZIP)

Describe the solution you'd like
I would like to create videos using a command line, the application can have some inputs and export the video.

This is very convenient in case ffmpeg already installed using winget, for example

Describe the bug
Using a mono audio file in a project will result in the export window to freeze and the app to get stuck in a loading state.

To Reproduce

1. Create a new project;
2. Upload an audio file in mono;
3. Add an object, e.g a visualizer;
4. Export the project as a video;
5. Observe.

Expected behavior
The export starts and the export window as well as the progress bar shows the progress of the export.

Desktop (please complete the following information):

• OS: Windows
• Version 0.3.0
• used .msi installer

Additional context
Add any other context about the problem here.

[2022-06-02T18:26:09.660] [INFO] export - audio loaded successfully.
[2022-06-02T18:26:16.340] [ERROR] export - Uncaught IndexSizeError: Failed to execute 'getChannelData' on 'AudioBuffer': channel index (1) exceeds number of channels (1)
source: file:///C:/Program%20Files%20(x86)/Wav2Bar/app-0.3.0/resources/app/js/export_renderer.js
 line: 171
[2022-06-03T18:24:38.870] [INFO] main_renderer - The window will be closed.

when exporting in 1920x1080, only the top left portion of the preview is exported, cutting off the rest of the video. the circle in the screenshot was centered perfectly in the preview.

Describe the bug
A clear and concise description of what the bug is.

working on a project I add a background image, a wavbar of any kind and a timer.
everything works fine while on Wav2Bar and while exporting the rendering shows movement on the bars and timer, but the final exported mp4 does include the bars but the timer object is missing or shows up but static, does not move

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
   not a matter of the process but mostly the final outcome. The timer as an object gets added with no problem, but is not included in the final render

Expected behavior
A clear and concise description of what you expected to happen (if the bug described below didn't exist).
Is expected for the objects to appear in the final render as they are added in the editing process

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Windows 10]
• Version [e.g. 22]
• additional specs judged useful
  **Win 11 x64
  0.3.1 beta, 0.3.0 beta
  ryzen 7 - 32gb
  **

Additional context
Add any other context about the problem here.

How to export more than 10 seconds?

Describe the bug
Using audio extensions that have capital letters in it can cause issues at export.

To Reproduce
Steps to reproduce the behavior:

1. Import an audio file with an extension containing capital letters.
2. Try to export the video.

Expected behavior
The video exports successfully.

Desktop (please complete the following information):

• OS: Windows 10
• Version: beta-0.3.0

Additional context
Using extensions without any capital letters (like .wav instead of .Wav or .WAV) is a workaround to the issue.

The current version of the application allows saving/loading templates.
My use case right now is to switch the audio file being used, change 1 image on a layer, and then export.

It would be a neat feature for the template to be friendly to edit and the application allow rendering from the template via the command line.

Allowing something like:
sed -i 's/old.mp3/new.mp3/g' template > working_template && wav2bar --template working_template --output new.mp4 export

Just something to consider for the remake you have intended.

Describe the bug
Clicking on the browse logs folder button in the settings throws an error.

To Reproduce
Steps to reproduce the behavior:

1. Go to settings
2. Click on BROWSE LOGS FOLDER

Expected behavior
Open the logs folder.

Actual behavior
An error in a new window is thrown.

Desktop (please complete the following information):

• OS: Windows 10
• Version 0.3.2-beta

Additional context
It seems to be an issue with slashes.

Describe the bug
Help of the save section in the project tab is outdated.

To Reproduce
Steps to reproduce the behavior:

1. Go to project tab
2. Hover question marks for all save related options.

Expected behavior
Indicating that it is saved in .w2bzip format, and that audio and video is saved.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Version 0.2.2

Additional context
Can be fixed by updating related strings in save section in assets/help/help.json.

Describe the bug
When opening a very long audio file, it is unclear whether the app is loading or can't support it. The app seems to freeze or stop responding.

To Reproduce
Steps to reproduce the behavior:

1. load a long audio file (more than half an hour)
2. Try to play it
3. Try to save it
4. Try to export it

Expected behavior
The app notifies when it can't proceed the audio. (This would be an evolution)

Desktop (please complete the following information):

• OS: Windows 10
• Version 0.3.3-beta

Additional context
The length required to reproduce the bug depends of the computer capabilities.

Describe the bug
The temporary and logs folder never get cleaned out, slowly consuming the drive where wav2bar is installed.

To Reproduce
Run a number of renders.
Check the temporary folder and logs folder.

Expected behavior
Temporary files are cleared after each render.
Oldest logs get removed if they grow too large.

Additional Info
My system showed over 100gb of usage in the wav2bar temp folder and 2.3 around logs.
A friend showed over 60gb of usage in the wav2bar temp folders.

Windows:

• temp folder is under the wav2bar folder in /tmp (eg: c:\wav2bar\tmp)
• log folder is under the wav2bar folder in /logs (eg: c:\wav2bar\logs)

Mac/OSX:
I ran the build commands to get wav2bar running:

• temp folder: ~/wav2bar/out/Wav2Bar-darwin-arm64/Wav2Bar.app/Contents/Resources/app/temp/
• logs folder: ~/wav2bar/out/Wav2Bar-darwin-arm64/Wav2Bar.app/Contents/Resources/app/logs

I cleaned out the temp/renders folder via: find . -delete (while prompt is in the renders folder)
I used find instead of rm due to an "argument list too long" error using rm.
I cleaned out the logs/ folder via: rm * (while prompt is in the logs folder)