The Official Sequential/Oberheim Forum
SEQUENTIAL/DSI => Prophet => Prophet Rev2 => Topic started by: Razmo on August 04, 2018, 08:47:16 AM
-
Do any of you out there have problems with the new OS 1.1.4.9? ... it sounds like all of my B layers are transposed wrong, and even programs that use only layer A sounds wrong... I'm amazed that DSI did not hear this, it is on god damned every program!
-
Even after power cycle & calibration?
-
I made an erase of the calibration data... switched the REV2 off and on, did a globals reset and then a calibration of the oscillators and filters... now everything sounds fine...
I'm a little confused because at first, right after the OS update, I reset the globals, then did a calibration.. and that resulted in every program sounding wrong... after that I did another calibration, still without any luck...
This OS update and calibration/global reset procedure seems to be one big mystery still... why do I need to take out all plugs before the calibration, why do I need to reset the globals and recallibrate every time, when DSI state in the manual it's only needed maybe once in a lifetime... nothing of these procedures makes any sense to me really...
on top of that... the OS update stated that if I was on an OS higher than 1.1.3, I'd not even have to do these global resetting and calibration... still, I was on OS 1.1.4.5 when I upgraded to 1.1.4.9...
Would really be nice if some light was shed on this subject... I've asked about the calibration in another thread, but no one at DSI obviously want to discuss why these things are the way they are...
I can write them again:
1. Why is it necessary to take out the plugs before a calibration?
2. Why will the calibration always freeze if the REV2 has been on for some time?
3. Why do you constantly advice to do calibrations and global reset, when the manual state it's not needed for more than once in the REV2's lifetime?
4. Why is there even a calibration data erase function in the service mode? does REV2 store more than one calibration data set for different ambient temperatures?
Personally I'm a bit tired of the calibration freezing up... why is it doing this!?
-
:-\
I made an erase of the calibration data... switched the REV2 off and on, did a globals reset and then a calibration of the oscillators and filters... now everything sounds fine...
I'm a little confused because at first, right after the OS update, I reset the globals, then did a calibration.. and that resulted in every program sounding wrong... after that I did another calibration, still without any luck...
This OS update and calibration/global reset procedure seems to be one big mystery still... why do I need to take out all plugs before the calibration, why do I need to reset the globals and recallibrate every time, when DSI state in the manual it's only needed maybe once in a lifetime... nothing of these procedures makes any sense to me really...
on top of that... the OS update stated that if I was on an OS higher than 1.1.3, I'd not even have to do these global resetting and calibration... still, I was on OS 1.1.4.5 when I upgraded to 1.1.4.9...
Would really be nice if some light was shed on this subject... I've asked about the calibration in another thread, but no one at DSI obviously want to discuss why these things are the way they are...
I can write them again:
1. Why is it necessary to take out the plugs before a calibration?
2. Why will the calibration always freeze if the REV2 has been on for some time?
3. Why do you constantly advice to do calibrations and global reset, when the manual state it's not needed for more than once in the REV2's lifetime?
4. Why is there even a calibration data erase function in the service mode? does REV2 store more than one calibration data set for different ambient temperatures?
Personally I'm a bit tired of the calibration freezing up... why is it doing this!?
Hi Razmo. I am sorry that you have problems with freezing and patches sounding different. The rev 2 was my first hardware Synth and I own it since one year now. I did several calibrations and never got stuck and I never unplug any cables. I made about 60 patches which all sound fine after updating the OS. So no problems here. I hope you get some answers from dsi support which will help you to sort out your problems.
-
I am not the only one experiencing this freezing... It happened with two REV2s I've had, both bought completely new... Others have had the problem as well... The funny thing is that it allways happen after the machine has warmed up... And if I quickly turn power off and on and do the calibration again, then it run thru like nothing ever happened... That is why I am fearing it is a hardware related issue, and not a software issue.
-
I’ve not had the freezing issue when calibrating but I have seen a few people mention it on here. With this latest update I also had to calibrate the wheels, something I’d never had to do before. Neither of my wheels did anything on any patch until I re-calibrated them.
-
I’ve not had the freezing issue when calibrating but I have seen a few people mention it on here. With this latest update I also had to calibrate the wheels, something I’d never had to do before. Neither of my wheels did anything on any patch until I re-calibrated them.
But have you tried letting your REV2 stay on for about 30-60 minutes, and then do the calibration? ... it's very important that you do NOT turn off the REV2 before doing this... this is the weird thing about the issue... I can warm up my REV2 for an hour, then do a calibration, and it WILL freeze during the calibration... if I then make a quick switch off and then on and try calibrating again, it goes smoothly thru the calibration... at this point the REV2 is still warmed up... that is what really puzzles me...
This is not something that happens occationally... it's every time my REV2 has warmed up that this happens... it happened with the first REV2 I had too... others have reported the same issue...
It annoys me that some people have this, and others do not because this makes me fear that I have a faulty REV2 here... even though it's not likely that the same issue should be with two different REV2's bought with almost a year in between... I wonder if it's a certain batch that has this "feature"...
-
I’ve not had the freezing issue when calibrating but I have seen a few people mention it on here. With this latest update I also had to calibrate the wheels, something I’d never had to do before. Neither of my wheels did anything on any patch until I re-calibrated them.
But have you tried letting your REV2 stay on for about 30-60 minutes, and then do the calibration? ... it's very important that you do NOT turn off the REV2 before doing this... this is the weird thing about the issue... I can warm up my REV2 for an hour, then do a calibration, and it WILL freeze during the calibration... if I then make a quick switch off and then on and try calibrating again, it goes smoothly thru the calibration... at this point the REV2 is still warmed up... that is what really puzzles me...
This is not something that happens occationally... it's every time my REV2 has warmed up that this happens... it happened with the first REV2 I had too... others have reported the same issue...
It annoys me that some people have this, and others do not because this makes me fear that I have a faulty REV2 here... even though it's not likely that the same issue should be with two different REV2's bought with almost a year in between... I wonder if it's a certain batch that has this "feature"...
No I’ve not tried that. I’ll give it a go over the next few days and let you know. I assume that when it freezes it is OK to turn it off and on again?
-
I’ve not had the freezing issue when calibrating but I have seen a few people mention it on here. With this latest update I also had to calibrate the wheels, something I’d never had to do before. Neither of my wheels did anything on any patch until I re-calibrated them.
But have you tried letting your REV2 stay on for about 30-60 minutes, and then do the calibration? ... it's very important that you do NOT turn off the REV2 before doing this... this is the weird thing about the issue... I can warm up my REV2 for an hour, then do a calibration, and it WILL freeze during the calibration... if I then make a quick switch off and then on and try calibrating again, it goes smoothly thru the calibration... at this point the REV2 is still warmed up... that is what really puzzles me...
This is not something that happens occationally... it's every time my REV2 has warmed up that this happens... it happened with the first REV2 I had too... others have reported the same issue...
It annoys me that some people have this, and others do not because this makes me fear that I have a faulty REV2 here... even though it's not likely that the same issue should be with two different REV2's bought with almost a year in between... I wonder if it's a certain batch that has this "feature"...
No I’ve not tried that. I’ll give it a go over the next few days and let you know. I assume that when it freezes it is OK to turn it off and on again?
Certainly... that is what I do every time...
The reason I wait until it has warmed up is to be certain that the filters will be in tune when the device has warmed up... i never calibrate from a cold machine because then all programs I make where playing the resonant filter will sound out of tune... so my machine has to be warmed up before I calibrate it... therefore that is my usual procedure: Turn on... wait 30 minutes, calibrate (it freezes), then switch off and on, and calibrate again... then everything is fine...
it's just a weird way to have to do this...
-
Since all on the new features and bug corrections listed do not concern me (I simply play and directly record the REV2 and don't use MIDI with it, nor do I use the convoluted sequencer/arpeggiator), I'm going to skip this update. Especially if it introduces new bugs that make everything sound wrong...
In fact, I'm thinking more and more about selling the REV2 and get something better suited to my needs. I'm slowly realizing that I might never get used to those harsh sounding CEM filters.
-
I'm slowly realizing that I might never get used to those harsh sounding CEM filters.
Please try a little external EQ, it makes a world of difference, turn up the bass a little bit, cut the highs a little bit, and get the sound more balanced. It's not just the filters, it's the sum of the whole analog chain, it's too bright and too light in the low end, just fix that and it's like a totally new synth, with a classic analog sound.
-
Since all on the new features and bug corrections listed do not concern me (I simply play and directly record the REV2 and don't use MIDI with it, nor do I use the convoluted sequencer/arpeggiator), I'm going to skip this update. Especially if it introduces new bugs that make everything sound wrong...
In fact, I'm thinking more and more about selling the REV2 and get something better suited to my needs. I'm slowly realizing that I might never get used to those harsh sounding CEM filters.
As I wrote later, the sound got right, after I did the right order of actions with calibration after the OS update... It sounds fine now.
The thread is now about why these calibrations are needed, why I had to do them at all, when DSI stated that it was not necessary unless I was previously on OS 1.1.3... I was on 1.1.4.5, and had to do a calibration anyway, and other users experienced that even the wheels had to be calibrated... On top of this I am tired of not knowing why my REVs and other users experience consistent freezing in the calibration when the machine has warmed up... A subject DSI continue to ignore in here when asked, or try to talk around with unsatisfactory answers... I begin wondering if it is a hardware design problem, that DSI would rather not talk about, but I'll keep bringing this up until I get a satisfactory answer.
-
My Rev2 has been switched on for 20 minutes, so I'm going to leave it another 10 minutes and then try a calibration.
-
My Rev2 has been switched on for 20 minutes, so I'm going to leave it another 10 minutes and then try a calibration.
I appreciate that you're trying it out, so I can know if this is just my luck with the two REV2s I've had, or if this is a common issue.
-
My Rev2 has been switched on for 20 minutes, so I'm going to leave it another 10 minutes and then try a calibration.
I appreciate that you're trying it out, so I can know if this is just my luck with the two REV2s I've had, or if this is a common issue.
I'll also give it a try this afternoon and let you know.
-
It seems that something was edited in the OS thread since it was posted... and as far as I can see, it's the line in CMBD's comment bellow that state that you must do a global reset when updated because of new global parameters... that line was not there before... so the reason for the weird transposition of layer B and other stuff was probably because of this missing action.
-
My Rev2 has been switched on for 20 minutes, so I'm going to leave it another 10 minutes and then try a calibration.
I appreciate that you're trying it out, so I can know if this is just my luck with the two REV2s I've had, or if this is a common issue.
I'll also give it a try this afternoon and let you know.
Thank you! ... i appreciate it because if a lot of users do not have this issue, I'll have to write support and have them look into this.
-
As a sidenote: one of the things I liked seeing in the new OS update was that the Edit Buffer dumps had been fixed... I've tested it thoroughly, and can say that it now works as intended... Layers behave correctly, and i can now browse my presets in my SoundDiver editor without having to constantly press the "stack A+B" button after each and every dump to the edit buffer...
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
It does not matter if you delete or not... it happens no matter what I do, as long as the device has been on for some time. I guess I'll have to write support and have this sorted out... I'm wondering if there has been some early revisions of the main board that sport this problem... the two REV2s I bought both came from the same retailer, so it may be that it's a certain older batch that is the problem... but I feel that now is the time for DSI to figure this out...
Yes... i do think it's worth it trying to see if there is a common reason for this... it's annoying.
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
It does not matter if you delete or not... it happens no matter what I do, as long as the device has been on for some time. I guess I'll have to write support and have this sorted out... I'm wondering if there has been some early revisions of the main board that sport this problem... the two REV2s I bought both came from the same retailer, so it may be that it's a certain older batch that is the problem... but I feel that now is the time for DSI to figure this out...
Yes... i do think it's worth it trying to see if there is a common reason for this... it's annoying.
Calibration process got stuck after some seconds. I switched off the rev 2 and back on and everything runs smooth within I think 20 seconds. Never had a calibration this fast. I have the 8 voice rev2.
-
My calibration did run slower at the start but I left it and then it seemed to speed up.
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
It does not matter if you delete or not... it happens no matter what I do, as long as the device has been on for some time. I guess I'll have to write support and have this sorted out... I'm wondering if there has been some early revisions of the main board that sport this problem... the two REV2s I bought both came from the same retailer, so it may be that it's a certain older batch that is the problem... but I feel that now is the time for DSI to figure this out...
Yes... i do think it's worth it trying to see if there is a common reason for this... it's annoying.
Calibration process got stuck after some seconds. I switched off the rev 2 and back on and everything runs smooth within I think 20 seconds. Never had a calibration this fast. I have the 8 voice rev2.
Seems you got the same problem then... if it is a problem... I've written support about this now, and will let you know what they say about it...
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
It does not matter if you delete or not... it happens no matter what I do, as long as the device has been on for some time. I guess I'll have to write support and have this sorted out... I'm wondering if there has been some early revisions of the main board that sport this problem... the two REV2s I bought both came from the same retailer, so it may be that it's a certain older batch that is the problem... but I feel that now is the time for DSI to figure this out...
Yes... i do think it's worth it trying to see if there is a common reason for this... it's annoying.
Calibration process got stuck after some seconds. I switched off the rev 2 and back on and everything runs smooth within I think 20 seconds. Never had a calibration this fast. I have the 8 voice rev2.
Seems you got the same problem then... if it is a problem... I've written support about this now, and will let you know what they say about it...
Thank you for your effort!
-
My calibration did run slower at the start but I left it and then it seemed to speed up.
With a warmed up REV2, in my case, it usually run a few numbers fast... then at a certain number it stops for quite some time, then advances a bit... this continues for every voice until I reach a few voices in... then it simply stops... I've tried waiting several minutes, but it's just frozen... I've never let it stand for hours because I really do not believe that waiting that long is acceptable... especially not when a power cyling seems to fix it every time... something happens to either the software or the hardware when this power cycling is done that makes everything run smoothly... i have no idea why it works this way, so I'm looking forward to hear a more detailed explanation from DSI support...
-
Updated this evening and experienced the same strange transposing on patches - like everything got kicked down half an octave
Read through the thread and have had hangups in the calibration process previously, but not every time, so I figured I'd give this a try.
My Rev2 had been on for a couple hours when I updated. Calibration froze early on in OSC1. Powered off, powered back on. Calibration then ran without a hitch.
However, it didn't change the transposing behavior. Resetting the Global Parameters after that though seemed to do the trick.
16 voice Rev2 over here.
-
Now I will not pretend that I know how this automatic calibration really works, but my guess is that it samples the outputs of the Curtis chips somehow, and then measure stuff to be able to create these calibration data... my guess is that something is interfering with these measurements when the REV2 has been on for a while making it harder for the calibration to finish and do it's measurements... even if a calibration goes thru, it may even do this at vastly different speeds... this is why I suspect that it's a hardware thing, and not really a software thing... the software is the same every time, and it's relying on measurements to be within a certain range for a calibration to be accepted I guess, but for some reason the expected measurement never happen, and so it stand in a loop waiting for that measurement to come (which is obviously never do)...
This is speculation... but I have no other explanation for this behavior...
-
My calibration did run slower at the start but I left it and then it seemed to speed up.
With a warmed up REV2, in my case, it usually run a few numbers fast... then at a certain number it stops for quite some time, then advances a bit... this continues for every voice until I reach a few voices in... then it simply stops... I've tried waiting several minutes, but it's just frozen... I've never let it stand for hours because I really do not believe that waiting that long is acceptable... especially not when a power cyling seems to fix it every time... something happens to either the software or the hardware when this power cycling is done that makes everything run smoothly... i have no idea why it works this way, so I'm looking forward to hear a more detailed explanation from DSI support...
Yes you're right , it does need an explanation. When I said mine went slower it only appeared to stop for about 20 seconds maximum on the early part of it. I would say that several minutes is an indication that it has frozen.
It's a shame you can't change the title of this thread to attract more people who have the same problem to post :)
-
Updated this evening and experienced the same strange transposing on patches - like everything got kicked down half an octave
Read through the thread and have had hangups in the calibration process previously, but not every time, so I figured I'd give this a try.
My Rev2 had been on for a couple hours when I updated. Calibration froze early on in OSC1. Powered off, powered back on. Calibration then ran without a hitch.
However, it didn't change the transposing behavior. Resetting the Global Parameters after that though seemed to do the trick.
16 voice Rev2 over here.
Seems this freezing is quite widespread... you can follow this thread as I'll post what support tells me about it, unless they decide to participate in this thread directly... I feel there is a need for users to know about this... if it can be fixed, or if we simply have to live with the "power cycle trick" every time we calibrate...
I see users which run into problems like this from time to time... their machines hanging, or behaving strange after an OS update because of all these diffuse things you have to do after an update... resetting globals, calibrating osc/filter, calibrating wheels... and some accordingly do not have to if they are on a higher OS prior to the update, other do, and again, then people who did not have to do these calibrations, have to do them anyway (like I had to) and have to find out by trial and error.
For me it's a chaotic procedure every time a new OS arrives... having to do calibration, global reset, wheels reset and even enter service mode to erase calibration data as well sometimes, before i get a working machine again... the order of the procedures are not really that clear, and on top of that I have to take power cycling into account to make the calibration...
I don't understand why we have to do a reset of the globals manually.. if DSI know that a reset is neede, why don't they just do this reset when the OS has been updated!? ... if a calibration is also needed, why not let it do this automatically too, when the globals had been reset!? ... that puzzles me a bit sometimes.
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
There have already been a thread about the calibration freeze... but DSI did not give any answers that solve anything or makes you wiser on what is going on... but when I get a response from DSI via support, I'll probably just start a new thread about the subject, if I feel it's necessary...
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
There have already been a thread about the calibration freeze... but DSI did not give any answers that solve anything or makes you wiser on what is going on... but when I get a response from DSI via support, I'll probably just start a new thread about the subject, if I feel it's necessary...
Ok cheers and good luck. I have to admit that I find the update processes a bit daunting as I'm never completely sure what I should be doing! I have the SoundTower software so I always do a backup via that before updating. I have tried the dump option but it's never completed properly. I even had problems loading a bank to the Rev2 that I purchased from GEOSynths via the SoundTower software - it got so far (around about preset 100) and then stopped. I then had to transfer the rest over to the Rev2 one at a time.
I have the Pro2 as well and that lost all my Cue/Play List settings when I did the last update. I know I should have done a backup but I didn't expect that to happen!
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
There have already been a thread about the calibration freeze... but DSI did not give any answers that solve anything or makes you wiser on what is going on... but when I get a response from DSI via support, I'll probably just start a new thread about the subject, if I feel it's necessary...
Ok cheers and good luck. I have to admit that I find the update processes a bit daunting as I'm never completely sure what I should be doing! I have the SoundTower software so I always do a backup via that before updating. I have tried the dump option but it's never completed properly. I even had problems loading a bank to the Rev2 that I purchased from GEOSynths via the SoundTower software - it got so far (around about preset 100) and then stopped. I then had to transfer the rest over to the Rev2 one at a time.
I have the Pro2 as well and that lost all my Cue/Play List settings when I did the last update. I know I should have done a backup but I didn't expect that to happen!
Dodgy MIDI interfaces, dodgy MIDI dump software... there can be many culprits... DSI advice on using MIDIOX, but that one does not work for me, and obviously needs arcane settings before working... I found that sending from Cakewalk Sonar works every time, no matter if I'm on USB or MIDI DIN... both for OS updates and dumping programs and banks.
Most of my bank management I handle with my SoundDiver editor though, and that works like a dream, and is EXTREMELY FAST when using USB... I can read all eight banks into the editor in less than 3 seconds, and write them almost just as fast... so when it comes to MIDI communication, it's 99% likely that your problem is with either your MIDI DIN interface, or even more likely; the software you use to do the transfers.
-
Ok my calibration went through without problems after leaving it to warm up for just over 30 minutes. I have the 16 voice keyboard version which was 16 voice out of the box. All I had connected to it was the left and right out which go to my Yamaha mixer and that was turned on.
Is it worth us trying to see if there's a common factor between all those units that freeze in this situation?
Edit - I didn't delete anything before running the calibration, wasn't sure if I was supposed to do that or not? I've never deleted any previous calibration information.
There have already been a thread about the calibration freeze... but DSI did not give any answers that solve anything or makes you wiser on what is going on... but when I get a response from DSI via support, I'll probably just start a new thread about the subject, if I feel it's necessary...
Ok cheers and good luck. I have to admit that I find the update processes a bit daunting as I'm never completely sure what I should be doing! I have the SoundTower software so I always do a backup via that before updating. I have tried the dump option but it's never completed properly. I even had problems loading a bank to the Rev2 that I purchased from GEOSynths via the SoundTower software - it got so far (around about preset 100) and then stopped. I then had to transfer the rest over to the Rev2 one at a time.
I have the Pro2 as well and that lost all my Cue/Play List settings when I did the last update. I know I should have done a backup but I didn't expect that to happen!
Dodgy MIDI interfaces, dodgy MIDI dump software... there can be many culprits... DSI advice on using MIDIOX, but that one does not work for me, and obviously needs arcane settings before working... I found that sending from Cakewalk Sonar works every time, no matter if I'm on USB or MIDI DIN... both for OS updates and dumping programs and banks.
Most of my bank management I handle with my SoundDiver editor though, and that works like a dream, and is EXTREMELY FAST when using USB... I can read all eight banks into the editor in less than 3 seconds, and write them almost just as fast... so when it comes to MIDI communication, it's 99% likely that your problem is with either your MIDI DIN interface, or even more likely; the software you use to do the transfers.
Thanks I’ll do some further investigation. I’m using USB rather than a midi connection but I am using a USB extension cable so I’ll try different cables and a different port on my PC. I’ve had problems with MIDIOX as well so might investigate other software.
-
Would really be nice if some light was shed on this subject... I've asked about the calibration in another thread, but no one at DSI obviously want to discuss why these things are the way they are...
I can write them again:
1. Why is it necessary to take out the plugs before a calibration?
2. Why will the calibration always freeze if the REV2 has been on for some time?
3. Why do you constantly advice to do calibrations and global reset, when the manual state it's not needed for more than once in the REV2's lifetime?
4. Why is there even a calibration data erase function in the service mode? does REV2 store more than one calibration data set for different ambient temperatures?
Personally I'm a bit tired of the calibration freezing up... why is it doing this!?
Hey Razmo
I have a theory for number 1.
I had one occasion last year when running the calibration routine that my Rev2 blasted out tones at full volume. It was really loud! I only noticed it the one time. After that I have almost always turned off my line mixer to save my monitors and ears when calibrating. However there have been a few times when I forgot to turn it off and there was no signal output during tuning. Perhaps they say to discount output cables as a precaution against a rare bug that can blast the output?
Has anyone else had an occasion where their Rev2 output tones during calibration?
I can also add my voice to the chorus of people that sometime have the calibration process freeze and have to power cycle.
Also your list is shrinking after my search of the forum found the answer to deleting the cal data from the tabletop Rev2 ;)
Hopefully DSI will eventually answer your remaining questions though I know some have been bouncing around for a long time.
Cheers
-
I suspect that the calibration routine is first using the previous data and checking it for accuracy, in order to save time, and only if the result is not satisfactory then it proceeds to calculate a new value with the old data as a starting point. But it might run into a dead end when the new calculation results are always worse than the previously saved data, and thus the calibration gets stuck ?
Just speculating, since no one from DSI is willing to talk about it.
BTW, my REV2 often got stuck in calibration right after a firmware update, no matter if it was cold or warmed-up.
I couldn't tell you this time, since I won't be updating it. It works fine enough as it is with 1.1.4.5.
One question: is it possible to downgrade to a previous O.S. version from a higher one ? I still have all the files, but I'm not sure that the REV2 would go into firmware update mode upon receiving older files than the one currently in it (just in case I decide to go ahead with 1.1.4.9 and want to revert back to the previous one) ?
-
@Razmo Tried the calibration after having my rev2 on for about an hour. It did not freeze. I'm on 1.1.4.9 eight voise version.
I'm experience trouble with the new arp beat sync settings. Will open a new thread about this.
-
@Razmo Tried the calibration after having my rev2 on for about an hour. It did not freeze. I'm on 1.1.4.9 eight voise version.
I'm experience trouble with the new arp beat sync settings. Will open a new thread about this.
And did you shut off the REV2 before you made the calibration? ... this is important information because if you did, it would pass thru... mine does... it only happens if you turn on the REV2, wait for about half an hour, and then (without a power cycle) start the calibration...
-
I suspect that the calibration routine is first using the previous data and checking it for accuracy, in order to save time, and only if the result is not satisfactory then it proceeds to calculate a new value with the old data as a starting point. But it might run into a dead end when the new calculation results are always worse than the previously saved data, and thus the calibration gets stuck ?
Just speculating, since no one from DSI is willing to talk about it.
BTW, my REV2 often got stuck in calibration right after a firmware update, no matter if it was cold or warmed-up.
I couldn't tell you this time, since I won't be updating it. It works fine enough as it is with 1.1.4.5.
One question: is it possible to downgrade to a previous O.S. version from a higher one ? I still have all the files, but I'm not sure that the REV2 would go into firmware update mode upon receiving older files than the one currently in it (just in case I decide to go ahead with 1.1.4.9 and want to revert back to the previous one) ?
Still it does not really say anything about why a simple quick power down and up makes everything work smoothly... I hardly believe that the chips can heat down in just 5-10 seconds which it takes to power cycle the REV2... I don't know what could cause this, this is why I need DSI's explanation of this... guessing will not get us anywhere near an explanation... i need to know, if I have a defect unit, if I have got an earlier board revision that does this or something else that might be the reason, so that I know if I have the rights to have another machine regarding warranty... but with so many experiencing this, I believe more in a board revision fault... a batch of bad devices or similar, instead of my unit alone being the reason for this... I've had two REV2's with the exact same behavior.
-
And did you shut off the REV2 before you made the calibration? ... this is important information because if you did, it would pass thru... mine does... it only happens if you turn on the REV2, wait for about half an hour, and then (without a power cycle) start the calibration...
No I did not shut off the rev2 before the calibration.
I just did a new calibration again. The rev 2 has been on since my last response some hours ago.Same result. I have only experienced one freeze before a few months ago after buying the synth used.
-
I suspect that the calibration routine is first using the previous data and checking it for accuracy, in order to save time, and only if the result is not satisfactory then it proceeds to calculate a new value with the old data as a starting point. But it might run into a dead end when the new calculation results are always worse than the previously saved data, and thus the calibration gets stuck ?
Just speculating, since no one from DSI is willing to talk about it.
BTW, my REV2 often got stuck in calibration right after a firmware update, no matter if it was cold or warmed-up.
I couldn't tell you this time, since I won't be updating it. It works fine enough as it is with 1.1.4.5.
One question: is it possible to downgrade to a previous O.S. version from a higher one ? I still have all the files, but I'm not sure that the REV2 would go into firmware update mode upon receiving older files than the one currently in it (just in case I decide to go ahead with 1.1.4.9 and want to revert back to the previous one) ?
Yes you can back level the firmware, I've just done mine from 1.1.4.9 back to 1.14.5 (until it's clear what bugs there are following the latetest 'beta' update).
-
I had one occasion last year when running the calibration routine that my Rev2 blasted out tones at full volume. It was really loud! I only noticed it the one time. After that I have almost always turned off my line mixer to save my monitors and ears when calibrating. However there have been a few times when I forgot to turn it off and there was no signal output during tuning. Perhaps they say to discount output cables as a precaution against a rare bug that can blast the output?
Has anyone else had an occasion where their Rev2 output tones during calibration?
I ask again. Has anyone else experienced audio output during calibration?
-
I had one occasion last year when running the calibration routine that my Rev2 blasted out tones at full volume. It was really loud! I only noticed it the one time. After that I have almost always turned off my line mixer to save my monitors and ears when calibrating. However there have been a few times when I forgot to turn it off and there was no signal output during tuning. Perhaps they say to discount output cables as a precaution against a rare bug that can blast the output?
Has anyone else had an occasion where their Rev2 output tones during calibration?
No I haven't noticed that. I will make sure I have my mixer and amp turned on for the next few I do.
I ask again. Has anyone else experienced audio output during calibration?
Somehow my original reply went missing! I haven't heard any sound come out when doing a calibration but I tend to have headphones connected to my mixer and wouldn't be wearing them whilst doing a calibration. I will keep an ear out for this whenever I do a calibration in future.
-
I had one occasion last year when running the calibration routine that my Rev2 blasted out tones at full volume. It was really loud! I only noticed it the one time. After that I have almost always turned off my line mixer to save my monitors and ears when calibrating. However there have been a few times when I forgot to turn it off and there was no signal output during tuning. Perhaps they say to discount output cables as a precaution against a rare bug that can blast the output?
Has anyone else had an occasion where their Rev2 output tones during calibration?
I ask again. Has anyone else experienced audio output during calibration?
I did, I'm ( you are ) not the only one. ;)
-
Thanks! Good to know it’s not an isolated incident. This could indeed explain why DSI recommends disconnecting outputs during calibration. It is strange that it is inconsistent.
-
I always turn the volume to zero but I'll have a look at this the next time I do calibration.
-
I had one occasion last year when running the calibration routine that my Rev2 blasted out tones at full volume. It was really loud! I only noticed it the one time. After that I have almost always turned off my line mixer to save my monitors and ears when calibrating. However there have been a few times when I forgot to turn it off and there was no signal output during tuning. Perhaps they say to discount output cables as a precaution against a rare bug that can blast the output?
Has anyone else had an occasion where their Rev2 output tones during calibration?
I ask again. Has anyone else experienced audio output during calibration?
I don’t yet own any dsi gear but have had both behaviours from other synths: Minitaur outputs audio on calibration whereas Subsequent is silent.
-
I had one occasion last year when running the calibration routine that my Rev2 blasted out tones at full volume. It was really loud! I only noticed it the one time. After that I have almost always turned off my line mixer to save my monitors and ears when calibrating. However there have been a few times when I forgot to turn it off and there was no signal output during tuning. Perhaps they say to discount output cables as a precaution against a rare bug that can blast the output?
Has anyone else had an occasion where their Rev2 output tones during calibration?
I ask again. Has anyone else experienced audio output during calibration?
No... I've never experienced this, but I know that other synths like the MOOGs make these pitches while calibrating... they do not stop the output obviously... somehow the REV2 probably does that, but must have failed in doing so in your case
-
Thanks! Good to know it’s not an isolated incident. This could indeed explain why DSI recommends disconnecting outputs during calibration. It is strange that it is inconsistent.
it MAY be the reason yes... but it would be nice to know from DSI themselves, if that is indeed the case because if there is more to it, that may make the calibration bad if something is plugged in, then it would be nice to know... if it's only a matter of an accidental outburst, I'd rather turn down the main volume pot, instead of having to take out all 7 plugs i have connected to my REV2 :)
Even though DSI state that calibration is rarely needed, they ask you to do this on almost every OS update anyway, and i calibrate rather often when the ambient temperature changes, otherwise the filters are not in tune, so I do this calibration so often, that I'd really hate to have to take out 7 plugs and plug them back in each and every time, if i can avoid it... therefore i want to know in detail, WHY this unplugging is needed... if it's just about the volume, it would be a hell of a lot quicker for me to just turn down the volume... that is as easy to forget as unplugging the cables... really.
-
Thanks! Good to know it’s not an isolated incident. This could indeed explain why DSI recommends disconnecting outputs during calibration. It is strange that it is inconsistent.
it MAY be the reason yes... but it would be nice to know from DSI themselves, if that is indeed the case because if there is more to it, that may make the calibration bad if something is plugged in, then it would be nice to know... if it's only a matter of an accidental outburst, I'd rather turn down the main volume pot, instead of having to take out all 7 plugs i have connected to my REV2 :)
Even though DSI state that calibration is rarely needed, they ask you to do this on almost every OS update anyway, and i calibrate rather often when the ambient temperature changes, otherwise the filters are not in tune, so I do this calibration so often, that I'd really hate to have to take out 7 plugs and plug them back in each and every time, if i can avoid it... therefore i want to know in detail, WHY this unplugging is needed... if it's just about the volume, it would be a hell of a lot quicker for me to just turn down the volume... that is as easy to forget as unplugging the cables... really.
I have calibrated a few times and got stuck every first time. Restart and it finishes fairly fast. I find this calibrating thing very vague.
-
Thanks! Good to know it’s not an isolated incident. This could indeed explain why DSI recommends disconnecting outputs during calibration. It is strange that it is inconsistent.
it MAY be the reason yes... but it would be nice to know from DSI themselves, if that is indeed the case because if there is more to it, that may make the calibration bad if something is plugged in, then it would be nice to know... if it's only a matter of an accidental outburst, I'd rather turn down the main volume pot, instead of having to take out all 7 plugs i have connected to my REV2 :)
Even though DSI state that calibration is rarely needed, they ask you to do this on almost every OS update anyway, and i calibrate rather often when the ambient temperature changes, otherwise the filters are not in tune, so I do this calibration so often, that I'd really hate to have to take out 7 plugs and plug them back in each and every time, if i can avoid it... therefore i want to know in detail, WHY this unplugging is needed... if it's just about the volume, it would be a hell of a lot quicker for me to just turn down the volume... that is as easy to forget as unplugging the cables... really.
I have calibrated a few times and got stuck every first time. Restart and it finishes fairly fast. I find this calibrating thing very vague.
Exactly... and it's worrying, that other do not experience this at all...
-
Thanks! Good to know it’s not an isolated incident. This could indeed explain why DSI recommends disconnecting outputs during calibration. It is strange that it is inconsistent.
it MAY be the reason yes... but it would be nice to know from DSI themselves, if that is indeed the case because if there is more to it, that may make the calibration bad if something is plugged in, then it would be nice to know... if it's only a matter of an accidental outburst, I'd rather turn down the main volume pot, instead of having to take out all 7 plugs i have connected to my REV2 :)
Even though DSI state that calibration is rarely needed, they ask you to do this on almost every OS update anyway, and i calibrate rather often when the ambient temperature changes, otherwise the filters are not in tune, so I do this calibration so often, that I'd really hate to have to take out 7 plugs and plug them back in each and every time, if i can avoid it... therefore i want to know in detail, WHY this unplugging is needed... if it's just about the volume, it would be a hell of a lot quicker for me to just turn down the volume... that is as easy to forget as unplugging the cables... really.
Totally agree!
-
I have encountered something that will actually let my REV2 run thru the calibration, even if it has been on for a long time... it still pauses at some points for 10-20 seconds though, but it eventually runs thru... this happens if I instead of power cycling the REV2, hit the transpose buttons + global, and choose to erase the calibration data, and then do the calibration routine after that...
I do not know what to make of it, but i just thought I'd say it here, so that others can use that method if they so choose.
-
I made another strange discovery... reason is, that after erasing the calibration data and calibrating, the calibration data was completely off... everything sounded wacky... so I decided to just switch the REV2 off and on, and do the calibration again... while i did this I watched the flow of the numbers in the calibration display, and the first few voices run thru really fast... but it soon dawned on me, that for each voice it got thru, the passing went slower and slower... the last af the voices being quite some time about finishing...
It seems that for the calibration to slow down does not require that the REV2 is on for very long before it begins slowing down... this is really weird...
Tomorrow, when the REV2 has cooled down completely, I'll be making another calibration from a completely cold machine and see if all voices calibrate much faster... this time it went thru after a power cycle, but the machine was still warm... so I'm curious as to how the calibration goes from a cold machine... I'll know tomorrow...
-
Please try a little external EQ, it makes a world of difference, turn up the bass a little bit, cut the highs a little bit, and get the sound more balanced.
This is a useful suggestion. Got any good, mid-range recommendations?
Been looking for a dedicated EQ specifically for the Rev2, but digging through threads on the matter leaves the head spinning somewhat, and it’s never Rev2 specific.
I use an old Boss Bass GE-7B on my Prophet 600, which has been fine, but there doesn’t seem to be much in the way of stereo (in anyway) EQ pedals, which I’d prefer as I could keep it right on top of the Rev. I could succumb to a rack option if necessary.
Curious as to your recommendations of EQs that are working well with your Rev2.
-
Do you all do a calibration reset before to calibrate ? I can't remenber to have seen this before, and if it's necessary.
-
Do you all do a calibration reset before to calibrate ? I can't remenber to have seen this before, and if it's necessary.
I’ve never done a calibration reset.
-
There is no calibration reset... there is a calibration data erase function in the service mode... for some reason when this is erased first, the calibration routine in the global menu runs faster... especially if I have my REV2 warmed up when i do it... but i got a completely wonky calibration yesterday when i did this... for some reason a power cycling is needed in my case...
I also realized, that if i powercycle quickly (less than 1sek), then the display still has lots of the details it had before power cycling, but this also result in a slower calibration afterwards... if i powercycle, but wait 20sec before turning it on again, then the display show "noise", and the calibration goes a lot faster thru...
I'm not sure what is happening, but I'm speculating about this issue being because of either some capacitors that may interfere with the calibration, or maybe it has to do with what sound you had as the current program when you initialize the calibration...
I also noticed that the first voices that it calibrates goes a lot faster then the voices following them... it's like it slow down over the course of the calibration...
I've not gotten any info from support on this yet, except a first reply that did not give me any answers or solved anything... but I'll let you know if/when I know more...
-
I also realized, that if i powercycle quickly (less than 1sek), then the display still has lots of the details it had before power cycling, but this also result in a slower calibration afterwards... if i powercycle, but wait 20sec before turning it on again, then the display show "noise", and the calibration goes a lot faster thru...
I can confirm this behavior. My display has always shown noise on either side of a power cycle. Initially, it worried me, but it hasn’t seemed to cause
any issues.
Also, like you, if powercycling quickly, my display will retain all the current info for a tick or 2 before going to noise and shutting down.
Always thought it was just normal behavior.
-
I think a new bug: I can't enter init patch from the global menu any more. Only the manip of transpose buttons is working.
Is-it the same with you ?
PS: ::) i did the mistake to do a calibration (warm one) with all jacks plug out, without problems but than had some serious voices issues when tried the synth...; Since I did a new one in same conditions but with usb unpluged too, even if I don't think it's important, and things seem to be ok now.
-
I’m late to the party.
Read through the thread and want to try and see if the model i have has the same behavior.
Questions:
Does this calibration hang up happen on the latest beta only or did it happen on older firmware? Ive not updated to the newest beta and would be willing to test things since im old older firmware.
To those having issues, it would be helpful to post your serial number to see how far spread it could be and what model from the factory. Ive a 16 voice from the factory.
So I need to power up the unit and wait at least an hour before calibrating?
Ive calibrated before after updating and recall the calibration happening with no issues.
Al
-
The calibration hang up has happened to me on a few different firmwares since purchase. I got mine used though, not direct from DSI.
I can post my serial later this evening.
-
To note, you should not have to calibrate the synth multiple times. We had changed some of the calibration procedures to tighten voice to voice PW on recent BETA OS versions. Due to the change in the calibration, it was advised that after updating the OS, the calibration data should be cleared and then instrument recalibrated thereafter.
To clear the calibration data from the synth, hold both TRANSPOSE UP and DOWN buttons and press the GLOBAL button. Navigate to the CLEAR CALIBRATION parameter and press the WRITE button.
Power cycle the synth and then perform the oscillator/filter calibration routine. Again, you should only need to calibrate a single time.
I hope this clears things up!
-
Also, please remember to reset the global parameter preferences after loading the most recent OS as new globals have been added.