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

[BUG]The following midi files do not work properly. ;( #2

Open
SysVR opened this issue Nov 21, 2022 · 9 comments
Open

[BUG]The following midi files do not work properly. ;( #2

SysVR opened this issue Nov 21, 2022 · 9 comments

Comments

@SysVR
Copy link

SysVR commented Nov 21, 2022

Format: 1 Tracks: 138 Divisions: 960
Sequence: The Convergence - Unify
Copyright: Copyright (C) 2018 - 2021

Unify - The Convergence | 15.6 Million Notes [Black MIDI]
https://www.youtube.com/watch?v=83CqPViJB0I
*Over 500,000 notes per second.

Please fix the bug.

@starg2
Copy link
Owner

starg2 commented Nov 21, 2022

Where can I get the midi file?

Could you explain what the issue is?

@SysVR
Copy link
Author

SysVR commented Nov 21, 2022

You can enter DiscordServer from Download in the video description and download from unify_updates.

The version used in the performance.
[tim41.7.0-x64-avx2.zip]

@starg2
Copy link
Owner

starg2 commented Nov 21, 2022

Thanks. Listening to the midi right now.

I noticed the tracer window is extremely slow at 0:29. Is this what you mean?

@SysVR
Copy link
Author

SysVR commented Nov 21, 2022

This is because Timidity's pronunciation-related processes are overloaded.

If the maximum channel voice, same tone series, voice, etc. can be set to [NoLimit], the problem of freezing at the tracer will be fixed.
(Probably because it was originally designed for Win2000, the limitation of voices, etc. is to avoid CPU overload and PC freezing.)

Also, a suggestion.
I think the window title should be Win64GUI instead of Win32GUI for 64bit.
The reason is that it will be mistaken for the 32bit version.

Extra.

https://discord.gg/fubXSvVSS4
In.
RED ZONE 88Million 672MB Domino limit (4GBpatch used) cab compression
When I loaded it, the memory used was outrageous at 2:35.

クリップボード

@starg2
Copy link
Owner

starg2 commented Nov 21, 2022

This is because Timidity's pronunciation-related processes are overloaded.

That is because TiMidity is not really designed for black midis.

If the maximum channel voice, same tone series, voice, etc. can be set to [NoLimit], the problem of freezing at the tracer will be fixed.

TiMidity preallocates voice buffers before playing. That's hard to change. It's possible to increase the maximum size, though.

@SysVR
Copy link
Author

SysVR commented Nov 22, 2022

I would like to increase as much as possible for the future, is this possible?

@starg2
Copy link
Owner

starg2 commented Nov 22, 2022

I would like to increase as much as possible for the future, is this possible?

How much do you want for now?

FYI, a single voice requires 35-100 kB of memory depending on the configuration (much more than that if voice effect is enabled).

@SysVR
Copy link
Author

SysVR commented Nov 23, 2022

Based on 100KB, 1GB 5GB 10GB.
In other words, 10,000, 50,000, or 100,000.

After that, it could be automatically calculated during playback by specifying the available memory space.

By the way, I have another phenomenon that I think is a bug, can I post it here?

Or should I split the thread?

@starg2
Copy link
Owner

starg2 commented Nov 23, 2022

Please start a new thread for each issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants