I have a problem for the notes color. I set different colors for the notes and they work very well in the app. But after I rendering the video, all the notes are grey and without texture. Could anyone help me with that?
Thanks!
Sean
6 answers6 replies
Like
Comments (12)
visualmusicdesign
Jun 12, 2020
I really appreciate you sending all of the information! It's all exactly what I asked for.
Unfortunately, I'm still just unable to replicate this issue at all on my own MacBook Pro, which also makes it impossible for me to fix it.
I will try to think of any possible solutions - I would suggest trying at least once to delete the app from the computer and install again.
- If you figure out any setting that allows you to render with the colors working correctly, it might help me understand what's going wrong in this scenario. Does the color work in the render on any of the other color settings?
- Does disabling the "Texture" fix the issue at all?
1
Zixiao Ye
Jun 12, 2020
Replying to
Reinstall the app or disable the "Texture" doesn't fix the problem. But I found that only Dynamic color work in the render, although the color also changes in the final video, the colors are different than how I set. The other color settings all only show grey notes after rendering.
Like
Zixiao Ye
Jun 12, 2020
Replying to
Is there an update coming soon? Maybe a regular update will somehow fix my problem.
Like
visualmusicdesign
Jun 12, 2020
Replying to
There have been updates for the last two days straight... Version 2.1.3 is the most recent. Do you have any other Mac computers you're able to to test it on?
One last thing to try would be to move the app cache folder to the desktop. Move this folder to your desktop:
To easily get to this folder, use the GO menu at the top of the Finder, and select GO TO FOLDER, and copy that address into it.
Like
visualmusicdesign
Jun 11, 2020
It would be helpful if, one time after it happens, you can quit the app, then upload the Log file.
The Log file on MacOS is located at:
~/Library/Containers/com.VisualMusicDesign.SeeMusicUnity/Data/Library/Logs/Visual Music Design/SeeMusic/Player.log
To easily get to this folder, use the GO menu at the top of the Finder, and select GO TO FOLDER, and copy that address into it.
If you have any issues uploading the file to the website, you can email it to visualmusicdesign@gmail.com
1
visualmusicdesign
Jun 11, 2020
Hello - I'm sorry, but I'm testing on a MacBook Pro and am unable to replicate the issue...
It would be very helpful if you could open up Quicktime Player, choose File - New Screen Recording, and make a recording of yourself using the app, doing a short 10 second render, then showing what the render shows.
In the video, can you please also click the Help button from the main screen, so that I can see the Version number?
Thank you!
1
Zixiao Ye
Jun 11, 2020
Replying to
Here is the screen recording!
Like
visualmusicdesign
Jun 11, 2020
Thank you for the information!
Does the issue also exists when you disable the video file and then render?
Could you please upload the original video file you are using?
Thank you!
1
visualmusicdesign
Jun 11, 2020
It would be very helpful if you could record and upload to this post a video screen capture of yourself using the app and rendering, demonstrating the issue.
Please also show your Color Settings, Visual Settings and Player Settings tabs in the video.
What platform and device are you using?
Thank you, and sorry for the issue!
1
Zixiao Ye
Jun 11, 2020
Replying to
I tried again this morning and it's still not right. Below is I attached the screenshos. You can see after rendering the notes are grey without texture.
I'm using MacBook Pro and OS 10.15.5
Thank you!
Like
visualmusicdesign
Jun 11, 2020
Could you please triple check you are using Version 2.1.2? There was a fix for this in an update previously
1
Zixiao Ye
Jun 11, 2020
Replying to
I did check the update. It's Version 2.1.2. I just tried couple more times and the notes are still grey.
I really appreciate you sending all of the information! It's all exactly what I asked for.
Unfortunately, I'm still just unable to replicate this issue at all on my own MacBook Pro, which also makes it impossible for me to fix it.
I will try to think of any possible solutions - I would suggest trying at least once to delete the app from the computer and install again.
- If you figure out any setting that allows you to render with the colors working correctly, it might help me understand what's going wrong in this scenario. Does the color work in the render on any of the other color settings?
- Does disabling the "Texture" fix the issue at all?
It would be helpful if, one time after it happens, you can quit the app, then upload the Log file.
The Log file on MacOS is located at:
~/Library/Containers/com.VisualMusicDesign.SeeMusicUnity/Data/Library/Logs/Visual Music Design/SeeMusic/Player.log
To easily get to this folder, use the GO menu at the top of the Finder, and select GO TO FOLDER, and copy that address into it.
If you have any issues uploading the file to the website, you can email it to visualmusicdesign@gmail.com
Hello - I'm sorry, but I'm testing on a MacBook Pro and am unable to replicate the issue...
It would be very helpful if you could open up Quicktime Player, choose File - New Screen Recording, and make a recording of yourself using the app, doing a short 10 second render, then showing what the render shows.
In the video, can you please also click the Help button from the main screen, so that I can see the Version number?
Thank you!
Thank you for the information!
Does the issue also exists when you disable the video file and then render?
Could you please upload the original video file you are using?
Thank you!
It would be very helpful if you could record and upload to this post a video screen capture of yourself using the app and rendering, demonstrating the issue.
Please also show your Color Settings, Visual Settings and Player Settings tabs in the video.
What platform and device are you using?
Thank you, and sorry for the issue!
Could you please triple check you are using Version 2.1.2? There was a fix for this in an update previously