yorolpal
Max Output Level: 0 dBFS
- Total Posts : 13829
- Joined: 2003/11/20 11:50:37
- Status: offline
Can't Name Patches in Amplitube 35 due to X1 retaining focus...
Been goofing with the latest version of Amplitube and noticed that when I try to name a preset or patch certain letters won't type due to X1's key-bindings taking precedence. Some letters just won't type in the A35 save dialog...but they will take actions behind it in X1. I know this used to happen in Guitar Rig 4 as well but I thought it had been fixed. Is there a way around this annoyance??
|
mudgel
Max Output Level: 0 dBFS
- Total Posts : 12010
- Joined: 2004/08/13 00:56:05
- Location: Linton Victoria (Near Ballarat)
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 12:33:44
(permalink)
I know it's no help but it's not affecting me. Are you aware that you need to use the Save or Save As buttons in the top row to th the right of half way to bring up a dialog box into which you enter text. I'm on SONAR X1b245 and just spent the afternoon setting up and playing with the new Amplitube 3.5 (x64) and Stealth Pedal. I have all the Amplitube models and I'm finding it to be a huge improvement. Not that it was bad before but this update is nothing short of awesome. Especially going 64 bit. It's a sign that IK will be moving all their products to 64 bit as they release updates.
post edited by mudgel - 2011/04/16 12:43:35
Mike V. (MUDGEL) STUDIO: Win 10 Pro x64, SPlat & CbB x64, PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz. Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2. Monitors: Adam A7X, JBL 10” Sub. Audio I/O & DSP Server: DIGIGRID IOS & IOX. Screen: Raven MTi + 43" HD 4K TV Monitor. Keyboard Controller: Native Instruments Komplete Kontrol S88.
|
yorolpal
Max Output Level: 0 dBFS
- Total Posts : 13829
- Joined: 2003/11/20 11:50:37
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 12:55:09
(permalink)
Agree 100% about the new A35. Yup, I'm using the Save As button. I'll go back and check again to make sure. EDIT: Yup, went back and checked...using the Save As button brings up the new patch dialog. In this particular instance I was trying to name a preset for my Fender Vibro King. I could not type lower case V or G (in just this particular instance). If I typed lower case v a new envelope appeared ( I assume volume) in the track I was working on. Don't know what happened when I typed lower case g (it used to bring up the adjust Gain dialog)...but it would not type. I'm sure there are many other letters that won't type in lower case. The solution (WORKAROUND) is to just name everything in uppercase. Sigh. It's always somethin.
post edited by yorolpal - 2011/04/16 13:04:04
|
F@ker
Max Output Level: -87 dBFS
- Total Posts : 182
- Joined: 2004/01/03 01:46:22
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 13:03:46
(permalink)
had a similiar issue with another app; the workaround was to keep notepad in the background and type in there, then copy paste :/
|
StepD
Max Output Level: -79 dBFS
- Total Posts : 594
- Joined: 2003/11/08 01:03:52
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 14:38:18
(permalink)
yorolpal
Been goofing with the latest version of Amplitube and noticed that when I try to name a preset or patch certain letters won't type due to X1's key-bindings taking precedence. Some letters just won't type in the A35 save dialog...but they will take actions behind it in X1. I know this used to happen in Guitar Rig 4 as well but I thought it had been fixed. Is there a way around this annoyance??
Is the "Give All Keystrokes to Plugin" button not working in your case?
Core2 6600 2.40 GHz, ASUS P5B Deluxe, 8GB RAM, GeForce GT 630 2GB, 3 Seagate Sata, Echo AudioFire 4 asio, Windows 10 Pro 64-bit, Sonar Platinum, Cakewalk by Bandlab
|
yorolpal
Max Output Level: 0 dBFS
- Total Posts : 13829
- Joined: 2003/11/20 11:50:37
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 15:21:06
(permalink)
Is that the little typewriter icon thing?? I ALWAYS forget about this. That's probably how I got my GRIG 4 to work. Thanks, I'll give her a whirl. Checked the typewriter icon (which is, indeed, give all keystrokes to plugin) and NO CHANGE AT ALL. Still won't take certain lower case letters. Sooo..to answer your question there StepD, ol pal. Yes...the give all keystrokes to plugin is NOT working.
post edited by yorolpal - 2011/04/16 15:26:05
|
Beagle
Max Output Level: 0 dBFS
- Total Posts : 50621
- Joined: 2006/03/29 11:03:12
- Location: Fort Worth, TX
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 15:24:27
(permalink)
if that doesn't work, I'd try using Sonar Plus by benstat and clicking on the MODIFY BIT BRIDGE WINDOWS. you might have to click on it twice to activate it correctly (I haven't mentioned this yet to Ben since it seems to work if I uncheck then check).
his MODIFY BIT BRIDGE WINDOWS will remove the "always on top" focus of plugins using bitbridge. it seems that your problem is actually the opposite, but it might be the same problem causing it is why I suggested trying it.
|
yorolpal
Max Output Level: 0 dBFS
- Total Posts : 13829
- Joined: 2003/11/20 11:50:37
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 15:28:04
(permalink)
Odd too as the new Amp35 is 64bit and wouldn't be using BitBridge. Or would it?
|
mudgel
Max Output Level: 0 dBFS
- Total Posts : 12010
- Joined: 2004/08/13 00:56:05
- Location: Linton Victoria (Near Ballarat)
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 23:25:20
(permalink)
yorolpal
Odd too as the new Amp35 is 64bit and wouldn't be using BitBridge. Or would it?
If it's using Bitbridge it's the 32 bit version. Check in plugin Manager by high lighting the Amplitube 3 VST and check the path. Amplitube3.dll (x64) is 208kb (that's the new 3.5 versions) Amplitube3.dll (x86) is 191kb (that's the new 3.5 versions). All the best.
Mike V. (MUDGEL) STUDIO: Win 10 Pro x64, SPlat & CbB x64, PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz. Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2. Monitors: Adam A7X, JBL 10” Sub. Audio I/O & DSP Server: DIGIGRID IOS & IOX. Screen: Raven MTi + 43" HD 4K TV Monitor. Keyboard Controller: Native Instruments Komplete Kontrol S88.
|
yorolpal
Max Output Level: 0 dBFS
- Total Posts : 13829
- Joined: 2003/11/20 11:50:37
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2011/04/16 23:56:54
(permalink)
No...it's the 64bit version. Odd tho that the "give all keystrokes to plugin" switch isn't working. And here's another anomaly: I thought that since it just didn't want to type certain lower case letters I'd just title every preset in all caps. BUT...if I press the "caps lock" key it still will not type those letters unless I release the caps lock, then hold down the shift key and type the capital letter. "Caps lock" still doesn't work for those particular letters.
post edited by yorolpal - 2011/04/16 23:58:21
|
Axeman49
Max Output Level: -81 dBFS
- Total Posts : 483
- Joined: 2003/11/11 01:51:35
- Location: Brandon, Florida
- Status: offline
Re:Can't Name Patches in Amplitube 35 due to X1 retaining focus...
2012/05/17 01:18:25
(permalink)
My "give all keystrokes to plugin" isn't working either. But F@kers idea works, as a work around. Thanks F@ker. Dan
after all else is exhausted, read the instructions...... Intel i7 3.40 12 Gig Ram M-Audio Delta 66 and 410 4 Terabyte of HD space SATA. GeForce GTX 550 Ti Windows 7 Pro SP 1
|