altruistica
Member
In my attempt to bring together the best of analogue and digital recording, my latest studio refurb includes TASCAM machines including the MSR16, MS-16 and MX2424 recorders, all synced together using a Midiizer and an IF-1000.
It's taken a while to get to this stage, but it all came together yesterday when the Midiizer began to suddenly behave itself right out of the blue!
The problem it has, is that when even using just one machine (in this case the MSR16) as MASTER, the Midiizer will read the timecode from the machine fine, but when the machine was stopped, the Midiizer would carry on counting code. This meant locking two machines was impossible as the SLAVE machine was forever hunting an imaginary position. The only way to stop the Midiizer from doing it was to apply for tension to the reels upon stopping. This lead me to think it was a problem with tape tension, but even after setting the tape tension well above normal, it was still occurring so I reset the tensions (in EDIT, PLAY , REW and FF) all back to where they should be. After dismantling the Midiizer again (along with another Midiizer which needed the battery changing) and removing the EPROMS, upon rebuilding the Midiizer now works as it should, with the proof to see here:
https://www.youtube.com/watch?v=naPL14HbKrI&feature=youtu.be
I can only think now it is either some strange connection /lead problem or more likely, the EPROMS have begun to behave erractically. If anyone has ever seen a Midiizer display this kind of fault (not stopping reading after the machine has stopped and also not reading correct positions during REW and FF) then please let me know what's wrong. The suspense is killing me!
I still have to figure out what's wrong with the other Midiizer. The working one is on EPROM 1.21 I think, and the faulty one (which doesn't operate the serial ACC2 Remote machine commands) but does read timecode is on version 2.00.
Fun and games......
Al
It's taken a while to get to this stage, but it all came together yesterday when the Midiizer began to suddenly behave itself right out of the blue!
The problem it has, is that when even using just one machine (in this case the MSR16) as MASTER, the Midiizer will read the timecode from the machine fine, but when the machine was stopped, the Midiizer would carry on counting code. This meant locking two machines was impossible as the SLAVE machine was forever hunting an imaginary position. The only way to stop the Midiizer from doing it was to apply for tension to the reels upon stopping. This lead me to think it was a problem with tape tension, but even after setting the tape tension well above normal, it was still occurring so I reset the tensions (in EDIT, PLAY , REW and FF) all back to where they should be. After dismantling the Midiizer again (along with another Midiizer which needed the battery changing) and removing the EPROMS, upon rebuilding the Midiizer now works as it should, with the proof to see here:
https://www.youtube.com/watch?v=naPL14HbKrI&feature=youtu.be
I can only think now it is either some strange connection /lead problem or more likely, the EPROMS have begun to behave erractically. If anyone has ever seen a Midiizer display this kind of fault (not stopping reading after the machine has stopped and also not reading correct positions during REW and FF) then please let me know what's wrong. The suspense is killing me!
I still have to figure out what's wrong with the other Midiizer. The working one is on EPROM 1.21 I think, and the faulty one (which doesn't operate the serial ACC2 Remote machine commands) but does read timecode is on version 2.00.
Fun and games......
Al