Arpasing Question + weird oremo glitch (?) +extra questions

[Miawerz]

So i was going to record a new arpasing bank (already done 3) but since weird stuff happened when i recorded the last one i decided to ask some questions and help
.....
so i was thinking, *is the old n-gram coverage totally unnecessary? Well, if so then there's no need to record them but for the banks where i already recorded them, *would deleting this files be fine or they could still be of some use?
................
now for the weird oremo glitch (i think, or probably i just did something stupid w/ it):
i already recorded 2 arpasing banks w/ no problem and i've been using these short chinese CVVC guide bgm's and they're fine... but for some reason when i recorded my 3rd bank, the samples were cut early... it was also recorded w/ the new 2.0 arpasing reclist... related? probablynotlol
so i fiddled w/ the .txt files of the guide bgm's and it kinda worked? w/c is weird because why would i even need to do that it worked before lol....
...........................
extra questions:
also apparently if you record an incomplete bank the index file won't let moresampler oto the bank (? idk if it was fixed ore sumthin)
it said "error reading file ____" (w/c is where i stopped recording because i don't think squidloid needs all the samples.... i recorded the core list only)

idk if that info was helpful but added it because i think it's sorta weird... (i deleted the extra parts in the index file so moresampler's auto-oto would work)
..................................
one last thing
so the oto moresampler generated for my 3rd arpasing vb was horrible (it even otoed on the silence parts)
and i thought maybe in theory if i copy-paste the oto generated from prev. vb maybe it wouldn't be as bad cuz it's recorded w/ the same guide bgm......... it was a lot worse
the oto seems to be off-tempo or something.... but i think it's recorded w/ the same tempo... unless fiddling w/ the .txt file did something or i'm stupid and that's not how things work lol



well that was a lot
i apologize if some questions maybe stupid/ already answered... i just wan't all that^ to not happen when i record a new arpasing vb ^^'

 

[Kiyoteru]

so i was thinking, *is the old n-gram coverage totally unnecessary? Well, if so then there's no need to record them but for the banks where i already recorded them, *would deleting this files be fine or they could still be of some use?

For banks you've already recorded, if you want to add the new samples to them, then you can leave the old samples in. Be sure to regenerate the OTO once you add the new samples, but make sure the index actually contains entries for all of them. It can be edited like a plain text file, so you may need to do some stitching together to get all 000 to 334.

now for the weird oremo glitch (i think, or probably i just did something stupid w/ it):
i already recorded 2 arpasing banks w/ no problem and i've been using these short chinese CVVC guide bgm's and they're fine... but for some reason when i recorded my 3rd bank, the samples were cut early... it was also recorded w/ the new 2.0 arpasing reclist... related? probablynotlol
so i fiddled w/ the .txt files of the guide bgm's and it kinda worked? w/c is weird because why would i even need to do that it worked before lol....

Weird, I have no idea what happened.

extra questions:
also apparently if you record an incomplete bank the index file won't let moresampler oto the bank (? idk if it was fixed ore sumthin)
it said "error reading file ____" (w/c is where i stopped recording because i don't think squidloid needs all the samples.... i recorded the core list only)

idk if that info was helpful but added it because i think it's sorta weird... (i deleted the extra parts in the index file so moresampler's auto-oto would work)

Yeah, moresampler is looking for every audio for everything in the index. If you're trying to use just 0.2.0 but it still has the numbers from 0.1.0, you can safely delete those. Future downloaders of the pack should have things set up properly.

one last thing
so the oto moresampler generated for my 3rd arpasing vb was horrible (it even otoed on the silence parts)
and i thought maybe in theory if i copy-paste the oto generated from prev. vb maybe it wouldn't be as bad cuz it's recorded w/ the same guide bgm......... it was a lot worse
the oto seems to be off-tempo or something.... but i think it's recorded w/ the same tempo... unless fiddling w/ the .txt file did something or i'm stupid and that's not how things work lol

