Never mind.....
If the the issue was fixed in RM 3.7.2 then I just need to update. I'll try it today.
Never mind.....
If the the issue was fixed in RM 3.7.2 then I just need to update. I'll try it today.
Now I am confused. What am I waiting a fix for?
I contacted support a few weeks ago and Burkhard replied "We have no specific date for a fix."
|
Then later said "There is no such issue."
|
Can you explain?
it wasn´t my intention to offend you.
I just wanted to say that a tuner is not the solution for a tuned guitar.
A bit off topic, but maybe not everyone knows it.
I'm not offended at all
So what your saying is it took you 45 years to learn to use your ears?
I learned 60 years ago how to adjust the intonation of the guitar (the best method is an oscilloscope, imo). I also learned about sweetened tunings for pedal steel. I quickly learned that investment in quality instruments is worth the expense. A guitar that constantly goes out of tune doesn't stay in my collection for long.
I never said anything about tuning every string with a tuner, don't try to put words in my mouth. Like you I usually tune one string (A) with a tuner and the rest to that string. IMO having a tuner in RM might be nice but not necessary.
"If you think you can't you probably won't."_ Ed Dixon
Are you arguing against tuners ? How do you feel about tuning forks and pitch pipes?
First of all, if we could have an responsive accurate tuner in Rig Manager it would be a good thing welcomed by many.
Having said that, I started in my first working band in 1964. The first thing any guitarist MUST lean is how to tune the instrument. We only had pitch pipes, harmonicas, pianos/keyboards or another guitar to tune to back in those days. Any musician should train his/her ear to instantly recognize when their instrument is out of tune and be able to correct it quickly. These days I refuse to work with anybody who can't.
Please read the chapters about Profiling in the manual. The process in the editor is not different, so there is no extra documentation. This thread has been open for a week, and nobody has chimed in so far. I guess that says something too.
I read the chapters about Profiling in the manual before I attempted profiling in the first place. I have had at least 3 other threads about this issue and others have chimed in, including your man Arne saying there would be a fix. If the process is simple and straightforward,, why are we waiting for a "fix"? Please stop trying to put the blame on me...
Please wait for the fix, and if you have questions then, please don't hesitate to ask. The process should be easy enough to understand without extra documentation.
Respectfully; "should be easy" means nothing to me. "same as on the hardware" means nothing to me, I have never profiled on the hardware. If the process had been documented the problem would have been discovered from the beginning and we wouldn't be waiting on a fix. How hard could it be to document the process. How much work has this caused Kemper by having to respond to these threads? Do yourself a favor and write the documentation for the Profiling assistant in RM then when the next person asks, all you have to do is refer to a page number instead of providing answers like "same as on the hardware".
waiting for the fix ...
I have tried to explain my issues (emphasis on "my") using the Profiling assistant in RM but I don't seem to be able to get my point across. Other users have confirmed my findings even Arne said it would be fixed in the next update.
I have made a video that may demonstrate my confusion and explain why I think documentation of the process is needed. It is not as clear to some of us new to profiling as it is to the Kemper support team.
Can you please tell me where I can find the official documentation for the profiling assistant in Rig Manager? I could not find it in in RM manual including the new Beta manual.
I am also waiting to see what problems still exist with OS 11 (I still on 10.2.3), especially problems with Rack units.
they also make a smaller version for pedal boards...
From my perspective the Kemper OS 11 is NOT an update, it's a long running Beta Test. I also think it does not reflect well on Kemper. I see many people on YouTube complaining about Kemper over the paid upgrades (which can ONLY be applied by installing the beta test version of the software and firmware).
That doesn't make my Rack unit obsolete but it did kill my enthusiasm for the company and any future products.
Just my $.02...
The Behringer P1 is on sale now for under $10.00: https://www.sweetwater.com/store/detail/P…cB&gclsrc=aw.ds
A P16m (a single one) costs $189: https://www.sweetwater.com/store/detail/P…uction_products
Both of these are excellent ways to get a great monitor mix on the cheap with an XR18.
I've had the P16 system in my studio for over 7 years never seen a P1. Does it monitor only one channel?
I use the Behringer P16 monitoring system over the Ultranet port on both the XR18 and X32 digital mixers. I have 4 of them in my studio. Each allows a different 16 channel mix for each musician. Not the cheapest solution but but they work with headphones, powered speakers and IEMs and let each musician dial in their own mix right there in front of them or if using wireless IEMs the P16 doesn't need to be on stage. no app needed. I have never compared the cost to other solutions because I never needed another solution.
This has been discussed for as long as I have been on this forum and I still don't get it.
1. If you are creating a rig and select a preset (to apply to an effect) make a note in the Comments field in RM or write it down elsewhere. I use the metadata in On Song to remember things like which drum machine I used, the drum machine preset, the bpm, the Kemper or TMP rig preset and any other info that will be useful later on. It could also be all the parameter settings of an effect but once that is baked into a rig I don't need that info anymore in On Song.
2. If you are trying to reverse engineer someone else's profile and don't know what preset is used you will have to use your ears and dial in the parameters for the effect. Then save it as your own preset.