You might also try this for the display issue. Go into Advanced Settings and change response mode to Slow.
Does the display issue change at all in Slow mode?
Rich
I understand the Response mode is for the antennae, I just tried changing it and the flicker issue is still there…
Y’know, it seems that people are reporting this display problem after they have upgraded their firmware.
SO,
I’m sure it would be useful to know if this is indeed a byproduct of something in the new firmware.
Could any of you that are having this problem load the old firmware back in (1.0.4, still available for download at the Moog download page) and see if the weird display problems go away? Follow the same update procedure as before, erasing the current firmware and then reloading the 1.0.4.
It would also be useful to know if:
Does this happen even when the unit is sitting idle, or
Does it only happen when using the pitch antenna, volume antenna, or both?
Does it have to warm up to do this?
Does it only happen when hooked up to the editor, or in stand alone (unhooked) as well?
seems my zippering display has disappeared!
using mac and the C6, i did the following: started the theremini for the erase procedure as told, and sent the erase file from the 10.4 packet. quit C6. started C6 again and sent the new 1.1 firmware. (i did so just to make sure C6 has only the new fw showing up in the window.) restarted the theremin and calibrated as told.
seems to work.!
(i firstly had it done like: after putting the theremini into the erase modus, as told, started C6. from the 1.1 package, loaded the erase file, and sent it. then loaded the new fw, so the window shows both files, highlighted the new fw and sent it, then reboot and calibrated.)
any body can confirm that experiment? does this make sense? anyhow…
happy new year to all…and let’s hope we don’t have to solve all of our troubles on our own.
Hmm. I use C6 on windows. Load the erase file and send. Then I load the firmware file and make sure it is highlighted and send.
Maybe on MAC you have to load/send, get out and then load/send the firmware.
Both are in the list when I do it. Can you recall if you had the firmware highlighted before sending the first time you did it?
Rich
firstly: trying to reproduce a certain issue is delicate and leads into trouble. after some erase/uploads it’s still gone now. the display zipper. i think it was firstly out of the box in pre-10.4 firmware state. unfortunately i did not check this. so i loaded the 1.1 right away on it. mine never saw the 10.4 firmware.
more important.: as said, messing around with those erase/uploads leads into trouble. but science need sacrifices :
claymenia, i have now the same issue like you… not sure why that happend but after another erase/upload procedure it fell dead-silent and the presets exactly like you described. so i hooked up the ipad, hope you have one, for the theremini app. because i thought that some under the hood settings went to zero and as a matter of fact some mostncertainly did: in the preset volume: zero, in the advanced menu volume antenna volume: zero. seems like the library can get corrupted somehow.
turn those virtual knobs up or replace right away the theremin presets with library presets one by one, and your t-mini sings again! no bullshit.
i realy wonder how it can be solved without the app!!!
any way to swap entire preset libraries in one go, or is it realy preset by preset? yawning.
Regarding my post above, some more bad news: the ipad editor app crashes after a while. First it worked well, But then happend this:
Each time asked if i want to oberwrite the preset i’ll try to confirm with yes. the app crashes, but stores also a bit of the preset into the theremini. Mostly misses the effect settings, and also adds some wierd extra characters after the preset name. I tried different ipads with the same results.
Some theremini-memory internals seem to have gone haywire in the basics. Also when trying out, on the editor, presets from the factory library, there are some issues with loading the preset effect. In the small window for the delay time settings (off/preset/slow…etc) it always jumps back to preset when trying to change it. no matter how the “loading preset” settings are in the advanced submenu on the theremini. the display also only shows for fx Preset, even if stored differently.
I already tried factory reset start, reinstallation of the fw, another download/ unzipping of the fw, even different usb cables, without success.
Any further idea what’s wrong or a possibillity to get this solved?
What IOS are you using?
hi rich, i’m using 5.1.1 on the first generation ipad. this one can’t get further updated anymore and 7.1.1 on the ipad2. and no, i don’t want to update to ios 8 right now.
both worked with the theremini editor perfectly. i even wondered that the first ipad worked without problems, because of the old ios.
it realy must be in the theremini. no doubt. some write/read onto the internal storage difficulties. i think it needs a full erase and a full new setup of the library etc..
so far, i could get it back sounding. as described before. with alot of difficulties, but it works somehow. hard to describe in english. whatever, as it is with those workarounds : the problem is still there and might even botch things up elsewhere in the unit.
(when sysex erase of the theremini, it erases down to block c. that’s ok? (block a an b got not erased))
d’ni,
Thanks.
You can log a ticket with Moog if you like.
However, they are aware of the issue and are looking into it.
Rich
Hello Everyone,
If anyone encounters this problem after updating the Theremini to the newest firmware, it is a simple matter to correct. It merely means that the presets need to be updated to a compatible version.
Please contact me directly at andy@moogmusic.com and I will be happy to provide for you the sysex file necessary to do the preset installation!
Thanks,
Andy Hughes
Tech Support Manager
Moog Music, Inc.
Hello Everyone!!!
Andy from the Moog Tech Support Lab here…we are aware of this unusual behavior in the new firmware and are working diligently to find a solution.
If anyone here is interested in beta testing a patch for this please email me at andy@moogmusic.com for details. One caveat: This is a beta level firmware that we are testing, so if your instrument is critical please continue to run the stable current public release until we can get this sorted.
Thanks to all of you for your patience!
Andy Hughes
Service Department Manager
Moog Music, Inc.
Hi Everyone!!!
Andy Hughes from Moog Tech Support here!
We are aware of this odd bug in the new firmware, and our programmers are hustling to find a fix for it.
Thanks in advance for your patience, and hang tight, hopefully a patch will be available very soon!!!
Thanks,
Andy Hughes
Service Department Manager
Moog Music, Inc.
thanks andy,
my previous posted issues have magically dissappeared.
just loaded the given tmini_presets_1_0_3.syx file into c6, made sure the theremini showed up in config, and hit send. right into the already running theremini, then restarted it.
Regarding the flicker on the screen, the bug is now gone too! I updated again today and the theremini is working almost perfect!
I noticed, however, that the note range includes both high and low notes regardless of the root and scale set in the preset. I would call this a bug and not a feature…
Not sure what your problem with range is. That’s a global setting on the Theremini and I don’t see what Scale or Root have to do with it. Root is needed to be able to quantize the desired scale correctly. I think there should be no connection between range and root. It’s perfectly ok to have a root of F but a range that say goes C1..C6. In fact you want the range to be independent of the root.
But perhaps I’m not really sure what you are getting at here.
Now when you play with the transposition function in the app, that’s a different story. That will affect range.
Rich
Maybe I didn’t made myself clear enough.
the thing is that, whichever scale and root you choose, both high and low notes are included, even if they don’t belong to neither scale nor root…
Ah. So if you set Root/Scale to C/Ionian and Range to say C#1..C#6, it plays the C#s when you go the full range of the scale?
If that is the case ( I never checked that) I would agree that is an error in quantization output - unless you set a scale that’s supposed to contain a C#/Db with a C root.
Though easy enough to fix by changing global range.
Rich
bichuelo,
i have about the same problems, that worries me. the note range changes with every preset i choose, no matter how i set low and high note in the theremini setup menu note range. meaning, i can put c< for and c8 for high, while playing then and change presets, those values get changed too. that changes the pitch field depending on the preset and not on the setup values. didn’t get it. it’s maybe that semitone settings, that confuses. or the theremini mode.
but the ipad app also does not show the correct high and low note values in the global settings. it doesn’t display notes as low as the new theremini can go after the update.like c<.
these global settings for the app and setup settings for the theremini looks like a double feature to me.
anyway, just messed my library back to bad, by midi.
this thing needs definte a fw update. and the app needs that too. yes, i heard that they’re busy on this about enough times.
Guys,
Make sure this is not related to a transposition set on the patches. That will make your range appear to be different as it tries to take the transposition into account and if that transposition is not set to the octave it will appear like range is being set to strange notes.
Load the patch in the app to easily see the transposition.
If your transposition is set to 0, the global range will always appear what you think it is, otherwise that range might appear to change.
Rich