On Monday, October 10, 2011 02:56:47 PM silverbear wrote:
> Apologies for delay in replying.
> 
> Re: cards being repeated in the same session:  I had 3 repeats in
> today's scheduled words (i.e. not learning ahead). I'd marked them as
> 3 the first time they showed up though though they'd probably marked
> as 4 or 5 in previous sessions. The repeat seemed like a good
> reinforcement to me so no problems. I'll monitor this during the next
> week.

It's certainly not as intended. If it occurs again, could you send me your 
'log.txt' file?

> I think I had so many on Saturday because I was learning ahead of
> schedule (playing with my new toy!).

Looks like a bug in learn ahead of schedule. 

BTW, learning ahead of schedule is not really recommend to be used often. For 
cramming, there is a shiny new toy which is the cramming scheduler plugin.

> Re: acented sound files: will the correction you' ve done be in the
> next beta release?

Yes.
 
> Re: suffices on file names: I'll be installing Mnemosyne 2 on another
> computer in the next day or so; I'll confirm the sound file changes
> then.

OK.

> Out of interest, will the Google Text-to-speech plugin work with
> Mnemosyne 2?

Needs to be rewritten, sorry...

Peter

> Kind regards
> Barbara
> 
> On Oct 7, 7:11 pm, Peter Bienstman <[email protected]> wrote:
> > > Hi Peter,
> > > Sorry about previous null message - fat fingers!
> > > 
> > > I'm giving beta6 a go and it's good stuff!
> > 
> > Glad you like it!
> > 
> > > FYI:
> > > - sound files with accents in the name still don't work (e.g.
> > > árbol.mp3);
> > 
> > Thanks, should be fixed now.
> > 
> > > sorry if I'm jumping the gun here, I know you're still in beta.
> > 
> > Not at all. Better to send these bug reports now, as opposed to waiting
> > until the release. Otherwise, what's the point of a beta :-)
> > 
> > > - when importing from a version 1 database, a small number of the
> > > sound files gained a _1_ suffix e.g. mano_1_.mp3 within the database.
> > > I couldn't see any obvious pattern to the file names or the files to
> > > cause this
> > 
> > This happens if you use the same sound file multiple times. Mnemosyne
> > will then creates a second copy of the file to make sure they don't
> > interfere.
> > 
> > > (I've edited them now so it's OK).
> > 
> > You shouldn't really need to edit them in order to get it to work. If it
> > does not work, then it's a bug, and I'd appreciate you mailing me your
> > mnemosyne 1.x directory privately.
> > 
> > > - the repetition algorithm seems to repeat more within the same
> > > session now; is this intended?
> > 
> > Could you elaborate a bit more what exactly happens and under what
> > circumstances?
> > 
> > The algorithm should be essentially the same. If anything, immediate
> > repetititons of the same card should be avoided better.
> > 
> > This being said, I'm aware of a bug in the scheduler where it sometimes
> > gets 'stuck' on a failed card and does not move to unmemorised cards. Is
> > this what you mean?
> > 
> > Keep the feedback coming!
> > 
> > Peter

-- 
Peter Bienstman
Ghent University, Dept. of Information Technology
Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium
tel: +32 9 264 34 46, fax: +32 9 264 35 93
WWW: http://photonics.intec.UGent.be
email: [email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"mnemosyne-proj-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/mnemosyne-proj-users?hl=en.

Reply via email to