Jump to content


MalH

Member
  • Posts

    169
  • Joined

  • Last visited

Everything posted by MalH

  1. https://www.iconnectivity.com/audio4c I've used their older 4-out interface for several years with iOS.
  2. Thanks - confirmed with tech support that it's not possible to change the assigmment for the pedals, which is very poor for a midi controller keyboard. It makes it impossible for me to use the sustain pedal to change the leslie speed on the YC88 organ which has a fixed CC#.
  3. Just received a new Novation Impulse 61 to use as a top keyboard, but I'm unable to assign new MIDI control messages to either of the pedals. Is this is a limitation or is my unit faulty? If so, it seems a huge issue for what's otherwise a full feature MIDI controller.
  4. I finally made a choice on my next keyboard and received last week a Yamaha YC88 - what an amazing keyboard! I spent today running a comparison of the latency of the YC88 in-built sounds vs an iPad running through the YC888 audio interface. The result is that the iPad is about 20ms delayed which, while not large, is nevertheless noticeable to me for piano, epiano and organ. I'll therefore be relegating the iPad for synth pads and backgrounds only. Here's what I did: Load the YC88 piano patch (CFX) and pan it left. Connect the iPad (2nd gen 12.9inch iPad pro) via usb to the YC88. Load Korg Module piano patch on the iPad (hosted by AUM with 128buffer @44.1kHz) and pan right. Configure MIDI to send from the YC88 to the iPad. Record the stereo output of the YC88 into a separate computer and interface running Logic Pro. Play various notes on the YC88 keyboard. Compare the note start times - the right channel is delayed by about 20ms compared to the left. Malcolm
  5. I'm using a 2nd Gen iPad Pro 12.9". As I mentioned, the latency is not large, but I noticed recently when I switched to playing a couple of hardware instruments in rehearsals that everything felt more immediate. It was subtle, but large enough to make a difference to my playing. Maybe it's my interface, so a comparison on a keyboard with audio interface such as the Numa X or Yamaha YC would be interesting.
  6. I'd very much appreciate it if someone who has a Numa X were able to perform a similar test e.g. create a setup that sends an internal piano sound to the left stereo output and a Korg Module piano panned to the right channel and record the output playing a few isolated notes. You can get the latency by looking at the wave in any DAW or post it here.
  7. I've been running an iPad as my main sound generator for the past couple of years but am about to go back to a hardware solution. The reason is latency. I have been running various hosts (Module, Auria or AUM hosting AUV3) all with a buffer of 128 @44kHz but there is still a very slight difference between the responsiveness compared to hardware. Last week I decided to quantify this by recording the outputs of my audio interface (iConnect Audio2+) hosting Module in parallel with the outputs of my keyboard (Casio PX5S). After optimising latency as much as I could, I could not get the interface to respond faster than 10ms slower than the hardware. This is not huge, but is like moving your monitor speaker about 3.4m further away, which does change the way you play. I will still use my iPad for pads, but for piano, epiano and organ I will stick with hardware.
  8. Just updated my main audio desktop hackintosh without issues. Logic and and all VIs running great. I almost managed to upgrade my 10-year-old hackintosh server. Unfortunately I haven't found a working solution to get metal running on the old NVidia GPU.
  9. I had a TX7 for a decade or two but did not get into it. So... what does a DX7 give you that software doesn't? They're both just bits and bytes...
  10. How many velocity layers do you detect? The PX5s has 4.
  11. I'm using an iConnectAudio2+. All midi channels are set within the apps themselves. The only routing that needs to be setup on the interface is that the interface's DIN MIDI input needs to patch to the iPad and the iPad audio out needs to patch to the analog outputs. It's just one set of 16 MIDI channels into the iPad and one stereo audio stream out. All apps receive from the same MIDI input and send audio to the same stereo output. I'm using a 2nd gen iPad Pro. I think this has 3GB RAM, which is needed for running all the apps concurrently. I don't get any breaks in the audio. I don't have a master EQ, as I dial the SSv3 to suit the room, but with the iConnect device it would be possible to route the audiostream with all the instrument sounds to another stream that is sent to an EQ app. The iCOnnect device is very powerful for internal routing and talking to the iPad. This would greatly increase complexity though.
  12. I've never felt I had a stable enough setup using a master host such as Audiobus or IAA. My preference is just to set each app on it's own midi channel and let them all talk to the audio interface directly. This has been bombproof. I can run concurrently: Ch 1: Korg Module, receiving program changes to switch between Ivory and Scarbee. Ch 2: Ravenscroft Ch 3: Galileo 2 Ch 4: Auria Pro routing to a 5GB piano SFZ Ch 5: Auria Pro routing to a 3GB Rhodes Suitcase SFZ, with Fabfilter Saturn saturation and distortion Everything is set to a 128 buffer. If Auria is launched before Ravenscroft, Ravenscroft will also run at 128. This all runs in the background while I use ForScore for charts.
  13. I have Cubasis but Auria Pro is by far my choice. It has an excellent soundfont player - the only one for iOS that can stream from disk, enabling you to run multi GB pianos. It also has the Fabfilter plugins for in-app purchase.
  14. I started daily boogie practice about 3 weeks ago for the same reason - to get some of that independence back. Luckily it came quite quickly. Once the brain learns the LH pattern you can switch the LH to autopilot and concentrate on more complex rhythms in the RH.
  15. An excellent instrument: very detailed and cleanly sampled (no hiss), very even tone, fantastically playable. I prefer a Steinway sound but this is a great complement for my Vintage D and Ravenscroft.
  16. I ported an open-source player to iOS: https://forums.musicplayer.com/ubbthreads.php/topics/2900811/SFZero_an_open_source_SF2_and_#Post2900811 I'm using the latest iPad Pro 12". I implemented stream-from-disk in the app in order to run large instruments. AUv3 on iOS are only limited to several hundred MBs RAM.
  17. The main limitation is the overall file size (2GB) as it uses 32-bit addressing. Otherwise no limitation on sample length, number of samples/splits/modulators. It's been superceded though by SFZ, which is just a text file referencing a bunch of sample files in any format. I run a 4GB SFZ Rhodes instrument on my iPad, which compresses down to 2GB flac files.
  18. I played the CA98 for about 30 minutes last week with high hopes. I was disappointed with a boxy sound and spongy bottoming of the keys. I much preferred the Yamaha 675 sitting next to it. I'm waiting on the Novus NV10 with even higher expectations. Up until now I've always used a stage piano (MP8) with near field monitors, but need something more acoustic-like for a teaching studio.
  19. 30 feet is adding about 26 ms of latency. That's becoming noticeable I would expect.
  20. An M-S recording usually uses an omni mic for the mid and something more directional for the side. Therefore the mid is not really what is common to both channels but the sum of the two.
  21. Another new adopter here after following this thread for the last 12 mths. I took the SS on its maiden gig last to an outdoor big band concert here beside Lake Zurich, Switzerland. I decided on the SS after dissatisfaction with my trusted but ageing Samson powered 12" PA and many comments from the band that they would like to be able to hear the piano better. Last night the SS was on an amp stand on its side with the side speaker reflecting off the paved ground. The source was a PX5s direct into the amp - not my favourite piano sound but surprisingly good with the SS. At home I had been testing the SS with my preferred piano - an adaption of the Galaxy Vintage D for an old E-mu sampler. All I can say is wow - complete satisfaction! All the band and conductor could hear the piano much better, but what I was most surprised by was how much clearer I could hear myself. With such an open sound, I could hear the subtleties in the playing much much better and respond with much greater control of dynamics. Thank you Aspen!
  22. Interesting topic as I just tried Pianoteq 5 and it's the first version I've played that comes close to the big sampled pianos to my ears. I think Pianoteq runs under Linux. I've just setup a Raspberry Pi as a media centre with IQAudio DAC+ for about $100. The Pi-2 has a 4-core ARM processor running at 900MHz with 4 USB ports. That would be a very cool solution if it could run Pianoteq. The IQAudio DAC+ sounds superb - Ti Burr Brown 384kHz DAC with 110dB S/N for £30.
  23. My initial post on the topic was not meant to mean building a SS from scratch, which I agree is difficult and wouldn't be worth the effort unless you wanted something bigger. I meant rather using powered monitors exactly as Keys has done. 20kg is still heavy for me with back problems, so if I can get a good approximation with 2x12kg I'd like to try. It also means I can try using active monitors that I already own.
  24. Correct, but my understanding is that the SS side speaker sends an out-of-phase signal out the other side of almost equal amplitude, which a standard PA speaker won't do. Hence my suggestion to use 2 out-of-phase side speakers.
×
×
  • Create New...