Share some tips, please. Which settings are you tweaking?
Posts by piotrmaj
-
-
Cześć, trochę sprzętu nagromadziłeś
- Też jestem bardzo zadowolony z profili SinMixa, który nawet ostatnio pojawił się na naszym wirtualnym spotkaniu. W domu gram wyłącznie na monitorach studyjnych, nie HS8, tylko Adam AX7 i jestem bardzo zadowolony, trzeba tylko przyciąć górę w okolicach 7 - 8kHz - bo inaczej za bardzo wszystko bzyczy). -
I don't. Another audio quality myth is that 24-bit audio will unlock some sort of audiophile nirvana because it’s that much more data-dense, but in terms of perceptual audio, any improvement will be lost on human ears. Capturing more data per sample does have benefits for dynamic range, but the benefits are pretty much exclusively in the domain of recording not human listening.
I agree: 16-bit resolution gives 65,536 values to represent samples. 24-bit resolution gives 16,777,216 possible values. This is huge improvement and since most (probably all) plugins are using floating point arithmetic, which has limited precision - it makes computation more precise if you start doing it from more precise values. You can export final product to 16-bit and you probably would not hear much difference, but recording and processing in 24-bit depth is a must, in my opinion.
-
no, pre/post is for looper placement (you usually want post or output, to be able to change sound for solo vs. rhythm). There is Looper Volume knob (on Stage it is page 4 of System Settings). Maybe you have looper set to Pre - in this case when you morph the sound would be changed to louder. Make sure looper is Post and adjust volume.
-
In system settings you can adjust looper volume.
-
Przypomnienie o piątkowym spotkaniu. Szczegóły powyżej.
-
But I think mathematically it doesn't make much sense to go beyond 48kHz for most of digital audio path (Nyquist) and as far as I researched the topic (I'm not a pro, just curious hobbyist) high end plugins, when needed to avoid digital artifacts (aliasing) oversample internally by a lot. Storing projects in 96K just takes more space and brings nothing at all to quality of audio, because all frequencies in human range can be perfectly represented in 48kHz (even 44.1kHz for vast majority of people on this planet). So maybe people are doing this "just in case", but I think they would have hard time to prove scientifically that it makes sense to go beyond 48kHz. It just uses more CPU and disk when less would do. It is mathematics - hard to argue with.
-
Just like you can send many analog signals over a single wire (look at cable TV in your house - it sends hundreds of channels simultaneously over the very same coax cable at the same time + internet) you can do exactly the same in digital domain and to be honest SPDIF is the crappiest protocol of them all - just 2 channels using short, quite expensive cable! For example Dante protocol (audio over ethernet) can transfer 1024 channels on a single CAT-5 cable, long distance. But I guess it is off-topic already by a few miles
-
RCA cables on have a single center conductor with a grounding sheath around it. I suppose you can get a stereo signal by the center conductor carrying the Left and the grounding shield carries the Right channel but you loose any shielding.
SPDIF is digital protocol. Kemper is banging bits out to the wire. There is no left and right channel as in case of analog cables. Both channels are traveling on the same wire in a "frame" (frame is some defined structure of digital words) along with some other information, like clock. And it doesn't need to be left/right - can be wet/dry - Kemper is flexible here.
-
You will have quite an upgrade! Have fun with new effects (delays and reverbs are awesome).
-
For Downloads page, Older Software section:
If your classical PROFILER model is even running an OS older than 1.8.2, you need to take three steps to get current: first install 1.8.2, then 7.3.2, then current OS.
-
Pierwsze spotkanie mamy za sobą - a że było bardzo sympatycznie to organizujemy kolejne.
23 kwietnia o 20:00 na Zoomie (link podeślę w przyszłym tygodniu)
Data dość odległa, a to dlatego, żeby dać szansę użytkownikom, który wpadają tu sporadycznie.
-
I suspect it is about special characters in folder names and length of folder names (and depth):
For example:
Kemper Wah-settings List as Presets 2021-03-18/USB-stick Transfer->/Shared/Effect Presets/Wah/Wah Wah/WW Dunlop JC95 1 - 2016-06-26 12-47-56.kpreset
contains character >, which is suspicious and maybe Windows tools are struggling with it. On Mac everything is good.
-
Yeah, latest RM gives me troubles as well. I sent Marc link to the video + logs: Ticket ##KA00207950. Hope this will be helpful for solving this issue.
-
yup, my experience as well. MIDI chase is not an option with Kemper (it is musical DDoS
) which is a shame because it is super convenient on rehearsals, when sometimes we want to start "somewhere in the middle", but can't because patch was not changed...Let us know if disabling chase helped.
-
The only difference between your process and mine is that I creat my performances in RM Local Library folder rather than the MyProfiler folder.
yeah, this is huge difference. The issue is that RM and KPA get out of sync easily when you are building a performance using RM with KPA in performance mode (my case). My process is very incremental - I build my performances slowly, often listening to what I just added to hear if new slot plays well with the rest. Doing so from RM always leads to issues, which is super frustrating. If a workflow is allowed from UI it should be predictible.
-
I created a video showing the issue, and as a user I really don't think I did anything wrong (just dragged rig into slot and hit save) and that I should understand more about inner workings of KPA to get this right.
https://www.icloud.com/icloudd…2moDZT54CiQ#KemperPerfBug
Needless to say my RM shows now this (after reloading performance by switching to different one and back):
And device itself this:
They are out of sync. Every single time I try to use this feature (which I always do after RM is updated in hope that maybe this time it will work) I fall into this or similar issues.
-
I did load the performance. The workflow I used was: load empty performance into KPA, then open second window of RM, drag and drop rigs from second window into slots open in first window - saving after each operation. I might have switched slots on device itself to audition previously added slots. Worked great until it stopped and "Crunch" slot appeared and what was supposed to be in slot #5 ended up in slots #4 and #5 with slot #5 renamed to Crunch. As far as I know I had only this one performance loaded. As a user I expect that when I drag and drop rig into slot #5 of performance #23 it will end up in slot #5 of performance #23 and only there (whether is it loaded or not should not matter - it is possible to execute such action from UI, so it should behave as expected). And if RM detects that I'm dragging a rig into slot #5 of performance #23 but in edit buffer it has something else it should warn me, saying: "hey, looks like you are dragging a rig into slot which is not part of loaded performance - this will possibly damage your previous work". But I suspect my case is different anyway - I had single performance loaded all the time. This whole process is too error prone and fragile.
-
Będzie repeta za jakiś czas
-
RM screwed up one of my performances just yesterday using latest version. I successfully used the same worflow to fill in first four slots. When I tried to insert fill in 5th slot, fourth slot contained what what fifth should, fifth slot had what fourth now had (both slots ended up containing the same rig), but fifth slot ended up being called... Crunch out of blue. Performance management is still broken as far as I am concerned and I have all patience in the world and ocean of good. I used various products in the past, both cheaper and more expensive, but performance management in RM is by far the least trustworthy feature and you can't just say it is a user error. User does same thing over and over getting random results and losing work.
