]]>
Normally it will be solved in the next release 1.1.009.
Thanks for all your feedbacks.
Statistics: Posted by senso — 10 Aug 2014, 21:49
]]>
also agree that the bug should be fixed but..... Blaakk.... how could I be thankful enough ????
You never could be. Muhahahahah. 
How did you get on with your gig then fractilist??? Nice one for t'other solution seamus/shawn!! I remember doing some pretty crazy routing in my first few days of HH.... forking a few midi streams, array-bending them, routing to various destinations (including midi LAN out, midi-busses) receiving at client, recording to piano roll, duplicating, sending back through a bus, etc. All of which behaved, yet all this type of routing began in the same device (following your original advice I believe).
Apologies for having 'jumped ship' here. Not long after my posts, I screwed up my SSD system drive and have since been in amongst getting to grips with GPT/UEFI installations (ie trying to fix it), and trying out Linux distros, studying driver development, Python, C/C++, JS/Coffeescript, version control and basically all that'll help me achieve controllable real-time audio-reactive shader pleasure (and stuff that probably wont). Khronos headers FTW! As well as all WebGL/GPUPU/Parallel Computing! And virtual networks/machines!
Hehe.... I'm getting there.
Sorry, a little diversion for yas here............ I was curious about something which I thought was a bug in the software (HH) on first opening my shiny archive a few months back... namely the demo workspace 'The Grid'. The audio was cutting out on line 3 'The Groove'. The reverb send was/is causing this in some way somehow. Not really a bug as such but... an inconvenience for any newbie sequentially working through these workspace tuts.
Thankfully related advice on the matter initiated a much needed system upgrade... but even with my new rig the same problem remains. Fresh install, current system/audio/video drivers, Win 8.1 (very impressed with this OS btw)..... loading 'The Grid' from an untouched extracted 1.1.008m (no chance of tainted config files as described be sephult) and then playing results in silence on switching to line 2.
Could any of you guys check this out from a fresh archive?
Statistics: Posted by Blaakk — 10 Aug 2014, 10:42
]]>
I have multiple midi input devices, including a device I use as my master midi clock, and a couple of controllers. (Lots of PBs and CCs...)
I had lots of stuck notes... Many, many stuck notes... Reading this thread, I opened all the little midi device patchlets and disconnected Midi to Usine in each. Instead, I sent data straight to a midi bus. Similarly, in my patches, I disconnected ALL uses of Midi Input, and instead used my new midi buses.
I was going to do this anyway, since I think it is the only way to route data from different input midi devices/ports discreetly to different destinations. Send to Usine/Midi Input seems to merge data from all ports (which may explain things getting "tangled" as described above).
Anyway, hours of playing later and NOT ONE stuck note.
I'll see if this holds true over many days/ hours. So far, so good.
This is definitely a Usine issue. I have used the same gear/setup with other hosts & had no dropped notes. I abandoned the others for the programmability offered by Usine.
Hope this helps,
Shawn
Statistics: Posted by shawnb — 09 Aug 2014, 09:05
]]>
]]>
I wonder If Senso is aware of this issue. I will file a bug report.
EDIT solution found!
in the midi devices i filter out the CC1 mod wheel info from the logidy controller and send that to a midi bus. this seems to have fixed the problem! YEAH! thanks everyone for your help!
Statistics: Posted by seamus — 29 Jul 2014, 22:37
]]>
]]>
Also are you sure all of your drivers are x64 as well? My earlier mention about the MOTU Midi Xpress was a driver problem that mostly happened in Sonar but would work other places quite well.
Definitely tricky business but you will get there.
I guess in my problem I was fortunate enough to get blue-screens ...lol. My first Win SDK debug experience but led me right to that driver every time. After bug reports, and no response. Magically Motu Drivers became solid for x64
Statistics: Posted by sephult — 26 Jul 2014, 14:29
]]>
I am using the latest hollyhock 64 bit.
Statistics: Posted by seamus — 26 Jul 2014, 00:33
]]>
Even with the laboratory in rack I did not have the glitches. In my case the only time I see glitches is if I am receiving timing clock from the LoopMIDI and it reaches the USINE interface in the device.
Is this close to the test you are explaining?
What version of HH you using are you purely x64 for all of your drivers as well?
I am using 1.1.008m x64
Statistics: Posted by sephult — 25 Jul 2014, 23:14
]]>
As I said before I don't encounter this problem in ableton so it is a Usine specific issue. There are many things that I can only do in Usine so I'm not about to give up on the software and as you can see above there are others who are experiencing similar problems.
Did you try the test I outlined in an earlier post?
Statistics: Posted by seamus — 25 Jul 2014, 21:42
]]>
I use a ton of MIDI devices simultaneously but do not see a problem this specific.
That case almost sounds like an install/config or Driver problem.
Have you tried de-activating all of your MIDI from setup then deleting all of your MIDI devices out of the "Devices" panel?
I would then re-scan MIDI and re-create them in the "Devices" section by activating them again. See if that behavior still exists.
I have recently noticed an issue with Arturia Beatstep, where every time I must delete the device from the panel, and re-activate.
If not I will get odd or no response. When I do all works as expected. I do not have to do this with any other devices.
Maybe there is a disconnect somewhere between the setup activated devices and the config/devices panel...a clue?
Statistics: Posted by sephult — 25 Jul 2014, 18:13
]]>
Statistics: Posted by seamus — 25 Jul 2014, 17:54
]]>
Actually I just realized I put it in the add-ons. It's rough and I need to update. Basically I used two faders 0-127 integer Data IN to Output and a Knob set to Integer, 0-2. Mode 0 is bypass, 1 is Odds, 2 is evens. If you filter you can limit the CC flow into usine to only respond to your odds or evens...this might help.
Or Maybe you can isolate by splitting the Notes from the CC values on the input device that might help you identify exactly at which point you are having the overflow.
Statistics: Posted by sephult — 25 Jul 2014, 16:00
]]>
]]>
]]>
]]>
]]>
Very interested on trying this example out and I will do so.
Statistics: Posted by sephult — 19 Jul 2014, 20:28
]]>
We follow this discussion and we made tests
about Midi CC + note corruption we'll of course, investigate around Usine device but you can also have some midi interface drivers which reach their limit quickly when sending a lot of informations
here an example
to test it , you need a sound card with Midi IN/OUT and a Din cable, send the rack 1 to the Midi input of your soundcard, the rack 2 receive the Midi Out of this same card. play the rack 1 and record on rack 2
note that this patch send a lot of informations , this don't correspond to real life , it 's only to stress the Midi flow. so be careful. For example it's a good idea to let the piano roll closed..But the result is that we don't have any corrupted notes( tested on several machine ( PC and Mac) , so this means that Usine can work with a big Midi flow
about the same question, some tips to test:
if you want record with the piano roll with heavy Midi flow, try to filter by events type and record them in different piano roll to test ( 1 for CC, 1 for notes...)
if you have several card or midi interface, test different configurations, avoid USB hubs, try different usb port and so..
Statistics: Posted by nay-seven — 19 Jul 2014, 19:11
]]>
At about 2 mins I can quite audibly hear fall behind with just two metronomes to a backbeat.
Statistics: Posted by sephult — 19 Jul 2014, 18:38
]]>
-S
Statistics: Posted by sephult — 19 Jul 2014, 18:17
]]>
HollyHock 1.1008m x64 - Rack 1, Tobias Ericson LoopMIDI set to receive midi time clock.
I add Native Instruments Absynth 5 to track 2 using a MOTU MidiExpress port 1 - with a Yamaha M1 controller.
Results - MIDI response seems to be altered for note on at first, picking up a few notes here and there. Next it seems to be responding fine then all the sudden I end up with stuck notes. After panic the same response occurs.
I will try a few more configurations today and see if it just my configuration or what is going on. However I do not ever recall having this issue with the same setup.
-S
Statistics: Posted by sephult — 19 Jul 2014, 18:06
]]>
]]>
-S
Statistics: Posted by sephult — 13 Jul 2014, 16:22
]]>