Modifying the numbers in the BGM txt does change the timing of things. I assume that everything was off-time by the same amount, so it's more like all the otos just slid to the side, rather than getting stretched or squeezed. Maybe a batch edit of the audio might realign things?

 

[Fanicom]

Oremo is evil!
1) Teh old n-gram coverage is still OK to use- the new one just helps people so their diphones would have more... "expression" to 'em, I assume. Either of them does its job, but it don't mean ya need to record both :'v unless you want more duplicates to oto! kkkkkkk
2) Maybe you were pretty lucky to get the first 2 pitches on time. BGMs work with those milisecond settings on the .txt, configures the offset and cutoff on yer recordings. You probably fiddled with those?
3) To avoid that evil oto error, you need to erase from the old index.csv entries 120 - 219 and put it back inside the bank you wanted More-chan to oto. It will work fine after that. But if you're confused, here' s a copy you can use! https://drive.google.com/open?id=0B7gHB4HlFEQ2NHhjamhoNHJoWGc
4) You using setparam by any chance? If you just switched banks while otoing, you sometimes gotta close the program and open it again ;<;

 

[Miawerz]

@Kiyoteru , @Fanicom
thanks for your help/response! ^^
the problem i'm most concerned tho is the oremo related.... oremo IS EVIL i guess...

Modifying the numbers in the BGM txt does change the timing of things. I assume that everything was off-time by the same amount, so it's more like all the otos just slid to the side, rather than getting stretched or squeezed. Maybe a batch edit of the audio might realign things?

oooooh i haven't thought of that lol.... i'd try it if that error happens again when i record my new bank, thanks^^

2) Maybe you were pretty lucky to get the first 2 pitches on time. BGMs work with those milisecond settings on the .txt, configures the offset and cutoff on yer recordings. You probably fiddled with those?

when i recorded the first 2 banks everything's fine, i don't need to do anything just record lol.... then i decided to record a third one then oremo magically cuts-off the recording early ;_; idk what happened.... i'm pretty sure i didn't change anything w/ the .txt files before....at that time is when i changed the cut-off so it actually records everything..... then the 4th problem came....if it's related lol

4) You using setparam by any chance? If you just switched banks while otoing, you sometimes gotta close the program and open it again ;<;

uhm...nah...

 

[VocAddict]

now for the weird oremo glitch (i think, or probably i just did something stupid w/ it):
i already recorded 2 arpasing banks w/ no problem and i've been using these short chinese CVVC guide bgm's and they're fine... but for some reason when i recorded my 3rd bank, the samples were cut early... it was also recorded w/ the new 2.0 arpasing reclist... related? probablynotlol
so i fiddled w/ the .txt files of the guide bgm's and it kinda worked? w/c is weird because why would i even need to do that it worked before lol....

I don't know if any of this will help but here it is anyway.

I experienced this problem once before I don't remember how I fixed it lol. It seems to be a delay between the mic and the OREMO. I would suggest trying the different audio input options in the program itself, or maybe decreasing the delay. Maybe you're recording slightly off-time with the BGM I doubt though

It could be a audio driver issue that's causing it so you can check that as well. Also, restarting a computer does wonders.

 

[Fanicom]

AHHH THANK YOU FOR THAT I was so confused on how to edit the index

Yer welcome! òwó

 

[Miawerz]

I don't know if any of this will help but here it is anyway.

I experienced this problem once before I don't remember how I fixed it lol. It seems to be a delay between the mic and the OREMO. I would suggest trying the different audio input options in the program itself, or maybe decreasing the delay. Maybe you're recording slightly off-time with the BGM I doubt though

It could be a audio driver issue that's causing it so you can check that as well. Also, restarting a computer does wonders.

OwO thanks! i'll try it out if the problem happens again lol
i did restart my laptop when that happened... didn't seem to work tho (or maybe it works now?)