Currently Being ModeratedApr 22, 2011 3:29 PM (in response to Cleuvenot)Re: RE: bug report, PitchGlide decimal values btw [-1;0]
I can confirm that I can reproduce this as well with firmware 1.20.
This is an exising bug that has been logged. We hope to see this fixed in a future update.
Currently Being ModeratedApr 23, 2011 5:35 PM (in response to Line6Hugo)Re: RE: bug report, PitchGlide decimal values btw [-1;0]
Thanks for your interest.
Will you some day publish a really detailed manual with the detailed meaning of the effect parameters? It would be very welcome.
Currently Being ModeratedAug 23, 2012 4:25 AM (in response to Line6Hugo)Re: RE: bug report, PitchGlide decimal values btw [-1;0]
This bug had been announced as fixed i the podHD500 v2 firmware. However, it is still NOT FIXED in PodHD300 v2 firmware!
I was very happy to get the amazing free HD300 v2 firmware and I thank line6 for this great work. I can understand, too, that this little bug is not a priority for line6 teams. But after so much time that it has been reported and having waited so long for the announced podHD300 v2, this oversight is quite... surprising.
Here is a copy of what is published for the pdHD500 v2 firmware, which let understand an reference to the above mentionned bug:
- Limited resolution for Pitch Glide Min/Max Settings in Controller Assign page – Fixed
Currently Being ModeratedApr 25, 2011 9:49 AM (in response to Cleuvenot)RE: bug report, PitchGlide decimal values btw [-1;0]
In regards to new documentation, please use the Features Suggestion portal to alert our product development team directly of your request (it's actually more effective than posting your questions here, since the requests go directly to the Dev Team): http://line6.com/company/contact/productfeedback/
Currently Being ModeratedMay 21, 2011 6:38 AM (in response to Kneehow)not fixed in firmware 1.31 Re: RE: bug report, PitchGlide decimal values btw [-1;0]
This bug affecting pitch glide decimal values between -1 and 0 has, unfortunately, not been fixed in firmware 1.31...
Currently Being ModeratedApr 30, 2012 2:30 PM (in response to Cleuvenot)Re: not fixed in firmware 1.31 Re: RE: bug report, PitchGlide decimal values btw [-1;0]
Fixed in firmware 2?
I am glad to see (and grateful to line6 staff) that, according to what is announced, this above mentioned bug seems to have been fixed in the firmware 2.
However, the satisfaction to see that line 6 takes into account his customer's remarks is a bit diluted by the strange feeling to be considered, as a medium budget podHD-only-300 owner, a kind of second zone client.
Last update only applied to pod HD bean, pro and 500. And after waiting for more than 2 months a "soon available" v2 update, we, little pod HD 300/400 owners, are still waiting. Indeed, the finally downloadable update was, once more, only for top-segment hardware. Consequently, the "soon available" remains a "soon available".
Let’s be fair: free update; new extensions and bass amp and mic preamp modeling! Fantastic and generous! A wonderful relation between passionate developers and passionate clients. But why do you waste that great feeling with such an unfair commercial hierarchy between your customers?
Best regards and, anyway, thanks for your work.