Forums > MaxMSP

Sflist~ preload not working in 64-bit mode?

February 11, 2014 | 2:44 am

Hi, I’m experiencing troubles in preloading soundfiles via the "preload" message to sflist~.
Simply put: it doesn’t work when running in 64-bit mode; it works flawlessly in 32-bit mode (and in Max 5).

Is it possible? Can I be doing anything wrong?
Max OS 10.7.4, Max 6.1.6

Daniele


February 11, 2014 | 7:57 am

I can’t reproduce that with the patcher bellow:

<code>

– Pasted Max Patch, click to expand. –

</code>


February 11, 2014 | 8:34 am

Hi Emmanuel,

your example works flawlessly on my machine; however unfortunately the issue was not on my machine, I’ll try to test it as soon as possible on the other Mac and send you a patch, if needed.

Thx,
Daniele


February 11, 2014 | 11:57 am

Make sure the buffer size are the same between sflist~ and sfplay~.


February 13, 2014 | 8:07 am

hi Daniele,

I am experiencing the same problem.
the funny thing is, I have just installed the new version of bach 0.7.3 and was about to post in your forum: "is there any problem with bach 0.7.3 and prebuffering with sflist~?". but then thought, ok, let’s have a look if there are any issues with the 64-bit version of max and sflist. Now it is YOU asking that question here, haha!
So have you found any answers?
do you think bach might be the reason for the sflist problems? (strange enough it would be though…)

best, nico


February 13, 2014 | 8:41 am

Hi nico,

Very honestly, I really doubt it: I can’t really see why nor how…. As I said, on my machine (with of course bach installed), everything seems to work flawlessly. The problem I experience was not on my machine, and no bach object was instantiated. Moreover, the issue is "deterministic", not "random" (read: "memory shit" :-), which is why I honestly tend to exclude bach from sflist~’s issue :)

(But maybe it’s worth to dig a little bit more: did you have any bach object instantiated when you experienced this problem or before? Did the issue go away when no bach objects were instantiated? This latter could be a big hint, of course.)


February 14, 2014 | 1:41 am

… just to be honest: if you perform a "proper" install of bach, you always have a bach object instantiated – that’s the bach object itself, placed in the extensions folder and responsible among the other things for greeting you from the Max window at startup. But if you remove the bach folder from your packages (you can just drop it on your desktop, assuming it’s not in your search path) you can be sure that bach will not interfere in any way with your system.

It would be very interesting indeed to know if the sflist~ problem disappears after removing bach…

Please, keep us posted!
aa
ps: just for the record, Emmanuel’s patch works on my 64-bit Max, with bach installed of course…


February 16, 2014 | 3:47 pm

Of course, I also have bach installed ;-)

@daniele if you can reproduce that would be useful to know what type of sound file you’re using and if the behavior is the same with sfplay~ (via open and via preload). Thanks.


February 16, 2014 | 6:07 pm

Hi Emmanuel,

unfortunately I have not access any more to the computer where the sflist~ issue occurred. But I’ll keep you posted if I can focus anything weird on my machine (it’s really not the case for now).


Viewing 9 posts - 1 through 9 (of 9 total)