-
Notifications
You must be signed in to change notification settings - Fork 25
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
SCD editor not showing loop markers or looping. (BUG) #199
Comments
which |
The one being loaded is music/ex5/BGM_EX5_Field_Sha_Day.scd, but it doesn't matter, even if I load say one I have already done before like Engsinger at music/ex4/bgm_ex4_ban_05.scd no markers will show up Even tried turning off the custom UI JUST IN CASE it was that but no luck :( Doesn't seem to be anything in the /xlog ` ` Turned off Penumbra as that seems to be causing issues but still nothing. For now I will just create a fade in / fade out as I am trying to replace a few overworld songs (which I have done before with perfect loking in the SCD editior. Thanks for all your hard work, I know its is only one TINY part of what this program does, it must be a god damn nightmare to keep it working. |
do you have "Simulate Loop Start/End", under the Settings menu, enabled? (I did not and was seeing the same behaviour) |
(sorry, not sure how to put the tags)
Hi, Thanks so much for this, before I was having to use that old explorerer program and that wasn't cutting it anymore so supper appreciate your work on this!
I've used your plugins SCD editor many times to replace music and normally it shows Markers for looping locations and loops, but currently that is not happening at all.
As you can see this is how it was before with the markers showing loop location
but currently none of that is showing, I have the markers clicked and even put in the location of the loops in the new section just for markers, but nothing shows and the loops also just don't happen.
Maybe I am messing something up somewhere with the new update or it's just not working, I am not entirely sure!
The text was updated successfully, but these errors were encountered: