DMayock13
Anyone notice that Fade Start and Exit points have gone missing in the new builds? Had a ton set and they appear to be gone.
Pretty much all other set points appear to still be there.
Pretty much all other set points appear to still be there.
Posté Thu 01 Jun 17 @ 7:31 am
klausmogensen
Like MixFadeStart and MixFadeExit?
Mine appears to still be there (when I click "show all")
I'm on the newest public build (b3734)
Mine appears to still be there (when I click "show all")
I'm on the newest public build (b3734)
Posté Thu 01 Jun 17 @ 10:26 am
DMayock13
3760 here. Lots, if not all, of previously Fade Start and Fade Exits have been erased.
Posté Thu 01 Jun 17 @ 4:06 pm
Adion
Are the poi erased, or just moved?
It looks like the fade points will indeed be recalculated even when set manually, this will be fixed in next build.
In the meantime you can go back to the current stable build until the update is available
It looks like the fade points will indeed be recalculated even when set manually, this will be fixed in next build.
In the meantime you can go back to the current stable build until the update is available
Posté Thu 01 Jun 17 @ 5:46 pm
DMayock13
They appear to be gone entirely.
I'll roll back and check.
I'll roll back and check.
Posté Thu 01 Jun 17 @ 5:50 pm
DMayock13
Rolled back to 3734. Still missing. How far back should I go?
Just want to voice my displeasure over this. I know it is an extremely complicated process to develop software, but it is very frustrating trying to take advantage of new features only to lose older, stable ones. I hope this stops happening.
Please don't take this as negative criticism. I could never do what you so. Just frustrated.
Just want to voice my displeasure over this. I know it is an extremely complicated process to develop software, but it is very frustrating trying to take advantage of new features only to lose older, stable ones. I hope this stops happening.
Please don't take this as negative criticism. I could never do what you so. Just frustrated.
Posté Thu 01 Jun 17 @ 6:29 pm
wickedmix
best way to avoid issues is NOT to use early access updates on your Gig Machine :-)
you will probably need to re-scan the tracks with it missing is my guess
you will probably need to re-scan the tracks with it missing is my guess
Posté Thu 01 Jun 17 @ 7:15 pm
DMayock13
Happened on a public build as well.
Posté Thu 01 Jun 17 @ 7:16 pm
DMayock13
Rolled all the way back to 3678. Still the same issue.
This is as far back as I am willing to go as I pay for the Deezer subscription.
This is as far back as I am willing to go as I pay for the Deezer subscription.
Posté Thu 01 Jun 17 @ 9:21 pm
wickedmix
have you re-scanned a track to see if they come back?
if they are actually removed i can see no other way for them to come back
also i do not have this issue with the latest early access build maybe a mac issue?
if they are actually removed i can see no other way for them to come back
also i do not have this issue with the latest early access build maybe a mac issue?
Posté Thu 01 Jun 17 @ 9:52 pm
DMayock13
Re-scanned them all. No luck.
All files back up on CrashPlan so I can roll back the database if needed.
All files back up on CrashPlan so I can roll back the database if needed.
Posté Thu 01 Jun 17 @ 9:55 pm
Adion
Going back to the current public build will stop it from removing the points from other songs you loaded.
The ones already loaded in current early access will already have been overwritten
It's still strange that they would be gone rather than overwritten though, can't get that to happen here
The ones already loaded in current early access will already have been overwritten
It's still strange that they would be gone rather than overwritten though, can't get that to happen here
Posté Fri 02 Jun 17 @ 5:03 am
DMayock13
Yay!!!
Haha. Can I roll the database back and recover?
Haha. Can I roll the database back and recover?
Posté Fri 02 Jun 17 @ 5:10 am
Adion
Yes kf course, if you revert your database.xml to your backup copy you will have your points back as well
Posté Fri 02 Jun 17 @ 5:18 am